Created attachment 704445 [details] Log file /var/log/Xorg.9.log Description of problem: Fedora 18 64bit on a HP Elitebook 8560w fails on fist boot after installation with display issues. Version-Release number of selected component (if applicable): kernel-3.7.9-205.fc18.x86_64 How reproducible: Perform clean Installation of F18 64bit DVD and select KDE Workspace. Start the system for the first time. Steps to Reproduce: 1. Install F18 64bit 2. At the first boot the screen was black and flickering. Even in single user mode the text graphics couldn't be displayed. Removing all parameters from kernel line displayed only the kernel messages and then nothing. 3. Ensure that you have configured your network during installation. 4. Log in remotely using ssh. 5. Run yum update. (1000 packages updated... wasn't supposed to be auto updated from the configured network on the installer already!?!?) 6. Reboot 7. Now the behaviour is slightly different. There is a white display and no flickering. Actual results: The installation is not usable. A perfect white screen that must be probably be the firstboot configuration is displayed. Expected results: The system should have a valid display. Additional info: I have charged this to kernel folks, since I have found old flickering reports for that series laptop due to kernel bug. Please, re-assign it appropriately. The system is accessible remotely with ssh in case you need more information. I'm attaching the xorg log.
Created attachment 704446 [details] Log file /var/log/messages
Created attachment 704447 [details] Output of dmesg command
Awkward workaround found: 1. Either wait or force system to go in standby mode by closing the lid 2. Press the power button to exit standby mode 3. The display now works fine I assume a proper workaround would be to force a vesa driver to be loaded temporary.
The issue has been resolved in the last updates of Tuesday 21st of May. The laptop was able to boot and display correctly the progressing fedora logo and the KDM login screen afterwards. Unfortunately, I don't know exactly in which layer was the problem to report the required version that resolves the issue. Maybe the bug 849347 that was fixed in xorg-x11-drv-ati-7.0.0-0.9.20121015gitbd9e2c064? However, suspend/resume was my workaround. My issue was in the initial boot of X server.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.