macOS 11 Big Sur on Unsupported Macs Thread

[Alex-Microsmeta]

@Badruzeus on the other "non-mac hardware" forums are there any fixes for AppleACPICPU early kernel panic for booting the USB BigSur Installer (or installation) when using IntelHD Arrandale (or Arrandale i5 cpu) and i3 Clarkdale cpu ?

Because these Intel architecture are unable to boot the BigSur beta1 kernel , probably they need some DSDT fix.

I made many attempts but can't figure it out, unless AAPL on BigSur beta 2 fixes this kp.

I have used your OpenCoreLoader3 togheter with parrotgeek1 patcher 1.3, but with same results of ASentientBot patcher. I have also resetted NVRAM (after this I can boot BS volume only using your loader) and removed telemetry. There is something at the end of the installation that causes a crash and a reboot on Penryn Core 2 duo P8600 2.4 ghz, before opening the first BS configuration panel. I'm searching a specific patch with a fix for this CPU on Macmini 2010 (Macmini4,1) NOTE: I can almost complete the installation only using bluetooth Apple original keyboard and mouse, maybe the crash is due to the USB or other kexts missing. With next beta I will try to patch also the BootKernelExtensions.kc , LegacyUSBInjector.kext
and do the other fixes that you have suggested. Thank you very much for your support!

 

[jackluke]

I have used your OpenCoreLoader3 togheter with parrotgeek1 patcher 1.3, but with same results of ASentientBot patcher. I have also resetted NVRAM (after this I can boot BS volume only using your loader) and removed telemetry. There is something at the end of the installation that causes a crash and a reboot on Penryn Core 2 duo P8600 2.4 ghz, before opening the first BS configuration panel. I'm searching a specific patch with a fix for this CPU on Macmini 2010 (Macmini4,1) NOTE: I can almost complete the installation only using bluetooth Apple original keyboard and mouse, maybe the crash is due to the USB or other kexts missing. With next beta I will try to patch also the BootKernelExtensions.kc , LegacyUSBInjector.kext
and do the other fixes that you have suggested. Thank you very much for your support!

To properly use the USBOpenCoreAPFSLoader3, you should apply these fixes: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28631825

Copy this file BigSur prelinkedkernel fix.zip also in this path:

/Volumes/Preboot/UUID-BigSur/Library/Preferences/SystemConfiguration/

 

[Larsvonhier]

just found something out any other application that asks for camera or microphone access doesn't appear on big sur
system preferences

You can still use the tccplus tool to set those privacy per terminal command.

 

[jackluke]

I just wrote two scripts to automatically apply my prelinkedkernel fix to a BigSur installation:

1) "BigSur prelinkedkernel fix.command" is for those who want to use the prelinkedkernel instead of BootKernelExtensions.kc (even on Metal GPU mac it will work)

2) "BigSur prelinkedkernel fix2.command" is mainly for those who want to fix telemetry kp and legacy usb (maybe also sound and wifi) without using opencore, or for those who use USBOpenCoreAPFSloader3 (needed for non-APFS mac)

Both the script can be launched from Finder with double click (hold ctrl and open to allow unidentified developer) through a Catalina normal booting, HighSierra, Mojave (the macOS that can use APFS containers in few words), even directly from BigSur .

edit:

added "BigSur prelinkedkernel fix3.command" for any non-APFS and legacy USB Mac (works also without opencore)

 

[Larsvonhier]

I just wrote two scripts to automatically apply my prelinkedkernel fix to a BigSur installation:

1) "BigSur prelinkedkernel fix.command" is for those who want to use the prelinkedkernel instead of BootKernelExtensions.kc (even on Metal GPU mac it will work)

2) "BigSur prelinkedkernel fix2.command" is mainly for those who want to fix telemetry kp and legacy usb (maybe also sound and wifi) without using opencore, or for those who use USBOpenCoreAPFSloader3 (needed for non-APFS mac)

Both the script can be launched from Finder with double click (hold ctrl and open to allow unidentified developer) through a Catalina normal booting, HighSierra, Mojave (the macOS that can use APFS containers in few words), even directly from BigSur .

E X C E L L E N T !!
Thanks for sharing.

 

[jackluke]

To those who have multiple separated APFS containers, just before running the BigSur prelinkedkernel fix command script run this:

diskutil unmount Preboot diskutil list | grep "Preboot"

And mount the largest "MegaBytes" Preboot Volume: diskutil mount diskXsY

 

[Alex-Microsmeta]

I just wrote two scripts to automatically apply my prelinkedkernel fix to a BigSur installation:

1) "BigSur prelinkedkernel fix.command" is for those who want to use the prelinkedkernel instead of BootKernelExtensions.kc (even on Metal GPU mac it will work)

2) "BigSur prelinkedkernel fix2.command" is mainly for those who want to fix telemetry kp and legacy usb (maybe also sound and wifi) without using opencore, or for those who use USBOpenCoreAPFSloader3 (needed for non-APFS mac)

Both the script can be launched from Finder with double click (hold ctrl and open to allow unidentified developer) through a Catalina normal booting, HighSierra, Mojave (the macOS that can use APFS containers in few words), even directly from BigSur .

OK, this good news deserves a 7th trial on macOS Beta 1 ? I must reinstall BigSur because after last changes BS Volume is locked or unaccessible. I will use BigSur name instead of Big Sur, hoping that for your scripts will be the same, my Italian keyboard make terminal commands a real challenge!

 

[nitinnk]

sorry, can anyone tell me why these settings cannot be changed? also if you go to many advanced sections of system preferences, open an empty pop-up or open nothing. Could it be because it is still the first beta or installed on an unsupported macbook pro?

 

[Alex-Microsmeta]

OK, this good news deserves a 7th trial on macOS Beta 1 ? I must reinstall BigSur because after last changes BS Volume is locked or unaccessible. I will use BigSur name instead of Big Sur, hoping that for your scripts will be the same, my Italian keyboard make terminal commands a real challenge!

Just started 7th installation: Parrotgeek1 patched macOS beta selected from your OpenCoreLoader (this time separate volumes) target volume is an external USB 145 Gb hardisk APFS volume named BigSur . PS: if you relaunch a second time USBOpenCore loader INSTALLER from macOS, It cannot create the loader due to an already existing /private/tmp file that I have manually removed.

 

[johncaling40]

I just wrote two scripts to automatically apply my prelinkedkernel fix to a BigSur installation:

1) "BigSur prelinkedkernel fix.command" is for those who want to use the prelinkedkernel instead of BootKernelExtensions.kc (even on Metal GPU mac it will work)

2) "BigSur prelinkedkernel fix2.command" is mainly for those who want to fix telemetry kp and legacy usb (maybe also sound and wifi) without using opencore, or for those who use USBOpenCoreAPFSloader3 (needed for non-APFS mac)

Both the script can be launched from Finder with double click (hold ctrl and open to allow unidentified developer) through a Catalina normal booting, HighSierra, Mojave (the macOS that can use APFS containers in few words), even directly from BigSur .

What exactly is prelinkedkernel. I have not been keeping up with this thread for quite a few days because i got busy with other things. Also how would i use it?

 

[jackluke]

What exactly is prelinkedkernel. I have not been keeping up with this thread for quite a few days because i got busy with other things. Also how would i use it?

It's the kernelcache that apple used till Catalina to load the kernel and its base kext, on which machine you intend to use it?

Because I build many BigSur patched prelinkedkernel beta 1 for different group of machines.

 

[Minh_Ton]

Does kmutil works in single user mode (booting from a USB installer not from a Big Sur install)?

 

[jackluke]

