[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
Since I no longer run Xenial, I can't directly verify the fix on that distribution, so I'm not changing the tags. However, I'm confident the fix will work there as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash usbhid.quirks=0x1B1C:0x1B20:0x2448 RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97M-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
I am on 17.04 - I've just installed the proposed kernel (4.10.36) and verified that it does indeed solve my problem. My keyboard works through multiple reboots and "re-pluggings" as described above. ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Committed Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash usbhid.quirks=0x1B1C:0x1B20:0x2448 RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97M-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
The "devicequalifier" kernel doesn't appear to work. It presents a similar error either on boot or when hot-plugging the keyboard: [ 37.680914] usb 3-3: new full-speed USB device number 5 using xhci_hcd [ 48.097499] usb 3-3: New USB device found, idVendor=1b1c, idProduct=1b20 [ 48.097505] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 48.097508] usb 3-3: Product: Corsair STRAFE RGB Gaming Keyboard [ 48.097510] usb 3-3: Manufacturer: Corsair [ 51.331414] usb 3-3: can't set config #1, error -71 The error code has changed from -110 to -71, but the behavior seems to be very similar to that of the original bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Confirmed Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash usbhid.quirks=0x1B1C:0x1B20:0x2448 RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
The "delayinit" kernel seems to work! The keyboard is usable when the computer first boots, and every time I unplug and plug it back in. I did that while following the output of dmesg -w and got the following: [ 80.205969] usb 3-3: new full-speed USB device number 5 using xhci_hcd [ 81.468240] usb 3-3: New USB device found, idVendor=1b1c, idProduct=1b20 [ 81.468244] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 81.468246] usb 3-3: Product: Corsair STRAFE RGB Gaming Keyboard [ 81.468247] usb 3-3: Manufacturer: Corsair [ 81.468249] usb 3-3: SerialNumber: 0B03F020AEBD18445619787AF5001946 [ 86.703197] input: Corsair Corsair STRAFE RGB Gaming Keyboard as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/0003:1B1C:1B20.0005/input/input23 [ 86.703780] hid-generic 0003:1B1C:1B20.0005: input,hidraw0: USB HID v1.11 Keyboard [Corsair Corsair STRAFE RGB Gaming Keyboard] on usb-:00:14.0-3/input0 [ 86.705875] input: Corsair Corsair STRAFE RGB Gaming Keyboard as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.1/0003:1B1C:1B20.0006/input/input24 [ 86.706203] input: Corsair Corsair STRAFE RGB Gaming Keyboard as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.1/0003:1B1C:1B20.0006/input/input25 [ 86.706403] input: Corsair Corsair STRAFE RGB Gaming Keyboard as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.1/0003:1B1C:1B20.0006/input/input26 [ 86.706640] input: Corsair Corsair STRAFE RGB Gaming Keyboard as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.1/0003:1B1C:1B20.0006/input/input27 [ 86.706854] hid-generic 0003:1B1C:1B20.0006: input,hiddev0,hidraw1: USB HID v1.11 Keyboard [Corsair Corsair STRAFE RGB Gaming Keyboard] on usb-:00:14.0-3/input1 [ 86.706941] usbhid 3-3:1.2: couldn't find an input interrupt endpoint I haven't tried the devicequalifier kernel yet, will try that now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Confirmed Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no
[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
With the kernels from http://people.canonical.com/~khfeng/lp1678477-nolpm/ , the problem seems to have returned. I got the following error on boot: [1.273005] usb 3-9: new full-speed USB device number 3 using xhci_hcd [ 11.740700] usb 3-9: string descriptor 0 read error: -110 [ 11.740733] usb 3-9: New USB device found, idVendor=1b1c, idProduct=1b20 [ 11.740734] usb 3-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 16.860817] usb 3-9: can't set config #1, error -110 Unplugging and re-plugging the keyboard also gives me similar error messages on dmesg. More often than not it will eventually work on one of the retries, but sometimes it will fail three times in a row and stop. I guess one or more of the other two quirks are necessary too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Confirmed Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash usbhid.quirks=0x1B1C:0x1B20:0x2448 RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
I've also installed the linked kernel today, and verified it works for me as well! The keyboard was detected correctly every time through multiple unpluggings and reboots, with output similar to what Frits pasted above. I too always get the "couldn't find an interrupt endpoint" message, but other than the device seems to work well. I'll keep using this kernel and will report if the problem appears again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Confirmed Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash usbhid.quirks=0x1B1C:0x1B20:0x2448 RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97M-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
I can also confirm that I've never experienced the problem on Windows or on the GRUB menu, both with the keyboard plugged into a single USB 3.0 and into 2 USB 2.0 ports. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Confirmed Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash usbhid.quirks=0x1B1C:0x1B20:0x2448 RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97M-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
I upgraded to Ubuntu 17.04 a couple of weeks ago, and the problem persisted under its version of kernel 4.10. I just installed all the four packages in the link above, and booted into the new Kernel on Ubuntu 17.04. The problem still persists. This is the output of 'dmesg | grep "usb 3-3"' shortly after boot under this kernel, where usb 3-3 is the USB 3.0 port where the keyboard is plugged in: [1.017724] usb 3-3: new full-speed USB device number 2 using xhci_hcd [6.369206] usb 3-3: unable to read config index 0 descriptor/all [6.369238] usb 3-3: can't read configurations, error -110 [6.489148] usb 3-3: new full-speed USB device number 3 using xhci_hcd [ 11.744636] usb 3-3: unable to read config index 0 descriptor/all [ 11.744675] usb 3-3: can't read configurations, error -110 [ 11.864580] usb 3-3: new full-speed USB device number 4 using xhci_hcd [ 17.124668] usb 3-3: unable to read config index 0 descriptor/all [ 17.124705] usb 3-3: can't read configurations, error -110 [ 17.252017] usb 3-3: new full-speed USB device number 5 using xhci_hcd [ 22.495509] usb 3-3: unable to read config index 0 descriptor/all [ 22.495512] usb 3-3: can't read configurations, error -110 [ 39.338187] usb 3-3: new full-speed USB device number 8 using xhci_hcd [ 39.479693] usb 3-3: New USB device found, idVendor=1b1c, idProduct=1b20 [ 39.479695] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 39.479696] usb 3-3: Product: Corsair STRAFE RGB Gaming Keyboard [ 39.479696] usb 3-3: Manufacturer: Corsair [ 39.479697] usb 3-3: SerialNumber: 0B03F020AEBD18445619787AF5001946 The last set of messages is where I unplugged the keyboard and plugged back in. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Confirmed Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine:
[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
For me, whether the keyboard will work or not seems random: sometimes it works right away, sometimes it works after replugging it once, sometimes it takes multiple attempts. The error messages are the same ones you posted. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Confirmed Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash usbhid.quirks=0x1B1C:0x1B20:0x2448 RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97M-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
s/"Complete"/"Confirmed"/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Confirmed Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash usbhid.quirks=0x1B1C:0x1B20:0x2448 RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97M-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
I tested it a few days ago but forgot to mark it as "Complete", sorry about that. To further add information to my previous comment here, the bug I described occurs both when the keyboard is plugged into a USB 3.0 port and when it's plugged into 2 USB 2.0 ports. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Confirmed Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash usbhid.quirks=0x1B1C:0x1B20:0x2448 RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97M-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
Another possibly useful bit of information: I have the keyboard connected to a USB 3.0 port - this model requires either a USB 3.0 port or 2 USB 2.0 ports, because it draws more power than a USB 2.0 port provides. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Incomplete Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash usbhid.quirks=0x1B1C:0x1B20:0x2448 RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97M-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
Tested with 4.11.rc5, and still found this issue. Took me three tries to get the keyboard to work, with the same messages and all the same config options as above. ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Incomplete Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash usbhid.quirks=0x1B1C:0x1B20:0x2448 RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97M-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1678477] [NEW] Kernel has troule recognizing Corsair Strafe RGB keyboard
Public bug reported: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint >From what I have been able to determine, the Corsair Strafe RGB has three >inputs, with the last one being used as input/output and having something to >do with the LEDs. It only has a single USB configuration, though I don't know >why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash usbhid.quirks=0x1B1C:0x1B20:0x2448 RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97M-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: New Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being
