Hello Sun Managers,
Thanks to everyone who responded. The problem has been solved. Here is the
summary:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The original question:
I have a SParc Station 20 whose motherboard was changed recently. In order
to maintain the host id and other details, the PROM chip of the old
motherboard was fitted in the new one.
Now whenever i boot this machine, i get the message:
Boot Device: /iommu/sbus/espdma@f,400010/esp@f,800010/sd@4,0
and the machine hangs.
The jumper on the hard disk is set on 3 and the actual boot device is :
/iommu/sbus/espdma@f,400000/esp@f,800000/sd@3,0
The machine boots properly when i do Stop-A and give the command
boot disk3
I want this setting to be permanent. So i issued the commands:
setenv boot-device disk3 (at ok prompt)
eeprom boot-device disk3 (as root user)
these settings have been stored but booting still doesn't take place
automatically.
Are there any other settings to be done. Please help. I will summarise
to the list
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The solution:
1. You've just been caught by the "magic diskname" system of the SS20.
Change your "setenv" to "disk", NOT disk3, NOT disk0.
On SS machines (at least before the Ultra) strapping a disk for "3"
makes it the "0" disk.
This was suggested by :- Jim Harmon <jharmon@telecnnct.com>
Charles Gagnon <charlesg@nynexst.com>
AND
2. eeprom diag-device=disk OR setenv diag-switch disk
The following people suggested a solution which matched the above command:
Anderson McCammont <and@ms.com>
Steve Butterfield <steve.butterfield@pcs.co.uk>
Michael Sullivan <mike@trdlnk.com>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Other suggestions (which may be useful in other situations) :
1. "Birger A. Wathne" <birger@vest.sdata.no>
at the boot prom:
ok set-defaults
should reset the boot prom to default values.
2. Art Kufeldt 669-2147 <ackufel@hnsun5.ppco.com>
I had a similar problem one time with an old Sparc2, and what I finally had to
do was issue the command:
setenv boot-device /iommu/sbus/espdma@f,400000/esp@f,800000/sd@3,0
I know that looks a little messy, but it usually works.
3. "Thornton, Charles (cthornto)" <cthornto@harris.com>
You are setting the correct variable but I believe you need to identify
it differently.
Test the variable by doing a boot
/iommu/sbus/espdma@f,400000/esp@f,800000/sd@3,0
The variable should be set to the string
"/iommu/sbus/espdma@f,400000/esp@f,800000/sd@3,0"
This should do the trick....
4. Nadya Williams <nadya@bog.ucsd.edu>
I had to change the mother board and PROM recently on Ultra II.
The only command to be executed after the exchange was :
set stop-A after the system banner appears during booting
ok setenv #power-cycles 0
I don't know whether it is related to your problem though...
5. Bismark Espinoza <bismark@alta.jpl.nasa.gov>
The eeprom may not be retaining info.
Also, look at the rc.d files.
6. Benjamin Cline <benji@hnt.com>
It's a little drastic, but if nothing else works, you might want to try
the "L1-N" command to reset the NVRAM parameters to their default. Take a
look at the man page for monitor(1M) for more information about this
command.
7. CHENTHIL KG <chenthil@mtcts1.mt.lucent.com>
Do the following at the OK prompt.
use-nvramrc?=true
nvramrc=devalias disk /iommu/sbus/espdma@f,400010/esp@f,800010/sd@4,0
or
Change the disk id to 4...This is an easier way..
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I would like to thank all the above mentioned people and also those whose
replies may be on the way.
Pravin
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:05 CDT