Got a tip for us?
Let us know
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
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Thank you for taking the time to clarify the docs. Based on that update, is unclear to me if
AppleEvent should be left to its default failsafe value (Auto)? For now is custom set to Builtin, into setup.py.
Thanks for reminding me on that part of the guide. Changed SMBIOS in config.plist accordingly.
I honestly find the OC notion of failsafe a bit confusing (too...?) - but the idea seems to be some mixture of 'do no harm' (which indeed is your understanding) but with an added mixin of 'do as close as possible to nothing'.
Whatever it is, it really *isn't* the same as a recommended value; so for instance the recommended value of
KeyForgetThreshold was previously 5 in the docs (it is now listed as between 5 and 7), even though its failsafe is and always was 0 (that example applies on systems using KeySupport, not real Macs however).Equally, the failsafe value of the new
PointerSpeedMul is 0 - which is clearly mad, it means never move the mouse! However the *recommended* value (only just added...) is 1.So the recommended value, for all times starting from when it was introduced and for all systems, for
AppleEvent, is Builtin (and yes, I do agree with you that many recommendations in the docs are indeed somewhat Hackintosh specific - but, I can safely say, not this one).Which is an overlong way of saying: yes, I agree with your choice.
Last edited:
So, can anyone confirm or deny whether Big Sur 11.3 brings in issues for booting (via OC 0.6.7 or 0.6.8) a Mac Pro 5,1 if a USB 3.x or a Titan-Ridge Thunderbolt 3 PCI card is installed?
Hi all
When my 5,1 boots I get two different backgrounds during the process; the first is the one set in OC and the second the one I believe it to be the default for big sur. Between those two there are a few seconds of black screen. Thus my questions are:
Can I set the default background value in OC to match the second one and is the black screen during the switch from one to the other normal?
Thanks!
When my 5,1 boots I get two different backgrounds during the process; the first is the one set in OC and the second the one I believe it to be the default for big sur. Between those two there are a few seconds of black screen. Thus my questions are:
Can I set the default background value in OC to match the second one and is the black screen during the switch from one to the other normal?
Thanks!
Attachments
On modern Macs, the background is "syrah black." For legacy Macs, it was "light gray." Both colors can be set in OC. However, because no Macs with the gray background are supported in Big Sur, the gray option may lead to unexpected results during the second-stage screen, like the apple turning white. Thus it is recommended to use black. It will also make the normal blackout period between the first and second screens less noticeable.
Just installed 0.6.8 on my work machine but had to revert back to 0.6.7 due to WIFI no longer functioning. What's odd is that BT and WiFi hardware is detected but WIFI remains in a constant "off" state. Otherwise, 0.6.8 seems to boot 11.2.3 just fine from a PCIe drive. It however, seems to be significantly slower in booting (debug off) than 0.6.7.
Attaching a copy of my config.plist in case something stands out as being wrong, thus preventing WiFi from working. Has anyone else experienced WIFI issues on an cMP5,1 and 0.6.8?
Attaching a copy of my config.plist in case something stands out as being wrong, thus preventing WiFi from working. Has anyone else experienced WIFI issues on an cMP5,1 and 0.6.8?
Will try that a bit later today. Just to confirm, these are the patches in question?
These patches are for non-Apple cards, right?
Thanks @Dayo, the above tip worked. WiFi is fully functional again. Is there a way ConfigFactory can query if a native-Apple card exists, and if so, automatically disable those patches?
Anyway, 068 seems to be running fine on 11.2.3. Processor speed also seems to be correctly reported now. Curious, but I don't recall seeing SMC version getting "spoofed" with 067 but under 068, it's now reported as 9.9999. Will report back if I notice anything else unusual.
Anyway, 068 seems to be running fine on 11.2.3. Processor speed also seems to be correctly reported now. Curious, but I don't recall seeing SMC version getting "spoofed" with 067 but under 068, it's now reported as 9.9999. Will report back if I notice anything else unusual.
I had a similar discussion with @cdf earlier and I agree that while is best to keep the failsafe values in place for a configuration, certain values do not make sense. Your example is great, that is why I set
PointerSpeedMul to 1 also. See release entry.
Was something that was not ready for release and should have been disabled/deleted (as done now)
There was a recent scare that not only was firmware being inadvertently upgraded, but that the same was happening to the SMC. Turned out to be unfounded but the risk is there. ConfigFactory now sets things up to prevent such from happening if an attempt is made ... similar to the firmware version change.
I have the stock Apple BT/Wifi card that came shipped with most of the cMP5,1 late 2010 models. It won't work natively under Big Sur.
I have been off the forum for a while. I have been sporadically following the Big Sur implementation but haven't committed as I have been swamped and I use my Mac for work-related processing. Yesterday I jumped back in. First, turned VMM flag on and upgraded to the latest Catalina through system pref software update. Then, upgraded OC 0.6.6 --> 0.6.8. Then, upgraded to Big Sur 11.2.3 again just through the system pref software update. Everything went smoothly. The Big Sur upgrade went through 4 login followed by a reboot cycles which was a bit unnerving but in the end Big Sur came up. As far as I can see everything is working (BT, wifi, boot screen). System seems stable and performance is excellent.
Thanks again to everyone involved!
Thanks again to everyone involved!