Bug 928561
Summary: | Gaming USB Keyboard Genius GX Imperator - multimedia keys not working | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Honza Brázdil <jbrazdil> | ||||||||||||
Component: | kernel | Assignee: | Benjamin Tissoires <btissoir> | ||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||
Priority: | unspecified | ||||||||||||||
Version: | 19 | CC: | btissoir, gansalmon, itamar, jbrazdil, jonathan, kernel-maint, madhu.chinakonda | ||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | x86_64 | ||||||||||||||
OS: | Linux | ||||||||||||||
Whiteboard: | |||||||||||||||
Fixed In Version: | kernel-3.10.13-101.fc18 | Doc Type: | Bug Fix | ||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2013-10-01 01:58:05 UTC | Type: | Bug | ||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||
Documentation: | --- | CRM: | |||||||||||||
Verified Versions: | Category: | --- | |||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
Embargoed: | |||||||||||||||
Attachments: |
|
Description
Honza Brázdil
2013-03-27 23:08:34 UTC
Fedora 19 - still not working. Is there anything I can do to make it working? $ uname -a Linux janinko-privat 3.9.9-301.fc19.x86_64 #1 SMP Thu Jul 4 15:10:36 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux I just solved the same problem on bug #959721. However, I need a way for you to dump the full report descriptors. Once I have them, I will be able to write the same fix for your device. As hid-generic is failing, I need you to follow these steps: 1. Locate the device in USB/HID go to /sys/bus/usb/drivers/usbhid use the Sysfs lines from /proc/bus/input/devices to identify which file names of the form 2-1:1.0 correspond to your device (the folders containing 0003:0458:4018.XXXX). 2. Release the device from USB/HID for every of these, do echo 2-1:1.0 > unbind. Of course, 2-1:1.0 is just an example. Be careful not to include any trailing / in the file name. check that your device has disappeared from the directory 3. Retrieve the description of the device type lsusb -v > /tmp/descriptors.txt 4. unplug/replug the keyboard to make it work again If you can get the reports (i.e. no "Report Descriptors: ** UNAVAILABLE **") in the output of lsusb -v, I should be able to do the proper patch. Created attachment 772456 [details]
relevant output of # lsusb -v
I believe this is the relevant part of the lsusb -v output.
(In reply to Honza Brázdil from comment #3) > I believe this is the relevant part of the lsusb -v output. Nearly :) I have got the two report descriptors from the working interfaces, but I am missing the reports from the second interface: wDescriptorLength 131 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: There should be one device in usbhid still attached. Created attachment 772571 [details]
output of # lsusb -v
Sorry, the second interface didn't show up in /proc/bus/input/devices so i missed it.
Thanks for the new lsusb. I made a patch [1] for you to test. After cloning, just run "make ; sudo make install". Then unplug / replug the keyboard. The kye module should handle the device and you should see in your dmesg something like: [ 8474.687051] kye 0003:0458:4018.0022: fixing up Genius Gx Imperator Keyboard report descriptor [ 8474.687568] input: KYE Systems Corp. (Mouse Systems) Imperator as /devices/virtual/misc/uhid/input47 [ 8474.688106] kye 0003:0458:4018.0022: input,hidraw5: USB HID v0.00 Mouse [KYE Systems Corp. (Mouse Systems) Imperator] on If so, I'd like you to record some traces of the 3 hidraw devices attached to your keyboard thanks to hid-recorder [2]. I need them in case we made a deep change in the hid subsystem, so that we can replay the events and check if everything is fine. Thanks! [1] https://github.com/bentiss/hid-kye [2] http://bentiss.github.io/hid-replay-docs/ Created attachment 772605 [details]
hid-recorder /dev/hidraw2
Created attachment 772606 [details]
hid-recorder /dev/hidraw3
Created attachment 772607 [details]
hid-recorder /dev/hidraw4
Thanks, the multimedia keys are now working. But xev didn't captured anything when I pressed macro keys (but they aren't so important). The hidraw2 reacted to macro preset keys, macro keys and right-click-key (next to right ctrl). The hidraw3 reacted to multimedia keys and macro preset keys. The hidraw4 reacted to macro preset keys and normal keyboard keys. Thanks for the feedback. I took some time to investigate the non-working macros, and I believe they are not working because they are not set by the Windows driver :) In the hidraw3 file you sent, they just send a null pointer motion event, in addition to a vendor specific event. In the hidraw2 file, macros are sending out of range events that are not documented in the spec. So having the macro keys working will be more effort. Anyway, I'll still send my current patch upstream so that we can include it in Fedora. Link to the upstream commit: http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.12/upstream&id=0adb9c2c5ed42f199cb2a630c37d18dee385fae2 It will land in v3.12. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. This bug has been fixed in upstream commit 0adb9c2c5ed42f199cb2a630c37d18dee385fae2 It will land in a 3.12 kernel (it is already in 3.12-rc1), so 3.11 does not ship it. We'll look at backporting that. Added this to F18-F20. kernel-3.11.2-201.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/kernel-3.11.2-201.fc19 kernel-3.10.13-101.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/kernel-3.10.13-101.fc18 Package kernel-3.11.2-201.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.11.2-201.fc19' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-17865/kernel-3.11.2-201.fc19 then log in and leave karma (feedback). kernel-3.11.2-301.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/kernel-3.11.2-301.fc20 kernel-3.11.2-201.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. kernel-3.11.2-301.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. kernel-3.10.13-101.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |