Red Hat Bugzilla – Bug 70363
"no screens found": bad XF86Config (HorizSync) for Sony Multiscan 15sf
Last modified: 2005-10-31 17:00:50 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529
Description of problem:
The /etc/X11/XF86Config produced by anaconda (2nd limbo beta) interchanged the
HorizSync and VertRefresh figures for manually-specified Sony Multiscan 15sf
monitor, so 'startx' failed with "no screens found" because no Mode Lines matched.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Fresh install 2nd limbo beta, Personal Workstation option.
2. During configuration for X11, manually choose Sony Multiscan 15sf monitor
(Display card is generic Cirrus Logic GD543x with 1MB RAM and no DDC support.)
3. Accept 800x600@16 bits, but change default to text mode login.
Actual Results: firstboot service fails because "no screens found". [I
specified text login, but firstboot tries X11 anyway.] User-level 'startx'
fails because "no screens found".
A copy of /etc/X11/XF86Config is attached. These lines are wrong:
VendorName "Monitor Vendor"
ModelName "Monitor Model"
The HorizSync and VertRefresh numbers have been interchanged.
Expected Results: The corrected entries in the Monitor section are:
ModelName "Multiscan 15sf"
How could this go wrong? RHL 7.3 had the correct figures for HSync and VRefresh.
If this is some kind of deliberate "coverage test" for the beta (to see if
anybody tries it, notices, and reports), then I consider it to be an extremely
poor choice. You _can_ fry hardware this way!
Created attachment 68065 [details]
actual bad /etc/X11/XF86Config produced by anaconda
Created attachment 68066 [details]
good XF86Config-4 from install of RHL 7.3
Created attachment 68067 [details]
/var/log/XFree86.*.log with "no screens found"
Created attachment 68068 [details]
/var/log/XFree86.*.log after correcting monitor freqs
Created attachment 68069 [details]
output from user-level 'startx' under bad XF86Config
Created attachment 68070 [details]
output of user-level 'startx' with good XF86Config
Boot for install was "linux text" because only 32MB RAM. [Package Installation
took 3hr 14min for 531 packages/1770MB. From 'startx' to quiescent Gnome
desktop takes 15 minutes. RestInPeace, 32MB configurations;
LinuxTerminalServerProject here we come!]
It's a transcription error in building /root/anaconda-ks.cfg, which contains:
xconfig --card "Cirrus Logic GD543x" --videoram 1024 --hsync 50.0-120.0 --vsync
31.0-64.0 --resolution 800x600 --depth 16 --defaultdesktop gnome
Please add the Monitor VendorName and Monitor ModelName to the description.
They really do help documentation and troubleshooting.
I have installed Limbo beta 2 and manually picked the Multisync 15sf and the
anaconda-ks.cfg and /etc/X11/XF86Config files both had the correct values.
I'm a bit confused how you ended up in the state you ended up in. Could you
please try it again and verify?
OK, I'm willing to try the install again.
But it's a 3.5hour process (only 32MB RAM), so if there's anything particular to
look for, please tell me by 1700 EDT today.
It's reproducible. I re-ran the complete initial install of 2nd limbo beta, and
both /root/anaconda-ks.cfg and /etc/X11/XF86Config have the hsync and vsync
ranges interchanged: claiming a horiz freq of 50.0-120.0 [KHz], and a vert freq
of 31.0-64.0 [Hz]. It should be horiz 31.0-64.0 [KHz], and vert 50-120 [Hz].
Initial boot from install floppy was "linux text". Probe during boot messages
reported video card "Cirrus Logic GD543x" [which is correct] and monitor "Unable
to probe" [which is expected because there is no DDC support on the card].
Anaconda detected low RAM [32MB] and "switched to text mode" even though that's
what I asked for in the first place.
I chose Personal Workstation. After 3.5 hours, Package Installation finally
finished. I said No to the boot disk. Then:
Video Card Configuration
Video Card: Cirrus Logic GD543x
Video RAM: 1024
which is correct, and I said OK.
Monitor: Unprobed Monitor
HSync Rate: 31.5-48.5
VSync Rate: 50-70
Here I hit <Enter> to Change the Monitor. Nothing happened within 1 second, so
I hit <Tab>. Then I waited about 4 or 5 more seconds, and the list of monitors
appeared [cpu is 90MHz PentiumPlain]. I held down <PageDown> to get to the Sony
region, then hit <up-arrow> a few times to go back to Sony Mulitscan 15sf, and
selected it. The screen now said:
Monitor: Sony Multiscan 15sf
HSync Rate: 31.0-64.0
VSync Rate: 50.0-120.0
which is [would be] correct. I OK'd that. Then:
Color Depth: Hi Color (16 bit)
Default Login: (*)Graphical ( )Text
I changed to Text. Installation soon finished.
At 1st boot after install, I booted to single user mode by editing the kernel
command line in GRUB to append " single". I looked at /boot/anaconda-ks.cfg and
at /etc/X11/XF86Config using "cat" and "vi". Both files were incorrect (horiz
and vert ranges were interchanged), just like the first time I did the complete
Found it (at least, narrowed considerably). Using a spare 2.5GB partition on a
new modern fast machine (10 minutes for Package Install), with ATI Rage 128 card
with 32MB [card supports DDC, I think], same Sony Multiscan 15sf monitor
[monitor does not have DDC: "unable to probe" monitor type]:
If I boot directly from CD-ROM and use a Graphical install of Personal
Workstation, and Change monitor type to Sony Multiscan 15sf, then the
frequencies are correct in each of the install display, ananconda-ks.cfg, and
If I boot from a floppy with boot.img, and enter "linux text", and do a text
mode install of Personal Workstation, and Change monitor type to Sony Multiscan
15sf, then the install display [character based 'newt', I guess?] is correct,
but the anaconda-ks.cfg and XF86Config are both wrong (numerical ranges of horiz
and vert have been swapped).
So it's something about text mode install, possibly even floppy boot.
Thanks - it was a typo in the text mode installer.
I've fixed it.
I appreciate you looking into this further!
fix verified in Phoebe public beta 2