MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[PeterHolbrook]

Hi all, I have updated to OC 0.6.7 using OCLP 0.0.11 into a USB Key to boot my Mac Pro 3,1 with Big Sur 11.2.2.
If I boot selecting the OpenCore EFI with the boot picker activated (opencanopy enabled), the Mac Pro hang.
If I disable the opencanopy the boot work well (text mode).

There is a fix for this issue on the boot picker?

Thanks

Your case might be entirely different from mine, but I had to update all the Open Canopy components yesterday when I updated to OpenCore 0.6.7. With the previous one I had (perfectly valid for 0.6.6), 0.6.7 would simply show a functional, yet text-only picker.

 

[eVasilis]

Rarely, my mac after a cold restart (overnight) boots straight to big sur without the boot picker (or boot screen). Bootrom is brand new, flashed a few days ago (thanks tsialex). I am on OC 0.6.7 but it did happen with 0.6.6. too.

Any ideas?

 

[startergo]

Let's see what Vitaly answers on #1543. If that is the case, I will use -1 for uniformity reasons.

Can you show a calculator conversion screenshot example?

Signed integer (32-bit) Converter

Online binary converter. Supports all types of variables, including single and double precision IEEE754 numbers

www.binaryconvert.com

Also in the default Mac programing calculator try 2's complement of 1

 

[PeterHolbrook]

Considering the content of the 0.6.7 config.plist sample, I wonder if the value of the BIOSVersion, BoardProduct, FirmwareFeatures and FirmwareFeaturesMask in SMBIOS is no longer relevant now? That would be highly surprising, at least for me, if that is so.

 

[cdf]

Considering the content of the 0.6.7 config.plist sample, I wonder if the value of the BIOSVersion, BoardProduct, FirmwareFeatures and FirmwareFeaturesMask in SMBIOS is no longer relevant now? That would be highly surprising, at least for me, if that is so.

The sample configuration will give you basic functionality on Apple hardware. In the advanced configuration, we enable hybridization by regenerating the SMBIOS with two new values: we set BoardProduct to Mac-7BA5B2D9E42DDD94 (iMac Pro), and as a precaution against iMac Pro firmware updates, we set BIOSVersion to 9999.0.0.0.0. As of 0.6.7, the rest of the SMBIOS properties are automatically taken from the original SMBIOS values.

 

[startergo]

The sample configuration will give you basic functionality on Apple hardware. In the advanced configuration, we enable hybridization by regenerating the SMBIOS with two new values: we set BoardProduct to Mac-7BA5B2D9E42DDD94 (iMac Pro), and as a precaution against iMac Pro firmware updates, we set BIOSVersion to 9999.0.0.0.0. As of 0.6.7, the rest of the SMBIOS properties are automatically taken from the original SMBIOS values.

What changed that OC no longer needs firmware features change for Big Sur updates? Or is it BS version specific requirement?

 

[cdf]

What changed that OC no longer needs firmware features change for Big Sur updates? Or is it BS version specific requirement?

It's just not practical to do all the tests to confirm this, but this is what I think has happened:

For long I had incorrectly assumed that omitting FirmwareFeatures and FirmwareFeaturesMask in SMBIOS would preserve the original values. In fact the values were being zeroed. (Note that the firmware features in the SMBIOS can be inspected with dmidecode; they are different than those found in the NVRAM.) The zeroed values led to certain Big Sur versions not installing or updating with hybridization. (This was never an issue with Catalina, which however, requires the VMM flag, at least for the Mac Pro 5,1.) Not realizing that the firmware features were actually zeroed before, I though that it was the changed bit in the now expressly set firmware features that had done the trick.

After realizing this, I commented on it here:

macOS 11 Big Sur on Unsupported Macs Thread

The reason is that both FirmwareFeatures and FirmwareFeaturesMask must be specified when changing any SMBIOS properties in manual mode (Automatic=false). As a failsafe, these properties are set to 0, and upon detecting the absence of firmware features, the installer indicates that a firmware...

forums.macrumors.com

@Bmju, who independently came to the same conclusion, ultimately brought proper OEM preservation to 0.6.7:

OC: Remove misleading (?) statement within warning about using Automatic=false · Issue #1508 · acidanthera/bugtracker

Hi - I was planning to raise this, it is somewhat related to #1506, and so I felt I should raise it sooner rather than later, as I would also like to give @cdf the chance to comment, if they would ...

github.com

Use OEM values as failsafes for Apple-specific SMBIOS properties · Issue #1506 · acidanthera/bugtracker

I've been following the recent developments regarding OEM values in automatic mode and I thought I'd raise an issue for manual mode. On Apple hardware, manual mode is useful for doing minor SMBIOS ...

