Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,625
441
I have same log, but reboot again it not appear!
It appears consistently for me. I think that is probably due to some debug code in Lilu or Whatevergreen that someone neglected to remove in the release version of the relevant kext, or debug code in OC itself.
 

Wombat58

macrumors newbie
Aug 20, 2022
4
0
yes, this is the place for precise and detailed informations. You can't use Bootcamp for Windows since a long time.

Here is some more rtfm ;-) https://dortania.github.io/OpenCore-Legacy-Patcher/WINDOWS.html
Yes, that page sent me to this thread because I am trying to install on a 2012 Mac Pro. Now I have Windows 10 installed, but before I could even run the Apple utilities it must have loaded it's own drivers and now I get a blank screen when it boots. Do I need to reinstall? Or is there some way to enter a safe mode with a keyboard shortcut?
 

dr.mav

macrumors newbie
Jan 5, 2023
13
0
OC itself shouldn't be affected by the OS.

OC is a boot loader, it works before the OS start to load. So, Monterey shouldn't stop OC to activate the Vega FE's UEFI GOP.

In your case, most likely only the Eco mode ROM has a UEFI GOP that can be functioned on the cMP.

Once you finish Monterey installation, you should turn off VMM and turn on SMBIOS spooding. This can re-gain proper CPU power management (including entering low power state and TurboBoost), and should enable full HWAccel for the Vega FE.

If multi monitors setup has issues. Please try single DP monitor setup first. If that works consistently, then we know the cMP and the Vega FE are fine. Just need to find out how to connect the monitors.
I was able to install the Monterey. After that I swap the OC folders with the original ones from your package. I can see the boot screen just under the Eco mode, even with 2 screens connected via DP. Maybe there is something wrong with the firmware on the "power" mode, but there I can't get boot screen, after couple restarts it can appear through HDMI.
Additional issue I have is the performance related. I can work in FCP for about 20 minutes and after the frame rates drops as it was on the hardware without the acceleration. Interesting that the pressure on GPU is always near the 1/3 of the max.
 
Last edited:

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
I was able to install the Monterey. After that I swap the OC folders with the original ones from your package. I can see the boot screen just under the Eco mode, even with 2 screens connected via DP. Maybe there is something wrong with the firmware on the "power" mode, but there I can't get boot screen, after couple restarts it can appear through HDMI.
Additional issue I have is the performance related. I can work in FCP for about 20 minutes and after the frame rates drops as it was on the hardware without the acceleration. Interesting that the pressure on GPU is always near the 1/3 of the max.
In this case, may be you better open another thread which specifically discuss FCP performance issue (or find an old related thread to join).

I believe this is not OC related anymore.
 

roobarb!

macrumors 6502
Jul 30, 2009
277
185
Does anybody know where I can get a trustworthy copy of Monterey 12.3.1? I'm still experiencing unexpected black screen reboots with 12.6 and would like to experiment with the pre-AVX version.

Otherwise I may drop the Mac Pro to Big Sur now I've got this laptop set up with a dock. Graphics-wise the Radeon VII still thrashes this M1 Pro (and I can boot Windows on the MP5,1, woo) but the MacBook Pro is twice as fast multi-core and nearly three times faster single-core for the daily chew. And it saves my electricity bill, think it's using about 5 W. 😂
 

petefox

macrumors newbie
Mar 29, 2022
7
1
Not sure if this is the correct thread. The issue is Open Core related though.
I have a 4,1 Mac Pro (2009), did everything that needs to be done to turn it into a well working 5,1 with Big Sur. The Open Core Version then was 0.6.8 if I remember correctly.

All was good and working perfectly. I installed Windows and that was fine, too. At some point, after booting into Windows at the next boot into Mac OS it froze after selecting Big Sur and would not boot. Instead it got into a loop chiming and jumping back to the picker screen.
As this is only a secondary backup machine I thought I'd just start over again and put the original Mojave startup drive in. Same problem, it freezes halfway through the boot process (there is a flashed GX 680 in there so I have a boot screen).

I've been reading about the possibility that a Windows boot could mess with Boot ROM. Unfortunately I'm not smart enough to re-set Boot ROM to its original state.

Now the question, if I got a 4,1 backplane logic board - they seem to be not so expensive - could I then flash that into 5,1 (like I did originally) even if the processor board is now fitted with (de-lidded) Intel Xeon X5675 CPUs and 48GB of RAM?
I still have the old CPUs and RAM but would be nice if I didn't have to put those back in.

I understand the backplane and processor board versions need to match because of SMC.

Any thoughts appreciated, thanks,

Peter
 

Macschrauber

macrumors 68030
Dec 27, 2015
2,981
1,487
Germany
Thanks, I had fully reset NVRAM already, that didn’t help.

To double check: one data point of a successful full nvram reset is that the startup chime gets louder from the 2nd boot on. Of course if one sets the volume lower before.

In more nerdish way: A successful deep nvram reset is visible in a firmware dump in the appearance of no variables that are marked for deletion, high free space and an empty 2nd VSS stream.

But this is something for the bootrom thread where the gurus like tsialex and syncretic have more details to tell. I am just the person what gathers the information and made a tool around it :)
 

StoneJack

macrumors 68030
Dec 19, 2009
2,731
1,983
Not sure if this is the correct thread. The issue is Open Core related though.
I have a 4,1 Mac Pro (2009), did everything that needs to be done to turn it into a well working 5,1 with Big Sur. The Open Core Version then was 0.6.8 if I remember correctly.

All was good and working perfectly. I installed Windows and that was fine, too. At some point, after booting into Windows at the next boot into Mac OS it froze after selecting Big Sur and would not boot. Instead it got into a loop chiming and jumping back to the picker screen.
As this is only a secondary backup machine I thought I'd just start over again and put the original Mojave startup drive in. Same problem, it freezes halfway through the boot process (there is a flashed GX 680 in there so I have a boot screen).

I've been reading about the possibility that a Windows boot could mess with Boot ROM. Unfortunately I'm not smart enough to re-set Boot ROM to its original state.

Now the question, if I got a 4,1 backplane logic board - they seem to be not so expensive - could I then flash that into 5,1 (like I did originally) even if the processor board is now fitted with (de-lidded) Intel Xeon X5675 CPUs and 48GB of RAM?
I still have the old CPUs and RAM but would be nice if I didn't have to put those back in.

I understand the backplane and processor board versions need to match because of SMC.

Any thoughts appreciated, thanks,

Peter
Windows booter overcomes Mac booter. You have to reinstall Mac system without Windows to restore booter.
 

tsialex

Contributor
Jun 13, 2016
13,455
13,601
Now the question, if I got a 4,1 backplane logic board - they seem to be not so expensive - could I then flash that into 5,1 (like I did originally) even if the processor board is now fitted with (de-lidded) Intel Xeon X5675 CPUs and 48GB of RAM?

If the early-2009 backplane is not yet cross-flashed to MP5,1 firmware, you can't boot with a Westmere Xeon.

I still have the old CPUs and RAM but would be nice if I didn't have to put those back in.

You can buy an already cross-flashed to MP5,1 backplane, but you never know unless the seller specifically states that. Most times it will be with the factory firmware and require the original Nehalem Xeons.

I understand the backplane and processor board versions need to match because of SMC.

Correct.
 

hwojtek

macrumors 68020
Jan 26, 2008
2,274
1,277
Poznan, Poland
Windows booter overcomes Mac booter. You have to reinstall Mac system without Windows to restore booter.
What? No. He's got OC and he can select BS in OC bootpicker. No Windows "booter" overcomes anything, because from the BS standpoint, the Windows does not exist. It's a Big Sur issue or some OC screwup.
I'd remove the Windows disk completely from the OS and use an OC DVD with a vanilla config.plist to check if BS starts. If yes - it's OC. If not - it's either OC or BS. If a BS installation starts after booting from an OC DVD - it's BS issue and a reinstall should remedy it.
 

TECK

macrumors 65816
Nov 18, 2011
1,129
478
Windows booter overcomes Mac booter.
You probably have the default OC Boot Timeout set to 5 seconds or ShowPicker is set to false or your screen is not turning on fast enough to let you pick the right disk. Set it to 15-20 seconds, or during boot, tap the right arrow key on your keyboard at 1 second intervals and eventually your Canopy disk selector will show. When you install Windows, the default boot disk is set to it. Once you are logged into Mac, you can set the default boot disk.
 

antonlinus

macrumors regular
Oct 10, 2019
100
16
This guide explains how to use the excellent OpenCore boot loader to install, run, and update macOS Catalina, Big Sur or Monterey on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.

