MP 1,1-5,1 MacPro5,1: What you have to do to upgrade to Mojave (10.13/10.14 BootROM upgrades instructions thread)

[krikorola]

Southbridge SATA ports are the four drive bays and the two ODD bays. Disconnect everything that you not gonna use, simplify.

So before taking out the other SSD, I copied the console at the time I pressed the turn off on the installer.
here it is attached.

————

erreur 12:32:45.503922 +0200 mdworker Asked to exit for Diskarb
erreur 12:32:45.504358 +0200 mdworker Asked to exit for Diskarb
erreur 12:32:45.505398 +0200 mdworker Asked to exit for Diskarb
erreur 12:32:45.507697 +0200 mdworker Asked to exit for Diskarb
erreur 12:32:45.508263 +0200 mdworker Asked to exit for Diskarb
erreur 12:32:45.508734 +0200 mdworker Asked to exit for Diskarb
erreur 12:32:45.509470 +0200 mdworker Asked to exit for Diskarb
erreur 12:32:45.510310 +0200 mdworker Asked to exit for Diskarb
erreur 12:32:45.511587 +0200 mdworker Asked to exit for Diskarb
erreur 12:32:45.512207 +0200 mdworker Asked to exit for Diskarb
par défaut 12:32:45.519053 +0200 trustd cert[2]: AnchorTrusted =(leaf)[force]> 0
par défaut 12:32:45.522688 +0200 tccd MacOS error: -67050
erreur 12:32:45.527053 +0200 dirhelper create_relative: mkdirat(<private>, 700): Operation not permitted
par défaut 12:32:45.533678 +0200 trustd cert[2]: AnchorTrusted =(leaf)[force]> 0
par défaut 12:32:45.535226 +0200 photolibraryd MacOS error: -67050
par défaut 12:32:45.538148 +0200 com.apple.MediaLibraryService Unable to determine system photo library URL. Error: Error Domain=com.apple.reddwarf Code=21 "RDErrorNoValueForLibraryKey" UserInfo={NSLocalizedDescription=RDErrorNoValueForLibraryKey}
par défaut 12:32:45.557623 +0200 kernel apfs_vfsop_unmount:1589: unmounting dev
par défaut 12:32:45.567871 +0200 kernel apfs: total mem allocated: 144336034 (138 mb);
par défaut 12:32:45.567881 +0200 kernel apfs_vfsop_unmount:1846: all done. going home. (numMountedAPFSVolumes 2)
par défaut 12:32:45.577966 +0200 icdd #ICDebug - 119:{ICDiskBrowser.m} (Disk Changed)
par défaut 12:32:45.578040 +0200 icdd #ICDebug - 178:{ICDiskBrowser.m} (Disk Appeared)
erreur 12:32:45.581556 +0200 sandboxd Sandbox: diskarbitrationd(65) System Policy: deny(1) file-read-data /dev/rdisk2s3
Violation: System Policy: deny(1) file-read-data /dev/rdisk2s3
Process: diskarbitrationd [65]

 

[krikorola]

So before taking out the other SSD, I copied the console at the time I pressed the turn off on the installer.
here it is attached.

I removed all PCIe modules only leaving data HD in SATA2 ports and one OS.
Still acting the same.
I'm going to try a reinstall from a USB stick.

 

[flowrider]

^^^^Be careful about showing your SN information on a public forum

You should remove it.

Lou

 

[krikorola]

^^^^Be careful about showing your SN information on a public forum View attachment 838922

You should remove it.

Lou

It’s done.
[doublepost=1558797580][/doublepost]

I removed all PCIe modules only leaving data HD in SATA2 ports and one OS.
Still acting the same.
I'm going to try a reinstall from a USB stick.

I formatted the hard drive, Installed high Sierra from a usb stick. Before doing that I removed all pcie and other peripherals. This time everything went smoothly and I could upgrade to 144.0.0.0 bootrom.

 

[flowrider]

It’s done.

