MP 1,1-5,1 MacPro5,1: BootROM thread | 144.0.0.0.0

[bsbeamer]

for the most i would say yes... but i mean i've got guys that are to me "geniuses" in that department...

So not factoring in the cost, would there be any advantages?

If you have the time, money and resources - give it a go and let us know how you make out.

 

[tsialex]

for the most i would say yes... but i mean i've got guys that are to me "geniuses" in that department...

So not factoring in the cost, would there be any advantages?

The 2010/2012 SMC version seems more stable and less susceptible to problems with high PCIe fan RPM caused by some GPUs. But this is a useless discussion, you will need to change both the CPU tray and backplane H8S. The cost to acquire 2010/2012 boards to remove the H8S makes this inviable even if you are not factoring supplies and equipment.

[doublepost=1548799886][/doublepost]

If you have the time, money and resources - give it a go and let us know how you make out.

I know of only one person that did this, he already had some corroded/damage boards to extract the H8S micro controller.

Btw, he have 5 digits worth of repair equipment in his lab.

 

[Kon_Kipa]

The 2010/2012 SMC version seems more stable and less susceptible to problems with high PCIe fan RPM caused by some GPUs. But this is a useless discussion, you will need to change both the CPU tray and backplane H8S. The cost to acquire 2010/2012 boards to remove the H8S makes this inviable.

I didnt realise that once you changed the SMC chip that other IC's would also need to be changed...

The only reason i asked is because i've got a 2009 cDMP which is still factory everything & im about to go the whole hog & get it fully spec'ed

Which comes my next question, apart from Squid PCI-e Gen 3 adapters, would you "highly" recommend any other 4 port M.2 PCI-e x16 adapters which will function & work with a cMP

 

[tsialex]

I didnt realise that once you changed the SMC chip that other IC's would also need to be changed...

The only reason i asked is because i've got a 2009 cDMP which is still factory everything & im about to go the whole hog & get it fully spec'ed

Which comes my next question, apart from Squid PCI-e Gen 3 adapters, would you "highly" recommend any other 4 port M.2 PCI-e x16 adapters which will function & work with a cMP

This is now totally off-topic. Please, go to the Blade SSDs - NVMe & AHCI thread, read it, and ask your questions there. All switched adapters that work are on the first post (Amfeltec Squid 2.0/3.0 and HighPoint SSD7101A/SSD7102).

 

[tsialex]

Checking dumps from MP4,1 that I cleaned/upgraded, found that one had a non public original BootROM version, probably B06:

Know MP4,1 BootROMs:

• MP41.88Z.0081.B03.0902231259 (B03)
• MP41.88Z.0081.B04.0903051113 (B04)
• MP41.88Z.0081.B07.0910130729 (B07 / EFI 1.4)
• MP41.88Z.0081.B08.1001221313 (B08)

I don't have dumps from B03/B04, but those are listed in the efiupdater table:

 

[TrumanLA]

Hey guys - I have a Medusa II ... how can I inject this in to a Mac Pro 3,1

Does a 4,1 just require I hack it to run the newer OS by changing it's identity ... and then just do a regular update?

Last ... any help getting Apple's NVMe drivers injected in to the ROM ? I'm willing to pay someone for some consulting even, if you can help me make this efficient.

Thanks

 

[Reindeer_Games]

Hey guys - I have a Medusa II ... how can I inject this in to a Mac Pro 3,1

Does a 4,1 just require I hack it to run the newer OS by changing it's identity ... and then just do a regular update?

Last ... any help getting Apple's NVMe drivers injected in to the ROM ? I'm willing to pay someone for some consulting even, if you can help me make this efficient.

Thanks

https://forums.macrumors.com/threads/blade-ssds-nvme-ahci.2146725/

 

[tsialex]

Hey guys - I have a Medusa II ... how can I inject this in to a Mac Pro 3,1

MP3,1 hardware is totally different from MP4,1/5,1.

Does a 4,1 just require I hack it to run the newer OS by changing it's identity ... and then just do a regular update?

Yes.

To run Mojave with a MP4,1>5,1 you need to upgrade your GPU to a METAL supported one and probably your AirPort Extreme too.

