[pre-release] macOS Big Sur

[Irish_Man]

7 minutes ago, eSaF said:

@dzontra - Are you asking about Catalina desktop pic showing instead of one for Big Sur and the lack of Big Sur disk not showing in Startup Disk? The Desktop Pic is a Bug on some machines including some genuine Macs and the lack of a BS startup disk is a bug on hackintosh machines. If you look in the 'Feedback Assistant' you will see all the bugs that has been fixed with this latest Beta and the ones that hasn't but with provided work arounds.

 

 Im asking about that flickering part (if you watch the clip, you'll see)

 

17 minutes 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 without the vsmcgen=1. Haven't tested the recovery though.

 

  Reveal hidden contents

 

 

 

Yup, it's fixed. Just tested. Recovery too

[eSaF]

1 minute ago, dzontra said:

 

 Im asking about that flickering part (if you watch the clip, you'll see)

 

Oh ok - my bad.

[Matgen84]

18 minutes 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 without the vsmcgen=1. Haven't tested the recovery though.

 

  Reveal hidden contents

 

 

 

 

Hi @Cyberdevs
 

Despite APFS settings in OC config.plist, I can't boot into BS Beta 3 Recovery Partition.

 

Always:

OCB: LoadImage failed = Not Found

Halting on critical error 

[Cyberdevs]

@Matgen84

Hi there, yeah I have the same issue with Big Sur's recovery partition 

[Matgen84]

4 minutes ago, Cyberdevs said:

Hi there, yeah I have the same issue with Big Sur's recovery partition 

 

I post the wrong error message for BS Recovery Partition issue: 

 

ocb: loadimage failed - unsupported

Halting on critical error

[eSaF]

@Matgen84 - What version Lilu are we talking about here? Because I have ver:1.4.6

[markl18]

hi this is all I can get out of it it is still locked me out 

Edited July 27, 2020 by markl18

[Irish_Man]

7 minutes ago, eSaF said:

@Matgen84 - What version Lilu are we talking about here? Because I have ver:1.4.6

 

 

 

This one? https://onedrive.live.com/?cid=fe4038da929bfb23&id=FE4038DA929BFB23!494419&authkey=!APmm0wzlSerRn04

It just got updated as I type, lol. 

Edited July 27, 2020 by dzontra

[iCanaro]

1 hour ago, Sbrillo said:

thank you!. It's so kind of you. I noticed slightly different on some quirks. But nothing change. Freq seems still a bit high. For the temperature, nothing change.

Can you please share your efi folder to see if I miss something? Maybe some drivers, or a table ACPI. I don't know.  

 

Here a screen from intel power gadget with the last changes made from your config.plist

 

create an SSDT for the custom PM for your CPU

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

[Matgen84]

4 minutes ago, eSaF said:

@Matgen84 - What version Lilu are we talking about here? Because I have ver:1.4.6

 

@eSaF I don't talk about Lilu but @Cyberdevs and @Sherlocks did.
 

Have a look to the commits today in the repo ! Lilu Beta 1.4.6 (7/27)

[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

[eSaF]

Nope!!! even with the Lilu version posted here I still need vsmgen=1 in boot-args to boot. Actually the only thing that is bugging me right now is the lack of BS showing in Startup Disk, all else is perfect as much as this Beta3 allows.

[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.

[eSaF]

@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.

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.

 

Same here

Edited July 27, 2020 by eSaF

[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?

[eSaF]

12 minutes ago, Cyberdevs said:

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

Lilu.kext.zip

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 

[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

[FirstTimeCustomac]

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?