Created attachment 355188 [details] Xorg.log Description of problem: No display when graphical boot starts on Fujitsu-Siemens Lifebook S6010 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Boot from Fedora 11 Live CD 2. 3. Actual results: When the display is switched from VGA text mode to graphics mode near the beginning of the boot process the display just fades to grey. If a monitor is connected to the VGA port a picture is present on the monitor. Expected results: Fedora 11 graphical boot displayed. Additional info: The live CD was installed to hard disk, updated to latest, and VSFTPD installed and configured to access the files from another machine. The Xorg.log and dmesg from this are attached. No xorg.conf was used.
Created attachment 355190 [details] dmesg
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command yum upgrade --enablerepo='*-updates-testing' Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD . Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Tried with latest nightly compose (kde-i386-20091105.16.iso). this also fails to start X. If I boot with nomodeset to runlevel 2 and run startx it fails to start and shows an error: (EE) Screen(s) found, but none have a usable configuration. In this mode I can access the Xorg.log file. It doesn't appear to detect the internal display and spends its time looking for a monitor on the VGA port.
Created attachment 367833 [details] Xorg.log for kde-i386-20091105.16 live cd
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.