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

[Darmok N Jalad]

That is the prohibited boot screen - means your OS is unsupported. You would see that for example if you spoofed a MacPro7,1 and tried to boot Mojave since Mojave is not supported by the MacPro7,1.

What OS are you trying to boot? What computer are you spoofing?

Aha! So I’m currently on Mojave, but was running those patches to be able to jump to Big Sur or Monterey. How do I make the leap? I was going to run the installer from the Applications folder, but I guess that’s a no-go. I would be spoofing the 7,1 to get there.

 

[sfalatko]

Aha! So I’m currently on Mojave, but was running those patches to be able to jump to Big Sur or Monterey. How do I make the leap? I was going to run the installer from the Applications folder, but I guess that’s a no-go. I would be spoofing the 7,1 to get there.

You need to put a "-no_compat_check" in your config.plist boot args or you could spoof the iMacPro (see the first post)

<key>NVRAM</key>
<dict>
<key>Add</key>
<dict>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>boot-args</key>
<string>-no_compat_check</string>
</dict>
⋮
</dict>
<key>Delete</key>
<dict>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<array>
<string>boot-args</string>
</array>
</dict>

 

[Dewdman42]

at this point, what are people's opinions about AVXpel vs NoZVXCompression approach to dealing with AVX in latest Monterey?

I started with AVXpel per this guide, but then when I was having Kernel Panics a few weeks ago I switched to NoAVXCompression, which did not solve that problem by the way. I later solved that problem by simply reinstalling MacOS...but anyway, I'm still using NoAVXCompression and it seems to be working fine, just wondering what thoughts people have about one method vs the other. The AVXpel method requires quite a bit more editing to the config.plist, which if for no other reason probably leads me to just continue with NoAVXCompression, but I also prefer to follow CDF's recommendations most of the time, so I'd like to hear the pros and cons or thinking along the lines of which method is most preferable and why.

 

[eVasilis]

That's a bit confusing. The OC manual state this

Trim operations are only affected at booting phase when the startup volume is mounted. Either specifying timeout, or completely disabling trim with 0, will not affect normal macOS running.

So, my understanding is that will only disable the "manual TRIM" during boot, but not completely disable TRIM inside normal macOS operation.

I don't know how often the OS will TRIM the SSD, and I personally haven't monitor it. But one of the OpenCore user told me that he did observed TRIM operation 2-3 days after boot (with SetApfsTrimTimeout=0). Assuming he know what he was doing. And he did that correctly. Then SetApfsTrimTimeout=0 shouldn't cause too many extra wear to the SSD.

In terminal run

log show --predicate "processID == 0" \--start $(date "+%Y-%m-01") | grep spaceman

This will print all related operations regarding trim and relevant disks.

I duplicated a folder on my desktop, filled with various files, and then deleted it. Then, I set the apfs trim value in config to 0, replaced the one in the OC EFI and rebooted. Running the above command produced these:


2022-11-08 22:18:58.716891+0200 0x44d Default 0x0 0 0 kernel: (apfs) spaceman_metazone_init:191: disk1 metazone for device 0 of size 2693771 blocks (encrypted: 0-1346885 unencrypted: 1346885-2693771)


2022-11-08 22:18:58.716900+0200 0x44d Default 0x0 0 0 kernel: (apfs) spaceman_datazone_init:625: disk1 allocation zone on dev 0 for allocations of 1 blocks starting at paddr 49315840


2022-11-08 22:18:58.716906+0200 0x44d Default 0x0 0 0 kernel: (apfs) spaceman_datazone_init:625: disk1 allocation zone on dev 0 for allocations of 2 blocks starting at paddr 12058624


2022-11-08 22:18:58.716913+0200 0x44d Default 0x0 0 0 kernel: (apfs) spaceman_datazone_init:625: disk1 allocation zone on dev 0 for allocations of 3 blocks starting at paddr 16023552


2022-11-08 22:18:58.716920+0200 0x44d Default 0x0 0 0 kernel: (apfs) spaceman_datazone_init:625: disk1 allocation zone on dev 0 for allocations of 4 blocks starting at paddr 42762240


2022-11-08 22:18:58.716982+0200 0x3d0 Default 0x0 0 0 kernel: (apfs) spaceman_scan_free_blocks:3172: disk1 scan took 0.000000 s (no trims)


2022-11-08 22:18:58.716990+0200 0x3d0 Default 0x0 0 0 kernel: (apfs) spaceman_scan_free_blocks:3154: disk1 scan took 0.000000 s, trims took 0.000000 s


2022-11-08 22:18:58.716995+0200 0x3d0 Default 0x0 0 0 kernel: (apfs) spaceman_scan_free_blocks:3156: disk1 0 blocks free in 0 extents,

where disk1 is the disk where the duplicate folder was deleted. So, I guess, regardless of the value used in SetApfsTrimTimeout in config, if you enable trim within macos with "sudo trimforce ebable", trim remains up and running.

 

[tesax]

My System is a cMP5.1 which I tried to update from running OC 7.7 (Monterey 12.1) to the now up to date OC 8.6.
The Graphiccard is non-bootscreen Sapphire RX560 in Slot 1 with high DPI-Display connected via DP cable.
The newest .kext files and .efi files were added/updated now the cMP is caught in reboot-loops, my config.plist is attached.
I would be glad if there will be help.

Edit: <key>0<\key> was't the only copy and paste error, found some more...

Thank you very much cdf!

 

[Darmok N Jalad]

You need to put a "-no_compat_check" in your config.plist boot args or you could spoof the iMacPro (see the first post)

<key>NVRAM</key>
<dict>
<key>Add</key>
<dict>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>boot-args</key>
<string>-no_compat_check</string>
</dict>
⋮
</dict>
<key>Delete</key>
<dict>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<array>
<string>boot-args</string>
</array>
</dict>

That did it! I had deleted these lines because I last made that config under Catalina. Thank you!

This time I've backed up my EFI contents so I can bounce back more quickly in the event of a big screw up.

Also, is Monterey or Big Sur the more stable bet for daily use on a 5,1? I don't need the latest and greatest, but there are a few features in Photos that I like that started with Big Sur.

 

[cdf]

My System is a cMP5.1 which I tried to update from running OC 7.7 (Monterey 12.1) to the now up to date OC 8.6.
The Graphiccard is non-bootscreen Sapphire RX560 in Slot 1 with high DPI-Display connected via DP cable.
The newest .kext files and .efi files were added/updated now the cMP is caught in reboot-loops, my config.plist is attached.
I would be glad if there will be help.

See Device Properties > Add. You’ve nested the dictionary entry one level too deep with that unnecessary <key>0<\key>.

 

[cdf]

at this point, what are people's opinions about AVXpel vs NoZVXCompression approach to dealing with AVX in latest Monterey?

Since my workflow doesn’t trigger any AVX related issues, I actually don’t use either fix, though I’m happy to know they exist if ever I need them!

 

[Dewdman42]

hehe Well I am going to try AVXpel for a while again. I actually don't use any of those features either, so it probably doesn't matter for me either, except I seem to recall there was something that might happen during booting?

 

[Darmok N Jalad]

Took me long enough!

 

[sfalatko]

That did it! I had deleted these lines because I last made that config under Catalina. Thank you!

This time I've backed up my EFI contents so I can bounce back more quickly in the event of a big screw up.

Also, is Monterey or Big Sur the more stable bet for daily use on a 5,1? I don't need the latest and greatest, but there are a few features in Photos that I like that started with Big Sur.

I have been happy with Monterey. Others including @tsialex recommend Big Sur as more stable. I think either is fine.

Regards,
sfalatko

 

[flaubert]

I have been happy with Monterey. Others including @tsialex recommend Big Sur as more stable. I think either is fine.

Regards,
sfalatko

I think we're all gonna be on Monterey eventually... if we want to run out the support until the bitter end, two years from now.

 

[prefuse07]

That did it! I had deleted these lines because I last made that config under Catalina. Thank you!

This time I've backed up my EFI contents so I can bounce back more quickly in the event of a big screw up.

Also, is Monterey or Big Sur the more stable bet for daily use on a 5,1? I don't need the latest and greatest, but there are a few features in Photos that I like that started with Big Sur.

If you are feeling courageous -- 12.6.1 has been VERY stable, actually performing even better than Big Sur did for me, and apple somehow increased benchmarks (compared with Big Sur).

Again, if you're feeling courageous, I say go for it -- go for both OC 0.8.5 (or 0.8.6 since I see it's out now) and 12.6.1

 

[h9826790]

If you are feeling courageous -- 12.6.1 has been VERY stable, actually performing even better than Big Sur did for me, and apple somehow increased benchmarks (compared with Big Sur).

Again, if you're feeling courageous, I say go for it -- go for both OC 0.8.5 (or 0.8.6 since I see it's out now) and 12.6.1

Yeah, I just got my cMP back, and run 12.6.1 with OC 0.8.5 (0.8.6 now) for a week now. Extremely stable and smooth. Really highly recommended for cMP user with proper hardware upgraded.

 

[Darmok N Jalad]

I noticed my 5,1 isn't going to sleep on its own in Big Sur. If I manually put it in sleep, it sleeps/wakes just fine, but it will just idle if I walk off without manually entering sleep mode. I noticed there's no sleep mode slider, just display timer, and an option to prevent sleeping with display, which is off. Am I missing a setting somewhere?

 

[Macschrauber]

I noticed my 5,1 isn't going to sleep on its own in Big Sur. If I manually put it in sleep, it sleeps/wakes just fine, but it will just idle if I walk off without manually entering sleep mode. I noticed there's no sleep mode slider, just display timer, and an option to prevent sleeping with display, which is off. Am I missing a setting somewhere?

You can enter

pmset -g

In Terminal to check if some app or service keeps the Mac awake.

 

[DigitaLife]

