MP 1,1-5,1 Reviving my $100 Mac Pro 4.1 → 5.1

[3ric4]

Howdy y'all! I recently snagged a cMP 4.1 → 5.1 locally for what I thought was a nice bargain. The rig had dual x5680 cpu's, 64gb 1333mhz ram, 3tb of spinning platter discs, both original graphics card and rx580, as well as a pixlas mod already done.

The previous owner was running macOS via OpenCore and after an update, his system wouldn't boot anymore, so he sold the rig for cheap.

I was hoping this was just a software issue, and started trying to get the computer back in operation. An order was placed for two 1TB NVME drives, as well as inexpensive pcie 4x card readers for the SSDs. I threw on a windows 11 install one one of the NVMEs, and it booted without any issue.

macOS on the other hand has been an absolute pain to get installed, so I'm reaching out for some help!

I found this video to be helpful, as it takes High Sierra up to Monterey via OpenCore

But currently, I can't get any macOS operational to do things like updating the boot ROM.

After following this instructional, I thought I was going to get HS installed, but after running my boot USB, the screen just showed command line information and went to a blank screen with the computer on standby.

Any input would be greatly appreciated! Currently I don't have a mac computer that I can operate, so hopefully this can be solved using windows.

Thanks,
Eric

 

[3ric4]

https://imgur.com/5TE2q5m

This is an example of what I see when booting off my USB. The computer loads some prompts and then goes to sleep indefinitely

 

[tsialex]

Take some steps back and install a fully supported macOS release, the easiest to install is Sierra to a SATA drive - no required firmware updates like High Sierra and Mojave.

After you get Sierra working, you will know the real Mac Pro config without any OC/OCLP spoofing. Only then you can try moving on.

Since it's a cross-flashed early-2009, the Mac Pro BootROM is probably shot, also since you run Windows 11, you probably make it even worse, since without OC ProtectSecureBoot enabled, the Windows UEFI SecureBoot signed the Mac Pro BootROM all over.

 

[3ric4]

Take some steps back and install a fully supported macOS release, the easiest to install is Sierra to a SATA drive - no required firmware updates like High Sierra and Mojave.

After you get Sierra working, you will know the real Mac Pro config without any OC/OCLP spoofing. Only then you can try moving on.

Since it's a cross-flashed early-2009, the Mac Pro BootROM is probably shot, also since you run Windows 11, you probably make it even worse, since without OC ProtectSecureBoot enabled, the Windows UEFI SecureBoot signed the Mac Pro BootROM all over.

Thank you @tsialex for the reply. Looks like you do legendary work on here!

What's the recommended way to get a pure Sierra install? Downloading it from apple, and then mounting that InstallOS.dmg file to a USB via TransMac? I don't own another mac computer right now, but could probably source one from a friend/family if it's easier to setup the full install.

I'm not up on the details of a BootROM, does a mangled ROM still allow for possible repair? Is it something that has to be physically flashed? Or done via software?

Apologies for my ignorance on this subject, I'm eager to learn however!
-Eric

 

[tsialex]

What's the recommended way to get a pure Sierra install? Downloading it from apple, and then mounting that InstallOS.dmg file to a USB via TransMac?

Never had to use Windows to do that, so, can't help you with that.

I don't own another mac computer right now, but could probably source one from a friend/family if it's easier to setup the full install.

Sierra from Apple is not a normal DMG, it's a PKG that creates the DMG. I bet that will be a lot easier to do with a real Intel Mac.

I'm not up on the details of a BootROM, does a mangled ROM still allow for possible repair? Is it something that has to be physically flashed? Or done via software?

Yes, it's possible to repair and upgrade the BootROM with a payed BootROM reconstruction service, I'll send you a PM about.

Anyway, you need to get macOS running first, it's not possible to do it via Windows.

 

[3ric4]

Thanks for all the help! Is it better to take a working mac, and install a fresh OS onto an SSD, and then swap that SSD into the mac pro?

Or just use the working mac to create a boot drive, and use that to install Sierra on my mac pro?

I'm getting access to one tomorrow.

Cheers!

 

[tsialex]

