Linux 2.6.32 won't boot ubuntu 10.04

[NoBugs!]

The 2.6.32 kernel won't boot 10.04, it gives an error:
An error occurred mounting /proc/bus/usb
It says to press S to skip, M for manual, but neither work. It does work with 2.6.31.

[NoBugs! (luke32j)]

I fixed the /proc/bus/usb problem. I looked in the /etc/fstab and saw:
# for virtualbox:
none /proc/bus/usb usbfs devgid=126,devmode=664 0 0
After commenting out the none /proc/bus/usb with #, it doesn't show that mount error.
However, I still can't use 2.6.32, everything starts up fine but the laptop keyboard and usb keyboard are not recognized at all, not even ctrl+alt+F2.

[Jeremy Foshee (jeremyfoshee)]

Hi NoBugs!,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 571528

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]