Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Does anyone want to check the status of the GOP driver for the RX580/RX560 with this firmware?

On my MP3,1 the driver is loaded from the Option ROM of the RX580, however it doesn't link as it's seen as in "INVALID" driver. It's AMD GOP driver version 1.62.

I know for a fact that some 1.5xx drivers worked on the R9 280x for GOP boot screens, and I should have one of those cards shipping to me later today, so I can do some testing on my 3,1 to see if I can get later versions of the AMD GOP driver to work with boot screens.



If anyone would do a quick check, you'll need a UGA/EFI card installed as well as a card with a GOP rom on it, folks with nVidia cards should try too, just bless and boot a EFI Shell and find you mapped file system type:

drivers
drivers > driver.txt

https://drive.google.com/open?id=1Amfzy_0TWfdHS_R1RsOMbl1D2JA8vw8P

Just unzip that shell, mount your EFI partition and copy it there, then bless it for the next boot only.

Code:
diskutil list
/dev/disk1 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *500.1 GB   disk1

   1:                        EFI EFI                     209.7 MB   disk1s1

   2:                  Apple_HFS None                    9.9 GB     disk1s2

   3:                  Apple_HFS El Capitan              489.2 GB   disk1s3

   4:                 Apple_Boot Recovery HD             650.0 MB   disk1s4
mkdir /Volumes/EFI
sudo mount -t msdos /dev/disk1s1 /Volumes/EFI

Your EFI partition may not be disk1s1, just look for it in the list of the diskutil.

Copy the Shell to the EFI folder or the EFI/BOOT folder and bless it for the next boot.


Code:
sudo bless -mount /Volumes/EFI -file /Volumes/EFI/EFI/Boot/Shell64.efi     --setBoot  --nextonly --verbose

Reboot to the Shell and find were your EFI partition is mapped, likely FS1:

Code:
fs1:
ls

If you don't see the EFI folder, try fs0: or fs2:-fs9:.

The drivers > driver.txt will pipe the output of the drivers command to a text file on your EFI partition.
 
Last edited:
138.0.0.0.0 was able to boot both AHCI Sierra/Mojave on HFS+ and APFS.

No booting at all with NVMe on my machine. I may try again later to see if I overlooked something, but I don't expect a positive result.

Recapping how I installed.
Installed NVMe drive.
Booted from slow SATA II SSD with Mojave b6, I downloaded Beta 7, installed the firmware upgrade
Updated the operating system.
Attempted to boot with NVMe and failed.
Rebooted and tried to use ROMTool and failed.
Shutdown. Installed an Apple 512G SSUAX SSD with Sierra, copied necessary files for the flash across
Rebooted into Sierra, I backed up the 0138 ROM, injected the NVME_dxe.ffs and Flashed the new image.
Rebooted into Sierra dp7, the NVMe drives appeared with the modified bios. Selecting dp6 with nvme startup disk..
Rebooted into Sierra dp6 on the 970 pro nvme with dp6. SUCCESS. WELL SORT OF.

I guess I have not tried booting from nvme on dp7. That may be the issue you are encountering.
 
  • Like
Reactions: MIKX
Rebooted into Sierra dp7, the NVMe drives appeared with the modified bios. Selecting dp6 with nvme startup disk..
Rebooted into Sierra dp6 on the 970 pro nvme with dp6. SUCCESS. WELL SORT OF.
I am assuming you meant Mojave DP6 and Mojave DP7 here. Because Sierra wouldn't make sense to me.
 
Just to confirm, I downloaded the public beta of Mojave and went with the firmware update, all went well no boot screens as others have said. after rebooting I quit the installer to keep high Sierra until gm release. Booted into HS with my SAM 951 AHCI drive and all perfect.

I now have 5gt/s link speed on my RX580 which is nice to see, I don't use NVMe drives at the moment, I will wait to see what works on the GM release.

But a big thumbs up to apple for the update so far, if only they could release an update to allow NVMe drives.
 
Recapping how I installed.
Installed NVMe drive.
Booted from slow SATA II SSD with Mojave b6, I downloaded Beta 7, installed the firmware upgrade
Updated the operating system.
Attempted to boot with NVMe and failed.
Rebooted and tried to use ROMTool and failed.
Shutdown. Installed an Apple 512G SSUAX SSD with Sierra, copied necessary files for the flash across
Rebooted into Sierra, I backed up the 0138 ROM, injected the NVME_dxe.ffs and Flashed the new image.
Rebooted into Sierra dp7, the NVMe drives appeared with the modified bios. Selecting dp6 with nvme startup disk..
Rebooted into Sierra dp6 on the 970 pro nvme with dp6. SUCCESS. WELL SORT OF.

I guess I have not tried booting from nvme on dp7. That may be the issue you are encountering.

No. I followed a nearly identical path as you. The NVMe drive would not show up under boot-picker after all was said and done. Selecting NVMe boot under High Sierra (this is where I patched the 138 dumped BootRom) resulted in no boot. It hangs at white screen for a long time, then boots into the next available macOS drive.

Exact same result in Mojave. The machine just won't recognize that it's present until a full OS has loaded. The drivers take over from there and I can access the drive. I just can't boot it. PB6/DP7/High Sierra all give the same result.

I did an SMC/PRAM rest several times, no change.

I've been busy with bug reporting the lack of NVMe support today.

It seems that Feedback Assistant, Web Bug Reporter (Public and Developer) aren't connected and don't talk to each other even-though my login credentials are the same for each.

I file a comprehensive bug report using feedback assistant, then copied it to the other bug/feedback portals.

Hopefully they will decide to throw some goodwill our way on this issue.
 
I sincerely feel that people who are currently able to boot NVMe SSD's or M.2 blades in Sierra or High Sierra should hold off from upgrading the bootrom to 138.0.0.0 until we see what happens in future Mojave Betas.

I'm sure that dosdude1, handheldgames & crjackson2134 will prevail. :)
 
Last edited:
  • Like
Reactions: Stux
I sincerely feel that people who are currently able to boot NVMe SSD's or M.2 blades in Sierra or High Sierra should hold off from upgrading the bootrom to 138.0.0.0 until we see what happens in future Mojave Betas.

I'm sure that dosdude1 & handheldgames will prevail. :)

Booting Mojave on NVMe is not a problem at all. It's just that the firmware doesn't like the NVMe_DXE.ffs driver.

There was a problem when adding back the missing microcode on 0087 whereby the NVMe driver wouldn't work unless it was the last thing loaded. I might be a location problem. I don't know, not my Forte.

I'm version locked at MP51.0089.B00 w/NVMe until a solution presents. I won't stop me from booting Mojave from NVMe at present. However, if they start slipping unexpected firmware upgrades through a normal OS install, it could BECOME a problem.
 
  • Like
Reactions: handheldgames
No. I followed a nearly identical path as you. The NVMe drive would not show up under boot-picker after all was said and done. Selecting NVMe boot under High Sierra (this is where I patched the 138 dumped BootRom) resulted in no boot. It hangs at white screen for a long time, then boots into the next available macOS drive.

Exact same result in Mojave. The machine just won't recognize that it's present until a full OS has loaded. The drivers take over from there and I can access the drive. I just can't boot it. PB6/DP7/High Sierra all give the same result.

I did an SMC/PRAM rest several times, no change.

I've been busy with bug reporting the lack of NVMe support today.

It seems that Feedback Assistant, Web Bug Reporter (Public and Developer) aren't connected and don't talk to each other even-though my login credentials are the same for each.

I file a comprehensive bug report using feedback assistant, then copied it to the other bug/feedback portals.

Hopefully they will decide to throw some goodwill our way on this issue.

Wanna do some troubleshooting? If yes, try to inject on the DP7 MP51.fd and check if you can boot from the NVMe drive - you will loose access to iCloud/FaceTime/iMassage but will narrow down the problem.

If the injected MP51.fd work, I’ll need some info from your Mac by PM to send you a full working and personalized bootROM.
[doublepost=1534272401][/doublepost]Off-topic:

Post here from Safari on iPhone is a test of patience if you need to edit something.
 
Last edited:
Wanna do some troubleshooting? If yes, try to inject on the DP7 MP51.fd and check if you can boot from the NVMe drive - you will loose access to iCloud/FaceTime/iMassage but will narrow down the problem.

If the injected MP51.fd work, I’ll need some info from your Mac by PM to send you a full working and personalized bootROM.
[doublepost=1534272401][/doublepost]Off-topic:

Post here from Safari on iPhone is a test of patience if you need to edit something.

Read your PM
 
I am assuming you meant Mojave DP6 and Mojave DP7 here. Because Sierra wouldn't make sense to me.

Proofing my earlier post.

