I don't think that we know enough about what is causing this to make a hypothesis. Anyone dumped the problematic 140.0.0.0.0?
I dumped it prior to the 144.0.0.0.0 upgrade. I can send it to you on Tuesday when I am back at work.
I don't think that we know enough about what is causing this to make a hypothesis. Anyone dumped the problematic 140.0.0.0.0?
Thx!I dumped it prior to the 144.0.0.0.0 upgrade. I can send it to you on Tuesday when I am back at work.
I still think it has something to do with jumping directly from 140.0.0.0.0 to 144.0.0.0.0. Seems that almost everyone having this problem (including myself) skipped the 141.0.0.0.0 bootrom that was released with 10.14.4.
You will have to suck it up and install onto a SATA drive if you want to install 144.0.0.0.0
I have the Kryo m.2 PCIe adapter running a 970Pro NVME drive. I went directly from 140 to 144 without a problem.
Yeah, sounds like it's not a straightforward cause. Is yours an authentic 5,1 or was it a 4,1 flashed to 5,1?
Anyway, let's try to consolidate this discussion to the dedicated thread for it so people don't have to hunt around for data points and info: https://forums.macrumors.com/thread...0-0-0-0-to-144-0-0-0-0-does-not-work.2182219/
I had no issues going from 140 to 144. I downloaded the full installer from the AppStore and upgraded the firmware that way.I still think it has something to do with jumping directly from 140.0.0.0.0 to 144.0.0.0.0. Seems that almost everyone having this problem (including myself) skipped the 141.0.0.0.0 bootrom that was released with 10.14.4.
You will have to suck it up and install onto a SATA drive if you want to install 144.0.0.0.0
I had no issues going from 140 to 144. I downloaded the full installer from the AppStore and upgraded the firmware that way.
Apologies alex, but what do you mean by 10.15 blocking mp5.1, have I missed some news?Even with 10.15 blocking MP5,1, I checked for new firmwares. No Mac got a firmware upgrade with 10.15 19A471t.
We missed the cutoff 2013 and newer Mac Pros.Apolgies alex, but what do you mean by 10.15 blocking mp5.1, have I missed some news?
Apologies alex, but what do you mean by 10.15 blocking mp5.1, have I missed some news?
No sweat, just change that ... We are about to enter Hackintosh territory with this one.
No sweat, just change that ... We are about to enter Hackintosh territory with this one.
I'm a little surprised ours don't support it. I guess I can see why Apple wouldn't want to officially support us given they finally have a new Mac Pro out, but as long as we have metal cards, I'm not sure what is stopping us from installing it. 2012 Macbookpros etc and 2012 iMacs are all compatible, what does there's have that we don't?
I wouldn't be surprised if "unofficially" we're able to install it. Although we won't get anymore firmware upgrades, but I appreciate Apple for still upgrading our firmware so far.
Great great point. Why would Apple want to support something that has security vulnerabilities. Apple would then need to spend time trying to patch Intel's problems. For them, there's no reason to do so.BLAME INTEL. The lack of microcode updates for all MP5,1 issued CPUs for the recent vulnerabilities are likely the main reason 10.15 will officially be unsupported.
MP5,1: Catalina Developer Preview works, more or less…Great great point. Why would Apple want to support something that has security vulnerabilities. Apple would then need to spend time trying to patch Intel's problems. For them, there's no reason to do so.
For us Mac Pro 5,1 fans, hold out hope. I believe we'll be able to install it unofficially, as everything I've read and saw if it supports Mojave it supports Catalina.
Mac: | EFI version: |
---|---|
IM13,1 | 286.0.0.0.0 |
IM14,1 | 138.0.0.0.0 |
IM14,2 | 138.0.0.0.0 |
IM14,3 | 138.0.0.0.0 |
IM14,4 | 198.0.0.0.0 |
IM15,1 | 229.0.0.0.0 |
IM16,1 | 228.0.0.0.0 |
IM16,2 | 228.0.0.0.0 |
IM17,1 | 168.0.0.0.0 |
IM18,1 | 173.0.0.0.0 |
IM18,3 | 173.0.0.0.0 |
IM19,1 | 220.270.076.0.0 |
MB10,1 | 176.0.0.0.0 |
MB8,1 | 182.0.0.0.0 |
MB9,1 | 182.0.0.0.0 |
MBA5,1 | 258.0.0.0.0 |
MBA6,1 | 116.0.0.0.0 |
MBA7,1 | 187.0.0.0.0 |
MBP10,1 | 256.0.0.0.0 |
MBP10,2 | 279.0.0.0.0 |
MBP11,1 | 155.0.0.0.0 |
MBP11,2 | 155.0.0.0.0 |
MBP11,4 | 193.0.0.0.0 |
MBP12,1 | 185.0.0.0.0 |
MBP13,1 | 234.0.0.0.0 |
MBP13,2 | 257.0.0.0.0 |
MBP13,3 | 257.0.0.0.0 |
MBP14,1 | 196.0.0.0.0 |
MBP14,2 | 196.0.0.0.0 |
MBP14,3 | 196.0.0.0.0 |
MBP9,1 | 227.0.0.0.0 |
MM6,1 | 279.0.0.0.0 |
MM7,1 | 243.0.0.0.0 |
MP5,1 | 144.0.0.0.0 |
MP6,1 | 131.0.0.0.0 |
$IBIOSI$ MP61.88Z.F000.B00.1905251553
Copyright (c) 2005-2019 Apple Inc. All rights reserved.
Apple ROM Version
Model: MP61
EFI Version: 131.0.0.0.0
Built by: root@saumon
Date: Sat May 25 15:53:29 PDT 2019
Revision: 131 (B&I)
ROM Version: F000_B00
Build Type: Official Build, Release
Compiler: Apple clang version 3.0 (tags/Apple/clang-211.10.1) (based on LLVM 3.0svn)
All Macs had firmware upgrades except MP5,1
Interesting, firmware itself wasn't updated, but the efiflasher was. Maybe Cupertino devs corrected the firmware update problems?!?
[doublepost=1560275762][/doublepost]Another side channel vulnerability announced today, RAMBleed, a variant of the previous Rowhammer that defeats ECC.
https://arstechnica.com/information...hammer-bitflips-to-steal-2048-bit-crypto-key/