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.

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,602
Perfect, we should meet for a business lunch one of those days in 2019... :)

Last question here for finding the ultimate Mojave solution:

- If I get a Quadro K5000 Mac edition in slot 1&2, it would give me Mojave capability. Check
- Moving my current Nvidia 980Ti in slot 3&4 with the Pixlas power cable should work as well. Check
- That leaves me with one open PCI slot (5) for a I/O Crest SP_Pex40129 card to move my two PCIe SSDs on there.
My USB card would need to be scraped, or going for an expensive netsor PCI expansion chassis.

In Windows I guess I would have still the power of the 980Ti with the "right configuration" for games using the 980Ti
On the OSX side I could Use the 980TI for Resolve in Mojave.

This might be better then a solo VEGA64 because of missing bootscreens and missing bootcamp and gimped apple encoding.

Do think this config would be feasable, did I forget something?

I don't think you can use 980Ti without drivers as a CUDA card, for Mojave, any NVIDIA card newer than Kepler just don't exist for Apple native NVIDIA drivers.

Quadro K5000 will only occupy Slot-1, the double space one, like GTX-680. Mac Pro don't have 5 slots, just 4

I don't have experience with the Windows side of it, but seems reasonable.

AMD or NVIDIA, HEVC encoding/decoding support is the same, no diff.

This is interesting setup questions, but way off topic for this thread, if you have more questions, please open a dedicated thread. Let's keep on the BootROM topic here.
 
  • Like
Reactions: h9826790

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,602
After more than a hundred BootROMs reconstructed, I was thinking that I wouldn't find anything new. I was wrong:

Screen Shot 2018-12-08 at 16.51.08.png


I saved the second gzip compressed blob and tried to extract with gunzip, no go:

Screen Shot 2018-12-08 at 17.16.48.png


I'm going to investigate what the heaven is this two weird gzip compressed data blobs into the 1st and 2nd NVRAM streams.
 

orph

macrumors 68000
Dec 12, 2005
1,884
393
UK
hay just want to check if my rom is safe for the update or not
i used the romtool and chose the auto selected rom so hope thats correct

Code:
DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
0             0x0             UEFI PI firmware volume
16524         0x408C          UEFI PI firmware volume
24972         0x618C          CRC32 polynomial table, little endian
35787         0x8BCB          mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
49948         0xC31C          UEFI PI firmware volume
524288        0x80000         UEFI PI firmware volume
540812        0x8408C         UEFI PI firmware volume
549260        0x8618C         CRC32 polynomial table, little endian
560075        0x88BCB         mcrypt 2.2 encrypted data, algorithm: blowfish-448, mode: CBC, keymode: 8bit
574236        0x8C31C         UEFI PI firmware volume
1048576       0x100000        UEFI PI firmware volume
1114112       0x110000        UEFI PI firmware volume
1187379       0x121E33        Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1252915       0x131E33        Certificate in DER format (x509 v3), header length: 4, sequence length: 986
1343511       0x148017        bzip2 compressed data, block size = 100k
1376256       0x150000        UEFI PI firmware volume

is it safe for me to update?

edit
ok this is an example of a not safe to update rom, so if you have the same as me it's not ok to d the firmware update!
 
Last edited:

adam9c1

macrumors 68000
May 2, 2012
1,890
315
Chicagoland
Not certain if this was posted before.

I’ve attempted to apply the 140 boot rom by extracting the recovery partition installer.

This still did not trigger the firmware update screen like we saw earlier with the APFS conversions.

I powered down, and powered up holding the button until the beep sound.

I think I’ll put this into notes somewhere as I forgot this step.

I now have a cMP 2009 4,1 flashed to 5,1 and 140. On Mojave.
 

Mordaz

macrumors newbie
Dec 13, 2018
7
0
Hi dude...

I just want to upgrade my 5.1 to 1.40 but i don't have a Metal card.
I have been following your comments, and i have realized it is possible with the macOSUpd10.14.1.RecoveryHDUpdate.pkg, unfortunately it is not available anymore.
I've tried with the macOSUpd10.14.RecoveryHDUpdate.pkg, following your instructions, but it DOES ask for a metal card.
Could you send me an actual link to download macOSUpd10.14.1.RecoveryHDUpdate.pkg ?
Please.

Thanks!
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,602
Hi dude...

