Red Hat Bugzilla – Bug 135321
Text display distorted when unable to start X
Last modified: 2007-11-30 17:10:51 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3)
Description of problem:
Text screen is distorted when X-based installer failed to initialize.
VMWare 3.2 is hosting FC3 for testing. Same VMWare version hosts RHEL
2.1, 3.0, (and other Linux distros) with no issues.
I got past the "CD Found" dialog. anaconda began startup, and
eventually failed, despite correctly identifying the video card.
, Unable to Start X
X was unable to start on your machine.
Would you like to start VNC to connect
to this computer from another computer
and perform a graphical install or
continue with a text mode install?
use text mode Start VNC
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Insert CD #1
2. Power on VMWare virtual machine
3. View error
Actual Results: See screen shot
Expected Results: A neater screen
Created attachment 105027 [details]
anaconda failure message
This looks fine for me here... are you booting with 'nofb' or similar?
No special boot parameters are being used in any case (FC3T1 or RHEL).
When you say it looks fine - does that mean you don't get the error?
The nofb parameter indicates to me that you are getting a graphical
display, which is not the issue - the error reporting mechanism is
working correctly. The issue being reported is that the error is
munged and it is really unclear what the default answer is as the
highlighting is in the wrong place. Perhaps this is a UTF-8
Also note that this page's format is not consistent with the rest of
the text installer, which works perfectly. Something is different in
the initial error reporting part of anaconda than the rest of the
As test1 is somewhat old, could you retest on FC3T3 please. I just
tried to replicate off a more recent tree with VMwareWorkstation
4.5.2, and I can't replicate as X starts. I'll dig up an older tree
but I'd be gratefull if you could test FC3T3.
Problem does not exist with FC3T3. Closing record.