Red Hat Bugzilla – Bug 77280
Xserver locks up when booting computer
Last modified: 2007-04-18 12:48:09 EDT
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description of problem: The Xserver is set to start on boot. When the Xserver starts, the computer locks up and the screen is just a big jumble of colors. I am using a ATI Radeon 7200 PCI version. But, when I install it only probes the Intel 810 chipset which is disabled in my BIOS, so I go through the list and choose my Radeon. I've installed it over and over again and it repeatedly does the same. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Turn on computer 2. The last line on the screen is "Running firstboot:" 3. Freeze up, and jumble of colors. Actual Results: Lock up, not even the caps lock light on the keyboard will come when the button is pressed. Expected Results: The computer should start up and show me a login screen. Additional info: I did try the interactive start up once and hit NO for everything, and it said that the Xserver failed to load. And said that there was a fatal error loading font "fixed".
Please attach your X server log file /var/log/XFree86.0.log, and your X config file, as well as your /var/log/messages from after a crash. Also attach the output of the following commands: lspci -vn uname -a
Created attachment 83784 [details] /var/log/XFree.86.0.log
Created attachment 83785 [details] /var/log/messages
Created attachment 83786 [details] output from command lspci -vn
Created attachment 83787 [details] output from command uname -a
The log file you attached contains garbage. Please attach a new one. Note that if you disable onboard video and have a problem, or if your machine does not allow you to disable onboard video, then it is a broken hardware issue. It may be able to be worked around somehow at somepoint in software but it would not be considered a bug, but rather a "fix my broken hardware with a software workaround" enhancement request. Anyway, please attach the file so we can investigate.
Please respond if this issue is still present, and you are still interested in the issue being tracked and resolved.
Closing bug due to insufficient information, and over a year of inactivity. If this problem still persists in Fedora Core 2 test2 or later, or Red Hat Enterprise Linux 3, feel free to file a new bug report and attach all of the information requested above in individual uncompressed file attachments, and confirm they're not corrupted upon upload. Closing as 'NOTABUG'.