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.
I add also that from recent BigSur releases to disable SIP without a "Custom Configuration" this value for OpenCore worked csr-active-config: fwgAAA==
I'm intrigued by your comment. Is there a way to disable SIP from the OpenCore config.plist? I've looked up "csr-active-config" in the OpenCore Reference Manual (0.6.1) and it appears its use is frowned upon as a possible value for NVRAM LegacySchema. If this is possible at all, can you give us an example of the relevant config.plist parameters that will disable SIP and the relevant parameters to undo that change on shutdown?
 
I guess you referred to a previous opencore version 0.6.0 , but seems from 0.6.1 setting SecureBootModel Disabled is required to boot BigSur on unsupported Mac, and either with Disabled you can have a snapshot booting and OTA update, while to disable snapshot booting this should work to fix "sudo mount -uw /":
https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28958380

Thank you to clarify this!Then it behaves differently on other hack, sorry for the ot (I was quite sure it was the same).
I was referring to the latest master version, updated as of today.
SecureBootModel=Disabled

Disabled.png


SecureBootModel=Default
Default.png
 
Last edited:
Someone might of already asked this, and i know its completely unrelated but where/how did you get that image for the about this mac?
Haha, I get this question every months, either in this forum, via PM, or other facebook group.

It's extracted from the Apple Technician Guide (with little bit of Photoshop skill).
 
Haha, I get this question every months, either in this forum, via PM, or other facebook group.

It's extracted from the Apple Technician Guide (with little bit of Photoshop skill).
I know the one you are talking about, im not very good at photoshop and everytime i try to edit out the gradient background it just ends up looking very messy and rough. Would you possibly mind sharing your photoshopped one?
 
I'm intrigued by your comment. Is there a way to disable SIP from the OpenCore config.plist? I've looked up "csr-active-config" in the OpenCore Reference Manual (0.6.1) and it appears its use is frowned upon as a possible value for NVRAM LegacySchema. If this is possible at all, can you give us an example of the relevant config.plist parameters that will disable SIP and the relevant parameters to undo that change on shutdown?

Using this csr-active-config dwgAAA== works to disable SIP correctly on Catalina and previous macOS, but on BigSur csrutil status with "Custom Configuration" and csrutil authenticated-root disabled.

Instead this new value fwgAAA== works to disable SIP correctly on BigSur and authenticated-root, but on Catalina and previous macOS SIP is in "Custom Configuration".

Here is the config.plist example :
Code:
    <key>NVRAM</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <dict>
                <key>UIScale</key>
                <data>AQ==</data>
                <key>DefaultBackgroundColor</key>
                <data></data>
            </dict>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <dict>
                <key>boot-args</key>
                <string>-no_compat_check</string>
                <key>csr-active-config</key>
                <data>fwgAAA==</data>
                <key>run-efi-updater</key>
                <string>No</string>
            </dict>
        </dict>
        <key>Delete</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <array>
                <string>UIScale</string>
                <string>DefaultBackgroundColor</string>
            </array>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <array>
                <string>boot-args</string>
                <string>csr-active-config</string>
                <string>run-efi-updater</string>
            </array>
        </dict>
 
Thanks for the reply. I got OpenCore installed. Finally got the boot selector to show up. So now I am trying to install Windows 10. I followed the steps and tried 3 different USB drives, but none of them show up in the boot selector.
I used Mac to format the USB into the exFat MBR, copied the windows iso with rsync to the USB. Updated the config and copied over the exFatDxeLegacy.efi to the drivers folder and added the line to the drivers array in config. Not sure what I am doing wrong.
Edit: I figured it out, there is a mistake for following the copy command too closely.
Everything works, do install Windows USB, via Bootcamp
 

Attachments

  • Bildschirmfoto 2020-10-02 um 23.52.58.png
    Bildschirmfoto 2020-10-02 um 23.52.58.png
    384.8 KB · Views: 191
Using this csr-active-config dwgAAA== works to disable SIP correctly on Catalina and previous macOS, but on BigSur csrutil status with "Custom Configuration" and csrutil authenticated-root disabled.

