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

[mike.101]

I did the sudo mount -uw /
and got this
mount_apfs: volume could not be mounted: Permission denied
mount: / failed with 66

For the next part I got

Can't open /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents/MacOS/AirPortBrcm4360: No such file or directory.

Is there something I'm missing?

Had the same issue. This worked for me.
You need to add the SMBIOS bit in the config.plist
Replace the PlatformInfo with this :
<key>PlatformInfo</key>
<dict>
<key>Automatic</key>
<false/>
<key>CustomMemory</key>
<false/>
<key>UpdateDataHub</key>
<false/>
<key>UpdateNVRAM</key>
<false/>
<key>UpdateSMBIOS</key>
<true/>
<key>UpdateSMBIOSMode</key>
<string>Create</string>
<key>Memory</key>
<dict/>
<key>Generic</key>
<dict/>
<key>DataHub</key>
<dict/>
<key>PlatformNVRAM</key>
<dict/>
<key>SMBIOS</key>
<dict>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
<key>FirmwareFeatures</key>
<data>A1QM4A==</data>
<key>FirmwareFeaturesMask</key>
<data>P/8f/w==</data>
</dict>
</dict>

 

[Alexis Noel]

Had the same issue. This worked for me.
You need to add the SMBIOS bit in the config.plist
Replace the PlatformInfo with this :
<key>PlatformInfo</key>
<dict>
<key>Automatic</key>
<false/>
<key>CustomMemory</key>
<false/>
<key>UpdateDataHub</key>
<false/>
<key>UpdateNVRAM</key>
<false/>
<key>UpdateSMBIOS</key>
<true/>
<key>UpdateSMBIOSMode</key>
<string>Create</string>
<key>Memory</key>
<dict/>
<key>Generic</key>
<dict/>
<key>DataHub</key>
<dict/>
<key>PlatformNVRAM</key>
<dict/>
<key>SMBIOS</key>
<dict>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
<key>FirmwareFeatures</key>
<data>A1QM4A==</data>
<key>FirmwareFeaturesMask</key>
<data>P/8f/w==</data>
</dict>
</dict>

Like this?

 

[octoviaa]

Thanks. sadly didn't work. wifi doesn't get enabled. I'm in Big Sur.


Another question, is Lilu and Whatevergreen not working with Big Sur? I get crash reports upon reboot.

also nightshift enable doesn't seem to work.

Did you copied the mojave.kext file into the OC kext folder (where Lilu and WEG are)?

 

[mike.101]

Like this?
View attachment 1678140

I think you have an extra </dict>. But otherwise, yes.

 

[Alexis Noel]

I think you have an extra </dict>. But otherwise, yes.

okay tried without the extra </dict> but I just ended up in an endless restart loop
went back to conic I had prior and I managed to log in to my OS but m BT crapped itself. I did another reboot any everything is working fine, still no handoff or Apple Watch unlock.

 

[Banst]

Hello there, quite new to OC so I may ask some questions that has already be answered. Please forgive me.
So I followed the wiki to install Catalina on my 5,1. Really well documented, thanks. This forum is a gold mine. It did work fine, so I've continued to update to Big Sur (thanks for the posts that did help me). I can boot and log to Big Sur and do not have spotted any major issues yet. But the graphics are a bit laggy. For example moving a window is not smooth at all. Actually if I keep moving the window quite fast, it seems to put pressure on my GPU. I can hear its fan spinning hard. I'm sorry I'm not an expert on low level Mac debug (but please guide me to proper tools or documentation if you know them).

My GPU is a Radeon RX 480 with 8 GB of VRAM. I'm ok to change it if there is better options out there, but I would also like to know the root cause of the struggle, to get better at playing with OC.

I've also followed the Enabling Hardware Acceleration part of the wiki. I've attached my final config.plist file if that's any help.

 

[Inzajeano]

Hi everyone,

I installed Big Sur on my 5.1 using OC6.3 and now I am unable to login to message. it says. 'An unknown error occurred'. Any help on fixing this will be appreciated

 

[h9826790]

Hi everyone,

I installed Big Sur on my 5.1 using OC6.3 and now I am unable to login to message. it says. 'An unknown error occurred'. Any help on fixing this will be appreciated

Tried logout and login iCloud yet?

 

[AndreeOnline]

Request: Could someone well versed in the inner workings of Open Core and the Mac add an additional section to the Wiki between 'Requirements' and 'Part 1, installation' called 'Abstract' (or similar, depending on convention).

I would like to see the "explain it to me, like I'm an 8 year old" version of how Open Core interacts with the system in the various stages (if more than one). It should be as 'human readable' as possible and assume no knowledge of the person reading understanding Firmware, Bios, UEFI, EFI... and whatnot. Of course, these terms need to be used, but always with an explanation of their role.

I'd like it to be clear what the process would be without Open Core and where Open Core makes changes and why. I would like it to be clear if there is an entry and exit point of Open Core during boot, or if Open Core files are somehow "active" once booted.

I hope someone knowledgeable understands what I'm after and finds it in their heart to add it. I think it would be valuable to a lot of users.

Thanks!

 

[Inapurna]

Hello there, quite new to OC so I may ask some questions that has already be answered. Please forgive me.
So I followed the wiki to install Catalina on my 5,1. Really well documented, thanks. This forum is a gold mine. It did work fine, so I've continued to update to Big Sur (thanks for the posts that did help me). I can boot and log to Big Sur and do not have spotted any major issues yet. But the graphics are a bit laggy. For example moving a window is not smooth at all. Actually if I keep moving the window quite fast, it seems to put pressure on my GPU. I can hear its fan spinning hard. I'm sorry I'm not an expert on low level Mac debug (but please guide me to proper tools or documentation if you know them).

My GPU is a Radeon RX 480 with 8 GB of VRAM. I'm ok to change it if there is better options out there, but I would also like to know the root cause of the struggle, to get better at playing with OC.

I've also followed the Enabling Hardware Acceleration part of the wiki. I've attached my final config.plist file if that's any help.

I have a MacPro 5,1 dual CPU with Radeon RX 580 8Gb and it 's on Big Sur with HW Acceleration. I don't need use Lilu, WhateverGreen, and graphic card PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0). I just need AppleMCEReporterDisabler.kext.

My SMBIOS is MacPro7,1 (#5,090)

My config.plist is (attach files)

 

[AndreeOnline]

I have a MacPro 5,1 dual CPU with Radeon RX 580 8Gb and it 's on Big Sur with HW Acceleration.

Have you experimented with and without Radeonboost.kext?

Or is that file not relevant anymore?

 

[Inapurna]

Have you experimented with and without Radeonboost.kext?

Or is that file not relevant anymore?

I don't have experimented with Radeonboost.kext yet, perhaps later

 

[TECK]

It should be as 'human readable' as possible and assume no knowledge of the person reading understanding Firmware, Bios, UEFI, EFI... and whatnot.

Read the Configuration.pdf of OpenCorePkg, is well explained. For any terms you don’t understand, Google it. That’s how I learned, knew nothing about OC or macOS guts before.

 

[AndreeOnline]

Read the Configuration.pdf of OpenCorePkg, is well explained.

Do you mean the manual? Yes, I have that as well.

That is not what I'm looking for. I'm looking for an intelligent description of that manual distilled down to two or three paragraphs in layman's terms.

Something akin to what some call the 30.000 ft perspective.

 

[startergo]

Do you mean the manual? Yes, I have that as well.

That is not what I'm looking for. I'm looking for an intelligent description of that manual distilled down to two or three paragraphs in layman's terms.

Something akin to what some call the 30.000 ft perspective.

What is OpenCore and who is this guide for​

OpenCore is what we refer to as a "boot loader" – it is a complex piece of software that we use to prepare our systems for macOS – specifically by injecting new data for macOS such as SMBIOS, ACPI tables and kexts. How this tool differs from others like Clover is that it has been designed with security and quality in mind, allowing us to use many security features found on real Macs, such as SIP and FileVault. A more in-depth look can be found here: Why OpenCore over Clover and others

This guide specifically focuses on two main things:

• Installing macOS on an X86-based PC
• Teaching you what makes your Hack work

Because of this, you will be expected to read, learn and even use Google. This is not a simple one-click install setup.

Please remember that OpenCore is still new and currently in beta. While quite stable, and arguably much more stable than Clover in pretty much every way, it is still being frequently updated, so chunks of configuration change quite often (i.e. new quirks replacing old ones).

 

[AndreeOnline]

Thanks @stargergo,

So we can see right there in the intro that what I'm looking for is not what the guide is for—which underlines my point.

 

[startergo]

I'm looking for an intelligent description of that manual distilled down to two or three paragraphs in layman's terms.

Because of this, you will be expected to read, learn and even use Google. This is not a simple one-click install setup. A more in-depth look can be found here: Why OpenCore over Clover and others

In short we started using OC on real Macs for few reasons:
1. Enable boot screen
2. Install Catalina and Big Sur on unsupported Mac
3. Enable native updates for Catalina and Big Sur.
4. Enable HWA including HEVC encode/decode and DRM playback for AMD GPU's in Safari.
5. Boot UEFI Windows without possibility of NVRAM corruption.

 

[TECK]

@AndreeOnline you need to put the work effort to learn. I'm sure you are great at something specific. You did not become good at it by reading a newbie manual, you spent time to learn and try things. OC is a technical product and with any technical related products, it takes time and patience to learn it. I would not expect a kitchen chef to read a file and know everything about OC. But he does have all the tools to learn about it.

 

[AndreeOnline]

You're caught in a loop there. And perhaps I am too.

At this point I think you've realised that pointing to the same information—repeatedly—isn't productive.

You might feel that everything one needs to know is either in that document, or can be found with its help. Yet, that wasn't what I was asking for. So why hammer the crooked nail.

I'm trying to improve the situation for the common good. I don't want to replace of supersede existing documentation. I feel there is a missing part at the beginning.

 

[AndreeOnline]

@AndreeOnline you need to put the work effort to learn.

That's a great tip and life lesson!

Anyway: I have the manual so that's good. If you don't see the value in what I'm proposing (even if I'm not sure I have been properly understood), no need to engage further.

 

[Banst]

I have a MacPro 5,1 dual CPU with Radeon RX 580 8Gb and it 's on Big Sur with HW Acceleration. I don't need use Lilu, WhateverGreen, and graphic card PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0). I just need AppleMCEReporterDisabler.kext.

My SMBIOS is MacPro7,1 (#5,090)

My config.plist is (attach files)

Thanks for your help. I've rolled back the Lilu and WhateverGreen and updated my config.plist to match yours. Everything still works, but as for the laggy feeling and GPU struggle when moving a window around.

 

[tsialex]

That's a great tip and life lesson!

Anyway: I have the manual so that's good. If you don't see the value in what I'm proposing (even if I'm not sure I have been properly understood), no need to engage further.

Writing comprehensive technical documentation is very time consuming/expensive, for most software engineers it's the most difficult part of any project.

A document the way you want won't appear from nothing, this will need community effort and probably funding.

 

[motochan]

Hey guys, are any of you having problems with following the Windows 10 installation guide? I used to be doing fine, but with one recent machine, I’m getting a Error 433 “A device which does not exist was specified.” when attempting to apply the dism command (index 6, Win 10 Pro or index 1, Win 10 Home doesn’t work, throws the same error). What gives?

 

[AndreeOnline]

In short we started using OC on real Macs for few reasons:
1. Enable boot screen
2. Install Catalina and Big Sur on unsupported Mac
3. Enable native updates for Catalina and Big Sur.
4. Enable HWA including HEVC encode/decode and DRM playback for AMD GPU's in Safari.
5. Boot UEFI Windows without possibility of NVRAM corruption.

