Hello,
My sincere apologies if this has been discussed, but I couldn't find
anything in the FAQ or in the mailing list archive. Please pardon the
length of this message, but I'm trying to give as much information as
possible.
I have been running kernel 2.4.5, and using my Microsoft Natural Pro
keyboard without any trouble at all for the past 4 months. All the
keys worked, including the little media keys ('search', 'mail',
'volume', etc) at the top of the keyboard. I had functions bound to
them in X.
This week, I upgraded to kernel 2.4.12, and the media keys all stopped
working. The regular keys all still work, so I'm getting 'generic'
keyboard support. I rebooted into 2.4.5, and the media keys worked
again, so I'm pretty sure that the only variable in this equation is
the kernel version.
Under 2.4.5, the keyboard would generate events viewable by xev (in X)
and by showkeys (in the console). Under 2.4.12, neither program shows
events when I hit those keys.
Additionally, I modprobed in 'evdev' and cat'ed /dev/input/event1 (the
keyboard). Again, the media keys are silent under 2.4.12 -- it's not
that the machine can't decode them, but rather that they don't even
seem to generate scancodes.
Finally, I checked the bootlogs for the box, and this is the one
difference that I found between kernels.
This is an excerpt from a 2.4.5 bootlog (the one where media keys work):
===
hub.c: USB new device connect on bus2/2/1, assigned device number 3
keybdev.c: Adding keyboard: input0
input0: USB HID v1.10 Keyboard [ Microsoft Natural Keyboard Pro] on usb2:3.0
keybdev.c: Adding keyboard: input1
input1: USB HID v1.10 Device [ Microsoft Natural Keyboard Pro] on usb2:3.1
hub.c: USB new device connect on bus2/2/2, assigned device number 4
mouse0: PS/2 mouse device for input2
input2: USB HID v1.00 Mouse [Logitech USB-PS/2 Mouse] on usb2:4.0
===
And here is the excerpt from 2.4.12 (where media keys do not work):
===
hub.c: USB new device connect on bus2/2/1, assigned device number 3
input0: USB HID v1.10 Keyboard [045e:001d] on usb2:3.0
: USB HID v1.10 Device [045e:001d] on usb2:3.1
hub.c: USB new device connect on bus2/2/2, assigned device number 4
input1: USB HID v1.00 Mouse [Logitech USB-PS/2 Mouse] on usb2:4.0
===
I noticed that the 2.4.5 kernel code recognized my keyboard by its
model name (Microsoft Natural Pro), but the new driver only gives it's
ID (045e:001d). My only theory for now is that the USB HID support
does some extra stuff when it recognizes a special device. For
whatever reason, that recognition isn't happening, so all I'm getting
is generic keyboard support.
Note that the Logitech Mouse (which is daisy-chained off of the
keyboard) works fine in both kernels, and is also recognized by name
in both kernels. It seems that 2.4.12 just doesn't want to recognize
my keyboard by name.
Wierder still is that /proc/bus/usb/devices under 2.4.12 shows:
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms
T: Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=045e ProdID=001d Rev= 1.11
S: Product=Microsoft Natural Keyboard Pro
There's the product name, so why does it exclude it from the logs?
Anyway, I hope that somebody can shed some light on this mystery for
me. While the media keys are not by any means vital, they used to
work perfectly well and I enjoyed controlling XMMS and Mozilla from
them.
Thanks,
Jason
--
Jason Healy | [EMAIL PROTECTED] | http://www.logn.net/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
