[pre-release] macOS Big Sur

[tore2003]

7 hours ago, Cyberdevs said:

Yeah my Haswell refuses to boot, it ends up with KP regardless.

Mine is a Sandy Bridge, same thing.

[Taruga]

16 minutes ago, bad_colne said:

.how to remove "OCS: No scheme for BlacklistAppleUpdate at 3 index, context <Security>" from OpenCore boot?

 

 

OpenCore Changelog
==================

#### v0.6.0
- Fixed sound corruption with AudioDxe
- Fixed icon choice for Apple FW update in OpenCanopy
- Fixed APFS driver loading on Fusion Drive
- Added Comet Lake HDA device code
- Fixed audio stream position reporting on non-Intel platforms
- Added `Firmware` mode to `ResetSystem` to reboot into preferences
- Replaced `BlacklistAppleUpdate` with `run-efi-updater` NVRAM variable
- Fixed reset value in `FadtEnableReset` ACPI quirk
- Fixed freezes during boot option expansion with PXE boot entries
- Updated underlying EDK II package to edk2-stable202005
- Added `ProvideMaxSlide` quirk to improve laptop stability, thx @zhen-zen
- Fixed slide choice on platforms when 0 slide is unavailable, thx @zhen-zen
- Fixed assertions caused by unaligned file path access in DEBUG builds
- Renamed `ConfigValidity` utility to `ocvalidate` for consistency
- Added `GlobalConnect` for APFS loading to workaround older firmware issues

 

Just replace `BlacklistAppleUpdate` with `run-efi-updater` NVRAM variable

[Cyberdevs]

Installation went successfully on my Haswell rig with GigaByte GA-H97-D3H.

Here is my EFI (without SMBIOS info) if you are interested.

Spoiler

Haswell OC 0.6.0 Big Sur USB Installer.zip

 

 

16 minutes ago, tore2003 said:

Mine is a Sandy Bridge, same thing.

I've built the latest Lilu+WEG and it solved the KP. Check my EFI folder it might help you to boot into macOS Big Sur.

[black.dragon74]

@lottenow try to boot only with Lilu, WhateverGreen and VirtualSMC. It will work then. 

[dannyboy9]

Funny enough, my efi which I made for my system, gives me a SIGABRT error on the USB. How can I fix this

[black.dragon74]

1 minute ago, dannyboy9 said:

Funny enough, my efi which I made for my system, gives me a SIGABRT error on the USB. How can I fix this

Reset NVRAM or try using FakeSMC instead of VirtualSMC.

[manmo71]

2 minutes ago, black.dragon74 said:

Reset NVRAM or try using FakeSMC instead of VirtualSMC.

 

@black.dragon74

How can I RESET NVRAM?

I used to have that option during boot earlier, I dont know what I changed in the process of trying to resolve this boot from USB. 

Now I dont get the NVRAM Reset option at OC boot anymore.

 

How can I fix that?

[dannyboy9]

12 minutes ago, black.dragon74 said:

Reset NVRAM or try using FakeSMC instead of VirtualSMC.

nvram reset is always set to true, fakesmc didn't work

[Cyberdevs]

@manmo71

Make sure HideAuxiliary is set to NO in the config.plist so you get the NVRAM Reset Option in OC's picker.

 

Spoiler

 

[manmo71]

4 minutes ago, dannyboy9 said:

nvram reset is always set to true, fakesmc didn't work

My config.plist has AllowNVRAMReset=YES but still no luck, I tried FAKESMC in place of VirtualSMC but still end up in a loop with SIGABRT.

[dannyboy9]

i still haven't found a solution to that SIGABRT. Can't seem to understand what is causing it

[bad_colne]

1 minute ago, dannyboy9 said:

i still haven't found a solution to that SIGABRT. Can't seem to understand what is causing it

What ver of Lillu do you use? Whats the file size?

[manmo71]

Spoiler

 

@Cyberdevs I had enabled HideAuxillary=YES, making that NO fixed the missing Reset NVRAM option. Thank you.

[dannyboy9]

1 minute ago, bad_colne said:

What ver of Lillu do you use? Whats the file size?

Lilu will never be the problem. It's 1.2MB, i've built the latest one

[bad_colne]

Just now, dannyboy9 said:

Lilu will never be the problem. It's 1.2MB, i've built the latest one

