Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
No, never have on this Mac and I used disk utility immediately prior to trying to install the OS. Erased drive and tried both APFS and HFS+. No go! WTH.
Only one drive in system, a 512GB SSUAX.
It's a 2009 5,1 cMP, with 138.0.0.0.0.
Maybe you could install from another drive, boot High Sierra, open Mojave installer, then point the installer to the drive you want to install.
 
Maybe you could install from another drive, boot High Sierra, open Mojave installer, then point the installer to the drive you want to install.
Yes, I'm sure there are workarounds, but I'm struggling to understand why Apple have blocked installing on a cMP with a GTX 680 when it works perfectly once the OS is installed.
A bug in the installer? We're very close to GM here! This may even be GM which makes it all the more concerning.
 
Last edited:
Upgrade from High Sierra 10.13.6 from the same Mojave USB flash drive works just fine.
Definitely an installer bug. Hopefully Apple will fix.
 
  • Like
Reactions: orph
Tested my two cards in Furmark

Card 1:
- 115% TDP
- Temp 81C
- Fan 60%

Card 2:
- 106% TDP
- Temp 79C
- Fan 57%

Idle temp 37C, fan 30%

Idle temp 31C, fan 30%

They have very similar results otherwise though. The one that is highest is the one I found paste on. Specs doesn't reveal overclocking though.

Will re-paste them, and consider card 2 as the "best" one.

Flash should remove any settings that could have been changed anyways right?
 
Flash should remove any settings that could have been changed anyways right?

Yep.

In fact, for those that had factory overclock models, they lose their factory overclock once flashed. But it is trivially easy to overclock using Kepler BIOS Tweaker.
 
Yep.

In fact, for those that had factory overclock models, they lose their factory overclock once flashed. But it is trivially easy to overclock using Kepler BIOS Tweaker.
Thanks.
I found out that the difference is actually normal between two identical cards (according to EVGA forums).

Temp did however match at idle after re-pasting.
 
Last edited:
Well that was easy...

Card 2 Flash.PNG


Card 2 Flash Confirm.PNG
 
While the first card literally took seconds, and after rebooting and reinstalling driver (I guess a bit different Windows driver for the versions?) it worked perfectly, but had 110% TDP and 81C instead of 105% and 79C.

Anyways, card number two was REALLY difficult. Still not sure it's OK...

I couldn't get all info in GPU-Z (even though I did before). Maybe the now currently installed "Mac" driver messed something up.

The flash went through, but couldn't be verified. This messed up the card.

After a few attempts I was successfull in flashing a "0000FFFF" named card, and do now see the GPU again. Very strange.

Will try to reflash to make sure.
[doublepost=1536950079][/doublepost]Nevermind, I think it is OK...

Very strange though.

Earlier driver, probably from Windows.

Skjermbilde.PNG
 
Upgrade from High Sierra 10.13.6 from the same Mojave USB flash drive works just fine.
Definitely an installer bug. Hopefully Apple will fix.

Yeah, that bug appeared with developer beta 7. It prevents you from applying firmware updates too without one of the few recommended cards. I'm keeping an install of beta 6 (18a353d) in case there are future firmware updates. Of course an install of HS 10.13.6 works too.
 
  • Like
Reactions: Squuiid
Do you use FileVault? Did you installed 138.0.0.0.0 before booting with the pendrive?
What's this? I'm seeing the same issue on my Mac Pro 2009 5.1. I thought FW updates came with the OS? At least it did during High Sierra update.

Yeah, that bug appeared with developer beta 7. It prevents you from applying firmware updates too without one of the few recommended cards. I'm keeping an install of beta 6 (18a353d) in case there are future firmware updates. Of course an install of HS 10.13.6 works too.

So will it work after flashing the firmware? I'd like to do a clean install of Mojave, but it seems like I'm stuck on this bug as well.

Will try to install High Sierra tonight, then update to Mojave.
 
What's this? I'm seeing the same issue on my Mac Pro 2009 5.1. I thought FW updates came with the OS? At least it did during High Sierra update.



So will it work after flashing the firmware? I'd like to do a clean install of Mojave, but it seems like I'm stuck on this bug as well.

Will try to install High Sierra tonight, then update to Mojave.
Read here MP5,1: What you have to do to upgrade to Mojave
 
Thanks!!
So basically I HAVE to have High Sierra installed first? The firmware is in the Mojave installer, but can’t be run without already having it installed...?
I did upgrade from El Capitan to High Sierra recently (after upgrading to 5.1 firmware) and was prompted with a firmware update for High Sierra.
So now I’ll have to do an update with the Mojave installer (from High Sierra) first, THEN boot from Mojave USB-stick and do clean install?
 
Thanks!!
So basically I HAVE to have High Sierra installed first? The firmware is in the Mojave installer, but can’t be run without already having it installed...?
I did upgrade from El Capitan to High Sierra recently (after upgrading to 5.1 firmware) and was prompted with a firmware update for High Sierra.
So now I’ll have to do an update with the Mojave installer (from High Sierra) first, THEN boot from Mojave USB-stick and do clean install?

It’s a 2-step operation. You have to have BootROM MP51.0089.B00 and 10.13.6 before upgrading to the Mojave BootROM.

You can only do a USB clean install after having BootROM 138.0.0.0.0.
 
Last edited:
It’s a 2-step operation. You have to have BootROM MP51.0089.B00 and 10.13.6 before upgrading to the Mojave BootROM.

You can only do a USB clean install after having BootROM 138.0.0.0.0.

So in short there is no way of upgrading to Mojave without 10.13.6 and running the Mojave installer once first...

Strange how they can’t run the FW update from USB key.

Doing a 10.13.6 clean install now, hopefully this will fix the issue.
 
So in short there is no way of upgrading to Mojave without 10.13.6 and running the Mojave installer once first...

Strange how they can’t run the FW update from USB key.

Doing a 10.13.6 clean install now, hopefully this will fix the issue.

Apple only supports USB firmware upgrade with the original 2010/2012 config, if you changed the GPU or has a 4,1, it will not work. You have to do the firmware upgrade from macOS opening the full installer for 10.13.6 and later with the full installer for Mojave.
 
Apple only supports USB firmware upgrade with the original 2010/2012 config, if you changed the GPU or has a 4,1, it will not work. You have to do the firmware upgrade from macOS opening the full installer for 10.13.6 and later with the full installer for Mojave.
Well, it did work with High Sierra... But of course that was upgrading when i think about it...not USB... I guess that was a clean install afterwards.

It is a 4.1, but flashed to 5.1, i thought they would be identical then?
The GPU is the GTX 680 so not original, but latest officially supported, and with working Mac EFI.
Well, 10.13 installs without a hitch, so I’ll do the FW flash, and clean install Mojave.

Love how a 2009 Mac Pro is suddenly a “beast” 2018 Mac with Mojave. 6 cores now (only single CPU board). A bit more noisy than I’d like though.
 
Not the same GPUs


USB installer can't even install Mojave with a GTX-680…
Not sure I understand here...

The motherboards are the same, and can be flashed to the same FW. But only “real” 2010 can be flashed with USB without getting the Metal/FileVault error?

Why shouldn’t the installer work with 680? It supports Metal?

After installing 10.13.6, I could confirm my FW was the most recent one, and after starting the Mojave installer, I now have 138.0.0.0.0. The screen was white while flashing, not the typical progress bar.

I thought this would mean that I can now install from a USB, a clean install, with my GTX 680?
 
Not sure I understand here...

The motherboards are the same, and can be flashed to the same FW. But only “real” 2010 can be flashed with USB without getting the Metal/FileVault error?

2009 and 2010 are not the same. SMC is different even if you install the 5,1 firmware. BootROM hardware descriptor is not the same. GPUs are not the same. Apple only tested efiflasher with HD 5770 and 5780.

Why shouldn’t the installer work with 680? It supports Metal?
Year long bug.

After installing 10.13.6, I could confirm my FW was the most recent one, and after starting the Mojave installer, I now have 138.0.0.0.0. The screen was white while flashing, not the typical progress bar.

I thought this would mean that I can now install from a USB, a clean install, with my GTX 680?

No, you can't. You have to do it from macOS. USB installer do not work with NVIDIA GTX 680. Read the thread MP5,1: What you have to do to upgrade to Mojave
 
2009 and 2010 are not the same. SMC is different even if you install the 5,1 firmware. BootROM hardware descriptor is not the same. GPUs are not the same. Apple only tested efiflasher with HD 5770 and 5780.


Year long bug.



No, you can't. You have to do it from macOS. USB installer do not work with NVIDIA GTX 680. Read the thread MP5,1: What you have to do to upgrade to Mojave
Oh, OK. I misunderstood. I thought it would be corrected after installing 138.0.0.0.0. I unfortunately confirmed this now.

So there is really no way to clean install Mojave on my Mac Pro 2009? I only have the GT 120, other than GTX 680.

So I guess I’ll have to reinstall High Sierra again, and then upgrade instead of clean install Mojave?
 
Oh, OK. I misunderstood. I thought it would be corrected after installing 138.0.0.0.0. I unfortunately confirmed this now.

So there is really no way to clean install Mojave on my Mac Pro 2009? I only have the GT 120, other than GTX 680.

So I guess I’ll have to reinstall High Sierra again, and then upgrade instead of clean install Mojave?
Use two disks, do from macOS. Open the installer, then select a empty disk or use startosinstall.
 
Do from macOS, use the installer pointing a empty disk or use startosinstall.
But what does this mean:

  1. After the reboot, open System Information and check if you have BootROM 138.0.0.0.0, if yes, you can do a createinstallmedia USB clean install or upgrade your previous High Sierra install.
It suggests USB clean install would work? (Which I unfortunately found out didn’t)
 
But what does this mean:

  1. After the reboot, open System Information and check if you have BootROM 138.0.0.0.0, if yes, you can do a createinstallmedia USB clean install or upgrade your previous High Sierra install.
It suggests USB clean install would work? (Which I unfortunately found out didn’t)
I’ll add the GTX-680 bug.
 
  • Like
Reactions: Squuiid
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.