Created attachment 494563 [details] checkerboard pattern Description of problem: Attempted to run Fedora 15 Beta 64bit Live KDE CDrom, and Xorg screen appears to have crashed. Everything appears okay up to and including the screen showing the 'f' in the center of the screen, but after that, the screen shows a checkerboard pattern, then eventually goes black. Pressing the power button brings back the screen showing the 'f' and eventually the computer shuts down okay. Version-Release number of selected component (if applicable): Fedora-15-Beta-x86_64-Live-KDE.iso released on 04-19-2011 as seen on Distrowatch How reproducible: Load CDrom and run from CDrom. Repeatable problem. Steps to Reproduce: 1. Load CDrom 2. Power-up computer 3. Wait for KDE screen to eventually appear.... but it doesn't. Actual results: Checkerboard screen pattern after the splashscreen showing 'f' logo Expected results: Expected a KDE screen Additional info:
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) * output of the dmesg command, 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.
Do you have another choice of options? Tried adding drm.debug=0x04 to Basic bootup, but got a different checkerboard pattern. Tried also for the 2nd Basic (with basic video) and that one simply came up as blackscreen after the blue bars eventually reached the Fedora 15 on the bottom of the screen. Is there a way to get a basic login prompt or something?
(In reply to comment #2) > Do you have another choice of options? I am sorry, this is most likely a duplicate. *** This bug has been marked as a duplicate of bug 698237 ***