MP 1,1-5,1 MacPro5,1: BootROM thread | 144.0.0.0.0

[goMac]

while other RX 580s (and even some Pulse RX 580s which had diffrent PNs) have to make do with a generic frame-buffer, is that screen shot on the latest Mojave Beta or? im trying to work out if Apple is giving more RX 580s proper frame-buffer personalities

Is there any significance to this? I did some searching around but I didn't find anyone talking specifically about the difference. I don't have a Pulse so I have the generic framebuffer, but I don't know what the difference actually is.

 

[tsialex]

Is there any significance to this? I did some searching around but I didn't find anyone talking specifically about the difference. I don't have a Pulse so I have the generic framebuffer, but I don't know what the difference actually is.

We can use that new Orinoco frame-buffer personality with the generic RX480/RX580 cards, but it's early to speculate.
[doublepost=1534297141][/doublepost]

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.

BTW, I know that HWC is the <configCode> from System Profiler, Hardware Wsomething Code.

Anyone knows what's the W stands for on that acronym?

 

[crjackson2134]

HardWareCode

?????

 

[tsialex]

HardWareCode

?????

Can be it.

SystemProfiler dumps the 4digit code from the BootROM, do a query on Apple servers, gets the name/model of the Mac and then store/cache the result on:

~/Library/Preferences/com.apple.SystemProfiler.plist

Example:

HWC = F501
<configCode>Mac Pro Server (Mid 2012)</configCode>

If you ever noticed on the first time you open About This Mac after a new macOS install, a little delay on the screen showing the model of the Mac, it's the System Profiler doing the query on the Apple server for the qualified name/model of the Mac.

 

[LightBulbFun]

Can be it.

SystemProfiler dumps the 4digit code from the BootROM, do query on a Apple server, gets the name/model of the Mac and then store/cache the result on:

~/Library/Preferences/com.apple.SystemProfiler.plist

Example:

HWC = F501
<configCode>Mac Pro Server (Mid 2012)</configCode>

If you ever noticed on the first time you open About This Mac after a new macOS install, a little delay on the screen showing the model of the Mac, it's the System Profiler doing the query on the Apple server for the qualified name/model of the Mac.

its also worth noting that in pre 2011ish Macs the code is just the last 3 digit of the the Serial No.

Is there any significance to this? I did some searching around but I didn't find anyone talking specifically about the difference. I don't have a Pulse so I have the generic framebuffer, but I don't know what the difference actually is.

a frame-buffer personality is basically a thing that tells OS X exactly what ports the video card has and how they are laid out and how they are to be configured (this goes back all the way to the PowerPC days)

when running a PC card, OS X will dynamically look at the VBIOS of the card and try and make a frame-buffer personality for the card we call this the Generic frame-buffer personality, while it works well for the most part, it has had its fair share of issues, especially around multi-display support

so when possible its preferable to have a proper pre-defined frame buffer personality for your card, however if you apply the wrong personality to your card or one that does not match your port layout then you can end up with many issues including some ports not working out right (for example the HDMI port on a Flashed ATI Radeon 7870 stops working, since the 7870 ROM uses the 7950 header which uses the Hamachi personality, ideally we would use the Futomaki personality for the 7870 if we could)

(For this reason the Orinoco personality should only be used with Pulse Radeon RX 580s or at least only with cards that have the same port layout as the Pulse RX 580)

 

[David403]

Man, this is like Christmas morning hoping that Santa brought you a 10-speed bike and then opening the box to find socks and underwear.

I mean, that's great that we got any sort of update. It's definitely an improvement to be able to flash firmware without an EFI GPU, and it's great we've got the newest microcode now. Plus, I guess the 5GT/S thing matters to some people, even though it doesn't seem to make any real world difference. But it's the boot screens that I think many of us feel is the number one problem hamstringing the cMP at this point... not just for FV2 but also for switching between bootcamp and back.

