MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[tsialex]

Can you comment on this a little bit?

On what exactly?

Do you know how that is working in Ventura?

Yes, tested myself.

Still requires OCLP patching?

Without patching you can't have Ethernet/Audio/GPU/USB working.

For me the main problem will be waiting to see how prevalant the use of AVX is. I think USB/BT and probably even DRM will be solved eventually; but I'm not as confident about AVX

AVX will need an emulator, Apple is hell bent on using AVX with GPU drivers, AFS, crypto and more. OCLP is doing a good job of circumventing it, but will be a wild ride.

 

[Frixo Cool]

Just a quick update with my OCLP update to 12.6.1. Wifi and BT now works but there is still an issue with USB ports. It's hard to say what changed, but after several reinstalls of OpenCore and Root Patches I got Wifi an BT operational. I found one OCLP install on some secondary SATA disk, so maybe that was the source of confusion. So, check your partitions with Clover Configurator for any "rogue OC installs"

However, the USB problem is puzzling! Front USB ports work, but not if you connect keyboard, mouse or trackpad! But you can use them with any USB storage device - even external HDD. If I boot to my backup Mojave disk without OC - you guess, everything works! So, what happened to front USB ports in 12.6.1 update? Anyone with the same issue?

 

[tsialex]

Just a quick update with my OCLP update to 12.6.1. Wifi and BT now works but there is still an issue with USB ports. It's hard to say what changed, but after several reinstalls of OpenCore and Root Patches I got Wifi an BT operational. I found one OCLP install on some secondary SATA disk, so maybe that was the source of confusion. So, check your partitions with Clover Configurator for any "rogue OC installs"

However, the USB problem is puzzling! Front USB ports work, but not if you connect keyboard, mouse or trackpad! But you can use them with any USB storage device - even external HDD. If I boot to my backup Mojave disk without OC - you guess, everything works! So, what happened to front USB ports in 12.6.1 update? Anyone with the same issue?

Apple removed USB1.0/USB1.1, HID devices are usually USB1.1, with the first Monterey release - this is not new. Use a USB2.0 or 3.0 HUB between your USB1.0/1.1 devices and your Mac Pro to force EHCI and overcome the removal of OHCI support from Monterey.

 

[Chicane27]

Hi, Folks, I want to make sure I'm locating the most recent and reliable Open Core process for updating my Mac OS running (open core) Monterey on my Mac Pro 5,1.

I have done really well with previous Open Core upgrades and the machine is working perfectly at the moment - but I have resisted updating from its current Monterey build. Can someone point me to the best instructions for doing the update to the latest Monterey build? I will wait for more comments on Ventura before I "venture" any further. Thanks!

 

[hwojtek]

Can someone point me to the best instructions for doing the update to the latest Monterey build?

On a proper OC setup I usually click "About this Mac", ""Software update" and then "Install". Once I am done with this procedure I allow myself some time off: watch an episode of "The Office" on Netflix, do the dishes, talk with my g/f, read a book, you know, the usual stuff. Then after some 40 minutes I come back to see what happened on the 5,1 and, boom, there's the updated system.

 

[Frixo Cool]

Apple removed USB1.0/USB1.1, HID devices are usually USB1.1, with the first Monterey release - this is not new. Use a USB2.0 or 3.0 HUB between your USB1.0/1.1 devices and your Mac Pro to force EHCI and overcome the removal of OHCI support from Monterey.

Hm... I made a SMC reset and guess what - front USB ports now fully work ...mouse, keyboard, trackpad, everyhting! So, I guess there is some patch in OCLP that handles EHCI/OHCI issue?

 

[cdf]

Hm... I made a SMC reset and guess what - front USB ports now fully work ...mouse, keyboard, trackpad, everyhting! So, I guess there is some patch in OCLP that handles EHCI/OHCI issue?

No. Your devices will work if they were plugged in before booting, but if you plug them in after booting (or unplug them and plug them back) they won’t work. This is a very well known issue.

 

[Bmju]

With some crucial input from mhaeuser, the hang when returning from sleep in the OpenCore emulated NVRAM driver is now fixed.

When combined with the NVRAM save script (Utilities/LogoutHook/Launchd.command), I really do think that this can be used as a daily driver now - a way to more or less completely avoid wear on your NVRAM in day-to-day use. At least I've used it (obviously without working sleep, up to now) for a considerable amount of time with no (other!) problems at all.

 

[Dewdman42]

On what exactly?

Yes, tested myself.

Without patching you can't have Ethernet/Audio/GPU/USB working.

AVX will need an emulator, Apple is hell bent on using AVX with GPU drivers, AFS, crypto and more. OCLP is doing a good job of circumventing it, but will be a wild ride.

I was asking about the RX580. You made some statements at Nvidia patching support, but I'm just wondering how the RX580 is faring with those attempting ventura

I agree about AVX

 

[tsialex]

I was asking about the RX580. You made some statements at Nvidia patching support, but I'm just wondering how the RX580 is faring with those attempting ventura

I agree about AVX

Polaris/VEGA/NAVI GPUs drivers now require AVX2.0. OCLP is downgrading the drivers for the most updated version from Monterey. This is alpha right now with several issues.

Btw, if Apple ever release drivers for NAVI 3x, we will never run it with a MacPro5,1…

 

[Dewdman42]

Is the RX580 Polaris, Vega or Navi?

 

[Dewdman42]

anyway I was just asking out of curiosity and to have a long term scope...honestly.. I am pretty sure I will not be upgrading past Monterey. But never know....

 

[cdf]

Is the RX580 Polaris, Vega or Navi?

Polaris. Note that a major roadblock is getting through the initial installation without swapping out the Polaris card. Since macOS 12.3 (bootable with the help of ASPP-Override), it is not possible to boot in safe mode.

 

[Dewdman42]

what is the safe mode requirement? what if I am using rEFInd boot manager instead of GPU boot screen?

 

[paul_bace]

Hey Folks, I'm losing what's left of my hair here.

I've installed Windows several times, and everytime after a successful install, it starts giving me issues. I can't seem to figure out how to mount the BootCamp/Windows EFI. It won't let me in Big Sur, and when I can get into Windows (sometimes after a few cold starts it fixes itself) I'm so Windows illiterate I don't know what to do to make it smooth. I've read the OP. I've done everything several times. Windows...works...but right now it's not flawless and seamless. I just wanna host my game library on a dedicated Windows drive! DAMNIT! (important stuff).

 

[cdf]

what is the safe mode requirement? what if I am using rEFInd boot manager instead of GPU boot screen?

rEFInd won’t help. Safe mode is required to prevent macOS from loading the AVX-dependant Polaris drivers (before they can be downgraded). Unfortunately, safe mode also prevents ASPP-Override from loading, which is required for booting in the first place. To make matters worst, other approaches for disabling the graphics drivers (boot-args such as -radvesa in WEG or -amd_no_dgpu_accel) have not been proven to work for the initial installation.

 

[hwojtek]

I've installed Windows several times

Can you at least give us a hint of what Windows installation you did? Bootcamp? Bare metal? EFI or legacy? Did you use OC to boot and then selected Windows USB installer as a source? What does "starts giving me issues" mean? Sore back? Blurred vision? Daughter coming home too late and with a smile you haven't seen before? Or maybe perhaps lack of drivers?

1. To easily mount (any) EFI partition from MacOS you may find the MountEFI script really helpful.
2. You post actually begs to be moved here, as it is (mostly) off topic in this thread.

 

[Bmju]

With some crucial input from mhaeuser, the hang when returning from sleep in the OpenCore emulated NVRAM driver is now fixed.

