X299 Big Sur Support

mrt1976 said:

@tedyun , @CaseySJ, @djlild7hina @tucoboy ok - so I'm (or was) back up and running with the 1070ti in High Sierra. I must have been missing something in the BIOS settings. However, I can't run the 6900 XT in Big Sur.

I retried installing the 6900 XT. When I plugged it in, I got the same Detect HDD in the MB display. It wouldn't load BIOS.

I reset CMOS.

Changed the BIOS back to those at the start of this thread. I got the same Detect HDD in the MB display.

Do you know what's happening here?

Thanks in advance,

Nick

Click to expand...

Check your bios settings here ( mandatory Above 4G decode enable and CSM disable) : X299 Big Sur Support #1

( You need OC 0.7.4 edit carefully according to OpenCore Install Guide and your configuration )

CaseySJ said:

On X99 and X299 motherboards it may not be necessary to modify the DMAR SSDT. Simply try the first 3 bullets in the following post:

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

That totally sounds like a plan! Thanks — will try shortly. I'm using it on Monterey and looks like it fixed the issues when AirDrop Continuity Handoff, Connection to AirPods Pro, RSSI stopped working after wake-from-sleep If Apple gives us back Bluetooth API in next Monterey versions I can...

www.tonymacx86.com

After rebooting, check if AppleVTD appears near the top of IORegistryExplorer. Also check if WiFi and Ethernet are still able to connect (i.e. actually connect to a network).

Click to expand...

@CaseySJ and @yosoyoco I have a question about the GA-X299-Designare EX and Thunderbolt NHI / Networking support. Running 0.7.5.

I have a 100% working EFI for Catalina (attached), including NHI for the Antelope Orion Studio 2017 which I'm trying to support in Big Sur.

The problem lies in Big Sur. With the same EFI WiFi and Ethernet drop out. I'm missing one reference where CaseySJ talked about this, can't find it.

I enabled AppleVTD by enabling Vt-D and disabling the DisableIOMapper quirk. It's recognized in IORegistryExplorer in both 10.15 and 11.6

So, I came to this point by already disabling all the unchecked kexts and ACPI SSDT and patches in the attached EFI. I mean to say the same problem exists with all these on enabled for Big Sur.

Except when I add the SSDT-DMAR for Z390 Designare to the mix. It fixes the dropping networking in 11.6 but disables parts of the Antelope interface, which makes it "undetected" (it shows up with errors in verbose, though). This is in the attached EFI configuration which works for Catalina.

When I enable all disabled ACPI SSDT and Patches in attached EFI, Big Sur has no networking drops and shows a lot of Antelope news in verbose, but in the and can't see the Orion Studio 2017.

I feel like I'm close. There seems a need to restrict the loading of the SSDT-DMAR (at least the Z390 one) to Big Sur, because it breaks my goal in Catalina.

So my question really is whether you could have a new look at the X299 Designare EX SSDT-DMAR.aml which I uploaded previously, to see whether it can be fixed properly, if that is what makes the difference. Only doing the first three bullets of the Z390 Designare procedure doesn't cut it in 11.6 apparently. Am I missing something, or is this where we should look for a solution?

I looked at the DMAR editing procedure but couldn't figure out how to patch this one, to be honest.

Cheers!

mrt1976 said:

@tedyun , @CaseySJ, @djlild7hina @tucoboy ok - so I'm (or was) back up and running with the 1070ti in High Sierra. I must have been missing something in the BIOS settings. However, I can't run the 6900 XT in Big Sur.

I retried installing the 6900 XT. When I plugged it in, I got the same Detect HDD in the MB display. It wouldn't load BIOS.

I reset CMOS.

Changed the BIOS back to those at the start of this thread. I got the same Detect HDD in the MB display.

Do you know what's happening here?

Thanks in advance,

Nick

Click to expand...

