Created attachment 453938 [details] Smolt Profile Description of problem: X blanks screen at launch when using the intel graphics drivers. Version-Release number of selected component (if applicable): xorg-x11-drv-intel-2.11.0-5.fc13.x86_64 xorg-x11-server-Xorg-1.8.2-4.fc13.x86_64 How reproducible: Consistently. Steps to Reproduce: 1. Use the intel graphics drivers. 2. Boot into X. 3. Actual results: The screen goes blank. You cannot switch to other terminals. Other than the graphics, there is activity (hard drive still loading, etc...) Expected results: The screen should display properly. Additional info: I have tried this with and without nomodeset on both fedora 13 and a fedora 14 beta live CD. I have attached smolt and Xorg.0.log.
Created attachment 453939 [details] Xorg.0.log
Created attachment 453961 [details] Oldest Xorg log I have
$ lspci 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05) 00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05) 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05) 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) 02:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 05) ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 05) ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 05) ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 05) ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 05) ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 05)
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), and * output of the dmesg command to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
*** Bug 643735 has been marked as a duplicate of this bug. ***
According to bug 643735, this is still reproduceable on F14. Reporter, if you don't care about F13 anymore (or if you just don't have any F13 system, where you could confirm a possible fix), please provide information required in the comment 4 just for F14, otherwise please provide both. Thank you
Created attachment 455361 [details] Fedora 13 xorg.conf
Created attachment 455362 [details] Fedora 13 dmesg output
After discussing this with Xorg developers, I am afraid there is not much better to advise then "Try the latest kernel/xorg-x11-drv-intel packages as they are built". Xorg developers are aware of a problematic Arrandale chips (it's actually apparently a hardware issue, not software) and trying to do their best. Please, let us know, if you observe any improvements.
I tried xorg-x11-drv-intel-2.12.0-5.fc13. No difference.
Some updates: After re-installing Fedora 14, and removing nomodeset from the boot arguments, the intel graphics driver is being used and appears to be functional using compiz. However, the screen is blank between the grub menu and the X login screen.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.