I just want to upgrade my 5.1 to 1.40 but i don't have a Metal card.
I have been following your comments, and i have realized it is possible with the macOSUpd10.14.1.RecoveryHDUpdate.pkg, unfortunately it is not available anymore.
I've tried with the macOSUpd10.14.RecoveryHDUpdate.pkg, following your instructions, but it DOES ask for a metal card.
Could you send me an actual link to download macOSUpd10.14.1.RecoveryHDUpdate.pkg ?
Please.

Thanks!
You are mistaken, it’s not possible to upgrade to 138/139/140.0.0.0.0 without a METAL supported GPU.

The only workaround for the efi2flasher METAL support requirement is reconstructing the BootROM with intermediate files.
 
Last edited:

Mordaz

macrumors newbie
Dec 13, 2018
7
0
Ups.
Thank you for the info.
By the way... i just have a GT120 and i did upgrade to 1.39, it doesn't require Metal GPU.
Anyway, thank you dude, i'll look for a Metal card!
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,602
Ups.
Thank you for the info.
By the way... i just have a GT120 and i did upgrade to 1.39, it doesn't require Metal GPU.
Anyway, thank you dude, i'll look for a Metal card!
How did you did the upgrade? efi2flasher only works with a METAL supported GPU.
 
Last edited:

Mordaz

macrumors newbie
Dec 13, 2018
7
0
I just installed a clean HighSierra from a USB, and it asked me to make a firmware upgrade to 1.39
I did it on 3 machines and it's the same. All of them with nVidia GT120.
As long as i know, Metal is only required for 1.40 ☹
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,602
I just installed a clean HighSierra from a USB, and it asked me to make a firmware upgrade to 1.39
I did it on 3 machines and it's the same. All of them with nVidia GT120.
As long as i know, Metal is only required for 1.40 ☹
No, you are mistaken again. 10.13.6 BootROM is MP51.0089.B00. This one needs an EFI GPU.

139.0.0.0.0 was never released as public BootROM, only people who have AppleSeed/Public betas access could kickstart the install via RecoveryUpdate and it's a beta BootROM from Mojave 10.14.1 Developer Previews/Public Betas. It's Apple efi2flasher for Mojave that ultimately do the upgrade and it requires a METAL supported GPU to flash the firmware.

I've updated the first post for 10.14.2 RecoveryUpdate link, btw.
 
Last edited:
  • Like
Reactions: Reindeer_Games

Mordaz

macrumors newbie
Dec 13, 2018
7
0
Now i'm a little confused. Can you help me? Which firmware do i have?
I post you a pic with the hardware report...
 

Attachments

  • Capture.png
    Capture.png
    33.4 KB · Views: 272

Mordaz

macrumors newbie
Dec 13, 2018
7
0
THANKSSSS!!!!
I'll look for a Metal card and make the upgrade.
Then i'll ask you again to very the firmware rom.
Thanks bro!!!
(by the way, where did you find the firmware version?)
 

Mordaz

macrumors newbie
Dec 13, 2018
7
0
I have that firmware. I'll try to upgrade asap.
Tell me why 087 is so infamous!? I'm worried!
Thanks!
 

TheIguana

macrumors 6502a
Sep 26, 2004
678
492
Canada
I have that firmware. I'll try to upgrade asap.
Tell me why 087 is so infamous!? I'm worried!
Thanks!

There appears to be a tendency that the EFI in those Mac Pro's has been corrupted and thus bricked during subsequent firmware upgrades.
 

PossiblyJP

macrumors newbie
Dec 15, 2018
17
6
Have a MacPro 4,1 upgraded to 5,1. Latest Mojave, firmware is @ 140. Just put in a WD Black 1GB (in an Angelbird Wings PX1). Its in slot 3. Boots just fine, but only getting about 760 MB/s read and write. I would expect about twice that. System report confirms 4x and 5GT/s and TRIM is on.

Any ideas why its running at about half speed?
 
Last edited:

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,602
Have a MacPro 4,1 upgraded to 5,1. Latest Mojave, firmware is @ 140. Just put in a WD Black 1GB (in an Angelbird Wings PX1). Its in slot 3. Boots just fine, but only getting about 760 MB/s read and write. I would expect about twice that. System report confirms 4x and 5GT/s and TRIM is on.

Any ideas why its running at about half speed?
Some WD Black are PCIe 3.0 x2 and get only 750MB/s into a Mac Pro. Check exactly what model you have.

The correct thread is Blade SSDs - NVMe & AHCI
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.