Instead this new value fwgAAA== works to disable SIP correctly on BigSur and authenticated-root, but on Catalina and previous macOS SIP is in "Custom Configuration".

Here is the config.plist example :
Code:
    <key>NVRAM</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <dict>
                <key>UIScale</key>
                <data>AQ==</data>
                <key>DefaultBackgroundColor</key>
                <data></data>
            </dict>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <dict>
                <key>boot-args</key>
                <string>-no_compat_check</string>
                <key>csr-active-config</key>
                <data>fwgAAA==</data>
                <key>run-efi-updater</key>
                <string>No</string>
            </dict>
        </dict>
        <key>Delete</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <array>
                <string>UIScale</string>
                <string>DefaultBackgroundColor</string>
            </array>
            <key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
            <array>
                <string>boot-args</string>
                <string>csr-active-config</string>
                <string>run-efi-updater</string>
            </array>
        </dict>

Regarding the csr-active-config, how do you convert the values fwgAAA== to the hex-string? I want to disable kext-signing in Mojave, so I found that the value of csr-active-config should be 01000000. But how do you convert the value 0100000 to something dat is the same data-format as the example here?
 
Regarding the csr-active-config, how do you convert the values fwgAAA== to the hex-string? I want to disable kext-signing in Mojave, so I found that the value of csr-active-config should be 01000000. But how do you convert the value 0100000 to something dat is the same data-format as the example here?


if you use Xcode plist editor you could type directly the hex value.
 
  • Like
Reactions: rippiedoos
Regarding the csr-active-config, how do you convert the values fwgAAA== to the hex-string? I want to disable kext-signing in Mojave, so I found that the value of csr-active-config should be 01000000. But how do you convert the value 0100000 to something dat is the same data-format as the example here?
I've been here alone and I'm going to show you how to turn off SIP Recovery mode.
EFFB62F1-6B9C-4C7C-82D6-44161F22A948.png
 
  • Love
Reactions: 205Maxi
Thanks for the website and conversion. Didn't realize it was HEX so I first tried converting it as a string. Now it works, thanks! kext-signing is now disabled!

Only problem now is that the SmallTree-driver still isn't loading, so my Intel X520-SR1 (converted to SmallTree-device) isn't working anymore. Any hints on how to debug this? This stopped working after configuring OpenCore. Also my EFI-version of Windows 10 won't even boot anymore with the card in my MacPro 4,1/5,1. If I take it out, it magically boots up again.
 
I installed Big Sur Beta 9 last night on my MacPro4,1(5,1) running OpenCore 0.6.1 with RX580.

Odd thing is that HEVC hardware acceleration is now listed as unavailable by VideoProc. Only H264 is listed as available.

To troubleshoot, I booted into macOS Catalina with the same exact hardware and OpenCore configuration, and Video Proc reported that both HEVC and H264 hardware acceleration are available.

Does anyone know how to resolve this and get HEVC hardware acceleration back? I have not encountered this issue in the prior Big Sur betas, so I assume Apple did something to Beta 9.
I have some family issues and stopped all Big Sur testing.

However, please check the GPU's ident in IOReg. You may need to manually patch PXS1 to GFX0 in order to make HEVC HWAccel work again in Big Sur.

 
  • Like
Reactions: octoviaa
Thanks for the website and conversion. Didn't realize it was HEX so I first tried converting it as a string. Now it works, thanks! kext-signing is now disabled!

Only problem now is that the SmallTree-driver still isn't loading, so my Intel X520-SR1 (converted to SmallTree-device) isn't working anymore. Any hints on how to debug this? This stopped working after configuring OpenCore. Also my EFI-version of Windows 10 won't even boot anymore with the card in my MacPro 4,1/5,1. If I take it out, it magically boots up again.

If you are using BigSur copy your third party kext to this path: /Library/Extensions/

then open a BigSur terminal and type:
Code:
sudo -s
chown -R 0:0 /Library/Extensions/
chmod -R 755 /Library/Extensions/
kmutil install --update-all
kcditto

you should get an output where kmutil is done mainly the Auxiliary Extensions, then reboot and once on desktop if still your driver don't worked try from terminal this: kextutil /Library/Extensions/YourDriverName.kext

