Bug 20539 - Got this trace when installing version 7.0J, installation fails, cannot boot
Got this trace when installing version 7.0J, installation fails, cannot boot
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
: 20509 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2000-11-08 16:22 EST by Need Real Name
Modified: 2007-04-18 12:29 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-12-04 10:46:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2000-11-08 16:22:34 EST
Traceback (innermost last):
  File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/iw/progress_gui.py", line 20, in run
    rc = self.todo.doInstall ()
  File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/todo.py", line 1664, in doInstall
    self.x.write (self.instPath + "/etc/X11")
  File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/xf86config.py", line 895, in write
    config4 = self.Version4Config ()
  File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/xf86config.py", line 1173, in Version4Config
    info["enableVariant"] = ""
NameError: info

Local variables in innermost frame:
data: {'screenModes': '\012\011Subsection "Display"\012        \011Depth       16\012                Modes       "1280x1024" "1152x864" 
"800x600" "640x480" \012\011EndSubsection\012\012\011Subsection "Display"\012        \011Depth       24\012                Modes       
"1152x864" "1024x768" "800x600" "640x480" \012\011EndSubsection\012\012\011Subsection "Display"\012        \011Depth       8\012            
    Modes       "1280x1024" "1152x864" "1024x768" "800x600" "640x480" \012\011EndSubsection\012', 'videoRam': '', 'pex5Mod': '\012\011Load 
"pex5"', 'XkbModel': 'pc101', 'monitorVert': '50 - 120', 'mouseDevice': 'psaux', 'cardVendor': 'S3 Trio3D', 'cardsOptions': '\011# no known options', 
'XkbRules': 'xfree86', 'cardBoardName': 'S3 Trio3D', 'ia64Mods': '', 'XkbLayout': 'us', 'nonSparcMods': '\012\011Load "fbdevhw"', 'defaultDepth': '', 
'XkbOptions': '', 'cardID': 'S3 Trio3D', 'emulate3': 'yes', 'enableOptions': '#', 'monitorHoriz': '30 - 69', 'enableVariant': '#', 'XkbVariant': 'nodeadkeys', 
'mouseProto': 'PS/2', 'files': '\012# The location of the RGB database.  Note, this is the name of the\012# file minus the extension (like ".txt" or 
".db").  There is normally\012# no need to change the default.\012\012    RgbPath\011"/usr/X11R6/lib/X11/rgb"\012\012# Multiple FontPath 
entries are allowed (they are concatenated together)\012# By default, Red Hat 6.0 and later now use a font server independent of\012# the X 
server to render fonts.\012\012    FontPath   "/usr/X11R6/lib/X11/fonts/TrueType"\012    FontPath   "unix/:7100"\012'}
self: <xf86config.XF86Config instance at 829c498>
maxdepth: 24
res: 640x480
test: 0
mouseProto: PS/2
emulate3: yes
modes: ['1280x1024', '1152x864', '1024x768', '800x600', '640x480']
depth: 8
	Subsection "Display"
        	Depth       16
                Modes       "1280x1024" "1152x864" "1024x768" "800x600" "640x480" 

	Subsection "Display"
        	Depth       24
                Modes       "1152x864" "1024x768" "800x600" "640x480" 

	Subsection "Display"
        	Depth       8
                Modes       "1280x1024" "1152x864" "1024x768" "800x600" "640x480" 

ToDo object:

Comment 1 Michael Fulbright 2000-11-13 14:55:52 EST
Please give us information on your system, as well as the steps required to
reproduce this problem.
Comment 2 Michael Fulbright 2000-11-13 15:00:00 EST
*** Bug 20509 has been marked as a duplicate of this bug. ***
Comment 3 Need Real Name 2000-11-13 16:13:04 EST
My server is an IBM Netfinity 3000 w Adaptec SCSI and Intel Ethernet NIC.  Initially I've installed the server type, which went well all the way, 
but than I realized that there is no desktop and gnome support at all, so I started all over again selecting workstation type instead.
It goes all the way to the end of the installation process, and then display the error message (see attached dump).  It does that every time.
Comment 4 Michael Fulbright 2000-11-15 11:20:28 EST
If you try a text mode installation does it work around this problem?

Note You need to log in before you can comment on or make changes to this bug.