Leaderboard

This thread becomes very interresting with the new release beta 3. As mentioned @eSaF there is positive or negative feedback and we can already see if there is any improvement we can hope for for the future version. For me i always appreciate the detailed and comprehensive comments as @arsradu (thanks) do them : it is very important for me because English is not my "mother tongue". There is some very useful information as detailed @fusion71au or @Pavo some posts above of course a lot of other guys are helping us sorry if i haven't mentioned them all. I notice the perseverance of @MorenoAv , @SavageAUS , @ameenjuz , @Matgen84 : they are always one line and also @eSaF :maybe they are the modern gladiators: if I am allowed to do "French humor" (sorry if I forgot others) One thing I'm particularly interested in as @MacPato has already mentioned about Big Sur on the AMD system. So unlike before, I will now start Big Sur beta 3 with my new AMD test system and keep you updated. The Big question is Big Sur or not Big Sur for the future PS : sorry for my "French" English

The answer is: Bien Sûr.

@eSaF I actually noticed the same issue on my MBP initially. Didn't pay much attention to it with previous Betas, but now that you mentioned it, then this looks more and more like a bug with Beta 3. As for the wishful thinking...personally, I like to think positive. Cause I believe, when we do that, positive things happen. Call ma naive, if you want. I don't care. I've seen it working way too many times before to know it can't be a coincidence. I also don't believe in coincidences. Cause that would mean that I also believe in random. And I don't think that anything that's happening with us, to us, is random, or can be random. I think we just don't know the reason for it...yet. So..., to answer your question, no, I wouldn't be surprised if it actually was pretty much smooth sailing going forward. I still couldn't figure out how to fix the "preboot" issue, but it doesn't really bother me that much, especially since I know it's also an issue on real Macs. Yeah, I have tried enabling/disabling SIP...but no change on my side. Anyway, as I said, I don't really mind it that much. :)) Hopefully next betas will fix this one, too.

Yes it is, but we march relentlessly toward the victory... ...

Ok from a fresh (vanilla) instal, all kexts latest versions and new EFI Folder, new ssd disk - (sorry for the delay, had to go out and get a Take-Away for the wife), The install was trouble free from start to finish, two things with Beta3 - The first - 'Preboot' is the default name of the boot disk at the Boot Menu (whether this is the new norm from Apple or a bug, we have to wait until the next update). The second is definitely a bug - There is no startup disk to choose from in System Preferences/Startup Disk because the volume is not mounted - even when Multi Booting it is not there - unless manually mounted after reaching the desktop then it shows. These are the only two major bugs I noticed in Beta3 and with these findings, I will stop trying to correct these two and let Apple solve them for the next release - Cheers.

Hey soldier!!! - That's not the spirit we're looking for in this Man's Army, now pull your self together and let's go No man just josting wid yah, if you're happy then go with it, as you say lets see what the coming week brings.

I’m leaving the disk name alone (Preboot) and the lack of a big sur option in startup disk so I can see what the next update brings. Should only be a week or so? I’m happy to be a guinea pig [emoji241] Sent from my iPhone using Tapatalk

Yes for me it is a war, some days I win some days I lose . I just done a Recovery not from Time Machine or a back-up disk but a Live one from Apple Servers, over my BS beta3 install and I did not get to the object of my initial plan which was to get the BS Disk to show in the Disk Start Up panel, All I achieved was the named Disk in the boot menu reverting to the name Preboot and BS still not in Start Up panel, so that is one battle I lost But on the plus side, Recovery works perfect you can install over the original installation or delete and install a fresh copy of BS, so far the moment I will recoup and gather the troops and save the battle for another day but that is not going to stop me from doing covert operations on BS like a Ninja.

I did a clean install using the Big Sur recovery partition and I also got the Preboot "issue" at the end. However, following the instructions of @fusion71au the "issue" was solved. I didn't copy any file, I just run csrutil disable, then csrutil authenticated-root disable in the terminal in the BS recovery partition and restarted my computer. After that the Big Sur volume was correctly shown in the OC picker! just like that. I hope it helps, Good luck.

@MorenoAv - My friend progress is slow and painful

This is all I needed for my drive name to show up correct in OpenCore boot menu. Thanks

I try csr-active-config=00000000 but I can't boot on BS Beta 3 Recovery Partition idem with blank You're welcome ( "French" English too)

I got Preboot issue on my update from beta2 to beta3, no issue during installation.. after few restart volume name back to normal

@MorenoAv Apple developers says: macOS Big Sur 11 beta 3 is a full app instead of only incremental update image. Maybe that means B1+B2+UpdateBS3=Beta 3 Despite of fresh install, I've got the "Preboot" issue on my Aorus Master it does not matter

ma LOL

@MorenoAv yeah, the 5GB one is the incremental update. The 12GB one is the full installer. And the fact that it's showing both seems to be a bug.

@eSaF, You are determined to wind the BS war... I like it, today when I return home I'm erasing my BS thingy and start fresh, because there are some things that I don't like. For that reason although I solved the "Preboot" issue, the bluetooth... fresh install it is... PS: On a side note, right now I'm at work, and I have a real Mac mini 2018, the update appeared and I installed it but it was only 4,99 GB. after finishing that update appeared the other with 11,98 GB to download. BS is weird even in real Macs... LoL ...

@SavageAUS - Ok you've convinced me - I am gonna do a Recovery and see if I can get the Disk to show in the Start Up section and if need be a full re-install, I got time on my hands for 'Crappery' today.

My coffee lake laptop i7-9750H works great with Catalina and Big Sur. I’ll update this post with my EFI folder folder soon. Sent from my iPhone using Tapatalk

Have any of you guys tried the new VP9 decoding feature of Safari in Beta 3? I can't seem to get it to work... I mean, it's enabled in Developer options, it's just not giving me the options for resolutions higher than 1080p in YouTube for example. Such as this video:

TextEdit is your friend. Open config.plist and change <true/> to <false/>. Or use Clover.app to do the work but not Clover Configurator.

for my part it does not show me all the disks, because I have two Big Sur and it shows me my other system and same thing when I try on the other system

I can not boot with or without this value. Do you need to add <false> values for Clover Quirks plist? If you look above, all I have are true values in the Clover Quirks plist. I'm hate to admit I used Clover Configurator and put check marks for values. It only generates true ones. Does it need to look like the OcQuirks plist with true and false values?

Thanks to @fusion71au's fantastic guide, The Intel Power Gadget is now working properly on my machine and I was able to modify CPU name without deleting the Snapshots. For those of you who don't already know, the easiest way I know so far to modify CPU name in "About This Mac" without deleting the snapshots is to mount your Big Sur system-volume to your desktop, navigate to Processors.strings from the Finder and edit the file from there as you will have full read/write access this way. After that, use @fusion71au's guide to create a Snapshot. To mount system volume on Desktop. (X and Y is to be replaced with your Big Sur volume's disk identifier) sudo mkdir ~/Desktop/Test && sudo mount -t apfs /dev/diskXsY ~/Desktop/Test One more thing I'd like to mention is that, if you have not deleted your previous snapshots, you can retag them for your next boot, if necessary. (This is to be done in Recovery) Mount as read/write, find the name of your Snapshots, and tag one of your working snapshots for the next boot. mount -uw /Volumes/Big_Sur diskutil apfs listsnapshots /Volumes/Big_Sur /System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -r "Name of your Snapshot" -v /Volumes/Big_Sur Reboot

Everything smooth on my dell, updated from the App like a Mac! just four reboots!

Yes! applause to the Germanic guys, Clover 5119 mod - the 3 new patches, launches Big Purge beta 3 already installed my Z370 https://www.hackintosh-forum.de/forum/thread/49311-macos-11-bigsur-dev-beta-clover-patch/?postID=626411#post626411 bootlog.txt.zip

I've managed to get into BS ß3 Recovery (with either csr-active-config = blank or all 0's) and have run both csrutil commands as shown above. Then, when I re-boot into BS ß3, with csr-active-config = 7708000 or 00000000, I cannot run the command to rename Preboot, as "operation is not permitted" (csrutil status says SIP is still enabled). It seems that csrutil disable is not remaining disabled after a re-boot. Any suggestions? Thanks.

Thanks @Max.1974, I was able to solve that a while ago... I don't know how but it worked... LoL PS: I'll tell everything but the only thing that I do was made another EFI folder from scratch, complete with fresh kexts, and compile the last commit of OpenCore... nothing more...

Hi my friend, try use Kext-Dropet by Chris1111 and install in L / E that will works!!! Im could get it install on my both Hacks!! Lenovo and Desktop!! But only was needed make this on Lenovo...:)

I can boot on Catalina Recovery without any change in my config.plist Despite of that I test ScanPolicy=0 as you says before.

I just updated OC and Weg kext and Big Sur showed up in Startup Disk option. But now I'm not able to boot from Recovery.

YESSS! Thank you SOOOOO much!

Here you go Brother. Please let me know that it works just incase I did something wrong, F11jGK Profile.zip - Bios Profile F11j GK with all the correct settings dialled in.

Thanks for this explanation about F11j GK I don't use it. Can you explain rollback procedure via USB, please!

Legend!!! This worked a treat and a half! I must admit I did go down the road of getting a new bios to try, I found the f11j on tweaktown but seemed a little unstable (maybe incorrect settings, do you have a profile for this?) as it was a vendor specific one I could not flash f11e over it as it kept saying "oemid mismatch" (any ideas on this) so had to flick to the backup bios and flash f11e on that (that was at f10), loaded profile and all is now gravy! Deffo the serial port causing issues. Again you are such a legend to offer your help like yo have :-)

@arsradu - Thanks for checking that out, yes it does show up if you manually mount that particular volume. In Beta1 & 2 the operation was normal where you could choose the start up disk without having to mount the disk. I was about to do a recovery or even a full install to see if I could correct the glitch but on reading your post, I decided against that idea so thanks - Yea I know I am quirky like that even though it is still a Beta - Good job on solving your Recovery glitch without the app.efi file hopefully going forward towards the Public Release, the Golden Master and the Final we won't encounter any major surprises and it will be smooth sailing or is that wishful thinking on my part?

Successfully updated Big Sur Beta 2 to Big Sur Beta 3 through VMware Fusion

@drlove You mean like this: ioreg -lp IODeviceTree | grep OEMBoard & ioreg -lp IODeviceTree | grep OEMVendor | "OEMVendor" = <"Gigabyte Technology Co., Ltd."> | "OEMBoard" = <"Z170X-Gaming 5">

Beta 3 updated with open core ver listed earlier on this thread just fine. hbp

Yeah, same here. And I wasn't paying attention to it with previous betas, but yeah, I think that might be a bug. Also, interestingly enough, now I can boot into Recovery without the apfs.efi file. Just with JumpstartHotplug set to Yes. Not sure what changed, but I'm glad it works now. Edit: sorry, my bad. It does show up if you mount it. But for some reason now it shows the currently booted system and the Bootcamp partition but not the other partition with Big Sur on it (which is still mounted). :)) Is it limited to two disks in the UI? :))

No problem getting Startup Disk to detect all of my installations.

Hello Thank you kindly, I will give this a burl. This is what makes this community what it is. Michael

Already answered here. Once Big_Sur volume sealed after installation, AFAIK, you can't unseal it. If you want to easily access your Big_Sur volume from older macOS, you have to prevent sealing before it happens in the first place eg use @ASentientBot's hax2 to patch the Installer. I don't recommend the "UpdateOptions.plist method" since this seems to interfere with deleting APFS snapshots later on. sudo mv ~/Downloads/disk_label.contentDetails /System/Volumes/Preboot/UUID/System/Library/CoreServices/.disk_label.contentDetails The UUID is unique to your own system and is actually the UUID of your Big_Sur — Data⁩ volume. Easiest way to find out the UUID value is to list the contents of Preboot - from terminal (after mounting the Preboot volume with sudo diskutil mount diskXsY), type... ls -l /System/Volumes/Preboot Also can see in Finder... Disable authenticated root SIP by setting csr-active-config to 77080000 in OC's config.plist, then reset NVRAM through the OC boot menu. Alternatively, with blank csr-active-config setting, boot to Recovery/Big Sur Installer and run csrutil disable, then csrutil authenticated-root disable in terminal.

yup without the vsmcgen=1 the installer won't load, once I added the vsmcgen=1 bootfalg I was able to boot into the installer and now it's in progress.

Mine also says "Preboot" right now. So far, no change. But, as I said before, this is probably also a bug on Apple side. So...I wouldn't worry about it too much.

@ameenjuz When the download is finished just open the pkg and it will install the Big Sur app to the Application folder

@ameenjuz Only PKG link if you want http://swcdn.apple.com/content/down...fasb0217grmmyplfd6o7mqfp/InstallAssistant.pkg

macOS Big Sur 11 beta 3 (20A5323l)

I can install doing the following 1. compile latest OpenCore and nightly builds from Lilu & WEG 2. download Beta from Apple Developer 3. make USB installer with createinstallmedia 4. add vsmcgen=1 boot-args in config.plist 5. boot from USB installer 6. make vanilla install, don't install over Catalina ! 7. after 2nd stage is finished and before installer switches to boot to install destination I add to NVRAM 7C436110-AB2A-4BBB-A880-FE41995C9F82 <key>booter-fileset-basesystem</key> <data> AA== </data> <key>booter-fileset-kernel</key> <data> AA== </data> 8. second stage of installation and voila ! 9. vsmcgen=1 can be removed (in my case) have to keep the NVRAM vars, otherwise Big Sur won't boot Hope that helps Edit: atm downloading 2nd Beta (20A4300b)

No need for the Beta Access Utility: sudo /System/Library/PrivateFrameworks/Seeding.framework/Resources/seedutil enroll DeveloperSeed