macOS 11 Big Sur on Unsupported Macs Thread

[minman]

Right, it was the BKE incompatible with different machines, it should be the stock BigSur one (66,7 MB currently), after the prelinkedkernel fix, do you have also AirDrop on BigSur Finder, and does Sound (Internal Speakers) and Mic (maybe try Siri also) are working ?
[automerge]1594129464[/automerge]


Could you check also if you have AirDrop on the BigSur Finder ?

Or from About This Mac, System Report, Wifi tab if the AirPortDriverBrcm4360 driver loaded and AirDrop channel is correctly detected.

yes everything works fine thank you

 

[Rastafabi]

[…] if restart my iMac with Catalina there are these problems:
1) Catalina immediately tells me that there is an unsupported hard drive.
2) A disc named "Update" appears on the Desktop.
3) If I open Disk Utility, Disk Utility crashes.

[…]

As you can see, moreover, if enable the complete list of devices in Disk Utility I get duplicates!!!

1: This can be expected as BigSur made some changes to how it handles APFS and thus also requires an update for Catalina. Nothing to worry about.
2: This disk is created for the new, faster BigSur update mechanics which works in the background. Catalina just does not know how do deal with it, yet (hide).
3: Presumably a symptom of 1.

Of course you get duplicates. This never has been different on Fusion drives. All associated disk get a virtual chunk of the shared partitions.

 

[jackluke]

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'd advise to use my latest prelinkedkernel fix: BigSur IvyBridge prelinkedkernel Sound AirDrop fix beta1.command.zip

because with that Wifi card you can use a more recent AirPortBrcm4360 driver and mainly enable the AirDrop channel.

 

[OKonnel]

I confirm. It also crashes my Catalina Disk Utility while opening (immediatly after trying to reorder containers, it closes) Works fine on Big Sur. @jackluke I bet you will fix that, too.
PS: Have you acceleration with Nvidia?

Good question Alex-Microsmeta!
I just tried with a medical software.
* I opened a very heavy CT skull scan;
* I put the image in 3D;
* I activated the GPU function (instead of CPU);
* I chose 16 Bit (instead of 8 Bit);
* I set details and shadows to maximum definition
Result:
activating the GPU the 3D image rotates perfectly, smoothly, even with the Zoom at maximum.
The density regulator and all controls work smoothly and better than Catalina.

P.S. If I open Word of Office 365 without installing Office, but directly from macOS Catalina -> Macintosh HD/Applications/, Word opens and it runs instantly. Literally it flies! Photoshop 21.2.0 too works directly and flies from /Applications/ folder of Catalina's volume, without the need for a full installation in Big Sur!

 

[jackluke]

I confirm. It also crashes my Catalina Disk Utility while opening (immediatly after trying to reorder containers, it closes) Works fine on Big Sur. @jackluke I bet you will fix that, too.

PS: Have you acceleration with Nvidia?

I can mount the BigSur APFS System and any volume from HighSierra, but I did a weird install through OTA Installer patching the distribution file, then erased the BigSur APFS through HighSierra DiskUtility, but I guess on the next BigSur beta 2, I also encounter this new BigSur encrypted sealed system snapshot booting.

About Nvidia I still can't get NVDAResmanTesla.kext loaded , so I don't have a proper Framebuffer, but I repeat the fact that Frameworks binaries are not in their folders, makes very hard to achieve some minimal OpenGL or non-metal acceleration.

 

[Maclinux]

That's weird you still don't have sound speakers on an Ivy Bridge Mac, because both Sound and Mic worked either with BigSur AppleHDA.kext or HighSierra one, I'd exclude that FileVault could block it, because you are using a patched IO80211Family.kext in the prelinkedkernel.

If you open the Sound prefpane from "Sound effect" tab can't you select as output device "Internal Speakers" ?

Try to unplug your external "t24d-10" I guess it's an HDMI monitor (and any other plugged digital audio devices), and reboot without it, and check if Internal Speakers are detected.

If still doesn't work then try this from a BigSur terminal: kmutil install --update-all

