Contribute
Register

Z490 & Z590 - Will Z590 ever have macOS Support ?

@tsanko.dimitrov looks like the I22V is working fine with sleep. I've been through 3 sleep/wake cycles now and ethernet is still good. I am getting random wakes - but that's something else to investigate.

I am applying a device-id to the I22V in DeviceProperties. I also have to set the hardware duplex to "full-duplex, flow-control" (in Network prefs) otherwise I get no connection. Ethernet won't work without both these fixes.

<key>PciRoot(0x0)/Pci(0x1B,0x2)/Pci(0x0,0x0)</key>
<dict>
<key>device-id</key>
<data>8xWGgA==</data>
<key>device_type</key>
<string>Ethernet Controller</string>
<key>model</key>
<string>Intel Ethernet Controller i225-V</string>
<key>name</key>
<string>Intel Ethernet Controller i225-V</string>
</dict>
 
@tsanko.dimitrov looks like the I22V is working fine with sleep. I've been through 3 sleep/wake cycles now and ethernet is still good. I am getting random wakes - but that's something else to investigate.

I am applying a device-id to the I22V in DeviceProperties. I also have to set the hardware duplex to "full-duplex, flow-control" (in Network prefs) otherwise I get no connection. Ethernet won't work without both these fixes.
Mine is working without any patches when I've enabled the VT-d option, applied a custom DMAR table and has the AppleVTD enabled. If I disable the VT-d option, do not drop the original DMAR and not having the AppleVTD enabled I'm facing a KP on login screen. In this situation if I apply a device ID of 15F38086 only (as you said), I'm facing no more KPs and the NICs are working with automatic settings. I'm not sure if there are a hardware differences in the boards supplied in Europe (where I am) and the other regions. A couple of users with the Z590 VISION D motherboard having issues with the onboard NICs, but on my board the NICs are working without any patches, but with enabled VT-d option in BIOS, enabled AppleVTD and replaced original DMAR table. It's quite strange. I've seen a predifinied EFI folder in the HackinDROM app and in the provided config.plist is specified a device-id for both NICs.
 
@tsanko.dimitrov looks like the I22V is working fine with sleep. I've been through 3 sleep/wake cycles now and ethernet is still good. I am getting random wakes - but that's something else to investigate.

I am applying a device-id to the I22V in DeviceProperties. I also have to set the hardware duplex to "full-duplex, flow-control" (in Network prefs) otherwise I get no connection. Ethernet won't work without both these fixes.
Those may be normal “dark wakes”. Does the computer return to sleep by itself if left untouched?
 
Mine is working without any patches when I've enabled the VT-d option, applied a custom DMAR table and has the AppleVTD enabled. If I disable the VT-d option, do not drop the original DMAR and not having the AppleVTD enabled I'm facing a KP on login screen. In this situation if I apply a device ID of 15F38086 only (as you said), I'm facing no more KPs and the NICs are working with automatic settings. I'm not sure if there are a hardware differences in the boards supplied in Europe (where I am) and the other regions. A couple of users with the Z590 VISION D motherboard having issues with the onboard NICs, but on my board the NICs are working without any patches, but with enabled VT-d option in BIOS, enabled AppleVTD and replaced original DMAR table. It's quite strange. I've seen a predifinied EFI folder in the HackinDROM app and in the provided config.plist is specified a device-id for both NICs.

Interesting. If I enable AppleVTD then the NIC does work without the device-id. I still have to use a manual configuration and disable "energy-efficient-ethernet" unfortunately.

Is there any advantage to enabling AppleVTD (I don't use any Thunderbolt devices)?

Those may be normal “dark wakes”. Does the computer return to sleep by itself if left untouched?

I've re-enabled sleep and my Mac still seems to have insomnia (wakes after a while, does not return to sleep). Haven't had time to fully investigate. But at least I can shutdown/sleep/wake without hardware errors now :)
 
Interesting. If I enable AppleVTD then the NIC does work without the device-id. I still have to use a manual configuration and disable "energy-efficient-ethernet" unfortunately.

