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
Jumped onto rust to see if the activation worked. I get an average of 11 fps and every 5 minutes of running around its 4 fps at it's lowest settings. I see nothing outside that my internals are heating up and i'm using full blast to cool it down every time ambient goes over 28*C every few minutes. Awesome work x5690-radeon vii-and nvme ssd-and 96 supposedly triple channel. I got better scores with a 2.4 ghz 1gb 5870. 24gb ram with a hdd with no open core a y̶e̶a̶r̶ few years ago. what's up?
who wants a radeon vii that performs worse than a 5870 i guess? cool beanz
edit: analogous to what i'm doing with video. transferred film. scrubbing is like skating through ditches, run stop run stop. hate premiere as well, but i'm saving my temper tantrum for adobe because that's what i pay them for. bogus
who wants a radeon vii that performs worse than a 5870 i guess? cool beanz
edit: analogous to what i'm doing with video. transferred film. scrubbing is like skating through ditches, run stop run stop. hate premiere as well, but i'm saving my temper tantrum for adobe because that's what i pay them for. bogus
Last edited:
@h9826790
Hi Martin.
What changes need to be made to your config/kexts to get BT working on Monetery OC 0.77 with BCM94360 Card upgrade installed. Wifi is working but not bluetooth and I am not sure if we screwed up the installation or its related to OC configs or kexts!
Thank you
New card: Broadcom BCM943602CDP
System Info:
Bluetooth Controller:
Address: NULL
State: Off
Chipset: BCM_4350C2
Discoverable: Off
Firmware Version: v0 c0
Product ID: 0x0001
Supported Devices: 0x382039 < HFP AVRCP A2DP HID Braille AACP GATT Serial >
Transport: USB
Vendor ID: 0x004C (Apple)
Hi Martin.
What changes need to be made to your config/kexts to get BT working on Monetery OC 0.77 with BCM94360 Card upgrade installed. Wifi is working but not bluetooth and I am not sure if we screwed up the installation or its related to OC configs or kexts!
Thank you
New card: Broadcom BCM943602CDP
System Info:
Bluetooth Controller:
Address: NULL
State: Off
Chipset: BCM_4350C2
Discoverable: Off
Firmware Version: v0 c0
Product ID: 0x0001
Supported Devices: 0x382039 < HFP AVRCP A2DP HID Braille AACP GATT Serial >
Transport: USB
Vendor ID: 0x004C (Apple)
Last edited:
@h9826790
Martin:
I'm attempting to install Monterey on a 5,1 using your 0.7.8 V2 above (current release).
Box is 14.0.0.0 FW, with firmware rebuilt by Alex.
Dual Proc 3.46 6 Cores, Sapphire Pulse RX580.
Your OC is on it's own USB stick, the Monterey Installer on another one.
Monterey to be installed to a newly formatted (by the installer pre install) SSD with no partitions.
The OC Boot runs fine, it allows me to run the Monterey installer, it gets through it's first reboot (although I had to power it down and pack "macOSInstaller" from OC) and it continued to 2nd reboot. At this point it reboots, partially showing the progress bar, then the progress bar resets and the circle with a slash comes up.
I did a cold power, picked the installer from the OC menu, and then it comes up and says it needs a firmware update.
Now prior to this I watched the "Catalina / Monterey" video about how to turn on VMM Flag and switch off SMBIOS spoofing, but the video didn't have the usual closed captions on what to exactly set and the video is so blurry and moves so fast there's no way to tell what exactly to do, so I am just running your stock build at this point.
Any way to get past this?
Thanks
Mark
Last edited:
With the newer OC packages and Monterey I am experiencing extremely long boot times and sometimes it even fails to boot. If it fails to boot (it just gets stuck) a simple forced reboot does the job. Any suggestions?
Your config may be lacking the proper DataHub settings. See
OpenCore on the Mac Pro
Looks like we have our answer (thanks @vit9696!): https://github.com/acidanthera/bugtracker/issues/1903#issuecomment-1003723969 When using Lilu with recent versions of macOS, board-id should be present in IODeviceTree:/efi/platform. We can fix this by setting DataHub>BoardProduct to...
forums.macrumors.com
I am using the package from Martin lo, so can this still be an issue?Your config may be lacking the proper DataHub settings. See
OpenCore on the Mac Pro
Looks like we have our answer (thanks @vit9696!): https://github.com/acidanthera/bugtracker/issues/1903#issuecomment-1003723969 When using Lilu with recent versions of macOS, board-id should be present in IODeviceTree:/efi/platform. We can fix this by setting DataHub>BoardProduct to...
If I following your hint I find the following thing in my config:
</dict>
<key>PlatformInfo</key>
<dict>
<key>Automatic</key>
<false/>
<key>CustomMemory</key>
<false/>
<key>Generic</key>
<dict>
should I set Automatic now to true?
Last edited:
Yes.
No. This is what you need to do:
- Below
Code:<key>CustomMemory</key> <false/>
add
Code:<key>DataHub</key> <dict> <key>ARTFrequency</key> <integer>0</integer> <key>BoardProduct</key> <string>Mac-7BA5B2D9E42DDD94</string> <key>BoardRevision</key> <data></data> <key>DevicePathsSupported</key> <integer>0</integer> <key>FSBFrequency</key> <integer>0</integer> <key>InitialTSC</key> <integer>0</integer> <key>PlatformName</key> <string></string> <key>SmcBranch</key> <data></data> <key>SmcPlatform</key> <data></data> <key>SmcRevision</key> <data></data> <key>StartupPowerEvents</key> <integer>0</integer> <key>SystemProductName</key> <string></string> <key>SystemSerialNumber</key> <string></string> <key>SystemUUID</key> <string></string> </dict>
- Find
Code:<key>UpdateDataHub</key> <false/>
and change "false" to "true".
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
Alright, thank you very much! My machine still boots so everything should be fine. Will report if this solved the issue or not.Yes.
No. This is what you need to do:
You can learn more about setting up and maintaining OpenCore on your own here:
- Below
Code:<key>CustomMemory</key> <false/>
add
Code:<key>DataHub</key> <dict> <key>ARTFrequency</key> <integer>0</integer> <key>BoardProduct</key> <string>Mac-7BA5B2D9E42DDD94</string> <key>BoardRevision</key> <data></data> <key>DevicePathsSupported</key> <integer>0</integer> <key>FSBFrequency</key> <integer>0</integer> <key>InitialTSC</key> <integer>0</integer> <key>PlatformName</key> <string></string> <key>SmcBranch</key> <data></data> <key>SmcPlatform</key> <data></data> <key>SmcRevision</key> <data></data> <key>StartupPowerEvents</key> <integer>0</integer> <key>SystemProductName</key> <string></string> <key>SystemSerialNumber</key> <string></string> <key>SystemUUID</key> <string></string> </dict>
- Find
Code:<key>UpdateDataHub</key> <false/>
and change "false" to "true".
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.
Being new here, I understand this is an old post. Trying to decide on OC or OCLP but reading this install process became confused . My understanding after reading just about everything on this, I was under the impression that using the clover configurator was for hackintosh only but keep seeing this being applied to the Mac Pro as well. So is this for the cMP or just Hackintosh?
Last edited:
Just got this notification in Monterey 12.2 for my macOS drive:
Anyone recognize it?
Not sure if it was a conicence, but it came up at the exact same time as when I removed the cable from my wireless Apple keyboard which I usually use via Bluetooth. This has been working reliably via Bluetooth when switching between Windows 10 and macOS Monterey, but as of late I have to remove and re-pair the keyboard when going from one operating system to the other. Not sure why.
Found these articles on the topic:
osxdaily.com
For some other users, the error message appears if they’re running macOS Monterey on an officially unsupported Mac.
insightvas.com
?♂️
Anyone recognize it?
Not sure if it was a conicence, but it came up at the exact same time as when I removed the cable from my wireless Apple keyboard which I usually use via Bluetooth. This has been working reliably via Bluetooth when switching between Windows 10 and macOS Monterey, but as of late I have to remove and re-pair the keyboard when going from one operating system to the other. Not sure why.
Found these articles on the topic:
“Volume Hash Mismatch” Error in MacOS Monterey
Some macOS Monterey users are encountering a peculiar “Volume Hash Mismatch” error message, informing them that a hash mismatch was detected and to reinstall macOS on the volume. The fu…
osxdaily.com
For some other users, the error message appears if they’re running macOS Monterey on an officially unsupported Mac.
“Volume Hash Mismatch” Error in MacOS Monterey
Some macOS Monterey users are encountering a peculiar “Volume Hash Mismatch” error message, informing them that a hash mismatch was
insightvas.com
?♂️
Curious if anyone can chime in about about upgrading from Big Sur to Monterey - I'm currently on the Martins latest package (0.7.8) Am I able to simply install the upgrade from the standard Apple installer (are are there any special considerations if so)? Or do I have to wipe and reinstall fresh (which I'd rather not if possible)?
Thanks!
Joey
Thanks!
Joey
On my test environment (256 sata drive), I managed To get update without big trouble from each version to latest Monterey included. This is a clean install, without software nor data that I'm using to test upgrades.
On my « real » environment (1 To nvme drive) that was the same way before but I can’t do the update at Time each Time I’ve trie, it fails.
This comes probably from an old driver or software or nvme drive … but I haven’t had Time yet to start from a clean install To do it.
Stick To « only » big sur, but I have security update from a non obsolete system, this is ok for me (no more on Mojave !)
When I will have time , I‘ll try as proposed on this thread a clean install and restore onl’y data from my timebackup…
On my « real » environment (1 To nvme drive) that was the same way before but I can’t do the update at Time each Time I’ve trie, it fails.
This comes probably from an old driver or software or nvme drive … but I haven’t had Time yet to start from a clean install To do it.
Stick To « only » big sur, but I have security update from a non obsolete system, this is ok for me (no more on Mojave !)
When I will have time , I‘ll try as proposed on this thread a clean install and restore onl’y data from my timebackup…
Last edited:
Finaly I take time this week-end to copy with Superduper! my working test drive to the day2day one and restore datas with Apple migration assistant from a TimeMachine Backup.
All working as a charm.
The only thing is on boot time both drive/partition are named the same as I copy the disk, is there an easy way to change boot screen partition names to avoid misunderstanding.
The strange thing is that once botted, drives names are ok in MacOS environment/DiskUtil etc.
Confused about SIP status. I have a 5,1cMP running 11.6.4. I had OC 0.7.6 installed and tonight went to 0.7.8V2. With both versions, csrutil status shows: SIP disabled. I can't turn it on or off in recovery and according to recent posts, it's supposed to be "custom" now anyway. The original video at the beginning of this thread is out of date on SIP settings.
So...
Why does my status show SIP as disabled?
Should SIP be enabled or disabled with Martin's 0.76 and 0.78 packages by default?
In either case, should I and how do I re-enable it?
thanks.
So...
Why does my status show SIP as disabled?
Should SIP be enabled or disabled with Martin's 0.76 and 0.78 packages by default?
In either case, should I and how do I re-enable it?
thanks.
Attachments
Hi everyone! I'm using Martin Lo's 0.7.6 package with Big Sur 11.6.4 and couldn't be happier. Both Big Sur and the 0.7.6 EFI are on the same SSD and I keep all working files on other drives - so it's truly a boot drive. I want to keep a reliable backup. So far I've done this by plugging in another SSD via a SATA USB adapter and used Carbon Copy Cloner to create a clone. I wasn't able to get that script (EFIClone) that various folks have linked to to work to copy the EFI after the CCC job, so instead I just mounted the EFI partitions using Clover and dragged the file structure from my boot drive to my backup drive. (For those curious - the EFIClone script just seemed to hang at postflight - I didn't investigate further)
Two questions:
1) Now that I've backed up my EFI partition once, do I ever have to do it again (unless I update to a newer version of Martin's package)? I'm not sure if files update on the partition or not.
2) If I'm trying to safeguard against the situation where the primary boot drive dies and I want to replace it with this backup, should I bless this backup's EFI as well? I never leave the backup drive plugged in during boot or anything - it's just on a monthly backup cycle since it's just apps and would be replaceable (with effort). I'm not really sure what blessing is all about - and not sure if you can bless a drive while another blessed drive is already in place? Like I said I'm super happy with this setup and don't want to rock the boat.
Thanks!!
Two questions:
1) Now that I've backed up my EFI partition once, do I ever have to do it again (unless I update to a newer version of Martin's package)? I'm not sure if files update on the partition or not.
2) If I'm trying to safeguard against the situation where the primary boot drive dies and I want to replace it with this backup, should I bless this backup's EFI as well? I never leave the backup drive plugged in during boot or anything - it's just on a monthly backup cycle since it's just apps and would be replaceable (with effort). I'm not really sure what blessing is all about - and not sure if you can bless a drive while another blessed drive is already in place? Like I said I'm super happy with this setup and don't want to rock the boat.
Thanks!!
I just updated to Martin Lo's 0.78v2 and macOS 12.3, and my Mac won't boot. It booted once after installing 12.3 (think it took a couple of tries). But hasn't booted since I turned off VMM spoofing (just hangs at about 50%).Yes.
No. This is what you need to do:
You can learn more about setting up and maintaining OpenCore on your own here:
- Below
Code:<key>CustomMemory</key> <false/>
add
Code:<key>DataHub</key> <dict> <key>ARTFrequency</key> <integer>0</integer> <key>BoardProduct</key> <string>Mac-7BA5B2D9E42DDD94</string> <key>BoardRevision</key> <data></data> <key>DevicePathsSupported</key> <integer>0</integer> <key>FSBFrequency</key> <integer>0</integer> <key>InitialTSC</key> <integer>0</integer> <key>PlatformName</key> <string></string> <key>SmcBranch</key> <data></data> <key>SmcPlatform</key> <data></data> <key>SmcRevision</key> <data></data> <key>StartupPowerEvents</key> <integer>0</integer> <key>SystemProductName</key> <string></string> <key>SystemSerialNumber</key> <string></string> <key>SystemUUID</key> <string></string> </dict>
- Find
Code:<key>UpdateDataHub</key> <false/>
and change "false" to "true".
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.
Using Mojave, I applied the fixes to config.plist that you suggest above but it made no difference. Is anything else I need to do?
Last edited:
Yeah I've had this too, twice. Also use a wireless pro keyboard with numberpad (iMac Pro version), but haven't done anything unusual with that. Updated to 12.3 from 12.2 to see if it would fix the issue, but now my Mac won't boot. No hum...Just got this notification in Monterey 12.2 for my macOS drive:
View attachment 1970465
Anyone recognize it?
Not sure if it was a conicence, but it came up at the exact same time as when I removed the cable from my wireless Apple keyboard which I usually use via Bluetooth. This has been working reliably via Bluetooth when switching between Windows 10 and macOS Monterey, but as of late I have to remove and re-pair the keyboard when going from one operating system to the other. Not sure why.
Found these articles on the topic:
“Volume Hash Mismatch” Error in MacOS Monterey
Some macOS Monterey users are encountering a peculiar “Volume Hash Mismatch” error message, informing them that a hash mismatch was detected and to reinstall macOS on the volume. The fu…
For some other users, the error message appears if they’re running macOS Monterey on an officially unsupported Mac.
“Volume Hash Mismatch” Error in MacOS Monterey
Some macOS Monterey users are encountering a peculiar “Volume Hash Mismatch” error message, informing them that a hash mismatch was
?♂️
Damn it! Same here after updating to 12.3. Or rather, I managed to update after changing "Cpuid1Mask" to "on" to check for (find) and install the update. I could then boot into 12.3 fine, but then I switched back the "Cpuid1Mask" to "off" and restarted the computer -- after this I cannot get back into MacOS. Stalls or crashes and restarts during startup. OC 0.7.8.
Last edited:
Tried with the VMM flag set, as some people had success with this. Occasionally it gets to the desktop, but the keyboard doesn't work, so can't log in! Even using a regular RF keyboard.
Might try removing cdf's additions, but keep the VMM flag.
Also tried going back to OC 0.7.7, with and without VMM on, but that didn't work.
Edit: even with just Martin's stock OF 0.7.8 .plist with just the CPUID and SMBIOS stuff spoofed, it's still hanging at boot.
OK, I was able to log in by using VNC, but the physical keyboard still doesn't work! Can I downgrade to 12.2?
Might try removing cdf's additions, but keep the VMM flag.
Also tried going back to OC 0.7.7, with and without VMM on, but that didn't work.
Edit: even with just Martin's stock OF 0.7.8 .plist with just the CPUID and SMBIOS stuff spoofed, it's still hanging at boot.
OK, I was able to log in by using VNC, but the physical keyboard still doesn't work! Can I downgrade to 12.2?
Last edited:
Just went from Big Sur 11.6.3 to Monterey 12.3 using Martin Lo's 0.78 v2 package. I made the appropriate two modifications to the config.plist, and Monterey installed just fine. However, his instructions state that once Monterey is installed, you should revert those changes back to his original config.plist and reboot. I did that, and my system would not boot (showed the OC boot picker, showed the apple logo and the loading bar, then it would reboot). I tried resetting the SMC, resetting the NVRAM 3x, etc.
The only way I was able to get back into my machine was by putting my HD in another cMP I have, using Clover, and modding the config.plist back to what worked for the install. Now the machine boots but I have two issues.
1. I used a USB Broadcom Bluetooth adapter and I can't even get BT to turn on. I really need BT to work and didn't think this would be an issue since I'm not using the built-in BT of the machine.
2. When viewing system report, the system firmware says 144.0.0.0.0, when I believe it should state the OC version (how Martin has been doing it for quite some time now). I'm hoping this doesn't mean that OC isn't loading as I cannot afford the race condition to rear its head.
Hoping for some help. Thanks.
The only way I was able to get back into my machine was by putting my HD in another cMP I have, using Clover, and modding the config.plist back to what worked for the install. Now the machine boots but I have two issues.
1. I used a USB Broadcom Bluetooth adapter and I can't even get BT to turn on. I really need BT to work and didn't think this would be an issue since I'm not using the built-in BT of the machine.
2. When viewing system report, the system firmware says 144.0.0.0.0, when I believe it should state the OC version (how Martin has been doing it for quite some time now). I'm hoping this doesn't mean that OC isn't loading as I cannot afford the race condition to rear its head.
Hoping for some help. Thanks.
My internal (upgraded) BT isn’t working, but weirdly other, USB keyboards no longer work either. Mouse is fine. Remoting in with VNC at least gives keyboard access, though obviously isn’t convenient.
OC is definitely loading for me as I get the boot menu.
Looks like I’ll be restoring from a recent TM backup to 12.2, tomorrow night. I’m sure you used to be able to use a combo updater to go back a point revision?
Last edited: