Keyboard Freezes

Just for your information, this problem doesn't happen on any 2.4 kernels, only
noticed on recent 2.6 kernels I've used.

Please attach dmesg output

Created an attachment (id=677)
Output of dmesg

Very strange.

Update: A few ideas I've tried to fix the problem.

Removed all USB devices including USB mouse. No difference, still locked up.

Removed the NVidia commercial driver and went back to the nv driver included
with X, no difference still locked up.

Disabled APM/ACPI - no difference still locked up.

Any other things I should try, let me know.

Nick

This is a known problem with certain Toshiba laptops. I dont have a work around
for yet. If any.

chuck

So this is a different issue from the other keyboard-not-working bug(s)?

For toshibas yes. Googling for the particular laptop that this user is using,
shows alot of resutls of keyboard not working. Workarounds by using keystrokes
and the like.

chuck

Come to think about it, you might want to check to see if there is a bios upgrade.

chuck

Lowering severity since this is a bios issue.

(In reply to comment #10)
> Lowering severity since this is a bios issue.

I get the same behaviour on my system.
My machine is not a laptop.
I have a Microsoft Wireless Keyboard 1.1.

I find that when I use wvdial to dial up the internet, the keyboard almost freezes.
I can still type, but every second or third keystroke fails to appear on screen
and sometimes I have to try retyping a letter many times for it to appear.

I also have Windows 2000 and Novell Linux Desktop 9 on the same machine and this
problem does not happen on either of these OSes.

Novell Linux uname -a output: Linux NovLin 2.6.5-7.139-default #1 Fri Jan 14
15:41:33 UTC 2005 i686 athlon i386 GNU/Linux

(My BIOS clock is wrong - need new battery, hence strange date)

I think it is a Ubuntu specific bug and may have something to do with networking?

This bug has been flagged because it is old and possibly inactive. It may or may
not be fixed in the latest release (Breezy Badger 5.10). It is being marked as
"NEEDSINFO". In two weeks time, if the bug is not updated back to "NEW" and
validated against Breezy, it will be closed.

This is needed in order to help manage the current bug list for the kernel. We
would like to fix all bugs, but need users to test and help with debugging.

If this change was in error for this bug, please respond and make the
appropriate change (or email <email address hidden> if you cannot make the
change).

Thanks for your help.

Closing, inactive.