Bug 637926 - MacBook 5,1 does not resume properly after suspend when kernel boots with "nomodeset" option
Summary: MacBook 5,1 does not resume properly after suspend when kernel boots with "no...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 636326
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-27 18:49 UTC by W. Michael Petullo
Modified: 2012-08-16 18:40 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-16 18:40:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description W. Michael Petullo 2010-09-27 18:49:51 UTC
Description of problem:
I am running Fedora 14 on a MacBook 5,1. For the last month or so suspend / resume worked fine. After a recent update (not yet sure which), suspend / resume stopped working. If I close the laptop's lid, it suspends. If I open the lid and press a key it seems to spin up the disk but the screen remains completely black.

Version-Release number of selected component (if applicable):
kernel-2.6.35.4-28.fc14.x86_64

How reproducible:
Every time

Steps to Reproduce:
See above.
  
Actual results:
See above.

Expected results:
See above.

Additional info:
I am booting the kernel with the nomodeset option, see bug #636326. I am using the nouveau driver.

Comment 1 W. Michael Petullo 2010-09-27 19:59:17 UTC
I tested kernel-2.6.35.4-12.fc14.x86_64 and it works fine unless I boot with "nomodeset." In the latter case, I get the same symptoms as with kernel-2.6.35.4-28.fc14.x86_64. So, it seems the problem only exists when booting with "nomodeset," but I can't confirm this in kernel-2.6.35.4-28.fc14.x86_64
 because of bug #636326.

Comment 2 Rolf Offermanns 2011-08-28 17:39:34 UTC
Same behaviour for my MBP (5,2) with the F16 alpha release (3.1.0-0.rc3.git0.0.fc16.i686.PAE).

I have to boot with "nomodeset" because of bug #679583.

Comment 3 Rolf Offermanns 2011-08-28 17:41:35 UTC
Can someone please add Fedora 16 to the version field of this bug and maybe of bug #679583, too? Or shall I create new bugs for that?

Comment 4 Fedora End Of Life 2012-08-16 18:40:34 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.