if still don't worked you might consider to disable SIP and authenticated-root too .
 
Are you using BigSur ? If so copy your third party kext to this path: /Library/Extensions/

then open a BigSur terminal and type:
Code:
sudo -s
chown -R 0:0 /Library/Extensions/
chmod -R 755  /Library/Extensions/
kmutil install --update-all
kcditto

you should get an output where kmutil is done mainly the Auxiliary Extensions, then reboot and once on desktop if still your driver don't worked try from terminal this: kextutil /Library/Extensions/YourDriverName.kext

No, I'm still on Mojave. Any change on command's there?
 
No, I'm still on Mojave. Any change on command's there?

For Mojave this should work, copy your third party kext here /Library/Extensions/ :
Code:
sudo mount -uw /
sudo -s
chown -R 0:0 /Library/Extensions/
chmod -R 755 /Library/Extensions/
kextcache -i /

if after reboot don't worked, you might consider to copy it here /System/Library/Extensions/
 
For Mojave this should work, copy your third party kext here /Library/Extensions/ :
Code:
sudo mount -uw /
sudo -s
chown -R 0:0 /Library/Extensions/
chmod -R 755 /Library/Extensions/
kextcache -i /

if after reboot don't worked, you might consider to copy it here /System/Library/Extensions/
Yes, thanks!

The installer put the kext into /System/library/Extensions so I moved it to /Library/Extensions, ran kextcache and did a manual load of the driver, SmallTreeIntel8259x.kext. Now it's loaded and I can assign an address again and it is listed in the Ethernet Cards overview again. Thanks!

The only thing that is left, is why my Windows 10 install won't boot with the card installed anymore. Do I have to update my firmware of the card first, or enable the card firmware again? My Windows 10 was converted to UEFI, maybe the card needs newer EFI-firmware or something?
 
I have some family issues and stopped all Big Sur testing.

However, please check the GPU's ident in IOReg. You may need to manually patch PXS1 to GFX0 in order to make HEVC HWAccel work again in Big Sur.

Hi, thank your for the suggestion.

However, using HackingTool, it seems that the RX 580 is already identified as GFX0 in Big Sur Beta 9. See attached screenshot. Regardless, I tried your suggestion and inserted the patch segment you suggested into my config.plist's ACPI section and rebooted under OpenCore.0.6.1. I then did a check for HEVC under VideoProc, and it is still showing up as Not Available.

Anyone has any idea how to get HEVC hardware acceleration back in Big Sur Beta 9? I am using RX 580 in Slot 1 on a MacPro 4,1/5,1. This problem did not show up until Beta 9.
 

Attachments

  • Screen Shot 2020-10-02 at 3.56.05 PM.png
    Screen Shot 2020-10-02 at 3.56.05 PM.png
    670.9 KB · Views: 156
Big Sur Beta 9 killed HEVC encoding on AMD GPUs. Might be just a bug... or they are enforcing T2 for encoding now. Decoding HEVC still works fine.
I do not think this is just a bug, I could be wrong but more inclined towards " they are enforcing T2 for encoding " I also read somewhere that now to watch Netflix 4K you have to have a T2 ... Isn't it related?

I hope I am all wrong...
 
Netflix playback is decoding and as I said, this still works. We will see if it's a bug or not. Apple killed HEVC encoding on AMD GPUs in the past by mistake. This even happened in a final release (I think it was back in Mojave). Wouldn't surprise me if they just introduced that bug once again.
 
  • Haha
Reactions: 205Maxi
Netflix playback is decoding and as I said, this still works. We will see if it's a bug or not. Apple killed HEVC encoding on AMD GPUs in the past by mistake. This even happened in a final release (I think it was back in Mojave). Wouldn't surprise me if they just introduced that bug once again.
Finger crossed, why would they do such mistake?? Oh just to scare us maybe ahahaha ...

Well hope you are right... Otherwise we will love with the red dot...
 
Why do they make so many other mistakes? Apple's software development is pure mess. They can't surprise me anymore. :rolleyes:
Oh bet it is, thanks for answering though, I have 2 questions for you, is it possible to PM you? Thank you.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.