[pre-release] macOS Big Sur

[arsradu]

6 hours ago, fusion71au said:

Just mount the Big_Sur Preboot volume, then delete/remove the boot.efi file from the hidden folder /System/Volumes/Preboot/UUID/com.apple.installer...

 

 

I see...  Didn't know that. Thank you!  

[htanh034]

Hi,

 

I have been using OpenCore 0.5.2 for a long time. Everything worked great here and I had no disadvantages. Now I have ventured for a new version (0.6.0).

Unfortunately, I now have the problem that I can no longer get into my BIOS. After pressing F2, the black screen (monitor is on) and the flashing stroke and mouse cursor (movable) come, but nothing else happens.

 

I have already read that I should reset the NVRAM in OpenCore, but unfortunately it didn't help.

I could also reflash the BIOS, but I would like to keep free as a last option that otherwise all settings will be lost.

 

Furthermore, I can't write NVRAM variables over the boot process, which means that after booting, self-set variables have disappeared again. I think both problems are related.

 

Main GIGA Z97M-D3H.

[nmano]

22 hours ago, Alex HQuest said:

You likely has something identified to macOS as a battery source (Corsair’s CommanderPro USB module is the most common), which reports 0% charge. This causes the installer to fail, since any battery below a certain threshold will cause the installer to fail, even on real Apple hardware.

Thanks @Alex HQuest I disconnect Corsair’s CommanderPro Now Its worked.

You save lots time for me.

Edited July 20, 2020 by nmano

[SavageAUS]

9 minutes ago, nmano said:

Thanks [mention=85724]Alex HQuest[/mention] I disconnect Corsair’s CommanderPro Now Its worked.
You save lots time for me.

And once your up and running you should be able to exclude that port if you choose to reconnect it.


Sent from my iPhone using Tapatalk

 

[ameenjuz]

8 hours ago, AppleBreak said:

When opting for DoNotSeal true, for some reason, I cannot delete snapshot following @fusion71au's great guide.  The system always returns with operation not permitted when trying to tag snapshot.  Please do let me know, how yours goes. Thanks.

@fusion71au Yes i have same issue

DoNotSeal true, for some reason, I cannot delete snapshot too after installation

following

operation not permitted when trying to tag snapshot

[aryaone]

so, after struggling for a week in order to modify IO80211Family.kext on S/L/E on big sur beta 1 (and never succeeded), today i decide to do clean installation big sur beta 2. then, surprise...!!! my dw1820a is fully working now, with latest airportbrcmfixup.kext and usual setting on config.plist/device properties (just like on catalina).
i'm so happy but still confused, is the big sur beta 2 fixing the IO80211Family.kext to support dw1820a/bcm94350?
 

[lottenow]

On 7/19/2020 at 1:01 AM, mnfesq said:

 

I have tried just about every possible configuration of OC and Clover.  With both bootloaders, I can boot to the USB installer or to a USB hard drive with an installation of Big Sur on it (made on a real Mac).  No matter what configuration I use, or what drivers I use or what kexts I use, or what DSDT/SSDT I use, I cannot get any of the plugins for IOAHCIFamily.kext to work. (I have a DVD drive on my laptop so both SATA and ATAPI devices cannot be read). At this point, I am thinking that the issue may likely be the BIOS on my HP laptop.  It cannot be configured and all advanced options are locked. However, SATA is set to AHCI so it should work.  I am at a loss to understand what to do next.

 

P.S. I took out my SATA hard drive and slipped it into a USB adapter and was able to install Big Sur on it. I then put it back into the SATA slot in the laptop and it could no longer be located when booting up.

 

@mnfesq: Hey, thanks for your sum up.

 

So, here is what I have tried so far:

 

1) Using SATA-100-unsupported.kext only

 

2) Using SATA-unsupported.kext only

 

3) Injecting pci8086,a103 under DeviceProperty

 

4) Both 3) + 1) and 3) + 2)

 

5) Booting without any SATA-related kext or property

 

6) Injecting solely pci8086,a102 (SkyLake spoof)

 

7) Injecting solely pci8086,9d03 (Laptop spoof)

 

None of the above seems to be working for me. I asked for more support from the OpenCore team on GitHub, but I do not have the required expertise to continue with what they are asking.

 

What SATA controller does your machine have? You can find this in Windows > Device Manager or under macOS using Hackintool, PCIE list. It contains both the Device Path (PciRoot...) and the Property Name (pci8086,a103 in my case).

 

Could it be that the APFS volume is somewhat sealed and therefore cannot be read by OC?

 

I think the problem lies with OpenCore as I cannot boot in Catalina with the latest commits using the same configuration as for Big Sur. I have to use a different OC configuration for Catalina. Again, I do not have the required knowledge to debug this.

 

Let me know your thoughts!

Edited July 20, 2020 by lottenow

[Guest ricoc90]

1 hour ago, aryaone said:

i'm so happy but still confused, is the big sur beta 2 fixing the IO80211Family.kext to support dw1820a/bcm94350?

Nah, latest airportbrcmfixup.kext injects the old Broadcom kexts. Wish I'd have found out about that sooner, lol

Edited July 20, 2020 by ricoc90

[mick3lson]

Someone has installed big sur on probook 4540s 1080p, I tried with "install Media HP Laptop OC" by chris1111, but I have kernel panic in the first stage of usb booting, I can't see the error because rebooting quickly.

[OrpheusInHell]

Anyone succeeded on a 3900x and a RX 5700 XT yet ? As soon as I add

agdpmod=pikera

, I go into the infamous SIGABRT loop 

[mnfesq]

2 hours ago, lottenow said:

 

@mnfesq: Hey, thanks for your sum up.

 

So, here is what I have tried so far:

 

Spoiler

1) Using SATA-100-unsupported.kext only

 

2) Using SATA-unsupported.kext only

 

3) Injecting pci8086,a103 under DeviceProperty

 

4) Both 3) + 1) and 3) + 2)

 

5) Booting without any SATA-related kext or property

 

6) Injecting solely pci8086,a102 (SkyLake spoof)

 

7) Injecting solely pci8086,9d03 (Laptop spoof)

 

None of the above seems to be working for me. I asked for more support from the OpenCore team on GitHub, but I do not have the required expertise to continue with what they are asking.

 

What SATA controller does your machine have? You can find this in Windows > Device Manager or under macOS using Hackintool, PCIE list. It contains both the Device Path (PciRoot...) and the Property Name (pci8086,a103 in my case).

 

Could it be that the APFS volume is somewhat sealed and therefore cannot be read by OC?

 

I think the problem lies with OpenCore as I cannot boot in Catalina with the latest commits using the same configuration as for Big Sur. I have to use a different OC configuration for Catalina. Again, I do not have the required knowledge to debug this.

 

Let me know your thoughts!

 

@lottenow and @PC IT: I have the Sunrise Point-LP SATA Controller (pci8086,9d03) (PciRoot(0x0)/Pci(0x17,0x0)).  This is the controller for both my SATA drives (HDD and M.2-SSD) and my ATAPI drive (DVD).  None of these drives can be detected when trying to boot to Big Sur.

 

At times, I will get boot messages that say that Serial ATAPI drive could not be properly configured and, after 3 of these messages, it will say that Serial ATAPI did not respond and the operation is terminated.  Sometimes, I will get a message that an HDD could not be read after 5 tries and that operation is terminated.  Sometimes, I do not get these messages but the boot process stalls with the last boot message saying something about AppleIntelPCHSeries, which is the name of the AHCI controller.

 

I do not believe it is related to an APFS volume because I have a HDD with an APFS volume but it also has a regular GUID partition that is formatted in HFS+ and that cannot be read/initialized either. I am advised that my SATA controller should work OOB so I don't think that device id injection will solve anything.  I'm also unsure of what options to include in any SSDT patch for the SATA controller other than compatible ids.  

 

I'm taking a break from this for a while because I spent way too much of my work time trying to solve this problem.  Please let me know if you have any breakthroughs.  Also, see if you can capture @MaLd0n's interest in this issue.  We may not have the collective expertise alone to resolve this.

[norton287]

I successfully got Big Sur to install with the new Clover 5120, but when I boot now it goes to a black screen instead of the apple logo and then the desktop.  It's all black.  I have a Saphire Pulse RX580 8GB, anyone get that working with Big Sur yet?  I have agdpmod=pikeralpha configure in the config.plist.  Had it there since Catalina.

 

Any help would be appreciated

 

John

EFI.zip

Edited July 21, 2020 by norton287
Attach EFI Folder

[ameenjuz]

1 hour ago, mnfesq said:

 

@lottenow and @PC IT: I have the Sunrise Point-LP SATA Controller (pci8086,9d03) (PciRoot(0x0)/Pci(0x17,0x0)).  This is the controller for both my SATA drives (HDD and M.2-SSD) and my ATAPI drive (DVD).  None of these drives can be detected when trying to boot to Big Sur.

 

At times, I will get boot messages that say that Serial ATAPI drive could not be properly configured and, after 3 of these messages, it will say that Serial ATAPI did not respond and the operation is terminated.  Sometimes, I will get a message that an HDD could not be read after 5 tries and that operation is terminated.  Sometimes, I do not get these messages but the boot process stalls with the last boot message saying something about AppleIntelPCHSeries, which is the name of the AHCI controller.

 

I do not believe it is related to an APFS volume because I have a HDD with an APFS volume but it also has a regular GUID partition that is formatted in HFS+ and that cannot be read/initialized either. I am advised that my SATA controller should work OOB so I don't think that device id injection will solve anything.  I'm also unsure of what options to include in any SSDT patch for the SATA controller other than compatible ids.  

 

I'm taking a break from this for a while because I spent way too much of my work time trying to solve this problem.  Please let me know if you have any breakthroughs.  Also, see if you can capture @MaLd0n's interest in this issue.  We may not have the collective expertise alone to resolve this.

format and try usb bootable with MBR

mine is working Sunrise Point-LP SATA Controller (pci8086,9d03)

 

 repartition /dev/disk1 MBR, two partitions
# first partition, "CLOVER EFI" FAT32, 200MiB
# second partition, "install_osx", HFS+J, remainder

diskutil partitionDisk /dev/disk3 2 MBR FAT32 "CLOVER EFI" 300Mi HFS+J "install_osx" R

sudo /Applications/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/install_osx

 

i attached my Patched DSDT and config

Compare your DSDT

DSDT-Config.zip

[aziiz3]

Hey guys, wanted to ask, does  Big Sur installer (DP2) can be booted on Laptop now with latest opencore and kext ? i've tried booting and always stuck at gIOLockscren smt smt. 

here i attached my EFI, please take a look at it and maybe you guys can see what might be wrong.

Thanks

 

Spoiler

 

EFI.zip

[Moviemakergr]

28 minutes ago, aziiz3 said:

Hey guys, wanted to ask, does  Big Sur installer (DP2) can be booted on Laptop now with latest opencore and kext ? i've tried booting and always stuck at gIOLockscren smt smt. 

here i attached my EFI, please take a look at it and maybe you guys can see what might be wrong.

Thanks

  

  Hide contents

 

EFI.zip

This screen is not gIOLockscren screen

when see again the gIOLockscren use -wegnoegpu boot flag.

Yours EFI is a "scary" EFI, better to talk with @MaLd0n to fix for you a DSDT

kexts use ONLY the absolutely necessary  on this phase.. 

[mnfesq]

3 hours ago, ameenjuz said:

format and try usb bootable with MBR

mine is working Sunrise Point-LP SATA Controller (pci8086,9d03)

 

 repartition /dev/disk1 MBR, two partitions
# first partition, "CLOVER EFI" FAT32, 200MiB
# second partition, "install_osx", HFS+J, remainder

diskutil partitionDisk /dev/disk3 2 MBR FAT32 "CLOVER EFI" 300Mi HFS+J "install_osx" R

sudo /Applications/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/install_osx

 

i attached my Patched DSDT and config

Compare your DSDT

DSDT-Config.zip

 

I tried as you suggested and while I was able to make a bootable USB drive following your instructions (thank you), it didn't solve the problem of not being able to detect SATA/ATAPI drives.  It did, however, slow down the boot process and I was able to see that long before I saw the messages about not being able to reconfigure my ATAPI drive or SATA not being able to see HDD after 5 tries, I got a boot message (2x) saying "couldn't alloc class "AppleIntelPchSeriesAHCI".  I'll be researching that for new ideas.

[ameenjuz]

7 minutes ago, mnfesq said:

 

I tried as you suggested and while I was able to make a bootable USB drive following your instructions (thank you), it didn't solve the problem of not being able to detect SATA/ATAPI drives.  It did, however, slow down the boot process and I was able to see that long before I saw the messages about not being able to reconfigure my ATAPI drive or SATA not being able to see HDD after 5 tries, I got a boot message (2x) saying "couldn't alloc class "AppleIntelPchSeriesAHCI".  I'll be researching that for new ideas.

i think that this is bug of Big Sur with Intel 100 series chipset controller

look at differences bitween Catalina and Big Sur

 

Big Sur shows Generic AHCI Controller

 

Spoiler

 

Catalina shows Intel 10 series chipset

 

Spoiler

we hope that Apple will be fixed in next release of Big Sur

[aziiz3]

2 hours ago, Moviemakergr said:

This screen is not gIOLockscren screen

when see again the gIOLockscren use -wegnoegpu boot flag.

Yours EFI is a "scary" EFI, better to talk with @MaLd0n to fix for you a DSDT

kexts use ONLY the absolutely necessary  on this phase.. 

 

I'll DM him, and by "scary" can you tell more about it ?

i declare -wegnoegpu using disable-external-gpu under Device Properties ? It's the same thing right ?

and yes, i've tried using minimal kext like applealc, lilu, vsmc and weg. It still stuck on gIOLockscreen.

[Stefanalmare]

7 hours ago, mick3lson said:

Someone has installed big sur on probook 4540s 1080p, I tried with "install Media HP Laptop OC" by chris1111, but I have kernel panic in the first stage of usb booting, I can't see the error because rebooting quickly.

 

OC.zip

[Moviemakergr]

3 hours ago, aziiz3 said:

 

I'll DM him, and by "scary" can you tell more about it ?

i declare -wegnoegpu using disable-external-gpu under Device Properties ? It's the same thing right ?

and yes, i've tried using minimal kext like applealc, lilu, vsmc and weg. It still stuck on gIOLockscreen.

Sorry about my english is plain.. Scary i mean very complicate,.with to many SSDT,for sure u need a DSDT..

For example i upload my success oc from my MSI laptop with the same CPU i7-9750H

I hope it helps you..

 

OC.zip

[lottenow]

4 hours ago, ameenjuz said:

i think that this is bug of Big Sur with Intel 100 series chipset controller

look at differences bitween Catalina and Big Sur

 

Big Sur shows Generic AHCI Controller

 

  Hide contents

 

Catalina shows Intel 10 series chipset

 

  Hide contents

we hope that Apple will be fixed in next release of Big Sur

I agree. It is either this or OC. Most likely a bug.

 

Would it be too big to ask for a copy of the kext from Big Sur so I can compare it to Catalina? You could zip it and attach it or PM it to me.

 

Also, what is your Device Path and Ioreg Path name for the Sata controller under both Big Sur and Catalina? You can check this from Hackintool > PCIe.

 

Thanks @ameenjuz!

Edited July 21, 2020 by lottenow

[hohoho]

10 hours ago, mnfesq said:

 

@lottenow and @PC IT: I have the Sunrise Point-LP SATA Controller (pci8086,9d03) (PciRoot(0x0)/Pci(0x17,0x0)).  This is the controller for both my SATA drives (HDD and M.2-SSD) and my ATAPI drive (DVD).  None of these drives can be detected when trying to boot to Big Sur.

 

At times, I will get boot messages that say that Serial ATAPI drive could not be properly configured and, after 3 of these messages, it will say that Serial ATAPI did not respond and the operation is terminated.  Sometimes, I will get a message that an HDD could not be read after 5 tries and that operation is terminated.  Sometimes, I do not get these messages but the boot process stalls with the last boot message saying something about AppleIntelPCHSeries, which is the name of the AHCI controller.

 

I do not believe it is related to an APFS volume because I have a HDD with an APFS volume but it also has a regular GUID partition that is formatted in HFS+ and that cannot be read/initialized either. I am advised that my SATA controller should work OOB so I don't think that device id injection will solve anything.  I'm also unsure of what options to include in any SSDT patch for the SATA controller other than compatible ids.  

 

I'm taking a break from this for a while because I spent way too much of my work time trying to solve this problem.  Please let me know if you have any breakthroughs.  Also, see if you can capture @MaLd0n's interest in this issue.  We may not have the collective expertise alone to resolve this.

i think i have the same exact sata controller as yours, if that information helps. i tried booting with clover v. 5120 but i get the same exact problems that i get with OC. i can boot to the installer like OC, but i still can't see all my internal drives even with using clover, but it boots catalina perfectly like OC.

pcidevices.txt

clover 5120 config.zip

Edited July 21, 2020 by hohoho

[gengik84]

@meaganmargaret 

Hi

i try again and work

1. first phase: boot from installer and i selected my disk named "test" for installation
2. after reboot, boot from installer again and open terminal window

Spoiler

 

 

 

i checked and UpdateOption.plist is present in "macoOS install data" folder

i try set to true/false and again true

always worked

6 hours ago, meaganmargaret said:

The error said at first, file does not exist, then file not found.

I don't know exactly but maybe the possible causes are:

1. you got the wrong command
2. the plist was not present
    

[MICKHAEL]

hello
just like @mnfesq @lottenow @hohoho, I have issues with detecting my ssd storage from big sur installer. in my case its a pci8086,a103.
guys, did you found a solution for that? or we could try to use IOAHCIFamily.kext from Catalina?

Edited July 21, 2020 by MICKHAEL

[aziiz3]

4 hours ago, Moviemakergr said:

Sorry about my english is plain.. Scary i mean very complicate,.with to many SSDT,for sure u need a DSDT..

For example i upload my success oc from my MSI laptop with the same CPU i7-9750H

I hope it helps you..

 

OC.zip

your english is fine, maybe better be blunt rather quoting scary

well i thought it's better hotpatching SSDT rather than using a single DSDT, incase there will be a bios update or hardware change. so you could boot bigsur installer ?

you are using smbios MBP15,2 rather than MBP16,1 for 9th gen any reason ? MBP15,2 supposed for 8th gen intel?

and how about this boot flag agdpmod=vit9696 ? doesn't it for a pc ?

Edited July 21, 2020 by aziiz3