Macbook Pro keyboard fails with new kernel 2.6.32-17,19,20,21

Bug #549112 reported by TDJACR
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned
Nominated for Lucid by TDJACR

Bug Description

With 2.6.32-17 installed after an upgrade to beta, the keyboard fails to operate (caps lock fails too) on a MacBook Pro 5,3. If I tell grub to use older kernels, it works fine.

TDJACR (thedjatclubrock)
tags: added: kernel-bug
affects: ubuntu → linux (Ubuntu)
Revision history for this message
TDJACR (thedjatclubrock) wrote :

2.6.31-20 is now not functioning either, it just hangs. 2.6.31-19 works okay.

Revision history for this message
TDJACR (thedjatclubrock) wrote :

2.6.31-20's error was not reproducible after an update.

tags: added: kernel-series-unknown
Revision history for this message
TDJACR (thedjatclubrock) wrote :

Updated to the new kernel - 2.6.32-19. Same issue, keyboard doesn't work, touchpad is fine. No indication that the keyboard is recognized, as caps lock light doesn't function.

summary: - Macbook Pro keyboard fails with new kernel 2.6.32-17
+ Macbook Pro keyboard fails with new kernel 2.6.32-17 and -19
Revision history for this message
TDJACR (thedjatclubrock) wrote : Re: Macbook Pro keyboard fails with new kernel 2.6.32-17 and -19

I wish I could be of more assistance. If Lucid is going to be released this month, this error needs squashing soon. I'm not sure as to how widespread this bug is, but it seems as if MacBook Pro users won't be able to use their keyboards, which is a big no-no for a Long Term Support.

tags: added: lucid
removed: kernel-series-unknown
Revision history for this message
TDJACR (thedjatclubrock) wrote :

This is a big issue, and unless there is some configuration error with the machine, it's very important that the issue is resolved. LTS comes out in a matter of days and I still can't type on my computer :/

summary: - Macbook Pro keyboard fails with new kernel 2.6.32-17 and -19
+ Macbook Pro keyboard fails with new kernel 2.6.32-17,19,20,21
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi TDJACR,

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 549112

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

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
TDJACR (thedjatclubrock) wrote :

With the newest .32 kernel mainline, it works fine.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

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 development release http://cdimage.ubuntu.com/daily-live/current/ . 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.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.