Hi Mouncef, we had the same Problem with SLES8 and HP Proliants. Old systems worked with an old boot kernel. After purchasing a new Proliant some weeks ago the system wasn't able to get a DHCP IP after PXE boot. After changing the boot kernel to the SLES8 SP3 kernel in the tftp directory pxe boot and autoinstallation works fine. Just try to use the boot kernel from the 9.0 CD for installation. Regards Hartmut Dunker Mouncef_Belcaid@b lm.gov An: suse-autoinstall@suse.com Kopie: 18.05.04 21:22 Thema: [suse-autoinstall] Broadcom NICs [FinanzIT: Viruscheck] Hi everyone, I have used Autoyast successfully to install SuSE 8.2 Pro on multiple IBM Blade servers. Each one of these servers comes with two Broadcom gigabit cards, I used the bcm5700 module which worked fine during and after the installation. We purchased more of these Blades, which come with the next generation Broadcom cards, they work fine after a manual installation is complete. The problem is during the automated installation. After the installation kernel loads, the card tries to get a DHCP IP from the NFS server (before YAST starts), that's when it hangs. I checked the DHCP server logs and it doesn't seem like the request is even reaching the server. I tried loading 9.0 on one of the Blade servers, and it worked using Autoyast. But I have to stick with SuSE 8.2 for now. Is there an updated version of the SuSE 8.2 Pro loader files (initrd, linux, memtest...)? Thanks for your time, Mouncef -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com