macOS 11 Big Sur on Unsupported Macs Thread

[jackluke]

The WiFi randomly worked (then disappeared) because I used your ready-made prelinkedkernel file. Replacing the kexts hasn't yielded any results so far. OpenCoreAPFSloader3 along with modified Boot plists has allowed booting – but replacing kexts has been so difficult, maybe due to APFS snapshots…I think snapshots booting undo all our changes. I can't use Fix scripts either, because Ethernet isn't reliable – it can't fetch GitHub files.

I'm still documenting my method at post #796. After shifting to prelinkedkernel OpenCore USB method, kext replacement is the most confusing part – because snapshots must mess with everything

https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28608531

Try this new prelinkedkernel that should fix for MacBook7,1 Wifi AirDrop and Ethernet (credit to ASentientBot for ethernet fix on Nvidia based Mac):

MacBook7,1 BigSur prelinkedkernel Wifi AirDrop and Ethernet fix beta1

replaced it here: /Volumes/UUID-BigSur/Preboot/System/Library/PrelinkedKernels/

 

[quaccOS]

Try this new prelinkedkernel that should fix for MacBook7,1 Wifi AirDrop and Ethernet (credit to ASentientBot for ethernet fix on Nvidia based Mac):

MacBook7,1 BigSur prelinkedkernel Wifi AirDrop and Ethernet fix beta1

replaced it here: /Volumes/UUID-BigSur/Preboot/System/Library/PrelinkedKernels/

I have MacBookPro 7,1 – but I'm sure it's similar hardware. Replaced the prelinkedkernel, ran kextcache -i, kmutil, kcditto…but still the same.

Even if WiFi & audio working, system is not usable without NVIDIA graphics acceleration. Working with cryptographically-signed snapshots is also super confusing…you're never sure if the changes actually happened!? After GM, they might drop these prelinkedkernel legacy extensions, which'll make things even harder

 

[jhowarth]

I guess so, but twitter user suggested to use --bootefi --create-snapshot

the path for root mounted system is this: /Volumes/mount-point/System/Library/CoreServices/

I guess /System/Library/CoreServices/ is the diskXsYsZ that is a snapshot, so you should make the new snapshot from the mount-point path.

Also don't exclude that an unbootable new snapshot could be due to wrong kext installed.

Do you show any snapshots being present on your disk? I never explicitly created one but have...

6: APFS Snapshot ⁨com.apple.os.update-...⁩ 14.0 GB disk7s5s1

which suggests that Big Sur may be applying stealth updates that use snapshots.

 

[Payne Mononymous Bachman]

Just wanted to wish everyone a Happy 4th of July.

 

[justperry]

from BigSur terminal type: mount to detect the root mount point of your BigSur System (snapshot) example a generic "diskXsYsZ"

so since "sZ" is a "locked snapshot" (from where you are booting) you should type:
sudo mount -o nobrowse -t apfs /dev/diskXsY /Volumes/AnyDiskLabel/AnyEmptyFolder/

You can't use /Users/ folder as mount point because is busy of course it's using your current user and "disk2" is incorrect also /dev/disk2 is busy (I guess it's your BigSur APFS container), you should specify the partition example "disk2s3".

Once you mounted the System Volume (non-snapshot), then you can replace your kext and make a new snapshot of it.

Been a day later than I thought.

sudo mount -o nobrowse -t apfs /dev/disk2s5 /Volumes/Perry1/Perry/

Just before I wanted to say I didn't succeed, tried everything, eventually just before I wanted to point out it was a no go I tried the above, disk 2s5 is the system partition, that worked.

 

[justperry]

And now this.

perry$ sudo bless --folder /Volumes/Perry1/Perry/SSD/System/Library/CoreServices --bootefi --create-snapshot
Password:
No mount point for /Volumes/Perry1/Perry/SSD/System/Library/CoreServices
Can't determine mount point of '/Volumes/Perry1/Perry/SSD/System/Library/CoreServices' and ''


What is also odd is that it's mounted read only after the disk mounts, really od is that I could delete the ioFamily extension and do the chmod/chown on the extension (I used batchmod) but could not do this on the extension folder.

It should be bless --folder /Volumes/Perry1/SSD/System/Library/CoreServices --bootefi --create-snapshot
But even that does not work.

WTF, I pasted bless --folder and then dragged the coreservices folder onto the terminal, it's exactly the same as I type but now I get this

perry$ bless --folder /Volumes/Perry1/Perry/System/Library/CoreServices --bootefi --create-snapshot


Couldn't copy file "/Volumes/Perry1/Perry/System/Library/CoreServices/boot.efi.x86legacyap.im4m" - Error Domain=NSCocoaErrorDomain Code=513 "“boot.efi.x86legacyap.im4m” couldn’t be copied because you don’t have permission to access “CoreServices”." UserInfo={NSSourceFilePathErrorKey=/System/Volumes/Preboot/59ED799C-5E30-4F55-997F-A3309657C436/usr/standalone/i386/boot.efi.x86legacyap.im4m, NSUserStringVariant=(


Copy


), NSDestinationFilePath=/Volumes/Perry1/Perry/System/Library/CoreServices/boot.efi.x86legacyap.im4m, NSFilePath=/System/Volumes/Preboot/59ED799C-5E30-4F55-997F-A3309657C436/usr/standalone/i386/boot.efi.x86legacyap.im4m, NSUnderlyingError=0x7fbcb2c10af0 {Error Domain=NSPOSIXErrorDomain Code=13 "Permission denied"}}
Can't copy img4 manifests for file /Volumes/Perry1/Perry/System/Library/CoreServices/boot.efi

