I had similar worries about the AMD driver stability before I switched from NV about 5 years ago. But my experience has been great even back then and things have only improved since.
One data point to consider is that Valve is shipping the Steam Deck with an AMD AMU and stability and compatibility is paramount for that use case.
Any naming convention is fine as long as it’s meaningful to you. But it’s a good idea to keep your own repos separate from the random ones you clone from the internet.
What I see is an inexperienced developer who instead of systematically debugging the issue keeps trying random stuff hoping that it will somehow work.
Thanks. I tried to make sense of it and experimented a bit with making the same ioctl’s mentioned but couldn’t get it to work. I either didn’t get it right or it’s something else.
Maybe I will take another look later but for now my workaround is to just fire up Baba Is You which idles at a low cpu use and then run evfwd with the grab option so that Baba no longer gets the input.
Yes, that works too with one fairly big caveat: for some reason the Steam Deck’s controller is not producing evdev events until a game is actually running on the deck. So evfwd is not receiving events while the Steam UI is active. I haven’t been able to figure out yet why this is the case.
If you want to try it you can start a random game on the deck and then fire up evfwd on the controller device and using the -g (grab) flag to avoid passing events to the running game.
Edit: while we are talking about the Steam Deck: when ssh-ing to the deck it can be helpful to turn off wifi power management to avoid lag: iw wlan0 set power_save off
Ugh, that’s a pretty insane default. Thanks for the heads-up.