Created attachment 355123 [details] Screenshot of messed up screen Description of problem: Trying to boot with modesetting enabled results in a static vertically striped screen with white horizontal lines at each quarter of the display that looks like an LCD initialization problem. The machine seems to continue booting, but the display is unusable. Booting with a CRT attached works, however the LCD remains black, no backlight. Trying to enable it with xrandr doesn't work. Also there seems to be pixmap corruption issues. LCD works just fine with modesetting disabled. Toshiba Satellite 1100, Intel 830M chipset: http://www.smolts.org/client/show/pub_cfc61f77-d39b-475c-ab3d-d5b8c566d8d3 Version-Release number of selected component (if applicable): kernel-2.6.29.5-191.fc11.i586 kernel-2.6.29.6-213.fc11.i586 xorg-x11-drv-intel-2.7.0-7.fc11.i586 How reproducible: 100%
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 attach your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 357485 [details] Xorg log, no modesetting
Created attachment 357486 [details] dmesg, no modesetting
Well, there they are without modesetting. Getting them with modesetting will be a bit harder. I suppose I could do it with an external monitor attached?
Yes, or boot into runlevel 3. Create this /etc/X11/xorg.conf Section "ServerFlags" Option "DontZap" "false" EndSection and then (as normal user) run startx 2>&1|tee /tmp/Xorg.log Wait couple of seconds and kill Xserver with Ctrl+Alt+Backspace (you can do even blindly). Then attach both /var/log/Xorg.0.log and /tmp/Xorg.log to this bug report as separated uncompressed attachments. Thank you in advance
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.]
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.
For some reason I am getting auto-nagged about needinfo. The laptop in question was recycled years ago. So this bug is pretty moot.