I had the same problem and for me was Lillu with the 1.2MB filesize. I used another one that i was using with Clover that has 153KB and is working now.

[Alex HQuest]

6 hours ago, MacPato said:

Anyone with SIGABRT errors swap for FakeSMC and reset NVRAM

 

And where's the source or release of the latest FakeSMC code? Is it still RehabMan's one from 2018?

[EDIT] Or is it Slice's FakeSMC3 from 2019?

[EDIT 2] Neither works - manually resetting NVRAM and flipping from VirtualSMC to FakeSMC and FakeSMC3 still gives me SIGABRT every time.

Edited July 6, 2020 by Alex HQuest

[ham4ever]

Just now, dannyboy9 said:

i still haven't found a solution to that SIGABRT. Can't seem to understand what is causing it

yes same here, i tried all but none works

[RGarrido]

18 hours ago, SavageAUS said:

I think i'll wait for Dortania to update the guide. I cannot get the USB installer to work and i don't know what the KP means.
 

  Reveal hidden contents

 

EFI.zip

It was happening the same with me, but I rapidly realized it was the kexts. It’s something from the network or Bluetooth drivers, but I’ll try tomorrow 1 by 1 to see the problem. I’m using Intel AX200 and Realtek PCIe GB, with kexts “itlwmx” and “RTL8111”, respectively. As for the Bluetooth, I’m using “IntelBluetoothFirmware”

Coffee lake here

[lottenow]

1 hour ago, black.dragon74 said:

@lottenow try to boot only with Lilu, WhateverGreen and VirtualSMC. It will work then. 

 

Thank you so much @black.dragon74! I can finally boot to the installer of Big Sur.

 

I have created a partition on my M.2 SATA 1TB SSD, but none of the partitions including the SSD are showing up on either Install or Disk Utility.

 

Do I need any extra kexts to show APFS partitions/containers? I can only see the USB stick and Disk Image I am booting from.

 

Thanks in advance!

Edited July 6, 2020 by lottenow

[rianosx]

Hello friends, I'm trying to upload BigSur vanilla with an efi made available by a friend. But in the installation menu the hard drive is not recognized.

It doesn't even appear on diskutil actually.

 

My hardware:

I3-7020U

HD 620

HDD SATA

EFI.zip

[Max.1974]

23 minutes ago, lottenow said:

 

Thank you so much @black.dragon74! I can finally boot to the installer of Big Sur.

 

I have created a partition on my M.2 SATA 1TB SSD, but none of the partitions including the SSD are showing up on either Install or Disk Utility.

 

Do I need any extra kexts to show APFS partitions/containers? I can only see the USB stick and Disk Image I am booting from.

 

Thanks in advance!

 

Its possible share add plist for Fakesmc and the kext update? Thanks!!

[mnfesq]

Several people, myself, included, have stated here that they can boot to the installer but that the installer does not see any of their SATA drives.  Mine also does not see my M.2 SSD drive. It does, however, see any USB drives I connect to my laptop.  The boot log I see when I try to boot to the installer ends with this before going to the start menu of the installer:

IOAHCIBlockStorageDriver: could not recover SATA HDD after 5 attempts, terminating
disk0s1: no such device.
IOAHCIBlockStorageDriver: could not recover SATA HDD after 5 attempts, terminating
disk1s1: no such device.

I had the same problem when I booted into an installation of Big Sur made on a real Mac and, because of it, could not restore the installation to the partition on my SSD I had prepared for it.  Perhaps this is related to the UUID for the drives and that there is a check that can be bypassed with a boot arg.  Anyone?

[lottenow]

16 minutes ago, Max.1974 said:

 

Its possible share add plist for Fakesmc and the kext update? Thanks!!

 

 I have posted this here. My configuration is for Hades Canyon only, and I do not have FakeSMC, only Virtual SMC.

 

You can find the kexts compiled here, as there is a 10MB limit, which I am over when I upload mine.

[Cephalotus]

someone managed to solve the problem SIGABRT ? I tried to swap the virtualsmc for fakesmc but always gives this plist for virtualsmc not found

[Pavo]

11 minutes ago, Cephalotus said:

someone managed to solve the problem SIGABRT ? I tried to swap the virtualsmc for fakesmc but always gives this plist for virtualsmc not found

You should really know how to use OpenCore before going around and switching kext out. You must update the config.plist with whatever kext you are using.