macOS 11 Big Sur on Unsupported Macs Thread

[jackluke]

- running the following from 10.15.6. csr and boot-args already set
- downloaded 11.0 beta3 from link given in post #...., to /Applications
- installed via Hax3.app to BS beta2 disk (has to be on SATA for legacy USB machine during installation)
Thats it - boots via OpenCore. Next do new prelinkedkernel fix.

Having a Catalina installation is advisable and required for legacy USB Mac and any patching also because "Install macOS Big Sur Beta.app" requires Catalina (from Mojave doesn't worked).

After prelinkedkernel beta3 Penryn fix you can boot also without opencore (and from external USB disk), probably you just need to set csrutil disable and -no_compat_check .

I'd suggest to try this: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28701959

because if works you can use "sudo mount -uw /" and make your modification on BigSur system.

For a smoother graphics is required the Nvidia GeForce Tesla framebuffer, but I can't prelink those kext (even with NDRVShim), I mean NVDAResmanTesla is not loaded.

 

[TimothyR734]

Still no wifi or ethernet working after reinstall BS Beta 3 I think the volume has to be unsealed for BarryKn's patch-kexts.sh to work as I either get /Volumes\ is a directory or file or directory not found. And I noticed if you open the terminal type sudo -s then hit enter then type sudo mount -uw /; killall Finder does work without error 66 but because the volume is sealed and read-only you can't replace the IO80211Family.kext

 

[eksu]

After trying (and failing) to get my Mac to run the Beta 2 -> 3 incremental installer, my cMP has gotten into a state where it can't launch any non-apple applications, with an error saying "The application "_____" can't be opened, -1".

I am going to do a fresh install of beta 3 and restore from my Time Machine backup, but not sure what happened. Some applications give me an error log afterwards, and I can see that they say the code signing is invalid.

Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace CODESIGNING, Code 0x1

 

[ricoc90]

Still no wifi or ethernet working after reinstall BS Beta 3 I think the volume has to be unsealed for BarryKn's patch-kexts.sh to work as I either get /Volumes\ is a directory or file or directory not found. And I noticed if you open the terminal type sudo -s then hit enter then type sudo mount -uw /; killall Finder does work without error 66 but because the volume is sealed and read-only you can't replace the IO80211Family.kext

Create a USB installer of you don't have one already. Then boot into your installer, fire up terminal and mount your Big Sur volume using mount -uw /Volumes/volume_name where volume_name is the name of your Big Sur volume.

 

[hvds]

Having a Catalina installation is advisable and required for legacy USB Mac and any patching also because "Install macOS Big Sur Beta.app" requires Catalina (from Mojave doesn't worked).

After prelinkedkernel beta3 Penryn fix you can boot also without opencore (and from external USB disk), probably you just need to set csrutil disable and -no_compat_check .

I'd suggest to try this: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28701959

because if works you can use "sudo mount -uw /" and make your modification on BigSur system.

For a smoother graphics is required the Nvidia GeForce Tesla framebuffer, but I can't prelink those kext (even with NDRVShim), I mean NVDAResmanTesla is not loaded.

Successfully applied your new prelinkedkernel fix for beta3 for Penryn, working from 10.15.6.
- 11.0 beta3 now boots without OpenCore
- WLAN (and Ethernet as before) works.

Small tests with beta3 show that
- Photos still crashes (new version 6.0 (301.0.112)) as before, after transforming media library.

I might try the internal audio fix tomorrow, following your suggestion.

 

[Alex-Microsmeta]

For Penryn Core2Duo and non-APFS or legacy USB Mac my prelinkedkernel fix 1 2 3 4 doesn't work more on Beta 3 so don't use them

I am updating a new prelinkedkernel for those machines will publish later here editing this post.

Uh, I noticed that just now post-installing BS beta3, thank you

 

[Alex-Microsmeta]

Here is attached the new BigSur beta 3 prelinkedkernel fix for any Penryn Core2Duo included the non-APFS and legacy USB Mac, also Ethernet and Wifi should work.

You might also need this to preset a reduced transparency (to skip the non-metal loginUI Finder crash):
BigSur reducetransparency fix.command.zip

While if you want to disable the prelinkedkernel (if doesn't work) and return to the stock BigSur BootKernelExtensions just use this: BigSur generic BKE.command.zip

Hi @jackluke I have executed the command, but it doesn't patch my Preboot (mounted as requested) and I think that the correct one is disk2s1 (internal SSD) not the bigger Preboot. Where I'm wrong? Thank you!

 

[jhowarth]

Having a Catalina installation is advisable and required for legacy USB Mac and any patching also because "Install macOS Big Sur Beta.app" requires Catalina (from Mojave doesn't worked).

After prelinkedkernel beta3 Penryn fix you can boot also without opencore (and from external USB disk), probably you just need to set csrutil disable and -no_compat_check .

I'd suggest to try this: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28701959

because if works you can use "sudo mount -uw /" and make your modification on BigSur system.

For a smoother graphics is required the Nvidia GeForce Tesla framebuffer, but I can't prelink those kext (even with NDRVShim), I mean NVDAResmanTesla is not loaded.

So what is the state of the art for getting legacy usb support added once the snapshot is removed and 'sudo mount -uw /' works? Should I install LegacyUSBInjector.kext or patch IOUSBFamily.kext? Also does this now allow kc's to be built or should I use 'sudo kextcache -i /' to rebuild a prelinked kernel? If kc's work, what is the best command to use after the legacy usb kext support is added to build and install the kc?

 

[cpharada1]

Installed Big Sur Beta 3 with parrotgeek tool on iMac 14,1 without any issues.

 

[DeathBase]

Installed Big Sur Beta 3 with parrotgeek tool on iMac 14,1 without any issues.

View attachment 936823

From scratch or update??

 

[cpharada1]

From scratch or update??

Update from Beta 2

 

[DeathBase]

Update from Beta 2

Did you follow the steps from https://github.com/barrykn/big-sur-micropatcher or https://parrotgeek.com/bigsur/ to update??

 

[Joonyv]

I'm trying to update from my Catalina partition but on the Big Sur installer it only show my Catalina partition, not the one with Big Sur beta 2. This did not happen when updating from beta 1 to 2.
Help please.

 

[cpharada1]

Did you follow the steps from https://github.com/barrykn/big-sur-micropatcher or https://parrotgeek.com/bigsur/ to update??

Parrotgeek version only

 

[jhowarth]

Just updated my late 2012 Mac mini to beta 3. As expected no working WiFi after installation but just like Beta 2 all I had to do was to boot into the USB installer, mount the Big Sur volume with write access, copy over High Sierra's IO80211Family.kext and run the following commands:

kmutil install --volume-root /Volumes/volume_name --update-all --force

/Volumes/volume_name/usr/sbin/kcditto

bless --folder /Volumes/volume_name/System/Library/CoreServices --bootefi --create-snapshot

Edit: Note that I'm still using @ASentientBot's hax to prevent sealing of the volume.

View attachment 936555

I am puzzled how your instructions might interact with the proposed mechanism to remove a snapshot...

macOS 11 Big Sur on Unsupported Macs Thread

Hello, few notes about BigSur beta 3 now the BaseSystem.dmg is 884 MB (beta 2 was 740 MB), also from single user mode they introduced two new commands to easily mount the Data and Preboot Volume (both Volumes writable from single user mode even with a sealed system snapshot booting): mount -P 1...

forums.macrumors.com

Specifically, I am planning on installing beta 3 on a supported machine and use jackluke's instructions to remove the snapshot so that 'sudo mount -uw /' works under Big Sur. Then while still booted from a supported machine, I intend to install LegacyUSBInjector.kext and telemetrap.kext so that either a prelinked kernel or kc could be generated and installed for moving that external usb drive over to a MacPro 3,1 for booting. Won't your instruction to execute....

bless --folder /Volumes/volume_name/System/Library/CoreServices --bootefi --create-snapshot

recreate the pruned snapshot and then require me to use jakeluke's method to prune it away again?

 

[TimothyR734]

Hi @jackluke I have executed the command, but it doesn't patch my Preboot (mounted as requested) and I think that the correct one is disk2s1 (internal SSD) not the bigger Preboot. Where I'm wrong? Thank you!

I have tried but mine only show the bigger one and small one and tried both no luck

 

[ricoc90]

I am puzzled how your instructions might interact with the proposed mechanism to remove a snapshot...

macOS 11 Big Sur on Unsupported Macs Thread

Hello, few notes about BigSur beta 3 now the BaseSystem.dmg is 884 MB (beta 2 was 740 MB), also from single user mode they introduced two new commands to easily mount the Data and Preboot Volume (both Volumes writable from single user mode even with a sealed system snapshot booting): mount -P 1...

forums.macrumors.com

Specifically, I am planning on installing beta 3 on a supported machine and use jackluke's instructions to remove the snapshot so that 'sudo mount -uw /' works under Big Sur. Then while still booted from a supported machine, I intend to install LegacyUSBInjector.kext and telemetrap.kext so that either a prelinked kernel or kc could be generated and installed for moving that external usb drive over to a MacPro 3,1 for booting. Won't your instruction to execute....

bless --folder /Volumes/volume_name/System/Library/CoreServices --bootefi --create-snapshot

recreate the pruned snapshot and then require me to use jakeluke's method to prune it away again?

It will. It seems that when you're disabling sealing of the APFS volume, which I do, you won't be able to remove snapshots (calling apfs_systemsnapshot will error out with "operation not permitted"). That's why I am using the method as shown. If you have snapshots completely disabled you'll be able to edit the system files directly from / so then there's no need to run that last command.

 

[jhowarth]

It will. It seems that when you're disabling sealing of the APFS volume, which I do, you won't be able to remove snapshots. That's why I am using the method as shown. If you have snapshots completely disabled you'll be able to edit the system files directly from / so then there's no need to run that last command.

Any idea how to disable sealing on a normal Big Sur installation where you have used jackluke's method to prune off the snapshot? Is there some installed plist on the system volume that needs edited to do this after installation?

 

[ricoc90]

Any idea how to disable sealing on a normal Big Sur installation where you have used jackluke's method to prune off the snapshot? Is there some installed plist on the system volume that needs edited to do this after installation?

AFAIK you can't "just" disable the sealing of the APFS volume AFTER installation. However, disabling snapshots altogether will accomplish the same thing I guess. Once snapshots are disabled you'll boot directly off of the Big Sur volume and you'll be able to mount the root volume with write access and edit the system files directly.

 

[jhowarth]

AFAIK you can't "just" disable the sealing of the APFS volume AFTER installation. However, disabling snapshots altogether will accomplish the same thing I guess. Once snapshots are disabled you'll boot directly off of the Big Sur volume and you'll be able to mount the root volume with write access and edit the system files directly.

So if you prune of the snapshot and can directly use 'sudo mount -uw /', would that mean just using...

kmutil install --volume-root /Volumes/volume_name --update-all --force
/Volumes/volume_name/usr/sbin/kcditto
bless --folder /Volumes/volume_name/System/Library/CoreServices --bootefi

and leaving the --create-snapshot off of the bless command?

 

[TimothyR734]

Create a USB installer of you don't have one already. Then boot into your installer, fire up terminal and mount your Big Sur volume using mount -uw /Volumes/volume_name where volume_name is the name of your Big Sur volume.

That doesn’t work remember in the Big Sur usb the terminal uses bash so zsh commands don’t work and I have altered those lines and still doesn’t and say my ssd doesn’t exist

 

[DeathBase]

As a thank you and documentation, once again, I followed all Barry's "Patcher" steps and updated my MBP 9.2 of Beta 2 to Beta 3 without issues as usual

Thank you @Barry K. Nathan and the others involved

 

[ricoc90]

So if you prune of the snapshot and can directly use 'sudo mount -uw /', would that mean just using...

kmutil install --volume-root /Volumes/volume_name --update-all --force
/Volumes/volume_name/usr/sbin/kcditto
bless --folder /Volumes/volume_name/System/Library/CoreServices --bootefi

and leaving the --create-snapshot off of the bless command?

No, omiting the bless completely.

Only run kmutil and kcditto:

kmutil install --update-all
kcditto

Check this comment by jackluke:

macOS 11 Big Sur on Unsupported Macs Thread

For enabling Wifi 802.11n on any 2012 Mac or any other unsupported Big Sur but supported Catalina Mac (in few words those who use the AirPortBrcm4360 driver), this will work: https://forums.macrumors.com/threads/macos-11-big-sur-on-unsupported-macs-thread.2242172/post-28595200 To install it...

forums.macrumors.com

 

[thielsa]

I did a full update to from Beta 2 to Beta 3 using the Parrotgeek instructions on my MacPro 5.1 . Used my timemachime backup to restore. Worked really well.

 

[ricoc90]

That doesn’t work remember in the Big Sur usb the terminal uses bash so zsh commands don’t work and I have altered those lines and still doesn’t and say my ssd doesn’t exist

That ain't a zsh specific command. It's what that command always has been

mount -uw /Volumes/volume_name

Or find your disk first using diskutil, then mount it using diskutil

diskutil list
diskutil mount /dev/diskxsx

where both x's are corresponding to your disk and volume number.

Then run

mount -uw /Volumes/volume_name

If your volume name contains spaces backslash them or put them in quatation marks. E.g. in my case the command would be

mount -uw /Volumes/macOS\ 11

or

mount -uw "/Volumes/macOS 11"