Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 11 Big Sur on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
-
- Tags
- 10.16 macos unsupported
- Sort by reaction score
- Status
or it's possible the software update is checking if you hardware it's in the compatibility list
That is...if Software Update actually fetches the Update, it doesn't on my Mac Mini.
I think this is the problem, see screenshot below, before BS it always said you were on the Dev beta program, now it says managed externally, so, I think they check the model, my Mac Mini is unsupported.
Last edited:
You are awesome!)) Thanks.Install macOS Beta.app.zip
drive.google.com
Install macOS Beta.app.zip
Is that beta 2
Not yet, also CatalinaOTAswufix (based on SUVMMFaker.dylib) doesn't worked, but I guess spoofing with OpenCore to a supported Mac surely will work, but for now is not necessary just use the direct link provided.
Install macOS Beta.app.zip
Do we have to redo the previous instructions to fix Wi-Fi on rMBP `12?
Where is the link? Did I miss it? Sorry!. So to install beta 2, we must go through the same entire process used for beta1?
Shows that update cannot be installed on this Mac - Mac mini Late 2012
I've done the installation again without any issue, but, I just want to notice that
Upon the second restart back from the installation process, on the OC menu it shows only Preboot Installer:
- If I start from it and let if finish and reboot it, while it takes longer, it screws up the System drive so no possible -uw / mounting
- Now if I start from it but this time I interrupt it after 5 min in average, which it doesn't create the prelinkedkernel in the mount point which is supposed to be diskxsxsx, it let me -uw / mounting the System drive. This is my understanding on what I've done these two past days and today.
Now the WiFi is working, good to go without wires, and here's the result of that command:
Code:
Last login: Tue Jul 7 18:26:29 on console
ammoune78@AirMac78s-Mac-Pro ~ % sudo mount -uw / ; killall Finder
Password:
ammoune78@AirMac78s-Mac-Pro ~ % sudo -s
root@AirMac78s-Mac-Pro ~ # chmod -R 755 /System/Library/Extensions/
root@AirMac78s-Mac-Pro ~ # chown -R 0:0 /System/Library/Extensions
root@AirMac78s-Mac-Pro ~ # kextcache -i /
Executing: /usr/bin/kmutil install --volume-root / --check-rebuild
rebuilding local auxiliary collection
kmutil done
root@AirMac78s-Mac-Pro ~ # Kmutil install -—update-all
Error: Missing value for '-a <arch>'
Usage: kmutil install [--variant-suffix <variant-suffix>] [--arch <arch>] [--no-authorization] [--verbose] [--repository <repository> ...] [--volume-root <volume-root>] [--check-rebuild] [--update-all] [--force] [--authentication] [--no-authentication] [--update-preboot]
root@AirMac78s-Mac-Pro ~ # Kmutil install --update-all
checking collections...
updated extension 'com.apple.driver.AirPort.BrcmNIC' found on disk at '/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcmNIC.kext' (mach-o UUID changed from 1BFF3E8B-77F0-3C4B-A6C1-9DF06132B189 to 0F1637EA-51B0-3A81-9433-956A19427984)
updated extension 'com.apple.driver.AirPort.Brcm4360' found on disk at '/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext' (mach-o UUID changed from <unknown> to 8DE38A76-B284-34D2-AF4E-DB727D7FF250)
updated extension 'com.apple.driver.AirPort.Atheros40' found on disk at '/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortAtheros40.kext' (mach-o UUID changed from <unknown> to 9753F22E-5C85-3E95-B543-0870CF03838A)
updated extension 'com.apple.iokit.IO80211Family' found on disk at '/System/Library/Extensions/IO80211Family.kext' (mach-o UUID changed from 99011013-0804-3EF6-B433-D33B216C05DB to A879B51A-4562-3B95-B6C3-A2472B508F2F)
updated extension 'com.apple.driver.IO80211NetBooter' found on disk at '/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/IO80211NetBooter.kext' (mach-o UUID changed from C0A664A0-F3F6-3C63-919F-B33AA52EC96A to 22A50E20-A024-3B8D-9268-B69ECBA918A0)
updated extension 'com.apple.driver.AirPort.Brcm4331' found on disk at '/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4331.kext' (mach-o UUID changed from <unknown> to D4559F1A-005E-353C-B33F-3006C349EE5D)
rebuilding release collections: boot, system
rebuilding release collections:
boot kernel collection
system kext collection
rebuilding local auxiliary collection
kmutil done
root@AirMac78s-Mac-Pro ~ # kcditto
Copying deferred prelinked kernels in /...
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-685/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
Folder
), NSUnderlyingError=0x7fd11940f5f0 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/kext_tools/kext_tools-685/kc_staging.m.279: Encountered error while inspecting path: Error Domain=NSCocoaErrorDomain Code=260 "The folder “PrelinkedKernels” doesn’t exist." UserInfo={NSFilePath=/Library/Apple/System/Library/PrelinkedKernels, NSUserStringVariant=(
Folder
), NSUnderlyingError=0x7fd119412cc0 {Error Domain=NSOSStatusErrorDomain Code=-43 "fnfErr: File not found"}}
Copying KCs in /...
System Volume UUID: CE926A4D-369A-4779-ADB5-DBC0C1E82BD8
Volume Group UUID: E35067A5-0157-4B20-BC7F-94362BBF324D
Preboot disk: /dev/disk1s2
Preboot volume: /System/Volumes/Preboot
Copying: /System/Library/KernelCollections/BootKernelExtensions.kc.elides -> /System/Volumes/Preboot/E35067A5-0157-4B20-BC7F-94362BBF324D/boot/System/Library/KernelCollections
Copying: /System/Library/KernelCollections/BootKernelExtensions.kc -> /System/Volumes/Preboot/E35067A5-0157-4B20-BC7F-94362BBF324D/boot/System/Library/KernelCollections
Copying: /System/Library/PrelinkedKernels/immutablekernel -> /System/Volumes/Preboot/E35067A5-0157-4B20-BC7F-94362BBF324D/System/Library/PrelinkedKernels
Copying: /System/Library/PrelinkedKernels/prelinkedkernel -> /System/Volumes/Preboot/E35067A5-0157-4B20-BC7F-94362BBF324D/System/Library/PrelinkedKernels
root@AirMac78s-Mac-Pro ~ #Do you guys are booting Big Sur without the need of OpenCore?
Same entire process as beta1, for the link I'd advise to use the InstallAssistant.pkg because I retrieved it from the latest 10.16 seed software update catalog.
@h9826790 Did you noticed some CPU & RAM temperature rising, because the CPU now it shows 50 while 34 on Mojave and the RAM is very hot!
Not really.
I do monitor my CPU RAM temperatures, but pretty much the same range as in Mojave.
34 sounds like at real ideal temperature. And just little bit of background process can bring it to 50.
I have been using an external usb hard drive installed with Big Sur on a supported machine for my MacPro 3,1 testing. In my case, I could never get 'sudo mount -uw / ; killall Finder' to work without producing the 66 error. That approach also failed on my MacPro 3,1 when booted in single user mode. That is why I have been exploring the route of using mounted snapshots and chroot as a substitute for mounting a writable copy of root.
Just use OpenCore to spoof the SMBIOS to iMac Pro as per the code I shared in this post.
OpenCore on the Mac Pro
—- Warning!!! This config may brick your Mac. Do NOT use it unless you know what you are doing. —- As a record. The following setting to simulate iMac Pro will cause black screen. [Update: fixed by using agdpmod=pikera] PlatformInfo Automatic Generic...
forums.macrumors.com
Of course, it‘s relatively easy for Mac Pro 5,1, because we can upgrade some hardware to meet the requirement (e.g. GPU). All we need just a way to install and run Big Sur, no patch required.
I can confirm that the link I posted here: https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28649854
is the BigSur beta 2, because I checked some binaries without extraction and they are compiled by apple on July .
is the BigSur beta 2, because I checked some binaries without extraction and they are compiled by apple on July .
So to “update” to beta 2 on an unsupported Mac I’ll need to redo all the steps I did to install beta 1?
Yes, and I add that now the name after InstallAssistant.pkg extraction is Install macOS Big Sur Beta.app
Attachments
Edit: nevermind, the issue was that I copied the old path and not the new one like @jackluke posted.