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.
Thanks for the feedback! To be more clear, I never installed innie separately - I’m just receiving the benefit of NVME drives showing as internal that comes from your oc package.

Unfortunately, there’s no lilu in library/extensions (or, so far as I can tell, anywhere else except the EFI partition on the OS boot disk per your package).
Any other suggestions would be gratefully receivedo- could it possibly be an incompatibility with Softraid?
Possible RAID related. I never test my package with softraid.
 
Last edited:
could it possibly be an incompatibility with Softraid?
Sorry for quoting myself, but the answer is, “Yes it could”.
in fact, “yes it was”. I uninstalled Softraid and reformatted the disks in raid 0 using the Macos built in Disk Utility. Boots perfectly every time now.
[automerge]1587304610[/automerge]
Possible RAID related. I never test my package with software RAID.
Heh, you ninja’d me!
 
  • Like
Reactions: JedNZ and h9826790
Thanks @h9826790 you're amazing, and amazingly fast! The version in post #1314 is your latest development?
It's the latest release from me. May be another update later, but that should be for HS compatibility issues. Nothing for Mojave / Catalina.

In fact, that's for stopping HEVC HWAccel in HS to avoid system crash (if we eventually figure out what exactly need to be disable, and how to work around it).
 
  • Like
Reactions: pierrox
Firstly, thank you to h9826790 for all of your hard work on this thread. I've semi-successfully installed your latest oc package in my 5,1 cmp. Boot screen, bootpicker, innie and hardware h265 acceleration and Radeonboost are all present and working.

However, when I boot the machine things often go a bit wrong. I choose the OS drive in the boot picker (or allow it to be chosen by default) and the progress bar moves about 10% of the way but then the screen turns black for about 30 seconds, the startup chime starts and the boot picker reappears. (i.e., presumably the machine reboots).

When the default OS is chosen a second time, the machine will display the multi-language, "Your computer restarted because of a problem..." screen and then usually (but not always) boot properly. After logging in to the MacOS desktop, the error dialogue "You shut down your computer because of a problem - click open to reopen apps" appears.

So it seems that the machine fails to boot properly the first time, but then is able to boot the second time. Once booted, the machine is rock solid for days under load.

The problem seems to happen 100% of the time after a cold boot and about 60% of the time after a warm restart. It's driving me crazy because everything else is working so well! Any ideas what might be causing this?

Specs are:
Mac Pro 5,1 (2010)
MacOS Mojave 10.14.6
Dual 3.46 X5690 cpus
96Gb 1333Ghz DDR3
Radeon VII (powered via Pixlas mod) in slot 1
OWC Accelsior 4M2 NVME PCIE card in slot 2 via a PCIE extension cable and populated with:
2Tb Samsung 970 EVO plus boot drive (AFP)
2Tb Samsung 970 EVO plus time machine drive (AFP)
2x 1Tb OWC Aura P12 in RAID 0 (HFS+)
Together with 4x Samsung 860 EVO 4Tb SATA disks in RAID 4
[RAID handled by Softraid 5.8.3]
2x USB 3.2 gen 2 cards in slots 3 and 4
You can unable verbose boot and debug logging with a debug opencore.
 
We actually have the code ready, but still need more tests to work out if we really need this code to disable HEVC hardware decode.
Code:
<key>Patch</key>       
<array>
    <dict>
        <key>Base</key>
        <string></string>
        <key>Comment</key>
        <string>Patch IOGVAHEVCDecode to NOGVAHEVCDecode</string>
        <key>Count</key>
        <integer>0</integer>
        <key>Enabled</key>
        <true/>
        <key>Find</key>
        <data>SU9HVkFIRVZDRGVjb2Rl</data>
        <key>Identifier</key>
        <string>com.apple.kext.AMDRadeonX4000</string>
        <key>Limit</key>
        <integer>0</integer>
        <key>Mask</key>
        <data></data>
        <key>MaxKernel</key>
        <string>18.0.0</string>
        <key>MinKernel</key>
        <string></string>
        <key>Replace</key>
        <data>Tk9HVkFIRVZDRGVjb2Rl</data>
        <key>ReplaceMask</key>
        <data></data>
        <key>Skip</key>
        <integer>0</integer>
    </dict>
</array>
 
  • Like
Reactions: pierrox and Dayo
Later you can replace bootX64.efi file in the Windows EFI folder with the OC bootX64.efi and point to bootmgfw.efi (you need to find the location of this file in the Windows EFI folder either in the debug log or with devtree > devtree.txt, map -r > map.txt from UEFI shell)

How important is this step? I've got windows up and running now, and always get the boot picker when I restart. I can happily switch between my OSes, but don't want to inadvertently mess up by not having done this last step...

Also, now that I'm done with tinkering and happy with my setup, what state should my VMM Flag and SMBIOS spoofing be in?

This guide is absolutely incredible. Thank you to all contributors. I am now running a rig with a Radeon vii, dual boot Windows 10 and Mac OS Catalina, and functioning HW Accel and Thunderbolt 3 - all things I've been dreaming about for years! 🤤
 
Should MaxKernel be 17.0.0 to limit to HiSierra and below?
Max 17.0.0 means 17.2.0 (High Sierra 10.13.1) etc won't applicable.

TBH, I don't expect anyone will still run 10.14.0 (Kernel 18.0.0) nowadays. So, if they run 10.14.6, that's kernel 18.7.0. If they run 10.13.6, kernel version is 17.7.0.

What I want to block is "Mojave and above", but not "High Sierra and above".
 
  • Like
Reactions: pierrox
Hi guys, you’re doing an amazing job here.
@h9826790, @cdf and many others, thanks for everything.

I will tell my situation from the beginning, in the hope that there will be a solution.

My cMP has a very common configuration:

5.1 (updated from 4.1),
BootRom: 144.0.0.0.0,
CPU: 2x X5690,
Ram 40 GB 1333Mhz
GPU: Sapphire Radeon RX 580 8GB Pulse (Dual)

I followed cdf's OpenCore on the Mac Pro post, and get:
1 - Mojave (clean install) on a Sata hard drive in tray 1
2 - Catalina with opencore, on an NVME in the PCi 4 slot

So far so good, but neither hwaccel nor DRM (Apple TV +) has worked, as expected.

So I replaced the EFI folder with the one in the @h9826790 package, post #1314.
Then I set the SMBios Update parameter to "true" and disabled VMM, and DRM (Apple TV +) and H264 and HVEC HWAccel worked.

However, in Catalina, Geekbench 5 GPU performance drops by half, for both Open CL and Metal, compared with Mojave, in which everything works perfectly.

If I set SMBios Update to "false", Geekbench performance backs to normal, but I get no hwaccel nor DRM (Apple TV +).

I'm thinking about forgetting Catalina and installing Mojave on the NVME disk, but I feel that I'm probably missing something.

How can I fix it? Thanks.
 
Last edited:
I just tested this. I'm seeing the same compute score (>46K for Metal) with UpdateSMBIOS true or false.

Using Mojave I see the same score too.
The problem occurs in Catalina, in my case.

Should I change any other config.list parameter?
 
Hi guys, you’re doing an amazing job here.
@h9826790, @cdf and many others, thanks for everything.

I will tell my situation from the beginning, in the hope that there will be a solution.

My cMP has a very common configuration:

5.1 (updated from 4.1),
BootRom: 144.0.0.0.0,
CPU: 2x X5690,
Ram 40 GB 1333Mhz
GPU: Sapphire Radeon RX 580 8GB double pulse.

I followed cdf's OpenCore on the Mac Pro post, and get:
1 - Mojave (clean install) on a Sata hard drive in tray 1
2 - Catalina with opencore, on an NVME in the PCi 4 slot

So far so good, but neither hwaccel nor DRM (Apple TV +) has worked, as expected.

So I replaced the EFI folder with the one in the @h9826790 package, post #1314.
Then I set the SMBios Update parameter to "true" and disabled VMM, and DRM (Apple TV +) and H264 and HVEC HWAccel worked.

However, in Catalina, Geekbench 5 GPU performance drops by half, for both Open CL and Metal, compared with Mojave, in which everything works perfectly.

If I set SMBios Update to "false", Geekbench performance backs to normal, but I get no hwaccel nor DRM (Apple TV +).

I'm thinking about forgetting Catalina and installing Mojave on the NVME disk, but I feel that I'm probably missing something.

How can I fix it? Thanks.
Try Radeon Boost yet?
 
  • Like
Reactions: leoaf79
Try Radeon Boost yet?

Yep:

RadeonBoost 1.3 @ 5.1cMP - RX580 8GB (OpenCore):
  • Mojave - everything worked well, but without performance improvement (Geekbench 5).
  • Catalina - Geekbench 5 results drops to the half. If I deactivate SMBios spoofing, it backs to normal but Hwaccel doesn't work.


When SMBios update flag is true, shouldn't the model change to iMac? Mine always shows MacPro5,1.
 
When SMBios update flag is true, shouldn't the model change to iMac? Mine always shows MacPro5,1.
The idea here is to only change the board ID, but not the Mac's ident.

I prefer to keep the original ident / config as much as possible. e.g. original ident, therefore, the original serial number is valid.

Even though we can make the cMP ident as iMac Pro, but still use the original serial number, but clearly the serial number isn't for that machine. We don't know if that may cause any issue.

Therefore, we only inject the board ID, which just good enough to make HEVC hardware encoding works.
 
  • Like
Reactions: zoltm and leoaf79
I know everyone’s on open core now, but my 3,1 is pretty much where I want it and I don’t want to start messing around with it now.

Is there anything I’m missing, I’ve done the hex edit and the lilu.kext (seperate of course) but don’t seem to get hardware accell through any of the methods?

I’m on Mac Pro 3,1 and RX 580
 
Additional option 1: If you have 4K screen, and you want to scale up the boot picker or that Apple logo. You may download this package -> unzip it -> mount the EFI partition -> REPLACE the whole EFI folder by this one. (Please do all 4 steps above BEFORE you apply this option)

I managed to get scaled up Apple logo on my 4k display adding this under "Nvram" "Add" key:

Code:
    <key>NVRAM</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <dict>
                <key>UIScale</key>
                <data>Ag==</data>
                <key>DefaultBackgroundColor</key>
                <data>v7+/AA==</data>
            </dict>

I took this from this post:
 
  • Like
Reactions: h9826790
@h9826790

you guys are doing great work keeping the 'original' grater alive!

I have been running a intel DX58so W3680 hex hack since snow leopard and was running very stably on el cap with a 660 but that graphics card is not compatible in mojave so upgraded to a MSI Vega 56 airboost.. and the issues began

I was running a straight MacPro5,1 smbios with a modified DSDT and stability was lacking, I can only boot with my 4k TV attached to DP1 with a HDMI dongle, if I had second monitor ON at the HDMI port it would black screen at the login screen. If I booted with 1 monitor, got to desktop, then turn on the second, black screen. If i boot, sleep, wake, then turn on the second monitor it would work (provided the video card init'd and woke 50/50)

Reading this thread gave me some ideas...

I tried using a full iMac Pro smbios and it was a disaster, no power management, CPU didn't throttle etc

but seeing that you are using open core to spoof just the iMac pro board ID, keeping the rest of the smbios reporting 5,1 intrigued me..

I was already using WEG and SHIKIGVA board-id for iMac pro ... and up to 10.14.6 before the security updates, got me hardware enc/dec 264 and HEVC.. but things went south after 2020-002 and the latest WEG as the started messing with SHIKIGVA and depreciated 96

@vit9696

can you weigh it here on why setting board-id in smbios vs using a boot-arg shikiboardid for the iMac pro produced 2 different behaviors... IIR you are a dev on clover/opencore and acathandara right?>


SO TLDR ... I decided to change my smbios in clover to MP5,1 ident and iMac pro1,1 board id
messing with various SHIKI boot args.. I am now using shikigva=80, agdpmod=pikera, dropping he board ID i believe

I now have BOTH 264/hevc hardware enc AND dec and at least DRM working on Amazon, I don't have netflix

I tried SHIKIGVA=128 which is in the table on the WEG GitHub dev wiki for iMac/macpro that should have given me all DRM but resulted in Red screen and some other issues... also in the table was 64, same thing.. but saw some using 80 and gave it a try even though its not in the Documentation tables over at WEG

I burned through at least 30 minutes of handbrake video toolbox 265 encode without crash so far

one weirdness is that I upgraded to GeekBench 5.1.1 and it crashes running compute tests.. goes black screen.. locks the system, fans spin wildly and seem the video card gets REAL hot. have to hold down power..


SO using this split nvram personality seems like the way forward.. so I need to do anything else modding frameworks to keep the system from making any iMac Pro specific calls? I don't have to worry about intel graphics since that system didn't have it, but it does have a T2 right? and apple uses the T2 in ALOT of tasks on the iMac pro for video and hashing, and encryption etc...

I tried opencore last year, but it was not working well, really seem meant for sandy bridge and newer, and unlike you guys running real mac hardware, I would have to figure out how to fix everything that my custom DSDT and clover fix now.. and virtualsmc that replaces fakesmc didn't seem too compatible either with westmere

any thoughts on how to get this rig more stable? or some options I haven't tried?

reading through 65 pages has make my brain mush

also , now that I think this is the best config.. should I rebuild cache prebinds, xpc and dyld for example? what else should I flush?

thanks guys...
 
Last edited:
  • Like
Reactions: zoltm
Even though we can make the cMP ident as iMac Pro, but still use the original serial number, but clearly the serial number isn't for that machine. We don't know if that may cause any issue.

The first issues encountered when using false SMBIOS with valid serial number : iMessage will blocked eventually.

This was intended testing when I running hackintosh, tested on El Capitan back then. I only get so far because I am afraid my Apple account/ valid Mac Pro serial being flagged or blocked (I am emulated 6,1 with 5,1 serial). It might run just OK when Apple ID not signed, but not sure for long run.

off topics : I am curious and planning another test using valid serials from EOL/obsolete Macs. Having some of G5 and G4 case conversion, they still retain genuine serials on their enclosure and how happened if I marred them using today’s supported Mac SMBIOS. Might use dummy Apple account this time.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.