More on PXE error

[Keith von Borstel <keithvb@www.dminfo.com>]

Franz,

I'm using a diskless system with an on-board rtl8139 NIC. I got the 
rtl8139.pxe file from http://rom-o-matic.net/.
I 'turned on' the 'boot from NIC' feature.

The boot is in several steps.
	1. BIOS goes to server and downloads the boot ROM stuff.
	2. Boot ROM stuff initializes NIC
	3. NIC tftp's startup stuff from server...

/etc/dhcpd.conf contains:
#
   host cactus {
       option option-188 "*          Welcome Cactus         *";
     hardware ethernet 00:10:DC:1F:C1:23;
     fixed-address   192.9.200.173;
     if substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
       filename    "rtl8139.pxe";
     } else if substring (option vendor-class-identifier, 0, 9) = 
"Etherboot" {
       filename "/lts/vmlinuz-2.4.18-ltsp-1";
     }}

If it had a floppy drive I'd go to http://rom-o-matic.net/ and get the 
boot disk version and try it...
...but I've successfully 'disk booted' from floppy with a Netgear FA312 
and a Winbond 86c940.

The boot is simpler than with PXE.
	1. Computer boots from floppy disk containing boot ROM image
	2. Boot ROM stuff initializes NIC
	3. NIC tftp's startup stuff from server...
This is a typical /etc/dhcpd.conf entry I use:
#
   host vivian {
       option option-188 "*          Welcome Vivian         *";
     hardware ethernet 48:54:E8:21:B4:D5;
     fixed-address   192.9.200.171;
     filename      "/lts/vmlinuz-2.4.18-ltsp-1";
   }

Hope this helps,

Keith
-- 
Keith von Borstel
Software Engineer

D-M Information Systems
2744 Del Rio Place
Davis, CA 95616
(530) 750-7137


===========================================================================
This Mail was sent to netboot mailing list by:
Keith von Borstel <keithvb@www.dminfo.com>
To get help about this list, send a mail with 'help' as the only string in
it's body to majordomo@baghira.han.de. If you have problems with this list,
send a mail to netboot-owner@baghira.han.de.