Thanks Alex, so I guess I can flash the firmware to 140.0.0.0.0 simply by doing a reinstall of Mohjave from the App Store!?
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
Yes, but read the first post here MP5,1: What you have to do to upgrade to Mojave
Last edited by a moderator:
When I'm not busy, I usually read all new posts into the Mac Pro area. I started to notice in the last two or three weeks a lot of people having unbootable Mac Pros, probably some bricks too. Could be totally unrelated to the BootROM and just plain hardware failure and since most, if not all, are users that can't provide dumps from the SPI flash, we probably will never know for sure what is going on - but this is getting me a little worried that something weird is happening with all this Mac Pro problems.
Hi! Do they have unbootable Mac and failures after the successful flash or when attempting to flash and fail?
After. It's not direct related to the BootROM upgrade process, but something else.
It's not direct related to the BootROM upgrade process, but something else. Could be plain simple hardware failure, SPI flash cell exhaustion or NVRAM corruption.Oh my, I had a successful upgrade to 140 but now I'm starting to be worried
I had THREE MP5.1 die in the office last winter within half an hour of each other and a 6.1 also died but very slowly over the course of a few months!
In my case nothing to do with firmware but high humidity, salty air and corrosion ( we are by the sea)
What I am noticing is a more users are posting similar problems to what I experienced.
I just bought replacement 5.1 from ebay and changed over HDs and graphics cards.
However Tsialex is rightfully concerned, we have a 10 year old computers which need to be looked after carefully.
I've noticed a trend that SEEMS to be with upgraded/hacked 4,1>5,1 machines having issues when or after upgraded to Mojave, that also have Windows installed on the machines. I do wonder if Windows 10 updates have anything to do with this.
My personal authentic 5,1 has not had Windows installed on it (outside of a VM install for Windows XP and 7). I have not run into many of the issues these users are reporting.
It would certainly be worth keeping a bootable SATA SSD of High Sierra around for everyone. It's an easy first step for troubleshooting. Keep your Windows install on a separate drive (not just partition) if at all possible. Also recommend cloning your entire system on a semi-frequent schedule.
My personal authentic 5,1 has not had Windows installed on it (outside of a VM install for Windows XP and 7). I have not run into many of the issues these users are reporting.
It would certainly be worth keeping a bootable SATA SSD of High Sierra around for everyone. It's an easy first step for troubleshooting. Keep your Windows install on a separate drive (not just partition) if at all possible. Also recommend cloning your entire system on a semi-frequent schedule.
I’ve experienced max fan speeds twice now in the past few weeks with no obvious performance loss or an explanation why-loads are low and temps are cool. SMC reset or booting out of Mojave is the only solution I’ve found. Although the only boot issues I've had I believe are related to connectivity issue on my drives ( I finally ordered SSD sleds for the bays), and shifting the SSD's on the SATA prong usually fixes booting issues.
Mojave keeps loosing appeal, IMO. I've spent far more time rebooting in attempting to fix minor issues than I ever have in owning my flashed 4,1->5,1. I flashed mine and did the conversion in 2015/16 time frame and sourced my files from what I believe was the original code (but I can't recall exactly where I sourced it back then). Historically, I haven't had any major issues other than the 32/64 bit conversion (if I'm recalling correctly) where gray screens during install were common-it took 3 or 4 installs before success (Mavericks...I think?).
If I stay away from Mojave and only use Win 10 and High Sierra, I don't experience any issues. Anecdotal- I know, but that should give hope it's more than likely a software issue; hopefully. Reaching into my Mojave drive from High Sierra works well as a workaround for now.
Last edited:
Thanks to tsialex, reconstructed 140.0.0.0 with ver.15 CPU microcode on cMP/2009/4,1->5,1/Dual X5690/96GB/Flashed EVGA SC GTX680/10.13.6 works perfectly.
I will make one note in case it is helpful in diagnosing for anyone - have two SATA SSDs connected via PCIe on Apricorn Velocity Duo X2 (with updated firmware from Apricorn years ago) that very recently occasionally started not showing on the desktop when starting from a cold boot. The drives are fully accessible through finder and within all applications. Appears to be a purely "cosmetic" style issue. A shutdown and reboot fixes. Has happened maybe three times in the past two months. Waiting an extended period of time does not "fix" the issue. All direct SATA SSDs appear, as do all drives connected externally (currently via USB3). Have NOT installed that Innie workaround for external drive appearance and no desire to. On High Sierra 10.13.6 with firmware 140.0.0.0.0 and NVMe via PX1 for system drive.
I'm staying off of Mojave as long as I can. Really don't see the benefit for my needs with Mac Pro 5,1. Have so far been given an extension from particular client for "update compliance" through February 2019 mostly based on lack of NVIDIA/CUDA drivers. If I can continually prove with legitimate documentation there are workflow issues, I will be given another extension. Will likely update MBP around March/April 2019 if I can hold out that long.
I also have a Apricorn Velocity Duo X2 with two SATA SSDs, and during the last weeks I've also detected strange things that never happened before. Occasionally it stops detecting 1 of the discs when starting from a cold boot. Complete shutdown and reboot solve the problem (simple reboot does not solve it). I don't know what can be happening here
Last edited:
I also have a Apricorn Velocity Duo X2 with two SATA SSDs, and during the last weeks I've also detected strange things that never happened before. Occasionally it stops detecting 1 of the discs when starting from a cold boot. Complete shutdown and reboot solve the problem (simple reboot does not solve it). I don't know what can be happening here
Quite interesting and probably coincidental, but I started having this or a similar problem within the past 4–6 weeks. My main boot drive is on a Duo and, on occasion, it appears to not be detected on start up—nothing but a blank monitor and a running cMP. A shut down and restart fixes the problem. Until a week ago I was on HS and .0084, so shouldn't be related to any recent OS or firmware changes. Don't know if the upgrade has impacted the problem as I've haven't used the machine much since the upgrade.
I also have a Apricorn Velocity Duo X2 with two SATA SSDs, and during the last weeks I've also detected strange things that never happened before. Occasionally it stops detecting 1 of the discs when starting from a cold boot. Complete shutdown and reboot solve the problem (simple reboot does not solve it). I don't know what can be happening here
Was your firmware on Velocity Duo X2 ever upgraded by Apricorn? I'm starting to wonder if this issue is limited to Velocity Duo X2 models ONLY, or if there are other SATA PCIe adapters impacted, or if it's only limited to dual (or more) PCIe adapters.
Are you currently using NVMe at all, or just SATA SSDs?
What format are your SSDs (HFS+ or APFS)?
I'm on 140.0.0.0.0 and NVMe via PX1 for system drive now. Replaced Velocity Solo X2 directly with this (was also system drive) shortly after the 140 release. Do not recall having OCCASIONAL issues with Velocity Duo X2 before 138 or 140 firmware update(s). Again, if the issue does present a cold boot immediately resolves. Have only noticed 2-3 times and drives were still accessible via finder. SATA SSDs on Velocity Duo X2 are media drives, not system.
My gut says it's Windows 10 and what ever is writing the certs into the flash.
Just SATA SSDs, no NVMe at all. First SSD with APFS and HS, second with Windows 10 Legacy. I'm on 140.0.0.0.0.
I never updated the Velocity Duo X2 firmware, but I don't know if bought it with the latest firmware included, I bought it in April 2015. Do you know what your version is to compare it?
I don't remember ever having this issue before 138 / 140.
Edit: An additional curious fact, the drive that has always "disappeared" is the of HS / APFS one. The Windows drive never (at the moment). Maybe it was just coincidence, but maybe a problem with Velocity Duo + APFS ?
Last edited:
Could this be that Apple is try to get rid of all the 4,1 MacPro users who have flashed to a 5,1 firmware ?
Or are these failures also happening on 5,1 Mac Pro users.. ?