Jump to content

[pre-release] macOS Big Sur

gengik84

By gengik84,
in New Releases and Updates

 Share
3,698 posts in this topic

Recommended Posts

luky35
luky35
Posted
Posted
12 minutes ago, subjectdenied said:

 

i have exactly the same issue, and this is the first time i saw it mentioned by someone else. what system are you on? i'm on a xps13 9380 FHD, using a amd 570x egpu and booting / installing to from a tb3 samsung xd5. i still try to update an existing and working OC based catalina with big.sur beta1. funny thing is, i had it already working on the internal ssd by using qemu to update catalina via vm-method, until it crashed pretty hard after some hours (i think because of an incompatible non hackintosh related kext) and i couldnt boot it again afterwards

I get the same with Big Sur on my Lenovo Skylake Desktop PC.
No one has offered a solution yet?

  • Like 1
Link to comment
Share on other sites
Blu24
Blu24
Posted
Posted (edited)
1 hour ago, hohoho said:

i made a new OC EFI and this new one is working perfectly now with Catalina but i still can't boot the Big Sur USB Installer with it though. Thanks!

updated OC running perfect in catalina but can't boot Big Sur.zip

20200710_162428.jpg

Hi hohoho,

Nice to see you making progress :thumbsup_anim:

You need to make a few changes but one step at a time.

Here is an excellent config.plist checker called "OpenCore sanity checker" it will tell you if you have the correct settings.

https://opencore.slowgeek.com

 

Are you using 0.5.9 or 0.6.0 ?

 

 

Edited by Blu24
  • Like 1
Link to comment
Share on other sites
hohoho
hohoho
Posted
Posted
7 minutes ago, Blu24 said:

Hi hohoho,

Nice to see you making progress :thumbsup_anim:

You need to make a few changes but one step at a time. Here is an excellent config.plist checker called "OpenCore sanity checker" it will tell you if you have the correct settings.

https://opencore.slowgeek.com

 

Are you using 0.5.9 or 0.6.0 ?

 

 

Thanks! Really appreciate your help! I downloaded opencore from github and then i used the build_oc.tool. Will try that out. Thanks!

Link to comment
Share on other sites
hohoho
hohoho
Posted
Posted
36 minutes ago, subjectdenied said:

 

i have exactly the same issue, and this is the first time i saw it mentioned by someone else. what system are you on? i'm on a xps13 9380 FHD, using a amd 570x egpu and booting / installing to from a tb3 samsung xd5. i still try to update an existing and working OC based catalina with big.sur beta1. funny thing is, i had it already working on the internal ssd by using qemu to update catalina via vm-method, until it crashed pretty hard after some hours (i think because of an incompatible non hackintosh related kext) and i couldnt boot it again afterwards

Acer Aspire 3 (A315-51-51B0)

Intel i5-7200u (intel hd 620)

12 GB ram

..i just started with Opencore and trying to run the Big Sur vanilla USB installer a few days ago. thanks!

Link to comment
Share on other sites
PG7
PG7
Posted
Posted
6 hours ago, mnfesq said:

 

Voici un dossier EFI fonctionnel. J'en ai essayé plusieurs et tous démarrent sur le programme d'installation, mais aucun ne me permet de voir mes disques internes.

 

mnfesq EFI.zip

 

test with this EFI and say if you already have the HDD all in the OC menu!

 

mnfesq OC HP.zip

Link to comment
Share on other sites
dariuxzy
dariuxzy
Posted
Posted (edited)
9 hours ago, pico joe said:

 

assumed you run script BigSur prelinkedkernel fix2.command or prelinkedkernel fix4  

see my post above

Not working. I don't understand why after running the script, the audio doesn't work anymore

 

EDIT. I use BigSur generic BKE.command, and now the audio work again

Edited by dariuxzy
Link to comment
Share on other sites
Blu24
Blu24
Posted
Posted (edited)
8 hours ago, Matgen84 said:

 

Any ideas to solve this issue. Please. (Z390 config of course)

can you upload your EFI. please remove your MBL,SystemUUID,System Serial Number info before you upload:)

would it be possible to add your hardware signature?

Edited by Blu24
Link to comment
Share on other sites
asapreta
asapreta
Posted
Posted

Hi All.

Big achievements for all the community these days, from recovery installation to USB Vanilla install.

 

My Big Sur is running from a USB install and at the first boot, using a Preamade EFI from Mald0n for the 300 series chipset the sound wasn't working. Then, I edited the config.plist and added the DSDT he shared previously for the Z390M Gaming Board and fixed the sound issue.

 

As I am no expert, are errors like these critical on the boot? 

2020-07-10 09:27:24.180397-0300 0x9b       Default     0x0                  0      0    kernel: (AppleAPIC) IOAPIC: Version 0x20 Vectors 64:87
2020-07-10 09:27:24.217597-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-07-10 09:27:24.217598-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-07-10 09:27:24.217872-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [\_SB_.PCI0.XHC_.RHUB.HS11]
2020-07-10 09:27:24.217873-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [\_SB_.PCI0.XHC_.RHUB.HS11]
2020-07-10 09:27:24.218482-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  Namespace lookup failure, AE_NOT_FOUND
2020-07-10 09:27:24.218483-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  Namespace lookup failure, AE_NOT_FOUND
2020-07-10 09:27:24.219366-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/dswload2-274)
2020-07-10 09:27:24.219367-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/dswload2-274)
2020-07-10 09:27:24.229218-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) 
2020-07-10 09:27:24.229219-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) 
2020-07-10 09:27:24.238435-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) No Local Variables are initialized for method ["\" ]
2020-07-10 09:27:24.238436-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) No Local Variables are initialized for method ["\" ]
2020-07-10 09:27:24.248882-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) 
2020-07-10 09:27:24.248883-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) 
2020-07-10 09:27:24.258123-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) No Arguments are initialized for method ["\" ]
2020-07-10 09:27:24.258124-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) No Arguments are initialized for method ["\" ]
2020-07-10 09:27:24.268451-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) 
2020-07-10 09:27:24.268452-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) 
2020-07-10 09:27:24.277654-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_NOT_FOUND,
2020-07-10 09:27:24.277654-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_NOT_FOUND,
2020-07-10 09:27:24.278333-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) During name lookup/catalog
2020-07-10 09:27:24.278334-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) During name lookup/catalog
2020-07-10 09:27:24.278922-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/psobject-310)
2020-07-10 09:27:24.278922-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/psobject-310)
2020-07-10 09:27:24.288899-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-07-10 09:27:24.288900-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-07-10 09:27:24.289173-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) Method parse/execution failed
2020-07-10 09:27:24.289173-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) Method parse/execution failed
2020-07-10 09:27:24.289849-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [\] (Node ffffff801410b780)
2020-07-10 09:27:24.289850-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [\] (Node ffffff801410b780)
2020-07-10 09:27:24.290460-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) , AE_NOT_FOUND
2020-07-10 09:27:24.290461-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) , AE_NOT_FOUND
2020-07-10 09:27:24.290781-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/psparse-632)
2020-07-10 09:27:24.290781-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/psparse-632)
2020-07-10 09:27:24.301038-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-07-10 09:27:24.301038-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-07-10 09:27:24.301312-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [\_SB_.PCI0.XHC_.RHUB.SS07]
2020-07-10 09:27:24.301313-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [\_SB_.PCI0.XHC_.RHUB.SS07]
2020-07-10 09:27:24.301922-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  Namespace lookup failure, AE_NOT_FOUND
2020-07-10 09:27:24.301922-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  Namespace lookup failure, AE_NOT_FOUND
2020-07-10 09:27:24.302806-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/dswload2-274)
2020-07-10 09:27:24.302806-0300 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/dswload2-274)

Thanks!

Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted

After booting I am finding this folder 'Recovered files' in the Bin, in the folder is a file named 'ContextStoreAgent.plist.tl3CjpV', even when I empty the Bin, after reboot it is there again. Didn't have this in Beta1 so I am just wondering if you guys know anything about it or how to get rid. This is a fresh USB vanilla install.

  • Confused 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted (edited)
42 minutes ago, Blu24 said:

can you upload your EFI. please remove your MBL,SystemUUID,System Serial Number info before you upload:)

would it be possible to add your hardware signature?

 

My hardware (Z390 Aorus Master) is already in my signature since one year. :P

 

EFI.zip

Edited by Matgen84
  • Haha 1
Link to comment
Share on other sites
greythorne
greythorne
Posted
Posted
29 minutes ago, eSaF said:

After booting I am finding this folder 'Recovered files' in the Bin, in the folder is a file named 'ContextStoreAgent.plist.tl3CjpV', even when I empty the Bin, after reboot it is there again. Didn't have this in Beta1 so I am just wondering if you guys know anything about it or how to get rid. This is a fresh USB vanilla install.

 

I had  those in Beta 1 too. Now in Beta 2 also same. After reboot, i will see the recovered files in the Bin.

Link to comment
Share on other sites
greythorne
greythorne
Posted
Posted
6 hours ago, hohoho said:

i made a new OC EFI and this new one is working perfectly now with Catalina but i still can't boot the Big Sur USB Installer with it though. Thanks!

