Contribute
Register

[Success] ASUS Prime Z370-A+i9-9900k Pro Audio Build

Status
Not open for further replies.
Those were more so just an update.

So, how are you getting back to working Thunderbolt?

I'm not, sadly.

Reinstalling Windows without macOS drive plugged in, installing TB drivers, then shutting down, plugging macOS HDD back in and booting into macOS resulted in TB recognition.

The moment I booted back into Windows, TB was not recognized but it still worked (assuming some PCI Bridge mode). I cold-booted back to macOS, and TB recognition was lost.

I did a Windows "restore" which deletes all peripheral drivers and reinstalled TB drivers. TB is again fully recognized in Windows, but not in macOS.

At this point to regain TB recognition in macOS, I'd have to reinstall Windows again.

So this leads me to believe Windows is making changes to the card itself. Is there a way to fully reset the card besides unplugging? Because that doesn't seem to do the trick.
 
I'm not, sadly.

Reinstalling Windows without macOS drive plugged in, installing TB drivers, then shutting down, plugging macOS HDD back in and booting into macOS resulted in TB recognition.

The moment I booted back into Windows, TB was not recognized but it still worked (assuming some PCI Bridge mode). I cold-booted back to macOS, and TB recognition was lost.

I did a Windows "restore" which deletes all peripheral drivers and reinstalled TB drivers. TB is again fully recognized in Windows, but not in macOS.

At this point to regain TB recognition in macOS, I'd have to reinstall Windows again.

So this leads me to believe Windows is making changes to the card itself. Is there a way to fully reset the card besides unplugging? Because that doesn't seem to do the trick.

Just reinstalled Windows - installed drivers - cold-booted to macOS - and TB is working again.

I'm not going to boot into Windows through BIOS anymore. I want to see if I can get into Windows through OC and see if that retains TB functionality.
 
Just reinstalled Windows - installed drivers - cold-booted to macOS - and TB is working again.

I'm not going to boot into Windows through BIOS anymore. I want to see if I can get into Windows through OC and see if that retains TB functionality.

Oof, man. I’m sorry about that mess.

So after you figure out Windows through OC, if that fails, I think you should move to the simpler approach of ICM mode.

You remove the patches and the SSDT and add the SSDT from ckindrom.zapto.org. I believe this will work in both.
 
Oof, man im sorry about that mess.

So after you figure out Windows through OC, if that fails, I think you should move to the simpler approach of ICM mode.

You remove the patches and the SSDT and add the SSDT from ckindrom.zapto.org. I believe this will work in both.

Now a warm boot from Windows where TB is recognized results in TB being recognized in macOS. A pattern has not really established itself. It works either way, so I'm going to give it a few days and see if I can recognize a real pattern instead of throwing a bunch of useless info in this thread. Wish me luck.
 
i have same exact configuration 9900k sapphire rx 580 z370a prime and even your efi but im getting 7200 multicore score in geekbench! change smbios no different. any advise?
I'm sure you know, but a kind reminder to be careful with the SMBIOS changes. Make sure you're logged out of iCloud. BTW, with SMBIOS changes you'll need to update the the USBMap.kext.

So I'm actually running mine daily at about 1200/7200 in Geekbench 5. This is with the CPU under volted by -0.080 and set to sync all cores "40" which is 4.0.

I need to properly state this in the guide, but the overall goal is to have a seamless experience in pro audio. I want low wattage being used (20-35 peak right now), steady clock speeds without ramping up (4.0 all cores), steady low temps with passive quiet cooling (this current setting gives me 45-55c on work load), and lots of threads to spread out software. Still looking to tweak more.

That being said of course I experimented.

In AI Tweaker in bios set the profile to XMP1 and scroll down until you find a setting called 5GHz OC Profile and enable it. That's all! The thing to remember about this board being a Rev 2 (the Z370-A II) is that it was made to support the 9900K before they stopped tweaking its production. Are you using a V1 or V2?

I'd keep Intel Power Gadget up and read your temps during benchmark. It seemed hot but reasonable to use the computer this way. However, when running a benchmark like Cinebench, it ran at 99c and 5GHz and that to me doesn't seem like a great long term solution.
 
In Windows multicore score is about 9200 but Big Sur 7200...7800. I use 5GHz but no difference. And, yes, I have Z370a Rev 1.
I'm sure you know, but a kind reminder to be careful with the SMBIOS changes. Make sure you're logged out of iCloud. BTW, with SMBIOS changes you'll need to update the the USBMap.kext.

So I'm actually running mine daily at about 1200/7200 in Geekbench 5. This is with the CPU under volted by -0.080 and set to sync all cores "40" which is 4.0.

I need to properly state this in the guide, but the overall goal is to have a seamless experience in pro audio. I want low wattage being used (20-35 peak right now), steady clock speeds without ramping up (4.0 all cores), steady low temps with passive quiet cooling (this current setting gives me 45-55c on work load), and lots of threads to spread out software. Still looking to tweak more.

That being said of course I experimented.

In AI Tweaker in bios set the profile to XMP1 and scroll down until you find a setting called 5GHz OC Profile and enable it. That's all! The thing to remember about this board being a Rev 2 (the Z370-A II) is that it was made to support the 9900K before they stopped tweaking its production. Are you using a V1 or V2?

I'd keep Intel Power Gadget up and read your temps during benchmark. It seemed hot but reasonable to use the computer this way. However, when running a benchmark like Cinebench, it ran at 99c and 5GHz and that to me doesn't seem like a great long term solution.
 
God speed. I do think theres something more to it too.

I've noticed that if I boot into macOS with the patches and SSDT on then of course I have a beautiful full Thunderbolt Bus including the correct device names (DSB1, DSB4, etc...). On that same boot, if I disable all patches and SSDT, then restart, I will have the full thunderbolt bus but the names will be wrong because the SSDT isn't there.

So whatever is going on is staying in tact during reboots and therefore a boot into windows from macOS would trip it up. Also, inversely.

In fact, before this was all dialed in we needed to boot to windows first then warm boot to macOS.

There's a BIOS feature that I need to investigate that deals with enumeration and has a timer. I’m going to do a few tests to see if I can find the magic number for how long it takes to reset the TB controller fully on a warm boot.

After a few days, it seems the behavior is the same on Windows and Mac. Sometimes it works as full TB, other times in PCI Bridge Mode. This has to be something in the BIOS right? It's like the entire card is not waking up in time to be recognized.
 
After a few days, it seems the behavior is the same on Windows and Mac. Sometimes it works as full TB, other times in PCI Bridge Mode. This has to be something in the BIOS right? It's like the entire card is not waking up in time to be recognized.

Seems TB drivers are loading consistently now. When I shut down system for the night, I cut off power to the machine via a power strip (after properly shutting down of course). When I switch it on in the morning, I turn the power strip on for at least a minute, then power on the machine. Not sure if this is what is making the difference, but TB drivers have been loading every time.
 

Attachments

  • Screen Shot 2021-03-20 at 06.33.20.png
    Screen Shot 2021-03-20 at 06.33.20.png
    207.4 KB · Views: 1,305
  • Screen Shot 2021-03-20 at 06.33.34.png
    Screen Shot 2021-03-20 at 06.33.34.png
    227.1 KB · Views: 639
Status
Not open for further replies.
Back
Top