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

[hwojtek]

I've been using Ventura for a few days on my 2009 4.1 Mac Pro, 5.1 SMBIOS, 3GB RAM, spinning HD, single 2.66 Quad, and GeForce 120 GT.

How does it even install on this spec? 3GB RAM? GT120?

 

[NC12]

How does it even install on this spec? 3GB RAM? GT120?

I believe OCLP patches the OS to run on non metal cards. I can’t imagine it would perform well though

 

[Conzpiral]

Update from macOS Monterey 12.6.3 to 12.6.4 with OpenCore 0.9.0 went without problems here.

It seems Apple must have fixed a little few more things than just the security content in 12.6.4. In 12.6.3 when I logged out User the login screen always fell back to the default Monterey wallpaper and not my custom user one. Now with 12.6.4 it falls back to my custom wallpaper again.

 

[NC12]

I can also report that 12.6.4 works without issues

 

[powers74]

Heyy all you smart kids… sorry to clog up the actual discussion with probably something dumb, but I’m hoping someone can help me with what I’m missing.

I’m trying to follow the OCLP process according to this guy, but when it comes time to reboot holding down the option key, nothing happens. I thought maybe I skipped a step so I started the whole process over again to make sure I didn’t skip anything.

Still nothing happens at first option reboot. My hunch is that I need to pop the original video card back in to get this to work. Is that correct?

Edit - but then to point in post 12,603, would I get to the install and it not work?

Edit 2 - ok I am now realizing that there may be a substantial difference between the OCLP and what this thread is about. Do i understand correctly that OCLP is more of a “patcher for dummies” and the methods in this thread are more of the “manual/custom” route?

 

[PeterHolbrook]

Your second edit about sums it up correctly.

 

[Gustav Holdoff]

May be useful for operancore developers
after installing 12.6.4
at the first login, I caught two strange errors
1. I have two monitors - main and duplicate
on the main -opencore menu and it is the main one for the OS login
- the opencore menu appeared on the first -ok
- but the login did not appear on the first one - black screen
- on the second one I logged in
- but on the first one the desktop did not appear - black screen
2. got this dfsfileproviderextension error on first login

turned off the computer. reset smc and nvram
MACOS 12.6.4 is working

 

[NC12]

Heyy all you smart kids… sorry to clog up the actual discussion with probably something dumb, but I’m hoping someone can help me with what I’m missing.

I’m trying to follow the OCLP process according to this guy, but when it comes time to reboot holding down the option key, nothing happens. I thought maybe I skipped a step so I started the whole process over again to make sure I didn’t skip anything.

Still nothing happens at first option reboot. My hunch is that I need to pop the original video card back in to get this to work. Is that correct?

Edit - but then to point in post 12,603, would I get to the install and it not work?

Edit 2 - ok I am now realizing that there may be a substantial difference between the OCLP and what this thread is about. Do i understand correctly that OCLP is more of a “patcher for dummies” and the methods in this thread are more of the “manual/custom” route?

Yes this thread is the manual/custom route. Most of us have little experience with OCLP. You will find better help on the OCLP discord

 

[powers74]

Your second edit about sums it up correctly.

LoL thanks!

Yes this thread is the manual/custom route. Most of us have little experience with OCLP. You will find better help on the OCLP discord

Gotchya! Sorry for clogging the chat with my ignorance 😅

 

[bookemdano]

Well I finally set up OpenCore and have Monterey up and running on my cMP 4,1->5,1. Only took me three years to get around to it! Excellent job on the guide, @cdf.

Pretty much everything is working fine. One thing I noticed though is that even with setting the board ID of the 2019 Mac Pro, I am not getting the ability to enable true WiFi calling on my cMP (that is, making/receiving calls via my cellular line *even with my phone not nearby*). I can of course enable the more basic version which requires the presence of your iPhone, but that was possible even before OpenCore.

This is a feature Apple added to macOS years ago, but the cMP 5,1 was never whitelisted for it. I had hoped that the spoofing done by OpenCore would enable that functionality, but at least with the settings outlined in post #1 I am not getting the option to set it up.

The easiest way to tell whether WiFi calling is available is to open FaceTime.app and go to Preferences. You will either see:

"...when your iPhone is nearby" (the basic version):


or "...even when your iPhone is not nearby" (also has a button to update your e911 address), which is WiFi calling:



First question: Has anyone managed to enable WiFi Calling (i.e. seeing that second version of FaceTime preferences) on their cMP via OpenCore? If so, can you share your config file?

Second question: Has anyone figured out how Apple determines how to enable/disable that feature? If it is based on a serial number lookup then is it worth trying to enable it? I've read that spoofing another SN could break other stuff that is more important (iMessage, etc.)

Anyway, just wanted to see if anyone has already looked into this and gotten anywhere.

Edit: Just found this post, which implies it's either the board ID, serial number, or combination of the two: https://forums.macrumors.com/threads/numbersync-wifi-calling.1934785/post-22845347

 

[hwojtek]

First question: Has anyone managed to enable WiFi Calling (i.e. seeing that second version of FaceTime preferences) on their cMP via OpenCore?

Never seen this version, even though I have a couple of computers (both Intel and M1) supporting Ventura out of the box. I think it is rather a feature tied to particular carriers (note the "carrier account").

 

[lmateovf]

Hi!
- Nvidia GTX 970 4GB
- MacPro5,1
- Webdrivers on latest High Sierra (17G14042)

, Installed the webdrivers on another macbook, where i booted the high sierra as an external USB drive
- added shikigva=40 (replacing shikigva=128) and nvda_drv_vrl=1, to config.plist manually. OCLP won't boot... what am i doing wrong? The mac makes the boot sound, then 10 seconds aprox, and shutdown

 

[tsialex]

what am i doing wrong?

I can think of several things, like trying to make an unsupported video card to work with an unsupported macOS release, but the main point of my answer to you here is make it clear that you are asking OCLP support on a thread where the focus is for pure OpenCore. If you want OCLP help from people that actually use it, this is definitively not the correct thread. A better thread for OCLP help is this one:

macOS 12 Monterey on Unsupported Macs Thread

This thread will be dedicated to the discussion of running macOS 12.0 on unsupported Macs At the time of writing, WWDC has wrapped up and Developer Seeds have been sent out. We're eagerly awaiting for all our community developers and enthusiasts to test out the new version of macOS We will...

forums.macrumors.com

Btw, get a supported GPU - GTX 970 like any other Pascal NVIDIA GPU was never officially supported by Apple, can't install macOS by itself and can only work with NVIDIA web drivers - trying to make it to work is a constant uphill battle. Don't waste your time.

 

[bookemdano]

Never seen this version, even though I have a couple of computers (both Intel and M1) supporting Ventura out of the box. I think it is rather a feature tied to particular carriers (note the "carrier account").

Yes, it is definitely a carrier-dependent feature. You must first enable Wi-Fi calling on your iPhone (Settings > Phone > Wi-Fi Calling > Wi-Fi Calling on This iPhone), and then you must also enable "Add Wi-Fi Calling For Other Devices" on the same screen. Once those are enabled then your various Macs and iPads can be enabled for the feature.

The big three US carriers offer Wi-Fi calling, as do some MVNOs (smaller carriers). I do not know the situation in other countries.

But regardless, I have those settings on my phone enabled, and my cMP is the only Mac that I have that does not show the ability to enable Wi-Fi calling. I think perhaps the only way to enable it would be to spoof the serial number of a >2012 Mac, as just spoofing the board ID doesn't seem to be enough.

I've found some OpenCore documentation about spoofing a SN, but is anyone aware of any practical consequences of doing so? From the OC documentation it sounds like if you do it carefully and have an AppleID with other devices and a credit card on file, your risk of being blacklisted/banned is low.

Anyone here running OC with a spoofed SN?

Edit: Anyone can look up their carrier on this page to see if this is supported. It seems it is a separate/supplemental feature to "Wi-Fi Calling" that Apple refers to as "Wi-Fi Calling on supported iCloud-connected devices". So it looks like there are carriers that support Wi-Fi calling that do not support using it on Macs and iPads. I am guessing those are also the carriers that don't support Apple Watches, because I believe the same backend technology is used to forward calls to your Apple Watch.

 

[hwojtek]

Yes, it is definitely a carrier-dependent feature. You must first enable Wi-Fi calling on your iPhone (Settings > Phone > Wi-Fi Calling > Wi-Fi Calling on This iPhone), and then you must also enable "Add Wi-Fi Calling For Other Devices" on the same screen. Once those are enabled then your various Macs and iPads can be enabled for the feature.

I do have Wi-Fi calling on my iPhone since my carrier supports it, however there is no setting "Add Wi-Fi Calling For Other Devices". There is only the usual "allow calls on other devices".

Possibly this is an US-only feature.

 

[bookemdano]

I do have Wi-Fi calling on my iPhone since my carrier supports it, however there is no setting "Add Wi-Fi Calling For Other Devices". There is only the usual "allow calls on other devices".
View attachment 2181226
View attachment 2181227 View attachment 2181228

Possibly this is an US-only feature.

Yeah, I edited my previous post with a link from Apple where they detail the various features supported by different carriers.

In Europe, it looks like the only carrier offering "Wi-Fi Calling on supported iCloud-connected devices" is EE in the United Kingdom.

In Hong Kong, it is offered by carriers 3 and SmarTone.

In the US, it is available from:
AT&T
Metro by T-Mobile
Mint Mobile (soon to be acquired by T-Mobile)
Simple Mobile
T-Mobile USA
Ting
Ultra Mobile
Verizon Wireless

So you are right that it is predominantly available only in the US.

Anyway, curious to see if anyone here is running with a spoofed SN (which looks like that comprises a system serial number, MLB (board serial number) and UUID). I may attempt to spoof those to see if I can get my cMP to offer the ability to turn on WiFi calling like my other Macs. Of course it's better not to do that--I fully understand why hybridization is best, but the OpenCore docs are fairly re-assuring in that doing so is unlikely to get me blacklisted. Still, I will probably use my secondary Apple ID while experimenting just to be safe.

 

[startergo]

Yeah, I edited my previous post with a link from Apple where they detail the various features supported by different carriers.

In Europe, it looks like the only carrier offering "Wi-Fi Calling on supported iCloud-connected devices" is EE in the United Kingdom.

In Hong Kong, it is offered by carriers 3 and SmarTone.

In the US, it is available from:
AT&T
Metro by T-Mobile
Mint Mobile (soon to be acquired by T-Mobile)
Simple Mobile
T-Mobile USA
Ting
Ultra Mobile
Verizon Wireless

So you are right that it is predominantly available only in the US.

Anyway, curious to see if anyone here is running with a spoofed SN (which looks like that comprises a system serial number, MLB (board serial number) and UUID). I may attempt to spoof those to see if I can get my cMP to offer the ability to turn on WiFi calling like my other Macs. Of course it's better not to do that--I fully understand why hybridization is best, but the OpenCore docs are fairly re-assuring in that doing so is unlikely to get me blacklisted. Still, I will probably use my secondary Apple ID while experimenting just to be safe.

You can always add properties through an SSDT.

 

[bookemdano]

You can always add properties through an SSDT.

Thanks! Can you elaborate a bit? How could I go about determining what to add via an SSDT? I believe the earliest Macs officially supported for this feature were the 2012 models (with the exception of the 2012 cMP since it was just a 2010 with newer CPUs). This also roughly lines up with when Apple debuted all the Continuity and Handoff features, so in the beginning I was hopeful it would get enabled once a modern Airport card was installed. But despite having done that and with handoff/AW unlock/personal hotspot, etc all working, this one feature is still elusive.


Unfortunately (probably due in part to the fact that this feature isn't widely available worldwide) there is just very little information I've been able to find online about how Apple enables this particular feature. I do know that if I switch off the "Add Wi-Fi Calling For Other Devices" setting on my iPhone and then re-enable it, a push notification goes out to all supported devices (i.e. my ipad and all my Macs except for the cMP) offering to enable Wi-Fi calling on that device. But how exactly Apple is making that determination I don't know.

Maybe it's worth asking over at the OpenCore github to see if there is a way to enable it surgically without so drastic a step as SN spoofing?

 

[startergo]

Thanks! Can you elaborate a bit? How could I go about determining what to add via an SSDT?

In general you can add properties in this example SSDT looking at the IOregistry of your Mac or best at the IORegistry of a wifi calling supported machine.

 

[cdf]

Maybe it's worth asking over at the OpenCore github to see if there is a way to enable it surgically without so drastic a step as SN spoofing?

Given enough time and motivation, there is almost certainly a way to enable this feature via user-space patching, which is definitely preferable to system-wide spoofing. The first step would be to inspect the FaceTime app and related binaries through a reversing tool and to look for how the option is made available in the preferences. If a patch can be found, I’m sure Acidanthera would be happy to add it to FeatureUnlock.

 

[bookemdano]

Given enough time and motivation, there is almost certainly a way to enable this feature via user-space patching, which is definitely preferable to system-wide spoofing. The first step would be to inspect the FaceTime app and related binaries through a reversing tool and to look for how the option is made available in the preferences. If a patch can be found, I’m sure Acidanthera would be happy to add it to FeatureUnlock.

10-4.

I'll do some reading up and see what I can't figure out on this. Thanks for the replies!

 

[TECK]

@cdf or anyone else, I recently upgraded from OC 0.8.8 to 0.9.0 and I'm welcomed by a black screen upon boot, instead of the usual disk picker. It eventually reboots after a minute or so. This is the PR I created for required changes, did I missed any configuration settings?

Edit: I used the default setup.py, instead of the updated one. Everything is okay now.

 

[cdf]

Edit: I used the default setup.py, instead of the updated one. Everything is okay now.

So false alarm?

 

[Stez]

Hey folks, bit of a weird one. Would anyone know why Virtual Box decides to Kernel Panic my MacPro4,1 all of a sudden?

I've attached the kernel panic report but I can't find anything significant in it.

I'm running OpenCore 0.8.8. (a few versions old, yeah) and MacOS 12.6.2.

 

[cdf]

The guide has been updated to OpenCore version 0.9.1. Thanks to @Bmju, a new feature in this version is GopBurstMode, which accelerates preboot video and is therefore especially useful when using DirectGopRendering. Happy updating!