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
Done. Hard disk starts blinking as copying, and continues for hours without errors. But also If It works It Is too
much slow
Last edited:
Since for non-APFS or legacy usb Mac cloning a BigSur (with sealed system and snapshot booting) in most cases won't work, you should try this:
https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28662873
edit:
if you have a non-APFS firmware mac you need also this:
https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28675922
to continue the BigSur stage2 installer that is the: macOS Installer (on opencore menu).
Last edited:
I've never understood the logic of how that is supposed to work. If the stock Big Sur kc can't boot an unsupported machine, won't the installation fail on the first reboot during the installation process?
not quite,
MP1,1 -> MP2,1 was nearly the same thing, but atm irrelevant here due to Xeon restrictions to non-SSE4 processors ;-(
How much data are you trying to copy? It took about 20-30 minutes on a usb2 iMac for me. Sounds like you might have a hardware issue.
What program would you recommend for spoofing a MBP? I have a 6,1 that I can try on without shame and if it's smooth I can do it on my 8,1. Please let me know your recommendations. I have searched Safari (lol) for hours and can't find/figure out what approach works best/safest.
Stock BigSur kc "works" (no responsive keyboard mouse of course) for legacy USB (or non-APFS) Mac provided that the root disk (or root installer) is on the internal SATA , because on internal SATA the usb legacy even if not working are simply ignored by the bigsur kernel and this allows to continue booting, in case of the BigSur stage2 installer the process is automatic and doesn't require any user "usb input output" since all the installer setup selections are made directly from Catalina (or Mojave) desktop .
20 GB (basic BS beta2 installation) Maybe is due to the SSD source? I have launched it from Catalina, after having ejected both disks, to avoid "busy disk" warning.
I retry now from BS beta 1 to clone BS beta 2 SSD 100 GB (20 occupied) to external USB harddisk 101 GB
On my late 2012 Mac Mini (sealed, snapshot) the given solutions for getting working Wifi didn't work for me because obviously I got the error 66. Other solutions involved disabling and/or deleting snapshots which also didn't work for me because I'd always get a "operation not permitted" error (SIP and ARV are both disabled).
So today I did a complete reinstall using @ASentientBot's hax to prevent sealing of the volume. I booted back into the USB and mounted the Big Sur volume with write access
and copied over IO80211Family.kext.
I then ran
followed by kcditto from the "volume_name":
Finally I ran
Et voilà, upon rebooting into the system I've got myself working WiFi.
So today I did a complete reinstall using @ASentientBot's hax to prevent sealing of the volume. I booted back into the USB and mounted the Big Sur volume with write access
Code:
mount -uw /Volumes/volume_nameand copied over IO80211Family.kext.
I then ran
Code:
kmutil install --volume-root /Volumes/volume_name --update-all --forcefollowed by kcditto from the "volume_name":
Code:
/Volumes/volume_name/usr/sbin/kcdittoFinally I ran
Code:
bless --folder /Volumes/volume_name/System/Library/CoreServices --bootefi --create-snapshotEt voilà, upon rebooting into the system I've got myself working WiFi.
One word...weird.
DD copies the disk bit by bit, it should be a 100% copy, not 99.999999999999%
Might be the the sector size but I doubt it.
Last edited:
With BS beta 1 it always says: disk2 resource busy also if disabled. I retry with Cat 10.15.5. I have re-inizialisated target that was 99 GB to 101 GB to be sure
You most likely also be able to do that in Terminal in recovery.
I had that..."resource busy" quite a few times, most of the times Disk Utility, isn't the best Utility.
Most times I can do things on my Mac what a Windows PC can't, a Windows PC could do this one easier though, or Linux.
Resource busy is also not always what it says it actually means, that the disk you copy from is busy, I had it that the Target disk was the problem, odd actually, says one thing but means the opposite.
Started cloning from Catalina, here when I disable disk 1 (Big Sur SSD) at least it doesn't warn me of "resource busy".
Anyone know how DosDude1 is doing I know he was on vacation for 2 weeks but have barely heard from him in any of these post. Just want to make sure he is ok and everyone else in this thread is staying safe and healthy during these times. Also I would like to thank everyone again for all of the hard work they are doing.
Last edited:
My MacPro3,1 is currently working with BigSur DP1.
WLAN and BT work natively, Magic Maus works as always, BT Audio works
Unfortunately, the old AppleHDA and LegacyUSB are still missing.
currently my way is via SingleUserMode, exit, then... I have a keyboard in BigSur.
Here are a lot of tips. Which way is right now for Sound and LegacyUSB?
WLAN and BT work natively, Magic Maus works as always, BT Audio works
Unfortunately, the old AppleHDA and LegacyUSB are still missing.
currently my way is via SingleUserMode, exit, then... I have a keyboard in BigSur.
Here are a lot of tips. Which way is right now for Sound and LegacyUSB?
After 3 hours hard disk is still blinking. I have made screenshot to show you what I'm running. i point to APFS containers. Maybe you mean /dev/disk ? Because in the first APFS container there is Cat SSD. I will keep it running overnight, since I can still use mac mini flawlessy
Attachments
Last edited:
Assuming that you have access to supported machine, what worked for me was the following...
Code:
Disable authenticated-root in nvram using csrutil from Big Sur from the root level of a patched Catalina usb installer with..
sudo csrutil2 authenticated-csr disable
Also make sure to set...
sudo nvram boot-args="-no_compat_check"
Install Big Sur on an external drive from a supported machine. Attach this drive under Catalina mount it's Preboot volume.
cd /Volumes/Preboot/*/System/Library/CoreServices/
curl https://github.com/jacklukem/BigSurfixes/raw/master/prelinkedkernel%20fix/com.apple.Boot.plist --progress-bar -L -o /private/tmp/com.apple.Boot.plist
sudo cp -a /private/tmp/com.apple.Boot.plist .
curl "https://raw.githubusercontent.com/jacklukem/BigSurfixes/master/legacy%20usb%20prelinkedkernel%20beta1/prelinkedkernel?raw=true" --progress-bar -L -o /private/tmp/prelinkedkernel
sudo mv PlatformSupport.plist PlatformSupport.plist2
sudo cp -a /private/tmp/com.apple.Boot.plist .
cd ../PrelinkedKernels
sudo cp -a /private/tmp/prelinkedkernel .
Attach a usb memory stick with the following kexts files
from Catalina Patchers kext)
AppleHDA.kext
AppleIntelPIIXATA.kext
(from 10.15.5)
IO80211Family.kext
AAAMouSSE.kext v0.93
telemetrap.kext v0.22
*** commands below remove the incompatible kext ****
mkdir /tmp/mntpoint
sudo mount -o nobrowse -t apfs /dev/disk7s5 /tmp/mntpoint
cd /tmp/mntpoint/System/Library/Extensions
sudo rm -fr IO80211Family.kext
sudo rm -fr AppleHDA.kext
sudo ditto /Volumes/Untitled/IO80211Family.kext IO80211Family.kext
sudo ditto /Volumes/Untitled/AppleHDA.kext AppleHDA.kext
sudo chmod -R 755 IO80211Family.kext
sudo chmod -R 755 AppleHDA.kext
sudo chown -R root:wheel IO80211Family.kext
sudo chown -R root:wheel AppleHDA.kext
cd /tmp/mntpoint/Library/Extensions
sudo ditto /Volumes/Untitled/AppleIntelPIIXATA.kext AppleIntelPIIXATA.kext
sudo ditto /Volumes/Untitled/telemetrap.kext telemetrap.kext
sudo chmod -R 755 telemetrap.kext
sudo chmod -R 755 AppleIntelPIIXATA.kext
sudo chown -R root:wheel telemetrap.kext
sudo chown -R root:wheel AppleIntelPIIXATA.kext
*** commands to rebuild and move new prelinkedkernel to /System/Library/PrelinkedKernels for kcditto to find ***
*** add missing directory ***
sudo ln -s ../../../../System/Library/PrelinkedKernels /tmp/mntpoint/Library/Apple/System/Library/PrelinkedKernels
*** add missing symlink for kextcache -system-prelinked-kernel
sudo ln -s ../../../../System/Library/Caches /tmp/mntpoint/Library/Apple/System/Library/Caches
*** this is currently builds broken legacy usb prelinked kernels
sudo chroot /tmp/mntpoint mount -uw /
sudo touch /tmp/mntpoint/Library/Extensions/
sudo chroot /tmp/mntpoint kextcache -i /
*** don't bother installing broken prelinked kernels ***
**** sudo chroot /tmp/mntpoint kcditto ****
sudo bless --folder /tmp/mntpoint/System/Library/CoreServices --bootefi --create-snapshot
*** reboot to make modified snapshot active root ***You can use jacklukes's legacy usb beta 1 kernel but you do have to replace the installed copy of AppleHDA.kext and IO80211Family.kext in /System/Library/Extensions. The High Sierra version of AppleHDA.kext is required for the MacPro 3,1 and the Big Sur version of IO80211Family.kext has to be replaced with a copy from Catalina for wifi to work (at least for a BCM94360CD.
Note that this approach abandons trying to prune off the snapshot but rather uses that feature to allow the kext replacements.
ps It is still unclear to me whether a legacy usb prelinked kernel has even been built under beta 2 without snapshots present or if that was broken by beta 2.
pps This approach requires a little finessing to get the wifi working. You will have to manually enter the SSID and wifi password. It will report the network can't be found but, on the next login, wifi will automatically connect and show the scanned networks as well.
Last edited:
@jhowarth
Thank you for the instructions.
What should I change IO80211Family.kext for?
I have a BCM94360CD to PCIe adapter in MacPro3.1. This works apparently natively with BigSur.
Thank you for the instructions.
What should I change IO80211Family.kext for?
I have a BCM94360CD to PCIe adapter in MacPro3.1. This works apparently natively with BigSur.
Same situation here for internal audio, I'll try it tomorrow, too.
[automerge]1594840334[/automerge]
Last edited:
-- Replacing System Folder Icons --
Hi, I don't think this has been covered elsewhere in the thread. I've installed BS beta 2 on my Mac Pro 2010 on a separate internal SSD drive partition using the method of shutting down the usb installer half way through the final auto restart, in order to finish up with an unsealed OS, plus deleting the one created snapshot from recovery. This also means that the BS System disk is mounted on the Mojave and Catalina desktops, so avoid the 'unknown disk' notice. SIP/auth-root/compat-check all remain disabled across reboots. BTW, I'm finding BS faster/more responsive on my 5,1 than Catalina is. My daily OS is still 10.14 for now.
Apart from fixing Wifi for the existing 802.11n card, my main reason is to test out replacing the bright blue system folder icons in S/L/CoreServices/CoreTypes.bundle with those from 10.9. I've done this successfully in 10.14 and 10.15.
However, once replaced with the older folder icons and confirming they're still root:wheel, no matter how many times I try to clear the various icon caches, I'm still left with the original bright neon system folder icons I really dislike, even though they technically no longer exist. I can't see any unmodified CoreTypes.bundle file on the Preboot volume, although there's one in the BaseSystem.dmg on the Recovery volume. What is intercepting or overriding the older icons? As I appear not to be stuck booting into any snapshot, I'm pretty well stumped at the moment.
Any ideas?
Hi, I don't think this has been covered elsewhere in the thread. I've installed BS beta 2 on my Mac Pro 2010 on a separate internal SSD drive partition using the method of shutting down the usb installer half way through the final auto restart, in order to finish up with an unsealed OS, plus deleting the one created snapshot from recovery. This also means that the BS System disk is mounted on the Mojave and Catalina desktops, so avoid the 'unknown disk' notice. SIP/auth-root/compat-check all remain disabled across reboots. BTW, I'm finding BS faster/more responsive on my 5,1 than Catalina is. My daily OS is still 10.14 for now.
Apart from fixing Wifi for the existing 802.11n card, my main reason is to test out replacing the bright blue system folder icons in S/L/CoreServices/CoreTypes.bundle with those from 10.9. I've done this successfully in 10.14 and 10.15.
However, once replaced with the older folder icons and confirming they're still root:wheel, no matter how many times I try to clear the various icon caches, I'm still left with the original bright neon system folder icons I really dislike, even though they technically no longer exist. I can't see any unmodified CoreTypes.bundle file on the Preboot volume, although there's one in the BaseSystem.dmg on the Recovery volume. What is intercepting or overriding the older icons? As I appear not to be stuck booting into any snapshot, I'm pretty well stumped at the moment.
Any ideas?
Last edited:
DD is bit by bit cloning, there is no better option in my opinion, it should copy 100% of the disk.
I rechecked, you do it wrong, copy the whole disk, not the APFS container.
It's a 500 GB disk, you need a target disk of at least 500 GB
To be more precise, all partitions on the source disk have to be copied, reason, there are partitions on the disk which are needed, without them your clone is not bootable.
So, you can stop now, a 500 GB disk will take most of the day to copy, depending on the transport protocol, if you have Thunderbolt it would be fast, if it's a USB 3 disk it is a lot slower.
I once cloned a disk, can't recall how big it was, it took most of the day to copy the disk.
Last edited: