Description of problem: Changing the screen resolution with gnome-display-properties cause the screen to go white. Killing the server with ctrl-alt-backspace has no effect. Switching to a standard VT also does not remedy the problem. The only way to restore the screen is to (blindly) switch to a VT and hit ctrl-alt-delete. After reboot the screen was restored. I tried changing my resolution from a higher one to both 1024x768 60Hz and 1280x1024 60Hz. Both of these resolution changes manifest the problem. Version-Release number of selected component (if applicable): xorg-x11-drv-intel-2.6.99.902-3.fc11.i586 kernel-PAE-2.6.29.1-70.fc11.i586 This did not happen until the latest update from rawhide (4/14). I did an update on 4/13 from rawhide and all was fine. Something broke in between. How reproducible: 100% Steps to Reproduce: 1. Install F11 beta1 (32-bit) from DVD 2. Fetch latest updates from rawhide 3. Try to change resolution with gnome-display-properties Actual results: White screen which will not go away without reboot. Expected results: Normal resolution change. Additional info: System in test is a Compaq dc7100 with integrated intel 915 graphics. Monitor is a Compaq P700
Booting with the previous kernel (2.6.29.1-68) did not fix the problem.
After booting with the 2.6.29.1-54 kernel, I still had the problem, but on the subsequent reboot (back to the 2.6.29.1-70 kernel) the resolution changes were kept and the screen did not go white. I am also now able to change the resolution from 1024x768 to 1280x1024 without seeing the problem.
After a subsequent reboot, the problem has returned.
Sounds like something strange going on when the card is initialized, but - we're going to need your X log (/var/log/Xorg.0.log) and /etc/X11/xorg.conf if it exists. It would be particularly interesting to see /var/log/Xorg.0.log after the problem has manifested. Can you trigger the bug, then reboot *directly to runlevel 3* - add '3' as a kernel parameter - and take a copy of /var/log/Xorg.0.log before starting X? That should be the Xorg.0.log from before the reboot, when the problem triggered, and that's what we'd like to see. thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
no xorg.conf
Attaching the requested log file captured from a reboot to directly to init 3.
Created attachment 340029 [details] Xorg log fiel
Thanks a lot. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Retested with kernel-2.6.29.1-100 and xorg-x11-drv-intel-2.7.0-1 and problem seems resolved. I would recommend closing this bug as fixed and I can reopen if the problem returns.
sounds good to me! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers