midwestgerma.blogg.se - Kelk 2010 patcher v3

#Kelk 2010 patcher v3 update#
#Kelk 2010 patcher v3 Patch#
#Kelk 2010 patcher v3 code#
#Kelk 2010 patcher v3 mac#

The end result is that, on Late 2013 iMacs, SIP and ARV stay enabled the entire time during and after the installation process, just like on a supported Mac. The trampoline has been updated to leave APFS volume sealing enabled if both SIP and ARV are enabled.

#Kelk 2010 patcher v3 mac#

install-setvars.sh has been updated to automatically use the new variants on Late 2013 iMacs, but there are also command line options for overriding the Mac model detection. There are new variants of the setvars EFI program which enable, rather than disable, SIP and ARV (authenticated-root). Remount-sysvol.sh and rebuild-kc.sh have been updated with all of the applicable patch-kexts.sh bug fixes from this release and the last several releases, so they now work again. If patch-kexts.sh is run on a system volume snapshot, it now mounts the underlying volume at /System/Volumes/Update/mnt1, just like Apple's own delta updaters. Eventually I will document it, but future patcher releases may change the option's name or other implementation details first.

This option is currently not documented in the README.

#Kelk 2010 patcher v3 Patch#

This can help with troubleshooting problems with kext patches, especially during patch development.

Patch-kexts.sh also adds a -old-kmutil option that uses the kmutil from Big Sur beta 8 instead of the one that is installed on the system. It defaults to -wifi=mojave-hybrid (the one that has been used from v0.2.1 onward), but -wifi=hv12v-old (used in micropatcher v0.0.6-v0.0.20) and -wifi=hv12v-new (used in micropatcher v0.1.0-v0.2.0) are also available. Patch-kexts.sh now has a -wifi= option for choosing a WiFi kext patch. (Thanks to jackluke for reporting the bug.) Also, there is a new -force option to override the check. Patch-kexts.sh has an improved check for SIP/ARV that is less prone to false negatives.

#Kelk 2010 patcher v3 code#

Thanks to Ausdauersportler for the code contribution. At this time, the -iMac and -2011 command line options must be used together, and the -iMac option only works when running patch-kexts.sh on a live Big Sur installation, not when booted from the installer USB. Patch-kexts.sh now has a new -iMac command line option that adds the necessary kext patches for (2011) iMacs which have been upgraded with Metal GPUs.

#Kelk 2010 patcher v3 update#

When it is time to update to the next Big Sur build, make sure not to skip steps 7 or 9, especially on Late 2013 iMacs. Most existing users do not urgently need the improvements or bug fixes in this release and can wait until the next Big Sur beta (or GM) before updating. There are many changes in this release, mostly small changes I suppose, but different changes will be very important to different groups of users.

LegacyUSBInjector.kext has been updated to account for a USB-related kernel change that happened in Big Sur beta 3.

(As a side effect, LegacyUSBInjector.kext may no longer work properly on beta 4-9.

A patch-kexts.sh bug has been fixed that could, under some circumstances, cause kernel panics during boot on Big Sur beta 10 (and probably subsequent releases) on 2011 or earlier Macs.

In the process, error checking was improved considerably and several minor bugs were fixed.

patch-kexts.sh has undergone some code refactoring.

(My implementation of this feature is not 100% identical, but it is highly similar and based on Ausdauersportler's.)

Thanks to Ausdauersportler for creating the initial implementation of this feature.

patch-kexts.sh now automatically detects whether the Mac has an 802.11ac WiFi card and, if so, skips installation of the WiFi patch.

As a neat effect of the increased code reuse, kext unpatching no longer requires booting from the installer USB first. This way, the unpatching can now reuse as much of the patching code as possible.

unpatch-kexts.sh has been replaced by a -u option for patch-kexts.sh.

If you have already installed Big Sur successfully using a previous version of Big Sur Micropatcher, you do not need to update immediately, but I would suggest updating the patcher before upgrading to any future Big Sur betas or releases.