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

[cdf]

I'll make sure to set LauncherOption=Full when I sort 0.7.7. Why does the drive in bay 1 need blessing? It seems to be booting from there already since the NVRAM reset. So the NVMe drive's EFI shouldn't be affected any more?

Having OC blessed is necessary for proper boot variable routing, which is very important for updates.

What's the speed like booting Mojave off a USB stick? Presumably this needs to be in a built-in USB2 port?

Very slow. But it's fine for very occasional use.

 

[mode11]

Having OC blessed is necessary for proper boot variable routing, which is very important for updates.

I added LauncherOption=Full to the 0.7.1 config and rebooted. Not sure how to tell if the HDD's EFI is now blessed? I tried "sudo bless --info" but just get "Can't access "efi-boot-device" NVRAM variable".

I'm not sure if it's a consequence of having OC on a HDD and booting from an NVMe, but since switching, the boot progress bar now fills up to somewhere between 1/3 - 1/2 way and pauses for a while. Then the screen goes black briefly and the macOS login screen is shown. It used to fill somewhat steadily.

Also, the boot picker always shows, despite Showpicker=False in the Config. Plus, it selects the EFI partition (not sure which drive) by default, which seems wrong. Would it try booting from there rather than Macintosh HD, if I let it time out?

 

[cdf]

I added LauncherOption=Full to the 0.7.1 config and rebooted. Not sure how to tell if the HDD's EFI is now blessed?

If you really wanted to you could always use OpenShell in OC to confirm the blessing.

I'm not sure if it's a consequence of having OC on a HDD and booting from an NVMe, but since switching, the boot progress bar now fills up to somewhere between 1/3 - 1/2 way and pauses for a while. Then the screen goes black briefly and the macOS login screen is shown. It used to fill somewhat steadily.

This is a macOS thing. I noticed the same thing after updating to Monterey.

Also, the boot picker always shows, despite Showpicker=False in the Config. Plus, it selects the EFI partition (not sure which drive) by default, which seems wrong. Would it try booting from there rather than Macintosh HD, if I let it time out?

This is a problem. It indicates that you have multiple OC instances and are actually booting a different one than you think. That EFI entry in the boot menu is the other OC. Note that you cannot boot another instance of OC from OC, so selecting that entry will just reload the same boot menu.

 

[mode11]

This is a problem. It indicates that you have multiple OC instances and are actually booting a different one than you think. That EFI entry in the boot menu is the other OC. Note that you cannot boot another instance of OC from OC, so selecting that entry will just reload the same boot menu.

Strange. I've only got 2 drives in my Mac - the SATA HDD in bay 1 and the NVMe. Both do have an OC on them, but ShowPicker is set to False in both of their Configs. I can delete the OC on my NVMe, if it's safe to do so? I can always boot into Big Sur's Recovery and bless afterwards if necessary.

Whilst looking through my backed up non-working OC 0.7.7, I noticed that a few of the empty folders (e.g. ACPI) were missing. Would OC have automatically deleted empty folders (can't recall doing that)? If the folders were missing, would it have prevented OC from working?

 

[cdf]

Strange. I've only got 2 drives in my Mac - the SATA HDD in bay 1 and the NVMe. Both do have an OC on them, but ShowPicker is set to False in both of their Configs. I can delete the OC on my NVMe, if it's safe to do so? I can always boot into Big Sur's Recovery and bless afterwards if necessary.

Yes. Once you delete that OC, confirm that the EFI entry disappears from the boot menu.

Whilst looking through my backed up non-working OC 0.7.7, I noticed that a few of the empty folders (e.g. ACPI) were missing. Would OC have automatically deleted empty folders (can't recall doing that)? If the folders were missing, would it have prevented OC from working?

No. OC won't do this. The absence of these folders shouldn't prevent OC from working, but it might prevent OC from working properly.

To get to the bottom of the problems you're experiencing, you might want to generate an OC debug log. See Maintenance > Debugging.

 

[mode11]

Yes. Once you delete that OC, confirm that the EFI entry disappears from the boot menu.

Yep, that did it. No picker, just went straight to booting macOS. Perhaps the presence of multiple OCs causes the picker to display? Anyhow, should be blessed now as well if LauncherOption=Full did its thing.

 

[mode11]

OK, I've run OC in debug mode and it generated 3 txt files. The first 2 are full of "success" reports, but the end of the last one there are a bunch of issues (excerpt below). I don't know if this relates to the string for Innie, where my NVMe drive seems to have very long string as reported by gfxutil - PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0). Should the whole lot be used? It seems a lot longer than the example in the guide.

29:126 00:058 OCB: Adding bless entry on disk - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x3,0x0,0x0)/HD(1,GPT,C0CE9492-C62B-4362-BD3D-9205F22BFA03,0x28,0x64000)
29:179 00:052 OCBP: Blessed file is missing
29:237 00:058 OCBP: Blessed folder is missing
29:290 00:052 OCBP: Predefined <nil> \System\Library\CoreServices\boot.efi is missing - Not Found
29:349 00:058 OCBP: Predefined <nil> \EFI\Microsoft\Boot\bootmgfw.efi is missing - Not Found
29:361 00:012 OCBP: Predefined <nil> \EFI\BOOT\BOOTX64.EFI was found
29:415 00:053 OCB: Adding entry type (T:1|F:0|G:1) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x3,0x0,0x0)/HD(1,GPT,C0CE9492-C62B-4362-BD3D-9205F22BFA03,0x28,0x64000)/\EFI\BOOT\BOOTX64.EFI
29:467 00:052 OCB: Discarding discovered OpenCore bootloader
29:526 00:058 OCBP: APFS recovery volume handle missing - \EFI\BOOT\
29:599 00:073 OCB: APFS recovery is not present - Not Found
29:662 00:062 OCB: Adding bless entry on disk - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x3,0x0,0x0)/HD(3,GPT,D5720D79-4780-4B3E-A454-A6B789F3D46D,0xE8E5DCC8,0x40000)
29:689 00:026 OCBP: Blessed file is missing
29:737 00:048 OCBP: Blessed folder is missing
29:790 00:052 OCBP: Predefined <nil> \System\Library\CoreServices\boot.efi is missing - Not Found
29:848 00:058 OCBP: Predefined <nil> \EFI\Microsoft\Boot\bootmgfw.efi is missing - Not Found
29:901 00:052 OCBP: Predefined <nil> \EFI\BOOT\BOOTX64.EFI is missing - Not Found
29:960 00:058 OCB: Adding bless entry on disk - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x3,0x0,0x0)/HD(4,GPT,FD79F332-6872-47B0-ABFF-5D39E0D0D91C,0xE8E9DCC8,0xE8D2E1C0)
30:012 00:052 OCBP: Blessed file is missing
30:026 00:013 OCBP: Blessed folder is missing
30:078 00:052 OCBP: Predefined <nil> \System\Library\CoreServices\boot.efi is missing - Not Found
30:137 00:058 OCBP: Predefined <nil> \EFI\Microsoft\Boot\bootmgfw.efi is missing - Not Found
30:190 00:052 OCBP: Predefined <nil> \EFI\BOOT\BOOTX64.EFI is missing - Not Found

 

[cdf]

OK, I've run OC in debug mode and it generated 3 txt files. The first 2 are full of "success" reports, but the end of the last one there are a bunch of issues (excerpt below).

Your excerpt contains normal messages.

Should the whole lot be used? It seems a lot longer than the example in the guide.

Nothing to worry about here either. The path needed for device properties in the config has a different format.

 

[mode11]

The very last messages, after the ones above, are:

