[SunRescue] Solaris 7 and SS10

[Lyndon Griffin]

OH, yeah...  I guess it's not 3.2x on the new SS10...  I really don't
remember, but James L could probably tell you (I got it from him).  I'm
thinking of one of the Ultras I was working on, probably.  Sorry for the
mixup.  I don't like your answer, but it does confirm my own answer.  That
really blows, for me, but hey - I love this stuff - doing it *one more
time* just doesn't seem like enough ;)

Thanks,

<:)  Lyndon Griffin
http://www.bsd4us.org

On Thu, 10 Feb 2000, Gregory Leblanc wrote:

> > -----Original Message-----
> > From: Lyndon Griffin [mailto:lgriffin at BSD4US.ORG]
> > Sent: Thursday, February 10, 2000 10:12 AM
> > To: rescue at sunhelp.org
> > Subject: [SunRescue] Solaris 7 and SS10
> > 
> > 
> > OK - probably James L can answer this, but I'll throw it to 
> > the group...
> 
> I'll try, just in the interests of making myself look like a fool.  :)
> 
> > Will an older PROM version on an SS10 prevent booting from a 
> > drive that
> > was installed on a system with a newer PROM?  I built a new OS for a
> > production machine on an SS10 with a 3.2x PROM, plugged it 
> > into the SS10
> > with a 2.10 PROM, and I get something like SCSI message 
> > missed and corrupt
> > disk label.  I haven't put the drive back on the newer SS10, 
> > yet, as it's
> > in a different city.  Please tell me I didn't cook the drive 
> > in transit ;)
> 
> I don't see how a PROM downgrade could cause a drive to not work, unless
> there was some piece of hardware on the motherboard that required a newer
> prom to exist.  Actually, I'd expect that not to affect drives, but maybe
> audio, or some other semi-trivial system.  Mind you, the latest PROM
> revision I know of for the SS10 is 2.25, and not 3.2x.  That said, I don't
> really get magic numbers.
> 	Greg
> 
> _______________________________________________
> Rescue maillist  -  Rescue at sunhelp.org
> http://www.sunhelp.org/mailman/listinfo/rescue
>