[lkml]   [2003]   [Sep]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.0-test5 vs. APM or keyboard driver
    From: "Norman Diamond" <>

The above complaints all concern either APM or the keyboard driver. I am
not sure if the 2.6.0 keyboard driver could be the reason why the BIOS no
longer even gets signals from the keyboard. I have never seen any other
situation where a keyboard's "Fn" key plus functional meaning of another
key could get broken, so I'm not sure if a broken keyboard driver could
really be this powerful.

Some versions of 2.6 combined with some keyboard versions
will set the keyboard to scancode mode 3. Some (most? all?)
BIOSes expect translated scancode mode 2 and do not work
in any other mode.

So, in case you have scancode mode set 3, change that.

So far we have heard about precisely one keyboard in the world
where scancode mode 3 was useful. It is the Japanese keyboard
of John Bradford. He once wrote

> My keyboard has a distinct ID, and works fine in set 3,

Let me repeat the question:
John: What ID does this keyboard report?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:48    [W:0.018 / U:17.984 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site