this post was submitted on 23 Jan 2026
43 points (97.8% liked)
technology
24211 readers
315 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Idk, seems like the device (why is it a identifed as a gamepad?) doesn't respond. I guess in theory it could be the cable/connection, but I assume the thing worked fine in windows? Maybe worth trying to change the cable if that's possible anyway.
I really doubt that the Linux HID or USB drivers are actually at fault/bugged here, they work with thousands of different similar devices totally fine. Maybe that's something that might be fixed by a firmware update?
For a workaround, you might try
usbreset. You could (say) write a script that either runs every 15 minutes as a cronjob, or it looks at the logs and triggers automatically when it sees these relevant errors or something like that.I suspect it's udev issue. Udev is the system responsible for (among other things) identifying hardware and assigning the proper driver to it. It is sometimes necessary to add explicit udev rules for some obscure hardware to force the system to prefer one driver over another, or to recognize some wierd ass USB device would be perfectly happy being treated simply as e.g. a serial device. One somewhat common situation is explicitly telling udev to tread obscure knockoff gamepads as if they were an xbox controller.
I don't think so, it wouldn't even work if it wasn't recognized as keyboard. It probably is recognized as both a keyboard and a gamepad at the same time. Physical USB devices can (and frequently do) present as multiple devices to the host. For example, a keyboard with a scroll wheel will look like be both a keyboard and a mouse.