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.
0.8.8 macOS 12.6.3 working - with some restart/shutdown oddities


Yes, you called it correctly, a missing '<' due to my fingers expecting karabiner-elements remappings which are in my user account but not the admin account I use for macOS installs/updates.

Also, thanks for pointing out ocvalidate. I will try to use should I run into issues in the future. I must admit that I've only given a cursory viewing of the Dortania documentation and the OpenCore on MacPro thread.

I now have 0.8.8 with macOS 12.6.3 up and running. I had to edit
/System/Volumes/Preboot/uuid/System/Library/CoreServices/.disk_label.contentDetails to get the Boot Picker's drive name to match the boot volumes name. Is that the recommended way to deal with boot volume name changes or is there some other mechanism?

I do have a couple of issues with shutdown and reboot from the Apple menubar. This behaves slightly differently for my different accounts.

In my Admin account which is the cleanest, of I select restart, I see my desktop contents and menubar disappearing, then a momentary flash of a black screen, then the desktop background image with nothing else on it, at which point it waits for two minutes, then goes black and the boot picker. If I select shutdown, similar behavior with displaying the desktop background for two minutes, and then it will shutdown. Note, when I restart after the boot picker I do get the macOS flash screen stating "Your computer restarted because of a problem". This is for both a restart or shutdown.

In my main user account, there is slightly different behavior. Restart is the same as the admin account. However, for shutdown, it never shuts down. Rather the desktop only image is displayed for five minutes after which it displays the opencore bootpicker. I can shutdown by selecting the power button in the opencore bootpicker.

In all cases, macOS thinks ""Your computer restarted because of a problem" and after login I am presented with the dialogs for automatically restarting applications. I am puzzled by that because it starts up some applications even though I had quit them prior to selecting shutdown. It doesn't start everything. Just a couple of processes.

Also, shutdown -h now, in terminal has similar behaviour and doesn't really shutdown the computer but it does get me to the boot picker screen without the five minute wait.

I'm suspecting these restart and shutdown issues are not really due to opencore. Any thoughts on how to investigate?
Sounds like one of the user installed software fail to close. Which makes the OS stuck.

Just pure guess, when you command shutdown with admin account. It has high enough permission to force shutdown after time out. But the log still count that as an "abnormal shutdown".

When you command shutdown with your user account. The computer have to wait for that software to close, which never happen.

You may try if the attached software help. I have no such issue, can't test it on my cMP. But this little app seems can help to fix some shutdown issue on eariler macOS (e.g. Mojave).
 

Attachments

  • OS X Shutdown Fix.dmg.zip
    135.6 KB · Views: 103
  • Like
Reactions: cmphal
In order to have legacy bluetooth working on Monterey, I have to replace Comment with Enabled in Bluetooth-Spoof.kext and BlueToolFixup.kext. Correct?
 
In order to have legacy bluetooth working on Monterey, I have to replace Comment with Enabled in Bluetooth-Spoof.kext and BlueToolFixup.kext. Correct?
Correct, but no guarantee. My own beta testers told me they can activate legacy BT on their cMP by doing that. But many users also reported it doesn't work on their cMP. So, you have to try it by yourself.
 
  • Like
Reactions: captainhulk
I wouldn't do it now, there are Mac Pro BootROM modifications/improvements on this topic in the near future, with free and commercial solutions being developed and tested. Since it's not public yet, I can't give you more info, but works 100% with RX 580/VEGA 56/RX 6600 and most recent AMD GPUs - I don't own a VII and don't know if works or not, VII cards are somewhat problematic.

If it's critical for you to it right now, it's possible to flash the VII, but it's not a flashing yourself procedure. You can ask MacVidCards Europe if they can provide flashing service for the VII.
The VII is problematic as it has "elevated security".. since the GPU chip came straight from the HPC segment, it is protected by a key set in hardware, and the vbios is apparently encrypted to suit that key. If it does not check out with the key, it is a brick.. until reflashed. This was to avoid people purchasing "cheap" VII cards and converting them to the several times more expensive HPC cards based on the same chip.. i.e. unlocking the full FP64 speed typically very useful for scientific computations and simulations.
 
Last edited:
  • Like
