this post was submitted on 23 Jan 2026
43 points (97.8% liked)
technology
24182 readers
261 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
For your keyboard problem, try looking at the kernel logs, which you can see by running
dmesg. Congratulations for having an exotic af problem I didn't even know could happen.I don't have high hopes you can fix this honestly, keyboards are like the most standard hardware using the most generic driver, which means your keyboard somehow differs from all other keyboards in some subtle way, and Linux driver just happens to trigger this problem while the Windows driver doesn't. What you could probably do is a workaround, like resetting the USB connection or something like that every so often.
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.
ive tried two different cables and it works fine in windows
im wondering if it has something to do with it also being recognized as a gamepad?
i found this https://www.reddit.com/r/linuxquestions/comments/txwwne/unbinding_subhid_devices/
im wondering if it gets recognized as both a controller and a gamepad and when the "gamepad" logic doesn't see any input it just puts the whole device to sleep? i dunno im so lost
i might just try flashing qmk onto it
Idk for sure, but this theory seems far-fetched to me. Why would it put a gamepad to sleep at all? Why would putting the gamepad HID device to sleep affect the keyboard HID device? Why wouldn't the same thing happen on Windows?
Btw, just for my curiosity, what extra feature does this keyboard have that might make it show up as gamepad as well? Does it have an analog stick on it or what's going on here?
it doesn't have any bell or whistle that should make it show up as a gamepad, tbh to me it seems like a dev covering one too many bases or something because there really isn't any reason for it
Btw I just googled USB power management, and on Linux the default USB "autosuspend" seems to be 2 seconds. So it going into power safe mode after half an hour seems unlikely.
fingers crossed but I think I may of fixed it, i went through its old firmware updates and found the oldest before any mention of a "game mode" and it seems to function properly now for some reason
also when i use lsusb it just reads as a keyboard now instead of a gamepad
A Reddit link was detected in your comment. Here are links to the same location on alternative frontends that protect your privacy.
its very strange, in linux it never gives me the "usb disconnected message" and all the led lights stay on, it just stops responding
Seeing complaints of the same issue on macos too even though it is explicitly marketed as supporting it.
Supposedly this keyboard supports PS/2 so you could plug it in with a usb-PS/2 adapter if your PC has a PS/2 port and that should fix that problem but you'll lose your rgb or whatever.
As others have said this is probably some enshittification from the manufacturer. Software control center... it's a fucking keyboard... also a lithium battery... why.. keyboards can last decades even wireless ones using AA batteries... this thing is destined to be ewaste.
welcome to linux. only now can your hatred be pure.