Red Hat Bugzilla – Bug 448325
s-c-d crashes system with "Savage Twister PN133"
Last modified: 2018-04-11 07:44:59 EDT
Description of problem:
I was trying to configure a text-mode system into a graphical system containing
a "Savage Twister PN133" chipset. I had an empty xorg.conf file, and I ran
s-c-d to detect/configure the display. I found that
1. s-c-d could not detect the graphics chipset properly (even though the
'savage' xorg driver RPM was installed
2. s-c-d could not identify the monitor resolution
3. when i selected any of the xorg drivers (including the correct one, 'savage')
and quit s-c-d, the machine locked up and required a power-cycle.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set the system to text mode (runlevel 3)
2. Delete xorg.conf
3. Run s-c-d
System crashes when s-c-d exits
After the machine is rebooted, it works OK -- now that the correct xorg driver
is recorded in xorg.conf. Successive runs of s-c-d then do not crash the system.
Anaconda evidently configures xorg.conf correctly if the system is installed as
a graphical desktop in the first place. What is that anaconda is doing that
s-c-d is not?
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) 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.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
I can't reproduce this bug. I deleted the xorg.conf file and s-c-d and xorg
worked as advertised, filling in the driver as 'savage' and failing to crash, of
course. Unfortunately I don't have the previous xorg.conf file, which may have
had an incompatible driver section in it.
Sorry for the trouble.