Did you try replacing all three kexts, IOAHCIFamily, IONVMeFamily and IOPCIFamily?
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 Mac OS 11.3 has broken support for older Mac Pros
- Thread starter VitaminK
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
- Status
I noticed something odd. The startup disk is not in about this Mac. Is it because the PCIE is installed in slot1? Not sure.
This happens when the machine has only one disk. It's normal.
Replaced
Attempted to replace both
IOAHCIFamily.kext, but it does not fix the problem.Attempted to replace both
IO80211Family.kext and IO80211FamilyV2.kext, but symbols don't match:
Code:
sudo kmutil install --volume-root /System/Volumes/Update/mnt1/ --update-all
checking collections...
updated extension 'com.Areca.ArcMSR' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/ArcMSR.kext' (mach-o UUID changed from <unknown> to 01FC5EBD-0A34-3E77-9216-53B89DDD8CE4)
updated extension 'com.apple.driver.usb.AppleUSBVHCICommonRSM' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/AppleUSBCommon.kext/Contents/PlugIns/AppleUSBVHCICommonRSM.kext' (mach-o UUID changed from <unknown> to D2DACBE0-CDE2-3D7A-8AA4-632130700764)
updated extension 'com.apple.driver.AirPort.BrcmNIC' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcmNIC.kext' (mach-o UUID changed from D75BF2E4-37CF-3131-AEA1-92D089E0092E to 729DC69F-0B01-3807-B946-AE96C4584DA1)
updated extension 'com.promise.driver.stex' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/PromiseSTEX.kext' (mach-o UUID changed from <unknown> to AE253556-66D8-38D2-B9D1-179B78F29153)
updated extension 'com.apple.driver.IO80211NetBooter' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/IO80211NetBooter.kext' (mach-o UUID changed from F99B53F8-BA4B-37FE-BBFE-4D86A7BF5B92 to 56B5847C-8C9E-33D0-AA4C-027AB3618940)
updated extension 'com.apple.iokit.IO80211Family' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/IO80211Family.kext' (mach-o UUID changed from 0FEA34AB-B3C6-36E4-A63B-3FB8611D6F60 to 27EDE1C0-32A1-3BC9-A93A-49B4E7AD2167)
updated extension 'com.apple.iokit.IO80211FamilyV2' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/IO80211FamilyV2.kext' (mach-o UUID changed from 13EF976B-6D04-33F3-B9F4-46178D344179 to FA0689F9-1CFE-351D-8B83-117E0BEEB442)
updated extension 'com.apple.driver.IO80211NetBooterV2' found on disk at '/System/Volumes/Update/mnt1/System/Library/Extensions/IO80211FamilyV2.kext/Contents/PlugIns/IO80211NetBooterV2.kext' (mach-o UUID changed from 3B7F5205-F857-310A-94FF-556BF7D51C33 to BF28380F-8530-3A49-BB66-1E78C2FAFDBB)
rebuilding release collections: boot, system
rebuilding release collections:
boot kernel collection
system kext collection
failed to build release collection:
One or more binaries has an error which prevented linking. See other errors.
Could not use 'com.apple.driver.AppleBCMWLANCoreMac' because: Failed to bind '__ZN16IO80211Interface23setInterfaceOFDMDesenseE18apple80211_channelx' in 'com.apple.driver.AppleBCMWLANCoreMac' (at offset 0x7312b in __TEXT, __text) as could not find a kext which exports this symbol
com.apple.driver.AppleBCMWLANCoreMac:
Failed to bind '__ZN16IO80211Interface23setInterfaceOFDMDesenseE18apple80211_channelx' in 'com.apple.driver.AppleBCMWLANCoreMac' (at offset 0x7312b in __TEXT, __text) as could not find a kext which exports this symbol
Error Domain=KMErrorDomain Code=31 "Error occurred while building a collection:
1: One or more binaries has an error which prevented linking. See other errors.
2: Could not use 'com.apple.driver.AppleBCMWLANCoreMac' because: Failed to bind '__ZN16IO80211Interface23setInterfaceOFDMDesenseE18apple80211_channelx' in 'com.apple.driver.AppleBCMWLANCoreMac' (at offset 0x7312b in __TEXT, __text) as could not find a kext which exports this symbol
com.apple.driver.AppleBCMWLANCoreMac specific:
1: Failed to bind '__ZN16IO80211Interface23setInterfaceOFDMDesenseE18apple80211_channelx' in 'com.apple.driver.AppleBCMWLANCoreMac' (at offset 0x7312b in __TEXT, __text) as could not find a kext which exports this symbol
" UserInfo={NSLocalizedDescription=Error occurred while building a collection:
1: One or more binaries has an error which prevented linking. See other errors.
2: Could not use 'com.apple.driver.AppleBCMWLANCoreMac' because: Failed to bind '__ZN16IO80211Interface23setInterfaceOFDMDesenseE18apple80211_channelx' in 'com.apple.driver.AppleBCMWLANCoreMac' (at offset 0x7312b in __TEXT, __text) as could not find a kext which exports this symbol
com.apple.driver.AppleBCMWLANCoreMac specific:
1: Failed to bind '__ZN16IO80211Interface23setInterfaceOFDMDesenseE18apple80211_channelx' in 'com.apple.driver.AppleBCMWLANCoreMac' (at offset 0x7312b in __TEXT, __text) as could not find a kext which exports this symbol
}
Seems you don't get my point, until someone reproduces your find, it's dubious/not proved from a scientific stand point. Without a dump to understand and reproduce how your BootROM was created and prove it that is booting reliably while several others can't, it's useless for our diagnostic.
Have it your own way tsialex. I think others here (Pri-est maybe) have a reliably booting cMP3,1. When I have time this week, I'll build a High Sierra boot disk and dump the bootrom with ROMtool for your science (in which I have spent 40+ years working) experiment.
iMac 2020 with thunderbolt on BS beta:
forums.macrumors.com
macOS Big Sur (11.0) - Bugs and bug fixes
I have a 2020 iMac with two TB 3 connections to two separate disk arrays (Thunderbay 4s) which also has two external monitors connected. After the most recent update to 11.3 beta, my iMac boots to a login screen but as soon as I hit enter after my pword, it freezes briefly and then shuts down...
forums.macrumors.com
A glimmer of hope that Apple will fix this issue perhaps? Too bad they didn't get a PROHIBITED symbol.
I hope they report their issue, and I hope it relates to our issue, though Apple's fix could further break our machines.
Yes it looks like they will not fix it for the next release and there will be a lot of screaming.when the systems get updated.A glimmer of hope that Apple will fix this issue perhaps? Too bad they didn't get a PROHIBITED symbol.
There is a claim that the Thunderbolt issue is sorted out in 11.4b1
forums.macrumors.com
Big Sur 11.3 Beta problems - Thunderbolt Bridge!!!
This is FINALLY sorted out in macOS 11.4 Beta (20F5046g)... I called Apple last week when the 11.3 RC came out, and this time they actually wanted to listen to what I had to say.
forums.macrumors.com
So, with all the PCIe issues 11.3/11.4 created for us - from NVMe, to SATA SSD on PCIe, to Thunderbolt, etc. - why is nobody seemingly having any issues with the GPU? I've run GPU benchmarks and stress tests for hours with no issue. I've also copied several TB's of data between my SATA SSD on PCIe and internal HDD's, while booted off that PCIe SSD, and not had any kernel panics. The ONLY problem I've had with any 11.3 beta or 11.4b1 is booting. Maybe I should install a USB3 card and test further, but my CalDigit card doesn't work in Big Sur, and that's my only spare.
I can't even pretend I have the knowledge most of the people in this forum have; I just like to tinker. Still, this is, to my understanding, a valid point: if there is an incompatibility with PCIe in cMPs, it will definitely have an impact on GPUs. So, what if the problem is in the way 11.3 and 11.4 handle storage and kexts such as IOStorageFamily?
Just a thought.
Last edited:
Currently installing it on a Parallels 16.1.2 virtual machine. Not interesting for you, I'm afraid. I'm also looking forward to hearing some news about Titan-Ridge Thunderbolt compatibility on a Mac Pro 5,1 that boots Big Sur off an HDD.
I wiped my 11.4b1 PCIe SSD in the test machine, and am currently doing a fresh install of 11.2.3, from which I'll upgrade to 11.3GM. Not expecting anything different, but it'll be a fresh install that I can play with swapping KEXT's, etc. I must say, it's nice having a spare machine with drives/OS's you don't care about corrupting, on a 2nd monitor, while working from home.
EDIT: That is, on cool days that I'm not paying for air conditioning... we have a short heat wave coming in the next couple days... 96F/35.5C - won't have any excess equipment running!
Would a clean install be any different?I wiped my 11.4b1 PCIe SSD in the test machine, and am currently doing a fresh install of 11.2.3, from which I'll upgrade to 11.3GM. Not expecting anything different, but it'll be a fresh install that I can play with swapping KEXT's, etc. I must say, it's nice having a spare machine with drives/OS's you don't care about corrupting, on a 2nd monitor, while working from home.
In this case, not likely, but always a good idea for valid testing. That SSD was running 11.4b1, so I needed to downgrade anyway - might as well just wipe it and simulate the condition everyone else will be doing - 11.2.3 upgrade to 11.3.
Downloading it now to do a straight upgrade from 11.2.3, NVMe installed on Syba PCIe slot 2. See signature for model.
I performed a clean install of 11.2.3 to a SATA SSD on PCIe card, which went well as expected. I then upgraded it to 11.3, which didn't go well as expected. I lost count of how many times the progress bar got stuck (I have a post-it with a marker stuck on the screen so I know when it gets to that point), and got several prohibited symbols. I finally got to the desktop! What next? Replace some KEXT's with 11.2.3's KEXT's per the GitHub link? @startergo had symbol issues with IO80211Family.kext and IO80211FamilyV2.kext
github.com
Mac Pro 11.3 Beta NVME issues · Issue #110 · dortania/OpenCore-Legacy-Patcher
Describe the bug Im not sure this will fall within the scope of this patcher, Apple's changes in IONvmefamily has broken support with Mac Pros 5,1/4,1/3,1 the bug started with Beta 3 of 11.3 has co...
github.com
I'm running OC 0.6.8 with the Plistlib Generator setup.py example configuration (see #348 for my config.plist).
From 11.2.3, I updated to 11.3 with Software Update. It got stuck once at the progress bar (see below why) forcing me to manually shutdown from the power button. After power-up, it went through installation process rebooting twice and I was presented with the 11.3 setup screen.
After installation, I determined the following pattern for my machine: If there are no computer problems previously detected, the reboot will get stuck at Progress Bar, no matter what. (that explains why upon initial upgrade, Progress Bar got stuck). In other words, everything works if I'm welcomed by the "you shut down your computer because of a problem." error. Once I'm logged in 11.3 and I try to shutdown the Mac (which in 11.2.3 would fix this error message), I'm stuck at Progress Bar boot screen. As long as I don't shutdown, which will reset the shut down error, I can reboot fine many times (I tested the reboot 10 times). I also have a BootROM reconstructed by @tsialex, which I refreshed one month ago.
I'm able to constantly repeat this exact pattern every time. Anything else is functional in 11.3, I'm able to login with my Apple Watch, perform AirDrop, Wifi, Bluetooth, etc. See my signature for all hardware upgrades.
In my case, I might have better success than others because the chip used into Syba SI-PEX40129 (see #341 for chip details),
Posting now from 11.3, these screenshots:
Last edited:
- Status