Thanks for the thoughts guys... I probably will wind up compiling the kernel again from
scratch since I haven't been able to make any headway with this issue. I thought I'd read
somewhere that genkernel was working pretty smoothly and saved a lot of hassle, but I
guess it isn't all it's cracked up to be.
As for your questions, the loss of keyboard and mouse occurs while I'm in X, however, I'm
in X most of the time, so that doesn't necessarily mean that much. And after
force-quitting X (there's something interesting... ctrl-alt-backspace still works!), I'm
generally hosed on the command line too... sometimes I get the wrong characters for keys,
sometimes I just get nothing and have to ssh in from another box and reboot.
I also did try showkey and I'm pretty sure I was getting weird random keycodes popping
out... especially if I typed fast. My hunch is that it's actually something in the PS2
driver and not anything in X or the keymap.
thanks again,
b
Moshe Kaminsky wrote:
Hi,
I don't really know what's going on. Just wanted to suggest some things:
1. I don't think it has anything to do with the 'Unknown key' messages.
This simply means that there are some funny keys on the keyboard that
the kernel doesn't recognize. You can check it with the showkey(1)
program (but under X)
2. Does it happen also when X is not running, or only under X?
3. Maybe you should try recompiling the kernel, and see if there are any
options specific to your keyboard (in menuconfig, you can search for
a string by pressing /). Maybe you should grep the kernel docs
(/usr/src/linux/Documentation) for your keyboard name.
Sorry I can't help more,
Moshe
* Ben Munat [EMAIL PROTECTED] [18/08/05 06:20]:
Really hoping someone has some idea on this... haven't found any solid
answers on the web...
b
--- original message -
Hello,
I recently did a fresh install of 2005.0 on a AMD thunderbird-based machine.
I wasn't in
the mood for kernel configuring, so I just let genkernel do it's thing,
installing a 2.6
kernel.
Things mostly went fine, however my keyboard and/or mouse keep going
berserk... they just
stop working half the time. I share the same keyboard with a windows machine,
and it works
fine (I'm typing this email with it).
Last week, I noticed a lot of entries in the logs like this:
Aug 16 22:33:53 venus atkbd.c: Unknown key released (translated set 2, code
0xe0 on
isa0060/serio0).
Aug 16 22:33:53 venus atkbd.c: Use 'setkeycodes e060 keycode' to make it
known.
Aug 16 22:40:18 venus atkbd.c: Unknown key pressed (translated set 2, code
0x8e on
isa0060/serio0).
Aug 16 22:40:18 venus atkbd.c: Use 'setkeycodes e00e keycode' to make it
known.
I found a thread on the forums where the poster went ahead and set the
keycodes as
indicated... for all of them. So, last week, I took the log and cut and paste
it together
to make a script that set all of them... at least until last night. It
started printing
these lines again, and I lost the mouse and the keyboard. Restarted X and it
was okay for
a few minutes, but then it freaked out again and then I couldn't type
anything
at the command line even after killing X.
Oh, I also managed to find the mouse and keyboard boot info from my logs:
Aug 9 20:28:35 venus input: AT Translated Set 2 keyboard on isa0060/serio0
Aug 9 20:28:35 venus input: ImExPS/2 Generic Explorer Mouse on
isa0060/serio1
So, if anyone has any ideas or can point me in any direction at all, that
would be great.
Ben
PS: I also found the following stuff in my logs starting at the time when I
lost control
of the keyboard and mouse; there's this MTRR stuff and then hundreds of lines
with the
call trace stuff:
Aug 16 22:46:31 venus mtrr: no MTRR for cd80,80 found
Aug 16 22:46:31 venus mtrr: no MTRR for cc00,100 found
Aug 16 22:46:31 venus mtrr: no MTRR for cd00,80 found
Aug 16 22:46:38 venus mtrr: no MTRR for cc00,100 found
Aug 16 22:46:38 venus mtrr: no MTRR for cd00,80 found
Aug 16 22:46:56 venus mtrr: no MTRR for cd80,80 found
Aug 16 22:46:56 venus mtrr: no MTRR for cc00,100 found
Aug 16 22:46:56 venus mtrr: no MTRR for cd00,80 found
Aug 16 22:48:08 venus
Aug 16 22:48:08 venus sibling
Aug 16 22:48:08 venus task PC pid father child younger older
Aug 16 22:48:08 venus init S 0 1 0 2
(NOTLB)
Aug 16 22:48:08 venus dfe3fecc 0082 00d0 c01313c2 c0131656
c039f200 c039eb00
Aug 16 22:48:08 venus 0001 c14053e0 082a 534ee15d
0001d93f c0399bc0
Aug 16 22:48:08 venus c1527a20 c1527b44 1f056d90 1f056d90 dfe3fed4
0800
Aug 16 22:48:08 venus Call Trace:
Aug 16 22:48:08 venus [c01313c2]
Aug 16 22:48:08 venus [c0131656]
Aug 16 22:48:08 venus [c033580f]
Aug 16 22:48:08 venus [c011ca6e]
Aug 16 22:48:08 venus [c01554f3]
Aug 16 22:48:08 venus [c0155127]
Aug