Actually it's not.

You may want to substitute this:

Lou

 

[mrtang42]

Seems you are obsessed with firmware 142.0.0.0.0. Let’s talk about that version a while. I tested it and I also bricked a machine with it. I had plenty of discussions with Developer Relations about firmware 142.0.0.0.0.

It was included in two test previews and ADR wasn’t aware of the problem that it caused. Thankfully I had @tsialex as a resource to help isolate firmware 142.0.0.0.0’s limitations with regards to CPU compatibility.

I recovered from this non-functional condition caused by firmware 142.0.0.0.0 rather quickly with the help of @tsialex . Apple released the firmware 142.0.0.0.0 in the another successive DP version as well.

With further communications to ADR about the inclusion of firmware 142.0.0.0.0, I was able to demonstrate the issue with firmware 142.0.0.0.0, and Apple pulled firmware 142.0.0.0.0. In this way, further damage was not caused by people attempting to use firmware 142.0.0.0.0.

It seems you don’t want people to know about the dangers of firmware 142.0.0.0.0. You should know there are plenty of developers who are not hardware gurus. They install DP versions to test with their own software creations. Said developers also received firmware 142.0.0.0.0 and needed help to recover. Help that Apple could not provide since they didn’t know about the problems with firmware 142.0.0.0.0.

Personally I’m very appreciative of the now-near, common knowledge, about the dangers of firmware 142.0.0.0.0. I have many friends here in the MR community who averted problems caused by firmware 142.0.0.0.0 by learning of its dangers through continued discussions about firmware 142.0.0.0.0.

Thank you for your highlighting concerns about firmware 142.0.0.0.0. By bringing highlighted attention, and reviving the topic of firmware 142.0.0.0.0, perhaps you have made many more people aware of the dangers of firmware 142.0.0.0. Now, with all the discussions about firmware 142.0.0.0.0, it will hopefully be easy to find information when someone uses the search phrase firmware 142.0.0.0.0.

Some people here gets pissed off so easily. I will not reply an emotional post. The whole point is it is beta firmware. Regular user will not be able to flash it at all now(not even developer as today). krikorola is a good example that he is confused by this. I am only giving suggestion to not include this, because it is only confuse people(some people may think he has to do firmware update step by step). If you can still find a the public access of this firmware, I will apologize. Otherwise, 142 is long gone. No newbie should care about it.

 

[Macschrauber]

A possible brick should be mentioned.

Noone expects this, it affects single CPU Mac Pros in shipping configuration. It has to be in the 1st post of a wiki thread what goes very deep into firmware tech.

It is a developer firmware version what has been pulled (because of bug reports from MR members ?).

Anyway, where when not in this thread, should be this information ?

 

[krikorola]

A possible brick should be mentioned.

Noone expects this, it affects single CPU Mac Pros in shipping configuration. It has to be in the 1st post of a wiki thread what goes very deep into firmware tech.

It is a developer firmware version what has been pulled (because of bug reports from MR members ?).

Anyway, where when not in this thread, should be this information ?

Regarding my question about single cpu firmware brick, I should have read further in the post, I was tired and mixed things up when I posted about it. If I had read it thoroughly I wouldn't have asked about it.
Anyway now Mojave is working like a charm on my single 6 core 3.33.
Thanks everyone and @tsialex

 

[Orionator]

Just so everyone knows, just updated from 138.0.0.0.0 to 144.0.0.0.0 while running 10.14.5. I had upgraded a while ago (which was why I was on BOOTrom 138). The EVGA GEFORCE GTX 770 is functional (i.e. METAL approved) for the Mojave upgrade.