updated OC running perfect in catalina but can't boot Big Sur.zip

20200710_162428.jpg

 

Please refer to my post few pages back. Had the exact same issues. Realized that the Lilu.kext is the issue. Compiled the latest Debug and problem was solved! No idea why when i compiled the latest release version got the same error.

  • Like 2
Link to comment
Share on other sites
eSaF
eSaF
Posted
Posted
10 minutes ago, greythorne said:

 

I had  those in Beta 1 too. Now in Beta 2 also same. After reboot, i will see the recovered files in the Bin.

You may have a point there because I just swopped out the EFI Folder for the one I used in Beta1, rebooted, cleaned the NVRAM and now all is well so what ever it was is gone. :thumbsup_anim:

  • Like 1
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted (edited)

It is with great pride that I announce the boot on the HP ProBook 6570B With the latest OpenCore Boottloader

I just say thanks to the DEVS and all friends Users:wink_anim:

 

 

IMG_2255.thumb.jpeg.1bcc0cb57a1cab70cd9ff8c86aa838d9.jpegIMG_2256.thumb.jpeg.2721311110c8e9d9af73394a37b39993.jpeg

Edited by chris1111
  • Like 5
Link to comment
Share on other sites
jsl2000
jsl2000
Posted
Posted
16 minutes ago, greythorne said:

 

Please refer to my post few pages back. Had the exact same issues. Realized that the Lilu.kext is the issue. Compiled the latest Debug and problem was solved! No idea why when i compiled the latest release version got the same error.

Thanks for this info.

Can you share the Debug version of Lilu of 1.4.6 ?

Link to comment
Share on other sites
crazybirdy
crazybirdy
Posted
Posted
10 minutes ago, chris1111 said:

It is with great pride that I announce the boot on the HP ProBook 6570B With the latest OpenCore Boottloader

I just say thanks to the DEVS and all friends Users:wink_anim:

 

 

IMG_2254.jpeg

 

Good news.

 

I just figure out... boot with CLOVERX64.efi (Big Sur from someone) can reach to this installer screen too.

But it's complicated, need to modify BaseSystem.dmg.:wallbash::hysterical:

 

  • Like 2
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted
Just now, crazybirdy said:

 

Good news.

 

I just figure out... boot with CLOVERX64.efi (Big Sur from someone) can reach to this installer screen too.

But it's complicated, need to modify BaseSystem.dmg.:wallbash::hysterical:

 

Thanks I know but you have the skill to succeed I trust you :guitar:

  • Like 4
Link to comment
Share on other sites
Blu24
Blu24
Posted
Posted (edited)
1 hour ago, Matgen84 said:

 

My hardware (Z390 Aorus Master) is already in my signature since one year. :P

 

EFI.zip

There is a lot that needs to be fixed. if you still have issues I can configure it for you but it’s better if you do it.

 

To be corrected:

Please delete all archived and disabled folders

 

  • SSDT-EC-USBX(disabled) is missing from your ACPI folder also you have not injected your config.plist folder.
  • Set to true AppleCpuPmCfgLock, AppleXcpmCfgLock,ApplePanic
  • ScanPolicy set to 0
  • Remove: booter-fileset-kernel booter-fileset-basesystem(not needed for 0.6.0 issue has been addressed)
  • boot-args: -v keepsyms=1 debug=0x100 alcid=1 slide=1
  • -lilubetaall (not needed for 0.6.0 issue has been addressed)

Let me know how you get on

 

 

Edited by Blu24
Link to comment
Share on other sites
crazybirdy
crazybirdy
Posted
Posted (edited)
13 hours ago, chris1111 said:

Thanks I know but you have the skill to succeed I trust you :guitar:

 

I have to use Clover to install Big Sur, cause of I can't make OC work with my hack.:(

 

--

Bad news.

 

Now Clover can reach the installer screen, and finish the stage 1 to make target volume with macOS Install Data.

But stop while loading /macOS Install Data/Locked Files/BootKernelExtensions.kc

 

I think, Clover can't load BootKernelExtensions.kc, if it works with BootKernelExtensions.kc, then Clover can install Big Sur from full installer app.

 

Edited by crazybirdy
  • Like 4
Link to comment
Share on other sites
greythorne
greythorne
Posted
Posted
3 minutes ago, jsl2000 said:

Thanks for this info.

Can you share the Debug version of Lilu of 1.4.6 ?

 

Attached is the Kexts i used for booting BS in USB. After complete install I used back release version of Lilu.kext.

Also in the zip file I included Lilu, WEG, VSMC & ALC. WEG, VSMC & ALC compiled against Debug version of Lilu.kext.

 

Kexts.zip

  • Like 2
Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...