Description of Problem: Using kickstart for automated install. Finds the dhcpd
address, finds the next-server, know's where to finds the directory for the <ip-
address>-kickstart file. It starts to run /sbin/loader. The last message if
you hit <alt> F3 is "nodns is 0". The install stops with a blue screen.
I set this up for RH7.2 and is working without a hitch. I took what I did
there and duplicated on the RH7.3 machine. The only real difference is the
kickstart file. I used the ksconfig gui on RH7.3 to start my ks.cfg file.
I can install RH7.3 interactively.
Here is a copy of the sysconfig.cfg on my boot floppy:
append ks initrd=initrd.img lang= devfs=nomount ramdisk_size=8192
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create boot floppy from bootnet.img
2. Edit sysconfig.cfg file to look like above
3. Boot machine you want to build
Install stops with a blue screen on the monitor
Automatically install RH7.3 on new machines
Created attachment 58104 [details]
kickstart used in automated install
Created attachment 58105 [details]
Do you have a shell on vc2?
No, I can't get vc2, only vc1, 3 & 4.
I know that Ali told you that I was having the same problem with my RH7.2
kickstart server. I am not. It is working fine. I had mixed up boot disks.
What sort of hardware is this on? Do you see the request to get the kickstart
config or is it hanging trying to mount the server with the kickstart config?
The hardware is dual-processor DELL 420 and 530 machines. I believe Tom
Callaway (tcallawa) has a 530 similar to what Pratt is using.
The more important question is what sort of behavior you're seeing as far as the
server sides -- are you seeing the nfs server get a mount request? Does the
dhcp server actually see the request for an ip?
The dhcpd server does see the request and does hand out the ip-address to the
server. I can see that in the messages file. I can ping the dhcp address with
zero packet loss. It does see the directory where I have the kickstart config
files, but it does not seem to get past that part.
If it's hanging at nodns, then it's trying to do a reverse name lookup and then
hanging -- what happens if you add 'nodns' to your kernel command line (note
that you'll need to change any references to hostnames to be IPs)
Closing due to inactivity. Please reopen if you have any new information to add
to this report.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.