EDIT: sudo bless --folder /Volumes/Perry1/Perry/System/Library/CoreServices --bootefi --create-snapshot

Seems to have worked.

pvda:~ perry$ sudo bless --folder /Volumes/Perry1/Perry/System/Library/CoreServices --bootefi --create-snapshot
Password:
pvda:~ perry$

No error this time....time to restart.


Did not work, no Wifi.

I think I forgot one step, updating the kernel cache, damn.
All else is ok, see screenshot below.

 

[jhowarth]

I don't have BigSur snapshots (that's why I can build custom prelinkedkernel), so don't know their exact behaviour, but the new snapshot should be only temporary on the folder mount point, and then I assume it copies the snapshot on the BigSur APFS container.

But what's the safest place to where put the sealed "BigSur System", I am not sure of it.

How exactly do you install the original copy of Big Sur beta? Installing on a supported machine seems to result in a snapshot being present for at least one update. Without access to a working recovery partition for Big Sur, it is unclear how you can delete that snapshot so that 'mount -uw /' can work.
[automerge]1593907671[/automerge]

And now this.

perry$ sudo bless --folder /Volumes/Perry1/Perry/SSD/System/Library/CoreServices --bootefi --create-snapshot
Password:
No mount point for /Volumes/Perry1/Perry/SSD/System/Library/CoreServices
Can't determine mount point of '/Volumes/Perry1/Perry/SSD/System/Library/CoreServices' and ''


What is also odd is that it's mounted read only after the disk mounts, really od is that I could delete the ioFamily extension and do the chmod/chown on the extension (I used batchmod) but could not do this on the extension folder.

It should be bless --folder /Volumes/Perry1/SSD/System/Library/CoreServices --bootefi --create-snapshot
But even that does not work.

WTF, I pasted bless --folder and then dragged the coreservices folder onto the terminal, it's exactly the same as I type but now I get this

perry$ bless --folder /Volumes/Perry1/Perry/System/Library/CoreServices --bootefi --create-snapshot


Couldn't copy file "/Volumes/Perry1/Perry/System/Library/CoreServices/boot.efi.x86legacyap.im4m" - Error Domain=NSCocoaErrorDomain Code=513 "“boot.efi.x86legacyap.im4m” couldn’t be copied because you don’t have permission to access “CoreServices”." UserInfo={NSSourceFilePathErrorKey=/System/Volumes/Preboot/59ED799C-5E30-4F55-997F-A3309657C436/usr/standalone/i386/boot.efi.x86legacyap.im4m, NSUserStringVariant=(


Copy


), NSDestinationFilePath=/Volumes/Perry1/Perry/System/Library/CoreServices/boot.efi.x86legacyap.im4m, NSFilePath=/System/Volumes/Preboot/59ED799C-5E30-4F55-997F-A3309657C436/usr/standalone/i386/boot.efi.x86legacyap.im4m, NSUnderlyingError=0x7fbcb2c10af0 {Error Domain=NSPOSIXErrorDomain Code=13 "Permission denied"}}
Can't copy img4 manifests for file /Volumes/Perry1/Perry/System/Library/CoreServices/boot.efi

EDIT: sudo bless --folder /Volumes/Perry1/Perry/System/Library/CoreServices --bootefi --create-snapshot

Seems to have worked.

pvda:~ perry$ sudo bless --folder /Volumes/Perry1/Perry/System/Library/CoreServices --bootefi --create-snapshot
Password:
pvda:~ perry$

No error this time....time to restart.


Did not work, no Wifi.

I think I forgot one step, updating the kernel cache, damn.
All else is ok, see screenshot below.

View attachment 930740

It will be interesting to hear if you can still boot after rebuilding the kernel caches. In my hands, the following always produces a kernel that fails to boot.