This looks like a constructive effort to help. Thanks!

But I know this. Then again, some others might not know that. But I do think that there is something similar at the start of the thread as an "intro", if you will. I think this is covered. Possibly with the exception of point 5.

Writing comprehensive technical documentation is very time consuming/expensive, for most software engineers it's the most difficult part of any project.

A document the way you want won't appear from nothing, this will need community effort and probably funding.

I sense that what I was asking for still isn't really understood. I agree about the part "will not appear from nothing" and that it will "need a community effort". But these two things are equally true for what we already have in the wikis of Open Core and HWA.

In a bit more detail then. I think it would be valuable to have a short cursory description of the flow in the Mac Pro boot process:

We press power and then A happens. Unless interrupted A allows B to be read into memory and installed components to be woken up, which leads to C being read from disk...

That is, a short description of a series events and their relationship. First how a vanilla Mac boots, and then who an Open Core Macs differs. What files are read at what time, and is the OC process started and ended at boot, or is something different after the desktop shows? I'm looking for a text the size of a mid-sized post in the forum that contextualises the steps and their reasons.

In the flow chart, normal technical terms would be used but their role should be described, but there could also be a short description below for keywords like Firmware, EFI, kexts, nvram, SMC and so on.

So, not another manual "without difficult words", but rather a smallish section at the beginning for context to bring everyone to square 0, ready for square 1, regardless of previous experience or knowledge of the boot sequence.

 

[joevt]

This looks like a constructive effort to help. Thanks!

But I know this. Then again, some others might not know that. But I do think that there is something similar at the start of the thread as an "intro", if you will. I think this is covered. Possibly with the exception of point 5.

I sense that what I was asking for still isn't really understood. I agree about the part "will not appear from nothing" and that it will "need a community effort". But these two things are equally true for what we already have in the wikis of Open Core and HWA.

In a bit more detail then. I think it would be valuable to have a short cursory description of the flow in the Mac Pro boot process:

We press power and then A happens. Unless interrupted A allows B to be read into memory and installed components to be woken up, which leads to C being read from disk...

That is, a short description of a series events and their relationship. First how a vanilla Mac boots, and then who an Open Core Macs differs. What files are read at what time, and is the OC process started and ended at boot, or is something different after the desktop shows? I'm looking for a text the size of a mid-sized post in the forum that contextualises the steps and their reasons.

In the flow chart, normal technical terms would be used but their role should be described, but there could also be a short description below for keywords like Firmware, EFI, kexts, nvram, SMC and so on.

So, not another manual "without difficult words", but rather a smallish section at the beginning for context to bring everyone to square 0, ready for square 1, regardless of previous experience or knowledge of the boot sequence.

I think you are saying that, partly, you want an explanation of why the below items are a problem and how Open Core solves them. This may require going through the code of OpenCore.

In short we started using OC on real Macs for few reasons:
1. Enable boot screen
2. Install Catalina and Big Sur on unsupported Mac
3. Enable native updates for Catalina and Big Sur.
4. Enable HWA including HEVC encode/decode and DRM playback for AMD GPU's in Safari.
5. Boot UEFI Windows without possibility of NVRAM corruption.

So for each of the above, we have something like the below (I'm totally guessing - this is inadequate, incomplete, and/or wrong but you get the idea):

1: enable GOP driver, etc. gop driver is.... gop driver can be tested by ... gop driver can be extracted by ... driver vs option rom ... gop vs uga on old Macs .. gop on uga ... uga on gop ... console ... text ... etc.
2: add VMM flag, etc.
3: ^ + patches
4: device properties / kexts / whatever
5: override runtime services NVRAM variable functions (which functions? what is Windows doing? what variables are special?)

Basically, the explanation should allow someone to recreate the solution using alternative methods or to verify that the solution is in effect or to find the code that implements the solution.