[Raion]

So I finally managed to start up the Onyx2 after nearly a year of having it. 

I have a GE16-4 and two IR3s installed along with 4G between two nodeboards with dual 400s each.

Trying to startup causes this screen: https://imgur.com/a/JGOG7GE

After about a minute of running. 

I tried running the diagnostic mode but it trips my breaker if I have another computer on the same breaker and I don't have the ability to run it in a different room at the moment. 

If I started up in normal mode it doesn't show anything on the diag port.

Which port on the onyx 2 is used for serial console access? Hoping that I can get serial console work so that I can at least see some of the error messages or more of the problem.

I hope it's the display generator and not the graphics engine or the raster managers cuz those were very expensive

[Raion]

So I did manage to get into the diag port. The one on the bottom on the back is for logging events on startup, the one on the IO6G will give you a console.

The effect continues into the boot screen but there's no signs of why that is.

I'll have to try and run the diag utils I think!

[Irinikus]

This is what mine shows when you power it up:



Confirm that there is noise present in your image?



Try running it with one RM, swapping between the two and remember that you must only use the slot closest to the GE's when using one RM.

It looks like you may have a raster memory issue. (due to the noise present on your screen.)

ALSO JUST REMEMBER THAT THESE THINGS TAKE A REALLY LONG TIME TO BOOT TO A POINT WHERE THEY REACH THE INFINITE REALITY BOOT SCREEN. (The colourful one.)

[Raion]

damn it. I'll try removing the second one. But this disheartens me.

[Irinikus]

The more RAM it has installed, the longer it takes to boot!

Here's a video showing mine boot, and it only has 1GB of RAM installed! (I used the same monitor for both the 320 and the Onyx2, so you don't see that initial screen shown by the Onyx2 in the video, but it does give you an idea as to how long it takes to boot with just 1GB of RAM.)

[Irinikus]

This is the port that you use for the serial console:

[jan-jaap]

By default the console is on the serial port (console=d). You can set it to console=g to get the console on the graphics monitor.

But I would run an irsaudit first (from the serial console). Try 'irsaudit REPEAT=5' to soak it well and catch spurious failures happening only when it's cold or warm.

The RMs and DG need to be securely seated, and that takes significant force.

[Raion]

Removing the second RM and starting up the system fixed the glitches.

Looking at the frontplane side of the VME I don't see any bent/busted pins, but I do see dust and some dirt. I couldn't get in there and get it out when I tried.

I'll go the store and get more canned air and try again.

[Irinikus]

Removing the second RM and starting up the system fixed the glitches.

Looking at the frontplane side of the VME I don't see any bent/busted pins, but I do see dust and some dirt. I couldn't get in there and get it out when I tried.

I'll go the store and get more canned air and try again.

Then swap it out with the one that's known to be working, that will will allow you to easily determine the faulty component.

---

I had a similar problem with a faulty RM10. The glitch in my case only presented itself when I attempted to run the system in a GL mode:

[Raion]

I think the issue may just be dirt on the VMEs though. We'll see.

Hopefully both RMs can be salvaged.