Contribute
Register

X299 Big Sur Support

Status
Not open for further replies.
I suspect you don't use the latest OC :

jya7980xe:~ jyavenard$ nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version REL-064-2020-11-13
jya7980xe:~ jyavenard$

Definitely the latest, unless a new one came since yesterday !

I did carry the config.plist across from the original OC 0.6.0 beta back from July.

I'll update with yours to test, thanks for your answer.

JY
As you can see on the screen shot below : (left yours right mine)
Under kernel / quirks : there is no ExtendBTFeatureFlags but DummyPowerManagement (no more used now)
But the structure of your EFI file is close to mine shared a few post before (same I used on my Prime Deluxe).

View attachment 495804

Also under NVRAM there are some different entries and missing csr-active-config <00000000>

View attachment 495805
 
I managed to take a photo right before it reboots:
PXL_20201114_110541164.jpg


Doesnt help much at this stage.

I also tried the OC folder provided by arkanis above, after only modifying the boot option to make the AMD 5700XT work, I get exactly the same outcome, immediate reboot.

It's weird, I had it booting much further just 2 months ago, and I didn't change much since.
 
Last edited:
I don’t have any Battery power.
I have corsair commander pro
Energy saver show current charge 0%
How to disabled this UPS?
Screen Shot 2020-11-14 at 7.16.41 AM.png
Screen Shot 2020-11-14 at 7.06.33 AM.png


Screen Shot 2020-11-14 at 7.05.40 AM.png
 
@salvatore.polito ciao Salvatore!
We got the same board, I’m having issues with audio. It works perfectly fine wherever, but when I do a phone call via my iPhone it goes kernel panic with some HDA Kexts related to coreaudiod process. It’s strange I can perfectly use onboard audio for everything but phone calls, this occurs only with Big Sur. Could you please check if your board causes the same issue? I’m on latest OC, Lilu and AppleALC and I use device property injection to insert layout id 7. Keep in mind I’m on 2002 bios, did u updated to the latest? In case I update, should I switch SSDT-RTC to the one built for latest bios? Where can I find it?

obviously everyone can contribute

i got another issue with DRMs in Netflix and Prime Video, but it seems a widespread issue even on real macs. Anyway I tried everything with my Radeon VII on MacPro7,1 and WEG on/off and shikigva 128 in device properties

HELP! :banghead::banghead::banghead:
 
Yes of course I can restart on the disk of my choice: Big Sur or Catalina or Windows
Then the computer shuts down and reboots, but the only requirement to reboot to the selected disk as far as I know is that this disk should be set as the priority of the boot disk over the bios.
Sorry but I don't understand where you want to end up here my friend.
The only thing I know since the first BS beta : I can not install Big Sur directly from Catalina or Mojave by select another disk : don't work.
@Loloflatsix: Are you saying we cannot "upgrade" our Catalina disk to Big Sur? And we have to install Big Sur on a newly formatted APFS drive? Please confirm. Thanks!
 
I have a problem after updating to Release BigSur. After restarting the Asus I get an Error 97. Does any of you with X299 do that too?
 
Finally after two days of research, test n trials I manage to install BigSur on Asus R6E. Cannot use the latest firmware (3105 & 3210) though.

Screenshot_2020-11-14_at_8_14_07_PM.png
 
@salvatore.polito ciao Salvatore!
We got the same board, I’m having issues with audio. It works perfectly fine wherever, but when I do a phone call via my iPhone it goes kernel panic with some HDA Kexts related to coreaudiod process. It’s strange I can perfectly use onboard audio for everything but phone calls, this occurs only with Big Sur. Could you please check if your board causes the same issue? I’m on latest OC, Lilu and AppleALC and I use device property injection to insert layout id 7. Keep in mind I’m on 2002 bios, did u updated to the latest? In case I update, should I switch SSDT-RTC to the one built for latest bios? Where can I find it?

obviously everyone can contribute

i got another issue with DRMs in Netflix and Prime Video, but it seems a widespread issue even on real macs. Anyway I tried everything with my Radeon VII on MacPro7,1 and WEG on/off and shikigva 128 in device properties

HELP! :banghead::banghead::banghead:
I've updated to the latest 3006 bios and proper SSDT-RTC, but it still kernel panics with phone call via iPhone, and sometimes when I wake up from sleep it panics too. For both KP types, the report clearly indicates issues with AppleALC (which worked super ok prior to Big Sur). That's crazy. @salvatore.polito

Edit: I checked IOReg and all the AppleHDA stuff seems to be correctly patched.
 
Last edited:
macOS Big Sur installation steps :

Reminder post #1 & post #2

1/ Launch directly install macOS Big Sur if you have a previous public beta installed - Open Core 0.6.3 is required

View attachment 495129


2/ Select the disk "Big Sur"

3.1 / Wait during the installation process until your computer restart

View attachment 495130

View attachment 495131

3.2 / First reboot : at gui boot screen select Macintosh HD (not Big Sur) : the installation process will continue in verbose mode mode during about 4 or 5 minutes (lots of verbose pages ...)

View attachment 495132


3.3 / Second reboot : at gui boot screen select Big Sur : installation process will continue with Apple Logo about 2 or 3 minutes the progress bar will be short

3.4 / Third reboot : at gui boot screen select Big Sur : the installation first ends in verbose mode and after the log screen will appear: you are done

( Not tested on X299 build yet with USB installer only in my old H87 build but it must also work for our system)
Can you elaborate "3.2 /" step ?
"Macintosn HD" is the Hard Drive with "Installer macOS Big Sur" within its Application Folder, isn't it ?
We mustn't chose the "macOS installer" at gui boot screen on this step ??
I'm confused ....
Any explanation is welcome
thanks
 
I managed to take a photo right before it reboots:
View attachment 495808

Doesnt help much at this stage.

I also tried the OC folder provided by arkanis above, after only modifying the boot option to make the AMD 5700XT work, I get exactly the same outcome, immediate reboot.

It's weird, I had it booting much further just 2 months ago, and I didn't change much since.

So if I understand you can not reboot after the first stage : you can first boot the installer , select your install disk and after the first process , you are stuck at reboot ?
 
Status
Not open for further replies.
Back
Top