hibernate makes ps/2 to usb keyboard connection fail

this also affect the suspend function. After suspending the laptop the keyboard again fails to work.

this also affects the suspend function. After suspending the laptop the keyboard again fails to work.

within the last six hours the entire ps/2 connection has died, both external keyboard and mouse. There were several backport updates today, I suspect some updated lib* package has now killed off my ps/2 connection.

that last post was incorrect.

It appears that if, during bootup, I hit a key to enter the bios, and then Esc to return to the normal bootup sequence, neither the external mouse nor keyboard will function.

however if I avoid entering the Bios the external connectivity continues to work (as long as I do not suspend or hibernate the laptop).

Still happening in Intrepid.

There is another bug I saw recently about a keyboard that did not work if plugged in after boot. Unfortunately I cannot find it, but I think it is the same problem. It has something to do with the current available to USB devices on plugging in.

In my case the keyboard stops working after suspend to RAM (have not tried hibernate yet), and does not work if plugged in after booting - which is why I think it is one problem.

Still happening in 13.10 Xubuntu.

I have a vaio vgn-cs11z and after waking up from suspention, the laptop' s keyboard doesn't work. However, a usb keyboard would work. This makes me believe that the connection of the laptop's keyboard on the motherboard is ps2 (thus I'm posting this here).

I'm interested in trying fixing this. If an Ubuntu developer comes across this post please give some info on where I could get started from (and / or hints/tips). It would really accelerate the course of my effort.

I have found a fix to the problem in my case.

So it seems that in my case (see post #6), the keyboard and touchpad are connected with ps/2 on a i8042 controller, who is not that well supported by the kernels for quite a while (based on info I picked up during my research, this problem exists for quite a while).

The fix that works for me, is to pass the arguments i8042.direct and i8042.dumbkbd to the kernel via grub. But these arguments are for me... for other laptops, maybe other arguments would do the trick. Here's a link I found with a good enough sample of options concerning i8042:
http://lightrush.ndoytchev.com/random-1/i8042quirkoptions

So maybe others could check this fix and post back... Then we can have a good idea if this is the common source of the problem... Here's how:

First check if the laptop is actually using that controller, by running
dmesg | grep i8042

that would give you an idea. So if the controller is there, there is a chance that fix might be for you. Then check which kernel you're using running
uname -a

Then go to /boot/grub/grub.cfg and find which entry calls the kernel that's used. Go to the line that starts with 'linux...' and then has the name of the kernel. Then, go at the end of the line, and add the i8042 options that you're trying. Example,
i8042.direct i8042.dumbkbd

Cheers

jensporup, thank you for reporting this bug to Ubuntu. Fiesty reached EOL on October 19, 2008.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this reproducible in a supported release? If so, could you please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 129725

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]