Reactions: h9826790
I am having issue with HWAccel and Ventura 13.2 that I recently installed using OCLP 0.6.1. It simply is not enabled. The card is the Radeon VII, and it was fully activated under Monterey. Booting Catalina from the same boot loader now activates it.. So, some difference in Ventura prevents it from activation - maybe not a surprise considering how much was changed in the graphics stack and what went into making OCLP for Ventura work.
 
  • Like
Reactions: Narkoverian
The VII is problematic as it has "elevated security".. since the GPU chip came straight from the HPC segment, it is protected by a key set in hardware, and the vbios is apparently encrypted to suit that key. If it does not check out with the key, it is a brick.. until reflashed. This was to avoid people purchasing "cheap" VII cards and converting them to the several times more expensive HPC cards based on the same chip.. i.e. unlocking the full FP64 speed typically very useful for scientific computations and simulations.
I'm not referring to the signed GOP/VBIOS/firmware, but to the card personality - AMD did make a mess.

Even with a Mac Pro firmware modified for pre-boot configuration support with GOP cards and perfectly working with RX 580/VEGA 56/RX 6600/RX 6800XT and not modifying anything with the factory VII firmware, VII GPUs are troublesome with providing pre-boot configuration support.
 
I'm not referring to the signed GOP/VBIOS/firmware, but to the card personality - AMD did make a mess.

Even with a Mac Pro firmware modified for pre-boot configuration support with GOP cards and perfectly working with RX 580/VEGA 56/RX 6600/RX 6800XT and not modifying anything with the factory VII firmware, VII GPUs are troublesome with providing pre-boot configuration support.
Interesting.. is this modified Mac Pro firmware supporting GOP a recent development? Hope it will be available at some point. Very interesting indeed.

Radeon VII also requires a special setting in the Open Core configuration to avoid distorted or maybe even no output; DirectGopRendering set to true. Maybe some connection.
 
If trying to run a 4K TV via HDMI from an AMD RX5700 XT card in the Mac Pro (Mid 2010) in macOS Monterey at times causes the computer to suddenly turn off, is it because the power supply can’t keep up, or what do you think? Never had any problems when driving a 1080p TV or a 1920x1200 display via DisplayPort to DVI.
 
If trying to run a 4K TV via HDMI from an AMD RX5700 XT card in the Mac Pro (Mid 2010) in macOS Monterey at times causes the computer to suddenly turn off, is it because the power supply can’t keep up, or what do you think? Never had any problems when driving a 1080p TV or a 1920x1200 display via DisplayPort to DVI.
Do you have Pixla's mod done to your power supply? That card requires an 8 pin and a 6 pin connector The connections on the backplane board are not enough at heavy loads
 
Do you have Pixla's mod done to your power supply? That card requires an 8 pin and a 6 pin connector The connections on the backplane board are not enough at heavy loads
No, where can I read more on that? I haven't had any problem with heavy loads before – when on a lower pixel display (1920 x 1200).

Thanks!
 
No, where can I read more on that? I haven't had any problem with heavy loads before – when on a lower pixel display (1920 x 1200).

Thanks!

This is the Pixla's mod reference thread:

 
Last edited:
  • Like
Reactions: star-affinity
Any guide or easy video to follow on how to switch from OCLP to Martins Build?
For unpatched macOS, same as update OpenCore
 
  • Like
Reactions: Rams1976
Can we use the kexts from OCLP to fix the legacy Wi-Fi and BT issue in martins build by adding them to the EFI folder and amending the config.plist?
 
  • Like
Reactions: osxfr33k
Hi @h9826790, Could you clear my doubts?
I removed OCLP and put in Martin OC.
1 - When I turn on MacOS, the OpenCore Boot Picker does not appear, I am using a Sapphire RX580 8GB Pulse, and Apple Boot Loading does not appear and an image appears when it asks for the user's password.
2 - When I order to restart the system, it doesn't show the image and it doesn't even enter OpenCore and MacOS, so I have to turn off MacOS and start again, and the issue of the first question occurs.

The strangest thing, if I put the SSD that is with the original EFI it starts normally.
What configuration do I need to make to stop these problems from occurring?
 
Hi @h9826790, Could you clear my doubts?
I removed OCLP and put in Martin OC.
1 - When I turn on MacOS, the OpenCore Boot Picker does not appear, I am using a Sapphire RX580 8GB Pulse, and Apple Boot Loading does not appear and an image appears when it asks for the user's password.
2 - When I order to restart the system, it doesn't show the image and it doesn't even enter OpenCore and MacOS, so I have to turn off MacOS and start again, and the issue of the first question occurs.