To those who have an external USB BigSur installation (or internal disk) on non-APFS Mac or Mac with legacy USB, and after used my fixes still don't have responsive usb input output devices (keyboard, mouse, trackpad and so on) there are two possible way to fix:

1) After alt-option key apple startup manager, target your BigSur volume hold CMD+S to boot single user mode, then type "exit" to boot BigSur

For those who use USBOpenCore, try the same, boot with opencore then target the BigSur volume with CMD+S, type "exit" to continue booting

2) I can provide a new patched prelinkedkernel that this time should work for any non-APFS or legacy USB Mac

 

[Barry K. Nathan]

Does kmutil works in single user mode (booting from a USB installer not from a Big Sur install)?

Yes, kmutil works when booted from the USB installer. (So does kcditto, although it might work a bit differently than you would expect if you haven't carefully read the kcditto man page.)

On a related note, I just released version 0.0.6 of my patcher, which now includes a shell script that can install the WiFi kexts if you're booted from the USB installer. (I do want to see if I can meke the kext installer script more robust for the next release, maybe this weekend or early next week, but I think it's still reasonably robust as it is.)

Edit: I forgot to mention, my patcher doesn't do anything involving legacy USB (yet), so for machines that need legacy USB, it's still too immature.

GitHub - barrykn/big-sur-micropatcher: A primitive USB patcher for installing macOS Big Sur on unsupported Macs

A primitive USB patcher for installing macOS Big Sur on unsupported Macs - barrykn/big-sur-micropatcher

github.com

 

[johncaling40]

It's the kernelcache that apple used till Catalina to load the kernel and its base kext, on which machine you intend to use it?

Because I build many BigSur patched prelinkedkernel beta 1 for different group of machines.

I want to use on macBook Pro 8,1. So will it fix some issues like sound and display?

 

[Alex-Microsmeta]

@jackluke you are a GENIUS (a true Genius not like Apple help desk boys ?)

@dosdude1 Success in installing on Macmini 2010 (Macmini4,1) using @parrotgeek1 @ASentientBot and @jackluke USBOpenCoreLoader and last fixes !!! More soon...

 

[jackluke]

@jackluke you are a GENIUS (a true Genius not like Apple help desk boys ?)

@dosdude1 Success in installing on Macmini 2010 (Macmini4,1) using @parrotgeek1 @ASentientBot and @jackluke USBOpenCoreLoader and last fixes !!! More soon...

I am far light years away from a genius, now through usbopencore you can boot also from Recovery 10.16 (dmg) or Recovery Beta, to attempt fixing Sound and Wifi try to use the "bigsur prelinkedkernel fix2" that includes a patched prelinkedkernel.

Some tips: from a non-metal BigSur avoid to click the Finder upper right icons (they log-out due to CoreDisplay or SkyLight crash), rather use the System Preferences to manage Network and any other settings, instead the Finder top menu is working correctly, also avoid to open any document or picture files with Preview.app that is very slow in rendering the apple animations.

If you have an USB (or bluetooth) external speaker it could work to enable audio on your mac, ethernet I guess requires also a kext patch that ASentientBot found for Catalina: https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-27468713

Maybe I'll include "nvenet.kext" in the next opencore version.

 

[hvds]

To those who have multiple separated APFS containers, just before running the BigSur prelinkedkernel fix command script run this:

diskutil unmount Preboot diskutil list | grep "Preboot"

And mount the largest "MegaBytes" Preboot Volume: diskutil mount diskXsY

Big Sur 10.16.0 DB1 running on external (USB) ssd of my MBP5,2 (mid 2009, a machine with Legacy USB), now including wifi. Writing this from BS.

BS was installed using ASentientBot's Hax3.app with the disk on internal (SATA) connection, as necessary for such machines at present. Then moved the disk to USB, where all other changes were made. Catalina as production system on internal ssd. Booting BS always with OpenCore loader.

