Cool! Thanks, I was worriedthe RX 560 is a 8x PCIe card not 16x so your Speeds look to be correct for 8x 5GTs
Cool! Thanks, I was worriedthe RX 560 is a 8x PCIe card not 16x so your Speeds look to be correct for 8x 5GTs
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.
Handheldgames is testing it right now, so we’ll know soon.
I've backed up the 0089 ROM, installed the 138 upgrade and Mojave is finishing it's install on a SATA II SSD. Once Mojave Boots, I'll add nvme.ffs to the rom and install the Highpoint SSD7101a / 970 Pro to test out NVMe
Anyone checked for NVMe on 138.0.0.0.0? I forgot to do that.Fingers crossed...
Anyone checked for NVMe on 138.0.0.0.0? I forgot to do that.
Paraphrasing, forgot to check 138.0.0.0.0 for native NVMe support.See above post.
Use it on 10.13.6, I've downgraded from 138.0.0.0.0 to MP51.0089.B00 with ROMTool earlier.Upgrading to Beta 7, ROMTool no longer works. DirectHW.kext cannot load.
I have absolute confidence in dosdude1's ability to deal with thisUpgrading to Beta 7, ROMTool no longer works. DirectHW.kext cannot load.
Apple is changing dramatically the MP5,1 firmware. If they implement signing/certificates, like on iMac Pro and MacBook Pro 2018, adieu firmware mods. So it's really important to bug Apple to include NVMe natively.I have absolute confidence in dosdude1's ability to deal with this
Apple is changing dramatically the MP5,1 firmware. If they implement signing/certificates, like on iMac Pro and MacBook Pro 2018, adieu firmware mods.
BTW, I'd never even hoped that Apple changed the BootROM like they did today.
Time to bug Apple to include NVMe natively.If they would give us NVMe it wouldn’t even matter, they created the situation to begin with.
That said, I’ll stick with the newest, moddable version. If I have to lock it down, so be it for now.
Time to bug Apple to include NVMe natively.
Other people need to keep pressure, not people who already did the request. Even if Apple will respond as duplicate, it will show on QA.Yeah, I did already, so what happens if you keep filing a bug report on the same thing?
Other people need to keep pressure, not people who already did the request. Even if Apple will respond as duplicate, it will show on QA.
Use it on 10.13.6, I've downgraded from 138.0.0.0.0 to MP51.0089.B00 with ROMTool earlier.
I've booted into sierra to mod the rom. Currently booting into Mojave on a SATA II SSD. I should be able to restart from NVMe
L O N G - D R U M R O L L .....
EDIT:
We're good for now. That Google doc sure comes in handy.
When switching from Mojito to HS, progress bar time always increases. Restart in HS, then do full shutdown, then startup in HS should be normal.
When switching from Mojito to HS, progress bar time always increases. Restart in HS and set the startup disk to HS, then do full shutdown, then startup in HS should be normal.
[doublepost=1534215227][/doublepost]
Yeah, I have it on my desktop...
Every time I switch away from Mojave to another OS version, it loads slower until I’ve made 2 consecutive boots into the same OS/SSD Drive. I don’t think this is related to NVMe, and possibly not even this firmware. Mine has been doing that since day 1 with switching from SATA to M.2 booting. For me it started Long before I went NVMe.
[doublepost=1534216202][/doublepost]Did you try booting the stock 138 on NVMe to confirm no native support?