Is the 2kb difference enough to prohibit NVMe injection? I wouldn't think so personally, what do you think?
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
Is the 2kb difference enough to prohibit NVMe injection? I wouldn't think so personally, what do you think?
No, that's microcode space, not driver space.
You have to remove one of the microcodes, usually 206C0, if you need to add 106A4 microcode for some i7 and ES processors.
Well, that's good news (I think).
I actually expect that injecting the NVMe payload will work as usual. I'll wait until I hear back from @handheldgames before tampering though. If it doesn't work however, I'll just continue on with the 0089 firmware. I already get 5 GT/s and boot picker with my ATI card, so I don't think it will be a big issue to skip the firmware update if necessary in order to keep NVMe bootable.
I could be totally wrong, but from what I saw investigating the 138.0.0.0.0 binary and other things, Apple will get the firmware updates more dynamically for now on, the firmware changed a lot.
I found some interesting things but some of that seems covered in NDA until Mojave release. All the needed things still present, so not need to worry much. You still can easily personalise MP51.fd for example.
Last edited:
I have been wondering if this new firmware update affects how future updates will be delivered (ie will we still need to hold down the power button and enter programmers mode etc)
well from what we’ve seen it’s already changed a lot (non EFI firmware flashing)
I'm thinking about that too. One thing intrigued me a lot, seems some mechanism to update dynamically the firmware, maybe even downloading from Apple like XProtect/GateKeeper?
Maybe I'm crazy tired but with a daemon acting like ucupdate this is possible from now on with all the things Apple put in place today.
Last edited:
Can confirm that Sapphire Nitro+ OC RX 480 allowed for for firmware upgrade without boot screen of course, and also can confirm PCI-E link speed is now 5GT/s
Microcodes on High Sierra with 138.0.0.0.0, 0x1f = 31:
Microcodes on Mojave with 138.0.0.0.0:
Mojave DP7/PB6 has newer and bigger microcode.dat.
Microcodes on Mojave with 138.0.0.0.0:
Mojave DP7/PB6 has newer and bigger microcode.dat.
Last edited:
I think every card with installed driver now works 5GT/s. I'm curios about bootcamp side.Can confirm that Sapphire Nitro+ OC RX 480 allowed for for firmware upgrade without boot screen of course, and also can confirm PCI-E link speed is now 5GT/s
Yeah, maybe. Probably gonna have to wait for bootcamp drivers to be updated for it to reflect in Windows I would assume.
Following the usually developer install path, the full mojave b7 download is no longer pushed through the App Store. Apparently apple is preferring the software update process for full mojave downloads. A full download comes in at 5.x gb vs 3.x gb for the revision update..
Yeah, I don’t know how to get a full installer from the PB software applet. I didn’t seen any option to download, only upgrade was available AFAIK.
I got the full installer from dosdude’s Mojave Patch Tool.
Next time try with installinstallmacos.py, it's the same code as SUS replacement Reposado, made by Pixar people with a lot of Apple support.
I’ve used it before, I was just referring to the lack of a download option as opposed to an update only option in the PB.
I've cancelled the download and I'm now using dosdude's tool. I haven't been part of the discussions on the new python script.
It's not new, came from Reposado. Take a look on it latter, great code, used by every MacAdmin.
Last edited:
Agreed ! We need some adventurous cMP owner who is already NVMe M.2 booting with a spare motherboard and lot's of spare time to see whether the y can still boot to NVMe after the upgrade.
On the other hand . . perhaps in future Mojave betas we might even get native NVMe booting for cMP's - the 5.0 GT/s for the new AMD cards shows that our cMP's are being regarded as still being viable Apple machines.
If Mac Books /Mac Book Pro's still boot from NVMe with the new Mojave bootrom then perhaps all is well as they already have the . NVMe_DXE183.ffs don't they ?
EDIT : I'm not sure whether Mac Books / Mac Pro's / iMacs got the 138 bootrom
Personally, I will be watching future Mojave updates with great interest but I won't be installing it until it goes GM.
I'm very happy with being able to boot M.2 960 EVO into High Sierra 10.13.6.
The next few months should be interesting indeed.