Return to BSD News archive
Newsgroups: comp.unix.questions,comp.unix.bsd,comp.unix.internals,comp.sys.sun.apps,alt.unix.wizards,can.sun-stroke,alt.sys.sun Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.bhp.com.au!mel.dit.csiro.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!swrinde!newsfeed.internetmci.com!news.duc.auburn.edu!doug From: doug@eng.auburn.edu (Doug Hughes) Subject: Re: Dead Sparc 2 Message-ID: <DpJr5I.Kny@mail.auburn.edu> Followup-To: comp.unix.questions,comp.unix.bsd,comp.unix.internals,comp.sys.sun.apps,alt.unix.wizards,can.sun-stroke,alt.sys.sun Sender: usenet@mail.auburn.edu (Usenet Administrator) Nntp-Posting-Host: netman.eng.auburn.edu Organization: Auburn University Engineering X-Newsreader: xrn 7.03 References: <4ia1rs$1j1@sol.sun.csd.unb.ca> <p4trqukut.fsf@lpbcsun.lpbc.jussieu.fr> <DoC1x4.A7x@mail.auburn.edu> <3149FFFD.41C67EA6@ASG.unb.ca> <314E178D.41C6@acci.COM.AU> <4itabl$jmn@usenet2.interramp.com> <4k5eql$3q4_002@speednet.com.au> Date: Mon, 8 Apr 1996 14:05:42 GMT Lines: 66 Xref: euryale.cc.adfa.oz.au comp.unix.questions:79860 comp.unix.bsd:16782 comp.unix.internals:10063 comp.sys.sun.apps:12949 alt.unix.wizards:3580 alt.sys.sun:10152 In article <4k5eql$3q4_002@speednet.com.au>, cunning@speednet.com.au (Brian Cunningham) writes: |> >Mark Sitkowski <marks@acci.COM.AU> wrote: |> > |> >>Dear Sun experts, |> >>I need your help on this one, it's really weird: |> > |> >Not an expert, but try setting (from the OK prompt) |> >setenv diag-switch? false |> >then tell the system to boot. |> > |> >If this doesn't help, your problem is probably worse than just the |> >battery dieing. |> > |> >Remember that now that your nvram is dead, you will have to reset this |> >and any other variables you care about each time the power goes off. |> > |> >Mark Hendersons' NVRAM FAQ is excellent for getting the NVRAM replaced |> >and back up and running. |> > |> > |> >Phyllis Smith |> >p_smith@interramp.com |> > |> >Computersmiths |> > (719) 635-7215 |> >fax (719) 635-7212 |> > |> > |> |> Mark, your problem is that your NVRAM chip (IDPROM) has somehow become |> corrupted. The only *real* fix for this (unless you know FORTH really well and |> have a copy of the IDPROM editors guide) is to get this reburnt or purchase a |> new one. |> |> Don't forget however that merely reburning one to copy another will result in |> duplicate MAC addresses *suddenly* being in existence ( a big no-no). |> |> Any decent SMCC ASP or SunService Provider should be able to reburn or sell |> you a new chip easily enough. I purchased one about 2 months ago for approx. |> US$100. |> |> Hope this helps, |> |> Brian ... |> It depends on which chip has gone bad. If it's the battery backed up one, (the fat thick one), then you should just need a new battery. If it's the PROM, you just have to have a prom burner and copy a good one to the bad one. We've done this to upgrade all our pre 1.2 bootproms that did not support security mode. Now all our 1's and 1+'s that didn't have a security mode feature do! The hostid, MAC address, and other save information is stored in the battery backed up one. The boot information, forth interface, and low level command configuration is stored in the normal PROM, (which you should be able to buy from electronics firms like Jameco) I just wanted to clarify this. We've saved a bundle just by copying a newer PROM over older ones after blanking them with UV light. -- ____________________________________________________________________________ Doug Hughes Engineering Network Services System/Net Admin Auburn University doug@eng.auburn.edu