Otherwise you should try to disable FileVault, then do a PRAM reset, and check if Internal Speakers are detected, because BigSur AppleHDA.kext works for any Ivy Bridge Mac.

I have disconnected the HDMI (effectively a monitor) and reboot, but still no option appears for internal speakers. Curiously, the headphones with jack work perfectly.

The Terminal returns an error when writing the code (attached image)

Nice to see it work well everything else thank you thank you thank you

🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗

 

[jackluke]

I have disconnected the HDMI (effectively a monitor) and reboot, but still no option appears for internal speakers. Curiously, the headphones with jack work perfectly.

The Terminal returns an error when writing the code (attached image)

Nice to see it work well everything else thank you thank you thank you

🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗🤗

I know some cases that when you plug a splitter or any combo headphone-microphone 3.5 mm jack with more than two contacts, example the TRRS with four contacts, this could switch the input as a digital input output signal (a red led from the 3.5mm jack should notice), so you should plug and unplug a 3.5mm jack that turns it to an analog signal and output for internal speakers, I'd suggest to reset PRAM, but before that disable FileVault .

 

[Maclinux]

I know some cases that when you plug a splitter or any combo headphone-microphone 3.5 mm jack with more than two contacts, example the TRRS with four contacts, this could switch the input as a digital input output signal (a red led from the 3.5mm jack should notice), so you should plug and unplug a 3.5mm jack that turns it to an analog signal and output for internal speakers, I'd suggest to reset PRAM, but before that disable FileVault .

Putting the headphone jack on and off repeatedly has fixed the problem!!!!

When I went to put the headphones on the jack, I saw that there was a red light on the connector that did not seem usual. I plugged and unplugged the jack a couple of times and it worked correctly. Everything works correctly for me in MBPro 9.2

Now for Beta 2!!!!! 😜

Thank you very much for the help!!
😊😊😊😊

 

[ammoune78]

@jackluke Hey, thanks mate it worked, and wifi was enabled on my Mac Pro 5,1.
After that successful, I've completely reinstalled the Big Sur from USB, but I don't know what I did to the config file of OpenCore, then the USB installer no longer enable R/W on the System partition again. I've tried OC 0.5.9, 0.6.0 old and New 0.6.0 build by myself with no success. Each time when the USB installer reboots to begin the Installation on the Preboot Installer the Mac shut down and the USB can't boot anymore from OC, I've to re bless it from another macOS drive, and makes the reboot installer no longer shown on OC bootPicker. But if with I don't know for what reason the Big Sur install successfully, the System drive no longer writable from the earlier commands nor from the USB installer itself. If you have a OC EFI folder to share, please I'll be grateful.

 

[jackluke]

@jackluke Hey, thanks mate it worked, and wifi was enabled on my Mac Pro 5,1.
After that successful, I've completely reinstalled the Big Sur from USB, but I don't know what I did to the config file of OpenCore, then the USB installer no longer enable R/W on the System partition again. I've tried OC 0.5.9, 0.6.0 old and New 0.6.0 build by myself with no success. Each time when the USB installer reboots to begin the Installation on the Preboot Installer the Mac shut down and the USB can't boot anymore from OC, I've to re bless it from another macOS drive, and makes the reboot installer no longer shown on OC bootPicker. But if with I don't know for what reason the Big Sur install successfully, the System drive no longer writable from the earlier commands nor from the USB installer itself. If you have a OC EFI folder to share, please I'll be grateful.

The prelinkedkernel fixes that I am uploading are intended to use without opencore, because opencore currently is unable to manage the BootKernelExtensions and to disable the new "csrutil authenticated-root", if you can't R/W the BigSur System it's because it has decided to install in that sealed snapshot way.

Type mount, if you have a Volume with diskXsYsZ , then you have a sealed snapshot booting.

It's not a config.plist issue, so you instead could try this from any OpenCore menu, press space bar to show the macOS Recovery dmg, then select: 10.16 Recovery (dmg) or Recovery Beta (you can use also an USB BigSur Installer with apple createinstallmedia), then from BigSur Recovery terminal: csrutil authenticated-root disable