Hey MRT, I was thinking since you have the same original version Prime X299-DELUXE (ver. 1) mobo and AMD 6900XT GPU, then why don't you use my EFI file that is now running OC 0.7.4 and make sure you set up the BIOS exactly the way Loloflax and djlild7hina have instructed (link provided below):


and you should be up and running fine... maybe. Can't hurt right? I would try it. Just download my EFI from page 251 / Post #2510. Hope it helps.

tucoboy said:

Hey MRT, I was thinking since you have the same original version Prime X299-DELUXE (ver. 1) mobo and AMD 6900XT GPU, then why don't you use my EFI file that is now running OC 0.7.4 and make sure you set up the BIOS exactly the way Loloflax and djlild7hina have instructed (link provided below):

ASUS-X299-Hackintosh/BASE-EFI at main · shinoki7/ASUS-X299-Hackintosh

Contribute to shinoki7/ASUS-X299-Hackintosh development by creating an account on GitHub.

github.com

and you should be up and running fine... maybe. Can't hurt right? I would try it. Just download my EFI from page 251 / Post #2510. Hope it helps.

Click to expand...

@tedyun , @CaseySJ, @djlild7hina @tucoboy, @Loloflatsix

Thanks for the reply. I'll try this. The trouble I'm having at the moment is that the HDD doesn't seem to be recognised after I've updated the BIOS settings according to the page you sent. I tried again this morning, being very careful with everything, but got the same outcome.

I had a search around the forum last night for information and actually found one of your posts where you seemed to be having the same issue. At the time, you were on BIOS v1503 (which is what I'm currenlty on). I also noted that you upgraded to a later version some time afterwards. Could this be my problem?

The thing is I'm worried about not being able to get back into High Sierra on the 1070ti as I need that for work. Could updating the BIOS mess that up?

@Loloflatsix Thanks also for the reply. I just wanted to confirm that I'm using OC 0.7.4

Cheers,

Nick

AlBeast said:

…
I feel like I'm close. There seems a need to restrict the loading of the SSDT-DMAR (at least the Z390 one) to Big Sur, because it breaks my goal in Catalina.
…

Click to expand...

Quick question (from my iPad, so I haven’t looked at config.plist):

• In ACPI —> Delete section, are you dropping the standard DMAR table?

CaseySJ said:

Quick question (from my iPad, so I haven’t looked at config.plist):

• In ACPI —> Delete section, are you dropping the standard DMAR table?

Click to expand...

Yes, if I add DMAR I drop it. If I don't add I don't drop.

I'll make sure to double check in a few mins, but I believe I was consistent.

Thanks for getting back to me!

Update:

Catalina:
No DMAR adjustment
DTPG added
TbtOnPch disabled (and related patches as well)

-> Works

Big Sur:
No DMAR, no TbtOnPch -> Antelope gets detected but can't be accessed. Networking dropouts. (not sure if it gets detected only because it was in Catalina. As I remember last night it never got detected in Big Sur at all)
TbtOnPch, but no DMAR -> idem.
TbtOnPch and DMAR -> Networking is fixed, no Antelope detected.

In all instances I do see Antelope/Thunderbolt related information in verbose, some errors some notifications. Nothing that leads the way.

I have the feeling the SSDT-DMAR from Z3x0 isn't good enough for X299 in Big Sur. I'm curious why so much seems needed to fix it in Big Sur, whereas Catalina just does it with AppleVTD on (which is great, btw).

mrt1976 said:

@tedyun , @CaseySJ, @djlild7hina @tucoboy, @Loloflatsix

Thanks for the reply. I'll try this. The trouble I'm having at the moment is that the HDD doesn't seem to be recognised after I've updated the BIOS settings according to the page you sent. I tried again this morning, being very careful with everything, but got the same outcome.

I had a search around the forum last night for information and actually found one of your posts where you seemed to be having the same issue. At the time, you were on BIOS v1503 (which is what I'm currently on). I also noted that you upgraded to a later version some time afterwards. Could this be my problem?

The thing is I'm worried about not being able to get back into High Sierra on the 1070ti as I need that for work. Could updating the BIOS mess that up?

@Loloflatsix Thanks also for the reply. I just wanted to confirm that I'm using OC 0.7.4

Cheers,

Nick

Click to expand...

@tedyun , @CaseySJ, @djlild7hina @tucoboy, @Loloflatsix

ok - so I'm back from work now and updated the BIOS to 3105. It's booting now into Big Sur and the 6900 XT!

Initial testing shows that the following aren't working:

Front USB 3.0 ports - I have these plugged into the internal header next to the sata ports, not the one at the bottom. @djlild7hina , is this port enabled in the EFI that you used?

It's running hot! I'm using a Corsair h115i. Can you suggest some OC settings that won't melt the CPU?

Cheers for the help and support, so far. It's very much appreciated!!!

Nick

AlBeast said:

Yes, if I add DMAR I drop it. If I don't add I don't drop.

I'll make sure to double check in a few mins, but I believe I was consistent.

Thanks for getting back to me!

Update:

Catalina:
No DMAR adjustment
DTPG added
TbtOnPch disabled (and related patches as well)

-> Works

Click to expand...

Yes, on X99 and X299 we believe it's not necessary to delete and replace the DMAR table. However, the WiFi/Ethernet problem was not present in Catalina. It was first seen in Big Sur, but not with X99 and X299.

AlBeast said:

Big Sur:
No DMAR, no TbtOnPch -> Antelope gets detected but can't be accessed. Networking dropouts. (not sure if it gets detected only because it was in Catalina. As I remember last night it never got detected in Big Sur at all)
TbtOnPch, but no DMAR -> idem.
TbtOnPch and DMAR -> Networking is fixed, no Antelope detected.

In all instances I do see Antelope/Thunderbolt related information in verbose, some errors some notifications. Nothing that leads the way.

I have the feeling the SSDT-DMAR from Z3x0 isn't good enough for X299 in Big Sur. I'm curious why so much seems needed to fix it in Big Sur, whereas Catalina just does it with AppleVTD on (which is great, btw).

Click to expand...

In Big Sur on X299:

• If you enable VT-d in BIOS and uncheck DisableIOMapper, but you do not delete and replace DMAR table:
  • Does AppleVTD appear in IORegistryExplorer?
  • Does Antelope Audio connect and work?
  • Do Ethernet and WiFi connect and work?

mrt1976 said:

It's running hot! I'm using a Corsair h115i. Can you suggest some OC settings that won't melt the CPU?

Click to expand...

What do you define as hot?

Besides, try limiting the power allowed for the CPU in BIOS while keeping the desired clockspeed.
If possible that is - my BIOS has a setting for short term and longer term power limit and i set mine to something along the lines of 190 and 210W (if i rember correctly) while using a all-core clockspeed limit of 4.5GHz.
This works for my 8-core i7-7820X with 240mm AIO. Temps might climb to 90°C after prolonged heavy use.

Also try setting lower AVX limits.

CaseySJ said:

Yes, on X99 and X299 we believe it's not necessary to delete and replace the DMAR table. However, the WiFi/Ethernet problem was not present in Catalina. It was first seen in Big Sur, but not with X99 and X299.


In Big Sur on X299:

• If you enable VT-d in BIOS and uncheck DisableIOMapper, but you do notdelete and replace DMAR table:
  • Does AppleVTD appear in IORegistryExplorer?
  • Does Antelope Audio connect and work?
  • Do Ethernet and WiFi connect and work?

Click to expand...

From my previous post:

Big Sur:
No DMAR, no TbtOnPch -> Antelope gets detected but can't be accessed any further through the "Antelope Launcher" software. Networking dropouts.
TbtOnPch, but no DMAR -> idem.

In all my examples VT-d is enabled and DisableIOMapper is disabled. AppleVTD shows up everytime afaik.