[pre-release] macOS Big Sur

[Cyberdevs]

@Matgen84

I disabled the OpenCanopy and now I can boot into the Big Sur's recovery lol

[markl18]

4 minutes ago, Cyberdevs said:

@Matgen84

I disabled the OpenCanopy and now I can boot into the Big Sur's recovery lol

should I try the same

[Cyberdevs]

Just now, markl18 said:

should I try the same

Well I guess if you do a clean install that would be the easiest way to resolve the issue, but even if the same thing happens after a clean install so there must be a misconfiguration in your EFI folder so I guess it's up to you.

If I understood correctly you didn't have this issue with DP2 correct? so if that happens on DP 3 and after the update I think the update process didn't go quite well.

[Alex HQuest]

26 minutes ago, iCanaro said:

 

create an SSDT for the custom PM for your CPU

https://github.com/Piker-Alpha/ssdtPRGen.sh

I was going to suggest the same. Seems people forget the SMBIOS of a particular model only carries the tables of the hardware they are supported; anything deviating from their standard hardware has to be manually added, as a kext, SSDT table or hot patch.

 

Also, yes, my system was sort of busy during that screen capture. It runs as low as sub 2GHz  and under 30C most of the time though.

 

Spoiler

 

[Sherlocks]

I think with the latest Lilu build it was resolved I was able too boot into the installer and the installed version of Big Sur Beta 3 without the vsmcgen=1. Haven't tested the recovery though.
 
Spoiler
 
 
 

thank you

나의 SM-N960N 의 Tapatalk에서 보냄

[Alex HQuest]

1 hour ago, Cyberdevs said:

I think with the latest Lilu build it was resolved I was able too boot into the installer and the installed version of Big Sur Beta 3 without the vsmcgen=1. Haven't tested the recovery though.

 

  Reveal hidden contents

 

Did not worked for me. Updated to latest sources from GitHub, got stuck during the boot, restarted, cleared NVRAM, retried, got stuck at the same stage. I'm still required to use vsmcgen=1.

[Cyberdevs]

2 minutes ago, Alex HQuest said:

Did not worked for me. Updated to latest sources from GitHub, got stuck during the boot, restarted, cleared NVRAM, retried, got stuck at the same stage. I'm still required to use vsmcgen=1.

try this one, I just compiled it it's a latest version.

Lilu.kext.zip

[mnfesq]

Has anyone had problems with kext injection using Clover v.5120?  Any ideas on how to fix it so that my custom kexts load?

[chris1111]

Very proud to announce I was able to boot macOS Big Sur Beta3 to my Dell Optiplex 790 in Legacy Mode (DUET) Working marvelously well

it was the last system I had left to complete with BigSur 

I never see Dell Optiplex 790 with OpenCore even less on Big Sur 

See spoiler

This is my EFI Partition and the boot BS USB Installer

Spoiler

 

 

Edited July 27, 2020 by chris1111

[FirstCustomac]

1 hour ago, Cyberdevs said:

I think with the latest Lilu build it was resolved I was able too boot into the installer and the installed version of Big Sur Beta 3 without the vsmcgen=1. Haven't tested the recovery though.

 

  Reveal hidden contents

 

 

 

Thank for the info.  My system boots now without vsmcgen=1 with the latest Lilu build.

3 minutes ago, chris1111 said:

Very proud to announce I was able to boot macOS Big Sur Beta3 to my Dell Optiplex 790 in Legacy Mode (DUET) Working marvelously well

it was the last system I had left to complete with BigSur 

I never see Dell Optiplex 790 with OpenCore even less on Big Sur 

See spoiler

This is my EFI Partition and the boot BS USB Installer

  Hide contents

 

 

Nice!! would you mind sharing your EFI? Thanks.

[markl18]

1 hour ago, Cyberdevs said:

Well I guess if you do a clean install that would be the easiest way to resolve the issue, but even if the same thing happens after a clean install so there must be a misconfiguration in your EFI folder so I guess it's up to you.

If I understood correctly you didn't have this issue with DP2 correct? so if that happens on DP 3 and after the update I think the update process didn't go quite well.

exactly I installed directly from usb . it rebooted 5 times and that was it then coudnt update until some one told me about SIP

 and that's where we are an no I can't log in even -x mode

[Cyberdevs]

40 minutes ago, eSaF said:

No go - whether it's this version or that version, I still need vsmcgen=1. so time for me to stop pulling at that particular thread 

I think you need to update the OC and the drivers as well, here's what happens, with the latest build of OC and the Kexts there is no need for vsmcgen=1 but if you use an older version of the OC and the kexts it will get stuck at boot.

Here is my latest OC folder and the updated kext. You might need to remove the SSDTs and reconfigure the kexts. 

 

Haswell Last update.zip

 