Last ... any help getting Apple's NVMe drivers injected in to the ROM ? I'm willing to pay someone for some consulting even, if you can help me make this efficient.

Thanks

MP3,1 NVMe injection caused some bricks, be warned. It’s not a simple process as was the MP5,1 one.

 

[Alex Sanders74]

OKAY, successful upgrade of my 4,1->5,1 to Boot ROM 140.0.0.0 and can use my NVMe PCIe drive as boot!!! Had to remove GT120 but was able to use GTX970 to install, which is weird as the Mojavi installer let me proceed without the 'all graphics card must be compatible with metal' message, which I assumed I would get.

Curious how that install went as I have a gtx750ti that was allowing me to install Mojave, but I bailed out with concern for no boot screen. Card is not flashed (Standard PC EFI) so wanted to ask how yours went with the gtx970.

I know your post was from last year, but I just got this 5.1 and would like to update the firmware but have no proper Metal approved card handy.

 

[tsialex]

I just got this 5.1 and would like to update the firmware but have no proper Metal approved card handy.

I'll send you a PM.

 

[Kon_Kipa]

@tsialex hey again Alex

just wanted to let you know i've tried flashing my cDMP from 4,1-->5,1 & it was a success

I have now tried to update the firmware using OSX 10.13 High Sierra & i think it was a success but i am not sure...

It now has Firmware version MP51.0084.B00
is that the correct version for 138.0.0.0.0??


thanks

 

[TrumanLA]

MP3,1 hardware is totally different from MP4,1/5,1.



Yes.

To run Mojave with a MP4,1>5,1 you need to upgrade your GPU to a METAL supported one and probably your AirPort Extreme too.

MP3,1 NVMe injection caused some bricks, be warned. It’s not a simple process as was the MP5,1 one.

Thanks bud.

And there's been no major changes as a byproduct of the 'renovation' to the ROMs associated with the auspice to the MP5,1 .... that's similarly benefiting the 13 / 14 MBPr ?

And - I already had the newer L13 MBPr AP cards and the Mini PCI adapter to upgrade them ... it didn't however require it to upgrade the first unit I did. And it's SWEET!

Fortunately, I have ONE "metal" GPU in stock. Anyway, thanks again. T

 

[p11hlf]

I just did the firmware update.

