8bitdo Adapter 2 does not work in Bazzite 3.5

Since updating my steam deck (Bazzite-Deck-Gnome version) and my main desktop (Bazzite-Gnome) today, both systems stopped recognizing the 8BitDo adapters, with which I connect my Dualsense controllers. The Dualsense still works wired and over bluetooth (both on my desktop and the deck), so the issue is specifically the 8BitDo adapters which are not recognised by Bazzite anymore. Also note, they are two separate adapters for two separate controllers, for two separate systems. On the nintendo switch the dualsense still works fine over de 8bitdo adapters. I have not been able to scrounge the changelog in details for xinput, xpad, xone, or udev rule related updates, but wanted to already create the issue in case someone already knows why this happened.
Solution:
hmmm, replugging the adapters already did the trick.
Jump to solution
8 Replies
Kyle Gospo
Kyle Gospo4mo ago
should be unchanged, same xpad and xonedo we've been shipping since 2.5 we did make some minor bluetooth fixes, but those were just configs what does your adapter report itself as?
Nivve
Nivve4mo ago
What command do I run to check that?
termdisc
termdisc4mo ago
lsusb for example, my 8bitdo Ultimate adapter appears as Bus 001 Device 003: ID 2dc8:3109 8BitDo Ultimate Wireless Controller you may need to run lsusb once before plugging in and then another time after plugging in to see differences if it's not reporting properly
Solution
Nivve
Nivve4mo ago
hmmm, replugging the adapters already did the trick.
Nivve
Nivve4mo ago
Weird, I am using them for multiple weeks on the systems and I never had to unplug them before
Kyle Gospo
Kyle Gospo4mo ago
certifiable computer moment
Nivve
Nivve4mo ago
jep I did some testing and it keeps working pretty consistently by just rebooting. However, when I freshly connect it (while powered off) it seems to need a replug once booted Not sure what component handles this, and why this replugging is necessary suddenly, but I can then just assume this is not an issue created by bazzite itself.
Nivve
Nivve4mo ago
Marked it as solved, as it is most likely an upstream issue and replugging does fix the issue temporarily.
Want results from more Discord servers?
Add your server