[weblacky]

Yo,
I was curious if anyone knew:

A. How to reset an L2 module (Linux busybox controller box brick) you might buy used...assume it's password protected or some junk.

B. Did anyone ever figure out how to power one of them from like a normal AC wall brick?  Pretend I don't have the power supply from a cluster to run it.  Anyone ever open one and power it via a DC bench PSU or something?

Thanks.

[jan-jaap]

Yo,
I was curious if anyone knew:

A. How to reset an L2 module (Linux busybox controller box brick) you might buy used...assume it's password protected or some junk.

B. Did anyone ever figure out how to power one of them from like a normal AC wall brick?  Pretend I don't have the power supply from a cluster to run it.  Anyone ever open one and power it via a DC bench PSU or something?

Thanks.

A. Don't think I ever had to, but can't you start it with 'init=/bin/sh' as kernel argument or something?

B. While most L2 controllers used an O3K power supply, there was also an official SGI wall wart for it. You can easily make your own using an 48V adapter and that's what I did for my O350. I used a D-Link DSA-0421S-50. The pinout of the three-row D-SUB connector is (used to be ?) known. I can open this one up if necessary. When I ordered the D-SUB and the backshell many years ago I had to order a minimum of 10 so I *should* still have some should you need them. Now, to find these part though ...



Update: might as well post a pic of the connector so I won't have to dig this thing up later ;-)



I assume red is +48VDC and black GND, but double check. I'm not responsible.

[weblacky]

Great info, thanks!

[jwhat]

Thanks Jan-Jaap,

I have 2 x L2 but only one power supply (wall wart ;-) ).

That is very helpful.

If you do come across the surplus shells I would love to have one.

I have checked on ebay and there are quite a few compatible 48V DC output power supplies available.

Cheers from Oz,


John.

[jwhat]

Hi Jan-Jaap, Weblacky & others,

I have dead L2 that is stuck in bootloader loop:

>> Linux/PPC load:
>> Uncompressing Linux...done.
>> Now booting the kernel
>> 
>> 
>> Validating L2 Controller Flash image....OK
>> Booting...
>> 
>> 
>> Ethernet address from Motorola VPD EEPROM is 08:00:69:11:B5:38
>> 
>> Linux/PPC load: ?                   <<=== see if there is some simple help built in....
>> Uncompressing Linux...done.
>> Now booting the kernel
>> 
>> 
>> Validating L2 Controller Flash image....OK
>> Booting...
>> 
>> 
>> Ethernet address from Motorola VPD EEPROM is 08:00:69:11:B5:38
>> 
>> Linux/PPC load:

I have tried the enter: "?" "help" "dir" "ls" and even "init=/bin/sh" at the load prompt but it just ignores the entry and continues on it cycle, entering anything stops the cycle temporarily until you press the return key.

So it is obviously going to some bootloader interpreter but I am not entering a valid command...

Any tips or guidance on this one ?

Cheers from Oz,

John

[weblacky]

OMG, I’m laughing too hard, sorry...you’re not gonna like this. 

Answer:
https://nixdoc.net/man-pages/IRIX/man1/flashsc.1.html

Use flashsc with the l2recover option and A NULL MODEM CABLE! 

That’s right, the command claims you have to connect the L2 console port (serial) using a null modem cable to perform a firmware recover. 

So your non-null modem cable solution, now requires null modem cables.

FYI, I also switched to MacOS as my primary like 11 years ago.  But that’s no excuse not have every old Windows PC or laptop I ever owned. I also have several (cheap as I got them used under fixable firmware bugs) Surface Pro 3 units about 2 years ago (not worth even half retail cost, but I only paid under $200 a unit) that I can use as serial terminals.

Since I used to do IT and Network management for a living I have several machines and use a heterogeneous environment. 

My motto, use the best tool for the job.  Translation, stopping forcing a single OS to do everything, none of them are good at it.  Get several options so you can pickup a tool, use it, and finish your job.  Don’t try to metaphorically use a hammer when you need a wrench.

[jwhat]

Hi Weblacky,

you are 100% correct that "flashsc -l2recover --dev /dev/ttyd2 l2.bin" is used to recover an L2, but this only works if the L2 successfully boots linux (Busybox) kernel, but is then unable to find a valid L2 image.

In this case it will go into a recovery sequence, which is output on the L2 console port:

>> Validating L2 Controller Flash image....FAILED!
>> INVALID IMAGE HEADER CHECKSUM (C55DDEBE)
>>
>>
>> FATAL ERROR!!!  Your L2 controller binary image is corrupted!!
>>
>> You must perform the L2 Controller flash recovery sequence, which
>> allows you to download a new L2 controller image via the Console
>> serial connection on the L2 controller
>> 
>> The typical recovery sequence is:
>> 1) Attach a serial (null modem) cable from the L2 Controller serial port
>>   marked "Console", to the serial port on the L3 Controller.
>> 2) Disconnect any terminal program that may be connected to the
>>   serial port.
>> 3) Execute the l2recover command on the L3 controller:
>>     /usr/cpu/firmware/sysco/l2recover /usr/cpu/firmware/sysco/l2.bin
>> 4) When the command completes, the L2 should reboot.  If it does not
>>   then power cycle the L2 to reboot it.

I have hit this problem as well, when L2 died part way through applying a firmware update and I was able to recover via Fuel using NULL modem cable.

So I have not managed to get rid of serial comms and cables completely ;-)

The Fuel was a good tool ;-)

I just have to much IT stuff lying around already so I get rig of everything I can ;-) like old PCs.

I opened up the L2 and it has a Motorola XPC860TZP50D3 32 Bit PowerPC chip and an AMD AM29LV040B EEPROM chip.

So I copied a good L2 EEPROM content onto the EEPROM from the bad (and non "flashsc --l2recover .." recoverable) L2, but even with this reflashed EEPROM it still fails to load kernel, so maybe the L2 has got bad RAM or something...

I think this one will go into scrap heap or the dusty "not worth the trouble pile" ;-) unless someone can suggest some bootloader diagnostic that might be available.

Thanks for tip and pointing out the irony, good to have a laugh not just sometimes but lots of times.

Cheers from Oz,


John.

[jan-jaap]

If you do come across the surplus shells I would love to have one.

I found them :-)

Looks like I have 7 connectors and 2 backshells.

Still need it now one of the L2 units is for the "not worth the trouble pile"  ?

[weblacky]

Hi John,
Way out of left field - you might want to try a re-CAP of the L2? I've heard of this once (recapping fixing a "wonky" L2). Consider trying it? It "could" be a power issue that causes the sudden suspension of activity (dirty power, fluctuating power, incorrect voltage, etc...).

[jwhat]

Hi Jan-Jaap & Weblacky,

Shells and plugs : I still have another one good one that needs a power supply (ordered) and some plug soldering. so yes please. PM on the way on this

Capacitors: Oh no, not more capacitor / power issues !!!!

Cheers from Oz,

John.