Asus X299 - Support

[izo1]

Has anyone attempted a W-3175x build out of curiosity?
I wonder how much it would differ from a KGP build...

Not worth it. Get a 10980XE and OC all cores with a good open water loop. (You can actually get close @ 4.5+Ghz all cores to the 2019 28c Mac Pro in terms of performance).

W-3175x is a weird CPU that no one is buying and Intel is going to have to reinvent the wheel anyway, so better off waiting.

 

[mm2margaret]

Be careful with a 621 or an X299 chipset if you are intending to use Opencore......the claim has been made that OC doesn't like the NVRAM in the implementation of Asus's 621 boards....which means booting can be complicated.

However, if you're only booting one OS, that won't apply.

 

[ryward]

Not worth it. Get a 10980XE and OC all cores with a good open water loop. (You can actually get close @ 4.5+Ghz all cores to the 2019 28c Mac Pro in terms of performance).

W-3175x is a weird CPU that no one is buying and Intel is going to have to reinvent the wheel anyway, so better off waiting.

@izo1 I just got a 10980XE, and have the Sage X299 SAGE 10G, not getting a post from mine and it doesn't seem to take a flashback either. Are you using a modified bios on yours?

 

[ryward]

@izo1 I just got a 10980XE, and have the Sage X299 SAGE 10G, not getting a post from mine and it doesn't seem to take a flashback either. Are you using a modified bios on yours?

Got it to post and flash. Interested still if you are using a modded bios ?

 

[izo1]

@izo1 I just got a 10980XE, and have the Sage X299 SAGE 10G, not getting a post from mine and it doesn't seem to take a flashback either. Are you using a modified bios on yours?

I have a 9980XE with 2002 Bios. BIOS is not modded.

Yours should work since ASUS updated their SAGE 10/G BIOS with the new microcode.

 

[ryward]

I have a 9980XE with 2002 Bios. BIOS is not modded.

Yours should work since ASUS updated their SAGE 10/G BIOS with the new microcode.

Thank you. After I got that problem sorted, think I may have a bummed board... A basic Windows install won't complete, swapped all parts except CPU and motherboard. First part of install works fine, but hangs on first Windows Boot with Q-code AA, which pretty much means anything Prob will try to RMA it. Much appreciated.

 

[ryward]

One thing I thought I should point out anyone wanting to use a X299 SAGE/10G board with Air Cooling... the GPU card in slot 1 is bang up super tight against an Air Cooler - so little room and most likely will touch. I would highly recommend against it. For bench testing purposes I am using a Noctua Chromax DH15, I will be on water cooling after my tests complete.

 

[Mettiu]

Following the Kgp guide, I installed Mojave on a Asus X299 TUF MK2, with a delided i9-7980xe.
I am a puzzled by the difference in Cinebench r20 scores between Win10 and Mojave though. In the first, I got 10153, while in Mojave 9460. I expected GPU performance being lower in MacOS, but usually the contrary is true when it comes to CPU. Any clue what the issue might be? Is anybody else experiencing this?

 

[tonyarnold]

Heads up: I did a test run with ASUS' Prime X299 Deluxe v3006 BIOS update today, and I could not my build to boot using OpenCore 0.5.5. I had to revert to BIOS version 2002.

It goes without saying that if you don't have a reason to update your BIOS: maybe don't (at least without setting aside a day to fix the things that might go awry).

I'm keen to hear other people's experiences with this update. My machine would boot to the FileVault login screen, but once I'd entered my password, it just hung. No progress bar, no KP, no text.

When I've got more time, I'll have another poke at it and see if I can get some more info about the error.

 

[Gaulomatic]

@tonyarnold Same for my Asus Rampage VI Extreme Omega, the new 3006 produces the same issues like the Cascade Lake X299-Refresh boards: MSR Lock setting in the BIOS has no effect and with a proper kernel patch to circumvent this it stops booting while PCI stuff is mentioned. This applies to Clover as well as Open Core.

Something in the new AMI firmware is quirky.