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.
macOS 12 Monterey on Unsupported Macs Thread
- Thread starter khronokernel
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
basslik
macrumors 6502a
A few inquired about it in previous post. I'm sure someone could have done it by now I would imagine. nonetheless I'm okay with the red circle. I would like to find out how to see the firewire network icon in the network tab.
Tratkazir_the_1st
macrumors 65816
Hello! Why after I updated the video card from GTX Titan to RX 6800 XT, it stopped automatically transferring me to the Open Core EFI Boot loader. The video card is fully flashed for Mac Pro 5.1, was bought at Macvidcards.
When turning on, it automatically loads to somewhere unclear, on the screen is a loading bar without the Apple logo. I have to press alt myself and manually select the OpenCore loader.
I am using MacOS Monterey and OpenCore Patcher version 0.6.4. OpenCore loader is installed on an empty separate drive in the first
SATA slot. Please help what to do, I can't find anything on the internet.
When turning on, it automatically loads to somewhere unclear, on the screen is a loading bar without the Apple logo. I have to press alt myself and manually select the OpenCore loader.
I am using MacOS Monterey and OpenCore Patcher version 0.6.4. OpenCore loader is installed on an empty separate drive in the first
SATA slot. Please help what to do, I can't find anything on the internet.
tsialex
Contributor
It's a common issue, NVIDIA webdrivers for GTX Titan are known to mess with the MacPro5,1 BootROM's NVRAM volume, saving a big blob inside the VSS stores that blocks AMD GPUs to work. If you can't access the Apple native BootPicker with your RX 6800XT MacVidCards flashed GPU, you have this issue.
You can try a deep NVRAM reset, if doesn't work, you will need a BootROM reconstruction service. You will also gonna need to clean install Monterey, since when you install an unsupported release via OCLP, the root patching process removes all GPU drivers but the drivers for the GPU you had installed when you did the macOS install.
So, if you changed the Titan for the RX 6800XT without re-installing Monterey, the 6800XT didn't work because of the missing GPU drivers.
Yes. It has been discussed on this thread before (but I'm too lazy to search for the link, you can try finding it using thread tools). The "community recommended" way to deal with this is to install a profile to disable major updates but it will leave minor updates intact. One tool to use is "iMazing Profile Editor".
OCLP possibly did something to enable updating indiscriminately, I don't know. It's not important enough the Devs will look into this.
deeveedee
macrumors 68000
Very interesting. I don't have a MacPro5,1, so this is probably a naive question...
Instead of a BootROM recontruction, could OpenCore's ability to emulate NVRAM be used to overcome this issue? There are many hackintoshes that emulate MP5,1 without native NVRAM support (emulated with OpenCore). Again, probably a naive question... just wondering.
EDIT: Read a little more here.
Last edited:
tsialex
Contributor
Emulated NVRAM is loaded after POST, so, any issues that affect loading OPROMs and etc while doing POST still happen. It's not a solution for this type of issues.
I would like to clarify that my operating system actually works well, and I do get access to the EFI Boot Loader, but not automatically. Each time I start my computer, I need to manually press the 'alt' key to access the boot menu and manually select the EFI Boot Loader. This is not very convenient, and I am looking for a way to automate this process.
I need help to make the computer automatically enter the EFI Boot Loader without having to manually select this option every time. Could you advise how to solve this?
Thank you for your time and assistance.
tsialex
Contributor
If the Apple native BootPicker is working, press Control and select whatever you want as the default boot.
Tratkazir_the_1st
macrumors 65816
Got a question.
ANybody beside me got troubles with BT headsets? I need some kind of headset (BT or USB) for work, SKype messaging. Got Behringer headset (BB560M when connected). Can't make microphone to work... It is shown in System preferences in Audion Input device, but don't catches sound. My main display is LED CInema 27", which has audio & webcam built-in. When it's micrphone is selected - it works. Acceess to microphone is granted for Skype. Where to look for else?
ANybody beside me got troubles with BT headsets? I need some kind of headset (BT or USB) for work, SKype messaging. Got Behringer headset (BB560M when connected). Can't make microphone to work... It is shown in System preferences in Audion Input device, but don't catches sound. My main display is LED CInema 27", which has audio & webcam built-in. When it's micrphone is selected - it works. Acceess to microphone is granted for Skype. Where to look for else?
It seems there has been a misunderstanding. Although I can access the native Apple BootPicker, the issue is that even after selecting the desired boot option while holding the Control key to set it as default, my computer still boots to an unknown location. I continue to see the loading bar without the Apple logo, regardless of my actions in the BootPicker.
Are there any other steps I can try to resolve this issue? Sorry for the confusion, but I really need to make my computer boot correctly and automatically.
Thank you for your patience and assistance.
tsialex
Contributor
Did you tried to deep reset the NVRAM? If you cant set the default boot disk, you have an issue with the BootROM.
Do you even have the Apple BootPicker? The grey one?
It seems there has been a misunderstanding. Although I can access the native Apple BootPicker, the issue is that even after selecting the desired boot option while holding the Control key to set it as default, my computer still boots to an unknown location. I continue to see the loading bar without the Apple logo, regardless of my actions in the BootPicker.
Are there any other steps I can try to resolve this issue? Sorry for the confusion, but I really need to make my computer boot correctly and automatically.
Thank you for your patience and assistance.
tsialex
Contributor
This is becoming circular…
If you can't bless via BootPicker + Control, you probably have an issue with the MacPro BootROM.
The only other way to bless is doing it manually, mount your ESP, then:
Code:
bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/EFI/BOOT/BOOTx64.efiFor more info, read the first post of the thread below:
Manually Configured OpenCore on the Mac Pro
In this guide, you'll learn how to use OpenCore to install, run and update macOS Catalina, Big Sur and Monterey on the 2009–2012 Mac Pro, ending up with a clean unaltered operating system just like on a supported Mac. The approach described in this guide is for setting up and configuring...
forums.macrumors.com
Yes, I successfully performed a deep NVRAM reset and heard the startup sounds, indicating that the reset was indeed performed. However, the core issue remains unchanged. After the reset, I still need to manually press the 'alt' key to access the Apple BootPicker, the grey one, and manually select the EFI Boot OpenCore, and then the Monterey system boots up. So, the system works, but I must manually select the boot option every time, which is not ideal.
It seems there might be an issue with the BootROM, as you've suggested, since I can't set the boot disk to automatically load through the EFI Boot OpenCore without manual intervention.
Do you have any further suggestions on how I might resolve this issue to automate the boot process? Or is there a specific method to diagnose or address the BootROM issue directly?
Thank you for your continued assistance.
Last edited:
tsialex
Contributor
Did you tried blessing it manually?
Try blessing it manually, if you still can't, you'll gonna need the BootROM reconstruction service. Let me know if you successfully blessed it or not.
K two
macrumors 68020
Updated to 12.7.4 with OCLP 0.6.8 on iMac 14.3 (a.k.a. late 2013) w/ Kepler graphics. Reinstalled root patches and everything is as good as it was 12.7.3.
f329
macrumors newbie
For Open Core Legacy Patcher users.
After upgrading Monterey to 12.7.4 (21H1123) on a MacPro 5.1 with an old Broadcom BCM43xx WiFi chip and re-patching with Legacy WiFi Patcher, the network (including LAN) completely drops out.
Tested with new OCLP 1.4.1 and old 0.4.11 - patching after upgrade to 12.7.4 completely crashes network interfaces.
After upgrading Monterey to 12.7.4 (21H1123) on a MacPro 5.1 with an old Broadcom BCM43xx WiFi chip and re-patching with Legacy WiFi Patcher, the network (including LAN) completely drops out.
Tested with new OCLP 1.4.1 and old 0.4.11 - patching after upgrade to 12.7.4 completely crashes network interfaces.
Frixo Cool
macrumors regular
Exactly my case! I lost 16 hours yesterday trying to fix it. Interesting points:
- macOS Monterey 12.7.4 reinstall from USB doesn't help
- reinstall OCLP 1.4.1 and patches doesn't help
- reverting to OCLP 1.3.0 doesn't help
- deleting and adding networks services doesn't help
- it works OK in Monterey Recovery mode, so I am sure that hardware and router is fine
- also it works in Windows and Big Sur on another drive
Let us know if you solve it, I'll try myself later today.
Update: it's seems it's a common problem and anyone with 5,1 and Monterey 12.7.4 with OCLP has this problem. Users of manually configured OC are fine and 12.7.4 works great on their machines. So it seems that it's a bug in this specific configuration with OCLP. Apparently, the 1.4.2 patch is already in preparation to fix this problem.
Last edited: