Arch Linux

Shinigami92

Member

From: Germany

Registered: 2020-09-11

Posts: 16

Website

Corsair K95 RGB not responding after login

I have a wired problem with my keyboard Corsair K95 RGB

When I boot up my PC everything is working fine
I see SDDM login screen and type in my password to log into KDE Plasma (not-wayland)
Then after the login in around 90% of the case my keyboard is not responding anymore
ckb-next has loaded and the keys turning blue (my lightning setup)

Now I have to go to the back of my PC and unplug both usb cables of the keyboard and replug them.
The keys turned white (I think thats the default lightning) and everything works (I can write again)

---

So what I have found out until now:

I have a Win 10 VM via qemu/kvm
At the bottom I have this setup

...
  <qemu:commandline>
    <qemu:arg value="-object"/>
    <qemu:arg value="input-linux,id=mouse1,evdev=/dev/input/by-id/usb-ROCCAT_ROCCAT_Kone_XTD-event-mouse"/>
    <qemu:arg value="-object"/>
    <qemu:arg value="input-linux,id=kbd1,evdev=/dev/input/by-id/usb-Corsair_Corsair_K95_RGB_Gaming_Keyboard_1804301EAEBE08015632C7E8F5001941-event-kbd,grab_all=on,repeat=on"/>
    <qemu:arg value="-audiodev"/>
    <qemu:arg value="pa,id=snd0,server=/run/user/1000/pulse/native"/>
  </qemu:commandline>
...

This doesn't work sometimes because it says it can not detect my keyboard

So I looked into

/dev/input/by-id/

and found these devices:

ckb-Corsair_K95_RGB_Gaming_Keyboard_vKB_-event -> ../event12
ckb-Corsair_K95_RGB_Gaming_Keyboard_vM_-event -> ../event13
usb-Corsair_Corsair_K95_RGB_Gaming_Keyboard_1804301EAEBE08015632C7E8F5001941-event-if00 -> ../event24
usb-Corsair_Corsair_K95_RGB_Gaming_Keyboard_1804301EAEBE08015632C7E8F5001941-event-kbd -> ../event22

(and some other stuff thats irrelevant)

I need too swap

/dev/input/by-id/usb-Corsair_Corsair_K95_RGB_Gaming_Keyboard_1804301EAEBE08015632C7E8F5001941-event-kbd

with

/dev/input/by-id/ckb-Corsair_K95_RGB_Gaming_Keyboard_vKB_-event

and then my VM starts working again

I also have configured the following in

/etc/libvirt/qemu.conf

cgroup_device_acl = [
"/dev/input/by-id/usb-ROCCAT_ROCCAT_Kone_XTD-event-mouse",
"/dev/input/by-id/usb-ROCCAT_ROCCAT_Kone_XTD-if01-event-kbd",
"/dev/input/by-id/usb-ROCCAT_ROCCAT_Kone_XTD-mouse",
"/dev/input/by-id/ckb-Corsair_K95_RGB_Gaming_Keyboard_vM_-event",
"/dev/input/by-id/ckb-Corsair_K95_RGB_Gaming_Keyboard_vKB_-event",
"/dev/input/by-id/usb-Corsair_Corsair_K95_RGB_Gaming_Keyboard_1804301EAEBE08015632C7E8F5001941-event-if00",
"/dev/input/by-id/usb-Corsair_Corsair_K95_RGB_Gaming_Keyboard_1804301EAEBE08015632C7E8F5001941-event-kbd",
"/dev/null", "/dev/full", "/dev/zero",
"/dev/random", "/dev/urandom",
"/dev/ptmx", "/dev/kvm"
]

(I just passed everything that could possible do something in my qemu)
(I use the left and right ctrl keys for switching from my host to guest and back)

So I think there is somewhere a problem (I don't know the source) that swaps the loaded keyboard after login or something like that

Also ckb-next detects two devices, but it's both my "K95 RGB" (there are really two tabs with the same name)

---

Further Info

5.4.93-2-lts
Plasma 5.20.5
ckb-next 0.4.3 (not ckb-next-git, I try to avoid "-git" packages)

---

Also found this post: https://bbs.archlinux.org/viewtopic.php?id=261386