Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

[bazzevo]

I am having a few issues running my UA Apollo Quad TB3 at 96KHz. I get a lot of static from the outputs, when I test them. It only seems to be stable a 64 samples buffer. Any other setting, and it just is not usable. If I run at 88.2KHz it is stable only at 128 samples. This is a problem if I wanna use more plugins, and need to increase buffer size. Is there any setting on they BIOS that will increase bandwidth for TB3 on the Z490 D? Why settings have you found work best? This is a none flashed TB3 chip. The 10900K has loads of CPU,. So it is nothing to do with the system, just TB3.

I also have a RME MADI PCIe card, which I can run at 96KHz or 192KHz, if I like. It runs without any issues at an buffer size. That is what leads me to believe it might be a TB3 setting in BIOS.

 

[CaseySJ]

Is it the only difference (headless vs non headless)? Because I am using the Intel config in headless mode. Using it in non headless take forever to boot so I disabled it. If it is the only difference, then, unknowingly, I am using the AMD config plist.

Yes that's the only difference, so it seems you're okay with the file you have. Running iGPU in headless mode is the recommended configuration.

 

[Media]

Hi Casey, I have a question for you. When I installed Big Sur, I just used all of the default settings from your OpenCore 0.6.7 EFI folder and added in the required serial numbers. I opened Open Core Configurator to check the plist file and noticed that the SSDT-NVRAM.aml file was disabled. Is this supposed to be disabled or should it be enabled? Thank you...

 

[CaseySJ]

** Possible problem with Big Sur 11.3 Public Beta 4 **​

11.3 Beta 4 released to the public a day or two ago has been very problematic on my Z490 Vision D:

• Unable to perform in-place update through System Preferences --> Software Update.
• Consequently, downloaded full installer using GibMacOS, but installation process hanged repeatedly during early stage of phase 1 install.
• Ran the full installer on Apple MacBook Pro 13" to perform a clean install on an external SATA SSD. Installation on MacBook Pro was successful.
• After transferring SATA SSD to Z490 Vision D, "welcome" wizard came up and I specified country, account name, etc., but system crashed before the wizard could complete.
• Rebooting the system brought me to the Login screen and I could log in, but system repeatedly crashed after a few minutes.

Finally, decided to do a clean install of 11.3 Beta 3, and it's been running perfectly. If you plan to install Beta 4, please make a full bootable backup first. Might be an even better idea to erase the backup disk before starting the backup. This allows Carbon Copy Cloner to use APFS Replicator, which is the only way macOS system can be backed up (along with all user folders).

The update finally succeeded, but latest Patch 4 of HackinDROM does not launch.

View attachment 512447
UPDATE 1: 11.3 Beta 4 is not stable on my system despite the clean reinstall. Locks up after a few minutes. Beta 3 runs fine.

UPDATE 2: System crashes may have been with NVMeFix.kext (v1.0.5). Continuing to monitor the system with NVMeFix to see if subsequent crashes (if any) still point to this kext.

UPDATE 3: 11.3 Beta 4 has been running FINE now for past 3 hours and 40 minutes:

% uptime
9:46  up  3:39, 2 users, load averages: 1.02 1.19 1.13

Unfortunately 11.3 Beta 4 is not stable for me. What I've observed so far:

• I believe changes were made to the NVMe driver (IONVMeFamily.kext) to address SSD caching issues with M1 Macs.
• Unfortunately, the new version has been crashing my system repeatedly. Kernel panics for the past 15 of 15 crashes since updating to Beta 4 have all occurred in IONVMeFamily.kext.
• Restoring back to Beta 3 fixes this problem completely.
• I have reported the last 5 of these crashes to Apple via the crash dump reporter.

Note 1: The problem may depend on make/model of NVMe SSD. My system has both Silicon Power and Sabrent Rocket (PCIe 3.0) NVMe SSDs.

Note 2: The problem may not occur on some motherboards. For example, my Gigabyte B550 Vision D (AMD Ryzen) with Silicon Power NVMe SSD and Sabrent Rocket (PCIe 4.0 version) remains rock solid on Beta 4.

 

[CaseySJ]

Hi Casey, I have a question for you. When I installed Big Sur, I just used all of the default settings from your OpenCore 0.6.7 EFI folder and added in the required serial numbers. I opened Open Core Configurator to check the plist file and noticed that the SSDT-NVRAM.aml file was disabled. Is this supposed to be disabled or should it be enabled? Thank you... View attachment 512617

Yes that's correct. We initially had it enabled just like on Z390, but then we discovered that it's not needed on Z490. I may delete it in the next EFI update.

 

[hughythomas]

I am having a few issues running my UA Apollo Quad TB3 at 96KHz. I get a lot of static from the outputs, when I test them. It only seems to be stable a 64 samples buffer. Any other setting, and it just is not usable. If I run at 88.2KHz it is stable only at 128 samples. This is a problem if I wanna use more plugins, and need to increase buffer size. Is there any setting on they BIOS that will increase bandwidth for TB3 on the Z490 D? Why settings have you found work best? This is a none flashed TB3 chip. The 10900K has loads of CPU,. So it is nothing to do with the system, just TB3.