The strangest thing, if I put the SSD that is with the original EFI it starts normally.
What configuration do I need to make to stop these problems from occurring?
I am not an OCLP user, but form memory, OCLP may inject the required GOP driver for the user if needed. May be your card has no working GOP drive, therefore, only works with OCLP.

Technically, even the OS is patched, the RX580 can still show the boot screen by using my OC package. Many users confirmed this.

If your card has broken GOP, the most permanent solution should be flashing the card with a known good factory ROM.
 
I am not an OCLP user, but form memory, OCLP may inject the required GOP driver for the user if needed. May be your card has no working GOP drive, therefore, only works with OCLP.
For this point, I did a clean install, formatted the SSD, installed Mojave and mounted the EFI and put your EFI, and strangely no image appears, and when I updated to BigSur and Monterrey I had the same problem, that when I restarted it did not enter OpenCore and stayed no image and had to shut down Mac and start again.
Technically, even the OS is patched, the RX580 can still show the boot screen by using my OC package. Many users confirmed this.
Using the original Mojave SSD, without changing the EFI, the gray bootscreen appears normally with the RX580.
If your card has broken GOP, the most permanent solution should be flashing the card with a known good factory ROM.
I believe this is not the problem, as the GPU using original EFI without OpenCore enters normally.

Initially I thought that it could be the motherboard battery not holding the OpenCore configuration to start, but I confirmed that it was not, because the SSD without modified EFI enters normally.

Issue OpenCore <<-- Video issue in OpenCore
 
Last edited:
For this point, I did a clean install, formatted the SSD, installed Mojave and mounted the EFI and put your EFI, and strangely no image appears, and when I updated to BigSur and Monterrey I had the same problem, that when I restarted it did not enter OpenCore and stayed no image and had to shut down Mac and start again.

Using the original Mojave SSD, without changing the EFI, the gray bootscreen appears normally with the RX580.

I believe this is not the problem, as the GPU using original EFI without OpenCore enters normally.

Initially I thought that it could be the motherboard battery not holding the OpenCore configuration to start, but I confirmed that it was not, because the SSD without modified EFI enters normally.

Issue OpenCore <<-- Video issue in OpenCore
If I understand correctly, you mean

1) Clean Mojave (no OpenCore) + RX580 = no boot screen, but works when the OS GPU driver is loaded

2) Mojave + my OC package + RX580 = same, no boot screen, but works when the OS GPU driver is loaded

If this is true, then 99% your RX580's GOP is broken (e.g. was flashed with a mining firmware etc), and the permanent way to re-gain the GOP boot screen ability (e.g. show boot screen with my OC package), is by flashing the RX580.

Otherwise, you may stay with OCLP if it can make your RX580 shows boot screen.
 
If I understand correctly, you mean

1) Clean Mojave (no OpenCore) + RX580 = no boot screen, but works when the OS GPU driver is loaded

2) Mojave + my OC package + RX580 = same, no boot screen, but works when the OS GPU driver is loaded

If this is true, then 99% your RX580's GOP is broken (e.g. was flashed with a mining firmware etc), and the permanent way to re-gain the GOP boot screen ability (e.g. show boot screen with my OC package), is by flashing the RX580.

Otherwise, you may stay with OCLP if it can make your RX580 shows boot screen.
But there's a third point, that when I restart MacOS, it doesn't boot the system, let alone launch OpenCore, as if it doesn't save the configuration, and with that I need to shut down MacPro and boot again.
 
But there's a third point, that when I restart MacOS, it doesn't boot the system, let alone launch OpenCore, as if it doesn't save the configuration, and with that I need to shut down MacPro and boot again.
Two suggestions.

1) Fix the problem one by one. That reboot problem isn't boot screen related. Set that aside first.

2) This issue isn't HWAccel related anymore. And most likely cannot be fixed within few posts. I suggest you open a new thread to discuss this issue.
 
i try to install OPC 0.8.8 on my Mac Pro 5.1 and Monterey.(AMD Radeon R9 270X) Titan Ridge 2
i get this error on start after i select the startup disc.

" FileSetPosition:3117:FileSetPosition:attenpt to set position for directory to 184467440737709551615"

then reebot again.

can someone attach me a ready 0.8.8 OPC thath work?
THX
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.