With my problem, the keyboard not working seems to behave like a random bug, popping up whenever it feels like it. I'm thinking that maybe this is some sort of race condition, which may or may not be related to multiple dependent threads running out of sync in the 686 kernel (But then again, I'm no kernel expert at all, just my hunch).
When it happens on my PC, I am able to put the keyboard in the PS/2 mouse port (it's open since my mouse is a USB mouse), and then the keyboard will work in this port until the next reboot. I've managed to get syslogs for each case, both when the keyboard works in the keyboard PS/2 port, and when it doesn't work, forcing me to unplug it and put it into the PS/2 mouse port. I've attached a tar.gz with both logs included as separate text files. The "Working_keyboard.txt" file contains the log of 2 separate working boots, with different kernels, 2.6.17-10-generic and 2.6.17-11-generic. I've marked the places in the file where one ends and the other begins. There is an interesting line in the file entitled "Broken_keyboard.txt" on line 178 as follows: "PNP: No PS/2 controller found. Probing ports directly." The cooresponding lines in the file entitled "Working_keyboard.txt" are lines 183 and 704, which both say: "PNP: PS/2 Controller [PNP0303:KBD] at 0x60,0x64 irq 1" Hopefully this helps. ** Attachment added: "syslog files" http://librarian.launchpad.net/6392586/syslogs.tar.gz -- no ps/2 keyboard with kernel 2.6.15-27-686-smp https://launchpad.net/bugs/83066 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
