[pre-release] macOS Big Sur

[iCanaro]

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

[Rocky12]

@iCanaro Can you please upload your EFI folder 

[iCanaro]

my EFI for Clover has no particular mysteries, as long as you have installed/updated Big Purge to beta 3 uses Clover 5119 mod that you find in the first post on the German forum complete with instructions and add in the config kernel patch the 3 new patches in the page linked previously
kexts compiled with the latest commits and boot-args vsmcgen-1

 

post 1 - https://www.hackintosh-forum.de/forum/thread/49311-macos-11-bigsur-dev-beta-clover-patch/?postID=619527#post619527

post 237 - https://www.hackintosh-forum.de/forum/thread/49311-macos-11-bigsur-dev-beta-clover-patch/?postID=626411#post626411

[markpenn]

Ever since Big Sur, my audio system always plan sound via my monitor (Via HDMI or Display port).

Even I change to internal speaker and mute the speaker,  audio always still plays via HDMI on display speaker. 

AppleALC latest kext is loaded, OpenCore latest is used, the same setup works without issue on MacOS 10.15.5 .

 

Any suggestion would be great, thanks!

 

[Dragster27]

2 hours ago, iCanaro said:

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

 

Yep, I can boot BS Beta 3 with clover 5119 mod & these updated patches.

 

Thanks 

[SavageAUS]

So I updated to latest master OC and updated to newest kexts this morning and still no Big Sur option in startup disk and still Preboot for volume name. But all still working so I can wait.

 

 

Sent from my iPhone using Tapatalk

[crazybirdy]

3 hours ago, iCanaro said:

my EFI for Clover has no particular mysteries, as long as you have installed/updated Big Purge to beta 3 uses Clover 5119 mod that you find in the first post on the German forum complete with instructions and add in the config kernel patch the 3 new patches in the page linked previously
kexts compiled with the latest commits and boot-args vsmcgen-1

 

post 1 - https://www.hackintosh-forum.de/forum/thread/49311-macos-11-bigsur-dev-beta-clover-patch/?postID=619527#post619527

post 237 - https://www.hackintosh-forum.de/forum/thread/49311-macos-11-bigsur-dev-beta-clover-patch/?postID=626411#post626411

 

Good news.

VM-method install Big Sur Beta 3,

Clover 5119 mod, New KernelToPatch, FakeSMC.kext, works fine here on installed Beta 3 now.

VirtualSMC.kext didn't work here with Clover.

 

 

Spoiler

 

 

Edited July 25, 2020 by crazybirdy

[d5aqoep]

1 hour ago, crazybirdy said:

 

Good news.

VM-method install Big Sur Beta 3,

Clover 5119 mod, New KernelToPatch, FakeSMC.kext, works fine here on installed Beta 3 now.

VirtualSMC.kext didn't work here with Clover.

 

 

  Reveal hidden contents

 

 

Possible for you to give HEX patches to be entered in clover configurator or Plist Editor Pro?

[crazybirdy]

5 minutes ago, d5aqoep said:

Possible for you to give HEX patches to be entered in clover configurator or Plist Editor Pro?

 

Works fine on Big Sur Beta 3 here.

BigSur Clover KextInjection Package.zip

[Matgen84]

12 hours ago, arsradu said:

Hi Mat! Yeah, same issue here (until now).

 

And yes, that's the file I used before to successfully get into Recovery.  

 

Thanks @arsradu I don't try yet apfs.efi to boot into Recovery Partition because I'm working. Maybe there is a issue for some machine, with apfsdriverloader integrated in Opencore.efi: it must be update, I suppose.

Edited July 25, 2020 by Matgen84

[Max.1974]

Since update, everething is fine...good weekend for all!!!

 

 

[arsradu]

21 minutes ago, Matgen84 said:

 

Thanks @arsradu I don't try yet apfs.efi to boot into Recovery Partition because I'm working. Maybe there is a issue with apfsdriverloader integrated in Opencore.efi: it must be update, I suppose.

Well, I don't know... I'm not so sure.  

