Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!uccba!alobar!grs
From: grs@alobar.ATT.COM (Gregg Siegfried)
Newsgroups: comp.sys.att
Subject: Re: 3B2 Floppy Key Problem
Summary: use crash(1M)
Keywords: floppy key nvram
Message-ID: <293@alobar.ATT.COM>
Date: 17 Oct 88 21:26:42 GMT
References: <1094@psu-cs.UUCP>
Reply-To: grs@alobar.UUCP (Gregg Siegfried)
Distribution: na
Organization: AT&T OSS Development, Cincinnati
Lines: 23

In article <1094@psu-cs.UUCP> paulm@psu-cs.UUCP (Paul Mauvais) writes:
>Someone in charge of the 3B2 before me changed the hardware
>password to something different from the default, and now
>no one knows what.  So, I follow the nifty manual directions
>and use my floppy key to reset the NVRAM.  

In order to find the firmware password (I don't know of a hardware
password) if one can log in as root, just use the crash(1M) program.
The crash command "nvram fwnvr" will display various firmware
parameters, among them the firmware password.  This works for my 600
running 3.1.1.  I haven't used an earlier 3B2 release in a long time,
so I don't remember if that particular crash command existed previously.
I would hope so.


Enjoy,
Gregg

-- 
 Gregg Siegfried            | Nothing I say should be construed as AT&T
 AT&T - Cincinnati          | policy or opinion .. I just hack here.
 UUCP: grs@alobar.att.com   | Don't Rock - Wobble
 ARPA: grs%alobar@att.arpa  | 513-629-8314 (work) 513-561-0368 (antiwork)