paulm@psu-cs.UUCP (Paul Mauvais) (10/15/88)
I have a 3B2/300 with 2MB of RAM and an internal 30MB HD
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.
Nothing. It resets the date/time just fine, but does nothing
to the hardware/diag password at all.
Any suggestions on what I can do??
Paul Mauvais
Assistant System Programmer/Administrator
LOCAL: paulm@psu-cs Portland State University CS
CSNET: paulm@cs.pdx.edu Portland Center for Advanced
ARPANET:paulm%cs.pdx.edu@relay.cs.net Technology
UUCP: {ucbvax,uunet,gatech}!tektronix!psu-cs!paulm
============================================================================jcs@tarkus.UUCP (John C. Sucilla) (10/17/88)
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. >Nothing. It resets the date/time just fine, but does nothing >to the hardware/diag password at all. No problem. Just remove the cover, locate the battery and disconnect it for a minute. The password will go back to it's default. -- John "C". Sucilla, A silicon based life form. {att,chinet,ddsw1}!tarkus!jcs You have a better idea? Now's the time..
jkj737@uxf.cso.uiuc.edu (10/18/88)
*>/* Written 7:08 pm Oct 14, 1988 by paulm@psu-cs.UUCP in uxf.cso.uiuc.edu:comp.sys.att */ *>/* ---------- "3B2 Floppy Key Problem" ---------- */ *>I have a 3B2/300 with 2MB of RAM and an internal 30MB HD *> *>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. *> *>Nothing. It resets the date/time just fine, but does nothing *>to the hardware/diag password at all. *> *>Any suggestions on what I can do?? *>/* End of text from uxf.cso.uiuc.edu:comp.sys.att */ The way we reset it is to unplug the nicad battery pack. It is in the right front corner of the machine. Just pop the lid and unplug it.... Beware, ALL VRAM is scrozzed, so you will have to reset date, time and nodename. The Firmware password will be reset to "mcp". Jeff Johnson ARPA: jkj737%uxf@uxc.cso.uiuc.edu UUCP: ...!uiucuxc!uiucuxf!jkj737
grs@alobar.ATT.COM (Gregg Siegfried) (10/18/88)
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)
rjd@occrsh.ATT.COM (Randy_Davis) (10/18/88)
In article <293@alobar.ATT.COM> grs@alobar.UUCP (Gregg Siegfried) writes: >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. Neat! I didn't know that existed. I read this, turned around to my 3B2 and typed the crash command, got the ">" prompt, typed 'nvram fwnvr' and it worked. This is on a 310 running release 2.0.4. Randy Davis UUCP: ...(att!)ocrjd!randy ...(att!)occrsh!rjd
abell@polyslo.CalPoly.EDU (abell) (10/20/88)
The easiest thing to do is to unplug the battery source to the NVRAM. This returns all the internally stored items to their initial state including the firmware password. In case you don't know it, it's default value is mcp. Another thing to note when entering the firmware password is that the terminal must be set to 9600 baud, and space for parity. ------------------------------------------------------------------------- | Alan Bell | For smart mailers (e.g. internet): | | Cal Poly State Univ. | abell@polyslo.calpoly.edu | | San Luis Obispo, CA 93407 | For dumb mailers: | | (805) 756-7185 | ...ucbvax!voder!polyslo!abell | -------------------------------------------------------------------------
rwhite@nusdhub.UUCP (Robert C. White Jr.) (10/21/88)
in article <49800004@uxf.cso.uiuc.edu>, jkj737@uxf.cso.uiuc.edu says: > *>/* Written 7:08 pm Oct 14, 1988 by paulm@psu-cs.UUCP in uxf.cso.uiuc.edu:comp.sys.att */ > *>/* ---------- "3B2 Floppy Key Problem" ---------- */ > *>I have a 3B2/300 with 2MB of RAM and an internal 30MB HD > *> > *>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. > *> > *>Nothing. It resets the date/time just fine, but does nothing > *>to the hardware/diag password at all. > *> > *>Any suggestions on what I can do?? > *>/* End of text from uxf.cso.uiuc.edu:comp.sys.att */ > > The way we reset it is to unplug the nicad battery pack. It is in the right > front corner of the machine. Just pop the lid and unplug it.... > Beware, ALL VRAM is scrozzed, so you will have to reset date, time and nodename. > The Firmware password will be reset to "mcp". I had a similar experience once, I even went as far as to remove the NV-RAM battery. No luck. . . . I was about to call out a very expensive serice call when it suddenly hit me. Some idiot (in this case me) had set the console to even parity. It turns out that, while the UNIX System /dev/console driver was only seven-bit significant, the firmware is eight-bit significant. When I set the terminal back to 9600-8-1-N the password worked fine. (yes verginia, it will be "mcp" [Thank you Disney Productions] ;-) Boy was that a stumpper for about 5 hours ;-) On a side note: Using the floppy key is identical in function to removing the batery (aledgedly) but you must *make* the key durring the inital installation (or any time there-after) yourself. The disk labeled "FLOPPY KEY" that comes with the rest of the stuff is just a blank, formatted diskette. This is the case because the key must have the serial number of your system board written on it (with other information too) for it to work in your system. This means that you can't use one key in another machine. (those of you who have floppy keys already know this, but a lot of people I used to work with didn't. Not fun, nor funny. So I thought I'd take the extra bandwidth to mention it.) Rob.