Booting client using the autoinstalldiskette fails.
I've been working for a day on this problem and need help. The Oscar-4.0 install goes well and the Oscar Wizard runs. But at Step 6, setup networking, I run into a wall. I made the Autoinstall Floppy, put it in the first client, and booted the client. The client loads the syslinux from the floppy and the systemimager splash screen shows. The kernel loads and the initrd.img loads. But ... the DHCDISCOVER trys to use the lo interface reach the head node. Ouch! Earlier in the boot messages I see that the boot disk tried to load the Intel eepro 100 driver and failed. That's reasonable because the client uses a Netgear 10/100 FA311 card and needs the natsemi driver.
I went back to the initrd.img, uncompressed it, mounted it -o loop, added the natsemi.ko module to the "my_modules" directory on the ram disk image. Then I built the new ramdisk image using the standard cramfs and gzip. Replaced the failing initrd.img on the floppy and rebooted the client....
The client booted with the same failure. It did not load the natsemi module. Using the busybox commands I confirmed that the natsemi.ko was in the clients my_modules directory. Trying "insmod my_modules/natsemi.ko" produced a string of unresolved links and the insmod fails.
How do I make a bootable floppy that will properly install the necessary Ethernet drivers?
-law
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Oscar-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-users