View attachment 2057744

I followed these instructions to install Windows 11 on an Nvme drive installed in my 5.1 cMP with the latest OC package by martin.
I successfully created the boot USB and executed the commands described in cdfs tutorial. Everything works without issues until the last part where after copying the efi files to the windows drive i reboot and use the bootpicker to select the drive. I get the windows logo and a loading ring but after a few second it gets stuck and nothing seems to happen anymore. I let it run for an hour but nothing changes its just frozen.

VMM flag disabled,ProtectSecureBoot enabled, exFat drivers are correctly loaded in the config and looking at the windows drive from macOS all the system data seems to be there…

Any ideas on how to fix this? I dont wanna run the windows installer in auto and potentially **** up my efi partitions…

Thanks in advance!
 
  • Like
Reactions: Enricote

StoneJack

macrumors 68030
Dec 19, 2009
2,731
1,983
What? No. He's got OC and he can select BS in OC bootpicker. No Windows "booter" overcomes anything, because from the BS standpoint, the Windows does not exist. It's a Big Sur issue or some OC screwup.
I'd remove the Windows disk completely from the OS and use an OC DVD with a vanilla config.plist to check if BS starts. If yes - it's OC. If not - it's either OC or BS. If a BS installation starts after booting from an OC DVD - it's BS issue and a reinstall should remedy it.
yep, thats why you better have not Windows installation when installing Mac and vs versa. Easiest to install separately and then manage entries in the OC booter.
 
  • Like
Reactions: hwojtek

StoneJack

macrumors 68030
Dec 19, 2009
2,731
1,983
You probably have the default OC Boot Timeout set to 5 seconds or ShowPicker is set to false or your screen is not turning on fast enough to let you pick the right disk. Set it to 15-20 seconds, or during boot, tap the right arrow key on your keyboard at 1 second intervals and eventually your Canopy disk selector will show. When you install Windows, the default boot disk is set to it. Once you are logged into Mac, you can set the default boot disk.
I actually went other way. I don't need Windows for anything except few apps and Age of Empires 2 DE, so I set ShowPicker not to show, boot directly in Mac, then installed Parallels and installed Windows in VM. Parallels is good for Age of Empires, not sure about FPS or other type of games and I have clean boot process, automatic Mac login screen. I have to add that my computer is Hackintosh i9-10950
 

StoneJack

macrumors 68030
Dec 19, 2009
2,731
1,983
I followed these instructions to install Windows 11 on an Nvme drive installed in my 5.1 cMP with the latest OC package by martin.
I successfully created the boot USB and executed the commands described in cdfs tutorial. Everything works without issues until the last part where after copying the efi files to the windows drive i reboot and use the bootpicker to select the drive. I get the windows logo and a loading ring but after a few second it gets stuck and nothing seems to happen anymore. I let it run for an hour but nothing changes its just frozen.

VMM flag disabled,ProtectSecureBoot enabled, exFat drivers are correctly loaded in the config and looking at the windows drive from macOS all the system data seems to be there…

Any ideas on how to fix this? I dont wanna run the windows installer in auto and potentially **** up my efi partitions…

Thanks in advance!
Remove your Mac boot disk, install Windows as usual. Afterwards, reconnect your Mac drive and manage Opencore boot sequence.
 

cdf

macrumors 68020
Original poster
Jul 27, 2012
2,256
2,583
I get the windows logo and a loading ring but after a few second it gets stuck and nothing seems to happen anymore. I let it run for an hour but nothing changes its just frozen.
Windows can be strange sometimes, especially on classic Mac Pros. I would recommend trying again. If it still doesn’t work, then try simplifying your hardware setup by removing and disconnecting anything not essential for the installation. Note that it is absolutely crucial that the installation be done by booting through OC, otherwise you will damage your BootROM and risk bricking your machine.
 

antonlinus

macrumors regular
Oct 10, 2019
100
16
Windows can be strange sometimes, especially on classic Mac Pros. I would recommend trying again. If it still doesn’t work, then try simplifying your hardware setup by removing and disconnecting anything not essential for the installation. Note that it is absolutely crucial that the installation be done by booting through OC, otherwise you will damage your BootROM and risk bricking your machine.
Yes thanks thats what i figured and thats why i didn’t want to remove my OC drive.
I’ll try it again with everything non essential disconnected ;) thanks 🙏
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.