Recapping how I installed.
Installed NVMe drive.
Booted from slow SATA II SSD with Mojave b6, I downloaded Beta 7, attempted to backup efi and failed. Romtool no longer works in dp6 dp7.
Booted into Sierra and backed up 0089 rom.
Rebooted into Mojave dp6 and downloaded dp7
installed the firmware upgrade.
Updated the operating system.
Attempted to boot with NVMe and failed.
Tried to use ROMTool and failed with an error.
Rebooted into Sierra, I backed up the 0138 ROM, injected the NVME_dxe.ffs and Flashed the new image.
Rebooted into Mojito dp7, the NVMe drives appeared with the modified bios. Selecting dp6 with nvme startup disk..
Rebooted into Mojave dp6 on the 970 pro nvme with dp6. SUCCESS. WELL SORT OF.

I never booted in dp7. That’s the sort of.

It’s been a busy day.
 
  • Like
Reactions: crjackson2134
Okay, I did some benchmark testing pre bootRom patch and after.

My specs
  • Mac Pro 2010 5,1
  • 12 core X5690
  • Sapphire Nitro RX480 4GB
  • 48 GB, removed two sticks to get tripple channel
  • Bootrom 89
  • Mac Os 10.13.6
  • Windows 10 Pro 1803

I ran the following benchmark apps on Mac OS and 1 on Windows 10 (1803), I did 3 runs pre and 3 runs after.
  • Unigine Valley
  • Cinebench R15.038
Now that 5GT/s is enabled I get better results, not a big difference, but still some.
However under Windows GPU-z it still reports as pcie 1.1 After a complete shutdown it reports 2.0 speed.

qcrAj4W.png


Unigine Valley (Mac Os)

Pre Bootrom
JM1W8AQ.png


Post Bootrom
pYjIJV8.png


Cinebench R15 (Mac Os)

Pre Bootrom
r8v2g3A.png


Post Bootrom
CMzVJor.png


Unigine Valley (Windows 10 Pro)

Pre Bootrom
4hnzDXR.png


Post Bootrom
K9cpw0y.png
 
Last edited:
I think cpuz shows 1.1 as long as there is no load on the gpu. Reopen cpuz during a benchmark perhaps it will show 2.0.
Okay, I did some benchmark testing pre bootRom patch and after.

My specs
  • Mac Pro 2010 5,1
  • 12 core X5690
  • Sapphire Nitro RX480 4GB
  • 48 GB, removed two sticks to get tripple channel
  • Bootrom 89
  • Mac Os 10.13.6
  • Windows 10 Pro 1803

I ran the following benchmark apps on Mac OS and 1 on Windows 10 (1803), I did 3 runs pre and 3 runs after.
  • Unigine Valley
  • Cinebench R15.038
Now that 5GT/s is enabled I get better results, not a big difference, but still some.
However under Windows GPU-z it still reports as pcie 1.1 After a complete shutdown it reports 2.0 speed.

qcrAj4W.png


Unigine Valley (Mac Os)

Pre Bootrom
JM1W8AQ.png


Post Bootrom
pYjIJV8.png


Cinebench R15 (Mac Os)

Pre Bootrom
r8v2g3A.png


Post Bootrom
CMzVJor.png


Unigine Valley (Windows 10 Pro)

Pre Bootrom
4hnzDXR.png


Post Bootrom
K9cpw0y.png
ry
 
I think cpuz shows 1.1 as long as there is no load on the gpu. Reopen cpuz during a benchmark perhaps it will show 2.0.

ry

The spacey thing on the right of the screenshot is a function of GPU-Z where it fully utilize the GPU. After a complete shutdown of my Mac it reported correctly to 2.0.

I updated the screenshot.
 
Alright.. Mojave dp6 is upgrading to dp7 on a 970 pro nvme. About 31 minutes remaining. Lets see if it survives the reboot. I have a feeling it will be ok. Although I could be wrong.

Edit: Mojave boots from NVMe in DP7
 
Last edited:
Alright.. Mojave dp6 is upgrading to dp7 on a 970 pro nvme. About 31 minutes remaining. Lets see if it survives the reboot. I have a feeling it will be ok. Although I could be wrong.

Edit: Mojave boots from NVMe in DP7

Still working on mine. Finally got it to boot by injecting the NVMe into the firmware included in the Mojave package instead of dumping.

@tsialex found my NVRAM somehow ended up with double entries for the NVMe section.

Went with firmware from Apple package, and now manually inputing missing SN's and iCloud info.

You wouldn't believe all the crazy/bizzar booting behavior this thing had. Every time I would select a different startup disk, it would post, start to boot, then loop again and finally boot to desired drive.

Injecting directly into the packaged firmware totally fixed all that. I've go some questions for @tsialex when this is all finished and working, but we may need to come up with a new flashing protocol. I'm thinking if we inject the firmware in the package directly, the Apple flasher my preserve the user info that's in NVRAM and eliminate dumping. That may be the new flavor of the day.
 