Is there any advantage to enabling AppleVTD (I don't use any Thunderbolt devices)?

Enabled AppleVTD, no NIC device-ids, NICs all automatic configuration:
Screenshot 2022-01-09 at 22.51.04.png
Screenshot 2022-01-09 at 22.51.16.png
Screenshot 2022-01-09 at 22.51.31.png


AppleVTD provide direct memory access and bring some Thunderbolt device to work correctly. As you said you do not need the TB, just turn it off. But I think that if you can enable the AppleVTD it will be better to have it enabled. All the Apple Macs are having it enabled. If you have it enabled your machine will be as closes as possible to a real Apple Mac and to benefit all the advantages of AppleVTD - maybe there are many other advantages, we still haven’t discovered yet.
 
On the Z590 Vision D, I recently updated to BIOS F7 to see if Thunderbolt hot plug would work in macOS. (It does not for me.) Also, F7 is bugged out in terms of the load line calibration and CPU stability when overclocked. The same exact voltage settings and turbo core ratios that have been stable for months on an older BIOS is unstable on F7.

Also, this BIOS, per Gigabyte's webiste, does not support downgrading to older BIOSes. But more advanced users are able to downgrade via flashback... so I don't know the point of disallowing downgrading in the GUI. My older T23 BIOS is extremely stable, so I am going to leave it alone forever until I retire z590, which will be sooner rather than later. Waiting on Raptor or Meteor Lake.
 
Got a build setup with Asus ROG Maximus XIII Hero z590 and having the strangest issue.

Thunderbolt works fine with 1 stick of RAM but does not work at with 2 sticks in any configuration. Tried resetting BIOS and everything else under the sun. Not sure if this is a software or hardware error. Anyone ever seen this before?

P.S. just to update from a previous post, BCM94360 does work in the M.2 slot of this board.
 
Thunderbolt works fine with 1 stick of RAM but does not work at with 2 sticks in any configuration. Tried resetting BIOS and everything else under the sun. Not sure if this is a software or hardware error. Anyone ever seen this before?
This looks like the issues with networking and variable amounts of RAM/RAM sticks in the Z390 Designare thread, until it was figured out how to enable AppleVTD.
 
On the Z590 Vision D, I recently updated to BIOS F7 to see if Thunderbolt hot plug would work in macOS. (It does not for me.) Also, F7 is bugged out in terms of the load line calibration and CPU stability when overclocked. The same exact voltage settings and turbo core ratios that have been stable for months on an older BIOS is unstable on F7.

Also, this BIOS, per Gigabyte's webiste, does not support downgrading to older BIOSes. But more advanced users are able to downgrade via flashback... so I don't know the point of disallowing downgrading in the GUI. My older T23 BIOS is extremely stable, so I am going to leave it alone forever until I retire z590, which will be sooner rather than later. Waiting on Raptor or Meteor Lake.
As per Gigabyte's Website there are a lot MBs with Z590 chipsets having an update to their BIOS with the same change log - vulnerabilities and capsule BIOS...... and a lot of hidden bugs (I don't know how is the situation with the other brands - Asus, MSI, Asrock, etc.). I think the whole Z590 lineup and the 11th gen was a mistake... a not needed platform between the Skylake system and the looooong awaited new era of CPUs for Intel. :thumbdown
 
Those may be normal “dark wakes”. Does the computer return to sleep by itself if left untouched?
@tsanko.dimitrov looks like the I22V is working fine with sleep. I've been through 3 sleep/wake cycles now and ethernet is still good. I am getting random wakes - but that's something else to investigate.

I am applying a device-id to the I22V in DeviceProperties. I also have to set the hardware duplex to "full-duplex, flow-control" (in Network prefs) otherwise I get no connection. Ethernet won't work without both these fixes.
My I225V also works fine with those duplex & flow-control settings, EXCEPT if I set my Netgear CM1100 modem and Netgear RAX70 router to both use "ethernet port aggregation" (i.e., 2 WAN cables). Although every other wired device on my home network (AppleTV4, and a couple of old MacPro's) work fine with the port aggregation, the I225V on my Hackintosh disconnects. (I do *not* have anything defined for it in "Device Properties" of my config.plist... somewhere along the way it was pointed out to me that was unneeded in my case, or possibly due to Monterey 12.x?) In any case, if port aggregation is used, the I225V also disconnects if I boot into Windows 11, so I'm thinking it's not just a Hackintosh problem.
 
Back
Top