Please read post #1 FAQ #28A first trial processing in VideoProc from H264 to HEVC of my 4K holidays movierun at 32 fps (3fps disabling HW accel in VideoProc options) but only the green light on INTEL (CPU, GPU and AMD still grey, i hope is only a cosmetic issue).
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 Activate AMD hardware acceleration
- Thread starter h9826790
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
update the current state:
Drive:
1. SATA SSD Bay1 (Catalina OS installed and success boot from boot menu)
2. Intel NvME SSD (Catalina installed from 1 OS use upgrade from Mojave) (Open core EFI contained)
3. Kingston SATA PCIE SSD (contain Data and Catalina installation program)
4. USB drive with Mojave installation program
Situation:
1. Open Core boot menu exist, can see the boot option
Boot Menu
-1. SATA SSD Bay1 (Catalina OS installed and success boot from boot menu)
-2. Recovery of 1
-3. Intel NvME SSD (Catalina installed from 1 OS use upgrade from Mojave) (Open core EFI contained)
-4. Recovery of 3
-5. Reset NvRAM
2. The EFI folder in drive 2, edited Config to allow installation of Catalina
3. Boot from SATA SSD of Catalina is success
4. Boot from Drive 2 Intel SSD fault to boot and freeze in apple logo like above image
Installation process:
1. Open core installed in drive 2 as it is original Mojave boot disk.
2. fault boot from drive 2, remove all drive rest NvRAM and boot from Mojave USB
3. install Mojave in Drive 1 (SATA SSD Bay1)
4. Edit config file Upgrade Drive 1 to Catalina (SATA SSD upgraded to Catalina)
5. keep config setting, upgrade Drive 2
6. Drive 2 still boot fault, freeze after boot menu
Now I can use open core to boot to SATA Bay, what should I do if I can boot from NvME SSD?
MACPRO FIRMWARE is 144.0.0.0.0
I have seem the Preboot of Drive 2 in CoverConfig
Please advice if I have done anything wrong
Thanks! h9826790
Drive:
1. SATA SSD Bay1 (Catalina OS installed and success boot from boot menu)
2. Intel NvME SSD (Catalina installed from 1 OS use upgrade from Mojave) (Open core EFI contained)
3. Kingston SATA PCIE SSD (contain Data and Catalina installation program)
4. USB drive with Mojave installation program
Situation:
1. Open Core boot menu exist, can see the boot option
Boot Menu
-1. SATA SSD Bay1 (Catalina OS installed and success boot from boot menu)
-2. Recovery of 1
-3. Intel NvME SSD (Catalina installed from 1 OS use upgrade from Mojave) (Open core EFI contained)
-4. Recovery of 3
-5. Reset NvRAM
2. The EFI folder in drive 2, edited Config to allow installation of Catalina
3. Boot from SATA SSD of Catalina is success
4. Boot from Drive 2 Intel SSD fault to boot and freeze in apple logo like above image
Installation process:
1. Open core installed in drive 2 as it is original Mojave boot disk.
2. fault boot from drive 2, remove all drive rest NvRAM and boot from Mojave USB
3. install Mojave in Drive 1 (SATA SSD Bay1)
4. Edit config file Upgrade Drive 1 to Catalina (SATA SSD upgraded to Catalina)
5. keep config setting, upgrade Drive 2
6. Drive 2 still boot fault, freeze after boot menu
Now I can use open core to boot to SATA Bay, what should I do if I can boot from NvME SSD?
MACPRO FIRMWARE is 144.0.0.0.0
I have seem the Preboot of Drive 2 in CoverConfig
Please advice if I have done anything wrong
Thanks! h9826790
Please try the config from cdf and see if that make any difference.
OpenCore on the Mac Pro
This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.
forums.macrumors.com
Work!! Thanks~ but when I connect two monitors, there is no boot screen.Please try the config from cdf and see if that make any difference.
OpenCore on the Mac Pro
This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.
I need to use the asus one to boot first and power on the LG when I boot to os
To activate HWAccel, You need to have Lilu and WhateverGreen installed. That should be in my package already. Please double check it (of course, you need to mount the EFI partition). If not there, you can follow the instruction in this post to download and install them.
Activate AMD hardware acceleration
This is the one stop shop HWAccel guide. The 1st half was invented by cdf, credit to him. I just put everything into a single post. So that no need to visit the OpenCore thread for those only interested in HWAccel. I won't explain anything in this post. The steps here just for "how to make it...
forums.macrumors.com
Once you confirmed Lilu + WEG is installed, go to the OC folder in EFI partition, and open config.plist with a text editor. There are 3 parts need to be modified.
1) Search
PlatformInfo, replace this part
Code:
<key>PlatformInfo</key>
<dict>
<key>Automatic</key>
<false/>
<key>DataHub</key>
<dict/>
<key>Generic</key>
<dict/>
<key>PlatformNVRAM</key>
<dict/>
<key>SMBIOS</key>
<dict/>
<key>UpdateDataHub</key>
<false/>
<key>UpdateNVRAM</key>
<false/>
<key>UpdateSMBIOS</key>
<false/>
<key>UpdateSMBIOSMode</key>
<string>Create</string>
</dict>by this
Code:
<key>PlatformInfo</key>
<dict>
<key>Automatic</key>
<false/>
<key>SMBIOS</key>
<dict>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
</dict>
<key>UpdateDataHub</key>
<false/>
<key>UpdateNVRAM</key>
<false/>
<key>UpdateSMBIOS</key>
<true/>
<key>UpdateSMBIOSMode</key>
<string>Create</string>
</dict>2) Search
Kernel, and replace this part
Code:
<key>Kernel</key>
<dict>
<key>Add</key>
<array/>
<key>Block</key>
<array/>by this
Code:
<key>Kernel</key>
<dict>
<key>Add</key>
<array>
<dict>
<key>BundlePath</key>
<string>Lilu.kext</string>
<key>Comment</key>
<string></string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/Lilu</string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string>18.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>
<dict>
<key>BundlePath</key>
<string>WhateverGreen.kext</string>
<key>Comment</key>
<string>Video card</string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/WhateverGreen</string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string>18.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>
</array>
<key>Block</key>
<array/>3) Search
boot-args, replace this part
Code:
<key>boot-args</key>
<string>-no_compat_check</string>by this
Code:
<key>boot-args</key>
<string>agdpmod=pikera shikigva=80 -wegtree -no_compat_check</string>
Last edited:
Perhaps I'm blind, but I don't see a difference in the before/after "PlatformInfo" section.
@heero503, because you have a dual-processor system, you will additionally need to install AppleMCEReporterDisabler.
Thank CDF I have it inside the KEXT folder.
There is AppleMCEReporterDisabler.kext, Lilu.kext, WhateverGreen.kxt
I follow h9826790 advise to edited the config and result endless loop. When the first time, I still can goto SATA internal drive Catalina. After reboot, all drive is endless root.
I do Nvram reset and it will result can boot in to NvEM drive.
Hardware decoding is confirm work now.
Current status is SIP enabled due to NvRam reset but my LG cannot set any 2560X 1080 HIDPI 60Hz only available in 30 Hz
HDR work for LG mon
I will not shut down my machine and I upload my config and system log file for you guy to see if I have done anything wrong.
h9826790 and cdf Thanks for your support!
You may have it in the folder but not in the config file. Therefore it will not operate. If you want to see what is going on you need to set:
Code:
<key>Debug</key>
<dict>
<key>DisableWatchDog</key>
<true/>
Code:
<key>PanicNoKextDump</key>
<true/>where? Sorry i am not good in config coding
is it means here?
<key>boot-args</key>
<string>agdpmod=pikera shikigva=80 -wegtree -no_compat_check</string>
Like that?
<key>boot-args</key>
<string>agdpmod=pikera shikigva=80 -wegtree -no_compat_check -v</string>
added -V and all drive cannot bootup, boot screen gary screen but no apple logo and many coding in boot screen and some showing fault, reboot and loop.
Tonight, I will boot it from Mojave and return to cdf config file first.
cdf config is the only config I can success boot right now to bootup but no hardware decoding...
This is hard~ haha
For LG over 2K only 30Hz issue that my mistake, I changed the Monitor DP to 1.2😝
Tonight, I will boot it from Mojave and return to cdf config file first.
cdf config is the only config I can success boot right now to bootup but no hardware decoding...
This is hard~ haha
For LG over 2K only 30Hz issue that my mistake, I changed the Monitor DP to 1.2😝
This is exactly why we want you to boot verbose mode, what’s the error?
OK I will do it tonight, many code inside and I will auto reboot. I try to capture it.
Capture a video, it should be relatively easy to capture the critical error message
OK will do later~
I have installed Teamviewer in system and I have seen my machine is online now but it cannot be login.
I believe it is because it hold in the error shut down, reopen app question screen and not enter to desktop.
There is very strange that the machine will endless reboot but sometime it will enter the system...
When you reboot, it will endless reboot again until suddenly success again...
Updated:
I have downloaded the package provided by Startergo "REL-057-2020-03-06" and copy to overwrite all of my EFI setting.
It can be normal boot with hardware decoding except there is no boot menu in dual monitor.
Is it normal? My monitor is one LG 34WK95U-W (5120x2160), and a Asus PB279 (2560X1440)
If only power on Asus, boot menu appear but LG no HIDPI in 60Hz, only 30Hz
If power on Both, there is no boot menu but everytime will be normal have HiDPI with 60Hz
How can I have boot menu with both monitor open and show in LG?
Thanks startergo, cdf and h9826790! Great help for me!
Last edited:
That is because 4K requires different setting.
Regular screen:
Code:
<key>UIScale</key>
<data>
AQ==
</data>
Code:
<key>UIScale</key>
<data>
Ag==
</data>
Code:
Resolution
Type: plist string
Failsafe: Empty string
Description: Sets console output screen resolution.
• Set to WxH@Bpp (e.g. 1920x1080@32) or WxH (e.g. 1920x1080) formatted string to request custom resolution from GOP if available.
• Set to empty string not to change screen resolution.
• Set to Max to try to use largest available screen resolution.
On HiDPI screens APPLE_VENDOR_VARIABLE_GUID UIScale NVRAM variable may need to be set to 02 to enable HiDPI scaling in Builtin text renderer, FileVault 2 UEFI password interface, and boot screen logo. Refer to Recommended Variables section for more details
4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:UIScale
One-byte data defining boot.efi user interface scaling. Should be 01 for normal screens and 02 for HiDPI screens.