According to David Reichelt <freud-schiller@gmx.net>:
>
> "DoN. Nichols" <dnichols@d-and-d.com> schrieb im Newsbeitrag
> news:e8cml00cqs@news3.newsguy.com...
> > According to David Reichelt <freud-schiller@gmx.net>:
> >>
> >> "David Reichelt" <freud-schiller@gmx.net> schrieb im Newsbeitrag
> >> news:e87v9u$p16$1@newsreader2.netcologne.de...
> >> > Hi Everybody,
> >> >
> >> > finally I got a working Sun 3/80 :-) Now I have two challenges:
> >> >
> >> > 1. Setting up the NVRAM!
> >> > I did this several times on Sun4c and Sun4m Machines
[ ... ]
> >> my input is like the one in the sample:
> >>
> >> fedfa7d8 ---> 01 (Version)
> >> fedfa7d9 ---> 42 (Systemtyp)
> >> fedfa7da ---> 80 (EthernetAddress)
> >> fedfa7db ---> 00 (EthernetAddress)
> >> fedfa7dc ---> 20 (EthernetAddress)
> >> fedfa7dd ---> 07 (EthernetAddress)
> >> fedfa7de ---> ed (EthernetAddress)
> >> fedfa7df ---> aa (EthernetAddress)
> >> fedfa7e0 ---> 24 (Date of Manufacture)
> >> fedfa7e1 ---> 74 (Date of Manufacture)
> >> fedfa7e2 ---> ec (Date of Manufacture)
> >> fedfa7e3 ---> 43 (Date of Manufacture)
> >> fedfa7e4 ---> 00 (2nd Byte hostid)
> >> fedfa7e5 ---> 50 (3rd Byte hostid)
> >> fedfa7e6 ---> 18 (4th Byte hostid)
> >> fedfa7e7 ---> 9c (IDPROM cross total - XOR)
> >>
> >> after entering the last line i switch off the system and then back on,
> >> but
> >> nothing changes :-( do i have to run a "save-Command"?
> >
> > Hmm ... I don't see you entering the 1st byte of the hostid. If
> > you left this out, your XORed checksum will be wrong, because it will be
> > missing some information.
>
> hm http://www.sun3zoo.de/en/nvram.html and
> http://www.squirrel.com/sun-nvram-hostid.faq.html donīt give any word on 1st
> byte of the hostid. You say that the 1st byte of the host id must be "42"
> both documents talk about setting systemtype to "42" (fedfa7d9 ---> 42
> (Systemtyp) can this be the same? that the systemtype is the 1st byte of the
> host id?
Yes -- I think so. It is the right value, at least. Strange
that it is separated from the rest of the HOSTID, and rather different
from what is shown in the FEH (Field Engineer's Handbook.)
> > Why do you need to enter this information anyway? It should be
> > stored in the NVRAM in the clock chip -- unless the battery has failed
> > in there, in which case you can key this in all you want and it will
> > keep getting lost.
>
> i repaired the nvram clock chip (more at the end)
O.K.
> > Note that the first two bytes of the hostid must be right, or
> > the OS will initialize looking at the wrong addresses for various I/O
> > devices and memory management hardware at a minimum. (And your ethernet
> > address *must* be unique. If you don't know the right values for that,
> > you must take a junked old ethernet card from a PC, yank the ROM or PROM
> > which contains the ethernet address and *destroy* it, and use the
> > ethernet address from the card (which should be on a label on the card.
> > This will assure that you get a unique address.
>
> in my small network the use of the default addresses given by the two
> documents is ok i think
Perhaps so -- as long as you don't connect to the outside
world via ethernet at least.
[ ... ]
> > You will have to calculate a new checksum for the NVRAM after
> > you change the HOSTID and the ethernet address. If you have a hex
[ ... ]
> http://www.sun3zoo.de/en/nvram.html provides u with a nice program to do the
> task
So I saw. That saves having to write the program.
> > The same page in the FEH says that the NVRAM lives at location
> > U0205, and is Sun part number 525-1031-01.
> >
> > If all of this is corrupted, then a lot of other things will
> > also have to be corrected. The ones which I see listed in the early
> > part of the Common EEPROM or NVRAM parameters include:
> >
> > 0x14 Installed memory (how many MB are installed)
[ ... ]
> > 0x493-0x49a The 8-byte password for the above.
>
>
> Man this a lot of information! u didnīt have that in your mind, did u?
No way! I just picked up my old Sun FEH (1992 date, IIRC) and
copied what looked meaningful.
> > 0x70b Sun 3/80 power-on mode <----- ***** IMPORTANT FOR YOU *****
> > 06 normal boot
> > 12 diagnostic mode
> > all else full diagnostic boot
>
> i set these settings and the nvram just keeps them in mind so i think i
> repaired it well
O.K. That is good.
> > The ID/NVRAM, as mentioned above, are in location U0205 (J7 B3),
> > and are not far from the parallel port connector.
> >
> > Bank 1 of SIMMs are in sockets:
> >
> > U0603, U0605, U0604, and U0606 -- and you must have all four
> > populated at a minimum with 1MB SIMMS. I see no mention of 4MB SIMMs,
> > so this makes the maximum RAM 16 MB
>
> Sun 3/80 with rom 3.0.3 are known to can take a maximum of 64mb by using 4mb
> simms.
O.K. That is good, and takes you up to 64 MB. I was going by
what was in the old FEH which I was consulting.
> > Most of this is from the "CPU -- Firmware" section of the
> > manual, and the rest from the two pages dedicated to the 3/80
> > itself.
> >
> >> can that be a problem that i use the standard values for the hostid and
> >> the
> >> date of manufacture?
> >
> > Since I can't tell whether your hostid starts with the right
> > byte, I don't know. Anything other than 42 00 as the first two bytes
> > will be wrong for the 3/80.
However -- based on your web information, the hostid is split
into two sections of memory, with the 42 (type) separated from the rest.
In later systems, the first two bytes of the HOSTID were the type, and
that was adjacent to the final two bytes.
> > But the first thing is to check whether
> > you have a good battery in U0205 (the clock/NVRAM chip) If not, you need
> > to either replace it with a good chip, or go into it and dig out the
> > battery terminals with a Dremel or the like, and cut the leads and
> > solder in a holder for a 3V coin battery to replace it. (Note that I
> > have heard that recent chips from the same manufacturer don't work
> > properly with some systems, so the battery-replacement surgery may be
> > the better choice.
>
> i used exactly the tools and parts u said. a dremel and a coin battery.
> for sun4c everything worked fine(~20 systems repaired)
Great!
> but this one is a hard task! If u have any ideas, please let me know!
I've pretty much run out of ideas -- other than perhaps setting
the diagnostic mode byte in the NVRAM and watching with a serial
terminal instead of the framebuffer and keyboard. (And, IIRC, part of
that diagnostic information will go to TTYB -- it was buried somewhere
in the listing of addresses and contents that I have you.
And -- of course -- you know that the 3/80 won't run the normal
version of SunOs 4.1.1 (the last major version released for the Motorola
processors). All the previous Sun-3 machines were MC68020 powered, but
the 3/80 was 68030 powered (and called "sun3x" instead of "sun3", so it
needed a different version of the OS. (Most of the utilities were the
same, but anything which works directly with the kernel needs to be
different, as the 3/80 used the built-in memory mapping hardware in the
68030, while the earlier sun3 machines used Sun's own hardware separate
from the CPU chip.
I've never owned nor used a 3/80 -- I should have gotten one
back at a hamfest several years ago for very little money, just so I
could have one. :-) I ran several other sun3 machines, starting with a
3/140, as well as a 2/120. The last was a 3/280, IIRC -- a big
rackmount VME machine.
One other thing which is different between the sun3 machines and
the sun4 ones is the parity on the boot disk. To boot, the disk must
have the SCSI parity jumpered *off*. The sun4 machines must have it
jumpered *on*. The frustrating part is that it will go through the full
install (from a booted tape) with no complaints, but once you try to
boot, it will fail. (I'm not sure *what* the 3/80 wants, since it is
sort of half-way between the sun3 line and the sun4 line.
And *today's* information comes from my memory.
Good Luck,
DoN.
--
Email: <dnichols@d-and-d.com> | Voice (all times): (703) 938-4564
(too) near Washington D.C. |
http://www.d-and-d.com/dnichols/DoN.html
--- Black Holes are where God is dividing by zero ---