This bug was fixed in the package linux - 4.10.0-37.41
---------------
linux (4.10.0-37.41) zesty; urgency=low
* CVE-2017-1000255
- SAUCE: powerpc/64s: Use emergency stack for kernel TM Bad Thing program
checks
- SAUCE: powerpc/tm: Fix illegal TM state in signal handler
linux (4.10.0-36.40) zesty; urgency=low
* linux: 4.10.0-36.40 -proposed tracker (LP: #1718143)
* Neighbour confirmation broken, breaks ARP cache aging (LP: #1715812)
- sock: add sk_dst_pending_confirm flag
- net: add dst_pending_confirm flag to skbuff
- sctp: add dst_pending_confirm flag
- tcp: replace dst_confirm with sk_dst_confirm
- net: add confirm_neigh method to dst_ops
- net: use dst_confirm_neigh for UDP, RAW, ICMP, L2TP
- net: pending_confirm is not used anymore
* SRIOV: warning if unload VFs (LP: #1715073)
- PCI: Lock each enable/disable num_vfs operation in sysfs
- PCI: Disable VF decoding before pcibios_sriov_disable() updates resources
* Kernel has troule recognizing Corsair Strafe RGB keyboard (LP: #1678477)
- usb: quirks: add delay init quirk for Corsair Strafe RGB keyboard
* CVE-2017-14106
- tcp: initialize rcv_mss to TCP_MIN_MSS instead of 0
* [CIFS] Fix maximum SMB2 header size (LP: #1713884)
- CIFS: Fix maximum SMB2 header size
* Middle button of trackpoint doesn't work (LP: #1715271)
- Input: trackpoint - assume 3 buttons when buttons detection fails
* Drop GPL from of_node_to_nid() export to match other arches (LP: #1709179)
- powerpc: Drop GPL from of_node_to_nid() export to match other arches
* vhost guest network randomly drops under stress (kvm) (LP: #1711251)
- Revert "vhost: cache used event for better performance"
* arm64 arch_timer fixes (LP: #1713821)
- Revert "UBUNTU: SAUCE: arm64: arch_timer: Enable CNTVCT_EL0 trap if
workaround is enabled"
- arm64: arch_timer: Enable CNTVCT_EL0 trap if workaround is enabled
- clocksource/arm_arch_timer: Fix arch_timer_mem_find_best_frame()
- clocksource/drivers/arm_arch_timer: Fix read and iounmap of incorrect
variable
- clocksource/drivers/arm_arch_timer: Fix mem frame loop initialization
- clocksource/drivers/arm_arch_timer: Avoid infinite recursion when ftrace
is
enabled
* Touchpad not detected (LP: #1708852)
- Input: elan_i2c - add ELAN0608 to the ACPI table
-- Thadeu Lima de Souza Cascardo <casca...@canonical.com> Fri, 06 Oct
2017 16:45:48 -0300
--
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 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:0x20000448
ckb-next recommended 0x20000408, 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:
USER PID 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.
lo no 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:0x20000448
RelatedPackageVersions:
linux-restricted-modules-4.8.0-45-generic N/A
linux-backports-modules-4.8.0-45-generic N/A
linux-firmware 1.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
