MacBook 4,1 screen remains black after opening the lid

[Matthew Paul Thomas]

Problem occurs with: Ubuntu Lucid, Linux kernel 2.6.32-16 and all other updates installed
Does not occur with: Ubuntu 9.04, Ubuntu 9.10

1. Close the lid of a MacBook.
2. Wait ten seconds.
3. Open the lid.

What happens: It wakes up, but the screen stays black.
What should happen: It wakes up and shows the unlock screen.

Workaround: After opening the lid, press Fn+Ctrl+Option+F1 (a text login prompt will appear), then Fn+Option+F7 (the unlock screen will appear).

This was previously marked as a duplicate of bug 488328. It might be related to bug 540134.

(Data from original report:)
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mpt 2184 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x90700000 irq 20'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,106b3600,00100103'
   Controls : 34
   Simple ctrls : 21
Date: Fri Feb 19 14:59:53 2010
DistroRelease: Ubuntu 10.04
MachineType: Apple Inc. MacBook4,1
NonfreeKernelModules: wl
Package: linux-image-2.6.32-13-generic 2.6.32-13.18
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-13-generic root=UUID=11cc112e-2fe8-415f-91d5-fd68b0f8dc1f ro quiet splash
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.29
Reproducible: Yes
RfKill:

SourcePackage: linux
TestedUpstream: No
Uname: Linux 2.6.32-13-generic i686
WpaSupplicantLog:

dmi.bios.date: 02/09/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB41.88Z.00C1.B00.0802091535
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F22788A9
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22788A9
dmi.modalias: dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9:
dmi.product.name: MacBook4,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[Chase Douglas (chasedouglas)]

@Matthew or @Angel:

Can you test the kernel in bug 488328 to see if it fixes your issue?

Thanks

[Matthew Paul Thomas (mpt)]

I tested using the i386 equivalent you provided, <http://people.canonical.com/~cndougla/488328/linux-image-2.6.32-13-generic_2.6.32-13.19~lp488328_i386.deb>. It fixed the problem.

[Chase Douglas (chasedouglas)]

Matthew confirmed that the kernel provided for the other bug fixes his kernel issues, so I'm marking this as a duplicate.

[Matthew Paul Thomas (mpt)]

While that kernel did fix the problem, bug 488328 has now been marked as fixed, but this bug still is not fixed with kernel 2.6.32-16. Reopening.

[penalvch (penalvch)]

Matthew Paul Thomas, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Matthew Paul Thomas (mpt)]

No, I have not experienced this problem in the past couple of years.

[penalvch (penalvch)]

Matthew Paul Thomas, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/524467/comments/7 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.