We've had some luck with IBM RPL using rpld with some DM9102 onboard network
workstations. We had to make the rpld.conf "load=" address 0xf000 and
the "execute=" address 0xf106 on most and 0xf006 on others. I'm not sure
why, it was mostly trial and error. Before messing with the load and
execute addresses the workstations would stop inside the etherboot program;
at the user input section for pressing N for network or L for local, etc.
rpld talks about a DM9102 fix program to run but we've not seen any change
with or without it running.
One rpld.conf line looks like this:
HOST { ethernet=00:30:21:00:65:BE; FILE {
path="/tftpboot/rplboot/dm9102.lzrom"; load=0xf000; }; execute=0xf106; };
The dm9102.lzrom was from the Etherboot project. Hope this helps.
James
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "Liam Marshall" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, June 15, 2004 7:03 AM
Subject: Re: [Ltsp-discuss] LTSP Wizard
> On Mon, 14 Jun 2004, Liam Marshall wrote:
>
> > and some of the nics don't have pxe as an option, even though they are
on
> > board nics. Only RPL-Rom, which fails to connect to the terminal
server.
> > I assume there is a config file somewhere to tell the terminal server to
> > work with both PXE and RPL-Rom?
>
>
> There are 2 different kinds of RPL bootroms. the Novell kind, and the
> IBM kind.
>
> The Novell RPL is based on IPX/SPX, and i've never heard any reports
> of them being successfully used to boot a Linux kernel.
>
> The IBM flavor of RPL is based on tcp/ip. there is a project
> called 'rpld' at http://gimel.esc.cam.ac.uk/james/rpld that is
> made for booting a Linux kernel using an IBM style RPL bootrom.
> BUT, this project seems to be fairly out of date, and i've never
> actually been able to boot an LTSP/Linux kernel with it.
>
> So, if your motherboard doesn't have PXE, then I think the choices
> are:
>
> 1) Boot Etherboot from floppy
>
> 2) Get a network card that contains Etherboot or PXE
>
> 3) Integrate Etherboot into the system bios. This step is dangerous,
> and can lead to a dead motherboard, if you screw up the bios.
> Having an eprom programmer to save the bios, and restore it if
> it gets messed up is a real good idea.
>
> Hope that helps,
>
> Jim McQuillan
> [EMAIL PROTECTED]
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.freenode.net
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