Since this is just version 0 of the new firmware version scheme, I remain somewhat hopeful that Apple isn't done improving it.

Edit: And I guess I don't even know if it's possible to load an EFI driver for the 560 & 580 in the cMP firmware itself, or if it would strictly require a new firmware on the card. Is there enough free "space" in the cMP firmware to hold a GPU EFI driver? I have no idea.

But I hope (and suspect) that Apple will have another Firmware update with GM or final release 10.14.0 that will give boot screen, boot selector, and enable file-vault on the non-Apple yet Apple recommended metal-capable GPUs.

I can't believe they would restrict security on their latest OS using their approved hardware ??

(Although Tim Cook did just handover all of Paul Manafort's iCloud account to Mueller!) - so much for Apple security a al San Bernardino. No mainstream or it security coverage of that one !

 

[h9826790]

Has anyone tried this bootrom on a 4.1 - 5.1 fw upgrade ? I guess it works but you never know...

It’s been tested, look at those screenshots, some are actually from

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.

Did you try inject the NVMe into the installer’s “clean” firmware, and then use the installer’s updater to flash it back into your Mac? So that it can automatically fix those S/N etc for you (assume you manually flash your own 0089.B00 back in)

For testing purpose, if possible. Please try

1) flash the “original” 0089.B00 back in (has your cMP serial number, but no MVMe injection.

2) PRAM reset

3) use the new installer updater to flash the NVMe injected but “clean” (not serial number) 138.0.0.0.0

Million thanks in advance.

 

[tarizo41]

download installinstallmacos.py from GitHub, run with

sudo python installinstallmacos.py

Select 18A365a, with for 6GB+ download, it will create a sparse image with Mojave DP7 installer.

I made all that but when I launch the installer , I got a message indicating that i can install Mojave only if all my graphics card are metal supported..II got a macro 4,1 > 5,1 with an original radeon 5870 apple edition...is it normal ? thanks in advance

 

[tsialex]

I made all that but when I launch the installer , I got a message indicating that i can install Mojave only if all my graphics card are metal supported..II got a macro 4,1 > 5,1 with an original radeon 5870 apple edition...is it normal ? thanks in advance

Your GPU is unsupported. You need to replace it for a Metal one. Take a look on the Mojave supported computers:

What Mac computers are supported?
macOS Mojave supports:

• MacBook (Early 2015 or newer)
• MacBook Air (Mid 2012 or newer)
• MacBook Pro (Mid 2012 or newer)
• Mac mini (Late 2012 or newer)
• iMac (Late 2012 or newer)
• iMac Pro (2017)
• Mac Pro (Late 2013, plus mid 2010 and mid 2012 models with recommended Metal-capable GPU, including MSI Gaming Radeon RX 560 and Sapphire Radeon PULSE RX 580)

https://beta.apple.com/sp/betaprogram/faq
[doublepost=1534328468][/doublepost]

It’s been tested, look at those screenshots, some are actually from


Did you try inject the NVMe into the installer’s “clean” firmware, and then use the installer’s updater to flash it back into your Mac? So that it can automatically fix those S/N etc for you (assume you manually flash your own 0089.B00 back in)

For testing purpose, if possible. Please try

1) flash the “original” 0089.B00 back in (has your cMP serial number, but no MVMe injection.

2) PRAM reset

3) use the new installer updater to flash the NVMe injected but “clean” (not serial number) 138.0.0.0.0

Million thanks in advance.

In @crjackson2134 specific case, it will not work. His NVRAM partition is duplicated since at least MP51.0089.B00 and reseting it only resets the first one. The problem propagates with the firmware upgrade, checked his backup BootROM dumps for MP51.0089.B00 and 138.0.0.0.0.

 

[tarizo41]

Your GPU is unsupported. You need to replace it for a Metal one. Take a look on the Mojave supported computers:



https://beta.apple.com/sp/betaprogram/faq
[doublepost=1534328468][/doublepost]

