I am not 100% sure I can blame VIAL FW for this.
I have an old HyperX Cloud 2 headset with a USB sound card.
If I connect this card to my Arch Linux system with Plasma, the keyboard switches its LED state for Num lock to off, despite Num lock being enabled on the system even after connect.
I suppose this is because the headset pretends to be a keyboard too(?), but I am not sure why the keyboard is picking up on this false state.
The RED LED gets turned on here since the state will be seen as off:
bool rgb_matrix_indicators_kb(void) {
if (!rgb_matrix_indicators_user()) {
return false;
}
if (host_keyboard_led_state().num_lock) {
rgb_matrix_set_color(49, 0, 40, 0); // ON = GREEN
} else {
rgb_matrix_set_color(63, 40, 0, 0); // OFF = RED
rgb_matrix_set_color(49, 40, 40, 0); // OFF = YELLOW
}
dmesg for USB soundcard connection:
[279491.560823] usb 1-2.1: new full-speed USB device number 19 using xhci_hcd
[279492.051739] usb 1-2.1: New USB device found, idVendor=0951, idProduct=16a4, bcdDevice= 0.10
[279492.051745] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[279492.051748] usb 1-2.1: Product: HyperX Virtual Surround Sound
[279492.051750] usb 1-2.1: Manufacturer: Kingston
[279492.051752] usb 1-2.1: SerialNumber: 00000000
[279492.541003] input: Kingston HyperX Virtual Surround Sound Consumer Control as /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:08.0/0000:0a:00.0/0000:0b:0c.0/0000:11:00.0/usb1/1-2/1-2.1/1-2.1:1.3/0003:0951:16A4.0047/input/input77
[279492.592917] input: Kingston HyperX Virtual Surround Sound as /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:08.0/0000:0a:00.0/0000:0b:0c.0/0000:11:00.0/usb1/1-2/1-2.1/1-2.1:1.3/0003:0951:16A4.0047/input/input78
[279492.603999] hid-generic 0003:0951:16A4.0047: input,hiddev101,hidraw9: USB HID v1.11 Device [Kingston HyperX Virtual Surround Sound] on usb-0000:11:00.0-2.1/input3
I am not 100% sure I can blame VIAL FW for this.
I have an old HyperX Cloud 2 headset with a USB sound card.
If I connect this card to my Arch Linux system with Plasma, the keyboard switches its LED state for Num lock to off, despite Num lock being enabled on the system even after connect.
I suppose this is because the headset pretends to be a keyboard too(?), but I am not sure why the keyboard is picking up on this false state.
The RED LED gets turned on here since the state will be seen as off:
dmesg for USB soundcard connection: