> Did you already find someone with a US keyboard? Yes as mentioned in thread it does not seem possible to write a hwdb-rule that works for both US and non-US keyboard. Also it is a general problem that affects other keyboards than Corsair, again see previous mails in this thread. David, it would be great if you could get your patch ready so this one could be closed. If you don't have the time to do it, perhaps my original patch could be considered again. I fully aggree that it is a hack but it does solve the problem with little risk of bad side effects. It can always be removed later we you have a proper fix. Regards, Fredrik On Fri, Dec 19, 2014 at 5:28 PM, RH <r@xxxxxxxxx> wrote: > Hello, > > I experience the same issue with my new keyboard: > *Corsair Raptor K30 (German version)* > > The issue can be fixed/worked around with this rule in hwdb: > > --------------- > #keyboard:name:*Corsair*:dmi:bvn*:bvr*:bd*:svn*:pn*:pvr* > keyboard:usb:v1B1Cp1B0A* > KEYBOARD_KEY_70031=reserved > --------------- > > So you think the US version won't work with this anymore? I guess they > will send both scancodes, too. > > This is the output of lsusb: > --------------- > Bus 004 Device 008: ID 1b1c:1b0a Corsair > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 64 > idVendor 0x1b1c Corsair > idProduct 0x1b0a > bcdDevice 1.03 > iManufacturer 1 Corsair > iProduct 2 Corsair K30A Gaming Keyboard > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 84 > bNumInterfaces 3 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xa0 > (Bus Powered) > Remote Wakeup > MaxPower 500mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 1 Boot Interface Subclass > bInterfaceProtocol 1 Keyboard > iInterface 0 > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.11 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 65 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 1 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 0 No Subclass > bInterfaceProtocol 0 None > iInterface 0 > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.11 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 25 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 EP 2 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0004 1x 4 bytes > bInterval 1 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 2 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 0 No Subclass > bInterfaceProtocol 0 None > iInterface 0 > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.11 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 37 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x000f 1x 15 bytes > bInterval 1 > Device Status: 0x0000 > (Bus Powered) > --------------- > > Did you already find someone with a US keyboard? Shall I write in the > corsair forums or to the support to find out whether US keyboards have > the same product IDs? If this is not the case, we could safely use vendor/ > product IDs for the workaround. > > I'd really like to submit working hwdb lines to the udev database to save > other users from having these troubles. > > Also, do you know why > > Greetings, > RH > > -- > To unsubscribe from this list: send the line "unsubscribe linux-input" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
