Red Hat Bugzilla – Bug 119470
XFree86/Anaconda does not configure correctly NetVista 6643 11u X40
Last modified: 2007-11-30 17:10:39 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040213
Description of problem:
I doubt if anybody will ever fix this or even care...but who am I to
say it shouldn't be recorded SOMEWHERE...
The Netvista 6643 11U X40 is an "All on one" Celeron system that IBM
manufactured back in 2000. It has an SiS 630 chipset used for video.
Typically, in order to use X on this system VESA needs to be used.
Hand configuring the Xfree86 Configuration file works, but upon first
installation when Anaconda/Xfree86 tries to autoprobe the video type
and Monitor (LCD) it correctly identifies the SiS 630...but not the
monitor (unknown). I can't be sure, but it looks like it tries to
start Xfree86...the screen is somewhat garbled or nonexistent...but
the installer continues anyhow (even though you cannot see the screen
or make it out). The solution is to run the installer in text mode.
I'm thinking that maybe X in Anaconda is starting VESA but has got the
horizontal and vertical frequencies wrong.
Not sure if there is a fix even possible for this...but in case
anybody else needs to install Fedora on this little system the bug
will be here!
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to install Fedora core 2 in default graphical mode
Actual Results: The installer actually thinks it's successfully
started X, but the display is unreadable
Expected Results: I should be able to see the screen
Workaround - run X in text mode....then hand hack the XFree86 Config
file after the fact to use Vesa with a conservative set of values for
Horizontal and Vertical Frequencies
Created attachment 98978 [details]
Technical Information Manual For Netvista X40 type 6643
This will probably dissapear someday off of the IBM website...but here is the
manual for this system incase anybody needs to see the specs for this system to
fix the bug
Ooops...the Workaround should say Run the installer in text
mode....not run "X" in text mode :)