Because, at the time when I was having issues a week or two ago, there were people with the exact same version who didn't have any issues. All they needed was that JumpstartHotPlug option enabled and that's it. Whereas on my end, it wouldn't work with only that option. Now it does. But a lot of things changed in the meantime (mostly in config). So...I don't know. But I think the issue might be somewhere else.

 

Anyway, if you wanna try the latest OC, I compiled it yesterday and you can give it a try if you want.

If it still doesn't work, my suggestions would be:

1. try the apfs.efi file. Don't forget to add it to config, as well. I always forget to do so. :))

2. try to compare the sample.plist (or my screenshot of NVRAM section) to yours and see if there's maybe something you need to change in there, as well

 

Something must be different, indeed. But I'm not sure it's the OC itself... Could be wrong though. So let's see.  

OpenCore-0.6.0-RELEASE.zip

[manmo71]

I have been attempting BS3 all this while with OC 0.6.0 and failed, but now after seeing people having success with Clover (have been a long time clover user)

I thought I will give a try at BS3 using a bootable USB and Clover.

But I am stuck at this point

 

Spoiler

 

I remember in the past that under quirks you need to enable AvoidRuntimeDefrag to get past this, which I have done but still no luck.

 

Spoiler

 

 

Anyone any clues?

 

Here is my EFI if anyone want to take a look at EFI.zip

Edited July 25, 2020 by manmo71

[arsradu]

3 hours ago, SavageAUS said:

So I updated to latest master OC and updated to newest kexts this morning and still no Big Sur option in startup disk and still Preboot for volume name. But all still working so I can wait.

Yeah, pretty sure those are both bugs... I mean, the Startup Disk thing works for me if I manually mount the BigSur system partition (not -Data) from Disk Utility. As for the Preboot thingy, yeah, that's a bug for sure. There seem to be some workarounds for it. But it doesn't bother me that much, so I think I'm gonna wait for the next update.

Edited July 25, 2020 by arsradu

[Matgen84]

4 minutes ago, manmo71 said:

I have been attempting BS3 all this while with OC 0.6.0 and failed, but now after seeing people having success with Clover (have been a long time clover user)

I thought I will give a try at BS3 using a bootable USB and Clover.

 

Hi @manmo71
Clover seems not ready yet with bootable USB BS Beta 3. See Clover discussion topic

[manmo71]

@Matgen84 Thank you for that update.

 

On OC, I tried the bootable USB method and also the VM method. With the bootable USB it kept failing at Asmedia, but on one of the USB ports it did progress.

 

Spoiler

 

But when I start the installation process, it fails at this, it is the same with with VM also, fails around this point with the same error.

 

Spoiler

 

I am unable to figure out the cause. I downloaded the BS3 around 3 times, assuming that it might be a corrupt installer. 

[Matgen84]

14 minutes ago, manmo71 said:

@Matgen84 Thank you for that update.

 

On OC, I tried the bootable USB method and also the VM method. With the bootable USB it kept failing at Asmedia, but on one of the USB ports it did progress.

 

 

But when I start the installation process, it fails at this, it is the same with with VM also, fails around this point with the same error.

 

 

I am unable to figure out the cause. I downloaded the BS3 around 3 times, assuming that it might be a corrupt installer. 

 

 

Sorry that is beyond my modest skills.

 

Did you use a USB2 port for the installation!

[manmo71]

Spoiler

 

Yup, it progresses further with the USB2 port and thats where I hit the next hurdle of the update failing....

[crazybirdy]

1 hour ago, manmo71 said:

@Matgen84 Thank you for that update.

 

But when I start the installation process, it fails at this, it is the same with with VM also, fails around this point with the same error.

 

  Hide contents

 

I am unable to figure out the cause. I downloaded the BS3 around 3 times, assuming that it might be a corrupt installer. 

 

shasum /Volumes/GPTData/Install\ macOS\ Big\ Sur\ Beta.app/Contents/SharedSupport/SharedSupport.dmg

e28034e835571e5c5aa8b5dab234c8e114091668  /Volumes/GPTData/Install macOS Big Sur Beta.app/Contents/SharedSupport/SharedSupport.dmg

 

