On 7 Mar, Achim Öhlenschläger wrote: I'm doing pxe installs of SLES8 now..
label suse81 kernel linux81 append console=ttyS0,19200n81 initrd=initrd81 ramdisk_size=65536\ ide=nodma apm=off acpi=off insmod=natsemi\ install=nfs://192.168.1.99/usr/local/dist/suse
Is that initrd81 file in /tftpboot world readable? If the network bits aren't working, try adding insmod=<module> with the suse kernel instead of building your own. My guess is your initrd for your kern didn't include all the right files that the suse installer needs to start the autoyast stuff. I had to specify the module for the dual opterons I'm using: LABEL suse kernel vmlinuz-suse append load_ramdisk=1 initrd=initrd-suse autoyast=nfs://192.168.1.1/local/mnt/SLES8/GV/ks/rs-blade.xml netdevice=eth1 insmod=bcm5700 install=nfs://192.168.1.1/local/mnt/SLES8 the insmod=bcm5700 is loading the bcm5700 driver... suse 9 detected them ok, but SLES8 didn't for some reason. Note that I'm also using pxe over eth1 on a closed, private net for the install while eth0 is plugged into the company network.. hence the netdevice argument. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Sideshow Bob: "I'll be back. You can't keep the Democrats out of the white house forever, and when they get in, I'm back on the street... with all my criminal buddies! Aaah ha ha ha!" ==> Simpsons.