Z490 & Z590 - Will Z590 ever have macOS Support ?

[8Cores8Threads]

Got i225-V ethernet working with just a Device Properties entry and Kernel Patch entry, just like Dortania's guide suggests:

Desktop Comet Lake | OpenCore Install Guide

dortania.github.io

I did not use any of the kexts:
FakePCIID.kext
FakePCIID_Intel_I225-V.kext
FakePCIID_Intel_HDMI_Audio.kext

I followed the guide and unless I messed something up, its not working for me. My Z590-A also has the i225-V but it won't even show up in System Information. I'm not sure where I went wrong.
Thanks for your help!

 

[c-o-pr]

That was a great write-up on pitfalls of new Thunderbolt!

For everyone following along, the IOMMU pre-boot config is a measure to deal with Thunderclap:

Thunderclap

thunderclap.io

This is a very significant peripheral device DMA vulnerability. Basically the original design of TB extended the PCI bus outside the chassis over serial, but didn't update the core-centric memory projection model to account for the huge change administrative surface of the system, so untrusted devices with rich logic (whole other computers) ended up being hooked straight up to kernel memory, which is a bit of a risk when the device contains logic more far flexible than a network or drive controller. My sense is the TB design still has not thought all this thru but also my thinking is far out of date, so big HAND WAVE for next comment: Basically the peripheral bus used to be thought of as under care of kernel and devices were adapted for a narrow I/O use-case through simple (and fast) controller logic and a kernel driver, both of which included an tacit agreement on part of designers that the device to not do bad stuff. But once the PCI bus becomes part of a fabric of other devices, the design of the kernel protection model gets ... more interesting, because it is an inherent property of a kernel to shield privileged device memory (below the syscall) from wanton userspace programs (above). Everything on bus which can do direct memory access (RAM) was considered trusted. Well as Peter Sellers once said as Inspector Clousseau about a priceless Steinway, maybe "not any more?"

 

[8Cores8Threads]

You are using kexts as well. Set both of them to NO and see is that will help.
View attachment 516266

My mistake, I uploaded an EFI from when I was tinkering. This is my newer one, but the issue persists on both the one I uploaded previously as well as this one.
Thanks!

 

[XixD-R-ExiX]

Hello community.

I can confirm that updating to the latest non beta BIOS (0605) on the HERO XIII breaks hot plug. Nevertheless, Thunderbolt works after complete shutdown.

Regarding the i225 Ethernet ports. The Dortania patch along with @CaseySJ method works without any kexts. However, in order to make it work I had to manually set the port to full duplex instead of automatic. Hope this helps you guys out there. I'll be keeping the Thunderbolt dock until Friday, so I can test Tthunderbolt hot plug under the new HERO's BIOS. Thank you.

 

[8Cores8Threads]

Everything looks good. Double check if your PCI device path is correct.
In my case on the first install lan worked with kexts and DeviceProperties. After I reinstalled the OS it no longer worked. The second time it worked with just DeviceProperties and Kernel Patch. Not sure what's going on with that device...

Do you know how I can check the device path? I ran gfxutil but I'm not sure how to tell what device is what, or if it will even appear here since it isnt being used by the system.

 

[8Cores8Threads]

I attached the output. In addition to needing the path to the ethernet interface, I also need to know the path to my GTX 1060, which is in the top PCI-E slot but needs to be disabled so that I can exclusively use the 760 with macOS. Any help identifying that would also be great. Thanks again!

 

[dehjomz]

Successfully updated to Big Sur 11.3. Now my front panel USB-C port is not working. It was working on 11.2.3

For those with USB problems with Big Sur 11.3, have you tried disabling the XHCIPortLimit patch? That is Kernel->Quirks->XhciPort Limit.

I'm on 11.4 beta1, and I just disabled this patch, and now after all this time, my USB2 devices finally work in all the mapped ports; before they only worked in 40 percent of the ports.

And finally after hours of troubleshooting, my hack can now go down to sleep and stay asleep when my Fenvi T919 Broadcom bluetooth adapter is attached to USB! When the XHCIPortLimit patch is applied, I was unable to set the particular port that the Bluetooth adapter is attached to to "Internal." And the Broadcom bluetooth adapter was automatically waking my system from sleep!

Seems that the XHCIPortLimit patch is interfering with USB code in Big Sur... so back to being only able to use 15 ports, but with ZERO bugs.

Hello community.

I can confirm that updating to the latest non beta BIOS (0605) on the HERO XIII breaks hot plug. Nevertheless, Thunderbolt works after complete shutdown.

Sorry to hear that. Hopefully there's a fix soon.


And finally, I've uncovered that there definitely is no need for Z590/Z490 Vision D users to solely use RGB fusion in windows to control RGB, as the BIOS/firmware has two hidden variables to control the RGB mode and the RGB color. There's also another variable that allows the RGB elements to operate while the system is in S3/S4/S5 mode, or RGB can be completely be disabled if the system is not up. RGB can also be disabled if it's not your thing.

Set the value of these hidden variables to your heart's content, and the RGB settings persist on the next boot! They persist until you clear CMOS or set optimized defaults. Gigabyte really should unhide these RGB settings in the BIOS.

 

[XixD-R-ExiX]

Sorry to hear that. Hopefully there's a fix soon.

Actually,

I noticed, yesterday, that the ssdt-ptpg.aml was not included within my efi folder. Once placed into the acpi folder hot plug works on the latest hero 13 bios (0605). Will do more testing today and see how stable the connection is. One thing I noticed was that if I restart the computer the thunderbolt drive does not show up after a reboot. However, once I unplug it and plug it back in, it shows up. Will test this behavior in windows as well, since I have a dual boot system. Hope this helps anyone out there.

 

[dehjomz]

Actually,

I noticed, yesterday, that the ssdt-ptpg.aml was not included within my efi folder. Once placed into the acpi folder hot plug works on the latest hero 13 bios (0605). Will do more testing today and see how stable the connection is. One thing I noticed was that if I restart the computer the thunderbolt drive does not show up after a reboot. However, once I unplug it and plug it back in, it shows up. Will test this behavior in windows as well, since I have a dual boot system. Hope this helps anyone out there.

Good. I think the problem with hotplug doesn't affect all thunderbolt devices.

In my experience with Maple Ridge NVM26/26.5, devices with JHL6340 controller chips hot plug just fine, same with those that have JHL7540 and JHL8440. But some other Thunderbolt 3 devices with JHL6240 and JHL6540 controllers are having issues with hotplugging. Do you know what controller your thunderbolt device(s) use(s)?

However, I should caveat that the devices work just fine if connected to the thunderbolt controller prior to pushing the power button. I wonder if your issue with your Thunderbolt drive disappearing (on warm boot) has anything to do with the hot plug issues? Does this issue happen if you warm boot after first resuming from sleep/suspend mode?

 

[XixD-R-ExiX]

Do you know what controller your thunderbolt device(s) use(s)?

@dehjomz how can I go about this ?I contacted western digital and they don't seem to know the controller the wd black d50 uses.

I wonder if your issue with your thunderbolt drive disappearing (on warm boot) has anything to do with the hotplug issues? Does this issue happen if you warm boot after first resuming from sleep/suspend mode?

haven't tried from sleep yet. will try it out some time tonight. I also have another Hero 13 with the original firmware so I will test both with my current EFI. test if the drive is recognize after reboot, sleep, and complete shutdown correct ? Will also test this behaviors in windows and see what the results are. hope this info helps out anyone out there. Specially since the hero 13 is an amazing board.