NFS kickstart fails with e1000.ko drivers
Joe Robertson
jrobertson at convera.com
Fri May 7 23:47:54 UTC 2004
> -----Original Message-----
> From: ccollier at viawest.net [mailto:ccollier at viawest.net]
> Sent: Friday, May 07, 2004 3:06 PM
> To: Discussion list about Kickstart
> Subject: RE: NFS kickstart fails with e1000.ko drivers
>
>
> On Fri, 7 May 2004, Joe Robertson wrote:
> --snip--
> >
> > Cody - can you also provide a sample of what parameters you use for
> > ksdevice etc
> > for your http setup? I haven't set up an http server
> for this yet
> > but
> > someone else told me he gave up on trying to use NFS
> and switched to
> > HTTP.
>
> [somehost]$cat
> /tftpboot/linux-install/pxelinux.cfg/netboot-rhel3_es-basic
> default linux
> label linux
> kernel vmlinuz-rhel3_es
> append initrd=initrd-rhel3_es.img vnc ksdevice=eth0
> ks=http://123.456.789.123/somepath/here/vwkickstart.py
>
> The images (vmlinuz-rhel3_es/initrd-rhel3_es.img) are just
> renamed and
> come from rhel3es-distribution/images/pxeboot/. I've found
> making the
> installation tree and the kickstart config file available via
> http to work
> very well.
>
> cody
>
I setup a configuration with the kickstart file on
an http server. I created a label with the entries
to match your example. When I tried to run, it failed
to retrieve the file (ALT-F3 console messages follow):
...
* load module set done
* getting kickstart file
* sending dhcp request through device eth0
* waiting for link...
* 0 seconds.
* doing kickstart... setting it up
* ks location http://10.0.125.106/pxe/fc2-3/ks/ks-min.cfg
* transferring http://10.0.125.106//./pxe/fc2-3/ks/ks-min.cfg to a fd
* failed to retrieve http://10.0.125.106///pxe/fc2-3/ks/ks-min.cfg
* trying to mount CD device hdc
<ALT-F3 console output stops here>
I can open a browser and enter the url specified as
ks location above and it will display the contents of the
kickstart configuration file.
This sounds like the same issue - the NIC driver... or anaconda...
I had another instance of this when I tried to use pxe to boot into
a diskless environment - the dhcp lease was failing. The /linuxrc
in the ramdisk was a script so I had it try again to get a lease
if the first try failed. It always succeeded.
This whole thing sounds like a timing issue and something is
simply not giving the driver enough time before it gives up
and reports a failure.
Joe
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickst> art-list
>
More information about the Kickstart-list
mailing list