Bug 826661

Summary: Macbook 3,1 monitor is broken
Product: [Fedora] Fedora Reporter: Michael Strobel <lebstrom>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: ajax, bugzilla, t.matsuu, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 17:43:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg
none
lspci -vv
none
xorg-log
none
dmesg with drm.debug=4
none
picture of the screen
none
xorg-log of a working kubuntu 12.04
none
kubuntu 12.04 dmesg with drm.debug=4 none

Description Michael Strobel 2012-05-30 17:32:12 UTC
Created attachment 587785 [details]
dmesg

Hello,

i've done a clean install of fc17 on my macbook 3,1 and it seems that the internal monitor is not recognized. My external dvi monitor is working fine while the internal does some kind of flickering. It does not show up in the gnome monitor configuration.

I'll attach dmesg / lspci -vv

Comment 1 Michael Strobel 2012-05-30 17:33:15 UTC
Created attachment 587786 [details]
lspci -vv

Comment 2 Michael Strobel 2012-05-30 17:41:17 UTC
Created attachment 587789 [details]
xorg-log

Comment 3 Adam Jackson 2012-05-30 20:01:12 UTC
Odd, the X log doesn't think you have any laptop outputs.  Can you boot with drm.debug=4 and attach dmesg from that?

Comment 4 Michael Strobel 2012-05-30 20:21:54 UTC
Created attachment 587846 [details]
dmesg with drm.debug=4

Comment 5 Michael Strobel 2012-05-30 20:28:51 UTC
Created attachment 587847 [details]
picture of the screen

Comment 6 Michael Strobel 2012-05-31 18:33:58 UTC
Created attachment 588167 [details]
xorg-log of a working kubuntu 12.04

Comment 7 Adam Jackson 2012-06-04 15:34:54 UTC
Any chance I can get drm.debug=4 dmesg from the kubuntu install?  I don't see anything in their patch set that would obviously fix this machine, so I suspect this is just a regression from 3.2.0 (in Precise) to 3.3.7 (in F17).

Comment 8 Michael Strobel 2012-06-04 17:17:37 UTC
Created attachment 589221 [details]
kubuntu 12.04 dmesg with drm.debug=4

Comment 9 Takanori MATSUURA 2012-06-13 11:37:07 UTC
According to bug 827654 comment #5, this seems to be caused by something other than xorg-x11.

Comment 10 Fedora End Of Life 2013-07-03 19:21:38 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 17'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 11 Fedora End Of Life 2013-07-31 17:44:03 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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