Alex i found it on the Mac Video Cards website
Anyhow having said this, the original poster is running 10.11.6 (FYI) - no disrespect intended
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
Anyhow having said this, the original poster is running 10.11.6 (FYI) - no disrespect intended
This kext was developed by a user here on MacRumors (jimj740), in 2015, never updated and is nowhere production ready. It's know for KPs. Don't use it.
For the time, was a breakthrough, but today is just a unnecessary risk.
Cool thanks, do you have a suggestions why this terminal command fails ?
macproosx:NVMe for OSX armindeeg$ sudo chown –R 0:0 NVMeGeneric.kext
chown: –R: illegal user name
Thanks Armin
People, please stop disseminating wrong info. If you don't know about something, please don't post about. Someone who knows the correct answer will post later. A lot of wrong info was posted here today.
Please don't do this.
Please don't do this.
I am unsure of its usefullness - TsiAlex has frowned upon its use as it is old & never been updated
[doublepost=1547728760][/doublepost]
Alex is there a way apart from installing OS X Mojave to install/inject (or what ever terminology) or using RecoveryHDMetaDmg.pkg (as explained by yourself) to update to firmware 140.0.0.0???
To upgrade to 140.0.0.0.0 you have first to upgrade to MP51.0089.B00, it's a two step firmware upgrade. Read the first post here: MP5,1: What you have to do to upgrade to Mojave.
You can't upgrade to 140.0.0.0.0 with a GT120, it's not a METAL supported GPU and Apple efi2flasher requires it. Your GTX 980 is a METAL supported GPU but it's not supported by Mojave native NVIDIA drivers. So, until NVIDIA release Mojave drivers for Maxwell and newer GPUs, you are can use the GT120 to upgrade to MP51.0089.B00.
The only workaround is manually reconstructing your Mac Pro BootROM.
Last edited by a moderator:
If you know how to extract the volumes from your BootROM, you can extract the NVRAM volume and the LBSN sector from your dump and insert into 140.0.0.0.0.
If you don't know, don't even try. This is a complicate process and the fastest way to get a brick.
Remove all GPUs, install only the Apple GT120 to upgrade to MP51.0089.B00. Remove it, install a supported one then upgrade to 140.0.0.0.0.
All info needed to upgrade is on the first post here: MP5,1: What you have to do to upgrade to Mojave.
done part 2 of firmware update, didnt know i had MoJave 10.14 only so it flashed to 138.0.0.0, then i used the RecoveryHDMetaDmg.pkg & redone it & its now 140.0.0.0 - damn its long with no thunderbolt & USB 3.0 Ports
got there in the end - so happy now
I have a 4,1->5,1 mac pro, with a EFI flashed HD 7970 (metal capable) GPU, and an SM951 AHCI SSD. I was running 10.13.6 and decided to instal Mojave yesterday because I plan to upgrade to an NVMe. During the install, I was prompted to update my firmware, after the firmware update and Mojave install, my boot rom is 138.0.0.0.0 not 140.0.0.0.0. I have been pouring over the threads all morning but I feel like I am just confusing myself further. Can you help?
This is already answered into the first post, 138.0.0.0.0 is the firmware from 10.14.0.
Delete your old Mojave installer, download the full installer for Mojave 10.14.2 from Mac App Store. Open the installer, it will ask you to upgrade the firmware to 140.0.0.0.0.
the same thing hapened to me
i just cloned back a copy of 10.13.6 to another HDD & then used RecoveryHDMetaDmg.pkg to update the firmware to 140.0.0.0.0
The copy of Mojave installer the above poster had/is 10.14 & not 10.4.2 (or 10.14.1 DP3+)
You DONT need to clone/copy over your current MoJave install either, just use another HDD - if you have one - it can be a USB connected copy of the 10.13.6
Two different users sent me PMs this week reporting two more bricks. Unfortunately, two users that can't dump the SPI flash externally.
Could be flash memory cell exhaustion, failed backplanes, old age, etc - but something is going on.
One is a mid-2012 MP5,1 made into September 2013, another is a November 2009 made MP4,1, I have the serials.
[doublepost=1548189215][/doublepost]Apple released 10.14.3, btw. Same 140.0.0.0.0 BootROM.
Last edited:
Would also be curious to know if Windows was ever installed on those machines, if boot camp was ever utilized, and reports of the GPU being used (and how it was powered). Trying to find common themes. Assume they're all on (were on) 140.0.0.0.0 firmware?
I did a BootROM reconstruction a month ago for the early2009 Mac Pro, so probably no NVRAM problems. I'll ask about Windows.
The mid-2012 is a recently purchased one, so no history.
MP4,1 with ACBel PSUs, the one with shittty caps, seems to…
Something is triggering. The list is long and would be great if we could somehow narrow down. Immediate culprits: Windows install/updates, firmware update issues, underpowered GPUs or maxed out PSUs, 4,1>5,1 issues, or failing PSUs or other board parts.
Some of this may just be coming to light with NVMe usage and RX580’s with machines that were never pushed that far. RX580 seems to be power hungry in my testing and do wonder if it’s triggering or contributing. Loadbalance between dual mini 6-pin is important but I’m sure this presents with multiple GPUs with multiple power requirements. IF that is not that case, at least it would be something to point to.
Something as freak as solar flares, power surges or similar are not likely since this seems software related, but can something like that be fully ruled out? Assume these are in multiple different locations throughout globe.
Some of this may just be coming to light with NVMe usage and RX580’s with machines that were never pushed that far. RX580 seems to be power hungry in my testing and do wonder if it’s triggering or contributing. Loadbalance between dual mini 6-pin is important but I’m sure this presents with multiple GPUs with multiple power requirements. IF that is not that case, at least it would be something to point to.
Something as freak as solar flares, power surges or similar are not likely since this seems software related, but can something like that be fully ruled out? Assume these are in multiple different locations throughout globe.
Were they all running Mojave? My fan issues and tone on boot becoming intermittent became normal again once rolling back to HS. On a fresh install a week ago or so of 10.14.2-odd booting and fan's revving for no reason again (I got a powerlink to try Mojave again, no go).
I'd thought about giving 10.14.3 a try and see if it ironed it out, but think I might reconsider a standstill for a while.
Last edited: