macOS 11 Big Sur
@eightarmedpet, Unfortunately I formatted my bootcamp partition to reinstall Catalina for now, so I can't test it right now. I'm pretty sure it was disabled though. I'm not super knowledgeable about this stuff in general but I'm pretty sure the iGPU would have allowed the Windows logo to appear on boot. I also noticed that although I get the Apple logo on startup, the boot progress bar doesn't show up. It just kinda glitches into the lock screen on both MacOS and Windows. It does a weird thing where purple horizontal lines flash across the screen and then the login screens show up. I can still access the boot selector and recovery through eGPU, but it's like it has to reinitialize the GPU or something when it gets to the actual OS. This is similar to how it behaved before the Big Sur firmware, but it would just glitch into a black screen before. As if it couldn't reinitialize the eGPU. The OS would only work after I unplugged and reattached the eGPU, and of course that would break Windows. Now it just glitches into a functional OS, if that makes sense.
EDIT: Additional info that could be useful, with the disclaimer that I don't really know what I'm talking about, I just find this community interesting and I'd like to contribute a little if I can. I'm using an Asus RX580 in a Razer Core X. I've always had a slight suspicion that the Apple doesn't support the older RX5xx cards like they do the newer ones. With the exception of those Sapphire cards that were in the original Apple eGPU kits. They had some special sauce firmware. I'm wondering if the newer cards like a 5700 or even the old sapphire cards might function almost perfectly now? Without the glitches I've described.
I'm not super knowledgeable about this stuff in general but I'm pretty sure the iGPU would have allowed the Windows logo to appear on boot.
For Thunderbolt 3 displays however, this is not a viable solution, hence requiring the extra work keep iGPU enabled.
I can confirm my Mac mini 2018/2020 works perfectly well with my eGPU Razer Core X and RX5700 XT on Big Sur beta 1. Installed without any problem and kept my bootcamp partition intact. Now I can run macOs with eGPU turned on and my both screen connected to the eGPU without any trouble. On Catalina I was stuck on a reboot loop.
To make my Windows 10 (2004 fast ring) works with the eGPU I process like this:
- hold option key with usb automated GPU EFI software on it.
- quickly turned on the eGpu select windows and right after the mention "Ready" indicated Windows is about to start I unplug the HDMI from the Mac mini and leave just one cable from eGPU connected via Display port to the second screen.
- Windows is loaded on the second screen so the video signal going through the Mac mini to the eGPU and then to the screen. AMD technology recognise everything works perfectly fine.
I will make a whole build cause this was a nightmare but glad to see that Big Sur doing more good than bad in my case.
Has anyone successfully updated to Developer Beta 2? I came home and saw the update notification last night so I clicked to proceed. I kept getting an error during the initial download progress bar. This happened on both 2019 13-in MacBook Pro and 2018 Mac mini.
@itsage, You're likely getting the error because your systems are not snapshot-booted. Apparently on T2 macs, you need to enable Full Security mode for the system to boot off of a snapshot when FileVault is enabled.
Or you can manually force a snapshot boot by disabling FileVault, disabling ART, creating a new system snapshot and setting it as default, update preboot volume, and then reboot.
You can verify that the error is related to snapshots by running the software update command:
I faced the same issue but was able to resolve it as noted above.
@itsage, I got errors trying to use the Software Update preferences panel to download Beta 2, so I used the direct download link instead.
Sometimes I have to boot my Mac mini more than once for it to respond to the Option key and show the Startup Manager.
@joevt, Thank you for the insight! The software update command confirmed the error was due to Secure Boot was not set to Full Security. I turned it back on and the update proceeded as expected. It's a concerning approach imo because in order to turn Secure Boot on, the system requires Internet connection for macOS Recovery to crosscheck the boot volume with Apple's server.
@itsage, it probably did, to install Ubuntu and Windows. I'm sure I turned it off more than once and never turned it back on. I can't get into Recovery with Command-R so I press Option key until the Startup Manager appears then press Command-R (with Big Sur - Data selected). I try the Security Utility which asks for a password but won't accept my password, so I try reinstalling Big Sur from Recovery. The progress bar appears and works for several minutes but then the screen went black (using USB-C to DisplayPort adapter) until I connected HDMI - the screen continues to work after disconnecting HDMI again for a few more minutes, then it reboots to do install I guess. Apple logo appears. Then progress bar under Apple logo, then screen flickers, then progression, then "About 29 minutes remaining...", 10 minutes later: restart, Apple logo, progress bar, progression, 8 minutes later: restart chime, Apple logo, progress bar, progression near end, screen flicker, progression near start, 3 minutes later: screen black, Apple logo, progress bar near end, screen flicker, progress ends, Big Sur desktop appears, with all my windows from before - did it actually reinstall? I guess so, it just wasn't a clean reinstall. Using "diskutil list", there is no Update partition in the Big Sur APFS partition so that's good.
I can't get into the Startup Security Utility. Recovery accepts my password to show the Recovery menu (Restore from Time Machine, Reinstall macOS, Safari, Disk Utility). But Security Utility does not accept my password.
I can boot the Catalina Recovery partition by using rEFInd and selecting Recovery from the tools list. But it also doesn't accept my password.
rEFInd says Secure Boot is disabled in the info window.
So the way macOS Big Sur is supposed to boot is that it never boots off the live volume, but a snapshot of it (its not happening on all systems though). Naturally, it is impossible to mount a "snapshot" as writable. So what can be done is as follows:
- In recovery Terminal:
As of Beta 1, FileVault needs to be disabled to turn off ART.
- Back in normal boot, mount the live volume as writable. This is possible as on Catalina:
- Make modifications to the live volume.
- Generate and tag new APFS System Snapshot as follows:
- Reboot and voila!
Thank you for your guide, but it's not working for me and I don't understand the reason..
First of all, there's a small mistake, if you want to change it in your post, it's not "Filesystem" but "Filesystems".
Here the description of my issue:
First thing I did was to ensure that I didn't have anything in the add section of NVRAM in the csr-active-config key in opencore: at the time of writing if I have some value in that field I'm not able to disable authenticated-root via recovery (if I boot into recovery with JumpstartHotPlug=true and give the command csrutil authenticated-root disable I receive "csrutil: Failed to disable the authenticated root setting. This tool needs to be executed from the Recovery OS.").
So, csr-active-config should be set as:
Then I can boot into recovery and disable SIP:
and disable authenticated-root:
I can verify with "csrutil status" and with "csrutil authenticated-root status".
All is ok, all is disabled.
Now I can mount the root partition in read and write mode (from the recovery):
and I can modify stuff in /System/Library/Extensions for example (in my case I need to add a kext there and other files in /System/Library).
Here issues start: I followed 2 guides:
First one (thi s one):
- generate and tag a new snapshot:
However after a reboot all I have is a kernel panic complaining about that the filesystem seal is broken
After modification, I run this command (from recovery):
But again same kernel panic about broken seal.
Another guide added some more steps for guide 1:
- installing kext after the copy (from recovery):
Again generate and tag a new snapshot:
- Copying updated BootKernelExtensions to the Preboot:
Copy BootKernelExtensions to Preboot:
And again same kernel panic...
I'm running out of ideas...it seems I'm missing the last step, like seal again the volume or disable the seal check (I was thinking that SSV is disabled by authenticated-root....).
Anyone with ideas?
What a surprise, now my system boots normal...i thought...
It stucks a few time in a bootloop and ends with a panicEFI error on the desktop - everytime.
Now i have two problems, a MacMini that boots in Catalina with tricks and with panic error in Big Sur - and a error 12 in Bootcamp if i won´t work with an very old Windows 10...
Any solution with the crappy mini and eGPU?
My 2017 Macbook Pro runs without any errors, with and without eGPU plugged in, Catalina and BigSur is also fine.