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

[mangombia]

Do you have

-no_compat_check

as part of your boot-args?

For the Monterey config - yes; for the Mojave config - no. But what I'm asking given my setup, with Mojave in SATA1, is if I pull the OC USB and boot, whether the cMP will automatically boot Mojave, and not try to boot either Win10 (in SATA2), or Monterey (in NVMe #2). It was my understanding that since the blessed OC USB is absent the NVRAM won't see the stored boot device, and will default to the first bootable OS in the order of Optical>SATA1-4>NVMe>USB>Network.

I'm just trying to eliminate the step of swapping configs in order to boot Mojave and then back to Monterey. If I could boot into Mojave by just pulling the USB, and then boot back to Monterey by reinstalling the USB, that would be a lot simpler.

 

[OVERKILL338LM]

Monterey is faster. See below.



@Gustav Holdoff I was wondering if you might have some scores for Mojave?

Interestingly, after installing Monterey and then doing the OLP root patch, unlike with Big Sur, both screens work, I don't need to unplug the HDMI cable for my 2nd screen then plug it back in once I login, which I've been having to do on Big Sur. That's a pleasant surprise!

 

[sfalatko]

For the Monterey config - yes; for the Mojave config - no. But what I'm asking given my setup, with Mojave in SATA1, is if I pull the OC USB and boot, whether the cMP will automatically boot Mojave, and not try to boot either Win10 (in SATA2), or Monterey (in NVMe #2). It was my understanding that since the blessed OC USB is absent the NVRAM won't see the stored boot device, and will default to the first bootable OS in the order of Optical>SATA1-4>NVMe>USB>Network.

I'm just trying to eliminate the step of swapping configs in order to boot Mojave and then back to Monterey. If I could boot into Mojave by just pulling the USB, and then boot back to Monterey by reinstalling the USB, that would be a lot simpler.

It should - check your setting for Startup disk. If it is not set to Mojave you can do that.

When I was using a flashed NVIDIA GTX680 I used a USB for OpenCore and would boot with the option key to get the Apple boot picker - I could choose Mojave, my Legacy Win10 or the USB to boot OpenCore for Catalina or Big Sur. When Monterey dropped NVIDIA I found a (relatively) cheap used RX 560 and changed to using a rescueCD for OpenCore

 

[cdf]

If I pull the OC USB (e.g., OC is not loaded) will the cMP default boot to Mojave?

It was my understanding that since the blessed OC USB is absent the NVRAM won't see the stored boot device, and will default to the first bootable OS in the order of Optical>SATA1-4>NVMe>USB>Network.

There is no default order. In my case, it is always my AHCI drive in PCIe slot 3 that gets priority after an NVRAM reset, no matter what other drives (and OSes) are present and where they are located. The quickest way to determine this is by trial and error (just be extra careful with Windows present).

If you're using Mojave just for maintenance, there's a procedure in post #1 for booting Mojave natively. See Maintenance > Disabling OpenCore.

You could also try to use bcfg in OpenShell to set your (native) boot order. However, you'd probably have to repeat the process after every NVRAM reset.

 

[startergo]

ACPI basics explained:

OC-Little-Translated/00_About_ACPI at main · 5T33Z0/OC-Little-Translated

ACPI Hotpatches and Guides for the OpenCore Bootmanager. Enhance and fine-tune your system by adding devices and enabling additional features not covered in the OpenCore Install Guide. - OC-Little-...

github.com

OC-Little: ACPI Hotpatch Samples and Guides for OpenCore​

GitHub - 5T33Z0/OC-Little-Translated: ACPI hotpatches, fixes and configuration guides for OpenCore Bootloader. Enhance and fine-tune your Hackintosh experience. Only place that covers how to use OpenCore Legacy Patcher to run macOS 13+ on Wintel PCs.

ACPI hotpatches, fixes and configuration guides for OpenCore Bootloader. Enhance and fine-tune your Hackintosh experience. Only place that covers how to use OpenCore Legacy Patcher to run macOS 13+...

github.com

 

[Made_in_JAP]

Hello, first of all I want to tell you that I am using an English translator, please excuse me if I do not express myself correctly. The second thing is to thank Martín Lo and all his people for the enormous generosity they have for having built this generic OpenCore package for everyone.

Le escribo con el siguiente problema y con la esperanza de que alguien pueda ayudarme. Tengo un Mac Pro 5.1 (actualizado de 4.1 a 5.1) con un solo procesador (actualizado a X5690 de seis núcleos) y con una tarjeta gráfica Nvidia GeForce 1080 de MacVidCards, ya sabes, con la pantalla de arranque EFI de Apple. Mi sistema operativo era High Sierra. Instalé el paquete 0.77 de Martin con la intención de actualizar a Catalina y así lo hice. Seguí todas las instrucciones proporcionadas por Martin y todo salió bien, la Mac arrancó perfectamente en High Sierra con OpenCore 0.77. Luego actualicé de la tienda de Apple a Catalina el sistema operativo es la última versión, y no tuve problemas. Sin embargo, cuando terminé lo primero que noté fue que mis aplicaciones de 32 bits NO eran compatibles... y aunque eso importa poco para mí, ya que muchos se pueden actualizar a 64 bits, en caso de que me sorprendiera, entonces me gustaría saber por qué. El verdadero problema te lo diré a continuación.

Cambié mi tarjeta gráfica Nvidia por mi nueva tarjeta gráfica Sapphire Nitro+RX 5700 XT y encendí la Mac, se inició como se esperaba, pero antes de que terminara de cargarse, la pantalla se volvió negra y desapareció. Lo he intentado varias veces, y siempre pasa lo mismo, veo que la barra blanca no completa su recorrido, y el monitor de video (tengo dos) se queda en suspensión, es decir se apaga. También lo he probado con los dos monitores. De todos modos...

¿Alguien puede por favor darme la solución? Veo en el foro que nadie tiene este problema. Le estaré eternamente agradecido.

Espero una respuesta.

Saludos cordiales a todos.

José Antonio.

 

[PeterHolbrook]

Josė Antonio, your translation is incomplete. I can understand Spanish, but there are more knowledgeable forum members that might help you better than me.

The latest versions of macOS are 64-bit only.

As for your Sapphire GPU, perhaps your cMP can’t provide the necessary power to it. You might need a Pixlas mod.

 

[Made_in_JAP]

José Antonio, tu traducción está incompleta. Puedo entender español, pero hay miembros del foro con más conocimientos que podrían ayudarte mejor que yo.

Las últimas versiones de macOS son solo de 64 bits.

En cuanto a su GPU Sapphire, quizás su cMP no pueda proporcionarle la potencia necesaria. Es posible que necesite un mod de Pixlas.

Hola Peter. Muchas gracias por tu ayuda. Bueno la verdad es que ando un poco confuso acerca del tema. Según las indicaciones de Martín lo, su OpenCore tiene la capacidad de que siga funcionando las aplicaciones de 32 bits. Por otra parte hay encontré en diferentes hilos que esa gráfica está funcionando perfectamente sin el mod. Gracias de nuevo y Saludos cordiales

 

[PeterHolbrook]

I don’t know about Martin Lo’s settings. I’ve always followed post #1 of this thread. Suerte.

 

[Made_in_JAP]

Gracias Peter. Saludos.

 

[719c6]

what's the output of

pmset -g

in Terminal?

System-wide power settings:
Currently in use:
hibernatemode 0
womp 1
networkoversleep 0
sleep 10 (sleep prevented by mds, apsd, mds_stores, UserEventAgent, SubmitDiagInfo, UserEventAgent)
Sleep On Power Button 1
ttyskeepawake 1
hibernatefile /var/vm/sleepimage
autorestart 0
disksleep 10
displaysleep 10

After a couple of minutes...

System-wide power settings:
Currently in use:
hibernatemode 0
womp 1
networkoversleep 0
sleep 10
Sleep On Power Button 1
ttyskeepawake 1
hibernatefile /var/vm/sleepimage
autorestart 0
disksleep 10
displaysleep 10

 

[startergo]

System-wide power settings:
Currently in use:
hibernatemode 0
womp 1
networkoversleep 0
sleep 10 (sleep prevented by mds, apsd, mds_stores, UserEventAgent, SubmitDiagInfo, UserEventAgent)
Sleep On Power Button 1
ttyskeepawake 1
hibernatefile /var/vm/sleepimage
autorestart 0
disksleep 10
displaysleep 10

After a couple of minutes...

System-wide power settings:
Currently in use:
hibernatemode 0
womp 1
networkoversleep 0
sleep 10
Sleep On Power Button 1
ttyskeepawake 1
hibernatefile /var/vm/sleepimage
autorestart 0
disksleep 10
displaysleep 10

Try this:

pmset -g log | grep -e "Sleep.*due to" -e "Wake.*due to"

 

[Made_in_JAP]

Hello 719c6, thanks for writing an answer. I will do what you suggest and let you know. Kind regards

 

[Made_in_JAP]

Hello 719c6, This is what the terminal shows me;

System-wide power settings:
Currently in use:
hibernatemode 0
womp 0
networkoversleep 0
sleep 0
Sleep On Power Button 1
ttyskeepawake 1
hibernatefile /var/vm/sleepimage
autorestart 0
disksleep 0
displaysleep 0

 

[Made_in_JAP]

Hello again, you are very kind to offer me your help. The last long piece of code you sent me I can't execute by typing it myself, this is due to my total ignorance of terminal usage. When I do, it gives me an error. I'm going to try to copy and paste. I hope I get lucky and this sheds some light on my problem. Kind regards 719c6

 

[Made_in_JAP]

Ah!! I just realized that two members are helping me. Sorry for the dismissal stertergo. Thank you so much for your help STARTERGO!!!

 

[719c6]

Try this:

pmset -g log | grep -e "Sleep.*due to" -e "Wake.*due to"

Did not fix it. FWIW, I tried on 4 cMP 5,1s, all same specs. 2010 dual x5670, 16G memory, HD5770 and a fresh copy of Mojave installed on spindle. For what its worth, sleep works in High Sierra. Mojave was installed with an old GT630 in slot, a little pixelated but works for install.

 

[startergo]

Did not fix it. FWIW, I tried on 4 cMP 5,1s, all same specs. 2010 dual x5670, 16G memory, HD5770 and a fresh copy of Mojave installed on spindle. For what its worth, sleep works in High Sierra. Mojave was installed with an old GT630 in slot, a little pixelated but works for install.

It is not for "fixing". It is for finding out the reason for Sleep/Wake.

 

[719c6]

I have another 2010 same specs except a GTX680 instead of the HD5770. Sleep works. Thinking it has something to do with 5770s...?

 

[719c6]

It is not for "fixing". It is for finding out the reason for Sleep/Wake.

2022-02-14 19:49:11 -0600 Sleep Entering DarkWake state due to 'Software Sleep pid=88': Using AC (Charge:0%) 5 secs

2022-02-14 19:49:16 -0600 Wake DarkWake to FullWake from Invalid [CDNVA] due to HID Activity: Using AC (Charge:0%)

 

[startergo]

2022-02-14 19:49:11 -0600 Sleep Entering DarkWake state due to 'Software Sleep pid=88': Using AC (Charge:0%) 5 secs

2022-02-14 19:49:16 -0600 Wake DarkWake to FullWake from Invalid [CDNVA] due to HID Activity: Using AC (Charge:0%)

Try resetting the SMC:

Desktop computers​

1. Shut down your Mac, then unplug the power cord.
2. Wait 15 seconds, then plug the power cord back in.
3. Wait 5 seconds, then press the power button to turn on your Mac.

Also what is the result from:
pmset -g assertions

 

[719c6]

Try resetting the SMC:

Also what is the result from:
pmset -g assertions

2022-02-15 20:04:14 -0600

Assertion status system-wide:
BackgroundTask 0
ApplePushServiceTask 0
UserIsActive 1
PreventUserIdleDisplaySleep 0
PreventSystemSleep 0
ExternalMedia 0
PreventUserIdleSystemSleep 0
NetworkClientActive 0
Listed by owning process:
pid 94(hidd): [0x0000002c00098066] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle.4294968268.3"
Timeout will fire in 600 secs Action=TimeoutActionRelease
Kernel Assertions: 0x104=USB,MAGICWAKE
id=500 level=255 0x4=USB mod=12/31/69, 6:00 PM description=com.apple.usb.externaldevice.fd300000 owner=Keyboard Hub
id=504 level=255 0x100=MAGICWAKE mod=12/31/69, 6:00 PM description=en1 owner=en1
id=505 level=255 0x4=USB mod=12/31/69, 6:00 PM description=com.apple.usb.externaldevice.fd330000 owner=USB Optical Mouse
Idle sleep preventers: IODisplayWrangler
System sleep preventers: .Display_boot

 

[tsialex]

2022-02-14 19:49:11 -0600 Sleep Entering DarkWake state due to 'Software Sleep pid=88': Using AC (Charge:0%) 5 secs

2022-02-14 19:49:16 -0600 Wake DarkWake to FullWake from Invalid [CDNVA] due to HID Activity: Using AC (Charge:0%)

HID is a Human Interface Device, such as mice/keyboards. BT devices can also be a HID and awake your Mac Pro. Do you have any Bluetooth device connected?

2022-02-15 20:04:14 -0600

Assertion status system-wide:
BackgroundTask 0
ApplePushServiceTask 0
UserIsActive 1
PreventUserIdleDisplaySleep 0
PreventSystemSleep 0
ExternalMedia 0
PreventUserIdleSystemSleep 0
NetworkClientActive 0
Listed by owning process:
pid 94(hidd): [0x0000002c00098066] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle.4294968268.3"
Timeout will fire in 600 secs Action=TimeoutActionRelease
Kernel Assertions: 0x104=USB,MAGICWAKE
id=500 level=255 0x4=USB mod=12/31/69, 6:00 PM description=com.apple.usb.externaldevice.fd300000 owner=Keyboard Hub
id=504 level=255 0x100=MAGICWAKE mod=12/31/69, 6:00 PM description=en1 owner=en1
id=505 level=255 0x4=USB mod=12/31/69, 6:00 PM description=com.apple.usb.externaldevice.fd330000 owner=USB Optical Mouse
Idle sleep preventers: IODisplayWrangler
System sleep preventers: .Display_boot

Also check your BR2032 RTC battery voltage, very weird the date being EPOCH (12/31/69, 6:00 PM Pacific Time)

 

[719c6]

HID is a Human Interface Device, such as mice/keyboards. BT devices can also be a HID and awake your Mac Pro. Do you have any Bluetooth device connected?



Also check your BR2032 RTC battery voltage, very weird the date being EPOCH (12/31/69, 6:00 PM Pacific Time)

No BT connected. And battery voltage okay.

 

[startergo]

No BT connected. And battery voltage okay.

There must be. Keyboard or mouse.