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

[6DecadesLater]

As a follow up to my previous post #11,435, 12.5 has been very stable since updating AVXpel MaxKernel. Even have bluetooth functionality back using iWatch to open.

Could someone comment on MaxKernel settings? Sometimes it is blank, others it is 21.99.99 and others are incrementally increased with each update (which I failed to do).
Could they all be set to 21.99.99? Are the blank ones needed to be blank - if so, could the MaxKernel entry be removed altogether?

Thanks

 

[Dewdman42]

Use the recommended settings. Try to find a process that works for you to make sure you don't miss every little detail that has changed in each update. The good news is that we only have a few more updates left on Monterey and most likely we will never be able to use Ventura on our 5,1, but never know.

The MaxKernel value is kind of a safeguard setting. In this case, Avxpel is basically a hack that tweaks some of the binary code in one of the existing kext binary files provided from Apple. Each time Apple releases an update, its always possible that they may have updated that kext binary, which might require this particular kext hack to be updated. The MaxKernel setting will prevent that hack from being performed until the MaxKernel setting is updated also. In this way, with each new MacOs Update, you should verify that the hack is still valid before updating that and continuing to use it. In my view you should not really update MacOS at all from here until someone else has verified that this hacks are still working and proper, before updating either the MaxKernel setting, or even before updating MacOS...unless you are adventurous and want to be the person to test it for the rest of us.

Other kext entries in config.plist that don't have MaxKernel value means that they are more safe and not as necessary to verify each new MacOS update.. That's why they are blank, to avoid that hassle. But when they aren't blank, then you probably should go through the verification hassle and bump it up when everyone says its safe to do so.

I'm not sure why some of them are set to 21.99.99 vs blank. @cdf ??

 

[cdf]

Could someone comment on MaxKernel settings? Sometimes it is blank, others it is 21.99.99 and others are incrementally increased with each update (which I failed to do).

Patches like AVXpel can become outdated from one kernel version to the next, and since they can break things when this happens, it's best to increment MaxKernel version by version.

When MaxKernel is left blank, there is no upper limit on the kernel version. This is appropriate for kexts like Lilu and its plugins, which already have version checks in place.

Could they all be set to 21.99.99?

I wouldn't recommend this. I suppose something like 21.99.99 is appropriate for settings that are expected to apply for all kernels with major version 21 (though I'm not sure how anybody would know this). If I expect a setting to apply in the long run, I'd just opt for leaving MaxKernel blank.

Are the blank ones needed to be blank - if so, could the MaxKernel entry be removed altogether?

To adhere to the specification, MaxKernel should be present, whether empty or not.

 

[tsialex]

Had a failed 12.5.1 OTA update today with my main Mac Pro, crash dumped while half way updating.

Lost a lot of time trying to get it working again without messing any of my data unsuccessfully. Booted my High Sierra blade, downloaded 21G83 full installer, made a createinstallmedia USB installer, nuked one of my blades and successfully did a clean install that seems to be working.

Btw, this is the link for the Monterey 12.5.1/21G83 full installer:

https://swcdn.apple.com/content/downloads/18/44/012-51693-A_2W745BUZP7/xtd63whw506llesta7af6cjvcxlyj8mxvf/InstallAssistant.pkg

 

[Dewdman42]

Thanks for the heads up. hmm, so what do you recommend at this point for those of us that can't or don't want to do a clean install? Were you using avxpel, etc.? Did you attempt that OTA update using VMM?

 

[tsialex]

Thanks for the heads up. hmm, so what do you recommend at this point for those of us that can't or don't want to do a clean install? Were you using avxpel, etc.? Did you attempt that OTA update using VMM?

Honestly, I should have waited the weekend to do the update, lost half a day to get Monterey installed again.

I'm using AVXpel and did the update without enabling VMM - maybe should have enabled it. Since no one else had the crash here (yet?!?), but saw tweets about having trouble with the software update with supported Macs, I can't say if it was just an unfortunate fluke or it's a real issue - to be confirmed.

