ckb-next does not recognize my Corsair K95 RGB Platinum keyboard

308 views
Skip to first unread message

Manish Jain

unread,
Feb 5, 2021, 5:47:25 AM2/5/21
to ckb-next

I am on Manjaro KDE Linux kernel version 5.4.

I just purchased a very expensive Corsair K95 RGB Platinum keyboard for its Cherry MX Blue switches. The keyboard has fantastic tactile feedback, which is what I needed.

But I have run into a major problem: the colours on the keys of the keyboard keep constantly changing - which directly runs into a medical condition I have (Obsessive Compulsive Disorder). My eyes and my brain badly need the colour on the keyboard keys to be static (single, uniform colour) and locked (not constantly changing). This is possible on Windows with Corsair’s iCUE software, and is supposedly possible on Linux too with ckb-next. I installed ckb-next from Arch User Repository but that leads me to the bizarre situation that ckb-next, on application startup, reports “No devices connected”.

How do I get ckb-next to recognize my Corsair K95 RGB Platinum keyboard?
I read somewhere that adding 'usbhid.quirks=0x1B1C:0x1B08:0x20000408' to Grub's commandline helps to fix the issue, but that does not work in my case. Although interestingly, when I hit the Generate Report button in ckb-next, I get a listing for my keyboard:

"Bus 001 Device 002: ID 1b1c:1b89 Corsair CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard"

Can somebody be kind enough to help me out so that ckb-next starts recognizing my keyboard ?

Thank you,
Manish Jain

Reply all
Reply to author
Forward
0 new messages