Next steps are to set up M.2 boot drive and get USB 3.1 functioning (probably not the PCIe's fault though, most likely San Disks proprietary hardware for running SD cards).

Hope this information helps someone.

Ben

 

[mixedfeelings]

First off thanks so much for this incredible thread. I have used it successfully to get a fresh install of a Mojave on a new to me 2010 5,1 a few months back.

Sadly, now that I am finally ready to upgrade my 2009 4,1->5,1 cMP (my main driver) from 10.13.6 to Mojave I am having trouble. I did the double firmware updates (first with the 10.3.6 install, then with the 10.4.5 install) and currently have the 144.0.0.0.0 firmware. I am now able to run the installer from within High Sierra, but every time it simply restarts into my current 10.13.6 install rather than actually running the Mojave install. Any idea what could be preventing it from actually installing?

My GPU, a 6mos old Sapphire Pulse RX 580 8GB is starting to glitch out (random GPU artifacts) and I have already ordered a replacement. Could a failing GPU prevent it from updating successfully?

Thanks in advance!
George

 

[tsialex]

First off thanks so much for this incredible thread. I have used it successfully to get a fresh install of a Mojave on a new to me 2010 5,1 a few months back.

Sadly, now that I am finally ready to upgrade my 2009 4,1->5,1 cMP (my main driver) from 10.13.6 to Mojave I am having trouble. I did the double firmware updates (first with the 10.3.6 install, then with the 10.4.5 install) and currently have the 144.0.0.0.0 firmware. I am now able to run the installer from within High Sierra, but every time it simply restarts into my current 10.13.6 install rather than actually running the Mojave install. Any idea what could be preventing it from actually installing?

My GPU, a 6mos old Sapphire Pulse RX 580 8GB is starting to glitch out (random GPU artifacts) and I have already ordered a replacement. Could a failing GPU prevent it from updating successfully?

Thanks in advance!
George

Replace the GPU, clean the NVRAM three times and reset the SMC and try again. Since you already have 144.0.0.0.0, with a working RX 580 you can install via createinstallmedia USB key too.

 

[Black Ninja Original]

Hi guys!


After the flawless update (clean install) to Mojave (thanks TSIALEX) my magic mouse is getting slow in some moments ... I ‘ve tried delete the Bluetooth preferences and mouse, reset the Bluetooth module (Debug) and reset SMC but nothing really solved ... I do not had this problem on High Sierra ... or other previous OS...

Is there any incompatibility or bug with the Mac Pro Bluetooth board on Mojave?

Has Mojave changed anything on Bluetooth that may be causing this problem? Maybe Bluetooth power...

Any clue?

(MacPro 8 cores 5.1, Nvidea QUADRO K5000 for Mac, 32 GB RAM, Samsung 860 EVO. Firmware 141.0.0.0.0)

 

[crjackson2134]

Is there any incompatibility or bug with the Mac Pro Bluetooth board on Mojave?

Not that I'm aware of, it's working perfectly for me.

 

[mixedfeelings]

Replace the GPU, clean the NVRAM three times and reset the SMC and try again. Since you already have 144.0.0.0.0, with a working RX 580 you can install via createinstallmedia USB key too.

Greetings from Mojave, thank you so much! it worked!

One thing they may or may not have had an impact, but either way very dumb of me: The first time I attempted the update with the new GPU (upgrade/overwrite not fresh from USB drive) it did the same thing as always: just booted back into high sierra. But the second time I deactivated Jettison and it worked. I think its possible that Jettison ejecting my USB install during shutdown was preventing the reboot into install process from working properly. Seems obvious now, but - hey, I'm in! Thank you!

 

[Black Ninja Original]

Not that I'm aware of, it's working perfectly for me.

Are you using one Bluetooth Magic Mouse with Mojave?
In some moments my mouse is very slow only on Mojave ...

 

[crjackson2134]

Are you using one Bluetooth Magic Mouse with Mojave?
In some moments my mouse is very slow only on Mojave ...

Yes I am. I have MM1 & MM2. They both work perfectly for me.

 

[kohlson]

Is there any incompatibility or bug with the Mac Pro Bluetooth board on Mojave?

Perhaps not Mojave, but BT has been an issue for 4,1 and 5,1 systems for years. I have a 4/5,1 which never worked well with a 1st-gen Magic Mouse. Tried a MM2, and it worked great, until it didn't. For awhile I thought it was CS6 that was tripping it up, but was not able to prove that conclusively. A friend has a 5,1 MP that sits on his desk about 2 feet from his mouse, and that had issues.
Most people solve this with a BT antenna. Or a different mouse.

 

[Black Ninja Original]

Perhaps not Mojave, but BT has been an issue for 4,1 and 5,1 systems for years. I have a 4/5,1 which never worked well with a 1st-gen Magic Mouse. Tried a MM2, and it worked great, until it didn't. For awhile I thought it was CS6 that was tripping it up, but was not able to prove that conclusively. A friend has a 5,1 MP that sits on his desk about 2 feet from his mouse, and that had issues.
Most people solve this with a BT antenna. Or a different mouse.

Yes I've always heard about MP and Bluetooth problems. But it was never a problem for me, my mouse always worked fine ... Until I installed Mojave ... very strange ...

 

[crjackson2134]

Perhaps not Mojave, but BT has been an issue for 4,1 and 5,1 systems for years. I have a 4/5,1 which never worked well with a 1st-gen Magic Mouse. Tried a MM2, and it worked great, until it didn't. For awhile I thought it was CS6 that was tripping it up, but was not able to prove that conclusively. A friend has a 5,1 MP that sits on his desk about 2 feet from his mouse, and that had issues.
Most people solve this with a BT antenna. Or a different mouse.

Mine has been anonymous in this regard I suppose. It’s been nearly perfect since the day I bought it. I’ve had 4 different BT modules in all (for testing and various other reasons), and the only time there was a problem, was when I had a particular USB3 card installed in PCIe Slot 2, and transferring files to a USB3 drive. It’s well known that USB3 / BT Signals conflict. Even then, placing the USB3 card in PCIe Slot 4 eliminated the problem for me.

Most people don’t have my luck with this, but it’s worth noting that my cMP sits on my desktop and only mere inches from my mouse, so I believe this is most likely why I have good luck. I also have my USB3 drives sitting 2+ feet from my tower and I’m sure this helps as well.

Just as an FYI, this isn’t just a cMP issue. It happens on 2 of my laptops, and my wife’s laptop. It’s really a USB3 vs BT issue.

Anyway, this is all off topic, so hopefully you get to read it before it gets moderated. Start a new thread with proper title and you’ll get lots of replies and solutions.

@tsialex , sorry for the tangent, I’ll have it removed after while...

 

[thgtrg]

Power on your Mac Pro and download 10.14.5 full Mac App Store installer. Download from the Mac App Store, don't use hacked installs, torrents, etc. Open it, the Mojave installer will ask you to perform a firmware update, shutdown your Mac Pro and do it.

i can't find "download 10.14.5 full Mac App Store installer" to download only update version. we will use exact 10.14.5 or 10.14.x version

Can anybody help?

 

[tsialex]

i can't find "download 10.14.5 full Mac App Store installer" to download only update version. we will use exact 10.14.5 or 10.14.x version

Can anybody help?

First post has every link you need.

 

[thgtrg]

First post has very link you need.

thanks @tsialex

 

[donluca]

@tsialex is there no way to update a Mac Pro 4.1 -> 5.1 to the latest 144 bootrom without a metal capable card?

I've read some workarounds to get NVMe working but I'd rather have them the proper way.

 

[tsialex]

@tsialex is there no way to update a Mac Pro 4.1 -> 5.1 to the latest 144 bootrom without a metal capable card?

I've read some workarounds to get NVMe working but I'd rather have them the proper way.

No, there's not. The only way to overcome the METAL need from efiflasher is doing a reconstruction, but it's not a end user process.

 

[donluca]

Got it, thanks man.

I'll see if I can ask a friend to borrow a metal compatible card just to do the flashing.

If I've understood the first post correctly I just need the card for the initial flashing and then I can stay on High Sierra without the metal card, correct?