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

For the Sun 3/80 Task I used this to guides:

http://www.sun3zoo.de/en/nvram.html
http://www.squirrel.com/sun-nvram-hostid.faq.html
The problem is, that if I enter a command like "m a fedfa000" the monitor
gets blank after "TIA MAP FEDFA000 [...] ? 33FA500" hitting enter :-( if i
enter "m b fedfa000" i get "TIB MAP FEDFA000 [...] ? 33FB80A" which is ok,
but them it asks a second line :-( So is there anybody out, who ever did
this and can help me out? (nvram is repaired)

2. Booting OS. My Board is 501-1401 10rev50 (RomVersion 3.0) so i can't
upgrade to 3.03 to boot from cd. My Sun 3/80 can boot from disk and tape. I
don't have a QIC tape but i have DDS1 and DDS2 Tapes, does anyone knows if I
can boot up from DDS1?

THX a lot David

p.s. there is no logo at the startup, is this right or is this something to
fix also? (http://www.sun3zoo.de/sun3arc/PALs/pals.html)

David Reichelt wrote:

|> 2. Booting OS. My Board is 501-1401 10rev50 (RomVersion 3.0) so i can't
|> upgrade to 3.03 to boot from cd. My Sun 3/80 can boot from disk and tape. I
|> don't have a QIC tape but i have DDS1 and DDS2 Tapes, does anyone knows if I
|> can boot up from DDS1?

On sun3arc.net there used to be a "How to create a bootable tape".
It was intended for QIC, but might be worth trying if you can find it.

--

"I'm a doctor, not a mechanic." Dr Leonard McCoy <mccoy@ncc1701.starfleet.fed>
"I'm a mechanic, not a doctor." Volker Borchert <v_borchert@despammed.com>

"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
>
> For the Sun 3/80 Task I used this to guides:
>
> http://www.sun3zoo.de/en/nvram.html
> http://www.squirrel.com/sun-nvram-hostid.faq.html
> The problem is, that if I enter a command like "m a fedfa000" the monitor
> gets blank after "TIA MAP FEDFA000 [...] ? 33FA500" hitting enter :-( if
> i enter "m b fedfa000" i get "TIB MAP FEDFA000 [...] ? 33FB80A" which is
> ok, but them it asks a second line :-( So is there anybody out, who ever
> did this and can help me out? (nvram is repaired)
>
> 2. Booting OS. My Board is 501-1401 10rev50 (RomVersion 3.0) so i can't
> upgrade to 3.03 to boot from cd. My Sun 3/80 can boot from disk and tape.
> I don't have a QIC tape but i have DDS1 and DDS2 Tapes, does anyone knows
> if I can boot up from DDS1?
>
> THX a lot David
>
> p.s. there is no logo at the startup, is this right or is this something
> to fix also? (http://www.sun3zoo.de/sun3arc/PALs/pals.html)
>

Hi again Everybody,

ok, now i understand the procedure shown in
http://www.sun3zoo.de/en/nvram.html

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"?

can that be a problem that i use the standard values for the hostid and the
date of manufacture?

PLZ help!

David

"David Reichelt" <freud-schiller@gmx.net> writes:

>ok, now i understand the procedure shown in
>http://www.sun3zoo.de/en/nvram.html

>my input is like the one in the sample:

>fedfa7d8 ---> 01 (Version)
....
>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"?

>can that be a problem that i use the standard values for the hostid and the
>date of manufacture?

Have you replaced the NVRAM chip? If nothing changes then very probably the
battery is dead in the NVRAM chip so it won't remember the things you enter
when you power off your system. Buy a replacement chip and retry things...

- Peter


--
--
Peter Eriksson <peter@ifm.liu.se> Phone: +46 13 28 2786
Computer Systems Manager/BOFH Cell/GSM: +46 705 18 2786
Physics Department, Linköping University Room: Building F, F203

"Peter Eriksson" <peter@ifm.liu.se> schrieb im Newsbeitrag
news:e8bt74$kqh$2@news.lysator.liu.se...
> "David Reichelt" <freud-schiller@gmx.net> writes:
>
>>ok, now i understand the procedure shown in
>>http://www.sun3zoo.de/en/nvram.html
>
>>my input is like the one in the sample:
>
>>fedfa7d8 ---> 01 (Version)
> ...
>>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"?
>
>>can that be a problem that i use the standard values for the hostid and
>>the
>>date of manufacture?
>
> Have you replaced the NVRAM chip? If nothing changes then very probably
> the
> battery is dead in the NVRAM chip so it won't remember the things you
> enter
> when you power off your system. Buy a replacement chip and retry things...
>
> - Peter
Hi Peter,
i replaced the nvram chip, but i replaced ist with one i repaired. i did
this several times, so i think this
one will work like +20 other. but i will check this point by switching to a
chip that is sure known to work.
David

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

[ ... ]

> Hi again Everybody,
>
> ok, now i understand the procedure shown in
> http://www.sun3zoo.de/en/nvram.html
>
> 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.

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.

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.

You also want to not have a hostid which conflicts with any
other machine on your local net at a minimum.

Looking at an old (1992) version of the Sun FEH (Field Engineer's
Handbook), I see that for a 3/80, the hostid must start "42" "00"
followed by two more bytes which are unique to the system -- I would
suggest making the first of those "F0" or higher, and the second by some
randomly selected value in the final byte, just to increase the chances
that you won't hit a value already in use. I don't know what the last
manufactured 3/80 used.

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
calculator which will do the XOR function (I use a HP 16C), just enter
the values of the bytes one by one until just before entering the last
byte, and you will see the proper value for the final checksum byte
remaining in the display. (For the 16C, set it in hex mode, key in the
first value, hit enter, key in the second, hit <gold-key:divide> (to get
the XOR function, and enter subsequent bytes and XOR them as you go.
You could write a small C program to calculate it for you as well.

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)

0x15 How much memory to test (MB also)

0x16 Monitor screen size:

00 1152x900 (standard resolution)
12 1024x1024
13 1600x1280 (high resolution -- see 0x50 & 0x51)
14 1440x1440
15 1024x768 (low resolution)

0x17 Watchdog reset action
00 Watchdog reset returns to the PROM monitor
12 Watchdog reset causes a Power On Reset (default)

0X18 Operating system boot device
00 Polls devices (default)
12 use EEPROM/NVRAM specified device

0x19-0x1a Sun boot device in ASCII

xy 78 79 id 69 64
xd 78 64 gn 67 6e
sd 73 64 le 6c c5
ie 69 65

And -- if you're booting from the SCSI disk it should be "sd".
If you're booting from the net, it is either "le" or "ie",
depending on which the 3/80 actually used.

0x1b, 0x1c, 0x1d Controller, unit, partition
00 00 00 (default)

0x1f primary terminal
00 Monochrome framebuffer
10 Serial port A
11 Serial port B
12 VMEbus and Sun 3/60 P4 Color frame buffers
20 P4 color Frame buffer

0x20 Power Up Banner
00 Sun banner
12 Custom banner

0x22-0x23 diagnostic boot device in ascii

(Same values as in 0x19 above)

0x24, 0x25, 0x26 Controller, unit, partition
00 00 00 (default)

0x28-0x4f Diagnostic boot path in ASCII

0x50 High Resolution number of columns
50 80 columns (standard display)
78 120 columns (full screen display)

0x51 High Resolution number of rows
22 34 rows (standard display)
30 48 rows (full screen display)

0x58 Serial port default A baud rate
00 9600 baud
12 Uses EEPROM/NVRAM defined baud rate

0x59-0x5a Serail port A baud rate

1200 baud 04 b0
4800 baud 12 c0
9600 baud 25 80

0x5b Serial port A DTR/RTS
00 Asserts DTR and RTS signals
12 Does not assert DTR and RTS signals

0x60 Serial port B default baud rate
00 uses 9600 baud
12 uses EEPROM/NVRAM defined baud rate.
in the diag position, port B is set to output at 1200
baud. The setting of location 0x60-0x62 is ignored.
0x61-0x62 Serial port B band rate
1200 baud 04 b0
4800 baud 12 c0
9600 baud 25 80

0x63 Serial port B DTS/RTS
00 asserts DTR and RTS signals
02 does not assert DTR and RTS signals.

(I'm not sure why "does not" is 0x12 for 0x5b, and 0x02 for
0x63). :-)

I'll skip over a bunch which are 386i specific.

0x492 Password mode select
Sun-3 & sun0-4 boot PROM >= 2.7.1
5e Fully secure mode
01 Command secure mode
all else non-secure mode.

0x493-0x49a The 8-byte password for the above.

0x70b Sun 3/80 power-on mode <----- ***** IMPORTANT FOR YOU *****
06 normal boot
12 diagnostic mode
all else full diagnostic boot


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

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 they 3/80. 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.

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 ---

"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
>
> [ ... ]
>
>> Hi again Everybody,
>>
>> ok, now i understand the procedure shown in
>> http://www.sun3zoo.de/en/nvram.html
>>
>> 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?

> 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)

> 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

> You also want to not have a hostid which conflicts with any
> other machine on your local net at a minimum.
>
> Looking at an old (1992) version of the Sun FEH (Field Engineer's
> Handbook), I see that for a 3/80, the hostid must start "42" "00"
> followed by two more bytes which are unique to the system -- I would
> suggest making the first of those "F0" or higher, and the second by some
> randomly selected value in the final byte, just to increase the chances
> that you won't hit a value already in use. I don't know what the last
> manufactured 3/80 used.
>
> 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
> calculator which will do the XOR function (I use a HP 16C), just enter
> the values of the bytes one by one until just before entering the last
> byte, and you will see the proper value for the final checksum byte
> remaining in the display. (For the 16C, set it in hex mode, key in the
> first value, hit enter, key in the second, hit <gold-key:divide> (to get
> the XOR function, and enter subsequent bytes and XOR them as you go.
> You could write a small C program to calculate it for you as well.

http://www.sun3zoo.de/en/nvram.html provides u with a nice program to do the
task

> 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)
>
> 0x15 How much memory to test (MB also)
>
> 0x16 Monitor screen size:
>
> 00 1152x900 (standard resolution)
> 12 1024x1024
> 13 1600x1280 (high resolution -- see 0x50 & 0x51)
> 14 1440x1440
> 15 1024x768 (low resolution)
>
> 0x17 Watchdog reset action
> 00 Watchdog reset returns to the PROM monitor
> 12 Watchdog reset causes a Power On Reset (default)
>
> 0X18 Operating system boot device
> 00 Polls devices (default)
> 12 use EEPROM/NVRAM specified device
>
> 0x19-0x1a Sun boot device in ASCII
>
> xy 78 79 id 69 64
> xd 78 64 gn 67 6e
> sd 73 64 le 6c c5
> ie 69 65
>
> And -- if you're booting from the SCSI disk it should be "sd".
> If you're booting from the net, it is either "le" or "ie",
> depending on which the 3/80 actually used.
>
> 0x1b, 0x1c, 0x1d Controller, unit, partition
> 00 00 00 (default)
>
> 0x1f primary terminal
> 00 Monochrome framebuffer
> 10 Serial port A
> 11 Serial port B
> 12 VMEbus and Sun 3/60 P4 Color frame buffers
> 20 P4 color Frame buffer
>
> 0x20 Power Up Banner
> 00 Sun banner
> 12 Custom banner
>
> 0x22-0x23 diagnostic boot device in ascii
>
> (Same values as in 0x19 above)
>
> 0x24, 0x25, 0x26 Controller, unit, partition
> 00 00 00 (default)
>
> 0x28-0x4f Diagnostic boot path in ASCII
>
> 0x50 High Resolution number of columns
> 50 80 columns (standard display)
> 78 120 columns (full screen display)
>
> 0x51 High Resolution number of rows
> 22 34 rows (standard display)
> 30 48 rows (full screen display)
>
> 0x58 Serial port default A baud rate
> 00 9600 baud
> 12 Uses EEPROM/NVRAM defined baud rate
>
> 0x59-0x5a Serail port A baud rate
>
> 1200 baud 04 b0
> 4800 baud 12 c0
> 9600 baud 25 80
>
> 0x5b Serial port A DTR/RTS
> 00 Asserts DTR and RTS signals
> 12 Does not assert DTR and RTS signals
>
> 0x60 Serial port B default baud rate
> 00 uses 9600 baud
> 12 uses EEPROM/NVRAM defined baud rate.
> in the diag position, port B is set to output at 1200
> baud. The setting of location 0x60-0x62 is ignored.
> 0x61-0x62 Serial port B band rate
> 1200 baud 04 b0
> 4800 baud 12 c0
> 9600 baud 25 80
>
> 0x63 Serial port B DTS/RTS
> 00 asserts DTR and RTS signals
> 02 does not assert DTR and RTS signals.
>
> (I'm not sure why "does not" is 0x12 for 0x5b, and 0x02 for
> 0x63). :-)
>
> I'll skip over a bunch which are 386i specific.
>
> 0x492 Password mode select
> Sun-3 & sun0-4 boot PROM >= 2.7.1
> 5e Fully secure mode
> 01 Command secure mode
> all else non-secure mode.
>
> 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?

> 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

> 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.

> 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 they 3/80. 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)

but this one is a hard task! If u have any ideas, please let me know!

Thx a lot David

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 ---

In article <e8i5mi0fm4@news1.newsguy.com>,
dnichols@d-and-d.com (DoN. Nichols) wrote:

> According to David Reichelt <freud-schiller@gmx.net>:

[ snip ]

> > > 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.

The MAC address is never seen outside the local network. The outside
world neither knows nor cares about it.

Josh

could a little hack work?

i take the nvram out of the sun 3/80, put it in a sun4c (which can boot with
death nvram) and use dd to put an image to the nvram.

will this work? can someone provide me with an working nvram image of a sun
3/80?