Bug 81948 - kickstart installation fails
kickstart installation fails
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-01-15 12:34 EST by Need Real Name
Modified: 2007-04-18 12:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-27 12:08:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Anaconda dump (84.42 KB, text/plain)
2003-01-17 15:14 EST, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2003-01-15 12:34:38 EST
Kickstart installation fails
with an exception in 

File /usr/bin/anaconda, line 694 in ?
intf.run (id., dispatch, configFileData) 

kickstart is generated using redhat-config-kickstart

#Generated by Kickstart Configurator

#System language
lang en_US

#Language modules to install
langsupport en_US

#System keyboard
keyboard us

#System mouse
mouse genericps/2

#System timezone
timezone --utc America/New_York

#Root password
rootpw --iscrypted $1$2JJŒS8xì$UZgMDUMYLroFBy4y0v2Aa/

#Reboot after installation

#Install Red Hat Linux instead of upgrade

#Use HTTP installation media
url --url

#System bootloader configuration
bootloader --location=mbr --append nousb 

#Clear the Master Boot Record
zerombr yes

#Clear all partitions from the disk
clearpart --all --initlabel 

#Disk partitioning information
partition /boot --size 20 --fstype ext3
partition swap --recommended
partition / --size 1200  --fstype ext3
partition /usr --size 3200 --fstype ext3
partition /var --size 2200 --fstype ext3
partition /home --size 1000 --grow --fstype ext3

#Use static networking
network --bootproto static  --ip  --netmask 
--gateway  --nameserver 

#System authorization information
auth  --useshadow  --enablemd5 

#Firewall configuration
firewall --high --ssh --smtp 

#XWindows configuration information
#Probe for video card
#Probe for monitor
xconfig  --depth 8 --resolution 640x480 --defaultdesktop=GNOME

%packages --resolvedeps
@GNOME Desktop Environment
@Server Configuration Tools
@Web Server
@Windows File Server
@Development Tools
@Administration Tools
@System Tools
Comment 1 Need Real Name 2003-01-15 12:37:01 EST
It downloads all packages (the last one is
intalls them and then gives the in line 694 exception.
Comment 2 Michael Fulbright 2003-01-16 11:22:09 EST
It would really help diagnose the problem if you could attach the traceback.
Comment 3 Need Real Name 2003-01-16 11:26:56 EST
I will try to get a trace.
This is not easy because I do not have a physical access to the computer.
I will try to get in in few days.
Comment 4 Need Real Name 2003-01-17 15:14:03 EST
Created attachment 89426 [details]
Anaconda dump
Comment 5 Need Real Name 2003-01-17 15:16:01 EST
In addition:
If I add 


option to kickstart the intallation ends OK,
no such problem arise.
Comment 6 Need Real Name 2003-01-18 16:40:01 EST
If I add


to ks.cfg intallation finishes OK.
Comment 7 Michael Fulbright 2003-01-30 16:13:53 EST
I fixed this internally. What was happening was we could not determine the video
ram for this chipset, and this was causing trouble when writing out the

If you put a --videoram option on your xconfig line in the original ks script it
might help.
Comment 8 Michael Fulbright 2003-02-27 12:08:42 EST
Closing due to inactivity - please reopen if you have additional information to
add to this report.

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