Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Yeah, I don't know why I can't expand that column. It's already the max width I can set.
Anyway, my Radeon VII also named as PXS1
I know but it's common practice in the Hackintosh world and often necessary. It won't do any harm.
So, the code should be ?
Code:
<dict>
<key>Comment</key>
<string>PXS1 to GFX0</string>
<key>Count</key>
<integer>0</integer>
<key>Enabled</key>
<true/>
<key>Find</key>
<data>UFhTMQ==</data>
<key>Limit</key>
<integer>0</integer>
<key>Mask</key>
<data></data>
<key>OemTableId</key>
<data></data>
<key>Replace</key>
<data>R0ZYMA==</data>
<key>ReplaceMask</key>
<data></data>
<key>Skip</key>
<integer>0</integer>
<key>TableLength</key>
<integer>0</integer>
<key>TableSignature</key>
<data></data>
</dict>
Last edited:
I believe that's a soft boot argument injection, not really hard writing anything to the NVRAM. Because OpenCore is designed for non Mac computer as well, NVRAM not necessary exist for it to write anything. If the boot argument need to be wrote into the BootROM in order to work, that will be meaningless as a Hackintosh boot loader.
Also, we can do a test
1) Boot to desktop by using OpenCore, dump the BootROM
2) We change the config plist boot argument, e.g. add "mbasd=1" into the boot argument (this is a very safe boot argument for cMP. The function is to allow cMP able to use the external USB super drive)
3) Reboot, and dump the BootROM again
4) Compare the bootROM image
If OpenCore write the boot argument into the NVRAM, we should able to see that "mbasd=1" in the result.
First test is done, I am able to rename PXS1 to GFX0. So, the code in post #31 is correct.
![Screenshot 2019-10-30 at 3.36.11 AM.png]( "Screenshot 2019-10-30 at 3.36.11 AM.png")
This test use the cdf default config + GFX0 patch, so, still ident as 5,1. With the hex edited AppleGVA framework, HEVC encoding still not available yet.
![Screenshot 2019-10-30 at 3.36.33 AM.png]( "Screenshot 2019-10-30 at 3.36.33 AM.png")
This test use the cdf default config + GFX0 patch, so, still ident as 5,1. With the hex edited AppleGVA framework, HEVC encoding still not available yet.
Last edited:
2nd test, OpenCore with iMac Pro SMBIOS injection + GFX0 patch, PRIMARY GOAL ACHIEVED!!! Full HWAccel with HEVC encoding!!!!
![Screenshot 2019-10-30 at 3.45.07 AM.png]( "Screenshot 2019-10-30 at 3.45.07 AM.png")
Million thanks to CMMChris!
Million thanks to CMMChris!
And now, it's time to fix the SMC issue (if ident as iMac Pro)
![Screenshot 2019-10-30 at 3.56.22 AM.png]( "Screenshot 2019-10-30 at 3.56.22 AM.png")
(Update 1: the two fans are the PSU fan, and PCIe fan. Max RPM shows up correctly in iStat menu. And will spin up accordingly when I stress the GPU.
All the missing fans are for CPU. Intake, Exhaust, Booster)
(Update 1: the two fans are the PSU fan, and PCIe fan. Max RPM shows up correctly in iStat menu. And will spin up accordingly when I stress the GPU.
All the missing fans are for CPU. Intake, Exhaust, Booster)
Last edited:
I will, but may be later. Since all temperature sensors' info are missing at this moment. I am not sure how safe to use this config at this moment. And I want to include the SMC fix in my tutorial if possible.
Anyway, everything I did is actually covered in this thread. The required code I shared in post #7 and post #31.
However, that base on my situation only.
e.g.
1) I only use one monitor. Only the 1st DP port is working at this moment after the iMac Pro patch. CMMChris already told me the fix, but I haven't have time to try that yet.
2) My graphic card is installed in slot 1, and the original ACPI name is PXS1
3) Lilu and WhateverGreen is installed
4) Only tested in Mojave (18G1012)
Last edited:
It was intentional, they don't want you to have it.
More issue found when ident as iMac Pro. The CPU only work at ~50% speed.
![iMad Pro.png]( "iMad Pro.png")
Not sure if it's SMC related. Or due to the computer now can't ident the CPU correctly (the CPU name came from my info edition, not from the system natively), and the Base Frequency is wrong obviously.
Not sure if it's SMC related. Or due to the computer now can't ident the CPU correctly (the CPU name came from my info edition, not from the system natively), and the Base Frequency is wrong obviously.
Nice problem there, hope you figure it out as it makes a 3,1 faster than your 5,1 according to a benchmark. Mine was 467/2820
Mac Pro (Early 2008) - Geekbench
Benchmark results for a Mac Pro (Early 2008) with an Intel Xeon X5482 processor.
browser.geekbench.com
I've observed the same thing about the frequency when OpenCore sets the platform information.
@h9826790 Try using original SMBIOS and set those boot args for whatevergreen:
shikigva=32 and shiki-id=Mac-7BA5B2D9E42DDD94
This spoofs iMacPro1,1 SMBIOS only for the AppleGVA framework to enable HEVC while the remaining components operate in your Mac Pro SMBIOS as intended.
shikigva=32 and shiki-id=Mac-7BA5B2D9E42DDD94
This spoofs iMacPro1,1 SMBIOS only for the AppleGVA framework to enable HEVC while the remaining components operate in your Mac Pro SMBIOS as intended.
Good idea. Tested with shikigva=96 and shiki-id=Mac-7BA5B2D9E42DDD94, doesn't work, but I forget to test 32 or 1......
The setup described in post #1 does not touch platform information at all. Most would be hard pressed to find differences between such a setup and a natively booted one.
Modifying the SMBIOS in automatic mode is what seems to lead to the wrong frequency. Perhaps manual mode gives more control. This remains to be tested.