USB devices disconnecting
USB devices disconnect (and reconnect, if wired) constantly, i believe it's related to this usb powersaving setting I'v found, but I am very inexperienced with linux overall and am having trouble troubleshooting this properly
setting is located in /sys/module/usbcore/parameters/autosuspend.
far as I can tell, there's no actual corresponding setting for this listed anywhere, not anywhere obvious like power-management atleast
trying to figure out how to overwrite that file, my understanding is that with bazzite being an immutable distro there's no easy way for me to actually edit system files like that.
it'll ask for my password to elevate access when attempting to save over, but then it'll still say i can't overwrite
making the change permanent is separate issue though, right now i'm just trying to figure out if that's actually the cause of my weird usb-devices problem, but I can't figure out any way to change that 2 to a -1. any help would be appreciated.
Solution:Jump to solution
just like any other linux system you can just add
usbcore.autosuspend=-1 to the kernel arguments to turn off usb autosuspend
in bazzite you do it with
rpm-ostree kargs --append-if-missing="usbcore.autosuspend=-1"
also the only read only part of the system is /usr...11 Replies
Solution
just like any other linux system you can just add
usbcore.autosuspend=-1 to the kernel arguments to turn off usb autosuspend
in bazzite you do it with
rpm-ostree kargs --append-if-missing="usbcore.autosuspend=-1"
also the only read only part of the system is /usr
/sys is temporariy so nothing you change there is kept even on a normal distro so nothing of what you have been trying to do would have been stopped by bazzite having /usr read only (you also need to change the files in /sys using echo blah | sudo tee from a terminal prompt to temporarily change them)thank you, and it does appear that that autosuspend setting was the cause of my problems
believe it has to do with the software certain usb-dongles use
aaaaand apparently not, it happens less frequently now but still enough to be annoying.
now instead of disconnecting entirely the cursor still shows but is completely unresponsive until the dongle is removed/reinserted.
as I'v mentioned, very new to this kinda of stuff right now, need to figure out just what's causing it to disconnect.
I'm fairly sure it's just because this dongle wasn't meant to be used with linux, or atleast I hope it's a problem with the dongle. i already know one of my usb ports is bad, would suck if more are failing.
guess the first thing i do is switch ports and hope it still fails...
all i'v got right now is this lsusb log and i'm not sure that's very useful (also the same using any port), more useful would be an active log of the device as it disconnects but i'm not sure how to do that.
so apparently the input logs already exist in /dev/input, i just got to figure out how to access them?...
I've never heard of a dongle needing anything you've done here
Ever
idk how much usb stuff you got on your system, but if you are like me and have a lot of usb devices connected, its worth noting you can overload the usb controller, in which case the whole usb controller fizzles out until you reboot.
in that case it would be worth moving around some of the usb devices (also in my specific case i noticed the one that always fizzled out for me was the one with usb-c whenever something was connected to that)
how much would be considered "a lot"?
alls i got is mouse/keyboard/headphones, that's like...the bare minimum
mine is a bit overkill but one of my controllers is currently handling 22 usb devices :clueless:
but i have seen controllers sometimes struggle with just 4 (2 ports but youre using a hub to get more ports) if one of them is high enough power
yeah that should not affect it, all i can recommend is if the dongle is using a usb hub or something (or usb c to usb a adapter) it would probably help to connect the dongle directly into the port without anything inbetween if possible
thats all the advice i have
already doing that, never really saw a need for hubs with just 3-4 devices
I see logs being populated in /dev/input whenever this disconnection happens, but can't for the life of me figure out how to actually read the damn things.
you only have a usb-c port free, you get a usb-c to 4x usb-a hub
there is your scenario
oh, no. it's just regular ol' usb-a to usb-a
i just gave you an example of where a 4 port usb hub might be needed and the controller might be crap 😛