Wifi works after applying jackluke's two scripts from post #1329, after mounting the right Preboot as described in #1331. This done from Catalina. So I'm using the prelinkedkernel already enhanced by jackluke for legacy USB, wifi, ...

That work is really excellent as Larsvonhier said. Installing and booting BS is already quite automated in this early phase. Big thanks to jackluke and ASentientBot!

(MBP5,2 17" mid 2009, 2.8GHz Penryn T9600, Nvidia 9600M GT, 8GB, APFS ROM patch applied. APFS SSD Samsung 860 EVO for production / 840 for testing, with Catalina 10.15.5.02 / Big Sur 10.16.0 DB1, resp.)

 

[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.

I 've been busy last day so sorry for my late...thank you, I will try this tomorrow.

I would expect the Kext-Droplet to work for 3rd party kexts in general, but not for replacing Apple's own. It's definitely not going to work for IO80211Family or AppleHDA. It's not so much that it doesn't work on unsupported Macs as it simply does things the wrong way for the kinds of kext installations we unsupported Mac users generally need.

Edit to clarify: I wouldn't be surprised if the Kext Droplet works for adding a driver for USB WiFi, but I don't think it'll work for any of the internal devices that Apple dropped in Mojave/Catalina/Big Sur. (I'll have a lot more to say soon, probably in the next few days, about this topic of kext installation.)

The reason it won't work is that there are 2 kexts, one is in /System//Library/Extensions, and another one in /Library/Extensions, the one in /System/Library/Extensions is newer and/or is the default, I am 100% sure a kext would load if there's no kext with the same name in /System/Library/Extensions.

 

[Alex-Microsmeta]

I am far light years away from a genius, now through usbopencore you can boot also from Recovery 10.16 (dmg) or Recovery Beta, to attempt fixing Sound and Wifi try to use the "bigsur prelinkedkernel fix2" that includes a patched prelinkedkernel.

Some tips: from a non-metal BigSur avoid to click the Finder upper right icons (they log-out due to CoreDisplay or SkyLight crash), rather use the System Preferences to manage Network and any other settings, instead the Finder top menu is working correctly, also avoid to open any document or picture files with Preview.app that is very slow in rendering the apple animations.

If you have an USB (or bluetooth) external speaker it could work to enable audio on your mac, ethernet I guess requires also a kext patch that ASentientBot found for Catalina: https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-27468713

Maybe I'll include "nvenet.kext" in the next opencore version.

Sounds work from bluetooth speakers (like Windows 10 2004 on same Mac mini 2010 )
Yes I noticed the bug on top right icons, trying to configure BS to connect to my Pixel Experience Android 10 Redmi Note 5 Hotspot , since wifi and acceleration must still be fixed. First thing to do: a clone of BigSure as backup, but Catalina Disk Utility now crashes for the BigSur container, so I'm trying using the macOS Recovery.

Thank you again, it's only the first step, but I'm in the game

 

[jackluke]

Sounds work from bluetooth speakers (like Windows 10 2004 on same Mac mini 2010 )
Yes I noticed the bug on top right icons, trying to configure BS to connect to my Pixel Experience Android 10 Redmi Note 5 Hotspot , since wifi and acceleration must still be fixed. First thing to do: a clone of BigSure as backup, but Catalina Disk Utility now crashes for the BigSur container, so I'm trying using the macOS Recovery.

Thank you again, it's only the first step, but I'm in the game

If from BigSur normal booting terminal you can't use "sudo mount -uw /" , then I guess you can clone BigSur only from its BigSur Recovery DiskUtility (or USB BigSur Installer), because BigSur System or any diskutil on its container is locked (or sealed) from Catalina or previous macOS apfs driver.

In my case I still have (after five installation) a weird "untethered" BigSur install (even with csrutil authenticated-root enable, I posted many pictures), I can use "sudo mount -uw /" and also mount its System volume "writeable" from HighSierra, probably because I erased the APFS container from there.

 

[hvds]

Big Sur 10.16.0 DB1 running on external (USB) ssd of my MBP5,2 (mid 2009, a machine with Legacy USB), now including wifi. Writing this from BS.

BS was installed using ASentientBot's Hax3.app with the disk on internal (SATA) connection, as necessary for such machines at present. Then moved the disk to USB, where all other changes were made. Catalina as production system on internal ssd. Booting BS always with OpenCore loader.

Wifi works after applying jackluke's two scripts from post #1329, after mounting the right Preboot as described in #1331. This done from Catalina. So I'm using the prelinkedkernel already enhanced by jackluke for legacy USB, wifi, ...

That work is really excellent as Larsvonhier said. Installing and booting BS is already quite automated in this early phase. Big thanks to jackluke and ASentientBot!

(MBP5,2 17" mid 2009, 2.8GHz Penryn T9600, Nvidia 9600M GT, 8GB, APFS ROM patch applied. APFS SSD Samsung 860 EVO for production / 840 for testing, with Catalina 10.15.5.02 / Big Sur 10.16.0 DB1, resp.)

...just to add that while internal audio isn't working yet, I have a bluetooth headset connected, and it works (listening to Dylan's latest album). I don't do entertainment often with my Mac, but that must be celebrated.

 

[jackluke]

I 've been busy last day so sorry for my late...thank you, I will try this tomorrow.




The reason it won't work is that there are 2 kexts, one is in /System//Library/Extensions, and another one in /Library/Extensions, the one in /System/Library/Extensions is newer and/or is the default, I am 100% sure a kext would load if there's no kext with the same name in /System/Library/Extensions.

When you copy or install any kext in /Library/Extensions/ (that is its Data Volume not the sealed System) the kernelcache for them is stored on /Library/KernelCollections/AuxiliaryKernelExtensions.kc
(that is the BigSur - Data Volume unlocked, unsealed, writeable)

Instead using the prelinkedkernel they are stored in one file.

 

[jhowarth]

I just wrote two scripts to automatically apply my prelinkedkernel fix to a BigSur installation:

1) "BigSur prelinkedkernel fix.command" is for those who want to use the prelinkedkernel instead of BootKernelExtensions.kc (even on Metal GPU mac it will work)

