AbebeAmare
asked on
machine doesn't exit from open boot PROM mode
I have a sparcstation 20 sun machine.
when the machine boots it displays this:
<#0> ok
when I inserted a solaris 8 cd and typed boot cdrom
the system outputs this message:
level 15 interrupt
and it again enters into the ok mode.
What can I do to make this machine work?
please help me.
when the machine boots it displays this:
<#0> ok
when I inserted a solaris 8 cd and typed boot cdrom
the system outputs this message:
level 15 interrupt
and it again enters into the ok mode.
What can I do to make this machine work?
please help me.
Is your devalias correct for cdrom?
first i will load the latest OBP on this system.
i will check the CD device. since interrputs comes from hardware and it is coming when obp is trying to probe cdrom in.
so either obp is suspected or cdrom.
also as liddler suggested check also cdrom alias since if is not suspected cdrom it is suspected the hardware where cdrom alias is pointing.
was this cdrom was working well before. is this cdrom came from Sun hardware or u put something from your side, if yes then did u check if this cdrom is supported.
i will check the CD device. since interrputs comes from hardware and it is coming when obp is trying to probe cdrom in.
so either obp is suspected or cdrom.
also as liddler suggested check also cdrom alias since if is not suspected cdrom it is suspected the hardware where cdrom alias is pointing.
was this cdrom was working well before. is this cdrom came from Sun hardware or u put something from your side, if yes then did u check if this cdrom is supported.
ASKER
I have the output of .version and devalias cdrom commands on the OBP.
.version
release 2.25 version 0 created 95/09/15
devalias cdrom
cdrom /iommu/sbus/espdma@f,40000
The cdrom eas working well for other machines.it is solaris 8 software installation cd.
.version
release 2.25 version 0 created 95/09/15
devalias cdrom
cdrom /iommu/sbus/espdma@f,40000
The cdrom eas working well for other machines.it is solaris 8 software installation cd.
obp looks quite old but should work here.
what were other machine, were they sun machines. what i am lloking at whether this cdrom is supprted on sun config or not.
could u run reset-all.
then run
test-all or something i really donot the full command but it should be something like this in obp.
or
test /iommu/sbus/espdma@f,40000
if u see anything unusual post it
what were other machine, were they sun machines. what i am lloking at whether this cdrom is supprted on sun config or not.
could u run reset-all.
then run
test-all or something i really donot the full command but it should be something like this in obp.
or
test /iommu/sbus/espdma@f,40000
if u see anything unusual post it
ASKER
the "other" machines are sun sparcstation 5 and sun ultra 10 machine.
When I try test cdrom it simply returns to the ok prompt after a brief delay.
When I typed boot disk it says level 15 interrupt and returns to ok mode.
I typed test-memory.
then I typed reset -all ( the environment variable diag-switch was set to true on the OBP)
The system responds with this:
testing 64 Mbytes of memory ...
and the system outputs a series of errors non stop (like the result of an infinite loop in any program)
Here is a single line from the error message:-
ERROR: physical address=0x1888 U-number=J0201
Expected=0xa5a5a5a5 observed= 0xa5b5a5a5
And there are infinite number of errors of that type (with different physical address value)
When I try test cdrom it simply returns to the ok prompt after a brief delay.
When I typed boot disk it says level 15 interrupt and returns to ok mode.
I typed test-memory.
then I typed reset -all ( the environment variable diag-switch was set to true on the OBP)
The system responds with this:
testing 64 Mbytes of memory ...
and the system outputs a series of errors non stop (like the result of an infinite loop in any program)
Here is a single line from the error message:-
ERROR: physical address=0x1888 U-number=J0201
Expected=0xa5a5a5a5 observed= 0xa5b5a5a5
And there are infinite number of errors of that type (with different physical address value)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No, Ultra 1, Ultra 2, Ultra 30 and Ultra 60 use the same type of RAM
ASKER
Thank you all guys for your comment especially PsiCop.
I unplug the memory unit at slot J0201 and then I re-seat it.After that I did a test-memory but the same problem persists.
I removed the bad memory unit and I did boot -r then everything becomes ok except for the filesystem needing an fsck.
I did fsck and the machine is working good.
Here is my question though:- Is there any chance that I can correct the bad memory unit? I am just curious.
Thank u very much for your invaluable support.
I unplug the memory unit at slot J0201 and then I re-seat it.After that I did a test-memory but the same problem persists.
I removed the bad memory unit and I did boot -r then everything becomes ok except for the filesystem needing an fsck.
I did fsck and the machine is working good.
Here is my question though:- Is there any chance that I can correct the bad memory unit? I am just curious.
Thank u very much for your invaluable support.
No :-(
Just throw it away
Just throw it away
Yes AbebeAmare, throw it away. it will lots of efforts and all to correct that memory and it would not worth it.
it erquires hardware intervention.
glad it worked.
it erquires hardware intervention.
glad it worked.
liddler is right - ram is cheap and the days when it was worth it for a manufacturer to map the memory defects, bypass bad cells and re-issue the RAM are long past. And in any case, that's only something that could be done in a production facility, its not an end-user operation. Chuck the RAM - or give it to a competitor. :-)
any update on it.
Questions: Whgat version of the OpenBoot PROM? What specific release date of Solaris v2.8?