Bug 876370 - Unable to boot F18 Beta TC8 into graphical desktop on MacBook Pro 5,1
Summary: Unable to boot F18 Beta TC8 into graphical desktop on MacBook Pro 5,1
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-13 23:25 UTC by Alex Murray
Modified: 2014-02-05 13:03 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 13:03:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
/var/log/Xorg.0.log when booting with nomodeset (8.79 KB, text/plain)
2012-11-15 12:38 UTC, Alex Murray
no flags Details
Xorg log - MBP 3,1 - no custom boot options - FC18 Beta release (7.75 KB, text/x-log)
2012-11-27 21:22 UTC, Gaspard Jankowiak
no flags Details

Description Alex Murray 2012-11-13 23:25:28 UTC
Description of problem:
Previously [1] the only way to successfully boot Fedora on a MacBook Pro 5,1 was to disable acceleration for nouveau (using the nouveau.noaccel=1 command-line parameter) - HOWEVER with Fedora 18 even this doesn't work.

Without noaccel - Machine Check Error occurs
With noaccel    - Freezes after trying to start gdm (I think)

So now the only way to boot at all is to use nomodeset - however in this case gdm fails to start (I'll try and attach an Xorg.0.log later if I can get it off the live environment). 

The only way to then successfully start a graphical login and run the installer is to install the proprietary drivers inside the live environment [2] and manually rmmod nouveau; modprobe nvidia; systemctl restart gdm


[1] https://bugzilla.redhat.com/show_bug.cgi?id=679583
[2] http://rpmfusion.org/Configuration

Comment 1 Alex Murray 2012-11-15 12:38:24 UTC
Created attachment 645609 [details]
/var/log/Xorg.0.log when booting with nomodeset

Comment 2 Gaspard Jankowiak 2012-11-27 21:20:39 UTC
I have a similar problem with MBP 3,1. Everything goes well (apart from screen flickering but that was in F17, see [1]) up to the point of starting X where it hangs, showing the 2 last messages from the boot sequence.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=825497

Comment 3 Gaspard Jankowiak 2012-11-27 21:22:45 UTC
Created attachment 653128 [details]
Xorg log - MBP 3,1 - no custom boot options - FC18 Beta release

Comment 4 Fedora End Of Life 2013-12-21 09:23:28 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is 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  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 5 Fedora End Of Life 2014-02-05 13:03:10 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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