Kickstart installation fails with an exception in Traceback: 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 #reboot #Install Red Hat Linux instead of upgrade install #Use HTTP installation media url --url http://209.10.98.88/redhat-8.0-installation/cdrom/ #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 192.168.3.77 --netmask 255.255.255.0 --gateway 192.168.3.1 --nameserver 192.168.3.1 #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 @Editors @Server Configuration Tools @Web Server @Windows File Server @Development Tools @Administration Tools @System Tools
It downloads all packages (the last one is xdelta-1.1.3-7.i386.rpm intalls them and then gives the in line 694 exception.
It would really help diagnose the problem if you could attach the traceback.
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.
Created attachment 89426 [details] Anaconda dump
In addition: If I add interactive option to kickstart the intallation ends OK, no such problem arise.
If I add skipx to ks.cfg intallation finishes OK.
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 anaconda-ks.cfg. If you put a --videoram option on your xconfig line in the original ks script it might help.
Closing due to inactivity - please reopen if you have additional information to add to this report.