CoolerMaster Quick Fire TK NOT detected when directly plugged in.

Commander · 2013-10-06 13:16:09

Hardware
Keyboard : http://www.cmstorm.com/en/products/keyb … ickfiretk/
lspci : https://gist.github.com/CommanderAlchemy/6853973
lsusb: https://gist.github.com/CommanderAlchemy/6853979 (Bus 004 Device 101: ID 2516:0014 is the keyboard)

Issue
I have an issue where if the keyboard is connected directly to my PC by USB it wont get detected all the time. Sometimes it will detect it for 10+ boots and then it will suddenly stop and wont detect it at all on any of my 16 USB ports for unknown time.

Only life i get is

[  928.475672] usb 8-2: new full-speed USB device number 14 using ohci-pci
[  946.116238] usb 8-2: new full-speed USB device number 44 using ohci-pci

Then few minutes later it got detected when not even touching the keyboard or computer. (not always)
I tried connecting it to my laptop and it works each and every time. Detects it instantly.

Then I tried to connect CoolerMaster keyboard to my previous Logitech G15 keyboard by using it's ports and it worked flawlessly each time. Now instead of having 2 keyboards on my desktop I have a Intel USB HUB and it detects the keyboard.

[  982.717841] usb 4-1.1: new full-speed USB device number 101 using ehci-pci
[  982.805007] input: CM Storm Quickfire TKL Nkeys as /devices/pci0000:00/0000:00:13.2/usb4/4-1/4-1.1/4-1.1:1.0/input/input18
[  982.805421] hid-generic 0003:2516:0014.000C: input,hidraw2: USB HID v1.10 Keyboard [CM Storm Quickfire TKL Nkeys] on usb-0000:00:13.2-1.1/input0
[  987.821264] input: CM Storm Quickfire TKL Nkeys as /devices/pci0000:00/0000:00:13.2/usb4/4-1/4-1.1/4-1.1:1.1/input/input19
[  987.821656] hid-generic 0003:2516:0014.000D: input,hidraw3: USB HID v1.10 Keyboard [CM Storm Quickfire TKL Nkeys] on usb-0000:00:13.2-1.1/input1

Looking at it I noticed just recently, ohci-pci when directly and ehci-pci when through a hub. Not sure what it used when it worked directly.
But any ideas why this happens?

Best Regards
Commander (Justice #archlinux)

Last edited by Commander (2013-10-06 13:23:19)

andy123 · 2013-10-06 14:02:55

So it seems to work with ehci but not ohci? Can you check if ehci is used when the keyboard is directly connected to your pc and works?

It might be possible to force ehci with udev, but you cloud also try to turn of "legacy usb" in your bios/uefi if that's possible. If you have the option, you probably want to go with "legacy usb=uefi only", to be able to use the keyboard before linux starts.

Commander · 2013-10-06 16:13:43

andy123 wrote:

So it seems to work with ehci but not ohci? Can you check if ehci is used when the keyboard is directly connected to your pc and works?
It might be possible to force ehci with udev, but you cloud also try to turn of "legacy usb" in your bios/uefi if that's possible. If you have the option, you probably want to go with "legacy usb=uefi only", to be able to use the keyboard before linux starts.

Will try to find this out when I finally manage to actually get it work directly if it uses ohci or ehci.

About the legacy, I think i have that to both (Auto) IE it detects if needs legacy or not. So the keyboard works in UEFI (BIOS) and also on desktop Linux.

Is there a way to force echi over ohci other than udev? and If so how can I find the correct path to the device? Tried somehow to find using /sys/class but inputs does not change if i disconnect/reconnect and /dev/.../usb.... does not help me much more.

Last edited by Commander (2013-10-06 17:03:36)

Commander · 2013-10-24 09:07:25

This is not solved but I mostly used to having a hub.
But i noticed that using different modes the keyboard behaves differently (obviously) however none of them behave the correct way.

kbd_mode -a (XLATE)
TTY switching works with ALT + F capslock/numlock LED's work partially*. And scrollock LED wont work.
* (Toggling numlock when capslock is enabled will turn of the LED for some reason)
And some keys are not mapped correctly (del arrows etc)

kbd_mode -u (Unicecode)
Same as above.

kbd_mode -s (RAW)
TTY switching does not work. capslock/scrolllock LED's wont work and wrong keyboard layout for del arrows etc.

kbd_mode -k (MediumRaw)
same as above

By default running showkey --scancodes in graphical mode returns
kb mode was ?UNKNOWN?
With this the layout where other modes fail is correct But switching TTY's wont work and LED's for capslock and scrollock wont work.
Any ideas how to proceed here?

Last edited by Commander (2013-10-24 09:38:59)

Commander · 2013-11-16 13:32:43

Still haven't found anything on how to solve this.

eldios · 2015-09-15 16:48:56

@Commander did you find any way to fix this behavior in the end?

I just bought a new TK and I also have the same NumLock issue + I saw that it's seen as a CM Storm TKL (6keys) instead of TK.

ideas?

WorMzy · 2015-09-17 10:12:11

Please open a new thread about your problem, and link back to this one if it is still relevant.

https://wiki.archlinux.org/index.php/Fo … bumping.22

Closing.

Arch Linux

#1 2013-10-06 13:16:09

CoolerMaster Quick Fire TK NOT detected when directly plugged in.

#2 2013-10-06 14:02:55

Re: CoolerMaster Quick Fire TK NOT detected when directly plugged in.

#3 2013-10-06 16:13:43

Re: CoolerMaster Quick Fire TK NOT detected when directly plugged in.

#4 2013-10-24 09:07:25

Re: CoolerMaster Quick Fire TK NOT detected when directly plugged in.

#5 2013-11-16 13:32:43

Re: CoolerMaster Quick Fire TK NOT detected when directly plugged in.

#6 2015-09-15 16:48:56

Re: CoolerMaster Quick Fire TK NOT detected when directly plugged in.

#7 2015-09-17 10:12:11

Re: CoolerMaster Quick Fire TK NOT detected when directly plugged in.

Board footer