30:248 00:058 OCB: Showing menu... (polling hotkeys)
30:301 00:052 OCHK: InitHotKeys
30:360 00:058 OCKM: Allocated key repeat context 746CF998 746CF918 746CFA18
30:372 00:012 OCAE: Set screen resolution to 2560x1440 - Success
30:426 00:053 OCTY: Registered handler
30:478 00:052 OCAE: Set screen resolution to 2560x1440 - Success
30:537 00:058 OCUI: Console attributes: 0
30:590 00:052 OCUI: UseDiskLabel: 0, UseGenericLabel: 0
30:648 00:058 OCUI: Console attributes: 0
30:701 00:052 OCUI: UseDiskLabel: 0, UseGenericLabel: 0
30:759 00:058 OCUI: Using flavour icon, custom: 0
30:833 00:073 OCUI: Console attributes: 0
30:892 00:059 OCUI: UseDiskLabel: 0, UseGenericLabel: 0
30:946 00:053 OCUI: Console attributes: 0
31:003 00:057 OCUI: UseDiskLabel: 0, UseGenericLabel: 0
31:057 00:053 OCUI: Using flavour icon, custom: 0

Doesn't seem to be much there.

 

[mode11]

Would it make sense to try using the default Config, with SurPlus added?

 

[cdf]

Would it make sense to try using the default Config, with SurPlus added?

Yes. That would be a good start if trying to update to 0.7.7 from Big Sur. You can then add more settings from there.

 

[mode11]

@cdf Thanks so much for all your help today - there were lots of questions! In the end though, I gave up and just used Martin Lo's package, which worked first time.

Although it was quite a struggle, I learned a lot about how OC works along the way. I finished by clearing the NVRAM, removing OC from all the EFIs, and finally installed OC to the Windows SSD in bay 1. This keeps things simple, means Windows is always blocked from booting on its own, and I can easily remove it and put the Mojave disk in its place for BootROM reflashes.

Now for Monterey...

 

[VaZ]

What to do if nvram boot-args don't stick ?!
SIP is off. Tried in Recovery, Big Sur installer, and single-user modes. Nothing.
In Mojave i see it gets added with sudo but after reboot its gone again.

 

[hwojtek]

Add them to your config.plist

 

[sfalatko]

What to do if nvram boot-args don't stick ?!
SIP is off. Tried in Recovery, Big Sur installer, and single-user modes. Nothing.
In Mojave i see it gets added with sudo but after reboot its gone again.

Are you using OpenCore? If so you can put boot args in your config.plist

 

[CaptainZag]

so although the installer crashes identical to the debian installer after a forced reboot i can see a Ubuntu Partition in the boot picker. As mentioned the linux install leaves a mess in my OC EFI partition but i backed it up and replaced the messed up one by the backed up one. Reboot and Linux still works.So i still don't know why the installer crashes everytime it tries to install GRUB but at least it seems to work...
no luck with debian11 thou...

I'm experiencing the same issue with Linux (Ubuntu & Manjaro). Did you manage to solve this, or has anyone a suggestion to get Linux installed successfully i.e. getting past the "Running :grub-install/...." issue?

 

[antonlinus]

I'm experiencing the same issue with Linux (Ubuntu & Manjaro). Did you manage to solve this, or has anyone a suggestion to get Linux installed successfully i.e. getting past the "Running :grub-install/...." issue?

