Red Hat Bugzilla – Bug 234549
Some Keyboard Keys Unresponsive on Microsoft Natural 4000
Last modified: 2008-02-11 09:22:33 EST
Description of problem:
Ever since a recent update, the lights on my MS Natural Keyboard don't light up
when caps/numlock/scrlk are pressed, even though they produce the desired effect
on the system. Also, the Fn keys are completely unresponsive. All other keys
seem to work normally.
Version-Release number of selected component (if applicable):
I'm running kernal version 2.6.20-1.2300.fc5smp
Chris, are you sure your other keys are working properly? I am having the same
problem as you describe with one extra benefit, X will crash if I use the
With the 2.6.19 and lower kernels, I was able to use the multimedia keys on my
4000 with this Xorg setup:
Option "XkbModel" "microsoft"
Option "XkbLayout" "us"
along with some shortcuts mapping, say, XF86Calculator to the correct events in
my Xfce configuration. But, as of the 2.6.20 kernels, I get crashes upon a
I know there is a kernel patch for the MS Natural Ergonomic Keyboard 4000 that
was developed by a Gentoo user:
But, I don't really know how to build patches against the Fedora kernels anymore
since it's all kind of changed. Li Yu (who seems to be the one running the 4000
kernel patches) has been active on this Ubuntu forum here:
One telling quote is this:
The hid core is split from USB since kernel 2.6.20. So we can not port this
driver to it easier.
I already have ported it to 2.6.21-rc2. see this URL:
version 0.5.0 http://lkml.org/lkml/2007/3/5/18
Well, I think it also can use it in 2.6.20 kernel, however it may need some
little changes ( adjust the offset of some lines ).
I'm guessing this split of hid from USB is the reason for the new problems.
Aw nuts, I just saw this was a FC5 bug. I'll open up an FC6 bug, as I'm using that.
Thanks for the insight. I'll investigate those tonight when I get home. About
the multimedia keys, I generally don't use them, but the volume and mute buttons
still work just fine.
Chris, I figured out with the help of the #livna people (long story) that the
multimedia crashes were my fault. My udev mojo wasn't good enough, so Xorg was
reading the multimedia keys as a mouse button or something.
My mouse event number changed, but I wasn't using my custom udev rule for my
mouse. So when there was a reboot, the event number changed, and kablammo.
But, I am still seeing the same NumLock and CapsLock "non-lighting" that you see
on my FC6 box.
Are you using USB or PS/2 to connect your keyboard. Please try the other method,
too, as it triggers different kernel code.
I'm using USB and I'm afraid I can't connect to a PS/2 port: there isn't one on
my box. 'Tis all USB, 'tis.
Sorry, sorry. Wrong thread to reply in.
Hello Chris, AFAIK it's fixed in 2.6.20-1.2952.fc6. Can you try?
I recently upgraded to Fedora 7, and everything on my keyboard appears to work
I have to rescind my previous statement. I'm using kernel 2.6.21-1.3228.fc7
and all of the Fn keys are still unresponsive. They had been working for a
while, but now they're broken again.
Everything seems to work, *except* the Fn keys. This is especially weird because
xev shows that the Fn keys are generating correct X events. the F1 key has
keycode 245, F2 has 135, F3 has 138, and so on. I'm unsure why X/Gnome are not
acting on these events.
Heh, well this is embarrassing. I didn't have my Fn lock set. Now everything
works perfectly. I think this bug can be closed.
Fine, changing component to kernel (this is not kbd bug at all), closing as