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

[Salfuman]

You can go to your Fireface Settings app and try setting the 'Bandwidth Limit' to e.g. Analog+AES, something lower than 'All Channels'. Does it help? If you don't have a Westmere Xeon CPU that could be a problem.

Hi, as I thought, there is no change doing what you say.

 

[PeterHolbrook]

@Salfuman: I take it for granted you've installed one of the latest betas or release candidates of Monterey 12.6.1. Can you say anything about the possible solution to a bug of 12.6 and/or Safari 16 that causes Notification Center Banners not to be clickable? Do Monterey 12.6.1 and/or Safari 16.1 (?) exhibit the same bug, or has it been solved?

 

[Salfuman]

@Salfuman: I take it for granted you've installed one of the latest betas or release candidates of Monterey 12.6.1. Can you say anything about the possible solution to a bug of 12.6 and/or Safari 16 that causes Notification Center Banners not to be clickable? Do Monterey 12.6.1 and/or Safari 16.1 (?) exhibit the same bug, or has it been solved?

Hello, I have installed the latest version available in the app, 12.16.1(21G211), I suppose it is the final version. I have no problems with the notification center banners, I can open them perfectly, at least the ones referring to Mail and extracted file notifications...

 

[PeterHolbrook]

I have no problems with the notification center banners, I can open them perfectly, at least the ones referring to Mail and extracted file notifications...

No, I didn't mean those. I was referring, believe it or not, to MacRumors Push Notifications. They are displayed, as they used to be, but you can't interact with them anymore. Clicking on them does nothing. Clicking on Show simply closes the banner, but nothing is displayed on a Safari tab. That became inoperative with the Monterey 12.6/Safari 16 update. It's VERY noticeable.

 

[Salfuman]

No, I didn't mean those. I was referring, believe it or not, to MacRumors Push Notifications. They are displayed, as they used to be, but you can't interact with them anymore. Clicking on them does nothing. Clicking on Show simply closes the banner, but nothing is displayed on a Safari tab. That became inoperative with the Monterey 12.6/Safari 16 update. It's VERY noticeable.

Sorry, I don't have push notifications turned on for websites...

 

[eVasilis]

Hi all
Recently I put a rx 5700 in my 5,1 macpro. On reboot, be it warm or cold I do not get the OC menu, just black screen and then the desktop. Any ideas?

Thanks!

 

[cdf]

Hi all
Recently I put a rx 5700 in my 5,1 macpro. On reboot, be it warm or cold I do not get the OC menu, just black screen and then the desktop. Any ideas?

Thanks!

Try with DirectGopRendering=true if it’s currently disabled.

 

[eVasilis]

DirectGopRendering is set to true. I'll try false.

Thanks

 

[eVasilis]

DirectGopRendering is set to true. I'll try false.

Thanks

Well, no joy with either.

 

[cdf]

Well, no joy with either.

You can get a better idea of what is going on with a debug log (take a look at Maintenance > Debugging in post #1). In many cases, though, the issue turns out to be the card having been flashed with a modified firmware.

 

[eVasilis]

You can get a better idea of what is going on with a debug log (take a look at Maintenance > Debugging in post #1). In many cases, though, the issue turns out to be the card having been flashed with a modified firmware.

Thanks for your help! As it turned out, it was a dummy display port plug I had plugged in one of the card's dp ports. Once out, the menu came back in.

 

[saltarob]

Thanks for the info.

You're right – my video playback problem wasn't related to AMPDeviceDiscoveryAgent – after a restart I still get that in the logs and now I can play videos just fine. I have ”Show this iPhone when on Wi-Fi” unchecked for my phone in the Finder and the messages are still there. Did you change it somewhere else, or?
Monteray is working well for me too overall, but there's always something annoying, right?

Did you ever get to solve what that was about?

After waking from sleep I have these mesages in the system.log

AMPDeviceDiscoveryAgent[766]: Entered:_AMMuxedDeviceDisconnected, mux-device:446
AMPDeviceDiscoveryAgent[766]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:446

The problem I'm facing is that I can't watch any videos on YouTube for example – the video tries to start (spinning circle) but it doesn't start no matter which wen browser I try. So I understand the problem is deeper. A restart will fix the problem, but would be nice to understand what causes it and possibly prevent it from happening.

Hi, I have the same problem with 11.7 (20G817) on Mac Pro 5,1, OpenCore 0.8.3. YouTube and Facebook videos are not playing (spinning circle) and also in DaVinci Resolve the video playback stutters, impossible to edit videos. The same video which stutters in Resovle plays fine in the Finder without any stutter. Yes a restart will fix it for a while but it's very inconvenient especially if I have to finish time sensitive work in Resolve.

Any ideas how to fix this problem?

 

[cakey]

Hi,
I picked up a 5,1 with Catalina installed. Seller told me it is open-core.
I would like to install Mojave (from my MBP - have it saved onto Time Machine drive) onto a SSD.
Do I need to do anything for this to work?
Cheers.

 

[Macschrauber]

Mojave runs natively if you have a Metal GPU.

To wipe what's installed:

add -no_compat-check to the boot-args into config.plist of OpenCore,
prepare a Mojave boot stick and test it,
boot the Mojave boot stick and format the Catalina disk,
do a deep nvram reset (cmd-alt-p-r) 4 times in a row to get rid of the boot entries for OpenCore in the firmware,
Mojave boot stick should be booted and you can install Mojave and migrate.

 

[Gustav Holdoff]

Another new experience from my life with opencore
I have a rescue disk with mojave for cleaning the computer using the tsialex method or for resetting the settings to the factory settings (if you want)
the mojave bootable was on a 500GB ssd - too big for such a small task
Over the weekend i decided to reformat this ssd for windows use and make a new 120gb mojave bootable ssd
Obviously, in order to boot into the mojave recovery, I had to replace the gpu with the standard for mojave - rx580
and remove the opencore disk
After replacing the gpu, i boot into mojave recovery and installed mojave on a new smaller ssd
Then, everything returned back to work in Monterey,
BUT
After reverse manipulation and resetting SMC and NVRAM,
I booted into Windows (I just didn’t see the opencore bootloader menu, since I have several outputs to monitors and I mixed up the connection sequence, and if I mix it up, then the menu is on one monitor, the login window is on another, etc.)
I had to restart several times without logging in to Windows, switching the sequence of connecting video outputs
until I restored the correct sequence and was able to boot into monterey
after logging in, I always run the Activity Monitor to check how disk indexing is going and if any extra processes have appeared
I got a 40% kernel task as it was before with my radeon pro W5700 and which I could not remove in any way
now this kernel task was not deleted by resetting smc and nvram
I turned off the computer and unplugged it for a few hours, unplugged the ram and put it on the back, then reset the nram again and booted into windows.
and then rebooted into macos.
Kernel task is gone.
Probably some codes are written to the nvram or maybe somewhere to the video card - I don’t know,
I’m not an expert
I think it is necessary to study the problem more carefully and use opencore to prohibit macos or windows from writing something in nvram or in the video card buffer
I'm on OC 0.8.5

 

[TECK]

@cdf, now that we know when Ventura is released, is there anything we need to add to OC configuration to block the accidental upgrade?

 

[cdf]

@cdf, now that we know when Ventura is released, is there anything we need to add to OC configuration to block the accidental upgrade?

I suppose this can be done simply by disabling automatic updates in macOS. Good point, though: upgrading to Ventura is not (yet) advisable.

 

[TECK]

upgrading to Ventura is not (yet) advisable

Do we have a planned solution that allows us to upgrade into near future? I thought Monterey is the end of line for cMP 5,1.

 

[tsialex]

I thought Monterey is the end of line for cMP 5,1.

Without patching the sealed system volume, yes, currently Monterey is the end of the line.

To run Ventura you need to patch/downgrade the GPU drivers to eliminate the AVX2.0 requirement, install the Rosetta dyld shared cache, re-install all the drivers removed (like the Intel Intel82574L Ethernet and the UHCI/OHCI USB stack/maps) and several other minor, but also showstopper, things.

Ventura support with MacPro5,1 and MacPro6,1 will likely require OCLP with root patching.

 

[cdf]

Do we have a planned solution that allows us to upgrade into near future? I thought Monterey is the end of line for cMP 5,1.

It’s the end of the line for running macOS unmodified on the 5,1 Mac Pro (unless AVX emulation can be made possible🤞). Ventura has completely changed the game for unsupported Macs. The OCLP developments illustrate that very well and give us an idea of what can be expected.

 

[Art Scrimshanker]

For disk labeling OC provides its own program called disklabel:
View attachment 1676598
Copy and paste that to your Bootx64.efi folder:
View attachment 1676600
cd to the folder in terminal and run:

g5@G5s-Mac-Pro-2 BOOT % /Volumes/EFI/EFI/BOOT/disklabel
Usage:
disklabel -d .disk_label image.ppm!
disklabel -e "Label" .disk_label .disk_label_2x
disklabel -bgra "Label" .disk_label .disk_label_2x

I normally pick the second option disklabel -e "OpenCore" .disk_label .disk_label_2x

 

[Aesthetica]

I'm trying to Install Windows 11 UEFI with OpenCore - and therefore trying to install Opencore on a separate 250mb partition as recommended here, but I don't get the option to install to an individual partition, only to the disk itself. Partition map is GUID and the Opencore partition I've created is FAT16, any ideas?

 

[hwojtek]

Partition map is GUID and the Opencore partition I've created is FAT16, any ideas?

Use FAT32 as God intended.

 

[roobarb!]

Everything is fine, until I boot into Windows 11 (installed in UEFI mode using instructions from Post 1). As it was installing updates I used the CTRL-ENTER combo in OpenCore to select Windows as the system to boot by default, so I'd not end up back in macOS with every update reboot. However, updates complete I reboot the machine manually from Windows, expecting to see the OpenCore menu... but I was immediately landed back into Windows. Seems as though Windows was now booting directly in UEFI mode, not good.

After the usual roundabout of CTRL-ALT-P-R NVRAM reset to boot Mojave, then boot into Mojave recovery, mount and bless the correct /Volumes/EFI I'm back to OpenCore again. So:

- What have I missed which has apparently allowed Windows to rule the roost?
- How can I tell from Windows whether OpenCore booted the system or not?

I'm sure this wasn't a problem previously. Running OC 0.8.1, config.plist attached. TIA for any pointers.

Evening folks, I'm revisiting this problem and hoped someone could take a peek at my config.plist to see if I'm missing something. It seems that Windows 11 in UEFI installation is somehow bypassing OC and booting itself directly, despite ProtectSecureBoot being enabled.

System is the MacPro5,1 in my sig, Windows 11 installed in UEFI mode on an NVMe drive. OC is installed on the NVMe drive which holds Monterey. Mojave is on a drive in Bay 1 for recovery purposes.

I boot Windows 11 using OC (which is configured with a 30 second timeout, so I know whether it's doing the booting or not). All is well and I install some updates. First set of updates install and auto-reboots, I end up back at OC boot menu with Monterey selected as default, as it should be. I choose Windows, boots up fine, finishes some updates. However, on the next reboot I find myself back at the Windows 11 login screen very quickly - in less than the 30 second timeout for OC. Subsequent reboots only boot me back into Windows and very rapidly. No OC boot screen, it's been bypassed, and this happens with warm and cold resets.

How is this possible?

To get back to normal I use CMD-ALT-P-R to reset the PRAM and the system boots into Mojave as it should. I check my BootROM for errors, luckily it's fine, then use sudo nvram "recovery-boot-mode=unused" && reboot to boot into recovery. I disable SIP with csrutil disable and reboot into Mojave. Then I mount the correct EFI partition and use sudo bless --mount /Volumes/EFI --setBoot to put OC back in the driving seat. Reboot and we're back to normal.

Can anyone see where I'm going wrong here? This is all with the latest OC 0.8.5.

 

[Bmju]

Use FAT32 as God intended.

Some FAT formatters will automatically choose FAT16 if the volume is under a certain size. I've never had any problems with it.