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

[h9826790]

Some help would be greatly appreciated. I've been running open core fine for a while now with great results. Recently, I haven't been seeing a boot screen even though I'm running a GTX680. I tried replacing my Open Core with the latest. Same thing. No boot screen.

You need to flash your GTX680. And that's not OpenCore related

GTX680 4GB - ROM Image - Full Boot Screens, Full Clock Rates & PCI-E 2.0 - 5GT/s

Anyone try this with a 3,1? Hey there, thanks much for all this incredible info. Checking the thread and the signatures of those posting, it looks like everyone is on a MP 4,1 or 5,1. Please forgive me if I missed it somehow, but has anyone tried this on a 2008 Mac Pro, the 3,1? Super...

forums.macrumors.com

 

[Itconnects]

You need to flash your GTX680. And that's not OpenCore related

GTX680 4GB - ROM Image - Full Boot Screens, Full Clock Rates & PCI-E 2.0 - 5GT/s

Anyone try this with a 3,1? Hey there, thanks much for all this incredible info. Checking the thread and the signatures of those posting, it looks like everyone is on a MP 4,1 or 5,1. Please forgive me if I missed it somehow, but has anyone tried this on a 2008 Mac Pro, the 3,1? Super...

forums.macrumors.com

Hey, It was working well with boot screen with or without open core, meaning it was flashed. It just started happening recently after 0.5.7 update of open core, then I lost boot screen. I am on a Dell s332odgf monitor as well

 

[nobullone1964]

Hey, It was working well with boot screen with or without open core, meaning it was flashed. It just started happening recently after 0.5.7 update of open core, then I lost boot screen. I am on a Dell s332odgf monitor as well

Have you considered updating to the most recent version of OpenCore?

 

[Itconnects]

Hey, It was working well with boot screen with or without open core, meaning it was flashed. It just started happening recently after 0.5.7 update of open core, then I lost boot screen. I am on a Dell s332odgf monitor as well

I tried replacing my Open Core with the latest. Same thing. No boot screen.

[automerge]1600379809[/automerge]

Have you considered updating to the most recent version of OpenCore?

 

[nobullone1964]

[automerge]1600379809[/automerge]

Try re-blessing the OpenCore partition. Also, check your config and look for "showPicker". If it shows "false" change to "true". This way it will show every boot. Check the first post and find the terminal command to verify OpenCore is loaded. Actually, try that first.

No quotes.

 

[Itconnects]

I have the bless app. I've blessed repeatedly. I'll try the config situation now and report back.

 

[startergo]

I have the bless app. I've blessed repeatedly. I'll try the config situation now and report back.

The same config file 99% cannot be reused from version to version sometimes even from commit to commit. Always check the config file with the example config file for the current commit or easier with ocvalidate

 

[nobullone1964]

The same config file 99% cannot be reused from version to version sometimes even from commit to commit. Always check the config file with the example config file for the current commit or easier with ocvalidate

I was just wondering. If he has a flashed GPU will it work friendly with bootpicker? I had to put my flashed 7970 in for diagnostic purposes and it wouldn't show Apple's screen when holding down "option".

 

[startergo]

I was just wondering. If he has a flashed GPU will it work friendly with bootpicker? I had to put my flashed 7970 in for diagnostic purposes and it wouldn't show Apple's screen when holding down "option".

It works. Besides he said it was working on 0.5.7.

 

[nobullone1964]

It works. Besides he said it was working on 0.5.7.

True. Thanks for the response. And...you may be right about him using an old config with a newer version of OpenCore.

 

[6DecadesLater]

True. Thanks for the response. And...you may be right about him using an old config with a newer version of OpenCore.

I suggest ITconnects post his config.plist. Also, downgrading to pre-0.5.7 to ensure it still works.

 

[h9826790]

How to get a good configuration OpenCore to use SSDT only for titan ridge ? Thanks

Are you using this SSDT with a correctly flashed Titan Ridge in slot 4?

 

[cdf]

The same config file 99% cannot be reused from version to version sometimes even from commit to commit. Always check the config file with the example config file for the current commit or easier with ocvalidate

In 0.6.1, ocvalidate is rather picky. The utility indicates that our reference config in the wiki is missing omitted SMBIOS entries. We omit those entries because we either do no spoofing, or only spoof minimally for hybridization.

 

[KevinClark]

I always get an error your computer has restart due an error
[automerge]1600443927[/automerge]
yes when I use SSDT File and titan ridge in slot 4

 

[h9826790]

In 0.6.1, ocvalidate is rather picky. The utility indicates that our reference config in the wiki is missing omitted SMBIOS entries. We omit those entries because we either do no spoofing, or only spoof minimally for hybridization.

Yeah, we really need to know what we are doing when use 0.6.1 ocvalidate. Otherwise, the return looks very scary.

 

[h9826790]

I always get an error your computer has restart due an error
[automerge]1600443927[/automerge]
yes when I use SSDT File and titan ridge in slot 4

There should be only one SSDT floating around.

I use it, and my flashed Alpine Ridge is plug and play.

If you use the same SSDT, then I suspect if your card has hardware issue, or if it's badly flashed.

 

[i.am.not.a.hipster]

I got OpenCore installed on my early 2009 MacPro4,1 flashed to MacPro5,1 -- running the latest Big Sur beta, Beta 7 (20A5374g).

GC-Titan Ridge on Slot 4 also shows up correctly.

Please see the screen shots attached.

A couple of observations that may be of interest: --

(1) For Big Sur Beta 7 to boot correctly under OpenCore, the VMM flag under Cpuid1Mask in the config.plist must be set to on, i.e., "AAAAAAAAAAAAAACAAAAAAA==". If set to off ('AAAAAAAAAAAAAAAAAAAAAA=='), Big Sur Beta 7 will show the typical big grey-out power button with multilingual languages asking you to restart your mac; and it will not boot to completion. This issue comes up only in Beta 7 it seems, because I did not encounter this in Betas 5, 6.

(2) I noticed that I must place my RX580 in Slot 2, and my StarTech NVME adapter with Samsung 960 Evo 250GB NVME in Slot 1 (and, of course, Titan Ridge in Slot 4) in order for the MacPro to boot to completion to the login screen. This happens under the Big Sur betas, and if I recall correctly, Catalina and Mojave as well.

Does anyone know why the RX580 needs to be in Slot 2 and the NVME in Slot 1 in order for my Mac Pro to boot to completion?

I'd like to move the RX580 to Slot 1 and the NVME to Slot 3 with the Titan Ridge on Slot 4 so as to improve airflow -- because right now, with the RX580 in Slot 2, its fan is spinning just 1-2 mm under the Titan Ridge in Slot 4.

Any help or insight on this slot order issue would be much appreciated.

Could it be because switching the Slots could perhaps change the path info (i.e., in the general form PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) etc) that I obtain from the acidandthera Github script and then specified in the config.plist -- such that the conflig.plist would need to be re-adjusted for the new slots? It would be difficult for me to test this -- since I only have one Mac.....

Spent the whole of yesterday switching slots and reinstalling stuff but no luck figuring this issue out. Again any help would be welcome.

*****EDIT & UPDATE*****

I can now change slots -- figured out that the path info needs to be updated in the config.plist if the previous slot path was referred therein, because the path changes when the slot is swapped.

***********************

(3) OpenCore 0.61 does not seem to work on my Mac Pro, for either Big Sur Beta 7 or Mojave. At the OC volume selection screen, selecting a volume (or letting it timeout and auto-select) to boot simply reverts back to the volume selection screen; and this loop keeps going. Currently on OpenCore0.60, which works with Big Sur Beta 7.

 

[Itconnects]

I replaced the Entire EFI file, so whatever config came with the latest version is what I'm using. ShowPicker=true...

I have had boot screen for months with or without open core. This only started happening after 0.5.7. I have removed Open Core from my computer still no boot screen. Even with Open Core installed isn't it suppose to show a boot picker?

Something interesting to note. When I remove the EFI file. MacOs doesn't seem to put any folder back in. It's completely blank.

 

[6DecadesLater]

I got OpenCore installed on my early 2009 MacPro4,1 flashed to MacPro5,1 -- running the latest Big Sur beta, Beta 7 (20A5374g).

GC-Titan Ridge on Slot 4 also shows up correctly.

Please see the screen shots attached.

A couple of observations that may be of interest: --

(1) For Big Sur Beta 7 to boot correctly under OpenCore, the VMM flag under Cpuid1Mask in the config.plist must be set to on, i.e., "AAAAAAAAAAAAAACAAAAAAA==". If set to off ('AAAAAAAAAAAAAAAAAAAAAA=='), Big Sur Beta 7 will show the typical big grey-out power button with multilingual languages asking you to restart your mac; and it will not boot to completion. This issue comes up only in Beta 7 it seems, because I did not encounter this in Betas 5, 6.

(2) I noticed that I must place my RX580 in Slot 2, and my StarTech NVME adapter with Samsung 960 Evo 250GB NVME in Slot 1 (and, of course, Titan Ridge in Slot 4) in order for the MacPro to boot to completion to the login screen. This happens under the Big Sur betas, and if I recall correctly, Catalina and Mojave as well.

Does anyone know why the RX580 needs to be in Slot 2 and the NVME in Slot 1 in order for my Mac Pro to boot to completion?

I'd like to move the RX580 to Slot 1 and the NVME to Slot 3 with the Titan Ridge on Slot 4 so as to improve airflow -- because right now, with the RX580 in Slot 2, its fan is spinning just 1-2 mm under the Titan Ridge in Slot 4.

Any help or insight on this slot order issue would be much appreciated.

Could it be because switching the Slots could perhaps change the path info (i.e., in the general form PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) etc) that I obtain from the acidandthera Github script and then specified in the config.plist -- such that the conflig.plist would need to be re-adjusted for the new slots? It would be difficult for me to test this -- since I only have one Mac.....

Spent the whole of yesterday switching slots and reinstalling stuff but no luck figuring this issue out. Again any help would be welcome.

(3) OpenCore 0.61 does not seem to work on my Mac Pro, for either Big Sur Beta 7 or Mojave. At the OC volume selection screen, selecting a volume (or letting it timeout and auto-select) to boot simply reverts back to the volume selection screen; and this loop keeps going. Currently on OpenCore0.60, which works with Big Sur Beta 7.

I had the same issue (3) with catalina when i upgraded to 0.6.1. I didn't do it step by step - ie I didn't reboot every time it said to but did check the config with plutil. I had a backup of the 0.6.0 EFI so simply went back to that and it worked fine. I then redid the entire 0.6.1 update but rebooting at each step indicated. It worked the second time. While doing it the second time I felt I had made an error the first time. One possibility was when enabling nightshift I copied the lilu entry a second time. Possible too that the kexts were not properly all copied (I think). Suggest you redo step by step.
Also rerun the PCI path as I think the PCIRoot string indicates the slot number.

 

[startergo]

In 0.6.1, ocvalidate is rather picky. The utility indicates that our reference config in the wiki is missing omitted SMBIOS entries. We omit those entries because we either do no spoofing, or only spoof minimally for hybridization.

Yeah, we really need to know what we are doing when use 0.6.1 ocvalidate. Otherwise, the return looks very scary.

Ocvalidate complains about generic section missing · Issue #1146 · acidanthera/bugtracker

When only SMBIOS is set in PlatformInfo and Update is set to UpdateSmbios ocvalidate complains about missing Generic section (new): OCS: Missing key Generic, context <PlatformInfo>!

github.com

OC boot halts on empty string in SystemProductName · Issue #1122 · acidanthera/bugtracker

commit 818f9e3f571908f6e0e6a08e09e8d84cc7c4872e added line 161 in OcMacInfoLib.c: ASSERT (ProductName != NULL); If the string SystemProductName exists as a parameter with a NULL (empty) value OC bo...

github.com

 

[6DecadesLater]

I replaced the Entire EFI file, so whatever config came with the latest version is what I'm using. ShowPicker=true...

I have had boot screen for months with or without open core. This only started happening after 0.5.7. I have removed Open Core from my computer still no boot screen. Even with Open Core installed isn't it suppose to show a boot picker?

Something interesting to note. When I remove the EFI file. MacOs doesn't seem to put any folder back in. It's completely blank.

This is strange. If it doesn't work without OC then it is not an OC issue. The fact that it doesn't work natively points to a GTX680 problem? reflash?

 

[cdf]

@startergo: Interesting, so it's an OC design decision that makes our config depend on failsafe values. If we eventually have to fill in the actual values, then the configuration for real Mac users will become unnecessarily complicated.

 

[startergo]

@startergo: Interesting, so it's an OC design decision that makes our config depend on failsafe values. If we eventually have to fill in the actual values, then the configuration for real Mac users will become unnecessarily complicated.

Actually if you open the config file in OpenCore Configurator and save it it will add automatically all missing empty fields in the SMBIOS (If SMBIOS board-id is used). At the same time it now asks for the generic section which is mandatory now even though no parameters are used there. My only concern is will the empty fields in the generic section create empty NVRAM parameters? If it does not then there is no problem. Also I am not using the generic section at all regardless of the ocvalidate complain and I don't see an issue so far.

 

[Itconnects]

This is strange. If it doesn't work without OC then it is not an OC issue. The fact that it doesn't work natively points to a GTX680 problem? reflash?

very strange. I haven’t changed or move anything except Upgrade to 0.5.7 and add a monitor, but I’ve used this monitor in the past with the gtx with no issues

 

[startergo]

very strange. I haven’t changed or move anything except Upgrade to 0.5.7 and add a monitor, but I’ve used this monitor in the past with the gtx with no issues

I would reset NVRAM first.