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

Dayo

macrumors 68020
Dec 21, 2018
2,257
1,279
6DecadesLater said:
Except - I have to clear the nvram with every restart or the bootpicker does not show up. Computer just sits there and does nothing. A simple quick press of the power button shuts it down - no long press needed. Then with the NVRAM reset (single boot chime - a triple reset doesn't fix problem beyond current boot) the bootpicker shows up and I can boot up Catalina, Mojave or Win10. This happens on a reset or a shutdown.

Thanks
Click to expand...
As @cdf mentioned, this is something related to your PCIe connection. See my request for reboot options to manage this which was then added to v0.5.8: https://github.com/acidanthera/bugtracker/issues/861#issuecomment-616344925

FWIW, I seem to have stopped having the issue after running the maintenance tasks in Onyx:
Screen Shot 2020-07-03 at 7.30.14 AM.jpg
 
startergo

startergo

macrumors 603
Sep 20, 2018
5,022
2,283
joevt said:
It is a list of strings that are used to produce the log. You can tell by all the "%" characters which are replaced by actual numbers and strings when the code is executed.
Click to expand...
I realized that. That is why I included the edit. But these lines/strings are different depending on how you compile the binary. And later when there is a stop during the execution they log different strings/letters (again depending how you compiled the binary). For debugging purposes it might be confusing. There are more options during building the binaries, which output more information, that I have not explored yet.
 
Dayo

Dayo

macrumors 68020
Dec 21, 2018
2,257
1,279
Muscovite said:
Is there a way to edit the text for the icons in the bootpicker? I understand these are derived from the volume names for each disk initially, but I subsequently changed the macos one from Catalina to macOS, yet the bootpicker icon text is still 'Catalina.'
Click to expand...
Only affects APFS drives and not easy to change. See: https://github.com/acidanthera/bugtracker/issues/886

I call it the APFS Label Bug and you would ultimately need to build your own patched version of OC as the devs have it as 'wontfix' at the moment. See: https://github.com/acidanthera/bugtracker/issues/957

You can use my build script, myOC.tool, to do the build and patching after modification for your system. The script only needs modification if doing this specific patch otherwise it can build any released version of OC from v0.5.0 as well as the current git head.

To build a version of OC with the APFS Label Bug Fix:
  • Run diskutil list in Terminal and get the id of the volume (e.g., /dev/disk7s1)
  • Run diskutil info /dev/disk7s1 in Terminal
    • Get the Volume UUID (e.g., B37B22BF-C0B1-4945-84B4-447AHCB2D094)
  • Get a copy of the myOC.tool and open with a text editor such a TextEdit.
  • Search for L"VOL_UUID" and amend to match your Volume UUID. (e.g., L"B37B22BF-C0B1-4945-84B4-447AHCB2D094")
  • Search for L"VOL_NAME" and amend to match the Volume Name you want to appear in OC Bootpicker. (e.g., L"MacHD")
  • Save and run myOC.tool (You need Xcode and such installed)
    • It takes quite a few params but all have defaults that are used if not specified
    • Make the first param "1" to apply this patch. I.E....
      • Running myOC.tool 1 will build current git head and apply this patch
      • Running myOC.tool 1 0.5.9 will build v0.5.9 and apply this patch
      • Running myOC.tool 0 0.5.9 will build v0.5.9 without this patch
      • Running myOC.tool will build current git head without this patch
 
Last edited:
Dayo

Dayo

macrumors 68020
Dec 21, 2018
2,257
1,279
startergo said:
these lines/strings are different depending on how you compile the binary. And later when there is a stop during the execution they log different strings/letters (again depending how you compiled the binary). For debugging purposes it might be confusing.
Click to expand...
... But it's not a log, it's code for generating the log as @joevt mentioned and different for different versions of the efi being compiled. REL Version is different from DBG Version. Not something to be used for debugging by users.
 
O

osxfr33k

macrumors regular
Jun 26, 2019
164
21
From the OP procedure I am not clear on what this is trying to explain what to do?

NVRAM in OC has two sections an Add and Delete. Leave the delete section alone and literally delete the NVRAM entries under Add both Child and Sibling if using a plist editor?

I have the EVGA GT 740 its boots to black screen then eventually boots to desktop. Does OC fix this? All edits in my config file are done according to the OP. I see that there was some posts after saying to make additional changes but this was not updated in the OP?
 
Dayo

Dayo

macrumors 68020
Dec 21, 2018
2,257
1,279
osxfr33k said:
...boots to black screen then eventually boots to desktop. Does OC fix this?
Click to expand...
Yes, it does.
If still getting that, perhaps OC is not actually loaded in the first place.
Go over the setup again to make sure.
 
O

osxfr33k

macrumors regular
Jun 26, 2019
164
21
Dayo said:
Yes, it does.
If still getting that, perhaps OC is not actually loaded in the first place.
Go over the setup again to make sure.
Click to expand...

OP is loaded I setup OP initially with a GT 640 EFI64 flashed card then put in my EVGA UEFI GT 740.

Proof that OP is loaded:


osxfr33k@osxfr33ks-Pro-2 ~ % nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version


4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version REL-059-2020-06-01



So are we suppose to delete Add Nvram entries?
 
R

richgoga

macrumors regular
Oct 11, 2013
150
61
TECK said:
I'm pretty sure he has the same issue.
Click to expand...
Hey, just chiming in here as requested. My issues have only ever been BSoD after installing BootCamp 5 drivers using the Apple installer. Everything is working fine on my latest install. The only Apple driver installed of for BTHostController (think that’s the device name anyway)
I’ve never had a freezing issue... not sure what this refers to.
Thanks for the support everyone
 
Dayo

Dayo

macrumors 68020
Dec 21, 2018
2,257
1,279
Looks OK. Could be something to do with that GPU.
Perhaps one of the experts might chime in.
 
M

Muscovite

macrumors member
Apr 19, 2020
72
40
Dayo said:
Only affects APFS drives and not easy to change. See: https://github.com/acidanthera/bugtracker/issues/886

I call it the APFS Label Bug and you would ultimately need to build your own patched version of OC as the devs have it as 'wontfix' at the moment. See: https://github.com/acidanthera/bugtracker/issues/957

You can use my build script, myOC.tool, to do the build and patching after modification for your system. The script only needs modification if doing this specific patch otherwise it can build any released version of OC from v0.5.0 as well as the current git head.

To build a version of OC with the APFS Label Bug Fix:
  • Run diskutil list in Terminal and get the id of the volume (e.g., /dev/disk7s1)
  • Run diskutil info /dev/disk7s1 in Terminal
    • Get the Volume UUID (e.g., B37B22BF-C0B1-4945-84B4-447AHCB2D094)
  • Get a copy of the myOC.tool and open with a text editor such a TextEdit.
  • Search for L"VOL_UUID" and amend to match your Volume UUID. (e.g., L"B37B22BF-C0B1-4945-84B4-447AHCB2D094")
  • Search for L"VOL_NAME" and amend to match the Volume Name you want to appear in OC Bootpicker. (e.g., L"MacHD")
  • Save and run myOC.tool (You need Xcode and such installed)
    • It takes quite a few params but all have defaults that are used if not specified
    • Make the first param "1" to apply this patch. I.E....
      • Running myOC.tool 1 will build current git head and apply this patch
      • Running myOC.tool 1 0.5.9 will build v0.5.9 and apply this patch
      • Running myOC.tool 0 0.5.9 will build v0.5.9 without this patch
      • Running myOC.tool will build current git head without this patch
Click to expand...
Thanks, this looks way beyond my abilities but I'll give it a shot. Alternatively, could I simply remove and reinstall Open Core with the desired macOS volume name in place? It did pick up 'Catalina' somehow...

Also, regarding the second issue of a 'stray' additional Windows icon on the bootpicker screen, could you or someone please take a look at my diskutil list output and see if you could identify the culprit leftover partition so that I could delete it? VM is virtual memory and is not it, right?

Three physical drives - disk0 is the 1TB no-os data-only PCIe, disk1 is the 128GB Windows drive, and disk2 is the macOS one with Open Core.

Thanks again
 

Attachments

  • Screenshot 2020-07-03 at 12.31.19.png
    Screenshot 2020-07-03 at 12.31.19.png
    154.7 KB · Views: 110
Dayo

Dayo

macrumors 68020
Dec 21, 2018
2,257
1,279
osxfr33k said:
Ok thanks so the OP instructions say to delete the nvram not sure what that is all about?
Click to expand...
Means put in "Delete" section

Muscovite said:
could I simply remove and reinstall Open Core with the desired macOS volume name in place?
Click to expand...
Not sure whether it would work but sure, you could.

Muscovite said:
Also, regarding the second issue of a 'stray' additional Windows icon on the bootpicker screen, could you or someone please take a look at my diskutil list output and see if you could identify the culprit leftover partition so that I could delete it? VM is virtual memory and is not it, right?
Click to expand...
There is no leftover partition there and what you are getting appears related to the first issue which OC has decided not to fix for various reasons.

I have found that running the maintenance tasks in Onyx cures a lot of issues. Perhaps install and give this a try.
 
  • Like
Reactions: osxfr33k
O

osxfr33k

macrumors regular
Jun 26, 2019
164
21
cdf said:
That step is part of the hybridization procedure, which makes -no_compat_check redundant.
Click to expand...

I understand now, but if I still want to use the boot-arg lets say verbose boot just for a while then can I just have delete section only -no_compat_check and delete boot-arg? I want to preserve boot-arg in Add section in case I want to place a -v in boot-arg for verbose boot or any boot argument I may need later.

Also I see some posts after the OP regarding iMac as the model giving a black boot screen, but this was early versions of OC and WTG kext, and nothing has changed in the OP instructions. I seem to have the issue with my EVGA GT 740 2GB GPU. I'll check with tech support but as far as I know those models are all UEFI. Maybe some of the earlier GT 740's were not UEFI, I will verify that and if not EVGA will have firmware to update it to UEFI.

CMMChris suggested alternate configurations to solve the black screen was it decided what was the best option maybe this will solve my black screen? I tried boot-arg agdpmod=pikera, I have not tried rename PXS1 to GFX0, or boot-arg shikigva=32 and shiki-id=Mac-7BA5B2D9E42DDD94. I think later versions of WTG fix some of these or not? Shouldn't there be a "-" in front of those arguments?
 
O

osxfr33k

macrumors regular
Jun 26, 2019
164
21
Well both my EVGA GT 740 and Aero RX560 boot to black screen. Can someone have a look at my Config.plist I followed the OP procedure leaving only external icons fix, I could not find AHCI PCI in System Information to get drive name I think this is for PCIe NvMe all my drives are internal connected the SATA ports.

Does it make any difference that I did the procedure starting with a supported GPU with EFI flashed GPU GT 640?

Config.plist attached.
 

Attachments

  • config.plist.zip
    2.7 KB · Views: 97
O

osxfr33k

macrumors regular
Jun 26, 2019
164
21
After installing OC in EFI are you suppose to leave the Apple folder with extensions and firmware there?
 
205Maxi

205Maxi

macrumors regular
Nov 3, 2019
175
53
I was finally able to get back, but hey what a pita to reinstall Big Sur Jesus... Yesterday I got a corruption on the EFI File, and was asking if someone had a dump, but I was told that it would not work. Anyways I have reconstructed it and finally back up everything and here.

I can see the recovery of Big Sur ( boot picker ) but I am unable to boot from either with 0.5.9 or 0.6 DBG
Does anybody know/have an idea on how I can force Big Sur Recovery to boot?

Note: I have tried the very last DBG and Big Sur did not boot at all, the prohibited sign came on and recovery the apple logo hang no loading bar.
I am actually running the DBG-060-2020-06-29 so with this one I can still boot but only the system, no recovery.

sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery sends me back to my SSD Big Sir.
I would like to run csrutil authenticated-root disable there.

Any any help? Thank you.
 
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