Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

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

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.
David403

David403

macrumors regular
Nov 5, 2017
144
136
USA
cdf said:
Post #1 now includes some instructions for downgrading the AppleFSCompressionTypeZlib kext that causes kernel panics in macOS 12.4 (look for "NoAVXFSCompressionTypeZlib" in Complete your setup > Spoofing, enabling missing features and other fixes). This should stop the panics. Many thanks to @khronokernel for providing the fix
Click to expand...
I'm posting this reply (1) to thank you and @khronokernel for the fix. and (2) for others who make use of the dictation capability of Voice Control to Please Note:-

After making the changes set out in post one for this fix and if you enable the VMM flag to install or update to 12.4 and then you immediately switch on System Preferences>VoiceControl>Dictation because the VMM flag impacts performance so much you will find it takes as long as 5 to 10 minutes, after speaking, for the text to appear.

You have to follow @cdf's advice and disable it. You'll then find the text appears straight away again.
 
Last edited:
Bmju

Bmju

macrumors 6502a
Dec 16, 2013
702
768
ZNDK said:
Thank you. However, when I press Shift+Enter in OC Picker, the Mac does not crash, but starts up successfully normally. It does not go into safe mode. I want to enable safe mode without messing with Terminal or OpenCore.
Click to expand...
What do you get if you type nvram boot-args in terminal after booting with Shift+Enter?
 
D

dmztff

macrumors newbie
Aug 27, 2018
8
11
cdf said:
Post #1 now includes some instructions for downgrading the AppleFSCompressionTypeZlib kext that causes kernel panics in macOS 12.4 (look for "NoAVXFSCompressionTypeZlib" in Complete your setup > Spoofing, enabling missing features and other fixes). This should stop the panics. Many thanks to @khronokernel for providing the fix!
Click to expand...
For what it's worth, this seems so far to have worked for me; I have not had a panic on my Mac Pro 5,1 since activating the "NoAVXFSCompressionTypeZlib" kext last night and this is by far the longest the machine has gone without a panic since installing 12.4.
 
  • Like
Reactions: ChadaStar, hwojtek and Bmju
Bmju

Bmju

macrumors 6502a
Dec 16, 2013
702
768
ZNDK said:
Terminal:
nvram boot-args
nvram: Error getting variable - 'boot-args': (iokit/common) data was not found
Click to expand...
Hot key detection code is not working properly on your system. Should be, on a MacPro. I guess, just to check, you do have PollAppleHotKeys enabled in your config?
 
Dewdman42

Dewdman42

macrumors 6502a
Jul 25, 2008
513
103
cdf said:
Post #1 now includes some instructions for downgrading the AppleFSCompressionTypeZlib kext that causes kernel panics in macOS 12.4 (look for "NoAVXFSCompressionTypeZlib" in Complete your setup > Spoofing, enabling missing features and other fixes). This should stop the panics. Many thanks to @khronokernel for providing the fix!
Click to expand...

So is this an indicator that future MacOS will be relying on AVX much more and we might actually be reaching end of life finally on the 5,1?

Or is some other hack-around being discussed to make the 5,1 more generally impervious to AVX requirements?
 
C

cdf

macrumors 68020
Original poster
Jul 27, 2012
2,256
2,583
Dewdman42 said:
So is this an indicator that future MacOS will be relying on AVX much more and we might actually be reaching end of life finally on the 5,1?
Click to expand...

The writing has been on the wall for a while. With AVX present on all supported Macs, there is no reason for Apple not to use it, even if just for compiler optimization as hypothesized by @joevt. In fact, as originally pointed out by @Syncretic, this has been the reality since Catalina.

While great contributions from @khronokernel (NoAVXFSCompressionTypeZlib) and @Syncretic (AVXpel) have proved that we can still work around the issue for now, there's no telling for how long. However, I like to believe that with Apple transitioning to its own silicon, x86 will get less attention, keeping any use of unfiltered AVX manageable.

Or is some other hack-around being discussed to make the 5,1 more generally impervious to AVX requirements?
Click to expand...

Yes, that would be AVX emulation.
 
Last edited:
  • Like
Reactions: JeDiGM, prefuse07, greenmeanie and 4 others
Dewdman42

