Steffen, That didn't work either. The log on console 3 shows the following: got info from the cmdline hostname: 169.10.248.66 netmask: 255.255.255.0 broadcast: 169.10.248.255 gateway: 169.10.248.1 server: 169.10.63.215 (no ip) nameserver: Looking for a network server... Ok that didn't work; see if we can activate another network device insmod /modules/tg3.ko Ok that seems to have worked trying to activate eth0 settting up localhost.... done eth0 activated http error: connect: No route to host When I do the dhcp test I get .... eth0 activated going for automatic install And it works. Any ideas? Thanks, David Bellis Steffen Winterfeldt <snwint@suse.de> To suse-autoinstall@suse.com 03/30/2006 03:12 cc AM Subject Re: [suse-autoinstall] Cannot disable DHCP On Wed, 29 Mar 2006, dbellis@mmm.com wrote:
So I have gotten a little further now.... but still no luck.....
I am using the following for my isolinux.cfg entry
# Autoyast Installation label autoyast kernel linux append initrd=initrd ramdisk_size=65536 splash=silent showopts
netsetup=1
install=http://169.10.63.215/x86sp3/ autoyast=http://169.10.63.215 /xml/server.xml
The netsetup=1 ends up prompting for IP, netmask, default gateway, and nameserver...... but then the install fails. It seems to still be trying to use DHCP. If I use DHCP it will work. Even if I use the exact same IP, netmask, gw, ns that I was trying to use in the static config.
Something like hostip=1.2.3.4/24 gateway=5.6.7.8 install=... should work. If not, have a look at the log on console 3. There is definitely no 'fallback' to use dhcp if static network config fails. Steffen -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com