I pulled my GTX 980 and put in at GTX 680 knowing it had Mojave support (little did I know that I don't have to install Mojave)

Super simple update, I just downloaded the update from the App Store, it told me to do a firmware update..... Followed the onscreen instructions and BANG! done!

I did a Before and after screen shot of the system profile and a geek bench before and after just incase.

Not much change!

Happy days!

 

[timmkroeger]

Yup, i've worked out that if you use the 2009 tray in a 2010/2012 the fans run at full speed...

I never bothered to find out what would happen if you put a tray from a 2010/2012 into a 2009 model (but i'm sure it would be something similar)

I believe this isn't news for most, but yes, wanted to confirm I've tried a tray from a 2010 model in a 2009 machine - the fans do run at full speed as well.

 

[flowrider]

I have now tried to update the firmware using OSX 10.13 High Sierra & i think it was a success but i am not sure...

It now has Firmware version MP51.0084.B00
is that the correct version for 138.0.0.0.0??

No. The FW version should read 138.0.0.0.0. BUT, the latest FW (Boot ROM) is 140.0.0.0.0, that is available with the Mojave Installer. You don't need to install Mojave to install the latest FW.

Lou

 

[crjackson2134]

If your Mac Pro have a BootROM earlier than MP51.0089.B00, to upgrade to 138.0.0.0.0 you will have to do:

1. Download the full Mac App Store installer for 10.13.6, open it and then do as the installer says to upgrade to MP51.0089.B00. After the firmware upgrade reboot, you can close the installer app.
2. Download the full Mac App Store installer for Mojave, the most recent one, open it and then do as the installer says to upgrade to 138.0.0.0.0. After the firmware upgrade reboot, you can close the installer app.

 

[tsialex]

@tsialex hey again Alex

just wanted to let you know i've tried flashing my cDMP from 4,1-->5,1 & it was a success

I have now tried to update the firmware using OSX 10.13 High Sierra & i think it was a success but i am not sure...

It now has Firmware version MP51.0084.B00
is that the correct version for 138.0.0.0.0??


thanks

Read the first post again. Look at the bottom:

[doublepost=1549127611][/doublepost]

Thanks bud.

And there's been no major changes as a byproduct of the 'renovation' to the ROMs associated with the auspice to the MP5,1 .... that's similarly benefiting the 13 / 14 MBPr ?

And - I already had the newer L13 MBPr AP cards and the Mini PCI adapter to upgrade them ... it didn't however require it to upgrade the first unit I did. And it's SWEET!

Fortunately, I have ONE "metal" GPU in stock. Anyway, thanks again. T

Besides being Mac Pros and having similar cases, everything else is different hardware and firmware wise:

• MP3,1 is one platform, MP4,1 and MP5,1 are another one.
• MP3,1 uses Xeons based on C2D. MP4,1/MP5,1 uses Nehalem/Westmere Xeons.
• MP3,1 firmware is 16Mb, MP4,1/5,1 is 32Mb.
• MP3,1 uses PRAM, MP4,1/MP5,1 uses NVRAM.
• and much more…

 

[iciconnect]

My system specs: flashed 4,1 to 5,1 using Dosdude method. 16gb memory, 1tb hard drive and a MSI Radeon RX 780 4gb DDR5 graphics card. No additional hardware.

I was running High Sierra on one partition
and Windows 10 Pro 64 on the other. I had no issues with selecting Windows from the Start Disk within High Sierra. Nor had I any issues booting from Windows 10 to High Sierra using Start Disk within boot camp settings menu in Windows 10.

I upgraded from High Sierra to Mojave this past Monday 01/28/2019. There were no issues so it seemed. I booted in Windows 10 using Start Disk. There was an update to Mojave and after that it seemed fine.

I was able to boot from each system’s partition using Start Disk. However there was an update in Windows 10. I don’t know which update it had. It’s been a while since my system connected to the internet so I didn’t bother running Windows 10 for several months prior to the SSD install. So it was Wednesday 01/30/2019 when I final connected to the internet and updated Windows 10.

I was able to dual boot from both Mohave to Windows 10 using Start Disk as normal. But when I tried using boot camp from within Windows 10 to boot into Mohave it would reboot into Mac Mojave recovery mode.

From the recovery mode I had to select Mojave as the Start Disk and it booted fine.
So Thursday I add a 512 SSD and cloned Mojave. My system booted from the SSD into Mojave just fine. Still must select from the Mojave recovery to get back into Mojave.

On yesterday I installed a 2nd SSD which had 500gb. I cloned Windows 10. Now I can’t boot into Windows 10 and I must flash the PRAM to get back to Mojave. I have yet to figure out how to fix the boot issue. When ever I select Windows 10 from Mojave to boot Windows 10 I get a insert bootable message.

 

[Alex Sanders74]

My system specs: flashed 4,1 to 5,1 using Dosdude method. 16gb memory, 1tb hard drive and a MSI Radeon RX 780 4gb DDR5 graphics card. No additional hardware.

I was running High Sierra on one partition
and Windows 10 Pro 64 on the other. I had no issues with selecting Windows from the Start Disk within High Sierra. Nor had I any issues booting from Windows 10 to High Sierra using Start Disk within boot camp settings menu in Windows 10.

I upgraded from High Sierra to Mojave this past Monday 01/28/2019. There were no issues so it seemed. I booted in Windows 10 using Start Disk. There was an update to Mojave and after that it seemed fine.

I was able to boot from each system’s partition using Start Disk. However there was an update in Windows 10. I don’t know which update it had. It’s been a while since my system connected to the internet so I didn’t bother running Windows 10 for several months prior to the SSD install. So it was Wednesday 01/30/2019 when I final connected to the internet and updated Windows 10.

I was able to dual boot from both Mohave to Windows 10 using Start Disk as normal. But when I tried using boot camp from within Windows 10 to boot into Mohave it would reboot into Mac Mojave recovery mode.

From the recovery mode I had to select Mojave as the Start Disk and it booted fine.
So Thursday I add a 512 SSD and cloned Mojave. My system booted from the SSD into Mojave just fine. Still must select from the Mojave recovery to get back into Mojave.

On yesterday I installed a 2nd SSD which had 500gb. I cloned Windows 10. Now I can’t boot into Windows 10 and I must flash the PRAM to get back to Mojave. I have yet to figure out how to fix the boot issue. When ever I select Windows 10 from Mojave to boot Windows 10 I get a insert bootable message.

Try boot champ. Lots of people on the forum have been using this to switch between Windows and Mac OS. There are a couple other startup apps similar to boot champ. Try searching the Mac Pro forum. I posted about it under another thread.

 

[tsialex]

My system specs: flashed 4,1 to 5,1 using Dosdude method. 16gb memory, 1tb hard drive and a MSI Radeon RX 780 4gb DDR5 graphics card. No additional hardware.

I was running High Sierra on one partition
and Windows 10 Pro 64 on the other. I had no issues with selecting Windows from the Start Disk within High Sierra. Nor had I any issues booting from Windows 10 to High Sierra using Start Disk within boot camp settings menu in Windows 10.

I upgraded from High Sierra to Mojave this past Monday 01/28/2019. There were no issues so it seemed. I booted in Windows 10 using Start Disk. There was an update to Mojave and after that it seemed fine.

I was able to boot from each system’s partition using Start Disk. However there was an update in Windows 10. I don’t know which update it had. It’s been a while since my system connected to the internet so I didn’t bother running Windows 10 for several months prior to the SSD install. So it was Wednesday 01/30/2019 when I final connected to the internet and updated Windows 10.

I was able to dual boot from both Mohave to Windows 10 using Start Disk as normal. But when I tried using boot camp from within Windows 10 to boot into Mohave it would reboot into Mac Mojave recovery mode.

From the recovery mode I had to select Mojave as the Start Disk and it booted fine.
So Thursday I add a 512 SSD and cloned Mojave. My system booted from the SSD into Mojave just fine. Still must select from the Mojave recovery to get back into Mojave.

On yesterday I installed a 2nd SSD which had 500gb. I cloned Windows 10. Now I can’t boot into Windows 10 and I must flash the PRAM to get back to Mojave. I have yet to figure out how to fix the boot issue. When ever I select Windows 10 from Mojave to boot Windows 10 I get a insert bootable message.

First thing, do a clean install of 10.11.6 then flash your firmware to MP51, read the various threads here and on Netkas. Once with a MP51 firmware, it's fully supported.

Don't install hacked installs into a Mac Pro 4,1, just upgrade it to MP5,1. What you did is a big source of trouble and headache in the long run.

 

[ddotjay85]

Pardon my noob question... but if I'm using and want to keep using High Sierra, but now with nvme boot... how do I install the rom needed for booting nvme (said to only be in the mojave installer), without accidentally updating to Mojave OS which I don't want.... ?

 

[tsialex]

Pardon my noob question... but if I'm using and want to keep using High Sierra, but now with nvme boot... how do I install the rom needed for booting nvme (said to only be in the mojave installer), without accidentally updating to Mojave OS which I don't want.... ?

Read the first post MP5,1: What you have to do to upgrade to Mojave. After the second firmware upgrade, MP51.0089.B00 to 140.0.0.0.0, close the installer.

 

[ddotjay85]

Read the first post MP5,1: What you have to do to upgrade to Mojave. After the second firmware upgrade, MP51.0089.B00 to 140.0.0.0.0, close the installer.

Ok, so it's going to give me a chance to install 140.0.0.0.0, and then quit before ever installing Mojave? Great.

 

[nicko3.0i]

Just started the Mojave installer 10.14.3 (using Mojave 10.14.3) just to upgrade firmware .... 138 to 140. Using a RX480 non efi. Flawless process, just impossible to see anything on the screen. Properly rebooted and now it's 140 :-D

 

[ddotjay85]

Ok, so it's going to give me a chance to install 140.0.0.0.0, and then quit before ever installing Mojave? Great.

Read the first post MP5,1: What you have to do to upgrade to Mojave. After the second firmware upgrade, MP51.0089.B00 to 140.0.0.0.0, close the installer.

THANKS!! Got it updated.