Thanks for all the help! Is it better to take a working mac, and install a fresh OS onto an SSD, and then swap that SSD into the mac pro?

While for most Macs this will work, some Macs initialize the disk in a different way than the MacPro5,1, so, it's not impossible that you can have trouble doing that.

Or just use the working mac to create a boot drive, and use that to install Sierra on my mac pro?

I'd do that, just make a Sierra createinstallmedia USB installer. You will have a better chance of success.

 

[3ric4]

Ok I'll give that a shot, and keep ya posted

 

[3ric4]

I was able to make a proper Sierra installer USB from a MacBook Air.

When booting the cMP, holding option, I still got the same black screen with white code. I then reset the SMC and NVRAM on the computer, and was able to view my USB Installer stick.

After selecting the installer, I got the white apple screen with grey logo, and the loading bar went to about 2/3, before going to a black screen with the cMP still running...

Any advice on how to go from here?
Thanks!

 

[Jhonjhon236]

Could you remove all GPUs except the original? The 580 wasn’t added until 10.13.4/

 

[3ric4]

Yes this is with the original stock GPU installed.

 

[tsialex]

When you get the black screen, any LEDs are lit? CPU tray have LEDs for memory problems near the DIMM slots. Also check if any of the DIAG LEDs on the backplane give any clue.

 

[tsialex]

Could you remove all GPUs except the original? The 580 wasn’t added until 10.13.4/

Apple added support with 10.12.6, anything earlier you get a black screen. High Sierra have proper acceleration, but for diagnostics and installation purposes, 10.12.6 is the first time that a RX 580 works.

 

[3ric4]

I left the computer unplugged for a couple hours and tried the same USB Sierra Installer, and this time got to the actual install page. Ran disk utility to format my SSD for macOS (it didn't show my nvme) and started the sierra install. Everything was looking good, and the progress bar, around halfway until the screen went black again.

The backplane diagnostic lights are not showing anything, but the CPU tray light array looks like the diagram below, with the x being lit.

[ ] [ ]
[ ] [ ]
[ ] [ ]
[ ] [x]

Feels like I'm getting closer. I appreciate the assistance.

 

[tsialex]

One of the DIMMs is defective, see the Apple Technician manual to identify it, around page 30 and something.

Maybe more DIMMs are bad.

 

[3ric4]

Thanks! I looked into it and sounds like the problem with some DIMMs are poorly torqued heatsinks? I know my CPUs are not de-lidded, which means you have to be careful on tightening the heatsinks.

I left the computer running with the screen black, and it woke back up! Now it's the white apple screen with grey logo, and progress bar is at ~80%. I'll keep y'all posted.

 

[tsialex]

Get delidded Xeons or de-lid yourself, it´s crazy to use lidded Xeons nowadays. It´s possible to get it exactly right, but the most probable outcome is a damaged CPU socket.

X56xx Xeons are extremely inexpensive nowadays, dual CPU trays are still expensive.

 

[3ric4]

The Sierra install was a success! I probably made it harder than it needed to be...

Boot Rom 144.0.0

Version 10.12.6

Is the next step to setup drivers for the RX580, and work on OCLP for Monterey/Ventura/Sonoma?

 

[tsialex]

No, you need to run ASD and see what is happening.

There are no drivers for AMD GPUs, macOS already have it internally.

 

[3ric4]

Get delidded Xeons or de-lid yourself, it´s crazy to use lidded Xeons nowadays. It´s possible to get it exactly right, but the most probable outcome is a damaged CPU socket.

X56xx Xeons are extremely inexpensive nowadays, dual CPU trays are still expensive.

It looks like just one slot no4 is not working, and I already bought 16gb sticks to make 96gb triple channel. Is it a bad idea to leave it as is, and source some delidded CPUs in the meantime? Or should I immediately fix that problem before proceeding?

 

[tsialex]

It looks like just one slot no4 is not working, and I already bought 16gb sticks to make 96gb triple channel. Is it a bad idea to leave it as is, and source some delidded CPUs in the meantime? Or should I immediately fix that problem before proceeding?

At least remove the defective DIMM and run ASD. You also have loads of kernel panics inside the NVRAM that will need cleaning.