Thanks for the quick response. This is the model I purchased.
https://www.amazon.com/gp/product/B07BRCLMTS/ref=od_aui_detailpages00?ie=UTF8&psc=1
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 MacPro5,1: BootROM thread | 144.0.0.0.0
- Thread starter tsialex
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Thanks for the quick response. This is the model I purchased.
https://www.amazon.com/gp/product/B07BRCLMTS/ref=od_aui_detailpages00?ie=UTF8&psc=1
Don't get me wrong, but this is totally of topic. Go to the correct thread and ask help there.
I know that the user is a newbie but you are not @orph, please don't reply to off-topic posts, I already showed the correct thread and pointed the off-topic question two times.
Let's keep this thread strictly BootROM related.
Last edited:
I have already updated to 140.0.0.0.0 and originally had an EFI install of Win10 on my 2009 MacPro 5,1. After reading about possible bricking of the ROM, I wiped and completed a Legacy install of Win10. Problem is, I still have the certificates inserted from the old EFI install.
Is there a way to reconstruct my BootROM and get rid of these 2 certificates? I know there shouldn’t be any issue now that I have Win10 installed as Legacy, but I’m freaked out about the whole ‘brick’ thing.
@tsialex. You are the one to help as far as I can tell...
Is there a way to reconstruct my BootROM and get rid of these 2 certificates? I know there shouldn’t be any issue now that I have Win10 installed as Legacy, but I’m freaked out about the whole ‘brick’ thing.
@tsialex. You are the one to help as far as I can tell...
Last edited:
Try booting 10.13.6, then opening the full Mac App Store installer for Mojave (the current one, 10.14.2).
Yesterday I installed two SATA SSDs from a W10 PC into my Mac Pro SATA bays, to backup user files and erase the SSDs. Inadvertently, as I was using a RX-580, my Mac Pro booted from one of the Windows SSDs.
Look what I got:
So, some things that I noticed with this fiasco:
Look what I got:
So, some things that I noticed with this fiasco:
- My Mac Pro booted over the SATA SSDs even with my SSD7101A/970Pro installed. So, the SATA bays have precedence into the boot order, even if my 970Pro was selected as the default boot drive.
- I couldn't control the boot order with a non Mac EFI GPU, I had to install my GTX 680 to boot back into my 970Pro using the boot selector.
- Just two boots with UEFI W10 and two SecureBoot certificates.
I can confirm the same behavior in my Sonnet. The Win10 on that drive always is first in the boot order. I also have Win 10 on a 970 pro with lycom.
Just FYI. I installed my new ADATA ASX8200PNP-1TT-C XPG SX8200 Pro with 1TB into my Mac Pro 5.1 with bootrom 140.0.0.0 using a cheap no name PCIe adapter. Worked out of the box. Installed Mojave on it, and it is booting without issues for me. Transfer is obviously way below the capability of this SSD, but I'm quite happy with the 1500 r/w without a raid 0 card...
Now that I saw that with just two boots my Mac Pro got two certificates into the first two streams of the NVRAM volume, I'm more worried than before - but this is my personal concern and opinion, not a hard cold fact, I'm just showing that this happens.
Let me explain why this behaviour get's me worried, since Windows SecureBoot certificates are written into the same two streams of the NVRAM volume that Apple configures RAM, boot, everything low-level, anything out of the ordinary there and you can't boot (like with users with TITAN GPUs noticed before). With newer Macs, that Apple supports Windows with UEFI and have Intel ME, the BootROM configuration is not affected by the SecureBoot certificates, since it's not in the same area that configures low-level things.
Another thing, with RX-580 and my default boot disk installed into a 970Pro, I got a Windows UEFI boot loop that I couldn't get out. Other people had reported this before and I didn't grasp how troublesome is. Just this is a motive to go back to BootCamp/CSM and use iMac Pro BootCamp boot assistant/selector.
Last edited:
Apple released 10.14.3 DP2 today, same 140.0.0.0.0 BootROM:
Code:
$IBIOSI$ MP51.88Z.F000.B00.1809191555
Apple ROM Version
Model: MP51
EFI Version: 140.0.0.0.0
Date: Wed Sep 19 15:49:52 2018
Build Type: Release
This thread was talking about 140.0.0.0.0 + RX580 + NVMe boot drive will cause some boot issue. Not sure if related to your boot loop problem.
https://forums.macrumors.com/thread...oot-on-pcie-nvme.2154517/page-2#post-26895148
I'm following that thread - I think that is a different problem than what I had, mine is probably related to the way MP5,1 firmware sets everything on PCIe as a External drive. The SATA ports got precedence even with the 10.13.6 970Pro selected as default boot drive.
Seems it is the same as this MacPro 4.1 windows and macOS
[doublepost=1545250468][/doublepost]BTW, I have the exact same config that @crjackson2134 have, except that his Mac Pro is a 2012 with W3680 and mine is a 2009 with X5680, same RX580 to the label, same SSD7101A, same 970Pro, BootROM reconstructed the same way. I didn't found that behaviour yet.
Last edited:
Causing from reconstruction method? Check your method a to z? Or try stock 140.0.0.0 fw. You know better than us.
Last edited:
Sorry. I don't know your reconstruct procedure nor macs update procedure. For example when i mod the legacy pc bios/stuff, i will control the checksums, modules etc in the end. Maybe you miss the some point in reconstruction stage that logic board checks them. Why not? Because of that i said re-check everything, every editing/reconstructing procedure.
Maybe stock 140.0.0.0 fw, not reconstructed one that came with 10.14.2 solve the problem. I don't know.
You know Mac's low level working principles better than me.
Have a nice day. I hope you will solve.
Maybe stock 140.0.0.0 fw, not reconstructed one that came with 10.14.2 solve the problem. I don't know.
You know Mac's low level working principles better than me.
Have a nice day. I hope you will solve.
Sorry. I don't know your reconstruct procedure nor macs update procedure. For example when i mod the legacy pc bios/stuff, i will control the checksums, modules etc in the end. Maybe you miss the some point in reconstruction stage that logic board checks them. Why not? Because of that i said re-check everything, every editing/reconstructing procedure.
Maybe stock 140.0.0.0 fw, not reconstructed one that came with 10.14.2 solve the problem. I don't know.
You know Mac's low level working principles better than me.
Have a nice day. I hope you will solve.
You are correct about checksums, initially when I started researching this, I didn't knew where and how the various checksums were made. I did some stupid things then, but I'm almost sure that I found every checksum and how to redo it for all streams correctly even before 139.0.0.0.0 was released. The boot loop problem happens even with the generic MP51.fd, I checked it yesterday to be sure.
I think that the boot loop with W10 UEFI SATA SSDs is not related with reconstructed BootROMs, but the way that Mac Pro firmware treats any PCIe drive as an external one, since the SATA SSDs had precedence and I wasn't using a Mac EFI GPU, I couldn't get out of it.
First boot after nvram reset is defaulted to sata drive. In my case I have HS on one of them and WIN 10 on the other .Both are running in the Sonnet tempo pro. Win10 is always selected first (could be it is first on the SATA card I have to confirm) .if I select another boot drive from the Boot camp manager in Windows everything works fine. Boot loop for Windows comes for me if I have GT-120 and RX-580 sometimes not always. The trick is to disconnect the cable from one of them untill booted.
Sounds not entirely right to me. In my experience, after PRAM reset, the cMP always boot back to the first available MacOS, not Windows. And the MacOS SSD can be on the Tempo SSD card. But I am not 100% sure if this behaviour has been changed after all these firmware upgrade. But the last few times after I perform PRAM reset (with 140.0.0.0.0), I can hold Command + R to boot to recovery partiton straight away (there is only one recovery partition available on my cMP. Which is on the SSD on a Tempo SSD card). My understanding is if Windows drive is selected, even I hold Command + R, the Mac will do nothing but continue boot to Windows.
That behavior is also after card change not specifically PRAM reset (which implies SMC reset after more than 15 s power off with power cable disconnected). Bear in mind Windows is in EFI mode .
Last edited: