* Indy netboot problems
@ 1997-09-24 21:37 Charles Lepple
1997-09-24 22:23 ` William J. Earl
1997-09-25 0:50 ` Alistair Lambie
0 siblings, 2 replies; 3+ messages in thread
From: Charles Lepple @ 1997-09-24 21:37 UTC (permalink / raw
To: linux
Hello all,
Sorry to bother you if this is a routine question, but I read the FAQ, and
therein lies my problem.
I'm trying to make an Indy netboot, but I'm not too familiar with the new
monitor (let's just say that I knew sifex much better...Anyone remember the
IRIS 3130s?). I need a way to correct the HW address, since it appears to be
set to '0:0:FF:FF:0:0', and it is complaining about it.
Is there any other way to change nvram settings except through the
setenv/printenv commands?
I hope to be contributing to this project soon, but I'm off to a fairly rocky
start ;-)
Thanks in advance,
--Charles Lepple, <clepple@foo.org>
<clepple@ugrad.ee.vt.edu>
http://www.ee.vt.edu/solarcar/
http://www.mitre.org/research/nanotech/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Indy netboot problems
1997-09-24 21:37 Indy netboot problems Charles Lepple
@ 1997-09-24 22:23 ` William J. Earl
1997-09-25 0:50 ` Alistair Lambie
1 sibling, 0 replies; 3+ messages in thread
From: William J. Earl @ 1997-09-24 22:23 UTC (permalink / raw
To: clepple; +Cc: linux
Charles Lepple writes:
> Hello all,
> Sorry to bother you if this is a routine question, but I read the FAQ, and
> therein lies my problem.
>
> I'm trying to make an Indy netboot, but I'm not too familiar with the new
> monitor (let's just say that I knew sifex much better...Anyone remember the
> IRIS 3130s?). I need a way to correct the HW address, since it appears to be
> set to '0:0:FF:FF:0:0', and it is complaining about it.
>
> Is there any other way to change nvram settings except through the
> setenv/printenv commands?
...
"setenv -p xxx yyy" will set xxx permanently (in NVRAM) to yyy. Without
the "-p", it just sets xxx in the environment in memory. For the hardware
address ("eaddr"), however, you cannot readily change it, as it is the
system serial number as well as the MAC address. I don't know any easy
way for it have been corrupted; it would normally be fixed by field service.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Indy netboot problems
1997-09-24 21:37 Indy netboot problems Charles Lepple
1997-09-24 22:23 ` William J. Earl
@ 1997-09-25 0:50 ` Alistair Lambie
1 sibling, 0 replies; 3+ messages in thread
From: Alistair Lambie @ 1997-09-25 0:50 UTC (permalink / raw
To: clepple; +Cc: linux
Charles Lepple wrote:
>
> Hello all,
> Sorry to bother you if this is a routine question, but I read the FAQ, and
> therein lies my problem.
>
> I'm trying to make an Indy netboot, but I'm not too familiar with the new
> monitor (let's just say that I knew sifex much better...Anyone remember the
> IRIS 3130s?). I need a way to correct the HW address, since it appears to be
> set to '0:0:FF:FF:0:0', and it is complaining about it.
>
> Is there any other way to change nvram settings except through the
> setenv/printenv commands?
>
You can not change this with setenv. If it is '0:0:FF:FF:0:0' there is
a fault and you need to get the motherboard replaced. It is probably
the 'Dallas Chip' that is the problem. I have twice seen where a pin
gets bent on this and it returns funny MAC adresses....so if you have
some hardware knowledge it may be worth checking that it is seated
correctly and the pins are not bent.
Cheers, Alistair
--
Alistair Lambie alambie@wellington.sgi.com
Silicon Graphics New Zealand SGI Voicemail: 56791
Level 5, Walsh Wrightson Tower, Ph: +64-4-802 1455
94-96 Dixon St, Wellington, NZ Fax: +64-4-802 1459
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~1997-09-25 0:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1997-09-24 21:37 Indy netboot problems Charles Lepple
1997-09-24 22:23 ` William J. Earl
1997-09-25 0:50 ` Alistair Lambie
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.