In @crjackson2134 specific case, it will not work. His NVRAM partition is duplicated since at least MP51.0089.B00 and reseting it only resets the first one.

Thank you . I just thought that I could update the firmware without completing the installation of Mojave. Thanks again

 

[tsialex]

Thank you . I just thought that I could update the firmware without completing the installation of Mojave. Thanks again

The macOS Mojave installer app checks the GPU before letting you upgrade the BootROM, you can manually upgrade but since we have at least 5 or more suspected cases of SPI-flash corruption here, two confirmed, it's best that you don't do it yourself.

I recommend that you upgrade your GPU first.

 

[thomasthegps]

But I hope (and suspect) that Apple will have another Firmware update with GM or final release 10.14.0 that will give boot screen, boot selector, and enable file-vault on the non-Apple yet Apple recommended metal-capable GPUs.

I can't believe they would restrict security on their latest OS using their approved hardware ??

(Although Tim Cook did just handover all of Paul Manafort's iCloud account to Mueller!) - so much for Apple security a al San Bernardino. No mainstream or it security coverage of that one !

very likely. I would expect to see boot screens in a week or so...

 

[tsialex]

very likely. I would expect to see boot screens in the a week or so...

One thing is Apple disable the EFI progress bar on the firmware flasher, another one is new UEFI boot screens/selector/FV2.

 

[Squuiid]

very likely. I would expect to see boot screens in a week or so...

I really don’t think this will happen.
The installer clearly states that a Metal capable card is required AND FileVault2 must be disabled before proceeding with the install. This will very likely not change.
The amount of work, and risk, to do this is far too great for Apple to go down this route. It won’t happen.

 

[MoerBoer]

I really don’t think this will happen.
The installer clearly states that a Metal capable card is required AND FileVault2 must be disabled before proceeding with the install. This will very likely not change.
The amount of work, and risk, to do this is far too great for Apple to go down this route. It won’t happen.

Guess that will be that then for me.

I personally think there will be a bit of backlash if this security feature ( FileVault2 ), cannot be used anymore.

Suppose we are all holding on to sliver of hope that we can still use our beloved cMP's. I for one cannot disable FileVault due to work related information on my machine.

Probably time to seriously start looking at Linux.

 

[tsialex]

Guess that will be that then for me.

I personally think there will be a bit of backlash if this security feature ( FileVault2 ), cannot be used anymore.

Suppose we are all holding on to sliver of hope that we can still use our beloved cMP's. I for one cannot disable FileVault due to work related information on my machine.

Probably time to seriously start looking at Linux.

It's easier to start searching for a PC eVGA GTX680 than migrate to Linux, no? If Apple change the Boot screens/selector/FV2 to UEFI, you could get a RX560 instead.

 

[MoerBoer]

It's easier to start searching for a PC eVGA GTX680 than migrate to Linux, no? If Apple change the Boot screens/selector/FV2 to UEFI, you could get a RX560 instead.

Yes, I won't mind buying a RX560, but obviously needs to be fully supported. My MacPro 2.1 already runs a flashed HD 5770 with Linux Mint.

Isn't the better option to get an AMD PC card to flash than a Nvidia due to Metal and all that?

 

[tsialex]

Yes, I won't mind buying a RX560, but obviously needs to be fully supported. My MacPro 2.1 already runs a flashed HD 5770 with Linux Mint.

Isn't the better option to get an AMD PC card to flash than a Nvidia due to Metal and all that?

Nvidia GTX680 is a Metal family1v4 card, fully supported on Mojave. I have a flashed HD7870 too and seems the same. I have more quirks on the HD7870.

I've searched auction sites for months trying to find a eVGA GTX 680 Mac Edition on the cheap, found one, then 2 weeks later I found another, this time eVGA Signature 4GB with backplate for ~$120, flashed in 5' using the ROM from here. It's the easier card to flash, no doubt.

 

[MoerBoer]

Nvidia GTX680 is a Metal family1v4 card, fully supported on Mojave. I have a flashed HD7870 too and seems the same. I have more quirks on the HD7870.

I've searched auction sites for months trying to find a eVGA GTX 680 Mac Edition on the cheap, found one, then 2 weeks later I found another, this time eVGA Signature 4GB with backplate for ~$120, flashed in 5' using the ROM from here. It's the easier card to flash, no doubt.

Any quirks with the GTX 680? All ports working?

 

[tsialex]

Any quirks with the GTX 680? All ports working?

Just the eventual little black rectangle on Finder file lists, you get used to it, all ports working.

All flashed cards have problems/little quirks, GTX680 seems to have just one. I have a long list of them on HD 7870.

 

[Squuiid]

Any quirks with the GTX 680? All ports working?

No quirks really, they work very well in my experience. All ports work if you get the reference eVGA cards.
Here's a pair of them for a pretty good price. These are pre-flashed.
2x EVGA Nvidia GTX680 SLI 2GB Graphics Cards with EVGA backplates Apple MAC & PC
[doublepost=1534337208][/doublepost]

Just the eventual little black rectangle on Finder file lists, you get used to it, all ports working.

Ah, odd. Have not seen that. Is that Mojave only?

 

[tsialex]

No quirks really, they work very well in my experience. All ports work if you get the reference eVGA cards.
Here's a pair of them for a pretty good price.
2x EVGA Nvidia GTX680 SLI 2GB Graphics Cards with EVGA backplates Apple MAC & PC
[doublepost=1534337208][/doublepost]
Ah, odd. Have not seen that. Is that Mojave only?

Since High Sierra betas, seems a driver problem, people reported it here on MacRumors from time to time.
[doublepost=1534337729][/doublepost]When eventually happens, it's something like this (I've made that on my rMBP, just to illustrate)

 

