Could you please try forcing loading the modules from the command line using the 'insmod' keyword, i.e.: autoyast=nfs://172.16.100.1/opt/SuSE/main.xml install=nfs://172.16.100.1/opt/SuSE insmod=<module name>
I will try if insmod=eepro100 (or insmod=eepro100.o ??) solves the problem. All modules I need seems to be in /modules. As I said before I get a message box telling me to insert modules disk3. If you press the no button you revert back to manual installation. In manual mode there is a menu selection where you can load modules manually. I tried to load the eepro100 driver and the sym53c8xx drivers that way but it failed. My theory is that after makeing the new root and chrooting linuxrc fails to find the modules on the new root. But I don't know..
If you are using the initrd from suse/images/boot/initrd then all modules should be there. Have you modifed the initrd?
No. But I modified it once and added sash (statically linked) to the initrd image and replaced linuxrc with sash: mv linuxrc linuxrc.orig ln -s bin/sash linuxrc Then I booted, got a sash prompt and verified that the initrd was correctly mounted and that all the files where there. Then I tried to run the original linuxrc file. cd / ./linuxrc.orig Linuxrc created a new root, added some new files and chrooted to that it. Then it returned to the sash prompt. OK so I run linuxrc.orig again. Then the autoinstallation started! I could see from the ethereal snoop that the install image on the installation server was mounted. Then it crashed when partitioning the disks. I didn't look closely on what the problem was but the autoinstallation started. Could be errors in my xml file. regards Jörgen