Btw, the today's weirdness started from the fact that Apple didn't sent 12.5.1/21G83 for the people on the developer's SUCatalog, only after changing back to the regular one the update finally appeared.

 

[TECK]

Had a failed 12.5.1 OTA update

I had no issues updating OTA without AVXpel, did it 30min ago.

 

[hwojtek]

Thanks for the heads up. hmm, so what do you recommend at this point for those of us that can't or don't want to do a clean install?

I did OTA to 12.5.1 on two machines already, works just like it should.

 

[trifero]

Honestly, I should have waited the weekend to do the update, lost half a day to get Monterey installed again.

I'm using AVXpel and did the update without enabling VMM - maybe should have enabled it. Since no one else had the crash here (yet?!?), but saw tweets about having trouble with the software update with supported Macs, I can't say if it was just an unfortunate fluke or it's a real issue - to be confirmed.

Btw, the today's weirdness started from the fact that Apple didn't sent 12.5.1/21G83 for the people on the developer's SUCatalog, only after changing back to the regular one the update finally appeared.

Why didn´t you install a clean 12.5.1 and then migrate? It is what I do when the straight update fails.

 

[trifero]

I did OTA to 12.5.1 on two machines already, works just like it should.

Same here.

 

[Dewdman42]

Seems to have worked for me also.

 

[sfalatko]

Honestly, I should have waited the weekend to do the update, lost half a day to get Monterey installed again.

I'm using AVXpel and did the update without enabling VMM - maybe should have enabled it. Since no one else had the crash here (yet?!?), but saw tweets about having trouble with the software update with supported Macs, I can't say if it was just an unfortunate fluke or it's a real issue - to be confirmed.

Btw, the today's weirdness started from the fact that Apple didn't sent 12.5.1/21G83 for the people on the developer's SUCatalog, only after changing back to the regular one the update finally appeared.

@tsialex - remind me again - what is your recommendation regarding updates and NVRAM? Reflash with reconstructed ROM prior to OTA update or simply do a forced GC?

 

[PeterHolbrook]

I did OTA to 12.5.1 on two machines already, works just like it should.

Should MaxKernel change for AVXpel entries? Something like 21.6.1?

EDIT: According to the Wikipedia, Darwin in Monterey 12.5.1 is still version 21.6.0, so I guess no changes are necessary in config.plist.

EDIT2: The update to 12.5.1 was successful. No issues.

 

[Gustav Holdoff]

i updated to version 12.5.1 on one of my cMP 4.1/5.1 using config V2 made by Marin Lo written for 0.8.0
update was easy
after the final reboot, I checked the work on the same version, only returned the config settings to working condition
1. disk indexing is not quite correct
there are many mds processes and especially mdsworker, which is part of the spotlight - it clones 12 times - according to the number of processors and does not stop, continuing to occupy the processor by 3-4% (although the activity monitor writes "50%" - it just needs to be divided by 12)
2. I replaced opencore with version 0.8.3, which I was working on before the update - now the system works as it should
3. I quickly checked the work in my main programs, everything is OK

My CMP 4.1/5.1 dual cpu xeon 5680, 96gb RAM, radeonpro w5700, nvme crucial 2tb, evo plus 1tb, TB3 alpine ridge, oc 0.8.0, mac os 12.5.1

 

[hwojtek]

Should MaxKernel change for AVXpel entries? Something like 21.6.1?

No need to touch anything, you got it right, kernel is still the same.

 

[w1z]

Another data point - been running 12.5 without any APFs/AVX patches and just updated to 12.5.1 .. All went smoothly.

 

[ZNDK]

I have updated to OpenCore 0.8.3. I read something about setting OpenVariableRuntimeDxe loadEarly to True for Macs like Mac Pro 5.1, so I tried that. I also set OpenRuntime loadEarly to True. When my Mac goes to sleep, it will not wake up from sleep. When I try to get the Mac to wake up from sleep, I hear the initial mechanical wake up sound, but there is nothing on the display, no signal coming through, no HDD or other operating sounds, and the Mac does not wake up from sleep.

Should I set "OpenVariableRuntimeDxe"? If so, is there any way to normalize the sleep function?

I have solved the warning dialog after starting up my Mac by updating to macOS 12.5.1.

But a new problem. I go to sleep and when I wake up from sleep, Mac's fan starts spinning almost full blast. At this time I can't seem to reliably reduce this RPM by rebooting my Mac. It seems that turning off the Mac, waiting a little while, and then cold booting it will return it to normal RPM. Is this a symptom unique to me?

 

[PeterHolbrook]

Is this a symptom unique to me?

Never heard of it on a Mac Pro. My elder son has an old iMac. He's been having an issue (since before OC times) with the internal fan ever since he replaced the HDD with an SSD. He's been able to solve it using Macs Fan Control.

 

[Stex]

Updated my cMP (signature) OTA from macOS 12.4 to 12.5.1 -- update went smoothly, system working well. Running OC 0.7.9 with AVXpel. Still pending: OC update plus BootROM re-flash when time allows.

 

[kkinto]

Never heard of it on a Mac Pro. My elder son has an old iMac. He's been having an issue (since before OC times) with the internal fan ever since he replaced the HDD with an SSD. He's been able to solve it using Macs Fan Control.

Maybe not related - but I had internal drive of a Mac Mini replaced with an SSD and when it came back the fans were on high always. Macs Fan sorted it, but turned out the technician broke a crucial sensor during the drive replacement operation.

 

[dataharvested]

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.

View attachment 1899553

Hello. I want to perform this manual installation of Windows 10 on my 5,1 that has OCLP installed. I am getting stuck on the "Enable the Driver" step as I'm not sure what I am supposed to be doing there. Also how to accomplish the "ProtectSecureBoot is set to true" and the "The VMM flag is disabled" bits. That's where I stopped as I did not want to botch anything. Any guidance is greatly appreciated.

 

[cdf]

Hello. I want to perform this manual installation of Windows 10 on my 5,1 that has OCLP installed. I am getting stuck on the "Enable the Driver" step as I'm not sure what I am supposed to be doing there. Also how to accomplish the "ProtectSecureBoot is set to true" and the "The VMM flag is disabled" bits. That's where I stopped as I did not want to botch anything. Any guidance is greatly appreciated.

If you're using OCLP, those steps should already be complete (the ExFat driver should be preinstalled and the Windows installer should be ready to boot). Just carefully follow all the other steps. Of course, you'll need to know how to do some basic stuff, like mount your ESP (where OpenCore is installed) to copy the Windows EFI files.

If you're interested in learning how to manually configure and maintain OpenCore (or curious about not being able to disable SIP ), I encourage you to go through the guide in the first post (see Basic setup and Complete your setup for the essentials).

 

[dataharvested]

If you're using OCLP, those steps should already be complete (the ExFat driver should be preinstalled and the Windows installer should be ready to boot). Just carefully follow all the other steps. Of course, you'll need to know how to do some basic stuff, like mount your ESP (where OpenCore is installed) to copy the Windows EFI files.

If you're interested in learning how to manually configure and maintain OpenCore (or curious about not being able to disable SIP ), I encourage you to go through the guide in the first post (see Basic setup and Complete your setup for the essentials).

Thank you! I will read up on the guide.

 

[dataharvested]

Okay, I'm typing from Windows 10 on my 5,1 now! Wondering if/where I would acquire drivers for the Bluetooth and any other important system devices. Do I need to get the Bootcamp drivers?

 

[dataharvested]

I tried the Brigadier step-by-step and the install said it was for Windows 7. Probably for the best because I read up on other people issues. I went into the drivers folder and got the Bluetooth driver installed. I don't have any Bluetooth devices so I'm not sure if it's working. I downloaded the graphics card driver and software from AMD's support page for my RX 580 card. Is there anything else I need to do to be sure things like the CPU fan speed and what not are going to work correctly in Windows 10 on my 5,1?