mkdir /Users/howarth/mntpoint
sudo mount -o nobrowse -t apfs /dev/disk7s5 /Volumes/BigSur/Users/howarth/mntpoint
<replacing kext in /Volumes/BigSur/Users/howarth/mntpoint/System/Library/Extensions/>
kextcache -i / ; kcditto
bless --folder /Volumes/AnyDiskLabel/Users/howarth/mntpoint/System/Library/CoreServices --bootefi --create-snapshot

The bit that I find really dubious in these instructions is...

kextcache -i / ; kcditto

since the changes aren't really present in the root filesystem currently mounted at / but are still trapped in Volumes/BigSur/Users/howarth/mntpoint/. So I think maybe one has to make the changes to the kexts, bless the snapshot and then trigger the rebuild of the prelinked kernel *after* the next boot? Otherwise, I don't see how...

kextcache -i / ; kcditto

can be working on the changed kexts.

 

[jhowarth]

Finally got audio working on a MacPro 3,1. After using kext-droplet to install...

(from Catalina Patchers kext)
AppleHDA.kext
AppleIntelPIIXATA.kext
LegacyUSBInjector.kext
LegacyUSBVideoSupport.kext

(from 10.15.5)
IO80211Family.kext

and after the reboot executing...
mkdir /Users/howarth/mntpoint
sudo mount -o nobrowse -t apfs /dev/disk7s5 /Volumes/BigSur/Users/howarth/mntpoint
cd /Volumes/BigSur/Users/howarth/mntpoint/System/Library/Extensions
sudo rm -fr IO80211Family.kext
sudo rm -fr AppleHDA.kext
bless --folder /Volumes/BigSur/Users/howarth/mntpoint/System/Library/CoreServices --bootefi --create-snapshot

The glitchy bit is here. Rebooting at this point will fail but if I boot back into Catalina, remount the Preboot partition on Big Sur and reinstall the prelinkedkernel that I was using, the boot will work again.

Under Big Sur, the audio now works and checking in Extensions of System Profiler shows that the duplicated kext for AppleHDA.kext and IO80211Family.kext are now missing so you don't have to worry about whether the SLE or LE kext wins out in loading.

I think we are missing some trickery before the blessing. Perhaps the form of those missing commands should be something like...

sudo kextcache -I /Volumes/BigSur/Users/howarth/mntpoint/
sudo kcditto

since we want the kext present in the mounted snapshot to be used rather than the current root one. I am unclear though whether that form of kextcache and kcditto will place the files in the correct locations for the mounted snapshot prior to the blessing.

 

[Barry K. Nathan]

Thank you i have install with your script big sur on my 2011 with k2100 gpu... But one question inwill install totalfinder but this need mount -uw ...i has 66 error can you help me or give me an trick ?

I'll try to take a look at TotalFinder in the next few days.
[automerge]1593932150[/automerge]

I'm trying to use barrykn's micro patcher, but when I try to run the terminal command for micropatcher.sh, it tells me that "payloads" folder wasn't found, even though I have it downloaded! Please help!

I'll try updating the patcher to deal with the situation that causes this instead of just erroring out. I'll try to get v0.0.8 done in the next couple days with this fix.

Edit: The fix was easier than I expected, so I've released v0.0.8 now. However, note that for 2011 MacBook Pros, brightness control doesn't work. I think I should be able to fix this in v0.0.9 of the patcher for 13" 2011 MacBook Pros, at some point in the next several days. (And hopefully some release after that for 15" and 17", but the 13" is what I have so it's what I need to try to get working and what I can test easily.)

 

[justperry]

How exactly do you install the original copy of Big Sur beta? Installing on a supported machine seems to result in a snapshot being present for at least one update. Without access to a working recovery partition for Big Sur, it is unclear how you can delete that snapshot so that 'mount -uw /' can work.
[automerge]1593907671[/automerge]


It will be interesting to hear if you can still boot after rebuilding the kernel caches. In my hands, the following always produces a kernel that fails to boot.

mkdir /Users/howarth/mntpoint
sudo mount -o nobrowse -t apfs /dev/disk7s5 /Volumes/BigSur/Users/howarth/mntpoint
<replacing kext in /Volumes/BigSur/Users/howarth/mntpoint/System/Library/Extensions/>
kextcache -i / ; kcditto
bless --folder /Volumes/AnyDiskLabel/Users/howarth/mntpoint/System/Library/CoreServices --bootefi --create-snapshot

The bit that I find really dubious in these instructions is...

kextcache -i / ; kcditto

since the changes aren't really present in the root filesystem currently mounted at / but are still trapped in Volumes/BigSur/Users/howarth/mntpoint/. So I think maybe one has to make the changes to the kexts, bless the snapshot and then trigger the rebuild of the prelinked kernel *after* the next boot? Otherwise, I don't see how...

kextcache -i / ; kcditto

can be working on the changed kexts.

It boots.
What I think is wrong is this, boot caches on / will be updated, to me that sounds wrong, it should be the mount point.
Like
kextcache -i /Volumes/Perry1/Perry/SSD ; kcditto