mh so i got it sort of solved but i dont really know. I enabled OpenLinux as described in the OpenCore documentation ( include the openlinuxboot.efi & ext4x64.efi in your config.plist + put the correct .efi files in your drivers folder if you haven't done already). look here (https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Configuration.pdf).
I then installed Ubuntu LTS (the latest stable i think 20.something or so). The install still got stuck at the bootloader install but somehow after i force restarted the partition still boots fine. ?‍♂️
I remember i have also set my bootpicker to only display some partitions. That solved the picker displaying multiple EFI partitions from the linux install...

 

[andysa1966]

Unless your video card has a broken GOP, you should have seen the OC boot menu, and from there, you should be able to select Mojave. If it just rebooted into Recovery, then it's possible that your ESP wasn't properly blessed.

I’ve flashed the rx580 with the original bios. I’ve gone thru the basic setup again, in recovery using terminal to bless the USB EFI, however after reboot it returns to recovery not macOS, I think my ESP is not properly blessed, tied the commands again in terminal, same result. Is there another way without replacing the gfx card with GT120

Thank you for your help

 

[antonlinus]

Anyone know how to fix broken Wifi in Monterey? I'm on latest OC release (0.7.7) and upgraded my Wifi Card to a Broadcom BCM94360CD. Everything worked fine on Catalina and Bluetooth still works fine in Monterey just Wifi not. When i got to Systempreferences > Network > Wifi i get an error message "error in system-preferences".

It also doesn’t work in my mojave partition anymore

Anyone experienced this too? I knew older OG Cards don't work but thought upgraded ones should be fine

 

[antonlinus]

Also it seems Monterey just freezes after maybe 10-15mins and then autorestarts. Known problem?.

I'm using Martins latest package and only moded it to support Thunderbolt and OpenLinuxBoot.
I only seem to have these issues with Monterey not in either Linux,Windows or Mojave.

 

[andysa1966]

I’ve flashed the rx580 with the original bios. I’ve gone thru the basic setup again, in recovery using terminal to bless the USB EFI, however after reboot it returns to recovery not macOS, I think my ESP is not properly blessed, tied the commands again in terminal, same result. Is there another way without replacing the gfx card with GT120

Thank you for your help

Issue with USB Drive, tried a different one and boots to macOS

 

[cdf]

I’ve flashed the rx580 with the original bios. I’ve gone thru the basic setup again, in recovery using terminal to bless the USB EFI, however after reboot it returns to recovery not macOS, I think my ESP is not properly blessed, tied the commands again in terminal, same result. Is there another way without replacing the gfx card with GT120

Thank you for your help

Issue with USB Drive, tried a different one and boots to macOS

Enter the following command in Terminal: nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version. This will tell us whether OC has started at all. It's still strange that the boot menu didn't appear.

 

[andysa1966]

Enter the following command in Terminal: nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version. This will tell us whether OC has started at all. It's still strange that the boot menu didn't appear.

The result


4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102pencore-version REL-077-2022-01-10

Im not seeing boot menu at startup with ShowPicker set to true (or false and Esc at startup), boots straight to Mojave or is this regarding macOS boot picker, not OC? How do I see the OC boot picker?

 

[cdf]

The result


4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102pencore-version REL-077-2022-01-10

Im not seeing boot menu at startup with ShowPicker set to true (or false and Esc at startup), boots straight to Mojave or is this regarding macOS boot picker, not OC?

Good. At least OC is loaded. You could generate a debug log to find out more about the boot menu issue. See Maintenance > Debugging in post #1.

 

[cybercylon]

mh so i got it sort of solved but i dont really know. I enabled OpenLinux as described in the OpenCore documentation ( include the openlinuxboot.efi & ext4x64.efi in your config.plist + put the correct .efi files in your drivers folder if you haven't done already). look here (https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Configuration.pdf).
I then installed Ubuntu LTS (the latest stable i think 20.something or so). The install still got stuck at the bootloader install but somehow after i force restarted the partition still boots fine. ?‍♂️
I remember i have also set my bootpicker to only display some partitions. That solved the picker displaying multiple EFI partitions from the linux install...

I think what happens is that the installer (for Ubuntu and perhaps other distros) is unable to write the needed boot files to the EFI partition on the disk that linux is installed on even though one has set things up correctly. On a PC, there is usually an error message that is displayed, but on a cMP, the installer just crashes at that boot loader install.

I eventually got my install to work by some round about method I'd rather not get into since it isn't an OC problem (unless OC is causing it somehow). I am not aware of this OpenLinux option, but I time has left me short for me to keep up with things.