Hi, This seems to be a general problem and has nothing with autoyast. Try installation manually first and see if it works for you. It is possible also to set the dhcp timeout on the prompt and you also need to enter the installation source, i.e. install=nfs://.... Anas David Corlette wrote:
Hello all,
I'm having trouble getting autoinstall to work with SuSE 9.1. I'm not sure if I'm doing something wrong or if something's broken. Here are the basics:
- I've downloaded a complete copy of the 9.1 distribution, put it on an NFS server (10.0.0.57) and exported it as /home/suse. - I've created a customized control file using YaST2-autoinstall (with manual customization) and placed it in /home/suse on the NFS server. - I've cut a CD using "boot.iso" from the distribution, with no customization; I'm just planning to manually enter the correct autoyast command-line. - I boot off the CD, interrupt the timer, and then put "autoyast=nfs://10.0.0.57/home/suse/arpmin.xml" in the command-line options line. - The system starts to attempt the autoinstall, then fails saying it can't contact the install server. Log attached below, please note comments following:
Log from installer: ---trim--- Looking for network server.. Ok, that didn't work; see if we can activate another network device... insmod /modules/mii.ko insmod /modules/e100.ko Ok, that seems to have worked. :-) Looking for a network server again... Trying to activate eth0 Setting up localhost...done Sending DHCP request to eth0... no/incomplete answer. Ok, that didn't work;see if we can activate another network device... No further network carcds found giving up. hostname: 10.0.0.200 netmaks: 255.255.255.0 broadcast: 10.0.0.255 gateway: 10.0.0.1 server: 10.0.0.10 nameserver: 10.0.0.8 Looking for a network server... Trying to activate eth0 Setting up locathost...done **** dhcpcd: already running **** dhcpcd: if not then delete /var/run/dhcpd-eth0.pid file Sending DHCP request to eth0... no/incomplete answer. Ok that didn't work; see if we can activate another network device... No further network cards found; giving up.. Automatic setup not possible. ---end---
Does anyone else find it odd that the script appears to give up on DHCP just before the machine apparently gets a full set of parameters from DHCP? Perhaps the timeout is ridiculously low?
In any case, if anyone has any idea how to fix this, I would really appreciate it. Thanks! Dave C
--------------------------------------------------------- David Corlette mailto:corlette@huarp.harvard.edu (617)495-5922 http://www.arp.harvard.edu