[pre-release] macOS Big Sur

[corint1]

1 minute ago, dvil said:

I have the exact same problem. I've tried all the combinations that I can think off (beta1, beta 2, different OC builds, parameters and kexts combinations)  with no success so far.

 

Any hint to solve this problem is very welcome   

post yor config.plist

[Alex HQuest]

5 minutes ago, manmo71 said:

I have everything working, Graphics both Radeon RX580 and the headless iGPU, audio, USB, WiFi and bluetooth.

Does your system plays DRM content (Netflix/Prime Video/Apple TV+)? If so, which kext's and/or boot-args are you using?

[manmo71]

Just now, Alex HQuest said:

Does your system plays DRM content (Netflix/Prime Video/Apple TV+)? If so, which kext's and/or boot-args are you using?

@Alex HQuest I have not tried that as I do not use any of them, but I do have Prime Video. Shall try and update you.

[dvil]

11 hours ago, corint1 said:

post yor config.plist

Attached, thanks!

 

Property List.plist

config.plist

Edited July 9, 2020 by dvil
NVRAM file added

[manmo71]

14 minutes ago, Alex HQuest said:

Does your system plays DRM content (Netflix/Prime Video/Apple TV+)? If so, which kext's and/or boot-args are you using?

@Alex HQuest I just checked out Prime Video and it works fine. No issues.

Here is the screenshot of my config.plist, it includes the kernel section to show you the kexts that I am loading and also the NVRAM section to see the boot-args for yourself if this helps.

 

If you are attempting to install from a USB, just ensure that you do the following in order

• RESET NVRAM
• On reboot Select the boot device as OPENCORE
• Now choose macOS BETA INSTALL

I trust things will go smooth.

 

Spoiler

 

 

Edited July 8, 2020 by manmo71
Some additional info

[DarkNeptune0]

I'm in the installer, is it better to erase the disk and install or just update?

[XnL]

28 minutes ago, dvil said:

I have the exact same problem. I've tried all the combinations that I can think off (beta1, beta 2, different OC builds, parameters and kexts combinations)  with no success so far.

 

Any hint to solve this problem is very welcome   

I was having that problem. what i did was populate all the platform info on config.plist (including firmware features  etc as in samplefull.plist when you download opencore release). also i disable acpi patches that weren´t necessary on ACPI section in config.plist(  leaving only EC patch). After that dont boot macos installer partiton if you have it, boot the usb installer and reinstall from it again then if that is sucessful boot the macos installer partion and let it do its thing it will reboot sometimes if it works.

Give it a try.

[Alex HQuest]

36 minutes ago, manmo71 said:

@Alex HQuest I just checked out Prime Video and it works fine. No issues.

 

 

Thanks for the suggestions. I ended changing my model from iMac19,2 to iMacPro1,1. Read on a translated place things work better with this model instead, and hey presto, works first time.

[dannyboy9]

31 minutes ago, DarkNeptune0 said:

I'm in the installer, is it better to erase the disk and install or just update?

You can just update

[PG7]

hello, installation of BigSur Beta Dev 1 and 2 from a USB installer.

- the first part passes (3 minutes) restarts, part 2 (29 minutes stays for a long time in "less than 1 minute") then restarts and then we have the problem !!! impossible to enter from that state 3!

I've tested everything between the latest kext and the last OpenCore but nothing works!

 

I tested both on the Broadwell HP EliteBook 820 G2 intel core i5-5300U hd 5500 chip = USB error but with the restoration of the image dmg to the HDD the OpenCore Boot works on BigSur and also on Catalina!

 

tested on HP Probook 430 G2 intel i3-5010U HD5500 same result as the first one (boot OK with BigSur restored from an image dmg and on Catalina this is also OK)

 

lastly tested also on the ivy bridge Dell Vostro 2520 intel i3-3110M HD4000

in this I go further with all the steps but at the second reboot (after installation) it simply gives me a display and reboot error

 

I haven't seen anyone anywhere that has successfully installed one of these chips

 

any tips or even resolution, opinions to be able to test I will be willing to do it; sure already for me and other community

 

thank you all

sorry my weak english because i am using google translator,

Languages I know Portuguese and Français

[manmo71]

Spoiler

 

@pg7 add in boot-args vsmcgen=1

If you are attempting to install from a USB, just ensure that you do the following in order

• RESET NVRAM
• On reboot Select the boot device as OPENCORE
• Now choose macOS BETA INSTALL

Try a fresh install again. I too was stuck like you, finally got it to work....

 

Edited July 8, 2020 by manmo71

[Andrey1970]

8 minutes ago, manmo71 said:

add in boot-args vsmcgen=1

vsmcgen=1 not needed with last Lilu from the master.

[manmo71]

Spoiler

 

@Andrey1970 Thank you for that update. 

[DarkNeptune0]

After the 3 minutes the computer reboots, I choose the data partition and after some time it stops here: is this normal or do you have to start again?

[dannyboy9]

10 minutes ago, Andrey1970 said:

vsmcgen=1 not needed with last Lilu from the master.

Thanks for the update. Building the new one right away.

 

When I try to build WEG, it builds resource converter. What am I possibly doing wrong here?

Edited July 8, 2020 by dannyboy9

[PG7]

56 minutes ago, manmo71 said:

  Révéler le contenu caché

 

@ pg7ajouter dans boot-args vsmcgen = 1

Si vous essayez d'installer à partir d'une clé USB, assurez-vous simplement de faire ce qui suit pour

• RÉINITIALISER LA NVRAM
• Au redémarrage Sélectionnez le périphérique de démarrage comme OPENCORE
• Maintenant, choisissez macOS BETA INSTALL

