Try reseating the connectors on the computer in the backbox for the monitors. Looks like the main screen one isn't responding. Check the cable at the monitor, too. Looks like the motherboard has DVI and VGA output.

Is it using the built-in DVI or an expansion video card? It's been done both ways.

Also, what motherboard is in it? Maybe resetting the CMOS would fix it. How long was it off?

Another thought is maybe your power supply is failing. Not enough power will give inconsistent boot results. Do you have a multimeter to check output from it?

This is an MSI H81M-P33.

Thinking about it some more, I doubt clearing the CMOS will help. I think the power supply is the first thing to check.

Nevertheless, JBAT1 is the one you want to short together (while the power is off) to clear the CMOS settings if you want to try it anyway.
MSI H81M-P33 (resized).jpg

You don't have a multimeter to check the power supply output (or even a spare ATX power supply you can try)?

Yes, where the ATX power supply connects at JPWR1, jam the multimeter black wire probe into the back of the connector (where the wire comes out) to any of the ground blocks (15, 17, 18, 19, 24, etc), then probe the back of the connectors listed on this diagram with the red probe and see if any power looks out of spec.

MSI-H81M-P33 Power (resized).jpg

Okay, well, back to cables.

It looks like you have three video cables. A DVI at 1, a VGA at 2, and I *think* (from that angle) a VGA at 3. Where do those go?

case-cables (resized).jpg

Do you have another DVI cable you can try to eliminate the cable as the problem?

Also, maybe check the power going to the monitor to make sure it's not low?

I'm out of ideas. This is a weird one. Maybe someone else can chime in that's had something like this happen. When you get it resolved, be sure to post so it's here for posterity...

Sounds like the system is simply not booting or not getting far into the boot up. Seen this on a pinball 2000 system some time ago. I would try and reseat those two dimm memory modules.

One last thing to try - if you have a spare SSD you might try mirroring your SSD to a new one, then re-installing the software again with a full install on the new one. If the SSD is going bad, maybe it's taking out files in the boot process.

That is an operating system error that Ubuntu is throwing. My initial thoughts are it is either a corrupted install of v1.60, loose / bad SATA cable or a bad SSD. Try re-seating the cable that connects the SSD to the motherboard on both ends. Next wipe the USB stick and try the whole install process again. If you continue to get errors, I would lean towards one of those components being bad.

LTG can help to get your JJP ticket in motion.

Send him a message.

SSDs are dirt cheap now. You can get a 500GB for $40-50USD here. I'm really thinking it's the SSD. What else is there that hasn't been checked?

I'm not sure about using a fresh SSD and installing from usb, but if that's didn't work, you can image the bad SSD to the new SSD and then do a fresh USB install and it should overwrite all the bad stuff.

A full install stick should setup a new SSD just fine.

Awesome, thanks for verifying.

So, yeah, now that it's verified a new off-the-shelf SSD works, that's definitely what I'd do. Get a cheap SSD somewhere in Melbourne or off the back of a truck, do a fresh install and see if you're back in business.

Ah, right. I forgot you had a resurgence and they locked you down again. Well, get a new SSD safely and then try a full install.

I had a similar problem with my RR WOZ when I first got it. JJP was stumped. I just decided to start checking all the connections because it didn't make sense to me either. What mine was is one of the USB cables was bad(cheap). I was shocked when it worked but its been great since then. It was getting to a boot section ( I assume when the USB comes up) and would error out. Worth a shot if you have some other USB cables sitting around. Good luck with the fix.

If they're next to each other you can just drape the cable over.

Yeah, given that he had a similar problem and that's how he solved it, checking all the USB connections and then swapping out cables seems like a good course of action.

Pull all 4 USB cables off of the motherboard. Disconnect them and then see if the game boots without any of them connected. Of course you’ll have no lights or anything but if it boots up okay, power off, add the I/o board usb back in. Power up again. If it boots, add the BAG board. Try again. And so on. See if something such as the camera is stopping it from booting properly. I’ve seen that before as have others.

Look at all this holiday weekend support you're getting, though!

Looking at some Ubuntu documentation, that error message means the grubenv file is > 1024 bytes, which is apparently a no-no.

There's a boot repair utility you can put on a bootable USB (same way you make a full bootable WoZ install USB) and use that to fix a hard drive Ubuntu install that won't boot. Maybe worth a shot?

https://help.ubuntu.com/community/Boot-Repair

But that was the first time you booted with no USB cables installed, right? That seems most likely to have sent the boot in that direction.

You might also want to try removing the add-on video card and see if that changes the boot.

Yes, the one next to the "3" in my picture. You might need to push a plastic tab at the bottom where the expansion slot is (at the inside edge of the slot) to release the card from the slot. You should be able to leave the other video cable attached to the case, and just release the expansion port it's plugged into from the card by taking off the ribbon cable at the top of the card that it connects to.

Yeah, those are cheap cards. Just make sure it's in the same family (Nvidia or AMD, I don't know which they use) and that should work.

Glad it's FINALLY been figured out. Three last tests:

1. Put the card in without connecting the aux video jack the other cable is connected to (so it's just the card) which will eliminate the video cable as the problem.

2. Check the BIOS settings for video card(s) and shared ram/allocated video ram. Maybe your CMOS died and when you reset they're fighting over shared VRAM.

3. When you put in the new card - if it fails again, it may be a motherboard problem with that slot or power regulation.

But at least you're finally in the right area for the root problem.

JJP, you need to bookmark this thread. I doubt this is the last time you'll see this issue.

As far as I know, DI uses an ATI 6450 with active cooling. Not easy to find these days. But as mentioned in case of a failure it’s always good to have a spare main oard and graphics card...