2) "BigSur prelinkedkernel fix2.command" is mainly for those who want to fix telemetry kp and legacy usb (maybe also sound and wifi) without using opencore, or for those who use USBOpenCoreAPFSloader3 (needed for non-APFS mac)

Both the script can be launched from Finder with double click (hold ctrl and open to allow unidentified developer) through a Catalina normal booting, HighSierra, Mojave (the macOS that can use APFS containers in few words), even directly from BigSur .

If you want to use the "BigSur prelinkedkernel fix2.command" option, do you have to run the "BigSur prelinkedkernel fix.command" first?

 

[Alex-Microsmeta]

I am far light years away from a genius, now through usbopencore you can boot also from Recovery 10.16 (dmg) or Recovery Beta, to attempt fixing Sound and Wifi try to use the "bigsur prelinkedkernel fix2" that includes a patched prelinkedkernel.

Some tips: from a non-metal BigSur avoid to click the Finder upper right icons (they log-out due to CoreDisplay or SkyLight crash), rather use the System Preferences to manage Network and any other settings, instead the Finder top menu is working correctly, also avoid to open any document or picture files with Preview.app that is very slow in rendering the apple animations.

If you have an USB (or bluetooth) external speaker it could work to enable audio on your mac, ethernet I guess requires also a kext patch that ASentientBot found for Catalina: https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-27468713

Maybe I'll include "nvenet.kext" in the next opencore version.

Ok, I have made a backup image of the BS container on an external USB "black box" called "Jackluke Patchers" ? with macOS 16 Recovery in 15 minutes (no more a crepy 4 hours installation) so now I can do experiments with all kekts.
[automerge]1593724633[/automerge]