On Sun, 7 Apr 2002 20:23, Justin A wrote:
> The problem with the aten kvm is exactly the same as with this HP
> keyboard, it works in 2.2.20, the mandrake 2.4 kernel, but none of the
> newer 2.4 kernels.
What does the "mandrake 2.4 kernel" claim to be (cat /proc/version)?
Which "newer 2.4 kernels" did you try.

> I tried adding the keyboard to the blacklist, but it is confusing since
> the keyboard/hub shows up in 3 places in lsusb
It isn't that confusing. The keyboard has a hub device build in. You'd see the 
tree if you plotted it out (or used a tool like usbview)


> It shows up as hub, keyboard, and an unexplained generic hub
> attached is the output of lsusb.  The only thing he says is connected is
> the keyboard, camera, and the mouse plugged into the keyboard.
It might have helped if you'd removed the other devices, to simplify your life 
and shorten the output.

> all dmesg has to say again is this:
>
> input0: USB HID v1.00 Keyboard [HP Multimedia Keyboard Hub] on usb1:5.0
> input1,hiddev0: USB HID v1.00 Pointer [HP Multimedia Keyboard Hub] on
> usb1:5.1
You can turn up debugging to get more information (also, look at the dmesg 
options).

> I tried every combination of NOGET and IGNORE on the 3 different
> devices, but nothing seemed to work.
Probably partly because two of them are hubs:)
Also, IGNORE says "never bind to this device", which you probably don't want.

> Here are the lines I used
>
> #define USB_VENDOR_ID_HP                0x03f0
> #define USB_DEVICE_ID_HP_MKH2           0x020c /*Multimedia Keyboard
> Hub*/
> { USB_VENDOR_ID_HP, USB_DEVICE_ID_HP_MKH2, HID_QUIRK_NOGET },
These are the only lines that are doing anything, but they look fine (assuming 
that it really is the same problem, which you haven't actually shown yet).
Which kernel are you trying this on?

Brad




_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to