CBRICK Error - Printable Version
+- IRIX Network Forums (//forums.irixnet.org)
+-- Forum: SGI/MIPS (//forums.irixnet.org/forum-3.html)
+--- Forum: Hardware/Triage/Repair (//forums.irixnet.org/forum-11.html)
+--- Thread: CBRICK Error (/thread-2558.html)
+- IRIX Network Forums (//forums.irixnet.org)
+-- Forum: SGI/MIPS (//forums.irixnet.org/forum-3.html)
+--- Forum: Hardware/Triage/Repair (//forums.irixnet.org/forum-11.html)
+--- Thread: CBRICK Error (/thread-2558.html)
CBRICK Error - sgifan2010 - 11-11-2020
Curious to see if anyone has been able to fix this and how? See JPEG.
Thanks!
RE: CBRICK Error - Raion - 11-11-2020
Hook up via serial console while the unit is off and check the L1 status.
RE: CBRICK Error - weblacky - 11-11-2020
I’ve never seen this but off the top of my head my guess is SN stands for serial number. It’s possible that the RTC that has been running it is finally dead and you have lost the NVRAM information along with the serial number.
Most systems can self recover if you put in a blank unused RTC Chip.
But yes, you should be able to confirm this condition by attempting to hook a null-modem cable to your console serial port and see what messages you get. If you get messages complaining there is no serial number than what I just said most likely applies
RE: CBRICK Error - jan-jaap - 11-12-2020
Actually, I think SN in this context has something to do with the system architecture.
SN0 = Origin 2K / Onyx2
SN00 = Origin 200
SN1 = Origin 3K / Onyx 3K
The LCD screen is attached to the L1 controller in the brick. So a message 'No L1 comm' is probably caused by difficulty of the brick L1 to communicate with something else (the brick? the L2?).
But yeah, dead NVRAM batteries/chips could be to blame here.
RE: CBRICK Error - jpstewart - 11-13-2020
(11-12-2020, 08:24 AM)jan-jaap Wrote: The LCD screen is attached to the L1 controller in the brick. So a message 'No L1 comm' is probably caused by difficulty of the brick L1 to communicate with something else (the brick? the L2?).
But yeah, dead NVRAM batteries/chips could be to blame here.
"No L1 comm" is the exact message you get from an O300 with a dead Dallas battery. I'd assume it's the same for the O3000 as well but I don't know enough about the brick architecture to be sure.