For those that use them Safari extensions seem to be working again in Big Sur as I have enabled Pocket which wasn't working for me in Catalina.
This may sound stupid but, as stated in step 3, where exactly is located "home folder"? Thanks in advance
The little home with your name next to it is the home folder
This may sound stupid but, as stated in step 3, where exactly is located "home folder"? Thanks in advance
I booted via OpenCore USB…and I have WiFi now! This is before I was going to try your Terminal commands.Try this from BigSur normal booting, open terminal:
Code:mount use "mount" detect the root mount point of your BigSur System (snapshot) example a generic "diskXsYsZ" "sZ" is a "locked snapshot" (from where you are booting) so you don't write it in next command sudo mount -o nobrowse -t apfs /dev/diskXsY /Volumes/AnyDiskLabel/AnyEmptyFolder/ AnyDiskLabel is an already mounted disk on your Mac AnyEmptyFolder is an empty folder that you make on that disk your non-snapshot System mounted diskXsY should have this mount point: /Volumes/AnyDiskLabel/BigSurLabel/ (AnyEmptyFolder is your BigSurLabel after used as mount point) then replace your kext here: /Volumes/AnyDiskLabel/BigSurLabel/System/Library/Extensions/ (chown and chmod the kext before replace) after you replaced, if you used the prelinkedkernel method you should use this: kextcache -i / ; kcditto then make a new bootable snapshot with embedded patched kext: bless --folder /Volumes/AnyDiskLabel/BigSurLabel/System/Library/CoreServices --bootefi --create-snapshot
Thank you for your response. It’s so right on that I can’t believe it hadn’t occurred to me. Looking forward to installing this once all of the incredible work here is ironed out.Just wait and WiFi will probably be fixed. If not get a USB wireless adapter. I wouldn’t tear apart an iMac for the wireless card.
Protect your health, here in Italy the situation finally is better, use face masks everywhere against Covid19 !Happy 4th of July be safe everyone
Possibly macOS Big Sur-PriseDate configuration options are disabled on my installation. Another Big Sur bug?
We need to call all Big Sur bugs that.Possibly macOS Big Sur-Prise
By BUG Sur? ?Possibly macOS Big Sur-Prise
Got WiFi working on my 2012 MacBook Pro 9,1 by just running 'BigSur prelinkedkernel fix1+2.commands' in a Mojave Terminal. Booted back to the Big Sur partition and bingo. Great job as usual @jackluke, thanks a lot.
I booted via OpenCore USB…and I have WiFi now! This is before I was going to try your Terminal commands.
It will not boot via default Apple boot picker anymore though – it will crash at start.
WiFi must be working because of your prelinkedkernel file. I still have to fix speakers/mic, display brightness control, graphics acceleration. Everything seems to working as expected
except for menu bar clock which all settings are greyed out for, and if I am logged out if you click the time.
I usually enable 24hr clock & show date in settings.
View attachment 930443
I am trying your commands, but I don't want to mess up WiFi now that it works, not even sure how it works – but it works. I think I may have misunderstood any disk, any folder etc…
View attachment 930442
IntelHD4000 has Metal acceleration on BigSur, maybe do you reduced the transparency ?
Because in my prelinkedkernel I guess are included stock metal drivers, otherwise I could make another prelinkedkernel with Metal IntelHD4000 drivers, also those machines can use the stock BigSur AppleHDA .
Good eye, yes I had 'Reduce Transparency' turned on earlier to see how it looks (not so good imho) and forgot about that when I tried your scripts yesterday. Just turned it off again, Transparency is back in menu bar and dock.IntelHD4000 has Metal acceleration on BigSur, maybe do you reduced the transparency ?
Because in my prelinkedkernel I guess are included stock metal drivers, otherwise I could make another prelinkedkernel with Metal IntelHD4000 drivers, also those machines can use the stock BigSur AppleHDA.
That alternative patched prelinked kernel (which is smaller than the other) doesn't provide functional usb injection. It boots up to the dialog asking to find a bluetooth keyboard because of that issue.
Well, on MB4,1 we have the same (technically forced) situation due to x3100 GPU for years. Also the debate about it (here) is as old as we got Mojave running on it - that´s why @0403979 included support for the machine in his patcher as @dosdude1 did not have it in his list of machines. With help from his side even the APFS Rom patch can be made on the MB4,1 (without the NVidia chipset risk of screwing up).
There´s also a completely OS-agnostic way to set/reset SIP:To use properly my patched prelinkedkernel , SIP needs to be properly disabled with "csrutil disable" (non-APFS Mac can surely do this through the El Capitan firmware) from a Recovery environment (I do this with USBopencore), while "csrutil authenticated-root disable" is not mandatory (even if useful), but the classic SIP must be disabled (and I guess AMFI too) otherwise the patched kext embedded in the prelinkedkernel cannot override the BigSur Extensions as AppleHDA and IO80211Family .
Thanks for the link. I will look into it.I have the same iMac and got WiFi working following this tutorial: macOS Big Sur Installation + WiFi on unsupported macs
It wasn't properly made so I removed it, about my patched prelinkedkernel, I guess I figure out why the IO80211Family.kext in prelinkedkernel worked for many and doesn't for some, and why AppleHDA.kext doesn't worked for many:
The IO80211Family.kext contains Plugins that are mainly (there also others in previous macOS) AirPortBrcm4331, AirPortBrcm4360 and AirPortBrcmNIC driver, in my prelinkedkernel I can embed only one Plugin (because from the target machine where I build it, Plugins not used are ignored).
AirPortBrcm4331 supports many legacy Wifi Broadcom cards (it also fits for some recent Broadcom cards), AirPortBrcm4360 supports many "Catalina supported Mac" Wifi cards ;
AirPortBrcmNIC supports all the "BigSur supported Mac" or Broadcom Wifi ac cards (they dropped the Wifi n).
I can't embed in my prelinkedkernel the stock AirPortBrcmNIC because I don't have any machine with such recent Broadcom Wifi cards (maybe I could make another prelinkedkernel for AirPortBrcm4360 instead).
The Wifi kext can override a BigSur stock Wifi driver because it contains only the Plugin AirPortBrcmNIC, so any other previous Plugin are correctly added from the prelinkedkernel.
Instead About AppleHDA.kext to make it working the prelinkedkernel needs to find a kext matching mach-o UUID on your BigSur System Volume at /System/Library/Extensions/
so anyone should replace the stock BigSur AppleHDA.kext with an HighSierra one.
Replacing AppleHDA.kext seems to be the rub as there appears to be some non-deterministic behavior on whether a kext installed in LE or even the one embedded in a prelinked kernel always wins out against those in SLE despite having a hacked boot.efi.
I suspect that the only real fix will be to get authenticated-root disabled on the unsupported machine so that the competing kext in SLE can be replaced with one from an earlier macOS release. I took a stab at using the prelinked kernel with legacy usb support, that works on a MacPro 3,1 under Big Sur, to replace the one on a Big Sur install usb stick. Unfortunately, when it boots, I get animated mouse, etc graphics indicating that a keyboard couldn't be found preventing me from using the Terminal there to set 'csrutil authenticated-root disable'.
Also, has anyone actually disabled authenticated-root on an unsupported machine? That is, are we sure that disabling that doesn't require some enhancements only presenting in the most recent upgraded boot roms from Apple.