X299 Big Sur Support

[NorthAmTransAm]

I'm looking for some help with Thunderbolt on my X299X Designare 10G platform.
I know this is the Big Sur topic and I'm running Catalina [for Pro Tools reasons].

You should head over to here. The answers are all in post one for you.

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

CaseySJ's Coffee Lake in Phanteks Evolv X ATX Case: Gigabyte Designare Z390 - i7-9700K - UHD 630 - AMD RX 580 (Please do not quote this build guide in its entirely. Post a link instead.) (See this post for how to refer to a Guide or Mini-Guide.) URGENT: Please avoid Clover 5123 and newer for...

www.tonymacx86.com

Also your intel wireless can be used now. Quite jealous! Its not fully functional but its' very close.

 

[jaspercat5]

The bios is configured correctly. I tried clean install from usb again but it always occurs KP arrived at the install screen. I don't think it's a problem with the 6900 XT but maybe some changes made by apple in beta 11.4 which maybe needs some new patch for the 299 platform.

I hoped my EFI and bios settings would solve your problems. I am running Beta4 and had no problems although it wasn't a clean install but an upgrade from Beta 3.

 

[BerndVP]

You should head over to here. The answers are all in post one for you.

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

CaseySJ's Coffee Lake in Phanteks Evolv X ATX Case: Gigabyte Designare Z390 - i7-9700K - UHD 630 - AMD RX 580 (Please do not quote this build guide in its entirely. Post a link instead.) (See this post for how to refer to a Guide or Mini-Guide.) URGENT: Please avoid Clover 5123 and newer for...

www.tonymacx86.com

Also your intel wireless can be used now. Quite jealous! Its not fully functional but its' very close.

Yeah I know about this,
I did a big read about Thunderbolt in that topic.
But my problem is something else I guess

 

[NorthAmTransAm]

Yeah I know about this,
I did a big read about Thunderbolt in that topic.
But my problem is something else I guess

What is your Thunderbolt issue?

 

[BerndVP]

What is your Thunderbolt issue?

Thunderbolt Expansion Chassis problems

Hi, I hope there are some smart people here who can try to figure out with me what is going wrong with my setup. So I'm a professional Audio Mixing Engineer and I have a studio. I'm using Avid Pro Tools Ultimate as my DAW along with an Avid HDX Card (DSP Based Audio PCIe 2.0 x4 card). For a...

www.tonymacx86.com

 

[egroys]

Has anyone ever had an issue installing the 10.15.7 Supplemental Updates? I am trying to do the latest one and I keep getting 'Some updates could not be installed automatically' when it boots back up.

I tried this several times:

• ran the update, it downloads
• asks to restart
• goes to the black apple screen and says one minute remaining
• then it restarts unusually fast
• Picker doesn't show any 'Install Mac OSX' options

Opencore 0.6.8 and never have had issues with updates before.

Any tips?

Thanks in advance!

 

[rustEswan]

Well it was a little more work than the previous MSI board but I would consider this ASUS PRIME X299-A II pretty much a "golden build" now with everything I've been able to test working:

• Native NVRAM
• Startup/Shutdown/Sleep/Wake
• USB ports all mapped and working even after sleep/wake
• Airdrop, handoff, iMessage all working perfectly

I've attached the EFI below, Platform Info and serials stripped of course, if you wanted to use this there are a few things to note:

• I have both AMD and Nvidia GPU's, you would need to remove SSDT-GPU-DISABLE and associated config.plist entries if not using a GPU that requires disabling.
• Also remove SSDT-GPU-RTX3070 and SSDT-GPU-RX560 these are just workarounds for displaying the correct device names in Big Sur when Device Properties method doesn't work
• You will need to adapt the Device Properties section of config.plist to correctly reflect your NVME drives, they will be different to mine
• Pay close attention to the SSDT-RHUB-Reset, SSDT-GPRW and the associated ACPI patch in the config.plist - without these I had issues with sleep and disappearing ASmedia USB controllers. They seem inter-related and I wasn't sure if the ASmedia USB was preventing sleep or sleep was breaking USB but further investigation led to this fix and it has since behaved perfectly.
• Modify TSCAdjustReset.kext to suit your actual CPU and number of cores, this EFI is set for the 14 core i9 10940X.
• Custom USB map (edit: now tested and working fine with 11.3 update) includes maps for every port on the board with the exception of one of the USB3.0 headers taking the Intel XCHI to the maximum 15 ports - it means that in my fractal case all of the external motherboard ports and front panel ports are all mapped with USB3 and USB2 personalities and no need for FakePCIID and re-routing USB2 ports to fake controllers. You may need to modify the map if using the internal USB2 headers for actual front panel Type A ports - I am using these for the NZXT AIO and Broadcom 94360CD bluetooth header. The map looks like so:

This is based around the latest UEFI BIOS version v1004 dated 19/4/21, where a setting isn't specified below, I've left it as default or its a specific setting for my system which you may need your own settings, (storage config or fan curves etc):

Ai Tweaker

• Ai Clock Tuner: XMP

Advanced

• CPU Config
  • All Enabled, except;
  • Max CPUID: Disabled
  • Boot Performance: Max Performance
  • MSR Lock Control: Disabled
  • CPU Power Management Config
    • EIST: Enabled
    • Turbo Boost: Enabled
    • Autonomous Core C-State: Enabled
    • Enhanced Halt (C1E): Enabled
    • CPU C6 Report: Enabled
    • Package C-state: C6 (non retention)
    • MFC Mode: OS Native
• Platform Misc. Config
  • All: Disabled
• System Agent Config
  • VT-d: Enabled (this will be disabled with the OpenCore config for MacOS so can be left on)
• PCH Storage Config
  • SATA Mode selection: AHCI
• PCI Subsystem Config
  • Above 4G Decoding: Enabled
  • Re-size BAR: Disabled (MacOS will not boot with this enabled at this time)
• Onboard Devices
  • Serial Port: Disabled
• USB Config
  • Legacy USB Support: Enabled
  • USB Mass Storage Support: Enabled

Boot

• Fast Boot: Enabled
• Above 4G Decoding: On
  • First VGA 4G Decode: Auto
• CSM (Compatibility Support Module)
  • Launch CSM: Disabled
• Boot Option #1: Opencore (you can set this after you're installed and the EFI is copied onto your NVME drive)

I still think there's life left in the X299 platform - even if it isn't anywhere near the performance of the latest Ryzen's and doesn't feature PCI-e 4, its still a very good multi-core platform if you need MacOS and Windows or Linux and for some people (although very niche of course) it might still be the ideal build and this is definitely a nice board with great features and compatibility.

Hope this is useful for somebody at least, and if you are an Asus user with sleep or strange USB issues, check out the Dortania guide on fixing sleep and GPRW patches, its what moved this into the prefect working category for me.

 

[cloudconnected666]

Hi guys!

I have X299 SAGE 10G and Radeon VII. I use this configuration for a long time. It worked with Catalina without problems. After upgrading to Big Sur I am having problems with my 10gbe. Only thing changed is OS upgrade and I added second Radeon VII card.

Everyhing looks like it works fine, but when I copy some pretty big files over 10gbe to my NAS, kernel panic happens. Not right away, but after some time, and this is how it looks like:

panic(cpu 6 caller 0xffffff801e6bf5a4): "Zone element 0xffffff93ddc0d800 was modified after free for zone kext.kalloc.512: " "Expected element to be cleared"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.81.3/osfmk/kern/zalloc.c:1963
Backtrace (CPU 6), Frame : Return Address
0xffffffc1bad5b020 : 0xffffff801debab4d
0xffffffc1bad5b070 : 0xffffff801dffd7e3
0xffffffc1bad5b0b0 : 0xffffff801dfede1a
0xffffffc1bad5b100 : 0xffffff801de5fa2f
0xffffffc1bad5b120 : 0xffffff801deba3ed
0xffffffc1bad5b240 : 0xffffff801deba6d8
0xffffffc1bad5b2b0 : 0xffffff801e6bef9a
0xffffffc1bad5b320 : 0xffffff801e6bf5a4
0xffffffc1bad5b330 : 0xffffff801df163aa
0xffffffc1bad5b360 : 0xffffff801df175d2
0xffffffc1bad5b3e0 : 0xffffff801dec8fc4
0xffffffc1bad5b430 : 0xffffff801e4444d3
0xffffffc1bad5b450 : 0xffffff7fbf0aa0ed
0xffffffc1bad5b4e0 : 0xffffff7fbf0b3f28
0xffffffc1bad5b580 : 0xffffff7fbf0b43c3
0xffffffc1bad5b5e0 : 0xffffff7fbf0b238c
0xffffffc1bad5bc00 : 0xffffff7fbf0b3e83
0xffffffc1bad5bc60 : 0xffffff7fbf0b4207
0xffffffc1bad5bcb0 : 0xffffff7fbf08c508
0xffffffc1bad5bd40 : 0xffffff801e17bf08
0xffffffc1bad5bdc0 : 0xffffff801e16cffd
0xffffffc1bad5be30 : 0xffffff801e4774e5
0xffffffc1bad5bee0 : 0xffffff801e477311
0xffffffc1bad5bf40 : 0xffffff801e5698cb
0xffffffc1bad5bfa0 : 0xffffff801de601f6
      Kernel Extensions in backtrace:
         com.apple.filesystems.smbfs(3.4.1)[25B4D36D-9E80-3737-A383-5C00EC04C221]@0xffffff7fbf066000->0xffffff7fbf0cffff
            dependency: com.apple.kec.corecrypto(11.1)[E009770B-BAFB-3BF9-B176-D6B4CC96DF5F]@0xffffff8021006000->0xffffff8021096fff
            dependency: com.apple.kext.triggers(1.0)[D4AC084E-97BE-37BC-BEB5-BE9A4BD1705D]@0xffffff7fbf0d4000->0xffffff7fbf0d6fff


