You are not logged in.
I have not been able to upgrade my kernel since 2.6.25.11 (x86_64).
All kernels prior to that work just fine. All kernels after that do not.
Basically, all of my multimedia keys stop working (Microsoft Wireless Laser Keyboard 6000 v2.0 - USB).
xev shows no output whatsoever, the kernel does not even register a keypress.
What has changed? Is this an Archlinux issue or a kernel issue?
(And no, it is not something simple like a missing .Xmodmap file. Like I said, simply downgrading back to 2.6.25.11-1 is all that is needed for things to operate as they have for the last two years)
Any clues?
Last edited by henno (2008-10-30 10:09:21)
Offline
xev shows no output whatsoever, the kernel does not even register a keypress.
In this case , there should be an entry in '/var/log/messages'.
Isn't there any ?
Mektub
Follow me on twitter: https://twitter.com/johnbina
Offline
xev shows no output whatsoever, the kernel does not even register a keypress.
In this case , there should be an entry in '/var/log/messages'.
Isn't there any ?
Mektub
There is nothing in the logs. Like I said, the kernel is not even registering a keypress, let alone logging one.
Offline
There is nothing in the logs. Like I said, the kernel is not even registering a keypress, let alone logging one.
Thats someting else, then, I am afraid I can't help.
About two years ago I had a similar problem, that is 'xev' didnt show any output, howewer in
'/var/log/messages' I had warnings like:
Jan 9 23:47:16 jerec atkbd.c: Unknown key released (translated set 2, code 0xe1 on isa0060/serio0).
Jan 9 23:47:16 jerec atkbd.c: Use 'setkeycodes e061 <keycode>' to make it known.
so to define my multimedia keys I had to put on my 'etc/rc.local' lines like
# Video
setkeycodes e014 183 #define KEY_F13
# Music
setkeycodes e013 184 #define KEY_F14
Mektub
Follow me on twitter: https://twitter.com/johnbina
Offline
This seems to be a general problem, not just Arch.
On my keyboard (Microsoft Laser 6000 - they do make quite nice hardware ...) some but not all the keys work. This happens in the new Ubuntu as well (was fine in older Arch and older Ubuntu). The keys don't generate any scankey events at any point in the system - there appear to multiple /dev/inputx files for the same keyboard.
Offline
Yep. I tend to agree with you there.
I would just love to know what changed between 2.6.25 and every other kernel that has come after it.
Offline
https://bugs.launchpad.net/ubuntu/+bug/281993
This seems very related.
Offline
I can confirm that the bug linked above is definately the issue.
Patching the kernel and recompiling has fixed it, although at the expense of taking out whatever quirks fixes were added too the kernel in the first place.
Offline