Essayez à nouveau une nouvelle installation. Moi aussi j'étais coincé comme vous, enfin ça a fonctionné ....

 

4 Install = Probleme idem BigSur DEV Beta 1 & BigSur DEV Beta 2 Idem .... 

[MorenoAv]

I'm back with a fresh install 5 reboot's and it's done... grabbed a copy of macOS Big Sur Beta 2 with the script from @crazybirdy, and tried to install that, but no dice...

Then removed one of my ssds from my hack and grabbed an EFI from Olarila made by @MaLd0n and booted from it.

At this moment I'm writing this from my new install... 

 

Many thanks to both, and to all that contribute and work for the community...

PS: As you can see in the photo below, I'm now an iMac Pro...

[Rocky12]

I'm trying to boot from Clover mod Big Sur beta 2 USB Installer but getting those errors 

service exited due to SIGABRT

service exited due to SIGIL L

Spoiler

 

[lottenow]

I am still trying to wrap my head around why Big Sur cannot load internal disks.

 

Has anyone found a solution yet?

[DarkNeptune0]

Apparently the problem is that the installer does not write any files, when rebooting after 3 minutes there is no new entry and the hard drive is still blank

[lottenow]

Here is my EFI with screenshots attached. Did I get my ACPI wrong?

 

I cannot understand whether the problem is related to Big Sur or Open Core or my configuration.

 

Thanks!

EFI Big Sur Beta 2.zip

BC6FD638-F481-49B0-A729-9297CA06A008.heic

CB153E89-D5CE-4398-BEEB-97675A9D2FC7.heic

[mnfesq]

16 minutes ago, lottenow said:

I am still trying to wrap my head around why Big Sur cannot load internal disks.

 

Has anyone found a solution yet?

 

No luck here but I have made some advances in my understanding of the problem.  The problem lies with the new AHCIFamily.kext and more particularly the IOAHCIBlockStorageDriver.kext.  It simply cannot read the internal drive information.  I tried using the AHCIPortInjector.kext but it did not solve the problem.  The problem is NOT that it cannot read internal vs. external drives.  The problem is that Big Sur cannot read SATA drives (i.e., drives physically connected to PRT.). You can see this if you use IORegExplorer.  I am thinking that this problem is not related to our hardware but I can't say for sure.  I have the Intel Series 10 chipset.  I have a custom DSDT and, among other things, I changed all references from SAT0 to SATA.  Without my custom DSDT, I cannot boot to Big Sur at all so I can't really test whether the problem is in some DSDT patch(es).  I also tried changing the SMBIOS from my usual MBP14,3 to iMac19,2 but also without success.  I was thinking that Apple might not allow internal drives that do not belong on that Mac model.   I may still try some type of MacPro since it can have a variety of internal drives.  I was asked by @SavageAUS if I could use a hot-plug SATA port but alas, my laptop does not have one to test that out.  BTW, my BIOS has very few options but, by default, it is set to AHCI, not IDE or RAID.  In fact, there is no option to change the SATA settings.  That's where I am so far.  I have not given up but I have spent way too many hours this month not working so that I could try to figure this out.

[PG7]

14 hours ago, lottenow said:

...

? 

 

13 hours ago, mnfesq said:

...

HP Envy Recline 23 Haswell Boot Clover Quirks!

 

[dariuxzy]

10 hours ago, eSaF said:

@dariuxzy - To get past that point (constant re-boots) I had to find and download Beta2 independently and then directly update over Beta1. The Inbuilt Updater gave me that error so I had to use the fore mentioned work around. Good luck.

Ok thanks. I'll try

[lottenow]

13 hours ago, mnfesq said:

 

No luck here but I have made some advances in my understanding of the problem.  The problem lies with the new AHCIFamily.kext and more particularly the IOAHCIBlockStorageDriver.kext.  It simply cannot read the internal drive information.  I tried using the AHCIPortInjector.kext but it did not solve the problem.  The problem is NOT that it cannot read internal vs. external drives.  The problem is that Big Sur cannot read SATA drives (i.e., drives physically connected to PRT.). You can see this if you use IORegExplorer.  I am thinking that this problem is not related to our hardware but I can't say for sure.  I have the Intel Series 10 chipset.  I have a custom DSDT and, among other things, I changed all references from SAT0 to SATA.  Without my custom DSDT, I cannot boot to Big Sur at all so I can't really test whether the problem is in some DSDT patch(es).  I also tried changing the SMBIOS from my usual MBP14,3 to iMac19,2 but also without success.  I was thinking that Apple might not allow internal drives that do not belong on that Mac model.   I may still try some type of MacPro since it can have a variety of internal drives.  I was asked by @SavageAUS if I could use a hot-plug SATA port but alas, my laptop does not have one to test that out.  BTW, my BIOS has very few options but, by default, it is set to AHCI, not IDE or RAID.  In fact, there is no option to change the SATA settings.  That's where I am so far.  I have not given up but I have spent way too many hours this month not working so that I could try to figure this out.

Thanks for the thorough explanation @mnfesq!

 

Yes, I think the problem lies with the system and the way our ACPIs are configured.

 

Would you mind sharing your EFI folder? What SSDs models are you using?

 

The fact that the SSD does not match the model of the actual SMBIOS is unrelated IMO, as MacBooks and MacMini have different models than what Hackintosh users use anyhow, and they still manage to boot.

 

I tried enabling ThirdPartyDrives as well as TRIM, but that didn't make any difference.

 

I am now trying to see whether I could potentially use the kext from the latest Catalina release, but I obviously get a KP as it is pre-linked in Big Sur. I have already copied this in Kexts, as well as enabling them under Kernel.

 

Is there a way to block a kext from loading in OC or bypass this?

 

Thanks in advance!