Process name corresponding to current thread: YoYotta
Boot args: alcid=1 chunklist-security-epoch=0 -chunklist-no-rev2-dev


Mac OS version:
20D91


Kernel version:
Darwin Kernel Version 20.3.0: Thu Jan 21 00:07:06 PST 2021; root:xnu-7195.81.3~1/RELEASE_X86_64
Kernel UUID: C86236B2-4976-3542-80CA-74A6B8B4BA03
KernelCache slide: 0x000000001dc00000
KernelCache base:  0xffffff801de00000
Kernel slide:      0x000000001dc10000
Kernel text base:  0xffffff801de10000
__HIB  text base: 0xffffff801dd00000
System model name: MacPro7,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0


System uptime in nanoseconds: 103505388501548
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x00005e2339e9fd3c
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x0000001d81ba7a36 0x0000000000000000

YoYotta software mentioned in KP is just copy application... But it is the same when using other copy software (sometimes SMB share just unmounts, sometimes KP happens).

Anybody has any idea what could be the problem? @djlild7hina I am using your latest EFI (DJ7-OC068-WS X299 Sage 10G), just without two SSDTs that are GPU specific, and with RestrictEvents, like this:

Aaaand I was using your EFI for Catalina, and for few latest version. Thank you for your continuous help over the years

 

[chessa]

I hoped my EFI and bios settings would solve your problems. I am running Beta4 and had no problems although it wasn't a clean install but an upgrade from Beta 3.


View attachment 516285

Thank you for support. Problem has been solved.

It was the bios version 3405 that caused the KP. Loaded version 3302 and finally installation without problems of 11.4 beta 1.

Mac pro 7.1, no WEG, no string agdpmod = in boot args. Some first tests:

 

[NorthAmTransAm]

Well it was a little more work than the previous MSI board but I would consider this ASUS PRIME X299-A II pretty much a "golden build" now with everything I've been able to test working:

• Native NVRAM
• Startup/Shutdown/Sleep/Wake
• USB ports all mapped and working even after sleep/wake
• Airdrop, handoff, iMessage all working perfectly

View attachment 516382
View attachment 516383

I've attached the EFI below, Platform Info and serials stripped of course, if you wanted to use this there are a few things to note:

• I have both AMD and Nvidia GPU's, you would need to remove SSDT-GPU-DISABLE and associated config.plist entries if not using a GPU that requires disabling
• You will need to adapt the Device Properties section of config.plist to correctly reflect your NVME drives, they will be different to mine
• Pay close attention to the SSDT-RHUB-Reset, SSDT-GPRW and the associated ACPI patch in the config.plist - without these I had issues with sleep and disappearing ASmedia USB controllers. They seem inter-related and I wasn't sure if the ASmedia USB was preventing sleep or sleep was breaking USB but further investigation led to this fix and it has since behaved perfectly.
• Modify TSCAdjustReset.kext to suit your actual CPU and number of cores, this EFI is set for the 14 core i9 10940X.
• Custom USB map includes maps for every port on the board with the exception of one of the USB3.0 headers taking the Intel XCHI to the maximum 15 ports - it means that in my fractal case all of the external motherboard ports and front panel ports are all mapped with USB3 and USB2 personalities and no need for FakePCIID and re-routing USB2 ports to fake controllers. You may need to modify the map if using the internal USB2 headers for actual front panel Type A ports - I am using these for the NZXT AIO and Broadcom 94360CD bluetooth header. The map looks like so:

View attachment 516384
View attachment 516385

I still think there's life left in the X299 platform - even if it isn't anywhere near the performance of the latest Ryzen's and doesn't feature PCI-e 4, its still a very good multi-core platform if you need MacOS and Windows or Linux and for some people (although very niche of course) it might still be the ideal build and this is definitely a nice board with great features and compatibility.

Hope this is useful for somebody at least, and if you are an Asus user with sleep or strange USB issues, check out the Dortania guide on fixing sleep and GPRW patches, its what moved this into the prefect working category for me.

Bravo!

If things ever get hairy in Big Sur check the ASMEDIA ports. I found on my board that Big Sur identified it wrong and it would cause a panic on restart which in turn caused the driver to fail to load on the start. Here's the fix.

I didn't come up with it but I think all users should know about it.