I should be clear I ran those commands from Big Sur installer after it had already installed and everything works but wifi. Any tips or tutorials would be awesome on public beta 1... Thanks!
I’m on a single cpu tray, stock 2.26 quad coreI’m gonna fresh install on my 2009 Mac Pro with the newest installer and see if I get any errors.
I wonder if the dual cpu is causing a weird problem for some reason. Although I don’t see why it would
No problem brosame, here.
i also would like to ask the same question.
every time i want to make the installer, always come that notice.
Its is normal? and are the installer is good to use?
No problem brosame, here.
i also would like to ask the same question.
every time i want to make the installer, always come that notice.
Its is normal? and are the installer is good to use?
after I downloaded Big Sur and hack file and typed the command , unable to boot and got this error .
There is something missing
(MACBOOK PRO MID 2012)
View attachment 943365
I have seen this several times, too! So I would call it unwanted but normal right now. Since I got a usable installer one could ignore it.same, here.
i also would like to ask the same question.
every time i want to make the installer, always come that notice.
Its is normal? and are the installer is good to use?
after I downloaded Big Sur and hack file and typed the command , unable to boot and got this error .
There is something missing
(MACBOOK PRO MID 2012)
View attachment 943365
I just did a fresh install with the latest patc/System/Volumes/Update/install-log-*.log
/System/Volumes/Update/patchd-*.log
(or just /Volumes/Update/... if you're accessing the files from High Sierra/Mojave/Catalina)
my fresh install is in a boot loop. In verbose mode it gets through everything fine. It’s when the Apple turns white and the bat loads a little bit and then it reboots. Iv gotten past it before. I’ll let you know what I do.I’m on a single cpu tray, stock 2.26 quad core
Usually that means your SIP not disabledafter I downloaded Big Sur and hack file and typed the command , unable to boot and got this error .
There is something missing
(MACBOOK PRO MID 2012)
View attachment 943365
UPDATE #2 on my patcher:
I have successfully created a patcher with a working usb installer recovery. Everything works PERFECTLY on a 2011 MBP, and I hope the same is the case for other Macs. My current project is to make variants of the kext patching for different Macs so that unneeded kexts won't be added to any Mac. I am also working on making a better UI and UX for the person downloading, similar to what dosdude1 has been doing. If anyone can give me any tips on patcher UI, it would be much appreciated. I can't give an ETA but I'm hoping that by August 15th it'll be ready.
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
mount -P 2
mount -vat nonfs
thanks to the @ASentientBot "apfs_systemsnapshot method", I have disabled on BigSur beta 3 snapshot booting directly from BigSur (without its Recovery), here are the steps, the two requirements are from a macOS Recovery or terminal recovery:
nvram boot-args="-no_compat_check"
csrutil disable
then from BigSur normal booting, open terminal and follow these steps:
Code:(this makes writable the mount point) cd /S*/L*/File*/apfs*/C*/R*/ sudo ./apfs_systemsnapshot -v ~/Snapshot -r ""
It would be more interesting to know what you did before you made it to this situation.See pic who can help.me still 30mins.....
@jackluke command.... I will use sudo mount -uw /"....
The.message Attempting tagging of snapshot on volume: /Users/yourusername/Snapshot was shown....but after reboot
mount -P 1
mount -P 2
mount -uw /
kmutil install --update-all
kcditto
exit
csrutil disable
from macOS recovery .How To Disable ?Usually that means your SIP not disabled
Many thanks for trying to sort it posted those log files their in page 123 post 3063I just did a fresh install with the latest patc
my fresh install is in a boot loop. In verbose mode it gets through everything fine. It’s when the Apple turns white and the bat loads a little bit and then it reboots. Iv gotten past it before. I’ll let you know what I do.
I couldn’t mess with it anymore last night because it was movie night and the other Catalina drive has my plex server on it
EDIT: I also noticed while I’m booted into Catalina, I don’t see the ‘UPDATE’ volume only the Big Sur volume.
i mention this because usually I see both
boot into your Big Sur Usb installer in the terminal enter nvram boot-args="-no_compat_check" and csrutil disableHow To Disable ?
I should be clear I ran those commands from Big Sur installer after it had already installed and everything works but wifi. Any tips or tutorials would be awesome on public beta 1... Thanks!
mkdir /tmp/mntpoint
sudo mount -o nobrowse -t apfs /dev/diskXsY /tmp/mntpoint
cd /tmp/mntpoint/System/Library/Extensions/
sudo rm -fr IO80211Family.kext
sudo ditto /Untitled/IO80211Family.kext IO80211Family.kext
sudo chmod -R 755 IO80211Family.kext
sudo chown -R root:wheel IO80211Family.kext
cd ~
sudo bless --folder /tmp/mntpoint/System/Library/CoreServices --bootefi --create-snapshot
Usually that means your SIP not disabled
I have seen this several times, too! So I would call it unwanted but normal right now. Since I got a usable installer one could ignore it.
@Badruzeus on the other "non-mac hardware" forums are there any fixes for AppleACPICPU early kernel panic for booting the USB BigSur Installer (or installation) when using IntelHD Arrandale (or Arrandale i5 cpu) and i3 Clarkdale cpu ?
Because these Intel architecture are unable to boot the BigSur beta1 kernel , probably they need some DSDT fix.
I made many attempts but can't figure it out, unless AAPL on BigSur beta 2 fixes this kp.
I just realize that you've asked me about this #LOL
Yeah, on an Arrandale laptop with i3-370M / Clarkdale I tried BS DP1-PB many times with no luck. It got KP with AppleACPI* IOPCI* AppleSMC* dependencies. Though, using Catalina's prelinkedkernel bypass this issue but another Panic occurred.