Fw: Node boot disk to designate eth0

Eric Miller emiller at techskills.com
Wed Apr 3 19:50:21 PST 2002


----- Original Message -----
From: "Eric Miller" <emiller at techskills.com>
To: "Donald Becker" <becker at scyld.com>
Sent: Wednesday, April 03, 2002 10:48 PM
Subject: Re: Node boot disk to designate eth0


>
> ----- Original Message -----
> From: "Donald Becker" <becker at scyld.com>
> To: "Eric Miller" <emiller at techskills.com>
> Cc: <Beowulf at beowulf.org>
> Sent: Wednesday, April 03, 2002 10:37 PM
> Subject: Re: Node boot disk to designate eth0
>
>
> > On Wed, 3 Apr 2002, Eric Miller wrote:
> >
> > > Subject: Node boot disk to designate eth0
> > >
> > > is there a switch I can pass to the node floppy routine that will
cause
> the
> > > node to boot using a designated ethernet adapter?  I have one onboard
> 10mb
> > > adapter and a PCI 100 mb adapter (eth0), but the node tries to connect
> > > throught the onboard eth1.  I cannot disable the onboard adapter in
BIOS
> > > (compaq :( ), so I need pass a pararmeter at boot time to use eth0.
Can
> > > this be done?
> >
> > The Scyld system tries all interfaces (using RARP) to find a master.
> > That allows the system to work with all network topologies.
> >
> > To avoid using finding the master on eth1, just don't connect that
> > interface to a master.
>
> It's odd, I can see that the drivers for both interfaces are being loaded,
> and they are both the correct drivers.  It does not seem to be looking on
> both interfaces, however.  It clearly is looking on only eth1, as it
> specifies it line by line during the RARP requests.  I've tried all the
> obvious, different NIC, different board, etc.
>
> Thanks, I guess Ill leave it alone.
> >
> > --
> > Donald Becker becker at scyld.com
> > Scyld Computing Corporation http://www.scyld.com
> > 410 Severn Ave. Suite 210 Second Generation Beowulf Clusters
> > Annapolis MD 21403 410-990-9993
> >
>




More information about the Beowulf mailing list