Keyboard (Corsair K50) works at BIOS but doesn't when ubuntu boots

Asked by Jared

Keyboard is a Corsair K50, have owned it for the last six months and it has worked really well.

Last night it stopped working on boot, interestingly during the BIOS boot up I can press DEL, F12 or ESC and get into the various setups and loaders but as soon as ubuntu loads the keyboard stops working. Even when I go through to Advanced Options and try running safe mode, the keyboard works until it then offers options of "continuing boot" or "managing packages".

The keyboard is flashing it's num/scroll/caps lock keys which according to a little dig around of the web suggests that the keyboard is in "BIOS mode", I've tried a few suggestions on the forums in terms of key combinations but I have a feeling this is a ubuntu driver issue.

I've also plugged the keyboard into a Windows machine, although the flashing lights persist the keyboard does type and work.

Any assistance to get this working again would be appreciated as it's a really nice (and expensive) keyboard.

Question information

Language:
English Edit question
Status:
Open
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Enable USB legacy mode in BIOS if possible. Have you tried the keyboard in different ports (not USB 3 for example)

Revision history for this message
Jared (subzerokangaroo) said :
#2

Rebooted into the BIOS, USB Legacy mode was already enabled.

Tried all the USB ports on the machine; lights are still flashing and the device doesn't type.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

Plug in the old keyboard and run:

xev

In a terminal. Does the new keyboard make events?

Is there a switch on the new keyboard to enable or disable it?

Revision history for this message
Jared (subzerokangaroo) said :
#4

Ran xev, no response from the keyboard, tried all the keys.

There's no way of turning the keyboard on and off apart from unplugging it.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#5

http://forum.corsair.com/v3/showthread.php?t=133929

May help to contact the developer

Revision history for this message
Jared (subzerokangaroo) said :
#6

I downloaded the driver and installed it, but it says that there is no device detected (possibly because it's an older model) which seems to fit in the flow of the device not being picked up when the OS is booted.

I've raised the issue here: https://github.com/ccMSC/ckb/issues/82

There's two other straws I'm clutching at that I'm sure if they are relevant.

1. The talk of drivers made me look in the settings dialog, under additional drivers I found:

Unknown Device
 [ ] Using processor microcode firmware for Intel CPUs from intel microcode (proprietary)
 [X] Do not use device

I changed it to the former and clicked Apply Changes, still not working so probably not relevant.

2. Secondly whilst rebooting I've noticed the brief message: "Booting in insecure mode" before the ubuntu logo. Is that an issue?

Revision history for this message
Jared (subzerokangaroo) said :
#7

I did a bit more debugging and digging to provide information I spotted a message about a device not being found during a recovery mode boot, I think I've traced it.

I ran "dmesg" and found the following lines:

[ 2.360931] usbhid 1-9:1.0: can't add hid device: -22
[ 2.360936] usbhid: probe of 1-9:1.0 failed with error -22
[ 2.368902] usbcore: registered new interface driver usbhid
[ 2.368904] usbhid: USB HID core driver

I also ran "lsusb" to get an idea of what is current plugged into the PC:
Bus 006 Device 002: ID 8087:8001 Intel Corp.
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 004: ID 05e3:0743 Genesys Logic, Inc.
Bus 004 Device 003: ID 2109:0812
Bus 004 Device 002: ID 0bc2:3312 Seagate RSS LLC
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 2109:2812
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 8087:8009 Intel Corp.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1b1c:1b04 Corsair
Bus 001 Device 004: ID 0603:00f2 Novatek Microelectronics Corp.
Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 006: ID 148f:5372 Ralink Technology, Corp. RT5372 Wireless Adapter
Bus 001 Device 005: ID 093a:2521 Pixart Imaging, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Curiously it's registered there as "Bus 001 Device 003: ID 1b1c:1b04 Corsair" but not recognising input.

Revision history for this message
Jared (subzerokangaroo) said :
#8

I looked up the error from usbhid and found this issue:
http://stackoverflow.com/questions/7199827/linux-usb-device-driver-not-getting-probed

The suggestion is that the systems drivers are overriding [the] driver. Is this worth creating a bug report for?

Can you help with this problem?

Provide an answer of your own, or ask Jared for more information if necessary.

To post a message you must log in.