github.com

 

[cdf]

Which one do we use @cdf, I need that calculator explanation. I opened #1543.

4294967295 is more explicit, but -1 is much easier. We should go with the latter.

 

[amstel78]

Sorry for asking a similar question but I've run into a problem and am a bit stumped.

I installed v067 on my MP3,1. I completely removed DosDude1's patched version of Catalina as well as cleared out any DosDude1 remnants residing in EFI volumes. I replaced Catalina with El Capitan which was the last officially supported OS for this Mac Pro.

I then proceeded to install Mojave which went fine with VMM flag turned on. Booting into Mojave was uneventful and completed the installation process. I'm typing this message in Mojave.

Only problem experienced is the lack of output audio. I do have input audio from a connected webcam. Checking system reporter, there are no hardware audio output devices loaded even though AppleHDA and AppleHDAController kexts are loaded.

I've reinstalled Mojave as well as reverted to OC v0.6.6 with no luck.

I'm assuming at this point that I need different legacy audio kexts but I'm not sure where to get them, or how to integrate them with OC once found. If someone could give me some pointers, or link me to where this might have already been discussed, I'd be most grateful.

 

[hwojtek]

I'm assuming at this point that I need different legacy audio kexts but I'm not sure where to get them, or how to integrate them with OC once found.

You need to install the "Legacy Audio Patch" from DosDude1 Patcher. ¯\_(ツ)_/¯

 

[TECK]

Also in the default Mac programing calculator try 2's complement of 1

I don't see the option to convert?

When I click 2's complement of 1, I get:

 

[TECK]

4294967295 is more explicit, but -1 is much easier. We should go with the latter.

See #90.

 

[startergo]

I don't see the option to convert?

View attachment 1738026

It is the button 2's. First type 0x1 and then press 2's button.
One of the uses of two's complement is to negate the number. So 2's complement of 1 is -1.

 

[cdf]

I don't see the option to convert?

Do you really need to convert? Simply regard 0 as 32 zeros and the largest number as 32 ones (0xFFFFFFFF). With modular arithmetic, 0-1=-1 wraps back to the largest number.

 

[TECK]

I'm assuming at this point that I need different legacy audio kexts but I'm not sure where to get them

You could purchase a proper audio USB interface and never worry about any future compatibility issues. I use Scarlett 2I2 with Yamaha speakers for audio, that interface can also be used to record studio audio into your Mac and edit it with professional software.

 

[TECK]

Do you really need to convert?

I'm trying to make it easy for the noob person and add it to the wiki, personally I do not know all these conversions and I do a quick DuckDuckGo search to find an online convertor. I wanted to see how it can be done the same thing with the calculator.

 

[amstel78]

You need to install the "Legacy Audio Patch" from DosDude1 Patcher. ¯\_(ツ)_/¯

Wouldn't that defeat the purpose of OpenCore though? Was hoping to get Mojave and/or Catalina up and running on my MP3,1 without the need for external patches.

I just deleted a DosDude1 patched version of Catalina which ran well for the most part. I can go back to it via a backup image but I'd like to see how this can be sorted via OC first.

 

[cdf]

personally I do not know all these conversions

I didn't want to come across as smart-alecky; I just figured that it would take away some of the mystery to understand what's going on with the conversion.

 

[hwojtek]

I just deleted a DosDude1 patched version of Catalina which ran well for the most part. I can go back to it via a backup image but I'd like to see how this can be sorted via OC first.

I never had audio running on my 5,1 in Mojave nor Catalina in OC, had to extract and install the patcher anyway. No idea why. It works out of the box in OC Big Sur, tho.

 

[TECK]

I didn't want to come across as smart-alecky

No worries, you don't. I simply want a proven method with a real example, so the person who never did this conversion before, will understand easy the logic behind.

 

[amstel78]

I never had audio running on my 5,1 in Mojave nor Catalina in OC, had to extract and install the patcher anyway. No idea why. It works out of the box in OC Big Sur, tho.

Interesting. My MP5,1 has audio with Mojave both natively and with OC v0.6.6. Same with Big Sur which surprisingly also just worked right out of the box. But, the system architecture between the MP3,1 and the MP5,1 are significantly different.

 

[dontpokebearz]

True. Here is the direct link to Darwindumper. Also direct link for the RadeonDump

So I downloaded Darwin Dumper, and this is what I get for Video BIOS:


ATOM BIOS Rom:
SubsystemVendorID: 0x1da2 SubsystemID: 0xe353
IOBaseAddress: 0x0000
Filename: 353Y06HU.O4V
BIOS Bootup Message:
E353 Polaris20 XTX A1 GDDR5 256Mx32 8GB
PCI ID: 1002:67df
Connector at index 0
Type [@offset 40726]: DisplayPort (10)
Encoder [@offset 40730]: INTERNAL_UNIPHY2 (0x21)
i2cid [@offset 40836]: 0x90, OSX senseid: 0x1
Connector at index 1
Type [@offset 40736]: DisplayPort (10)
Encoder [@offset 40740]: INTERNAL_UNIPHY2 (0x21)
i2cid [@offset 40863]: 0x92, OSX senseid: 0x3
Connector at index 2
Type [@offset 40746]: HDMI-A (11)
Encoder [@offset 40750]: INTERNAL_UNIPHY1 (0x20)
i2cid [@offset 40890]: 0x91, OSX senseid: 0x2
Connector at index 3
Type [@offset 40756]: HDMI-A (11)
Encoder [@offset 40760]: INTERNAL_UNIPHY1 (0x20)
i2cid [@offset 40917]: 0x93, OSX senseid: 0x4
Connector at index 4
Type [@offset 40766]: DVI-D (3)
Encoder [@offset 40770]: INTERNAL_UNIPHY (0x1e)
i2cid [@offset 40944]: 0x95, OSX senseid: 0x6



I'm assuming that 353Y06HU.O4V is not the stock BIOS?

 

[startergo]

Interesting. My MP5,1 has audio with Mojave both natively and with OC v0.6.6. Same with Big Sur which surprisingly also just worked right out of the box. But, the system architecture between the MP3,1 and the MP5,1 are significantly different.

Yes look at the dortania' OpenCore for legacy MACS. You have to add the audio device in device properties and add compatible device id.

 

[Dewdman42]

For long I had incorrectly assumed that omitting FirmwareFeatures and FirmwareFeaturesMask in SMBIOS would preserve the original values. In fact the values were being zeroed. (Note that the firmware features in the SMBIOS can be inspected with dmidecode; they are different than those found in the NVRAM.) The zeroed values led to certain Big Sur versions not installing or updating with hybridization. (This was never an issue with Catalina, which however, requires the VMM flag, at least for the Mac Pro 5,1.) Not realizing that the firmware features were actually zeroed before, I though that it was the changed bit in the now expressly set firmware features that had done the trick.

Thanks for pointing this out. (as a side-note, it would be really helpful if we saw a summary each month of what has changed, things that were removed from the previous guide, etc. or even better would be if the guides from each OC version were still available in their complete form to refer back)

I am using a script to update my config.plist, but basically stuff like this slips through the cracks. So previously, for some reason, I had a line to set FirmwareFeatures= A1QM4A== and FirmwareFeaturesMask= P/8f/w==

I can't remember if that was in your guide for 0.6.6 or if I had added it for some other reason, I presume it was in the 0.6.6 guide. But anyway, now it appears to be removed from the guide and the default config.plist has empty entries...which I assume you are saying that is what we should do now..leave them there, but blank. yes?

 

[startergo]

So I downloaded Darwin Dumper, and this is what I get for Video BIOS:


ATOM BIOS Rom:
SubsystemVendorID: 0x1da2 SubsystemID: 0xe353
IOBaseAddress: 0x0000
Filename: 353Y06HU.O4V
BIOS Bootup Message:
E353 Polaris20 XTX A1 GDDR5 256Mx32 8GB
PCI ID: 1002:67df
Connector at index 0
Type [@offset 40726]: DisplayPort (10)
Encoder [@offset 40730]: INTERNAL_UNIPHY2 (0x21)
i2cid [@offset 40836]: 0x90, OSX senseid: 0x1
Connector at index 1
Type [@offset 40736]: DisplayPort (10)
Encoder [@offset 40740]: INTERNAL_UNIPHY2 (0x21)
i2cid [@offset 40863]: 0x92, OSX senseid: 0x3
Connector at index 2
Type [@offset 40746]: HDMI-A (11)
Encoder [@offset 40750]: INTERNAL_UNIPHY1 (0x20)
i2cid [@offset 40890]: 0x91, OSX senseid: 0x2
Connector at index 3
Type [@offset 40756]: HDMI-A (11)
Encoder [@offset 40760]: INTERNAL_UNIPHY1 (0x20)
i2cid [@offset 40917]: 0x93, OSX senseid: 0x4
Connector at index 4
Type [@offset 40766]: DVI-D (3)
Encoder [@offset 40770]: INTERNAL_UNIPHY (0x1e)
i2cid [@offset 40944]: 0x95, OSX senseid: 0x6



I'm assuming that 353Y06HU.O4V is not the stock BIOS?

You will have to check at techpowerup.com with:
ATOM BIOS Rom:
SubsystemVendorID: 0x1da2 SubsystemID: 0xe353