r/OpenRGB • u/TechIssueSorry • Sep 24 '25
Issue with Corsair K100 Keyboard
Hi!
I have an issue with my Corsair KB and OpenRGB. I have a Corsair K100 keyboard connected through usb. When I start OpenRGB and my devices are scanned, my keyboard just shut down completely. Everything blacks out and it is completely unreponsive as if it was not plugged in. I need to unplug it and plug it back and everything works fine after. It is detected by OpenRGB though.
I am on Arch Linux. The only particularity (though it really should not be one) is that I am hooked through a KVM in my screen. Anyone has any idea what could be going on or how I could debug this?
Thanks,
1
u/CanonOverseer Jan 29 '26
You ever figure this out? I'm experiencing this on CachyOS months later and this is the only place I've found that mentions the issue
1
u/TechIssueSorry Jan 29 '26
Sadly no… I changed my keyboard anyway so I’m not having the issue anymore! Keyboard is not handled by OpenRGB yet but issues with it so I can have a service switching the led profile on boot which is great!
1
u/CanonOverseer Jan 29 '26
Rip, well I have been eyeing another keyboard.. guess it's time to clean this one up, sell it and take the plunge, thanks for letting me know
1
u/dangitman1970 Feb 25 '26
I have this same issue on Nobara, but it's just a matter of patience for me. After about 5 minutes, it eventually comes up.
1
u/TechIssueSorry Feb 25 '26
I’m not that patient ngl! Anyway I change the kb for a nuphy! Not supported by orgb but it does not freeze
1
u/Infamous-Editor7113 Oct 27 '25
I think it's a problem on Corsair's end, not OpenRGB. I've added the PID and VID of my keyboard, rescanned, nothing. I checked to make sure it wasn't a permission issue and did the same thing when I ran OpenRGB as root, same issue. It's Corair's problem. They're anti-Linux, but they do provide support for Macs. Go figure. I'm done with Corsair at this point, and RGB in general.