Perry1/Perry/SSD/ is the mountpoint
Next, bless the folder.

Or am I wrong?

I think we are missing some trickery before the blessing. Perhaps the form of those missing commands should be something like...

sudo kextcache -I /Volumes/BigSur/Users/howarth/mntpoint/
sudo kcditto

Seems like the both of us had the same idea.

 

[MacHacJac]

This is kind of unrelated and might sound like a silly question, but is there a way of installing Big Sur on a separate partition without having to create a new computer account/ having to re-sign into iCloud?

 

[jhowarth]

It boots.
What I think is wrong is this, boot caches on / will be updated, to me that sounds wrong, it should be the mount point.
Like
kextcache -i /Volumes/Perry1/Perry/SSD ; kcditto

Perry1/Perry/SSD/ is the mountpoint
Next, bless the folder.

Or am I wrong?




Seems like the both of us had the same idea.

I am still baffled how jackluke ever got 'sudo mount -uw /' to work under Big Sur. Every single clean install that I have done resulted in a snapshot for an update being present at disk7s6. My understanding is that the presence of snapshots will block the 'sudo mount -uw /' command so that you would have to undo the update by removing its snapshot under a Big Sur recovery volume (which doesn't exist yet for unsupported Macs). Even if you could do remove the snapshot, removing an update doesn't seem like a good idea.

So I think if we ever get to a dosdude1-type installer, it will have to assume that the user has disabled 'authenticated-root' with a Big Sur csrutil under a Catalina recovery partition so that the patched Big Sur installer can be created. We are going have to learn to tolerate the snapshots as part of the process.

 

[Larsvonhier]

Success on MB5,2 (or: as good as it can get atm)

Used @jackluke ´s method to switch to prelinked kernel boot, used his USB prelinked kernel first to boot.
Had some trouble initially due to kexts copied over from MB4,1 (IOSerialFamily etc.), so ended up with working USB but crashing near login...
In an attempt of not accepting the defeat, I booted into safe mode and that worked! Rebooted again (safemode, but single user to mount -rw)
Then corrected all kexts, copied over the specially patched MB5,2 (trackpad and some other) kexts from a working Catalina volume
and ran kextcache -i / and kcditto.

Result now: Fully working Wifi, trackpad (scrolling and fast mouse works) and audio output, 256MB framebuffer recognized for the 9400M.
Additional findings: Sound output to homepod works and brightness slider app also still runs on BS.

Here´s the link to my prelinked kernel for this machine / setup for anyone interested.

 

[kral84]

I have installes the kernel all working fine but when i mount -uw / it say failed 66.... have we any solution for this... i will install totalfinder...

 

[jackluke]

Success on MB5,2 (or: as good as it can get atm)

Used @jackluke ´s method to switch to prelinked kernel boot, used his USB prelinked kernel first to boot.
Had some trouble initially due to kexts copied over from MB4,1 (IOSerialFamily etc.), so ended up with working USB but crashing near login...
In an attempt of not accepting the defeat, I booted into safe mode and that worked! Rebooted again (safemode, but single user to mount -rw)
Then corrected all kexts, copied over the specially patched MB5,2 (trackpad and some other) kexts from a working Catalina volume
and ran kextcache -i / and kcditto.

Result now: Fully working Wifi, trackpad (scrolling and fast mouse works) and audio output, 256MB framebuffer recognized for the 9400M.
Additional findings: Sound output to homepod works and brightness slider app also still runs on BS.

Here´s the link to my prelinked kernel for this machine / setup for anyone interested.

View attachment 930862

View attachment 930863

For fixing Wifi on your MB4,1 I guess you need a very legacy IO80211Family.kext (the one embedded in my prelinkedkernel is from Mojave 10.14.5 ), same applies for AppleHDA.kext (the one I embedded is from 10.13.6 ) and IOUSB, I guess you need also very legacy IOUSB kext (that I don't included).

For any Nvidia chipset Mac if you use this ASentientBot method: https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-27468713

Ethernet works also on a BigSur unsupported non-metal, non-APFS, legacy usb mac, I attach my working kext from highsierra install.

 

[Larsvonhier]

Speaking of MB4,1:
First signs of Big Sur life...
(ignore the MBAir name in the status bar)

edit:
Got the framebuffer working for the x3100 GPU now, 144MB shared mem.
Smoother mouse movement and screen rendering!

edit2:
Wifi also up & running.

edit3:
Audio working now with HDA version 2.1.7

 

[indiawallah]

Don't know if this was just a problem that I had on my system or it was a general 'bug' on our unsupported Macs. If I clicked on any of the icons on the top right hand corner of the menu bar ( battery , wifi , notifications Siri ....it still crashes when I click on time though ) it would crash my system and take me back to sign in screen. I fixed this by going into System Preferences - Accessibility - and then setting reduce transparency and setting Menu Bar to large.

I have since noted when using Kext Droplet that when the process is complete I get a notification that is has done it's magic and get the pop up to reboot. Prior to finding this fix it would just crash back to the sign in screen. May not make that much difference to Kext being ' dropletted ' but just thought I would mention it.

 

[ammoune78]

Here is my IO80211Family kext version 12.0 if you wan to try it. Of course I'm using an Atheros card at the moment, all my MBPs have been upgraded to the BCM94360 from @troop231 i'll try a Mac mini once I get ahold of one.

Hey @highvoltage12v I've done the commands bellow but i've got and error with the last command here's the output, can you help please?

ammoune78@AirMac78s-iMac-Pro ~ % sudo mount -uw / ; killall Finder
Password:
ammoune78@AirMac78s-iMac-Pro ~ % sudo -s
root@AirMac78s-iMac-Pro ~ # chmod -R 755 /System/Library/Extensions/
root@AirMac78s-iMac-Pro ~ # chown -R 0:0 /System/Library/Extensions/
root@AirMac78s-iMac-Pro ~ # kextcache -i /
Executing: /usr/bin/kmutil install --volume-root / --check-rebuild
rebuilding local auxiliary collection
kmutil done
root@AirMac78s-iMac-Pro ~ # kmutil install --update-all
checking collections...
updated extension 'com.apple.iokit.IO80211Family' found on disk at '/System/Library/Extensions/IO80211Family.kext' (mach-o UUID changed from 99011013-0804-3EF6-B433-D33B216C05DB to EB3CF95B-714B-3A83-BDBC-E266AC5DD9DE)
updated extension 'com.apple.driver.AirPortBrcm43224' found on disk at '/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AppleAirPortBrcm43224.kext' (mach-o UUID changed from <unknown> to D50CC5CE-1632-314D-94B4-EB05D4B0178E)
updated extension 'com.apple.driver.IO80211NetBooter' found on disk at '/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/IO80211NetBooter.kext' (mach-o UUID changed from C0A664A0-F3F6-3C63-919F-B33AA52EC96A to D6F44D0F-7E37-3748-AEB7-8F43CD772318)
updated extension 'com.apple.driver.AirPort.Brcm4331' found on disk at '/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4331.kext' (mach-o UUID changed from <unknown> to B268EEFD-A0B8-340B-B9F5-B8F1A69ADFBB)
updated extension 'com.apple.driver.AirPort.Atheros40' found on disk at '/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortAtheros40.kext' (mach-o UUID changed from <unknown> to ABBC5EFD-7F18-30BE-A526-273DE99C1614)
updated extension 'com.apple.driver.CoreCaptureResponder' found on disk at '/System/Library/Extensions/CoreCaptureResponder.kext' (mach-o UUID changed from <unknown> to D04FEA18-A347-31F1-A04A-ED762DB9F0DE)
updated extension 'com.apple.driver.corecapture' found on disk at '/System/Library/Extensions/corecapture.kext' (mach-o UUID changed from 17974BCC-D7B0-352C-9B7C-11A5990F6FEA to 0B572B9E-F1D5-31B0-AB6B-E19630F5126C)
updated extension 'com.apple.driver.AirPort.Brcm4360' found on disk at '/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext' (mach-o UUID changed from <unknown> to A1B02848-0CC1-3630-8629-8163924DC663)
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.AppleBCMWLANBusInterfacePCIe' because: Failed to bind '__ZN15CCFaultReporter11reportFaultEjPKcjS1_P12OSDictionaryiS1_z' in 'com.apple.driver.AppleBCMWLANBusInterfacePCIe' (at offset 0x311dc in __TEXT, __text) as could not find a kext which exports this symbol
    Could not use 'com.apple.driver.AppleBluetoothDebug' because: Failed to bind '__ZNK13CCFaultReport18triggerCoreCaptureEP12CCDataStreamP5OSSetb' in 'com.apple.driver.AppleBluetoothDebug' (at offset 0x559c in __TEXT, __text) as could not find a kext which exports this symbol
    Could not use 'com.apple.iokit.IO80211FamilyV2' because: Failed to bind '__ZN15CCFaultReporter11reportFaultEjPKcjS1_P12OSDictionaryiS1_z' in 'com.apple.iokit.IO80211FamilyV2' (at offset 0xb7f8b in __TEXT, __text) as could not find a kext which exports this symbol
    Could not use 'com.apple.driver.AppleBCMWLANCore' because: Failed to bind '__ZN15CCFaultReporter11reportFaultEjPKcjS1_P12OSDictionaryiS1_z' in 'com.apple.driver.AppleBCMWLANCore' (at offset 0x144292 in __TEXT, __text) as could not find a kext which exports this symbol
    Could not use 'com.apple.driver.AppleMultiFunctionManager' because: Failed to bind '__ZN15CCFaultReporter11reportFaultEjPKcjS1_P12OSDictionaryiS1_z' in 'com.apple.driver.AppleMultiFunctionManager' (at offset 0x4d89 in __TEXT, __text) as could not find a kext which exports this symbol
    com.apple.driver.AppleBCMWLANCore:
        Failed to bind '__ZN15CCFaultReporter11reportFaultEjPKcjS1_P12OSDictionaryiS1_z' in 'com.apple.driver.AppleBCMWLANCore' (at offset 0x144292 in __TEXT, __text) as could not find a kext which exports this symbol
    com.apple.driver.AppleMultiFunctionManager:
        Failed to bind '__ZN15CCFaultReporter11reportFaultEjPKcjS1_P12OSDictionaryiS1_z' in 'com.apple.driver.AppleMultiFunctionManager' (at offset 0x4d89 in __TEXT, __text) as could not find a kext which exports this symbol
    com.apple.iokit.IO80211FamilyV2:
        Failed to bind '__ZN15CCFaultReporter11reportFaultEjPKcjS1_P12OSDictionaryiS1_z' in 'com.apple.iokit.IO80211FamilyV2' (at offset 0xb7f8b in __TEXT, __text) as could not find a kext which exports this symbol
    com.apple.driver.AppleBCMWLANBusInterfacePCIe:
        Failed to bind '__ZN15CCFaultReporter11reportFaultEjPKcjS1_P12OSDictionaryiS1_z' in 'com.apple.driver.AppleBCMWLANBusInterfacePCIe' (at offset 0x311dc in __TEXT, __text) as could not find a kext which exports this symbol
    com.apple.driver.AppleBluetoothDebug:
        Failed to bind '__ZNK13CCFaultReport18triggerCoreCaptureEP12CCDataStreamP5OSSetb' in 'com.apple.driver.AppleBluetoothDebug' (at offset 0x559c in __TEXT, __text) as could not find a kext which exports this symbol
failed to build any collections (expected: 1)
rebuilding local auxiliary collection
kmutil done

 

[Alex-Microsmeta]

Probably you already know but:

@ASentientBot @jackluke for not-metal macs maybe you can modify Nvidia Web drivers for High Sierra ... https://www.insanelymac.com/forum/t...es-for-macos-high-sierra-update-june-02-2020/

You can patch the installer for Mojave and maybe for Big Sur...

GitHub - Benjamin-Dobell/nvidia-update: Install nVidia drivers on macOS the easy way.

Install nVidia drivers on macOS the easy way. Contribute to Benjamin-Dobell/nvidia-update development by creating an account on GitHub.

github.com

Probably you already know but:

@ASentientBot @jackluke for not-metal macs maybe you can modify Nvidia Web drivers for High Sierra ... https://www.insanelymac.com/forum/t...es-for-macos-high-sierra-update-june-02-2020/

You can patch the installer for Mojave and maybe for Big Sur...

GitHub - Benjamin-Dobell/nvidia-update: Install nVidia drivers on macOS the easy way.

Install nVidia drivers on macOS the easy way. Contribute to Benjamin-Dobell/nvidia-update development by creating an account on GitHub.

github.com

I have patched last Nvidia web drivers for High Sierra to install on BS beta, package goes but returns an error when almost finished. Strangely graphic seem lighter now and mouse is fluid but the Nvidia Control Panel on System Preferences doesn't open. Maybe you skilled people may understand how to fix ?

 

[jhowarth]

Try this new prelinkedkernel that should fix for MacBook7,1 Wifi AirDrop and Ethernet (credit to ASentientBot for ethernet fix on Nvidia based Mac):

MacBook7,1 BigSur prelinkedkernel Wifi AirDrop and Ethernet fix beta1

replaced it here: /Volumes/UUID-BigSur/Preboot/System/Library/PrelinkedKernels/

Can you briefly describe exactly which kext you replaced in Big Sur to create the prelinkedkernel from...

legacy usb prelinkedkernel beta1

On my MacPro 3,1, with AppleHDA.kext and IO80211Family.kext removed from /System/Library/Extensions and Kext-droplet used to install...

LegacyUSBInjector.kext
LegacyUSBVideoSupport.kext
AppleHDA.kext 281.52
AppleIntelPIIXATA.kext

from those in the Catalina Patcher app and with...

IO80211Family.kext 1200.12.2

from Catalina 10.15.5 installed, booting under your prelinkedkernel works. However when I try to rebuild my own local copy of a prelinkedkernel with 'sudo kextcache -I /; sudo kcditto', that prelinked kernel reboots in the middle of the boot process.

When booted under your prelinkedkernel, I see that neither LegacyUSBInjector.kext nor LegacyUSBVideoSupport.kext appears to be loaded (which is the same behavior as under patched Catalina). The loaded AppleHDA.kext has the same 281.52 version. AppleIntelPIIXATA.kext is loaded and the DVD drive works. IO80211Family.kext is loaded and has the same 1200.12.2 version.

The size of my prelinkedkernel.bad, attached, is larger than...

legacy usb prelinkedkernel beta1
-rw-r--r--@ 1 howarth staff 19702112 Jul 5 06:54 prelinkedkernel

result from 'sudo kextcache -I /; sudo kcditto' for the above kexts
-rw-r--r-- 1 howarth staff 25749489 Jul 5 09:31 prelinkedkernel.bad

Dropbox link to download the problem prelinkedkernel (compressed).
prelinkedkernel.bad.zip

 

[jackluke]

Can you briefly describe exactly which kext you replaced in Big Sur to create the prelinkedkernel from...

legacy usb prelinkedkernel beta1

On my MacPro 3,1, with AppleHDA.kext and IO80211Family.kext removed from /System/Library/Extensions and Kext-droplet used to install...

LegacyUSBInjector.kext
LegacyUSBVideoSupport.kext
AppleHDA.kext 281.52
AppleIntelPIIXATA.kext

from those in the Catalina Patcher app and with...

IO80211Family.kext 1200.12.2

from Catalina 10.15.5 installed, booting under your prelinkedkernel works. However when I try to rebuild my own local copy of a prelinkedkernel with 'sudo kextcache -I /; sudo kcditto', that prelinked kernel reboots in the middle of the boot process.

When booted under your prelinkedkernel, I see that neither LegacyUSBInjector.kext nor LegacyUSBVideoSupport.kext appears to be loaded (which is the same behavior as under patched Catalina). The loaded AppleHDA.kext has the same 281.52 version. AppleIntelPIIXATA.kext is loaded and the DVD drive works. IO80211Family.kext is loaded and has the same 1200.12.2 version.

You can easily check if you are booting through my prelinkedkernel beta1, from a BigSur normal booting terminal:
kextstat | grep com.apple -v

If AAAMouSSE.kext and telemetrap.kext (credit to @Syncretic for those kext) are loaded then you are using my prelinkedkernel .

From system profiler extensions tab also @parrotgeek1 LegacyUSBInjector.kext is loaded but with "notarised: no".

I included also these kext: @highvoltage12v IO80211Family.kext and my HighSierra stock AppleHDA.kext .

Not sure if I rebuild kextcache from single user mode or normal booting, because during my earlier prelinkedkernel test for non-APFS mac needed to use CMD+S and "exit" to use legacy usb devices.

 

[jhowarth]

You can easily check if you are booting through my prelinkedkernel beta1, from a BigSur normal booting terminal:
kextstat | grep com.apple -v

If AAAMouSSE.kext and telemetrap.kext (credit to @Syncretic for those kext) are loaded then you are using my prelinkedkernel .

From system profiler extensions tab also @parrotgeek1 LegacyUSBInjector.kext is loaded but with "notarised: no".

I included also these kext: @highvoltage12v IO80211Family.kext and my HighSierra stock AppleHDA.kext .

Not sure if I rebuild kextcache from single user mode or normal booting, because during my earlier prelinkedkernel test for non-APFS mac needed to use CMD+S and "exit" to use legacy usb devices.

My bet is that the missing telemetrap.kext is the culprit. Can you post a download link for that kext so I can try adding it with Kext-droplet? It is surprising with so many hits for 'telemetrap.kext' on these boards that there are no download links.

ps I found a copy at telemetrap-0.22.zip. Is that the same one you are using?

 

[TimothyR734]

https://github.com/chris1111/Kext-Droplet-Big-Sur here is a link to Kext

 

[jhowarth]

You can easily check if you are booting through my prelinkedkernel beta1, from a BigSur normal booting terminal:
kextstat | grep com.apple -v

If AAAMouSSE.kext and telemetrap.kext (credit to @Syncretic for those kext) are loaded then you are using my prelinkedkernel .

From system profiler extensions tab also @parrotgeek1 LegacyUSBInjector.kext is loaded but with "notarised: no".

I included also these kext: @highvoltage12v IO80211Family.kext and my HighSierra stock AppleHDA.kext .

Not sure if I rebuild kextcache from single user mode or normal booting, because during my earlier prelinkedkernel test for non-APFS mac needed to use CMD+S and "exit" to use legacy usb devices.

Okay, I tried the following. On a normal apfs installation of Big Sur, I booted into single user mode and executed...

kextcache -i /
kcditto

The first thing I saw in single user mode was...

copying deferred prelinked kernels into /..

Then at the end of the kextcache build...

Failed to create directory /System/Library/Caches/com.apple.kext.caches - Read-only filesystem

Weirdly, the kcditto command in single user mode didn't install the caches which suggests that the prelinked kernels couldn't even be built (which was the case in a normal admin login).

Lastly, during the boot up from 'exit', I saw a lot of 'disk7s5s1 -device not readable' messages for a file system that looks like...

/dev/disk6 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *250.1 GB   disk6
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk6s1
   2:                 Apple_APFS ⁨Container disk7⁩         249.8 GB   disk6s2

/dev/disk7 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +249.8 GB   disk7
                                 Physical Store disk6s2
   1:                APFS Volume ⁨BigSur - Data⁩           13.1 GB    disk7s1
   2:                APFS Volume ⁨Preboot⁩                 315.4 MB   disk7s2
   3:                APFS Volume ⁨Recovery⁩                740.8 MB   disk7s3
   4:                APFS Volume ⁨VM⁩                      1.1 MB     disk7s4
   5:                APFS Volume ⁨BigSur⁩                  14.1 GB    disk7s5
   6:              APFS Snapshot ⁨com.apple.bless.A7DB...⁩ 14.1 GB    disk7s5s1

I'll explore next trying this...

mkdir /Users/howarth/mntpoint
sudo mount -o nobrowse -t apfs /dev/disk7s5 /Volumes/BigSur/Users/howarth/mntpoint
cd /Volumes/BigSur/Users/howarth/mntpoint/System/Library/Extensions
sudo kextcache -I /Volumes/BigSur/Users/howarth/mntpoint/
sudo kcditto
bless --folder /Volumes/BigSur/Users/howarth/mntpoint/System/Library/CoreServices --bootefi --create-snapshot

Update: That is likely a dead end as...

sudo kextcache -I /Volumes/BigSur/Users/howarth/mntpoint/

produces...

KernelCache ID: 0CFA9ECE9A2232F12F7F1F3F83A6C6C5
symlink("../../../PrelinkedKernels/prelinkedkernel", "/Volumes/BigSur/Users/howarth/mntpoint/Library/Apple/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 2 (No such file or directory)

 

[jackluke]

Okay, I tried the following. On a normal apfs installation of Big Sur, I booted into single user mode and executed...

kextcache -i /
kcditto

The first thing I saw in single user mode was...

copying deferred prelinked kernels into /..

Then at the end of the kextcache build...

Failed to create directory /System/Library/Caches/com.apple.kext.caches - Read-only filesystem

Weirdly, the kcditto command in single user mode didn't install the caches which suggests that the prelinked kernels couldn't even be built (which was the case in a normal admin login).

Lastly, during the boot up from 'exit', I saw a lot of 'disk7s5s1 -device not readable' messages for a file system that looks like...

/dev/disk6 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *250.1 GB   disk6
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk6s1
   2:                 Apple_APFS ⁨Container disk7⁩         249.8 GB   disk6s2

/dev/disk7 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +249.8 GB   disk7
                                 Physical Store disk6s2
   1:                APFS Volume ⁨BigSur - Data⁩           13.1 GB    disk7s1
   2:                APFS Volume ⁨Preboot⁩                 315.4 MB   disk7s2
   3:                APFS Volume ⁨Recovery⁩                740.8 MB   disk7s3
   4:                APFS Volume ⁨VM⁩                      1.1 MB     disk7s4
   5:                APFS Volume ⁨BigSur⁩                  14.1 GB    disk7s5
   6:              APFS Snapshot ⁨com.apple.bless.A7DB...⁩ 14.1 GB    disk7s5s1

I'll explore next trying this...

mkdir /Users/howarth/mntpoint
sudo mount -o nobrowse -t apfs /dev/disk7s5 /Volumes/BigSur/Users/howarth/mntpoint
cd /Volumes/BigSur/Users/howarth/mntpoint/System/Library/Extensions
sudo kextcache -I /Volumes/BigSur/Users/howarth/mntpoint/
sudo kcditto
bless --folder /Volumes/BigSur/Users/howarth/mntpoint/System/Library/CoreServices --bootefi --create-snapshot

telemetrap.kext 0.22 is the version I used, as I already told I have an untethered, unsealed, non-snapshot BigSur, and I don't know how delete snapshots on an non-APFS (or legacy USB) Mac, I make these prelinkedkernel from different machines.

Anyway if you use the ASentientBot Hax3.dylib and install BigSur directly from Catalina desktop on your MacPro but on internal SATA disk, this should work to disable BigSur snapshots and use "sudo mount -uw /" from normal booting or single user mode.

Here is the link: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28619108

You need an "Install macOS Beta.app" BigSur stock (9,58 GB), and copy it in Catalina /Applications/ , then run the ASentientBot Hax3.app to install it on your internal SATA disk.