Last edited:
Still working on mine. Finally got it to boot by injecting the NVMe into the firmware included in the Mojave package instead of dumping.

@tsialex found my NVRAM somehow ended up with double entries for the NVMe section.

Went with firmware from Apple package, and now manually inputing missing SN's and iCloud info.

It’s more complicated than that, somehow the entire NVRAM was duplicated, the full partition with all the info. I can’t even know how you could do that…
 
Last edited:
  • Like
Reactions: Synchro3
crjackson2134
Still working on mine. Finally got it to boot by injecting the NVMe into the firmware included in the Mojave package instead of dumping.
Injecting directly into the packaged firmware totally fixed all that.
WOW ! Absolute brilliant deduction Sherlock ! Why didn't I think of that ?
If your fix stays consistent throughout the beta program right up to 10.14 GM the NVMe booting problem is solved for Mojave.

Well done indeed.
 
  • Like
Reactions: crjackson2134
@handheldgames

On consecutive 2nd reboot into same drive, it's back to normal booting. No added delay...

The only time a delay is added for me now, is when I switch to another boot drive. First boot to said drive is delayed. If I'm working with that drive and need to boot again cold or restart, no more delay for me.

I'm very happy with it's current boot performance, if it stays the same after reconstruction of user data I have no qualms at all.
[doublepost=1534291229][/doublepost]
crjackson2134

WOW ! Absolute brilliant deduction Sherlock ! Why didn't I think of that ?
If your fix stays consistent throughout the beta program right up to 10.14 GM the NVMe booting problem is solved for Mojave.

Well done indeed.

@tsialex gets all the credit. I injected the firmware here, he tested on his own machine and inspected the contents. I sent along other versions of injected firmware for comparison. @tsialex is the real inspector Sherlock, I wouldn't have a clue upon inspecting anything in the NVRAM.
 
@handheldgames

On consecutive 2nd reboot into same drive, it's back to normal booting. No added delay...

The only time a delay is added for me now, is when I switch to another boot drive. First boot to said drive is delayed. If I'm working with that drive and need to boot again cold or restart, no more delay for me.

I'm very happy with it's current boot performance, if it stays the same after reconstruction of user data I have no qualms at all.
It’s not the user data, that’s the private part of the NVRAM and macOS will populate that later, it’s the Mac Pro identity:

SSN = SystemSerialNumber
HWC = forgot what’s that acronym ;)
SON = SystemOrderNumber
LBSN = LogicBoardSerialNumber
[doublepost=1534291497][/doublepost]
Is the error in any of your backup ROM's? Personally, I suspect the new EFI flash process from Apple. It's new code for a platform from 2009 in a beta release. This could be a bug.
Nope, the error started with MP51.0089.B00 or earlier than that. Nothing with 138.0.0.0.0, but the crazy showed itself after the upgrade.
 
Last edited:
  • Like
Reactions: h9826790
It’s not the user data, that’s the private part of the NVRAM and macOS will populate that latter, it’s the Mac Pro identity:

SSN = SystemSerialNumber
HWC = forgot what’s that acronym ;)
SON = SystemOrderNumber
LBSN = LogicBoardSerialNumber
[doublepost=1534291497][/doublepost]
Nope, the error started with MP51.0089.B00 or earlier than that. Nothing with 138.0.0.0.0, but the crazy showed itself after the upgrade.

I meant user data as all inclusive. I don't know all those acronyms either. That's why I just said user data. I should have said machine data, but I knew what it was mostly including. Poor choice of words in my post.
 
It’s not the user data, that’s the private part of the NVRAM and macOS will populate that latter, it’s the Mac Pro identity:

SSN = SystemSerialNumber
HWC = forgot what’s that acronym ;)
SON = SystemOrderNumber
LBSN = LogicBoardSerialNumber
[doublepost=1534291497][/doublepost]
Nope, the error started with MP51.0089.B00 or earlier than that. Nothing with 138.0.0.0.0, but the crazy showed itself after the upgrade.
Btw, I only found the duplicated NVRAM after I checked everything on UEFITool and found nothing, then I started analyzing with binwalk and got the problem at the first glance.
 
Is the error in any of your backup ROM's? Personally, I suspect the new EFI flash process from Apple. It's new code for a platform from 2009 in a beta release. This could be a bug.

I first noticed strange booting anomalies after flashing 0087. It was so bad, that I had to downgrade to 0085.

I didn't inject anything at all until 0089. I think it may have already been somewhat corrupted by the 0087 flash. I don't know for sure.
 
  • Like
Reactions: handheldgames
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.