Yeah, I just got my cMP back, and run 12.6.1 with OC 0.8.5 (0.8.6 now) for a week now. Extremely stable and smooth. Really highly recommended for cMP user with proper hardware upgraded.

Hi, could you kindly attach, as you usually do, the new OC 0.8.6 file, including your correct config.plist, in your post #1,314?
Thank you very much in advance.

 

[h9826790]

Hi, could you kindly attach, as you usually do, the new OC 0.8.6 file, including your correct config.plist, in your post #1,314?
Thank you very much in advance.

If you don't mind to be the beta tester, you can download my latest 0.8.6 package and report any issue to me. Thanks!

Dropbox - File Deleted - Simplify your life

www.dropbox.com

I tested it on my cMP. It works as expected in Mojave and Monterey. But another user reported the SMBIOS spoofing seems not working on his cMP. And no other user report to me yet. That's why I haven't upload this package to my post #1314 yet.

Anyway, it's tested can boot from HS onwarded. No crash. Should be safe to try.

 

[DigitaLife]

If you don't mind to be the beta tester, you can download my latest 0.8.6 package and report any issue to me. Thanks!

Dropbox - File Deleted - Simplify your life

www.dropbox.com

I tested it on my cMP. It works as expected in Mojave and Monterey. But another user reported the SMBIOS spoofing seems not working on his cMP. And no other user report to me yet. That's why I haven't upload this package to my post #1314 yet.

Anyway, it's tested can boot from HS onwarded. No crash. Should be safe to try.

Thank you very much!
It works very well with Monterey and much better than version 0.8.0!

 

[macoda]

If you don't mind to be the beta tester, you can download my latest 0.8.6 package and report any issue to me. Thanks!

Dropbox - File Deleted - Simplify your life

www.dropbox.com

I tested it on my cMP. It works as expected in Mojave and Monterey. But another user reported the SMBIOS spoofing seems not working on his cMP. And no other user report to me yet. That's why I haven't upload this package to my post #1314 yet.

Anyway, it's tested can boot from HS onwarded. No crash. Should be safe to try.

Just updated following the vid in the readme for 0 8.6 and I'm now in a boot loop. cMP 5,1, Big Sur. I got a recovery option at boot. Recovery 11.7.1 (dmg). Anyone fancy giving me a dig out?

 

[h9826790]

Just updated following the vid in the readme for 0 8.6 and I'm now in a boot loop. cMP 5,1, Big Sur. I got a recovery option at boot. Recovery 11.7.1 (dmg). Anyone fancy giving me a dig out?

So, all you did is just install that OC beta package (completely replace both BOOT and EFI folder). Then got into a boot loop when you try to boot Big Sur (but you can boot to recovery)?

 

[Darmok N Jalad]

You can enter

pmset -g

In Terminal to check if some app or service keeps the Mac awake.

Idle sleep preventers: IODisplayWrangler

My initial searching suggests this happens to regularly supported Mac users, but any chance this is related to running an unsupported OS? I do have the 12.3 power management patch in my config, which I guess wouldn't be needed if I'm on Big Sur. Is that what's doing it?

EDIT:
Actually, I'm wondering if it's because I'm booting from an NVMe drive on a PCIe riser. Thoughts?

EDIT2:
I also saw this by running that command:
sleep prevented by UserEventAgent

 

[macoda]

So, all you did is just install that OC beta package (completely replace both BOOT and EFI folder). Then got into a boot loop when you try to boot Big Sur (but you can boot to recovery)?

Yes. I think I might have found the issue. I'm not entirely sure what to do to fix this safely so maybe @tsialex could jump in?

 

[tsialex]

Yes. I think I might have found the issue. I'm not entirely sure what to do to fix this safely so maybe @tsialex could jump in?

View attachment 2111717

Did you tried a multiple/continuous NVRAM VSS store reset? Dump the BootROM image after you do it and check again.

Connect a wired keyboard that works for NVRAM resets and press/keep pressed CMD-Option-P-R until you hear the fifth chime (you just need three sequential resets to trigger the deep reset, but it's not easy to do it for the first time).

If you have a cross-flashed early-2009, won't solve the real underlying problems with the NVRAM volume, the MP4,1 NVRAM volume is slightly different from the MP5,1 one and you'll need a BootROM reconstruction service.

 

[macoda]

Did you tried a multiple/continuous NVRAM VSS store reset? Dump the BootROM image after you do it and check again.

Connect a wired keyboard that works for NVRAM resets and press/keep pressed CMD-Option-P-R until you hear the fifth chime (you just need three sequential resets to trigger the deep reset, but it's not easy to do it for the first time).

If you have a cross-flashed early-2009, won't solve the real underlying problems with the NVRAM volume, the MP4,1 NVRAM volume is slightly different from the MP5,1 one and you'll need a BootROM reconstruction service.

Yep, did that almost immediately after my last post as I've zero patience 😆

Looks a lot healthier now...

Time to see if I can get anywhere with 0.8.6