From: Jonathan Nieder <hidden> Date: 2012-01-26 21:39:40
Hi,
zitev wrote:
Thanks for your respond! I did try to probe again with the latest
sid kernel (Linux version 3.2.0-1-686-pae (Debian 3.2.1-2)
(ben-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org) (gcc version 4.6.2 (Debian 4.6.2-12) ) #1 SMP
Tue Jan 24 06:09:30 UTC 2012), but the problem's very same.
What more can I help you?
Here's some context.
Csaba noticed[1] that his keyboard (a "Gigabyte K8100 Aivia USB Gaming
Keyboard") does not work correctly on Linux. It is claimed by the
usbhid driver and:
all keys absolutely not working, but led's does light.
When I search for information about Linux support for this keyboard
elsewhere, I see that the backspace key and multimedia keys are said
to work but nothing else[2]:
| papibe June 4th, 2011, 09:51 PM
|
| Try to see if xev registers an event while pressing the backspace key:
| $ xev
| Regards.
|
| Peckles June 4th, 2011, 10:07 PM
| Thanks for the command, very useful. Thats going in the memory bank...
|
| The backspace key registers a backspace. Also all of the multimedia
| keys and special 5 mappable keys work as well. (very strange...)
The question becomes: where to go from here? Any idea about how we
can find out what how to drive this device? Does it have a driver for
Windows we could investigate? Is there perhaps some way to trace what
it sends over the wire in order to mock something up?
Csaba, please attach "lsusb -v" output.
Others: hints?
Thanks,
Jonathan
[1] http://bugs.debian.org/610467
[2] http://ubuntuforums.org/archive/index.php/t-1775541.html
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello Everyone!
I attached the lsusb output!
2012-01-26 22:39 keltezéssel, Jonathan Nieder írta:
Hi,
zitev wrote:
quoted
Thanks for your respond! I did try to probe again with the latest
sid kernel (Linux version 3.2.0-1-686-pae (Debian 3.2.1-2)
(ben-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org) (gcc version 4.6.2 (Debian 4.6.2-12) ) #1 SMP
Tue Jan 24 06:09:30 UTC 2012), but the problem's very same.
What more can I help you?
Here's some context.
Csaba noticed[1] that his keyboard (a "Gigabyte K8100 Aivia USB Gaming
Keyboard") does not work correctly on Linux. It is claimed by the
usbhid driver and:
quoted
all keys absolutely not working, but led's does light.
When I search for information about Linux support for this keyboard
elsewhere, I see that the backspace key and multimedia keys are said
to work but nothing else[2]:
| papibe June 4th, 2011, 09:51 PM
|
| Try to see if xev registers an event while pressing the backspace key:
| $ xev
| Regards.
|
| Peckles June 4th, 2011, 10:07 PM
| Thanks for the command, very useful. Thats going in the memory bank...
|
| The backspace key registers a backspace. Also all of the multimedia
| keys and special 5 mappable keys work as well. (very strange...)
The question becomes: where to go from here? Any idea about how we
can find out what how to drive this device? Does it have a driver for
Windows we could investigate? Is there perhaps some way to trace what
it sends over the wire in order to mock something up?
Csaba, please attach "lsusb -v" output.
Others: hints?
Thanks,
Jonathan
[1] http://bugs.debian.org/610467
[2] http://ubuntuforums.org/archive/index.php/t-1775541.html
Can you set up usbmon and get a trace of e.g., pressing, holding,
then releasing the "a" key? See Documentation/usb/usbmon.txt
in the Linux source or the doc directory of the linux-doc-3.2
package for details.
It works roughly like this:
1. Mount debugfs and load the usbmon module:
mount -t debugfs debugfs /sys/kernel/debug
modprobe usbmon
2. Start tracing:
{
sleep 1; # one second of quiet
cat /sys/kernel/debug/usb/usbmon/1u >/tmp/mon.out &
sleep 20; # twenty seconds or so to run the test
kill $!; # and then stop collecting data
}
3. Somehow summarize the output. If it is fairly small, an
attachment is fine; otherwise, excerpts and maybe a link to a
copy that can be downloaded online might work.
Hope that helps,
Jonathan
Can you set up usbmon and get a trace of e.g., pressing, holding,
then releasing the "a" key? See Documentation/usb/usbmon.txt
in the Linux source or the doc directory of the linux-doc-3.2
package for details.
It works roughly like this:
1. Mount debugfs and load the usbmon module:
mount -t debugfs debugfs /sys/kernel/debug
modprobe usbmon
2. Start tracing:
{
sleep 1; # one second of quiet
cat /sys/kernel/debug/usb/usbmon/1u>/tmp/mon.out&
sleep 20; # twenty seconds or so to run the test
kill $!; # and then stop collecting data
}
3. Somehow summarize the output. If it is fairly small, an
attachment is fine; otherwise, excerpts and maybe a link to a
copy that can be downloaded online might work.
Hope that helps,
Jonathan
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Jonathan Nieder <hidden> Date: 2012-02-01 19:35:56
zitev wrote:
I did every step of test, but after testing the /tmp/mon.out file is
0byte (empty)
Drat. Just to make sure I have the method right, could you do the
same with another keyboard (setting the bus number accordingly), or
using some key that does work, if any (e.g., backspace is said to
work)?
But anyway, this is believable. There is a Windows driver for the
keyboard, so if you are able to run Windows (e.g., in a VM), the hints
from
http://libnetmd.sourceforge.net/howto.html
might help. Also, contacting the manufacturer might help.
Given a rough description of the protocol the keyboard uses, folks on
this mailing list might be able to come up with a rough patch to try
out. One way to make progress.
Thanks,
Jonathan
i attached the detail of syslog:
"Feb 1 20:26:40 player kernel: [ 1247.275287] usb 1-1.1: new high-speed
USB device number 6 using ehci_hcd
Feb 1 20:26:40 player kernel: [ 1247.444488] usb 1-1.1: New USB device
found, idVendor=05e3, idProduct=0608
Feb 1 20:26:40 player kernel: [ 1247.520511] usb 1-1.1: New USB device
strings: Mfr=0, Product=1, SerialNumber=0
Feb 1 20:26:40 player kernel: [ 1247.596369] usb 1-1.1: Product: USB2.0 Hub
Feb 1 20:26:40 player kernel: [ 1247.672160] hub 1-1.1:1.0: USB hub found
Feb 1 20:26:40 player kernel: [ 1247.736605] hub 1-1.1:1.0: 4 ports
detected
Feb 1 20:26:41 player kernel: [ 1248.074036] usb 1-1.1.2: new
full-speed USB device number 7 using ehci_hcd
Feb 1 20:26:41 player kernel: [ 1248.240627] usb 1-1.1.2: New USB
device found, idVendor=1044, idProduct=7a02
Feb 1 20:26:41 player kernel: [ 1248.314881] usb 1-1.1.2: New USB
device strings: Mfr=0, Product=0, SerialNumber=0
Feb 1 20:26:41 player mtp-probe: checking bus 1, device 7:
"/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.2"
Feb 1 20:26:41 player kernel: [ 1248.391648] generic-usb: probe of
0003:1044:7A02.0006 failed with error -22
Feb 1 20:26:41 player kernel: [ 1248.459226] input: HID 1044:7a02 as
/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.1/input/input7
Feb 1 20:26:41 player kernel: [ 1248.523851] generic-usb
0003:1044:7A02.0007: input,hiddev0,hidraw0: USB HID v1.11 Mouse [HID
1044:7a02] on usb-0000:00:1a.0-1.1.2/input1
Feb 1 20:26:41 player kernel: [ 1248.592068] generic-usb
0003:1044:7A02.0008: input,hidraw1: USB HID v1.11 Device [HID 1044:7a02]
on usb-0000:00:1a.0-1.1.2/input2
Feb 1 20:26:41 player mtp-probe: bus: 1, device: 7 was not an MTP device
Feb 1 20:26:41 player kernel: [ 1248.729040] usb 1-1.1.4: new low-speed
USB device number 8 using ehci_hcd
Feb 1 20:26:42 player kernel: [ 1248.917065] usb 1-1.1.4: New USB
device found, idVendor=060b, idProduct=2270
Feb 1 20:26:42 player kernel: [ 1248.990757] usb 1-1.1.4: New USB
device strings: Mfr=1, Product=2, SerialNumber=0
Feb 1 20:26:42 player kernel: [ 1249.063713] usb 1-1.1.4: Product: USB
Keyboard
Feb 1 20:26:42 player kernel: [ 1249.136990] usb 1-1.1.4: Manufacturer: KB
Feb 1 20:26:42 player kernel: [ 1249.219263] input: KB USB Keyboard as
/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4:1.0/input/input8
Feb 1 20:26:42 player kernel: [ 1249.293903] generic-usb
0003:060B:2270.0009: input,hidraw2: USB HID v1.10 Keyboard [KB USB
Keyboard] on usb-0000:00:1a.0-1.1.4/input0
Feb 1 20:26:42 player kernel: [ 1249.380643] generic-usb: probe of
0003:060B:2270.000A failed with error -22
Feb 1 20:26:42 player mtp-probe: checking bus 1, device 8:
"/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.4"
Feb 1 20:26:42 player mtp-probe: bus: 1, device: 8 was not an MTP device"
2012-01-28 08:12 keltezéssel, Jonathan Nieder írta:
zitev wrote:
quoted
I attached the lsusb output!
Perfect, thanks.
quoted
Bus 001 Device 004: ID 1044:7a02 Chu Yuen Enterprise Co., Ltd
[...]
quoted
bNumInterfaces 3
[...]
quoted
Interface Descriptor:
bInterfaceClass 3 Human Interface Device
iInterface 2 KB
[...]
quoted
Interface Descriptor:
bInterfaceClass 3 Human Interface Device
iInterface 3 Mouse
Can you set up usbmon and get a trace of e.g., pressing, holding,
then releasing the "a" key? See Documentation/usb/usbmon.txt
in the Linux source or the doc directory of the linux-doc-3.2
package for details.
It works roughly like this:
1. Mount debugfs and load the usbmon module:
mount -t debugfs debugfs /sys/kernel/debug
modprobe usbmon
2. Start tracing:
{
sleep 1; # one second of quiet
cat /sys/kernel/debug/usb/usbmon/1u>/tmp/mon.out&
sleep 20; # twenty seconds or so to run the test
kill $!; # and then stop collecting data
}
3. Somehow summarize the output. If it is fairly small, an
attachment is fine; otherwise, excerpts and maybe a link to a
copy that can be downloaded online might work.
Hope that helps,
Jonathan
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
I did press backspace, and that key is logged to /tmp/mon.out!
2012-02-01 20:35 keltezéssel, Jonathan Nieder írta:
zitev wrote:
quoted
I did every step of test, but after testing the /tmp/mon.out file is
0byte (empty)
Drat. Just to make sure I have the method right, could you do the
same with another keyboard (setting the bus number accordingly), or
using some key that does work, if any (e.g., backspace is said to
work)?
But anyway, this is believable. There is a Windows driver for the
keyboard, so if you are able to run Windows (e.g., in a VM), the hints
from
http://libnetmd.sourceforge.net/howto.html
might help. Also, contacting the manufacturer might help.
Given a rough description of the protocol the keyboard uses, folks on
this mailing list might be able to come up with a rough patch to try
out. One way to make progress.
Thanks,
Jonathan
I did every step of test, but after testing the /tmp/mon.out file is 0byte
(empty)
next task?
Does /dev/input/eventX get created? (I guess it does, as at least some
key(s) make it through).
If so, please provide
cat /sys/kernel/debug/hid/<device>/rdesc
and
cat /sys/kernel/debug/hid/<device>/events
Please run the second command, then press some of the non-working keys
(press "a" for starters), and provide the output.
--
Jiri Kosina
SUSE Labs
I did every step of test, but after testing the /tmp/mon.out file is 0byte
(empty)
next task?
Does /dev/input/eventX get created? (I guess it does, as at least some
key(s) make it through).
If so, please provide
cat /sys/kernel/debug/hid/<device>/rdesc
and
cat /sys/kernel/debug/hid/<device>/events
Please run the second command, then press some of the non-working keys
(press "a" for starters), and provide the output.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Good, backspace works as expected on 0004 interface. Now please provide
output of the same file when pressing some of the non-working keys, let's
say "A".
Thanks,
--
Jiri Kosina
SUSE Labs