keyboard stops working after login

[hraq]

This bug appears to affect upgraded os 8.04 or a brand new installation of 8.04.
The keyboards tested are: the old format Apple keyboard and the new format Apple keyboards and a PS/2 keyboard.
All of them were working absolutely fine with 7.10 and earlier versions on the same system (Gigabyte motherboard):

System log viewer shows the following:

"usb 1-5.3 rejected 1 configuration due to insufficient available bus power"
"usb 5-5.3 rejected 1 configuration due to insufficient available bus power"
"usb 5-4.3 rejected 1 configuration due to insufficient available bus power"

all of above are reported because I tried all usb ports I have, which includes:
1. motherboard integrated usb ports
2. front usb ports
3. another front usb port

This is a horrible bug because it prevents me from using the system at all.

One thing strange happened old format Apple keyboard if plugged with new one will make the new one work partially ( only letters) no function keys or keypad.

The problem happened during a fresh installation of ubuntu 8.04 on the same hardware when the installer asked for user name and password and system name which come after partitioner finishes its job.

Keyboards are absolutely fine and work fine on many machines. Its got to be a software issue.
BIOS support for USB and legacy keyboards and USB 1 and 2 are the same and didn't change at all.
Please fix this issue ASAP

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[kernel-janitor (kernel-janitor)]

Hi hraq,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you 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-image-`uname -r` 226199

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.]