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 said:
Correct. That it behaves that way is not in dispute. The issue is that it behaves that way due to an undocumented "feature" the developer seems to take a dim view of.

EDIT/CLARIFICATION. The minimal approach is not my subject but the file structure. That is, what is included and what is left out. Definitely all for the minimal approach.

There are clear advantages to having a succinct file by leveraging this undocumented feature. However, as with any such feature, there is a big element of caveat emptor involved.

I suppose all that needs to be done is to keep an eye on changes bearing in mind that changes that impact on undocumented features are not typically documented themselves.


Note that this is not about more or less spoofing.
Click to expand...
FWIW (and having been brought up on this by the OC devs, as someone pointed out...) I would now say: use explicitly empty values for all parts of the config, and update the config with new settings as they are added to OC. If nothing else, this actually forces you to think explicitly about the settings which you are leaving at their defaults. It also means you can use ocvalidate with clean output (no non-errors to mentally filter out). Also, and probably at least as important as the other two, it means that you and your users are already working with an officially supported OC config (rather than e.g. having to turn it into one first, if any issues do arise).
 
  • Like
Reactions: TECK and cdf
h9826790 said:
Please enter the following command in Terminal, what's the return?
nvram boot-args
kextstat | grep -v com.apple
Click to expand...
Here's the results. Thank u

Schermata 2021-02-07 alle 18.04.49.png
 
@cdf @startergo @h9826790 besides the Bluetooth issues I have in Big Sur, there is another issue I noted when I switch back from Mojave to Big Sur, right after the login prompt, I get this warning message no matter how many I restart the Mac: You shutdown your computer because of a problem.



If I shutdown the Mac, then I start it back, the issue is solved.

Another interesting detail is the login theme appearance is not matching the actual desktop theme appearance when set to Auto. Note into above video the dark theme at login prompt and the day theme after login, is like the Mac does not know what time is at login or thinks is late at night, when in fact is 1pm:

IMG_4112.JPG
 
Last edited:
@jackfennimore Has a boot screen issue with his 5500XT on a 3840x2160 display. As you can see in the log, the resolution OC sets is Setting mode 0 with 1920x2160 resolution, which is incorrect. This is the latest config file he used and was still not able to see the bootscreen. Does someone use this 5500XT on a 4k Display?
 

Attachments

  • opencore-2021-02-07-021332.txt.zip
    10.8 KB · Views: 71
  • config (1).zip
    3.3 KB · Views: 63
  • Like
Reactions: jackfennimore
h9826790 said:
That's strange, all required kext and boot arguments are there. And this same combination seems allow other cMP to play DRM streaming videos.

5600XT is the only GPU onboard, right?
Click to expand...
Yes, only one gpu. Can it be related to DP port connector on the graphic card? ASAP I’ll try to use another one... just for trying...
I can also try open an issue ticket on lilu github...
 
startergo said:
I get this message on my supported MBP11,2 and 11,3 in BS with OC. It must be something related to OC.
Click to expand...
Do you mind opening a ticket with a debug log into Acidanthera bugtracker? You have so many Macs, is easy for you. :D Are you experiencing the weird non-detected timezone between login screen and actual screen?
 
Stefano85 said:
Yes, only one gpu. Can it be related to DP port connector on the graphic card? ASAP I’ll try to use another one... just for trying...
I can also try open an issue ticket on lilu github...
Click to expand...
TBH, that look like HDCP issue more than DRM issue to me.

May be you need another cable.
 
iw0rm3r said:
Thank you. I've installed Lilu and WEG, but still no luck. So, just to clarify my problem:
I've got a Mac Pro 5,1 (model A1289) with GTX970 video card (and no original card) running macOS 10.12.6 with NVIDIA web drivers. Tried following guide in this thread, but had no luck with OpenCore 0.6.6 - it just not starting: no boot picker (even if I'm trying to move cursor in boot menu blindly), no OC version from NVRAM, no boot logs (after config changes), no changes in behaviour at all.
At the same time I can run OC version 0.6.5 and earlier. Because there's a warning at the original post about sample config imcompatibility with non-0.6.6 versions I tried to make my own config using dortania guide (https://dortania.github.io/OpenCore-For-Legacy-Macs/config.plist/macpro.html) and had a boot picker at start, OC version from NVRAM, but still no video during boot (no graphics, nor text mode). So I've decided to get back to this guide and made it to the end of part 2. But now I have no video during boot process and no video after macOS load. Every generated boot log contains the same text (attached). Also attached my current OC config and screenshot of "About this Mac" window.
Hope someone in this thread can help me to sort out what's wrong with my setup.
Click to expand...
Can "Missing compatible GOP - Not Found" error be related to modified video card BIOS? I don't know the history or my GTX970 so I'm not sure if it's modified or not.
 
startergo said:
@jackfennimore Has a boot screen issue with his 5500XT on a 3840x2160 display. As you can see in the log, the resolution OC sets is Setting mode 0 with 1920x2160 resolution, which is incorrect. This is the latest config file he used and was still not able to see the bootscreen. Does someone use this 5500XT on a 4k Display?
Click to expand...
since there are no NAVI drivers for Mojave, i use a spare flashed GT 630 to configure OC. then once i've booted into Big Sur, i swap that card for the RX 5500 XT. i get no boot screen / boot picker, but full res picture on my 4K display once in macOS.
 
Hi all, apologies as I know this is slightly off topic but would this also be possible to use on a real Mac Pro 7,1? I would like to use OpenCore to hide one of my GPUs from macOS as it is causing Sleep/Wake issues (RTX Card) but I am really struggling to get the config right. Many thanks in advance for any help thaty can be provided!
 
As I'm (slowly) getting to understand what OpenCore can do for us, it's starting to look more and more that an awful lot of the discussion on this thread is applicable to using OpenCore on any legacy Mac, not just the Mac Pro (cf the question above, actually!).

So I was just wondering:

Do people agree that that impression is true?

Is the thread open to questions about using OpenCore (at least, with configs based off the page 1 config) on Macs other than the Mac Pro?

If yes to the above, I was also wondering, is it possible/likely that the thread title &/or the p.1 info might be updated to point out that some/much of this approach, and discussion, might be relevant not just on the Mac Pro? Or if not, I suppose would it be an idea to have another thread for this?

I'm asking the last question particularly because, although I've been dipping in and out of this thread, I've mainly been on this one instead, and been assuming (because of the title and p.1 description) that the basic steps on p.1 here were 'not for me' (with a MacBookPro10,2) - but now that I understand OC better, and having been pointed back here again by several people, I can see that the basic config and parts of the advanced config are just fine for me, and cleaner (far fewer unnecessary settings) than any other OC config I've come across too, which I greatly prefer! 🥳

Thanks! (Esp. to @cdf, @h9826790 and others for working on this approach! 😊)
 
  • Like
Reactions: cdf
sfalatko said:
Continuity in Big Sur? -

Any advice on how to enable continuity in Big Sur? I have successfully implemented manual patches in Mojave and Catalina but have not found anything on enabling it in Big Sur. Bluetooth and WiFi are working fine in Big Sur as I have upgraded my Airport card.

I did try the "ExtendBTFeatureFlags"setting as TRUE in my config.plist but that didn't work for me. Any help would be appreciated.

I have a 2010 MacPro5,1.

Regards,
SMF
Click to expand...
Anyone have success in getting Continuity/Apple Watch unlock in Big Sur?
 
I'm confused about the p.1 docs around VMM flag and SMBIOS. On my MacBookPro10,2 the VMM flag makes no difference at all to whether I am offered an update (which I am testing now, on the currently available developer track Big Sur 11.3 beta update) whereas spoofing the BoardProduct setting (which is mentioned later on p.1, and as being to do with hardware acceleration) makes all the difference as to whether I am offered the current update.

I've rebooted testing all four possible combinations of these two settings to see when I get offered the update, and it's definitely only the board id which is enabling it, for me. (To make sure nothing else was affecting this, I used the completely vanilla basic config.plist from p.1, with no other edits.)

From what I know now about OC, I would actually have expected the results I am getting! After re-reading p.1, I was hoping to find in the VMM flag a new and unexpected way of enabling updates! But, for me, it's not.
 
Bmju said:
Is the thread open to questions about using OpenCore (at least, with configs based off the page 1 config) on Macs other than the Mac Pro?
Click to expand...

I'd be okay that. Although we should maintain a focus on the Mac Pro and shouldn't go as far as discussing non-Apple hardware, considering other Macs may very well help us learn more about using OpenCore on the Mac Pro. Perhaps others can chime in if they don't agree.

Bmju said:
If yes to the above, I was also wondering, is it possible/likely that the thread title &/or the p.1 info might be updated to point out that some/much of this approach, and discussion, might be relevant not just on the Mac Pro?
Click to expand...

In response to this thread being mentioned by Acidanthera in a more general context, the wiki also uses the title "OpenCore on Legacy Apple Hardware." Depending on the applicability to other models, we can certainly make it more explicit in Part 1.
 
  • Like
Reactions: h9826790 and Bmju
TECK said:
Let's work together on this, is quite easy to keep the properties updated with the new OC releases, but is nice to compare the findings. I was also thinking if you can use the plistlib library formatting for your config.plist, it will be a lot easier for everyone to compare the differences.

plistlib format:
Code: 
<key>Patch</key>
<array>
</array>

Your format, which is perfectly fine:
Code: 
<key>Patch</key>
<array/>
Click to expand...
Assuming I'm allowed to express an opinion on this (given that I care because I want to use start using this setup on a MacBook Pro and not a Mac Pro ;) ) - can I add a note to say that I disagree with the suggestion of using the plistlib format, because the OC sample docs use <array/> and <dict/> and I think it's more important to tie any formatting choices to what they do.
 
I ballsed up an upgrade to OC0.6.6 by not reading the Update instructions, ruined my working macOS drive and then spent some time trying to retrieve the situation. I thought it best to follow the words this time and put an old Barracuda drive in for OC to boot from, and because the words say that Disk A can be 'Any GUID-formatted disk', I used MacOS Extended and not APFS. Turns out that OC0.6.6 really doesn't like anything other than APFS and it'd be good to update the words to include this clue for the clueless (like me). I appreciate that I could go and alter the words but it may be that @cdf had reason not to put that there...
 
  • Like
Reactions: what2be
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
Back