When combined with the NVRAM save script (Utilities/LogoutHook/Launchd.command), I really do think that this can be used as a daily driver now - a way to more or less completely avoid wear on your NVRAM in day-to-day use. At least I've used it (obviously without working sleep, up to now) for a considerable amount of time with no (other!) problems at all.

Btw, if anybody wants to know, in EFI 1.1 the NVRAM value AcpiGlobalVariable is required for wake from S3: it contains a link to the S3 boot script, i.e. how to set the machine back up correctly when it wakes from S3 sleep. But once the brand new NVRAM store has been set up and has taken over until the next full reboot, there is no such variable and the machine can't wake. What was required was to clone the variable, if present, into the emulated NVRAM during its set up. And I wasn't seeing any problem in non-Macs, because on newer, UEFI 2, machines, the S3 boot script is stored and retrieved by SMM calls (i.e. presumably somewhere in the management engine's memory), so there was never an issue there.

 

[Dewdman42]

No. Your devices will work if they were plugged in before booting, but if you plug them in after booting (or unplug them and plug them back) they won’t work. This is a very well known issue.

This sounds like it may require the actual installer to be patched in reality once we understand what exactly needs to be patched. And conceivably, all future updates would need to be patched also.

 

[paul_bace]

Can you at least give us a hint of what Windows installation you did? Bootcamp? Bare metal? EFI or legacy? Did you use OC to boot and then selected Windows USB installer as a source? What does "starts giving me issues" mean? Sore back? Blurred vision? Daughter coming home too late and with a smile you haven't seen before? Or maybe perhaps lack of drivers?

1. To easily mount (any) EFI partition from MacOS you may find the MountEFI script really helpful.
2. You post actually begs to be moved here, as it is (mostly) off topic in this thread.

Yes. Yes. No. Legacy. Yes. Blue Screen, although that appears to be because i dared to connect drives again. Yes a sore back thanks for asking. Almost. I have a daughter? ****. I've run bootcamp several times, and run windows update.

1. Thank you. Doesn't seem to work or I don't know how to use it.
2. The original post is why I'm here. Being the OCLP directs to this thread. Sorry if it's not the right one tho.

Thanks for the time!

 

[hwojtek]

Yes. Yes. No. Legacy. Yes.

So you mixed up the things properly to create a SNAFU event. OK, we will sort it out.

1. Make sure you have a Windows machine* to run a couple of things. Run Rufus on this machine (portable version will do).
2. Download a Windows ISO - you can do it with Rufus, or just head to microsoft.com and download a x64 ISO.
3. Use Rufus to create an USB installer. Should you choose Windows 11 (works beautifully), make sure to create a custom, non-secure boot and non-TPM2 installer (Rufus will ask you that).

You're done with the Windows machine, get back home.

4. Attach a spare disk (Windows will go onto it so it will be erased) to the Mac Pro.
5. Power the Mac to MacOS through OpenCore. Make sure you run the latest OC (or OCLP for that matter). Search this thread for hints regarding how to set config.plist so Windows will not mess with your NVRAM nor boot disk settings (boot policy, if I recall correctly)
6. Attach the USB you made earlier. One or two partitions will appear on desktop.
7. Restart the Mac and watch carefully for an UEFI_BOOT icon to appear in your usual Open Core disk picker. This is the USB you created. Navigate there using arrow keys on the keyboard or your mouse. Boot from it.
8. Make sure you select the right disk once you pressed Install in Windows installer.
9. Make sure you stay there while Windows installs, as it reboots a gazillion times and you need to select the Windows disk manually in OC bootpicker for the installation to progress.
10. Once you're done with the install, treat the Windows installation as a regular PC, forget about Mac things. Skip Bootcamp drivers, install whatever you need from respective manufacturers (yes, you will need to search for the sound driver).

And the MountEFI script is called from within terminal. Extract the zip to your home directory, open the Terminal and cd MountEFI followed by sudo ./mountefi.command.


* - this may and in lots of cases actually is a temporary Windows virtual machine ran inside a VirtualBox or such.

 

[tsialex]

rEFInd won’t help. Safe mode is required to prevent macOS from loading the AVX-dependant Polaris drivers (before they can be downgraded). Unfortunately, safe mode also prevents ASPP-Override from loading, which is required for booting in the first place. To make matters worst, other approaches for disabling the graphics drivers (boot-args such as -radvesa in WEG or -amd_no_dgpu_accel) have not been proven to work for the initial installation.

Yes, that's why the workaround with Kepler GPUs worked so well, the NVIDIA GPUs are unsupported and without drivers.

 

[prefuse07]

Hmmm, I'm having some weird issues, and I wonder if I am the only one?

Based on what i've been reading, people have been updating to 12.6.1 without issue, but I have not been so lucky...

Today I updated my OC ver to 0.8.5, after confirming that it was fully stable and working fine, I decided to take the plunge and go for 12.6.1.

After Monterey was done downloading and doing the initial install, I clicked "reboot" -- the initial reboot didn't work, sadly, and every time I clicked "macOS Installer" (I tried 4-5 times) it just kernel panicked, so I decided "what the hell, 2nd time's the charm"

Re-ran the Monterey installer, then rebooted. Apple logo actually filled up! (very slowly, but it filled!) Then my cMP rebooted automatically, and I was met with the OC boot picker without seeing any macOS Installer -- which told me that Monterey successfully installed!

So I chose "macOS" and then..... Kernel Panic a few seconds into apple logo loading...

I decided to see if I could maybe reinstall it, so on the OC boot menu, pressed Space to bring up the recovery options, and there I saw it "Recovery 12.6.1 dmg" so I clicked, but unfortunately, now I am stuck with KP reboots.

I have a solid, fully working 0.8.5 config.plist, and I made sure to use AVXpel.

Typing this from Windows, since I'm unable to boot into macOS or the recovery.

I don't know if this is of any importance -- but I am due to reflash my bootROM. Was going to do it earlier today but decided to put it off to tomorrow, as I also want to take the time to clean the inside of the cMP, when I take out the 6800 and put in the 580 to use Mojave.

The method I used for updating to Monterey was #2 from the macOS section of the guide -- since I normally run OC with SecureBootModel = Default, I use hybridization, and my FirmwareFeatures are updated. Also, when I updated BigSur all the way up to 11.6.5 previously, it all worked fine.

I don't think there is any way to salvage what I currently have since I am instantly met with KP, but I think I will try doing a deep NVRAM reset tomorrow (highly doubt that will do anything).

Any thoughts or help is highly welcome

Thanks!

 

[Gustav Holdoff]

Hmmm, I'm having some weird issues, and I wonder if I am the only one?

Based on what i've been reading, people have been updating to 12.6.1 without issue, but I have not been so lucky...

Re-ran the Monterey installer, then rebooted. Apple logo actually filled up! (very slowly, but it filled!) Then my cMP rebooted automatically, and I was met with the OC boot picker without seeing any macOS Installer -- which told me that Monterey successfully installed!

It looks very strange.
main ssd normal, not shrinked?
but maybe because of the old bootrom?
maybe the battery is old and it needs to be replaced (until you bought a BR, you can put a simple one, but it will swell in less than a week and become unusable)
try to install method 1, or try martin lo (0.8.0 version 2 - with 2 changes for update- I used to update according to his method, until I updated the bootrom - thanks tsialex)
you must carefully go through the procedure for changing the config to update
then rule out anything that could be the cause
what is the difference in configuration or hardware compared to the last monterey update
put another gpu (you still need to change it to do a bootRom cleanup)
one more fact - maybe something from the peripheral equipment conflicts during installation
- I used to have a thunderbolt card that could fail, or connected USB devices
or return a working 0.8.4 (try different methods)

 

[Macschrauber]

Everyone with kernel panics should boot verbose and capture the screen output.

Without the verbose text it is like „there was an error and I clicked it away dont reading it“