Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
I believe that -1 corresponds to 4294967295 (unsigned), the high value mentioned in the manual. It's probably best to stick with Apple's default 10 seconds (9999999).
I have followed @h9826790 setting for this - 999. According to the manual this setting disables the trim action during startup.
 
** Please Help **
I used the opencore program to upgrade to Catalina from Mojave and got that to work but I have no lost my WiFi. I have a zoom job interview tomorrow and I have no idea what to do to try and fix it. I don’t have access to Ethernet right now.
In the short term, the best course of action is just to use Mojave. In the long term, if you are not using Catalina-supported WiFi hardware, you can look into injecting the kext from Mojave:

 
I have followed @h9826790 setting for this - 999. According to the manual this setting disables the trim action during startup.
Why turn it off, though? This setting was introduced in 0.6.6 to address slow drives for which Apple's 10-second default was insufficient. It seems that either sticking to Apple's default (as it was before) or increasing it (to be on the safe side) would be the reasonable choice here.
 
  • Like
Reactions: Dayo
can someone please tell me how i inject a kext from Mojave to get my wifi working again please. I have followed the link and download the kext file and i understand where to put that but have no idea how to edit a config.plist
 
Here are some quick guidelines for editing the configuration file for the Mojave WiFi kext:
  • In your configuration file, locate the Kernel key
  • If this is your first time adding kexts, replace
XML:
<key>Add</key>
<array/>
by​
XML:
<key>Add</key>
<array>

<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>IO80211Mojave.kext</string>
<key>Comment</key>
<string>Mojave WiFi</string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/IO80211Mojave</string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string>19.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>

<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>IO80211Mojave.kext/Contents/PlugIns/AirPortBrcm4331.kext</string>
<key>Comment</key>
<string>Mojave WiFi</string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/AirPortBrcm4331</string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string>19.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>

</array>
  • Otherwise add the two dictionary entries to the array
Refer to Part 2: Advanced Configuration in the guide for more details.
 
Last edited:
  • Like
Reactions: Bmju and tsialex
Here are some quick guidelines for editing the configuration file for the Mojave WiFi kext:
  • In your configuration file, locate the Kernel key
  • If this is your first time adding kexts, replace
XML:
<key>Add</key>
<array/>
by​
XML:
<key>Add</key>
<array>

<dict>
<key>Arch</key>
<string>x86_64</string>
<key>BundlePath</key>
<string>IO80211Mojave.kext</string>
<key>Comment</key>
<string>Mojave WiFi</string>
<key>Enabled</key>
<true/>
<key>ExecutablePath</key>
<string>Contents/MacOS/IO80211Mojave</string>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string>19.0.0</string>
<key>PlistPath</key>
<string>Contents/Info.plist</string>
</dict>

</array>
  • Otherwise add the IO80211Mojave dictionary entry to the array
Refer to Part 2: Advanced Configuration in the guide for more details.
This means nothing to me I have no idea with this, can you give me help.
 
@richardjhurst
as an emergency you can always disable OpenCore and Mojave should work normally.
just remove the disk with the OC EFI partition.
to go back to catalina you must repeat the blessing in recovery.

about the help: in your config.plist find
Code:
<key>Kernel</key>
    <dict>
        <key>Add</key>
        <array/>
and replace as described above by @cdf
if you dont know how to do that, read the part about "Advanced Configuration" in the guide

and by the way... if you connect by cable there is no problem with mojave
 
Last edited:
@richardjhurst
as an emergency you can always disable OpenCore and Mojave should work normally.
just remove the disk with the OC EFI partition.
to go back to catalina you must repeat the blessing in recovery.

about the help: in your config.plist find
Code:
<key>Kernel</key>
    <dict>
        <key>Add</key>
        <array/>
and replace as described above by @cdf
if you dont know how to do that, read the part about "Advanced Configuration" in the guide

and by the way... if you connect by cable there is no problem with mojave
I was using it to get to Catalina which I managed but then had no WiFi. I followed the above and was sure I just did it correctly but no I get to the Apple logo and progress bar then it just blacks out and nothing
 
where is your WIFI problem, in catalina? in mojave?
where did you put your OC? on the catalina disk? then just remove that disk from your mac and boot.
 
I've been using OpenCore on my mid 2010 Mac Pro 5,1 for a few months now based on the information from this and a couple of other forums. I recently updated to OpenCore 0.6.6 and to Big Sur 11.2 from Catalina. And this evening did an OTA update to 11.2.1. Everything appears to be running fine. However I just checked in the system report and my System Firmware Version is now listed as 9144.0.6.6.0. Is this a bug or a feature? Should I be happy or panicking?
 
where is your WIFI problem, in catalina? in mojave?
where did you put your OC? on the catalina disk? then just remove that disk from your mac and boot.
The WiFi problem was in Catalina. But like I said I can’t restart now as it won’t boot past Apple logo. Can’t get into recovery mode either
 
@richardjhurst: read the second line of the post above!
you need to physically remove the harddrive or ssd with the OC install.
then you can boot to mojave. there select again mojave in system preferences / startup disk and reboot
now shut down, re-attach your catalina disk (the one with OC)
then reboot (still mojave) and from there you can fix the (probably messed up) config.plist
 
@richardjhurst: yes but if there is a problem in your config.plist this blocks your mac and you cant do anything.
OC should be on the catalina / big sur disk (and not on the mojave disk). then you always remove the disk and emergency fallback to mojave.
 
@richardjhurst: yes but if there is a problem in the config.plist it blocks your computer and you cant do anything.
it should be on the catalina / big sur disk and not on the mojave disk. then you always have an emergency fallback.
But the disk is one in the same surely. My SSD drive is my operating system if I pull that out there is nothing
 
Question on Update to 11.2.1

Just to confirm with a MacPro5,1 booting with Opencore 0.6.6 and the config.plist from the first post I am not seeing an OTA update to 11.2.1. I have confirmed that 066 is running and the VMM flag is present (see the terminal output). I thought that was all I needed to do in Big Sur to be able to install OTA updates (similar to Catalina).

Code:
StevesMacPro:~ steve$ nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version    REL-066-2021-02-02
StevesMacPro:~ steve$ sysctl machdep.cpu.features
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 SSE4.2 POPCNT AES VMM PCID

Have I missed something?

Regards,
SMF
 
Last edited:
But the disk is one in the same surely. My SSD drive is my operating system if I pull that out there is nothing
So are you saying you did not exactly follow the instructions in the first post? Do you have two drives in your computer - one for Mojave and one for Catalina or did you upgrade your Mojave install to Catalina and no longer have Mohave installed on your computer?
 
Question on Update to 11.2.1

Just to confirm with a MacPro5,1 booting with Opencore 0.6.6 and the config.plist from the first post I am not seeing an OTA update to 11.2.1. I have confirmed that 066 is running and the VMM flag is present (see the terminal output). I thought that was all I needed to do in Big Sur to be able to install OTA updates (similar to Catalina).

Code:
StevesMacPro:~ steve$ nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version    REL-066-2021-02-02
StevesMacPro:~ steve$ sysctl machdep.cpu.features
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 SSE4.2 POPCNT AES VMM PCID

Have I missed something?

Regards,
SMF
Confirmed. It seems Big Sur has been flip-flopping on the checks. Originally VMM wasn't enough, then for 11.1 and 11.2 it was, and now again it's not. However, hybridization has been consistent:
11.2.1.png
 
  • Like
Reactions: Bmju
Confirmed. It seems Big Sur has been flip-flopping on the checks. Originally VMM wasn't enough, then for 11.1 and 11.2 it was, and now again it's not. However, hybridization has been consistent:
View attachment 1727854
Thanks for the confirmation. Big Sur seems a bit more problematic as I don't have Continuity working and haven't found any pointers on how to manually patch Big Sur for that like there are for Mojave and Catalina and now OTA is not being consistent.

OK, so now I study hybridization. It appears that it really is just modifying the BoardID which then makes the system seem like a supported model for Continuity and for updates - correct?

I have been taking a very minimalist approach and only adding the BoardID for the MacPro5,1 to the "SupportedBoardIds" and adding the MacPro5,1 to the "SupportedModelProperties" in the PlatformSupport.plist in the Preboot and Recovery partitions for both Catalina and Big Sur and I have been running great in Catalina with everything working. I have been using OC on a USB stick to boot when I need to perform updates and I used that to install Big Sur on a separate partition (I have three OSs installed - Mojave, Catalina, and now Big Sur).

I will also add I truly appreciate you and everyone else who has gotten us this far.

Regards,
SMF
 
Last edited:
  • Like
Reactions: cdf
OK, so now I study hybridization. It appears that it really is just modifying the BoardID which then makes the system seem like a supported model for Continuity and for updates - correct?
Yes. More importantly, it allows for hardware acceleration.
 
  • Like
Reactions: Bmju
So are you saying you did not exactly follow the instructions in the first post? Do you have two drives in your computer - one for Mojave and one for Catalina or did you upgrade your Mojave install to Catalina and no longer have Mohave installed on your computer?
Yes exactly that. Just the one drive which I updated from Mojave to Catalina and have now ruined because I obviously changed the config.plist incorrectly
 
Not clear why you didn't follow the instructions in Post 1 to use two disks.
Are you actually on a MacPro or something else?

Put information about your system into your signature so that people can see what you are using when responding to your issues.
 
Not clear why you didn't follow the instructions in Post 1 to use two disks.
Are you actually on a MacPro or something else?

Put information about your system into your signature so that people can see what you are using when responding to your issues.
Hi yes Mac Pro 5.1 2012
 
Hi yes Mac Pro 5.1 2012
Add details to signature.

So why disregard the instructions?

Anyway, what's your backup strategy? Don't you have a spare bootable disk?

You need to get your hands on a spare bootable disk, boot into this and fix the situation.

You should have taken my earlier advice.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.