This is why Apple is not wise to invest in - cook is destroying the Mac with a toy OS. Mac OS is nothing but a toy with iOS, a snow Leopard Big Sur will NEVER be !
Do you know if a Big Sur patcher is being developed/worked on at the moment?Waiting eagerly for the patcher with my Early 2011 17" Macbook Pro (faulty radeon gpu desoldered and bypassed, intel graphics only)
it's likely that they will re-add support for the late 2013 iMacs
There is no AVX requirement!!!
View attachment 926185
View attachment 926186
All that is necessary to reach the desktop is installing with my method, then deleting the Telemetry plugin (thanks again @jackluke, that's three years now!) and it boots to the desktop. No accel, of course... that will be the real challenge.
But there is still hope
Lets not be a Debbie Downer some of us like out Mac's and like the challenge of getting macOS running on unsupported MacsAnd.. there is one more thing - another 2nd wave of COVID19 May wipe out Apple and further delay everything - in the Fall they are predicting a 2nd wave which will be far worse than this one.
You need to install on a host that officially support macOS Big Sur. Doing that right now. Will see whether I can transplant the resulting VM to a non supporting 5,1.
Thanks for this! I at least have hd3000 Airport and HDAudio working now, IOSurface was able to remain stock, no replacement needed. Going to test sleep now.Hey! I figured out kext loading and got the nVidia Tesla framebuffer (including brightness and sleep) working. The annoying part is it doesn't work in single-user mode sincekmutil
has to talk to some daemon...
Code:sudo mount -uw / # copy in the kexts as usual, unchanged from Catalina chown -R root:wheel /System/Library/Extensions chmod -R 755 /System/Library/Extensions sudo kmutil install --update-all # other than this command, it's basically the same sudo kcditto
Now time to work on real acceleration.
sudo /Applications/Install\ macOS\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/BigSurInstaller/
OK I've downloaded the "Install macOS Beta.app" through CatalinaOTAswufix , inspecting the package:
Contents/SharedSupport/SharedSupport.dmg
9,56 gb
mounting the SharedSupport.dmg (skipping the verifying it's too big), it contains a new structure
one main folder: com_apple_MobileAsset_MacSoftwareUpdate
(this name suggests that it has many things in common with iPadOS)
the folder contains some plist and xml, and mainly a big zip file 9,55 gb with a long string file name (as an iOS update).
The installer is still in HFS macOS Extended
to make the "BigSur" installer as usual using a 16 gb USB drive label it BigSurInstaller , open a Catalina (or Mojave) terminal:
Code:sudo /Applications/Install\ macOS\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/BigSurInstaller/
I making this because I use OpenCore.
Instead to load and install it "from Catalina desktop", as @ASentientBot explained, launch his new patch, then double click the Install macOS Beta.app , and install "Big Sur" on another empty volume.
The thing that is confusing me is how to use it. I have the patch downloaded but i cant work my head around it
nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1"
csrutil disable
reboot
Try booting from a recovery environment or USB Catalina Patcher, open a recovery terminal and type this:
Code:nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1" csrutil disable reboot
If I haven't misinterpreted Microsoft's disclosure of Windows 10 for ARM, it is capable of natively running 32- and 64-bit Windows applications for ARM and, in addition, it can also run 32-bit Windows applications for Intel by emulating Intel's architecture. If this is true, then Boot Camp should be able to go on running normally on Apple Silicon, provided Windows itself is the ARM flavor.The whole reason people run bootcamp is to run Windows applications and nearly all Windows Applications are not written for Intel... so it makes bootcamp nearly pointless.
After i do that what do i do
I remember reading about kmutil as a replacement for kextcache, possibly in the known issues page. I'm still installing so don't have a man entry for it to investigate.
I am exploring the installer now. It looks like the actual install file is in /Volumes/Shared\ Support/com_apple_MobileAsset_MacSoftwareUpdate/0dc2cd535db0da2a9f559215671686ea4c055394.zip, which is a modified .ipa file. I'm trying to extract and install it manually now
Edit: Also, it needs over 50 gigs to do a clean install. I'm assuming it extracts the .zip to a temp location (~10gb), builds an installer package from the pbzx compressed payload (~10gb) then actually executes the staged installer (~10gb), which puts the files on disk (~20gb). So at the moment it looks like a hybrid macOS/iOS installer. The boot process for basesystem.dmg is completely different too - they've hardened and signed rc.cdrom, and it no longer creates ramdisks
You’re right! It’s an image of an APFS container, minimally containing a System and a Preboot volume. Previous is about 160, which accounts for the increase in sizeTry to boot the USB "Big Sur" Installer, otherwise use the ASentientBot method to open and launch directly from Catalina desktop the "Install macOS Beta.app" but first you should run his dylib patch: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28589245
[automerge]1592897840[/automerge]
From what I am aware Ramdisk aka "Big Sur" /BaseSystem/BaseSystem.dmg is still there, its size now is 740 MB (while previously on Catalina 500 MB)
the main difference is that "Big Sur" BaseSystem.dmg now is an APFS Installer volume (no more an HFS macOS Extended)