• 1 Post
  • 17 Comments
Joined 3 years ago
cake
Cake day: June 11th, 2023

help-circle
  • Ah, yeah the Nacon WRC games are weird. I could never get them to work either but just with device detection in general, not only my wheel. Also people tend to say they weren’t amazing in terms of FFB feel and gameplay either so I stuck with the more popular titles. You’re totally right and I had completely forgotten that those games are just non-functional at the moment.

    I don’t use lutris for anything, I run umu directly with proton-ge for RBR and a few other non-steam games and it’s been great. Upgrades are as easy as just launching explorer in the prefix and double clicking the RSF installer, and since 10-22 I think you don’t even need the dll overrides since they are included in recent proton-ge. My opinions of the game and RSF are not as amazing though so I admittedly don’t play it much. I used to a lot but found interacting with the community to be pretty taxing at best, and not good as a Linux player. All the wine/proton development work in the world can’t improve a community that is borderline hostile towards a subset of players.

    JacKeTUs has a fork of proton-ge which helps with device detection stability which is the issue with AMS2. They are working on upstreaming that work I believe, but I’m unsure what the status is. From what I’ve heard soon devices constantly unbinding in many games will be fixed very soon across the board in wine. Assuming there are no holdups with that work that I’m unaware of. For now I do as you said and rebind my wheel axes every time. It does seem to remember buttons and other controllers though, just not the steering axis.


  • Yeah, my t300rs worked on linux but that’s because there’s a kernel module for it. Which it looks like they have expanded since I last took a look, so that’s cool. But I ditched it for the DD ffboard a while back.

    In terms of rally games not working, which ones are you having trouble with? I play all the big ones that people talk about and haven’t had any issues but I don’t have a moza wheel so I’m not sure what specific issues those have. Apart from EA WRC which doesn’t run anyway (and when it did I never thought it was that great of a game). ACR has input issues on windows too unfortunately.

    The SROL discord can be pretty helpful since it was started by a couple of very active developers in that space including the dev responsible for universal-pidff. I think the situation is quite good and always improving, but still depends a little bit on what hardware you have. There are some less popular wheels that are completely unsupported still. It also doesn’t help that iracing and EA are actively hostile to the linux community.








  • This. I had symptoms extremely similar to OPs and saw this in the kernel logs immediately before the system would reset:

    [    0.705185] mce: [Hardware Error]: Machine check events logged
    [    0.705187] mce: [Hardware Error]: CPU 17: Machine Check: 0 Bank 5: baa0000000090150
    [    0.705190] fbcon: Taking over console
    [    0.705191] mce: [Hardware Error]: TSC 0 MISC d012000200000000 SYND 4d000020 IPID 500b000000000
    [    0.705195] mce: [Hardware Error]: PROCESSOR 2:a20f12 TIME 1678252812 SOCKET 0 APIC 3 microcode a20120a
    

    It turned out to be a hardware issue with my CPU (AMD Ryzen 9 5950X). I got it replaced under warranty (twice actually, the first replacement had other issues) and everything is fine now. Definitely check what the kernel logs say.

    You can look at the previous kernel log from before a reboot with journalctl -k -b -1 (as root)







  • Gatgetbridge (your link) has a breakdown of devices they support https://gadgetbridge.org/gadgets/ . You can click through the vendors to find devices which are both “highly supported” and “no vendor-pair”. Meaning most/all the features work without any reliance on the vendor app.

    As for the similarity you are asking about with pixel->GrapheneOS, there are very few watches that can run an alternative open source firmware or operating systems apart from the ones that are already open source, like bangle.js, pinetime, etc. Wearables are even more specialized than phones, they require specialized code designed specifically for them and would likely require pretty extreme effort to reverse-engineer.

    I use a pebble 2 HR with gadgetbridge but the watch it self runs the old pebble firmware which gadgetbridge talks to. This is fine for me, but if you are looking for a more modern watch you may have to make some compromises.


  • Ok, I’m prepared to be downvoted today so here goes.

    Nextcloud is an enterprise cloud suite. The one you run in docker on your rpi (or whatever) is the same one that is run at a company, albeit with more high availability and redundancy, but the same application, proxies, caching, db, etc. Nothing is stopping you from running the stable channel and testing your upgrades, or even rolling out specific stable client versions to your devices.

    Said companies often have teams (more than one person) to run it, stage upgrades, automated testing, automated backups, monitoring, etc. They go to work and do just that, maybe not every day but at least a couple times a week their focus is Nextcloud and only Nextcloud.

    What many people in the self hosting community do is spin up docker, without ever having touched docker before, and try to run Nextcloud, forget that it exists, and then upgrade it a year later across multiple versions without maintaining the database. Then they obsess about how fast an app loads by refreshing it a whole bunch, and then complain on internet forums that it sucks. This, like many posts, doesn’t have a specific problem for us to help with, no logs or stack traces have been posted, and the subject of the complaint shows just how terrible your understanding of application security is.

    So, while there is legitimate criticism of some of Nextcloud’s design choices, this isn’t it. And at the risk of sounding a little gatekeepy, if you post “nextcloud updates break everything” with no context you probably should spend some time gaining a better understanding of how internet facing services work and make an attempt to fix the problem (probably misconfiguration, and in this desktop client case probably a heap of un-updated local software installed alongside the client), which I’m sure people would find if they did the bare minimum of reading a few log files or any of the other things that come with being an application admin.