|
From: Marty C. <md...@et...> - 2005-06-17 18:40:06
|
On Jun 17, 2005, at 2:10 PM, Michael Brown wrote: > On Fri, 17 Jun 2005, Krzysztof Lichota wrote: >>> Are you sure you're using Etherboot? We don't have any code that >>> supports RPL, nor do we use NDIS drivers. Is it possible that you're >>> using a different product? >> I am loading Etherboot ROM using RPL. > Out of curiosity, how? We have no rplprefix.S; does RPL allow you to > download and execute a PCI/ISA option ROM image (.rom), or are you > using a > ..dsk image with floppy drive emulation, etc.? > Michael This sounded familiar somehow, so I did some searching and found the message below. There are probably other ways to do it, but I remember thinking this was a neat hack. Marty > From: val...@no... > Subject: Re: [Etherboot-users] load an etherboot-rom by ethernet > Date: August 17, 2004 12:21:10 PM EDT > To: eth...@li... > Cc: da...@ix... > > Hi, > > At Mon, Aug 16, 2004 at 02:08:27PM -0700, Mike Castle wrote: >> Out of curiosity, how are you serving up RPL? I have an machine that >> supports RPL but not PXE, and if I could get an RPL -> etherboot >> solution >> going, that would be way cool. :-> > > Hee, I got it to work. Here's how. > > - get rpld http://gimel.esc.cam.ac.uk/james/rpld/index.html version > 1.7 (1.8 > crashes for me) > - make; make > - set rpld.conf to the following: > HOST { > ethernet = 00:de:ad:be:ef:01; > FILE { > path="/tmp/rom.iso"; > load=0x1000; > }; > execute=0x1000; > }; > > start rpld with ./rpld -C ./rpld.conf -f (or something alike) > > Then download the http://rom-o-matic.net/5.3.8/ rom image. For some > reason, > the "binary rom image" wouldn't work here (it started but hung when > detecting the ethernet card), even if I chose "execute=0x1006" (as > someone > suggested on this list). The 5.2.5 would work with a ROM image, but > those > don't support PXEboot which is what I want, so I went for 5.3.8 and > chose > the "isolinux without floppy" option. > > That worked nicely. The 5.3.8 rom would load our pxelinux stuff and in > turn > a kernel would load. > > The only thing I'm fighting now is that, for some obscure reason, the > NIC of > the RPL server needs to be in promiscuous mode. This is probably due to > protocol incompatibilities in IBM/ Novell implementation or so. > Communications now go like this: > RPLclient->broadcast: hello, anyone there? > > RPLserver->client: hello, I'm here to serve you > > RPLclient->some mac address that I don't recognize: well, send me the > files > RPLclient->some mac address that I don't recognize: well, send me the > files > RPLclient->some mac address that I don't recognize: well, send me the > files > RPLclient->some mac address that I don't recognize: well, send me the > files > [ad nauseam] > > Why it would have this Mac address is a mistery to me, but a hacking > workaround is to use promisc in the mean time. > > We still have some issues with the kernel that's being loaded: the > first one > we tried kept crashing and rebooting after the "unloading NIC" > message. This > might be due to a wrong processor or kernel size or other unknown > things. > We chose another, simpler kernel (the generic Debian boot kernel) and > this > made our first RPLbooted workstation (sorta) functioning this > afternoon. > > Thanks everyone so far! > > V. > -- > http://www.openoffice.nl/ Open Office - Linux Office Solutions > Valentijn Sessink val...@no... -- Try: http://rom-o-matic.net/ to make Etherboot images instantly. Name: Marty Connor US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA Voice: (617) 491-6935; Fax: (617) 491-7046 Email: md...@et... Web: http://www.etherboot.org/ |