Dewdman42

macrumors 6502a
Jul 25, 2008
513
103
cdf said:
However, I like to believe that with Apple transitioning to it's own silicon, x86 will get less attention, keeping any use of unfiltered AVX manageable.
Click to expand...

Yea one would hope. They are still shipping high priced Intel machines so I guess it makes sense they would continue optimizing for them too.
 
T

trondl

macrumors newbie
Jul 12, 2019
23
2
Hi!
I've realized that Win7 in EFI on my cMP 4,1->5,1 with an EFI flashed GTX980 is too time consuming, thanks to int10h and other crimes against humanity.
VgaShim and UefiSeven couldn't unlock C0000 (also tried to recompile with other addresses. No luck), and Flashboot Pro almost made it to the Windows logo, but gave a 5C BsoD (HAL Initialization failure).
A GT120 card had the same results.
May be due to firmware 144, as my MBP 5,1 actually has Win7 in EFI partially working sans Eth and GPU / display association thanks to gMux (VgaSave hell).

Too many hours have been spent with Grub2 on trying to reverse the CSM PATA back to AHCI in the PCI register and memory space and still end up with an unreasonable system load on System Interrupts (5% constant on an X5680).
If anyone wants to continue my research, shout. A generic 5,1 144 ROM was also tried with the same results.
I believe the load is due to a missconfiguration of ports 5 & 6 associated with bay 3 & 4 after the "reversal", which is lost when using the "common" MBR patch (4+2 instead of 6 combined ports).

Win10 in EFI seems to be the only _reasonable_ solution.

Since I have no intention of using anything past 10.13 High Sierra and already have bootscreen with my GPU, I plan to try OC installed only on the dedicated Win10 SSD in bay 2.
The only function I need is bootROM protection (already have a clean backup).

How could I achieve a _very_ minimal configuration in OC that basically only protects and boots Win10 with as little input during boot as possible?
Could I simply make an USB installer with Win10 that already have OC ready to boot the installer, and then when a reboot is required, I make a "pitstop" to configure the SSD EFI partition?
Ideally from bare metal.

Thanks for any input in advance!
 
startergo

startergo

macrumors 603
Sep 20, 2018
5,022
2,283
trondl said:
Hi!
I've realized that Win7 in EFI on my cMP 4,1->5,1 with an EFI flashed GTX980 is too time consuming, thanks to int10h and other crimes against humanity.
VgaShim and UefiSeven couldn't unlock C0000 (also tried to recompile with other addresses. No luck), and Flashboot Pro almost made it to the Windows logo, but gave a 5C BsoD (HAL Initialization failure).
A GT120 card had the same results.
May be due to firmware 144, as my MBP 5,1 actually has Win7 in EFI partially working sans Eth and GPU / display association thanks to gMux (VgaSave hell).

Too many hours have been spent with Grub2 on trying to reverse the CSM PATA back to AHCI in the PCI register and memory space and still end up with an unreasonable system load on System Interrupts (5% constant on an X5680).
If anyone wants to continue my research, shout. A generic 5,1 144 ROM was also tried with the same results.
I believe the load is due to a missconfiguration of ports 5 & 6 associated with bay 3 & 4 after the "reversal", which is lost when using the "common" MBR patch (4+2 instead of 6 combined ports).

Win10 in EFI seems to be the only _reasonable_ solution.

Since I have no intention of using anything past 10.13 High Sierra and already have bootscreen with my GPU, I plan to try OC installed only on the dedicated Win10 SSD in bay 2.
The only function I need is bootROM protection (already have a clean backup).

How could I achieve a _very_ minimal configuration in OC that basically only protects and boots Win10 with as little input during boot as possible?
Could I simply make an USB installer with Win10 that already have OC ready to boot the installer, and then when a reboot is required, I make a "pitstop" to configure the SSD EFI partition?
Ideally from bare metal.

Thanks for any input in advance!
Click to expand...
Not sure what you are trying to do, but Win10 in MBR rather than UEFI mode is the safest Windows on cMP. You don't need OC here.
 
  • Like
Reactions: Bmju
startergo

startergo

macrumors 603
Sep 20, 2018
5,022
2,283
trondl said:
I want AHCI, plain and simple.
Click to expand...
1654035099476.png


