[Kernel-packages] [Bug 1718703] Re: Kernel support for Corsair Strafe monochrome keyboard
dmesg1, dmesg2, which are the same as LP: #1678477: [7.388222] usb 3-14: can't read configurations, error -110 dmesg3: [ 40.156098] usbhid 3-14:1.1: can't add hid device: -110 [ 40.156314] usbhid: probe of 3-14:1.1 failed with error -110 So the original issue is solved, but now you hit another 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/1718703 Title: Kernel support for Corsair Strafe monochrome keyboard Status in linux package in Ubuntu: Confirmed Bug description: Related to bug: https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1678477 Support for Corsair Strafe RGB was added, but the Corsair Strafe monochrome keyboard has a different device ID and isn't covered by the RGB fix. Quote from other user: "I'm using a slightly different variant of this keyboard - Corsair Strafe (without RGB; product ID is 1b15). I had more or less the same problem (error -110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems to work every time. I did a quick test - previously keyboard worked 5 out of 10 reboots, and after applying this change it worked 10 out of 10 reboots (I also get this new message during boot, like others did before - "couldn't find an input interrupt endpoint"). As this keyboard has a different product ID (but the same vendor ID), it will probably require additional entry in the drivers/usb/core/quirks.c Please let me know if you need any additional info or tests from me." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718703/+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 1718703] Re: Kernel support for Corsair Strafe monochrome keyboard
Didn't work. I have 4 dmesg logs. dmesg1-13-delayed is running the regular debian kernel 13, and the keyboard responded normally after a brief (~2 second) delay. dmesg4-13-delayed is the same. dmesg2-13-bad is running the regular debian kernel 13, but this time the keyboard did not respond until I unplugged and plugged it back in. dmesg3-14-bad is running the kernel you provided. Keyboard didn't respond until it was unplugged and plugged back in. ** Attachment added: "dmesgs.tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718703/+attachment/4971153/+files/dmesgs.tar.gz -- 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/1718703 Title: Kernel support for Corsair Strafe monochrome keyboard Status in linux package in Ubuntu: Confirmed Bug description: Related to bug: https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1678477 Support for Corsair Strafe RGB was added, but the Corsair Strafe monochrome keyboard has a different device ID and isn't covered by the RGB fix. Quote from other user: "I'm using a slightly different variant of this keyboard - Corsair Strafe (without RGB; product ID is 1b15). I had more or less the same problem (error -110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems to work every time. I did a quick test - previously keyboard worked 5 out of 10 reboots, and after applying this change it worked 10 out of 10 reboots (I also get this new message during boot, like others did before - "couldn't find an input interrupt endpoint"). As this keyboard has a different product ID (but the same vendor ID), it will probably require additional entry in the drivers/usb/core/quirks.c Please let me know if you need any additional info or tests from me." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718703/+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 1718703] Re: Kernel support for Corsair Strafe monochrome keyboard
Try this: http://people.canonical.com/~khfeng/lp1718703-3/ It contains threes quirks: USB_QUIRK_DELAY_INIT, USB_QUIRK_NO_LPM, USB_QUIRK_DEVICE_QUALIFIER. -- 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/1718703 Title: Kernel support for Corsair Strafe monochrome keyboard Status in linux package in Ubuntu: Confirmed Bug description: Related to bug: https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1678477 Support for Corsair Strafe RGB was added, but the Corsair Strafe monochrome keyboard has a different device ID and isn't covered by the RGB fix. Quote from other user: "I'm using a slightly different variant of this keyboard - Corsair Strafe (without RGB; product ID is 1b15). I had more or less the same problem (error -110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems to work every time. I did a quick test - previously keyboard worked 5 out of 10 reboots, and after applying this change it worked 10 out of 10 reboots (I also get this new message during boot, like others did before - "couldn't find an input interrupt endpoint"). As this keyboard has a different product ID (but the same vendor ID), it will probably require additional entry in the drivers/usb/core/quirks.c Please let me know if you need any additional info or tests from me." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718703/+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 1718703] Re: Kernel support for Corsair Strafe monochrome keyboard
Also, it's quite hard to fully understand the problem without full dmesg. -- 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/1718703 Title: Kernel support for Corsair Strafe monochrome keyboard Status in linux package in Ubuntu: Confirmed Bug description: Related to bug: https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1678477 Support for Corsair Strafe RGB was added, but the Corsair Strafe monochrome keyboard has a different device ID and isn't covered by the RGB fix. Quote from other user: "I'm using a slightly different variant of this keyboard - Corsair Strafe (without RGB; product ID is 1b15). I had more or less the same problem (error -110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems to work every time. I did a quick test - previously keyboard worked 5 out of 10 reboots, and after applying this change it worked 10 out of 10 reboots (I also get this new message during boot, like others did before - "couldn't find an input interrupt endpoint"). As this keyboard has a different product ID (but the same vendor ID), it will probably require additional entry in the drivers/usb/core/quirks.c Please let me know if you need any additional info or tests from me." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718703/+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 1718703] Re: Kernel support for Corsair Strafe monochrome keyboard
Then I guess it's a better idea to try different approach. ** Changed in: linux (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- 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/1718703 Title: Kernel support for Corsair Strafe monochrome keyboard Status in linux package in Ubuntu: Confirmed Bug description: Related to bug: https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1678477 Support for Corsair Strafe RGB was added, but the Corsair Strafe monochrome keyboard has a different device ID and isn't covered by the RGB fix. Quote from other user: "I'm using a slightly different variant of this keyboard - Corsair Strafe (without RGB; product ID is 1b15). I had more or less the same problem (error -110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems to work every time. I did a quick test - previously keyboard worked 5 out of 10 reboots, and after applying this change it worked 10 out of 10 reboots (I also get this new message during boot, like others did before - "couldn't find an input interrupt endpoint"). As this keyboard has a different product ID (but the same vendor ID), it will probably require additional entry in the drivers/usb/core/quirks.c Please let me know if you need any additional info or tests from me." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718703/+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 1718703] Re: Kernel support for Corsair Strafe monochrome keyboard
I tried the new kernel with 4 reboots. On the first reboot, the problem was not there and everything was good. On reboots 2-4, the problem returned, and I had to unplug the keyboard at the login screen to get it to work. Sorry I don't have the full logs, but I suspect we'll need to try a different approach. Full disclosure - I'm running Debian, but I was still able to install the kernels. -- 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/1718703 Title: Kernel support for Corsair Strafe monochrome keyboard Status in linux package in Ubuntu: Confirmed Bug description: Related to bug: https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1678477 Support for Corsair Strafe RGB was added, but the Corsair Strafe monochrome keyboard has a different device ID and isn't covered by the RGB fix. Quote from other user: "I'm using a slightly different variant of this keyboard - Corsair Strafe (without RGB; product ID is 1b15). I had more or less the same problem (error -110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems to work every time. I did a quick test - previously keyboard worked 5 out of 10 reboots, and after applying this change it worked 10 out of 10 reboots (I also get this new message during boot, like others did before - "couldn't find an input interrupt endpoint"). As this keyboard has a different product ID (but the same vendor ID), it will probably require additional entry in the drivers/usb/core/quirks.c Please let me know if you need any additional info or tests from me." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718703/+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 1718703] Re: Kernel support for Corsair Strafe monochrome keyboard
Please try kernel in [1], it increased delay time. [1] http://people.canonical.com/~khfeng/lp1718703-2/ -- 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/1718703 Title: Kernel support for Corsair Strafe monochrome keyboard Status in linux package in Ubuntu: Confirmed Bug description: Related to bug: https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1678477 Support for Corsair Strafe RGB was added, but the Corsair Strafe monochrome keyboard has a different device ID and isn't covered by the RGB fix. Quote from other user: "I'm using a slightly different variant of this keyboard - Corsair Strafe (without RGB; product ID is 1b15). I had more or less the same problem (error -110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems to work every time. I did a quick test - previously keyboard worked 5 out of 10 reboots, and after applying this change it worked 10 out of 10 reboots (I also get this new message during boot, like others did before - "couldn't find an input interrupt endpoint"). As this keyboard has a different product ID (but the same vendor ID), it will probably require additional entry in the drivers/usb/core/quirks.c Please let me know if you need any additional info or tests from me." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718703/+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 1718703] Re: Kernel support for Corsair Strafe monochrome keyboard
Can you attach full dmesg? -- 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/1718703 Title: Kernel support for Corsair Strafe monochrome keyboard Status in linux package in Ubuntu: Confirmed Bug description: Related to bug: https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1678477 Support for Corsair Strafe RGB was added, but the Corsair Strafe monochrome keyboard has a different device ID and isn't covered by the RGB fix. Quote from other user: "I'm using a slightly different variant of this keyboard - Corsair Strafe (without RGB; product ID is 1b15). I had more or less the same problem (error -110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems to work every time. I did a quick test - previously keyboard worked 5 out of 10 reboots, and after applying this change it worked 10 out of 10 reboots (I also get this new message during boot, like others did before - "couldn't find an input interrupt endpoint"). As this keyboard has a different product ID (but the same vendor ID), it will probably require additional entry in the drivers/usb/core/quirks.c Please let me know if you need any additional info or tests from me." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718703/+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 1718703] Re: Kernel support for Corsair Strafe monochrome keyboard
Still getting error -110. kernel: [ 13.788028] usb 3-14: string descriptor 0 read error: -110 kernel: [ 13.788031] usb 3-14: New USB device found, idVendor=1b1c, idProduct=1b15 kernel: [ 13.788032] usb 3-14: New USB device strings: Mfr=1, Product=2, SerialNumber=3 -- 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/1718703 Title: Kernel support for Corsair Strafe monochrome keyboard Status in linux package in Ubuntu: Confirmed Bug description: Related to bug: https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1678477 Support for Corsair Strafe RGB was added, but the Corsair Strafe monochrome keyboard has a different device ID and isn't covered by the RGB fix. Quote from other user: "I'm using a slightly different variant of this keyboard - Corsair Strafe (without RGB; product ID is 1b15). I had more or less the same problem (error -110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems to work every time. I did a quick test - previously keyboard worked 5 out of 10 reboots, and after applying this change it worked 10 out of 10 reboots (I also get this new message during boot, like others did before - "couldn't find an input interrupt endpoint"). As this keyboard has a different product ID (but the same vendor ID), it will probably require additional entry in the drivers/usb/core/quirks.c Please let me know if you need any additional info or tests from me." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718703/+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 1718703] Re: Kernel support for Corsair Strafe monochrome keyboard
Please try kernel here: http://people.canonical.com/~khfeng/lp1718703/ -- 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/1718703 Title: Kernel support for Corsair Strafe monochrome keyboard Status in linux package in Ubuntu: Confirmed Bug description: Related to bug: https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1678477 Support for Corsair Strafe RGB was added, but the Corsair Strafe monochrome keyboard has a different device ID and isn't covered by the RGB fix. Quote from other user: "I'm using a slightly different variant of this keyboard - Corsair Strafe (without RGB; product ID is 1b15). I had more or less the same problem (error -110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems to work every time. I did a quick test - previously keyboard worked 5 out of 10 reboots, and after applying this change it worked 10 out of 10 reboots (I also get this new message during boot, like others did before - "couldn't find an input interrupt endpoint"). As this keyboard has a different product ID (but the same vendor ID), it will probably require additional entry in the drivers/usb/core/quirks.c Please let me know if you need any additional info or tests from me." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718703/+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 1718703] Re: Kernel support for Corsair Strafe monochrome keyboard
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1718703 Title: Kernel support for Corsair Strafe monochrome keyboard Status in linux package in Ubuntu: Confirmed Bug description: Related to bug: https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1678477 Support for Corsair Strafe RGB was added, but the Corsair Strafe monochrome keyboard has a different device ID and isn't covered by the RGB fix. Quote from other user: "I'm using a slightly different variant of this keyboard - Corsair Strafe (without RGB; product ID is 1b15). I had more or less the same problem (error -110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems to work every time. I did a quick test - previously keyboard worked 5 out of 10 reboots, and after applying this change it worked 10 out of 10 reboots (I also get this new message during boot, like others did before - "couldn't find an input interrupt endpoint"). As this keyboard has a different product ID (but the same vendor ID), it will probably require additional entry in the drivers/usb/core/quirks.c Please let me know if you need any additional info or tests from me." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718703/+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 1718703] Re: Kernel support for Corsair Strafe monochrome keyboard
Confirmed by Piotr Sowiński (psow86) ** 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/1718703 Title: Kernel support for Corsair Strafe monochrome keyboard Status in linux package in Ubuntu: Confirmed Bug description: Related to bug: https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1678477 Support for Corsair Strafe RGB was added, but the Corsair Strafe monochrome keyboard has a different device ID and isn't covered by the RGB fix. Quote from other user: "I'm using a slightly different variant of this keyboard - Corsair Strafe (without RGB; product ID is 1b15). I had more or less the same problem (error -110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems to work every time. I did a quick test - previously keyboard worked 5 out of 10 reboots, and after applying this change it worked 10 out of 10 reboots (I also get this new message during boot, like others did before - "couldn't find an input interrupt endpoint"). As this keyboard has a different product ID (but the same vendor ID), it will probably require additional entry in the drivers/usb/core/quirks.c Please let me know if you need any additional info or tests from me." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718703/+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