I also have a RME MADI PCIe card, which I can run at 96KHz or 192KHz, if I like. It runs without any issues at an buffer size. That is what leads me to believe it might be a TB3 setting in BIOS.

Hey Bazzevo,

Have you got a real Mac you can test the interface on to see if it exhibits the same behavior? It sounds like a Tthunderbolt issue but you can never be too sure!

I'm running an RME FF802 (USB) on 96KHz @ 128 samples on LPX 10.6.1 without an issue. However, I have found that Big Sur kicks up all sorts of weirdness when my overclock / RAM timings were not 24/7 stable (like they are now).

I have a UAD-2 card in my machine, and it used to be that the thing would not work with anything below 1024 samples. But now its quite happy at 128 (4.3ms round trip).

If you have overclocked at all try relaxing your settings. I always bow to the community's superior knowledge and wisdom though! I just thought I'd chime in as a fellow muso as I run a studio over here in Blightey.

 

[bazzevo]

Hey Bazzevo,

Have you got a real Mac you can test the interface on to see if it exhibits the same behavior? It sounds like a Tthunderbolt issue but you can never be too sure!

I'm running an RME FF802 (USB) on 96KHz @ 128 samples on LPX 10.6.1 without an issue. However, I have found that Big Sur kicks up all sorts of weirdness when my overclock / RAM timings were not 24/7 stable (like they are now).

I have a UAD-2 card in my machine, and it used to be that the thing would not work with anything below 1024 samples. But now its quite happy at 128 (4.3ms round trip).

If you have overclocked at all try relaxing your settings. I always bow to the community's superior knowledge and wisdom though! I just thought I'd chime in as a fellow muso as I run a studio over here in Blightey.

I did what you recommended, and I can get 96Khz running done as low as 128 samples on my MacBook Pro. No noise or interference, so it looks like it is not the TB3 card issue.

I may play around with the BIOS a bit, to see if that makes any difference.

Thanks for the help.

 

[studioj21]

Hey stranger!

Download the latest EFI from Casey, copy your serial info from this section into the new, AMD GPU config.plist
and you should be good to go!

(**This is a randomly generated SN and not my own - hence I didn't block it out as we're expected to!)
View attachment 512614

Success with the Biostar RX 560! It is like night and day in terms of responsiveness. Feels like my old trashcan Mac now, just faster . Thx for the help!!

P.S. I am running the Vision D with a UAD Apollo 8pre with Thunderbolt 3 adapter and I'm not experiencing those issues. All buffers seem to be working solidly. Sorry to hear that!

 

[maeluse]

Hi everyone,

That's a bit off-topic, but I would like to go back to the random short black screen issues with my Radeon RX 5700XT when it is connected to my UW-QHD monitor with my HDMI cable. I found a good workaround.

As already said here, this is a well known issue with the driver of this card on Mac systems. DP does not show this issue (@CaseySJ confirmed that information). However the DP port on my monitor is already occupied with another cable coming from my home office laptop, which only has that graphic output port type available unfortunately.

In the past I used to try some DP to HDMI adapter cables to connect my laptop into the HDMI of my monitor and my hackintosh into the DP (via a normal DP <-> DP cable). But after two failed attempts with two different cables I bought (the monitor could not sync to the HDMI signal given), which were, BTW, in the specs supposed to support resolutions up to 4K at 60 Hz, I resigned myself to the fact that this technology could not comply with my special UW-QHD resolution. I could indeed also read in some comments on Amazon for different products and from users, which have UW-QHD monitors, that they could not get their monitor sync to the signal successfully. So I gave up thinking of that option. This was my mindset a few months ago.

The last days I looked twice and decided, after some research, to give a chance to a third adapter... I was already ready to send the product back to Amazon when I received it, BUT... this time, it surprisingly worked flawlessly!!! I have been using it for two weeks now and never had any interruption or out-of-sync issues in the signal. I am a Frenchman lost in Germany, so I bought this product on amazon.de:
https://www.amazon.de/gp/product/B07WD75HCD
https://www.amazon.com/gp/product/B07WD75HCD

I can just highly recommend it. It solved all my problems. Well... in fact not ALL of my life problems, but you got me right?

So, my wait for a RX 5700 XT driver fix regarding the HDMI issue has become really secondary now. Everything is working fine with this new configuration. That's a good workaround!

 

[thomasjudge]

Hi, so, I have semi-successfully built a Vision D system, pretty minimal at this point, 32GB RAM & 1TB NVMe. I am trying to get it to work with an Apple Thunderbolt Display (I know...) using the Apple Thunderbolt adapter.

I was unable to successfully flash the Thunderbolt firmware eeprom (I may come back to this in a subsequent post) so I bought an GC-Alpine Ridge card which turns out is a 2.0 version. The card shows up in system report under PCI, although interestingly it is described as "Intel JHL-7540 Titan Ridge Thunderbolt NHI", but the Thunderbolt monitor doesn't show up or startup on cold boot, warm boot, or hot plug. Interestingly if I tail -f /var/log/system.log and plug and unplug the monitor, nothing shows up, so I am wondering if somehow through the adapter it is not even being detected? The monitor works without the adapter on an older hackintosh.

Any thoughts/help would be greatly appreciated. Let me know what I can attach.