Red Hat Bugzilla – Bug 212861
X display config appears to be faulty on second boot
Last modified: 2008-08-02 19:40:33 EDT
Description of problem:
Second boot after installation fails to bring up any graphical interface... the
character terms are still there.
Version-Release number of selected component (if applicable):
Probably hard to reproduce. It appears that the /etc/X11/xorg.conf that says it
is created by pyxf86config is messed up.
Steps to Reproduce:
1. Install system
2. Initial boot
window manager is not running on second boot.
I would have expected the window manager to run on each boot in runmode 5
I can attach the two xorg.conf files... maybe you can make sense of them.
From the casual observer, theough, it appears that the default file does not
have any "modes" like 1600X1200...
Created attachment 139675 [details]
This is the initial xorg.conf that I found on the system.
Created attachment 139676 [details]
This is the current xorg.conf that seems to work.
I resolved the issue by disabling the smart card driver (pcscd) in
system-config-services (I don't have any smart card devices attached so no
problem for me). As first boot after install was ok - didn't think to look at
How on earth would pcscd cause this? Can you attach X server logs from
attempting to start X with and without pcscd running?
I have exactly the same problem. After the reboot, when X starts you can see it
for an instant before the screen goes blank and the monitor eventually complains
"Scan out of range."
Abit motherboard (Celeron 486/66)
Matrox Millennium II AGP graphics
Sony Trinitron Multiscan E400 monitor
Created attachment 140484 [details]
config file created manually with menu system.
I am attaching yet another xorg.conf file created on the subject system by yet
another method. This time, I went through the admin menu system on the display
and selected the display vendor and model. Interesting in that the xorg.conf
file now carries information on horizontal and vertical refresh that wasn't in
either of the prior uploaded config files.
Just a note. Running through the admin menu system for the display seems to
have produced a config file that will work correctly through multiple reboots.
I did have problems with the config file that was uploaded (ID = 139676) later
on. That is why I tried using the menu system. This appears to be holding on OK.
Hopefully, a diff between the config files will show something lacking from one
to the other, and lead somebody to what is preventing a fully fleshed out config
(In reply to comment #8)
> Just a note. Running through the admin menu system for the display seems to
> have produced a config file that will work correctly through multiple reboots.
> I did have problems with the config file that was uploaded (ID = 139676) later
> on. That is why I tried using the menu system. This appears to be holding on OK.
> Hopefully, a diff between the config files will show something lacking from one
> to the other, and lead somebody to what is preventing a fully fleshed out config
It might, but you've only attached one config file, and no log files. Please
attach the config and log files from both a successful and unsuccessful startup.
Mass closure: This bug has been in NEEDINFO for over six weeks with no
additional information provided, and is therefore being closed. If this bug is
still an issue for you, please supply the requested information, and reopen the bug.