Click to view our Accessibility Statement or contact us with accessibility-related questions
Showing 1 of 1691 conversations about:
AudioSentinel
59
Aug 31, 2018
bookmark_border
theimmc
872
Aug 31, 2018
bookmark_border
AudioSentinelI plugged mine into a Raspberry Pi and it works just fine. Did you try it with a Windows box to determine if you have a defective keyboard? All of my Linux machines are VMs so I can't test with them.
AudioSentinel
59
Aug 31, 2018
bookmark_border
theimmcWorks on Windows just fine. When plugged in, LED rainbow scheme is running.
When I plug it on Linux (Xubuntu 16.04), LEDs are all lit but static and no keys work. dmesg shows it being plugged in. I can use mdloader to dump the firmware from the keyboard (pressing reset button works as expected).
Oh well, time to troubleshoot and learn more about QMK. I mean, if Massdrop haven't included the note that specifically talks about OSX/Windows, I would think something is wrong with the keyboard. But since they specifically included it... they probably knew it won't work somewhere ;)
It's probably something that only happens with my computer. Just my luck :)
Nevertheless, it's a beautiful keyboard :)
When I plug it on Linux (Xubuntu 16.04), LEDs are all lit but static and no keys work. dmesg shows it being plugged in. I can use mdloader to dump the firmware from the keyboard (pressing reset button works as expected).
Oh well, time to troubleshoot and learn more about QMK. I mean, if Massdrop haven't included the note that specifically talks about OSX/Windows, I would think something is wrong with the keyboard. But since they specifically included it... they probably knew it won't work somewhere ;)
It's probably something that only happens with my computer. Just my luck :)
Nevertheless, it's a beautiful keyboard :)
theimmc
872
Sep 1, 2018
bookmark_border
AudioSentinelReading your edited post, if the keyboard is plugged in when you reboot, it works, but not if you plug it in after it has booted up? And the change to grub fixes that?
Thanks for the info!
Thanks for the info!
AudioSentinel
59
Sep 1, 2018
bookmark_border
theimmcNot exactly.
If I plug it while Xubuntu 16.04 is running, keyboard doesn't work. If I reboot, keyboard just remains in 'stuck' state, for some reason even LEDs don't go off on reboot (while other keyboard that I had connected at the same time went off). Can't get into BIOS or anything else.
But if I (re)plug it as I am rebooting, it will work for BIOS.
If I plug it while Xubuntu 16.04 is running, keyboard doesn't work. If I reboot, keyboard just remains in 'stuck' state, for some reason even LEDs don't go off on reboot (while other keyboard that I had connected at the same time went off). Can't get into BIOS or anything else.
But if I (re)plug it as I am rebooting, it will work for BIOS.
theimmc
872
Sep 1, 2018
bookmark_border
AudioSentinelThat's extremely strange! Glad you had it figured out, and thanks for sharing the info.
FWIW, with the Raspberry Pi, I had no trouble booting up with it plugged in. I need to check if it works when I plug it in after it has booted up.
FWIW, with the Raspberry Pi, I had no trouble booting up with it plugged in. I need to check if it works when I plug it in after it has booted up.
Locke99gs
30
Aug 2, 2020
bookmark_border
AudioSentinelThis is good information, and steered me in the right direction. I wish I'd have known about these flags years ago when I was having issues with my Corsair keyboards :)
To anyone interested, this flags some attributes of the USB HID driver to change the way it behaves.
0x04d8:0xeed2 is the vendor:device ids (The Massdrop CTRL) and 0x20000408 is actually multiple stacked flags which do different things. From hid.h in the kernel source:
#define HID_QUIRK_NOGET 0x00000008
#define HID_QUIRK_ALWAYS_POLL 0x00000400
#define HID_QUIRK_NO_INIT_REPORTS 0x20000000
It does seem that this is most well known problem with Corsair keyboards, and a lot of this information is in regards to such. The flags are generic, however, and not specific to Corsair. The driver simply applies the flags to whatever vendor:device id you tell it to.
The usbhid.quirks addition to GRUB_CMDLINE_LINUX_DEFAULT would be in addition to anything else you might have there. For instance, if you've disabled watchdog or want t keep the boot splash, add this to the end, but staying inside the quotes.
(Edited)
Related Products
Drop Refurbished
Like-new products you can trustDrop Rewards
Get $5 for every 500 points you earn! Learn more
Drop Keyboard Club
Become a member and expand your keycap collectionCollaborate With Us
For Brands & DesignersFollow Drop
Turns out that keyboard works ok when I reboot and go into BIOS (then connect the keyboard - or connect while rebooting), so this is something specific to my Linux setup. It's normal Xubuntu 16.04 and everything else I've ever plugged in into it worked fine, so this is going to be fun (or not, I'll find out soon enough).
Edit 2: In case anyone else experiences the issue, this is most likely the solution.
Turns out that some Corsair keyboards have similar issues. To make the long story short, modifying /etc/default/grub to have a line like this ...
GRUB_CMDLINE_LINUX_DEFAULT="usbhid.quirks=0x04d8:0xeed2:0x20000408"
... fixed it for me.
You need to run update-grub after this change and reboot.
This seems to be a well documented issue, so googling for specific quirk (0x20000408) and some other keywords (depending on keyboard/etc) should provide enough details if anyone needs to troubleshoot more.