If you can't use more "sudo mount -uw /" from BigSur then as workaround to get Wifi try this: BigSur IvyBridge prelinkedkernel Sound AirDrop fix beta1.command.zip

 

[ammoune78]

The prelinkedkernel fixes that I am uploading are intended to use without opencore, because opencore currently is unable to manage the BootKernelExtensions and to disable the new "csrutil authenticated-root", if you can't R/W the BigSur System it's because it has decided to install in that sealed snapshot way.

Type mount, if you have a Volume with diskXsYsZ , then you have a sealed snapshot booting.

It's not a config.plist issue, so you instead could try this from any OpenCore menu, press space bar to show the macOS Recovery dmg, then select: 10.16 Recovery (dmg) or Recovery Beta (you can use also an USB BigSur Installer with apple createinstallmedia), then from BigSur Recovery terminal: csrutil authenticated-root disable

If you can't use more "sudo mount -uw /" from BigSur then as workaround to get Wifi try this: BigSur IvyBridge prelinkedkernel Sound AirDrop fix beta1.command.zip

I'll try that, but yesterday, I've installed it 4 times, the two first times I was able to use the sudo mount -uw / ; killall Finder command, like the screenshot of yesterday, but from the two last times and today I no longer able to do it I always get the ..... -66 error message.
The csrutil status is disabled also the csrutil authenticated-root is disabled to.
With OC 0.6.0 the newest build there's two ways in the NVRAM section which allows to boot the System Drive or the USB installer as follow:
booter-fileset-kernel=>Data:00 "for Big Sur System Drive"
booter-fileset-basesystem=>Data:00 "for USB installer"

 

[jhowarth]

I'll try that, but yesterday, I've installed it 4 times, the two first times I was able to use the sudo mount -uw / ; killall Finder command, like the screenshot of yesterday, but from the two last times and today I no longer able to do it I always get the ..... -66 error message.
The csrutil status is disabled also the csrutil authenticated-root is disabled to.
With OC 0.6.0 the newest build there's two ways in the NVRAM section which allows to boot the System Drive or the USB installer as follow:
booter-fileset-kernel=>Data:00 "for Big Sur System Drive"
booter-fileset-basesystem=>Data:00 "for USB installer"

My understanding is that if a snapshot exists for APFS filesystem, it will block 'sudo mount -uw /' from working. The approach that I am testing is...

mkdir /Users/howarth/mntpoint
sudo mount -o nobrowse -t apfs /dev/disk7s5 /Volumes/BigSur/Users/howarth/mntpoint
sudo chroot /Volumes/BigSur/Users/howarth/mntpoint mount -uw /
sudo chroot /Volumes/BigSur/Users/howarth/mntpoint kextcache -i /
cd /Volumes/BigSur/Users/howarth/mntpoint/System/Library/PrelinkedKernels
sudo cp /Volumes/BigSur/Users/howarth/mntpoint/Library/Apple/System/Library/PrelinkedKernels/prelinkedkernel prelinkedkernel
sudo cp /Volumes/BigSur/Users/howarth/mntpoint/Library/Apple/System/Library/PrelinkedKernels/prelinkedkernel immutablekernel
cd ~
sudo bless --folder /Volumes/BigSur/Users/howarth/mntpoint/System/Library/CoreServices --bootefi --create-snapshot
**** reboot ****
sudo kcditto
**** reboot under newly installed prelinked kernel ****

Note that this assumes that you have already installed any legacy copies of kext that you need into /Library/Extensions either manually or with Kext-droplet. Note that if you have to downgrade AppleHDA.kext or IO80211Family.kext to older copies, you can use the same approach to remove the Big Sur copies in /System/Library/Extensions.

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
cd ~
sudo bless --folder /Volumes/BigSur/Users/howarth/mntpoint/System/Library/CoreServices --bootefi --create-snapshot
**** reboot to use the modified snapshot ****

Finally, the disk7s5 should be replaced by whatever your mounted root snapshot is (disk7s5s1 in my case) with the trailing 's1' dropped off. If you are using LegacyUSBInjector.kext and ', you might try...

sudo chroot /Volumes/BigSur/Users/howarth/mntpoint kextcache -prelinked-kernel /Library/Apple/System/Library/PrelinkedKernels/prelinkedkernel -kernel /System/Library/Kernels/kernel -local-root -- /Library/Extensions/ /System/Library/Extensions/ /System/Library/Extensions/LegacyUSBInjector.kext

in addition to the previous

sudo chroot /Volumes/BigSur/Users/howarth/mntpoint kextcache -i /

I am convinced this is working except for the LegacyUSBInjector.kext which hopefully one of those above changes has addressed.

 

[dpamping]

I am waiting to install the beta on my Mac because I don't know how I can update then to the next beta, if its possible to update directly with the update option in system preferences or if you have to do it manually.

Beta 2 is here. Please let me know how is the update progress.

Thanks

 

[webg3]

Apple releases second developer beta of macOS 11 Big Sur with new interface and icons, more - 9to5Mac

Apple has released the second developer beta of macOS 11 Big Sur. The release of macOS Big Sur beta 2 comes two weeks after it was debuted at WWDC 2020

9to5mac.com

 

[Helghast59]

No update in system settings on Air 2012, any solutions?

 

[webg3]

No update in system settings on Air 2012, any solutions?

Download Beta Profiles

Download latest beta profiles for iOS, iPadOS, macOS, watchOS and tvOS.

betaprofiles.com

not even installing it, it doesn't appear here either.

MacBook Air 11" 2012

 

[DeathBase]

No update in system settings on Air 2012, any solutions?

Same here, MBP mid 2012.

 

[jackluke]

@jhowarth or @webg3 can you upload this file in zip archive:

/System/Library/LaunchDaemons/com.apple.softwareupdated.plist

 

[sinbad21]

@jhowarth or @webg3 can you upload this file in zip archive:

/System/Library/LaunchDaemons/com.apple.softwareupdated.plist

Here is mine (MBP mid 2012)

 

[webg3]

Can anyone capture the link for us like beta1?

[automerge]1594144671[/automerge]

@jhowarth or @webg3 can you upload this file in zip archive:

/System/Library/LaunchDaemons/com.apple.softwareupdated.plist

 

[dpamping]

Can anyone capture the link for us like beta1?

View attachment 931522

Are you updating via System preferences directly? If its that case, in what model?

 

[Alex-Microsmeta]

There we are

 

[justperry]

No update in system settings on Air 2012, any solutions?

Same for a 2012 Mac Mini.

 

[jackluke]

Can anyone capture the link for us like beta1?

View attachment 931522
[automerge]1594144671[/automerge]

If that is the download size means that apple is still delivering a full installer rather than an OTA update, for Catalina if I don't get wrong they started to deliver after beta 3 an incremental OTA update.

This should be the link: http://swcdn.apple.com/content/down...xje070in5dorjoovnmw61x03/InstallAssistant.pkg

After downloaded and unpackaged check in some Contents/Info.plist that the build number is higher than 20A4299v , because I can't download it for now, have low space on small partitions, and want to keep this BigSur beta 1 unsealed with "mount -uw /" working even from HighSierra.

Also for those who attempt the prelinkedkernel fix (that are for beta1) they could work too on beta2 but keep another macOS for example Catalina as internal or external bootable device, in that way you can easily fix it (without reinstalling) and use again the stock BigSur beta 2 BootKernelExtensions.kc .

 

[Fangio]

I'd advise to use my latest prelinkedkernel fix: BigSur IvyBridge prelinkedkernel Sound AirDrop fix beta1.command.zip

because with that Wifi card you can use a more recent AirPortBrcm4360 driver and mainly enable the AirDrop channel.

Thanks for the heads-up, works like a charm. 👍

I've executed this 'BigSur IvyBridge prelinkedkernel Sound AirDrop fix beta1.command' in a Mojave Terminal again, booted back to the Big Sur partition and now the AirPortBrcm4360 is used.