Created attachment 417507 [details] dmesg Description of problem: System startup failes when starting X server during boot. Black screen appears just after grub screen. System is up but X cannot start. I worked fine with F11 & F12, but not with F13. Version-Release number of selected component (if applicable): xorg-x11-drv-intel-2.11.0-4.fc13.x86_64 How reproducible: Just boot without nomodeset option on Dell E6500 with high-res Intel video-card. Actual results: Expected results: Additional info: #lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03) 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03) 00:1f.2 RAID bus controller: Intel Corporation Mobile 82801 SATA RAID Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03) 0c:00.0 Network controller: Intel Corporation WiFi Link 5100
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), * X server log file (/var/log/Xorg.*.log), and * system log (/var/log/messages), 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.
Created attachment 417819 [details] /var/log/messages Contains two startups : with and without nomodeset kernel option
Created attachment 417820 [details] /etc/X11/xorg.conf
Created attachment 417821 [details] /var/log/Xorg.0.log I cant have console access if the boot options dont contain "nomodeset", so Xorg.*.log using nomodeset option
(In reply to comment #4) > I cant have console access if the boot options dont contain "nomodeset", so > Xorg.*.log using nomodeset option You can let startup fail and then reboot in the text mode (with adding "3" on the kernel command line) and collect /var/log/Xorg.0.log from the failed attempt.
Created attachment 418190 [details] /var/log/Xorg.0.log Here is the expected file.
I have exactly the same issue -- same graphics hardware, also running 64-bit. Using drm.debug=0x04 works for me too. I'll attach my Xorg.0.log shortly
Created attachment 421493 [details] My Xorg.0.log
Update: installing xorg-x11-drv-intel-2.9.1-1.fc12.x86_64 and passing "nomodeset" to the kernel from grub has at least got me working X. It's not running in my full native resolution -- 1600x1200 instead of 1920x1200 -- but at least it's there. So it seems to be something in the kernel mode setting path ... ?
Flashing BIOS A22 solves this issue for me (Latitude E6500, 1929x1200). However, booting F13 with F12 kernel (2.6.32.14-127.fc12.x86_64) worked with BIOS A19.
Update : I flashed to BIOS A22 and tested without nomodeset kernel option .... Result : I can see the plymouth graphical theme, but after the black screen is back :-(
Bug is fixed with Fedora 14 (xorg-x11-drv-intel-2.12.0-6.fc14.1.x86_64)
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.