You can check the shasum, my beta3 is as above and work fine.

Or you can use my lazy-tool to make VMware ISO.

 

VMwareISOscript.zip

 

Edited July 25, 2020 by crazybirdy

[Matgen84]

1 hour ago, arsradu said:

Well, I don't know... I'm not so sure.  

Because, at the time when I was having issues a week or two ago, there were people with the exact same version who didn't have any issues. All they needed was that JumpstartHotPlug option enabled and that's it. Whereas on my end, it wouldn't work with only that option. Now it does. But a lot of things changed in the meantime (mostly in config). So...I don't know. But I think the issue might be somewhere else.

 

Anyway, if you wanna try the latest OC, I compiled it yesterday and you can give it a try if you want.

If it still doesn't work, my suggestions would be:

1. try the apfs.efi file. Don't forget to add it to config, as well. I always forget to do so. :))

2. try to compare the sample.plist (or my screenshot of NVRAM section) to yours and see if there's maybe something you need to change in there, as well

 

Something must be different, indeed. But I'm not sure it's the OC itself... Could be wrong though. So let's see.  

OpenCore-0.6.0-RELEASE.zip

 

Using new OpenCore 0.6.0 Beta Release (24/07) + Latest Lilu and his plugins:  I can't boot Big Sur. Stuck at apfs_module_start: 2411 (with or without apfs.efi, with or without SSDT-AWAC.aml

 

Any ideas ! Please.

[arsradu]

12 minutes ago, Matgen84 said:

 

Using new OpenCore 0.6.0 Beta Release (24/07) + Latest Lilu and his plugins:  I can't boot Big Sur. Stuck at apfs_module_start: 2411 (with or without apfs.efi, with or without SSDT-AWAC.aml

 

Any ideas ! Please.

 

Yeah, that's a different issue... The issue I was having was an error on OC side saying something like: OCB: LoadImage - unsupported. What you're describing is a different issue, and it's actually the exact same issue I'm having right now with Clover...

[Matgen84]

3 minutes ago, Coke said:

 

 

Had the same issue. Solved it by replacing VirtualSMC with FakeSMC in OC.

 

Thanks @Coke

 

Do you copy also smchelper.efi for FakeSMC?

[Matgen84]

7 minutes ago, Coke said:

Try without.

 

I've got "Halting on critical error" with or without SMCHelper on my Z390 Aorus Master config. 

[Matgen84]

7 minutes ago, Coke said:

A log would be helpful... Btw, did you update your config.plist accordingly?

 

 

I update my config.plist accordingly. I don't remember the procedure for log or debug log, sorry can you tell me.

 

EDIT: I forgot a '>' in the config.plist. I can boot with FakeSMC now

Edited July 25, 2020 by Matgen84

[arsradu]

@eSaF maybe if you install it with SIP disabled, the Preboot issue does not occur....? I don't know... I installed with SIP enabled (in order to see the update in System Preferences; by the way, that seems to be another bug) and I couldn't get it to show anything other than Preboot ever since. No matter if SIP is enabled or disabled. If you're doing it after the fact, it doesn't seem to change anything.

 

Also, I don't know why, but I can't seem to be able to disable SIP from Recovery. It says it's disabled and I have to reboot to see the changes, but...it's still enabled (if I left it enabled) when checking its status via: "csrutil status". In other words, no matter what you do in Recovery, doesn't seem to affect the live system. But I'm probably missing something... There are a ton of new things with Big Sur, so I wouldn't be surprised if this was yet another bug.

 

I didn't try to use the custom disk labels, so... that might work. But since it doesn't bother me that much, I think waiting for the next update (which hopefully will fix this issue) is the best overall solution, so I don't have to undo everything when that one comes out, or cause other issues with Beta 4. I mean, it's probably not gonna make the system unbootable, but still...since this is a bug on Apple's side, I think waiting might be the best approach here.

 

Still, weird that it just "fixed" itself in your case... My guess is that it might have something to do with the NVRAM. But what...I don't know.

 

Edited July 25, 2020 by arsradu