Still not clear. You need to elaborate. Here is a screenshot of Windows 11 in Legacy mode with AHCI controller.
 
T

trondl

macrumors newbie
Jul 12, 2019
23
2
startergo said:
It should use AH CI using VirtualBox Thread 'cMP5,1 and Apple BOOTCAMP assistant for creating Windows 10 partition' https://forums.macrumors.com/thread...nt-for-creating-windows-10-partition.2235132/
Click to expand...
Do you have acces to all drives, including bay 3 and 4 (sata ports 5 & 6)?
Is your sata controller pci id 8086 3a22?

Although a respectable hack, your approach seems a bit too VM heavy.
I’d prefer a more bare metal approach.
Therefore Win10 in EFI mode, ideally with OC protection.
 
T

trondl

macrumors newbie
Jul 12, 2019
23
2
Dewdman42 said:
Legacy mode does not use a VM. VirtualBox is only used temporarily to create the windows 10 partition.
Click to expand...
Which I don’t understand the need to.
Win10 will run on a dedicated ssd in bay 2. Doesn’t the win10 installer partition to the machines liking?
 
P

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,625
441
This is not a Windows support thread. Post #1 contains a valid procedure to install a UEFI Windows 10 or 11 that will be bootable via OpenCore. Those interested in a legacy/Boot Camp version of Windows 10 or earlier should ask elsewhere.
 
  • Like
  • Love
Reactions: prefuse07 and Dewdman42
T

trondl

macrumors newbie
Jul 12, 2019
23
2
PeterHolbrook said:
This is not a Windows support thread. Post #1 contains a valid procedure to install a UEFI Windows 10 or 11 that will be bootable via OpenCore. Those interested in a legacy/Boot Camp version of Windows 10 or earlier should ask elsewhere.
Click to expand...
I am _not_ interested in legacy or Boot Camp versions of Win10 or earlier, that is why I am asking here:
How to create a minimal instance of OC, only to protect Bootrom on a 4,1->5,1 cMP and chainload Win10 in EFI that only resides on a Win10 partition / USB install stick.
That is all.
 
justgu.us

justgu.us

macrumors newbie
Dec 20, 2021
14
1
Amsterdam, The Netherlands
cdf said:
Here is a set of instructions for preparing an OpenCore CD. Pay close attention to the disk identifier, because using the wrong identifier can lead to data loss!

Preparing an OpenCore Rescue CD

You will need:

An EFI folder placed in your home folder, filled with the all necessary OpenCore subfolders (OC and BOOT) and files, including a working configuration file with RequestBootVarRouting turned off (for native blessing)​

Create the EFI with all the files
  • Open Terminal
  • Create a RAM disk by entering hdiutil attach -nomount ram://409600
You should see the identifier of the disk created: /dev/diskA. Replace the actual identifier in the following steps.
  • Format the temporary disk by entering newfs_msdos -v 'EFI' /dev/diskA
  • Assign a mount point to the disk by entering mkdir OpenCoreCD; mount -t msdos /dev/diskA OpenCoreCD
  • Copy your EFI folder to the disk by entering cp -r EFI OpenCoreCD/
  • Unmount the disk and delete the mount point by entering umount OpenCoreCD; rm -r OpenCoreCD
Create an iso of the EFI
  • Make an image file of the disk by entering dd if=/dev/diskA of=OpenCoreCD.img
  • Convert the image to an iso and cleanup the files by entering hdiutil convert OpenCoreCD.img -format UDTO -o OpenCoreCD.iso; mv OpenCoreCD.iso.cdr OpenCoreCD.iso; rm OpenCoreCD.img
Burn the iso to a CD or DVD
  • Right click OpenCoreCD.iso in your home folder and select "Burn to Disk..."
Click to expand...
Can this be done from Linux? Creating an OCLP bootdisk? Or is there anyone who can share this .iso file for whatever version of OSX you're using it for? It would mean the world to me so I can burn the cd, boot my iMac and then finally create my own OC installation. It's just annoying to need a second Mac just to do that and it would help bypass the problem I'm having; showing OSX in High Sierra on my 2nd monitor
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom