Big Sur removes some of the drivers that are no longer supported, so the missing ones are okay to be missing!
This rings a bell. Similar problem was reported a few weeks ago and it was necessary to remove one of these audio drivers. My recommendation is to remove them all, boot into Big Sur, and install only the Big Sur-compatible versions of the drivers.
Here is the procedure to remove the drivers from the internal macOS SSD:
- At the OpenCore Picker, press space bar to reveal extra options. One of them should be Recovery.
- Boot the Recovery volume.
- Once booted, select Terminal from the Tools menu.
- Then type
ls -l /Volumes and note the exact name of your macOS disk.
- If the disk name contains spaces, type the disk name inside quotes in each line below that asks for it.
- Example:
- If the macOS disk is named Big Sur then each path name below should be entered like this:
/Volumes/"Big Sur"/Library/Extensions/Volumes/"Big Sur"/System/Library/Extensions
- Then type
cd /Volumes/[name-of-macOS-disk]/Library/Extensions
- Then type
ls -l
- Do you see those drivers listed?
- Then delete the following:
rm -rf Sonarworks.kextrm -rf SoundGrid.kextrm -rf UAD2System.kextrm -rf UAFWAudio.kext
- Now type the following (very important):
touch /Volumes/[name-of-macOS-disk]/Library/Extensionstouch /Volumes/[name-of-macOS-disk]/System/Library/Extensions
- Reboot and try to boot macOS normally.
- Does it boot up?
Hey
@CaseySJ,
Once again, you've nailed it! I can't be but grateful for your insights, which have helped me to get through any blockage so far. I appreciate your reliability, reactiveness and educational approach in that thread. So, a thousand thanks to you!
I am sorry to be late. The end of the week was quite busy, and I unfortunately could not find some time to write a decent answer.
So I followed your instructions and everything's working perfectly now!
I was just unable to touch the second
/Volumes/"Big Sur"/System/Library/Extensions directory that you listed, as the system warned me that the directory was read only. But the first touch worked and was apparently enough to force the system to update its kernel extensions.
I wish I could tell you which kext exactly caused the problem. But after having booted the recovery volume 4 times with each of the 4 suspicious kexts copied one after the other and of course touched the
/System/Library/Extensions directory, I could not manage to make crash the booting of the system anymore. It's like if a process happening at the end of the first successful boot (post update to Big Sur) cleaned something up that has definitively prevented any of these 4 kext from killing the system boot.
I also interestingly noticed that the OpenIntelWireless drivers version
2.0.0-alpha keep on working with the
SecureBootModel option still set to
Disabled after the installation (at least the BT module, I did not check the WIFI at that point). Then I anyway switched back to
Default as you recommended it... but I was wondering if it is still necessary for any kind of reasons to do that with the latest version of these drivers?
Last but not least, when I updated my system, the
11.3 version was not yet publicly available (at least here in France). So I am running now on
11.2.3. I could read that some people here are currently experiencing ports issues with this new release, contrary to you if I got you well. I have a
Gigabyte Z490 Vision D like you, would you say that it's safe for me to update to 11.3 with the latest version of OpenCore that you provided?
Thanks again for everything!
... you mean that we cannot use anymore these 4 ports with USB 2 devices, but USB 3 compliant devices will still work, right?