18 minutes ago, markl18 said:

exactly I installed directly from usb . it rebooted 5 times and that was it then coudnt update until some one told me about SIP

 and that's where we are an no I can't log in even -x mode

if you clean installed the DP3 why did you needed to install the update? I guess you installed the DP2 and then updated to DP3 and now it ended up in the current situation, am I correct?

[ileikcaek]

For those having issues getting into recovery (unsupported error), setting UEFI > APFS > JumpstartHotPlug to true worked for me. Recovery Images booted fine after.

 

-

 

I still haven't figured out my updating or installation on bare metal issue. trying the update in CLI gives errors about Mac OS not being booted in snapshot mode and that it must be to be able to update. The big 12.88GB Update begins installing but goes to restart too soon and stage 2 fails, this is the same experience as trying to fresh install from my installation USB. The only method to get Big Sur updated each time seems to be just installing it fresh to the SSD in VMware each time and this is definitely not ideal going forwards.

[markl18]

10 minutes ago, Cyberdevs said:

I think you need to update the OC and the drivers as well, here's what happens, with the latest build of OC and the Kexts there is no need for vsmcgen=1 but if you use an older version of the OC and the kexts it will get stuck at boot.

Here is my latest OC folder and the updated kext. You might need to remove the SSDTs and reconfigure the kexts. 

Haswell Last update.zip

if you clean installed the DP3 why did you needed to install the update? I guess you installed the DP2 and then updated to DP3 and now it ended up in the current situation, am I correct?

exactly did that picture I included do anything for anyone curious 

Edited July 27, 2020 by markl18

[Cyberdevs]

1 minute ago, markl18 said:

exactly

So what I suggested earlier is to download the DP3 full installer and do a clean install with that.

[markl18]

3 minutes ago, Cyberdevs said:

So what I suggested earlier is to download the DP3 full installer and do a clean install with that.

where do I get dp3 full installer and what does this error about update date

[Cyberdevs]

@markl18

Use @crazybirdy's script to download the full installer:

 

I'm not sure what that error means.

[valeryimm]

15 hours ago, mnfesq said:

 

It appears that VoodooInput.kext is located as a plugin in both VoodooI2C.kext and VoodooPS2Controller.kext.  Perhaps it is the presence of 2 of the same kexts that is causing your KP.

Yes, you're right. I removed on of the kexts. Still no luck with SATA drives.

[markl18]

1 minute ago, valeryimm said:

Yes, you're right. I removed on of the kexts. Still no luck with SATA drives.

as far as those kexts goes they have to be in certain order like gpis first than service and then i2c

[valeryimm]

Just now, markl18 said:

as far as those kexts goes they have to be in certain order like gpis first than service and then i2c

OK, gonna try

[swede420]

ga-z170m-d3h

i7-6700

rx570

 

success installing Big Sur without issues.

Edited July 27, 2020 by swede420

[valeryimm]

18 minutes ago, valeryimm said:

OK, gonna try

Yes, it works!

Now Disk Utility can see my SATA Drive.

Thank you very much

[markl18]

1 minute ago, valeryimm said:

Yes, it works!

Now Disk Utility can see my SATA Drive.

Thank you very much

my pleasure if I only new what was the question

[Stefanalmare]

2 minutes ago, eSaF said:

@Cyberdevs - Yep you was spot on - Updating OC cured booting without the need for boot-args vsmcgen=1. Funny thing is I thought I had the latest from here https://github.com/williambj1 as I normally do being lazy  but I just compiled my own like you advised, now booting without that boot-arg - Thanks again. 

OCBuilder.app! The easiest way. OC and latest kexts. 1 click.

[Alex HQuest]

3 hours ago, eSaF said:

@Alex HQuest - I'd be interesting to see what your temps are at idle because quite frankly seems a little hot but if the rig was under load, it's understandable.

 

I was installing Xcode during that screen capture. I'm still doing a lot of data xfers, so not truly "idle" from a CPU standpoint, but yeah, this one shows regular temps as they usually are like. Good thing is, even while under full load, package and/or core temps are hardly over 65C - perks of a custom loop water cooling 

 

Spoiler

 

 

2 hours ago, Cyberdevs said:

I think you need to update the OC and the drivers as well, here's what happens, with the latest build of OC and the Kexts there is no need for vsmcgen=1 but if you use an older version of the OC and the kexts it will get stuck at boot.

 

As I mentioned, I did fetched the latest and greatest from GitHub, but more likely the build tools I'm using decided to cache something, then. Or some code was "repurposed" from Xcode 12 when I recompiled on Xcode 11 (Lilu fails on Xcode 12, but OpenCorePkg compiles just fine). Will retry after cleaning my local caches to act as a "pristine" build. Thanks for the hint though.

Edited July 27, 2020 by Alex HQuest
Double posting