Bug 874918 - TC7 EFI boot won't show Xorg on Macbook pro 8,2
Summary: TC7 EFI boot won't show Xorg on Macbook pro 8,2
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-09 05:10 UTC by William Brown
Modified: 2012-11-13 03:04 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-11-13 03:04:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
X.log from macbook pro 8,2 (54.73 KB, text/plain)
2012-11-09 23:47 UTC, William Brown
no flags Details

Description William Brown 2012-11-09 05:10:08 UTC
Description of problem:
Anaconda is unable to show Xorg or graphical displays on Macbook pro 8,2. This forces users to use "nomodeset" and the text installer.

NOTE that Xorg *does* work on this model of hardware once the install is completed  with *no* kernel or command line modifications.


How reproducible:
Always


Steps to Reproduce:
1. Create Anaconda live USB with --efi support
2. Boot from EFI on a dual gpu macbook pro.
  
Actual results:
Display goes black

Expected results:
Anaconda and Xorg should start.

Additional info:

As previously stated, Xorg does work on this model of laptop with no kernel or grub2 modifications. the working kernel is 3.6.6. I am happy to try and work with this to find a fix, since it is hardware dependent.

Comment 1 Chris Lumens 2012-11-09 15:05:24 UTC
Can you attach /tmp/X.log from an attempt at running X to this bug report?

Comment 2 William Brown 2012-11-09 23:01:08 UTC
I have just attempted to get this for you - Remember, my screen (and all ttys) are fully black.

Doing the steps of:

ctrl + alt + f2
ifup eth0
sendmail "my email" < /tmp/X.log
sendmail "my email" < dmesg
reboot


I found nothing in my inbox. So either A) I messed up the networking, which is doubtful as I used this same connection to do the installation, or B) there is no tty2 avaliable, so I was running commands into nothing. Do you have any tips or ideas on how to get at this? 

Perhaps in the future it would be a neat idea to have an anaconda image, that when given a kernel parameter of the users email, emails them logs at various stages of the install, to make this kind of data collection easier. IE just as anaconda starts, email dmesg, when anaconda knows about Xorg and wether it starts or failed, email the Xorg log, or any exception can have it's stack trace sent also.

Comment 3 Jesse Keating 2012-11-09 23:03:14 UTC
Pass inst.sshd as a boot option and it'll enable an ssh server that you can ssh in as root (no password) and get to the shell.  That way you can get in and offload the requested logs.

Comment 4 William Brown 2012-11-09 23:47:51 UTC
Created attachment 641887 [details]
X.log from macbook pro 8,2

That did the trick.

I took the liberty of checking - It would seem the installer is using kernel 3.6.5 - According to #765954 Some of the graphics issues that are present are fixed by the upgrade to 3.6.6 . When will anaconda be updated to at least 3.6.6?

Attached x.log anyway.

Comment 5 Chris Lumens 2012-11-12 04:36:36 UTC
When the kernel is in updates and a new image is built, it should contain that version.  anaconda's got nothing to do with the version of the kernel included.  Reassigning, but it sounds like this can just be closed.

Comment 6 Josh Boyer 2012-11-12 15:13:55 UTC
Please try the Beta TC8 release and let us know if it's fixed.

Comment 7 William Brown 2012-11-13 03:04:48 UTC
This is fixed in TC8 - Thanks for the time.


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