Re: hid device not claimed but /dev/input/event exists
On Tue, 19 Feb 2008, Tomas Carnecky wrote: > This bug is in a completely different place then I thought! The speakers > were plugged into the hub built into my monitor. I plugged it directly > into the mainboard and voila, it works. Even g15daemon, the lcd driver, > can now display a nice clock on the lcd. Could it be that the hub is > defective? Definitely could be. Please collect usbmon logs (this is what you asked for previously -- the USB traffic analyzer -- see Documentation/usb/usbmon.txt) and send them to the usb-devel mailinglist. This is no longer related to HID code at all. Thanks for tracking this down, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: hid device not claimed but /dev/input/event exists
Jiri Kosina wrote: Does anything appear in dmesg when you press those buttons? There should be messages resembling the one you already have there: drivers/hid/hid-core.c: report (size 8) (unnumbered) drivers/hid/hid-core.c: report 0 (size 8) = 00 00 28 00 00 00 00 00 and they should react to keys such as FastForward, Play, Mute, Volume Up, etc. This bug is in a completely different place then I thought! The speakers were plugged into the hub built into my monitor. I plugged it directly into the mainboard and voila, it works. Even g15daemon, the lcd driver, can now display a nice clock on the lcd. Could it be that the hub is defective? tom -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: hid device not claimed but /dev/input/event exists
Jiri Kosina wrote: On Tue, 19 Feb 2008, Tomas Carnecky wrote: The device apparently has four 'interfaces' - whatever that is, see [1]. It seems like usbhid probes interface 2 (which is the LCD plus a few buttons, probably the four just under the LCD, as described [1]). Because usbhid doesn't know how to handle the buttons, it fails. But then it probes interface 3 which is a 'proper' HID device with well-defined buttons. Yes, the dump clearly shows that. Does anything appear in dmesg when you press those buttons? There should be messages resembling the one you already have there: drivers/hid/hid-core.c: report (size 8) (unnumbered) drivers/hid/hid-core.c: report 0 (size 8) = 00 00 28 00 00 00 00 00 and they should react to keys such as FastForward, Play, Mute, Volume Up, etc. Nothing. Not even after I removed the alsa-usb-audio driver. All I see is Keyboard.*, but the events from the speaker should be Key.*, right? It looks like the speaker goes into a different mode once the USB cable is plugged in. Without the USB cable, the Z-10 acts as simple/dumb speaker, the volume up/down buttons change the internal volume, and I see that on the display, too. The play/next/prev song buttons don't do anything, which is quite obvious. But once the USB cable is plugged in, the volume up/down buttons stop reacting. I assume they are now meant to send events to the computer so that some software can decide what to do. But features that are not useful for the computer (bass/treble), can still be controlled using the buttons on the speaker. The buttons are not dead. I can see that because the display goes to sleep after a few seconds of inactivity, and when I press the volume buttons, it wakes up and displays the current volume. So the speaker is definitely seeing that the buttons are being pressed. Is there a USB packet inspector/dumper, like libpcap for network? tom -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: hid device not claimed but /dev/input/event exists
On Tue, 19 Feb 2008, Tomas Carnecky wrote: > The device apparently has four 'interfaces' - whatever that is, see [1]. > It seems like usbhid probes interface 2 (which is the LCD plus a few > buttons, probably the four just under the LCD, as described [1]). > Because usbhid doesn't know how to handle the buttons, it fails. But > then it probes interface 3 which is a 'proper' HID device with > well-defined buttons. Yes, the dump clearly shows that. Does anything appear in dmesg when you press those buttons? There should be messages resembling the one you already have there: drivers/hid/hid-core.c: report (size 8) (unnumbered) drivers/hid/hid-core.c: report 0 (size 8) = 00 00 28 00 00 00 00 00 and they should react to keys such as FastForward, Play, Mute, Volume Up, etc. -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: hid device not claimed but /dev/input/event exists
Jiri Kosina wrote: On Tue, 19 Feb 2008, Tomas Carnecky wrote: usb 1-2.2: new full speed USB device using ehci_hcd and address 6 usb 1-2.2: configuration #1 chosen from 1 choice HID device claimed by neither input, hiddev nor hidraw input: Logitech Z-10 USB Speaker as /devices/pci:00/:00:02.1/usb1/1-2/1-2.2/1-2.2:1.3/input/input4 input: USB HID v1.10 Device [Logitech Z-10 USB Speaker] on usb-:00:02.1-2.2 Nobody claims the device and yet an evdev device shows up in /dev/input? That Yes, that looks indeed bogus. I enabled HID_DEBUG, but no debug messages show up in my dmesg output, which is strange. You have to modprobe the 'hid' module with 'debug=1' parameter. Please send me the resulting output. Attached is the dump from dmesg. The device apparently has four 'interfaces' - whatever that is, see [1]. It seems like usbhid probes interface 2 (which is the LCD plus a few buttons, probably the four just under the LCD, as described [1]). Because usbhid doesn't know how to handle the buttons, it fails. But then it probes interface 3 which is a 'proper' HID device with well-defined buttons. But still nothing shows up if I press the buttons. But something is strange, neither does when I press buttons on my sidewinder pad. Unless I 'cat /dev/input/event5' and then press the buttons, then they shows up in dmesg. But that trick doesn't work with the Z-10 speakers. Maybe the alsa driver is interfering somehow? [1] http://forums.logitech.com/logitech/board/message?board.id=stereo_20&message.id=633#M633 usb 1-2.2: new full speed USB device using ehci_hcd and address 8 usb 1-2.2: configuration #1 chosen from 1 choice drivers/hid/usbhid/hid-core.c: HID probe called for ifnum 2 drivers/hid/usbhid/hid-core.c: report descriptor (size 46, read 46) = 06 00 ff 09 00 a1 01 15 00 26 ff 00 75 08 95 08 06 00 ff 09 02 85 02 06 00 ff 09 03 81 02 09 04 95 03 b1 02 09 06 85 03 96 df 03 91 02 c0 drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0102 wIndex=0x0002 wLength=9 drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0302 wIndex=0x0002 wLength=4 INPUT(2)[INPUT] Field(0) Usage(8) ff00.0002 ff00.0003 ff00.0003 ff00.0003 ff00.0003 ff00.0003 ff00.0003 ff00.0003 Logical Minimum(0) Logical Maximum(255) Report Size(8) Report Count(8) Report Offset(0) Flags( Variable Absolute ) OUTPUT(3)[OUTPUT] Field(0) Usage(991) ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006 ff00.0006
Re: hid device not claimed but /dev/input/event exists
On Tue, 19 Feb 2008, Tomas Carnecky wrote: > usb 1-2.2: new full speed USB device using ehci_hcd and address 6 > usb 1-2.2: configuration #1 chosen from 1 choice > HID device claimed by neither input, hiddev nor hidraw > input: Logitech Z-10 USB Speaker as > /devices/pci:00/:00:02.1/usb1/1-2/1-2.2/1-2.2:1.3/input/input4 > input: USB HID v1.10 Device [Logitech Z-10 USB Speaker] on > usb-:00:02.1-2.2 > Nobody claims the device and yet an evdev device shows up in /dev/input? That Yes, that looks indeed bogus. > I enabled HID_DEBUG, but no debug messages show up in my dmesg output, > which is strange. You have to modprobe the 'hid' module with 'debug=1' parameter. Please send me the resulting output. -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
