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
I made a mistake, to update your EFI 0.6.5 --> 0.6.5 drm fix.
On Catalina, I delete /BOOT and /OC folders and add the one from the new "drm fix".
I made some change in the config.plist.
I enabled TB3 (I own a Titan Ridge flashed), Radeon Boost (I own a RX580 Pulse) but it's the first time I heard about Radeon Boost - never enabled this before, and finally enabled updates following your video.
I disabled AppleMCEReporterDisabler as I have a solo processor.
I had HW Acceleration with the last version, but not anymore in Videoproc 4.0 with this drm fix version.
What do you advise me to do now? It was an error to delete this folder instead of sliding the folders, right?
Well thanks in adavance.
On Catalina, I delete /BOOT and /OC folders and add the one from the new "drm fix".
I made some change in the config.plist.
I enabled TB3 (I own a Titan Ridge flashed), Radeon Boost (I own a RX580 Pulse) but it's the first time I heard about Radeon Boost - never enabled this before, and finally enabled updates following your video.
I disabled AppleMCEReporterDisabler as I have a solo processor.
I had HW Acceleration with the last version, but not anymore in Videoproc 4.0 with this drm fix version.
What do you advise me to do now? It was an error to delete this folder instead of sliding the folders, right?
Well thanks in adavance.
Just re-download the latest package, do NOT mod it, and follow the video to "update" OC.
After 1st reboot, you should have HWAccel.
If that works, then enable TB3, disable AppleMCEReporterDisabler (not require), and enable Radeon Boost.
If doesn't work, please simply install the OC 0.6.5 (NOT the DRM fix version). The DRM fix version aim to provide DRM fix for Big Sur, nothing new for Catalina.
In my opinion you have to disable the MacPro1,1 spoofing while installing Big Sur. You can enable it back after first installation made with a fitting patcher.
This gives you OTA upgrades and all other features.
At least this is what I had and have to do using an iMac with an RX580 MXM GPU.
Do you advice to use radeonboost on big sur ? I thought it was not working for macOS 11.
Sorry for my lack of experience, but what is the difference between the attachment "OpenCore 0.6.5 DRM fix" and "OpenCore 0.6.5"? Thanks in advance!
You may google what DRM is.
But in short, the latest package allow us to watch TV+ in Big Sur.
But in short, the latest package allow us to watch TV+ in Big Sur.
Hi, i have used the config from the WIKI and have made some changes. it runs well for me, but with your work, i have some new cool features (like the graphical BootPicker). Thanks for your work.
I use a flashed 5.1 and with Big Sur i have no options to stream my music via Airplay to my HomePod. That worked fine for me in Catalina. Is there a passage in the config i have to change for this feature?
I use a flashed 5.1 and with Big Sur i have no options to stream my music via Airplay to my HomePod. That worked fine for me in Catalina. Is there a passage in the config i have to change for this feature?
Perhaps its because i have to activate my AirPort at first with changing the config. Its an old AirPort/BT Card without Handoff support. In my Music app is the HomePod listed, but when i activate it, there will be an error-message that it can't be found or activated via Airplay. And perhaps it worked only with my other Macs ... i don't know 100%
Hi, Martin. I know it could "sound" a little out of topic, but could it be possible to fix audio, the crackling sound some of us experience when playing through Safari or Apple Music, with OpenCore? I have try in different forums but nobody seems to have an answer. I have seem some little improvements with this latest OpenCore 0.6.5 DRM fix, so I'm wondering if it could be farther and correct the sound issues that seems to be related to the CPU with both MacPro 4.1 and 5.1. For me, it worked fine with OpenCore and Catalina, but the issues that started with the latest Mojave versions returned in Big Sur from beta 1 until now. Thank you in advanced.
Why OpenCore would solve the removed support of Nehalem dual processors? Why not upgrade the processors and solve it once and for all? You can buy two X5677s for less than $35 and delid it easily.
Btw, this is a problem only for early-2009 dual CPU Mac Pros still with the original Nehalem Xeons (E55xx), the stuttering never happens with MP5,1, since all dual MP5,1 are Westmere.
Do you mean this CPU?
Attachments
Last edited:
@h9826790 Thank you "again" for your work and your latest OC package.
FYI: I use the boot picker only if I press and hold ESC at start after the sound chime. After my first boot I was wonder of the missing mouse pointer that was for me a good indicator that it's safe to release the ESC key and see the boot picker volumes. I fix it for me and put the integer value of 19 at the PickerAttributes section and so I enable 2 attributes I want:
0x0002 — OC_ATTR_USE_DISK_LABEL_FILE, provides custom rendered titles for boot entries
0x0010 — OC_ATTR_USE_POINTER_CONTROL, enable pointer control in the picker when available
I saw that you had this value also at the opencore 0.6.4 package.
FYI: I use the boot picker only if I press and hold ESC at start after the sound chime. After my first boot I was wonder of the missing mouse pointer that was for me a good indicator that it's safe to release the ESC key and see the boot picker volumes. I fix it for me and put the integer value of 19 at the PickerAttributes section and so I enable 2 attributes I want:
Configuration
dortania.github.io
0x0002 — OC_ATTR_USE_DISK_LABEL_FILE, provides custom rendered titles for boot entries
0x0010 — OC_ATTR_USE_POINTER_CONTROL, enable pointer control in the picker when available
I saw that you had this value also at the opencore 0.6.4 package.
Thanks for the report, I will make picker attribute = 19 as default in the future package release.
So , you have set:
0x0001 — OC_ATTR_USE_VOLUME_ICON, provides custom icons for boot entries
0x0002 — OC_ATTR_USE_DISK_LABEL_FILE, provides custom rendered titles for boot entries
0x0010 — OC_ATTR_USE_POINTER_CONTROL, enable pointer control in the picker when available
to have 19 in decimal (0x0013 in hexadecimal)?
You are right... about the HEX to Integer values... but:
I play around a little bit with that values and meanings but I never get my own ".VolumeIcon.icns" shown at startup. So I get a new icon set from here and put the value to 16 (mouse pointer only). Also the custom labels I don't use - the picker shows my correct internal volume names.
My first post, although long time reader of cMP threads. First of all, thanks h9826790 for sharing your work and for your support in this forum. And thanks to all contributors to this thread.
My system: cMP4,1->5,1 / 144.0.0.0.0 / 12-Core 3.33GHz Dual X5680 / Non-Flashed Radeon RX Pulse 580 8GB / 24GB RAM / Current Boot Drive SSD on OWC Accelsior S PCIe Adapter.
My cMP is getting stuck at boot - it startups but then loses power after a while and shutdown. This is what I did:
1- Originally had Mojave 10.14.6 running without issues. Followed instructions of post #1314 and successfully installed latest package 0.6.5 with DRM fix.
2- Re-enabled SIP at the end of the process.
3- System booted well but did not show boot picker screen. Followed the suggestion to flip switch on RX580 and that did the trick - boot screen showed afterwards as expected. Hardware acceleration showed up in VideoProc As expected.
4- Went ahead and downloaded and installed Big Sur 11.1. Process went smoothly. Everything worked well once installed, no issues.
5- Only thing I noticed was the RX580 fan was spinning fast as mentioned in prior posts in this thread.
6- Now this is where I obviously made a (very newbie) mistake: I went ahead and did a 3x NVRAM reset as I thought that would help... And after that NVRAM reset, the system starts up but does not load/reach the boot screen and shuts down.
My sense is that I should follow this suggestion from post #1: “If your cMP stuck at boot. After shutdown, please pull out the hard drive that contain OpenCore, then perform NVRAM reset. If still doesn't work, then please install your emergency graphic card that has boot screen. Hold Option to boot, then select your backup boot drive. This should disable OpenCore.”
Could you please advise if, indeed, the above is what I should try? If not, is there any other way to solve the getting-stuck-at-boot issue?
Thanks in advance!
My system: cMP4,1->5,1 / 144.0.0.0.0 / 12-Core 3.33GHz Dual X5680 / Non-Flashed Radeon RX Pulse 580 8GB / 24GB RAM / Current Boot Drive SSD on OWC Accelsior S PCIe Adapter.
My cMP is getting stuck at boot - it startups but then loses power after a while and shutdown. This is what I did:
1- Originally had Mojave 10.14.6 running without issues. Followed instructions of post #1314 and successfully installed latest package 0.6.5 with DRM fix.
2- Re-enabled SIP at the end of the process.
3- System booted well but did not show boot picker screen. Followed the suggestion to flip switch on RX580 and that did the trick - boot screen showed afterwards as expected. Hardware acceleration showed up in VideoProc As expected.
4- Went ahead and downloaded and installed Big Sur 11.1. Process went smoothly. Everything worked well once installed, no issues.
5- Only thing I noticed was the RX580 fan was spinning fast as mentioned in prior posts in this thread.
6- Now this is where I obviously made a (very newbie) mistake: I went ahead and did a 3x NVRAM reset as I thought that would help... And after that NVRAM reset, the system starts up but does not load/reach the boot screen and shuts down.
My sense is that I should follow this suggestion from post #1: “If your cMP stuck at boot. After shutdown, please pull out the hard drive that contain OpenCore, then perform NVRAM reset. If still doesn't work, then please install your emergency graphic card that has boot screen. Hold Option to boot, then select your backup boot drive. This should disable OpenCore.”
Could you please advise if, indeed, the above is what I should try? If not, is there any other way to solve the getting-stuck-at-boot issue?
Thanks in advance!
If you still have Mojave, pull out the Big Sur drive, then your cMP should boot to Mojave automatically.
Then you can boot to the recovery partition, disable SIP, and re-install OC etc.
Or you can swap in your original GPU, hold option to boot, and select EFI from there. That should be your OpenCore. And then you can boot to Big Sur again, and mount the EFI partition, and re-bless OC.