[chrfr]

Since High Sierra betas, seems a driver problem, people reported it here on MacRumors from time to time.
[doublepost=1534337729][/doublepost]When eventually happens, it's something like this (I've made that on my rMBP, just to illustrate)

View attachment 776073

I get those and other artifacts with my non-flashed 970. The artifacts vary with versions of the web driver so it's probably some bug in the drivers.

 

[thomasthegps]

No I’m confident that we will get bootscreens, I do not see why apple would take the time to create a new efi rom just to flash with no apple gpu when they could have easily dropped the mac pro 5.1 support for mojave.

I don’t see apple going in half way. They decided to officialy support the rx 580 and now with this new efi, I think they’re going to go all the way through. Firevault is a Mac Os feature and adding support for it only comes down to providing bootscreen support. Once you have a bootscreen they can create a bootloader that serves to decrypt the mac os partition. Just like on linux with grub.... I’m not an expert on the subject but I think that its already how fv works on other macs. When you boot your mac a first screen appears that asks for your password to decrypt the contents of your mac os partition and then another screen pops up to ask for your os passwd.

Usually Either apple fully supports stuff or they simply don’t... The argument it would be “too much effort” honeslty doesn’t make sense. They have already made the effort to release a new efi.

 

[Squuiid]

No we will get bootscreens, I do not see why apple would take the time to create a new efi rom just to flash with no apple gpu when they could have easily dropped the mac pro 5.1 support for mojave.

I don’t see apple going in half way. They decided to officialy support the rx 580 and now with this new efi, I think they’re going to go all the way through. Firevault is a Mac Os feature and adding support for it only comes down to providing bootscreen support. Usually Either apple fully supports stuff or they simply don’t... The argument it would be “too much effort” honeslty doesn’t make sense. They have already made the effort to release a new efi.

All they did was address the flash utility to allow it to flash the firmware with non-EFI cards. That indicates to me that they have no plans to add new functionality to non-EFI cards. (Other than 5GT/s which was an easy win.)
I might be wrong of course but to me it’s all pointing in one direction right now.
I do hope I’m wrong however.