Contribute
Register

Z490 & Z590 - Will Z590 ever have macOS Support ?

Did anyone with Z590 and Comet Lake (not Rocket Lake) ever get their iGPU fully working and accelerated?

I have Rocket Lake so I can't test that, but if it works I would like to add support for it in my HackinDROM Z590 Vision D for Comet Lake users.
No.. i have not managed to get my 10850k to drive the monitor with this Z590 Vision D motherboard. Just black screen with HDMI out. Tried with USB-C cable also plugged into the Thunderbolt ports without success.
 
Did anyone with Z590 and Comet Lake (not Rocket Lake) ever get their iGPU fully working and accelerated?

I have Rocket Lake so I can't test that, but if it works I would like to add support for it in my HackinDROM Z590 Vision D for Comet Lake users.

The iGPU comes up readily for Quicksync VDA using boilerplate framebuffer patch. CPUID is supported no need to patch.

But the typical SMBIOS for z590 Comet Lake is iMac 20,2 which expects a dGPU.

It took me forever to realize that iGPU was never gonna drive a display for this SMBIOS.

So you should explore another SMBIOS, but what's a good choice?

Age of Hackintosh is at precipice of history. Apple has solved entire problem by chucking PC out the Windows!

So to speak
 
BTW In 5 years when Intel iMac is no longer supported, we might not care because Apple silicon will offer such a crushing price / performance advance over today idea of hackintosh will seem a quaint relic.

Intel and Microsoft could not be less interested in advancing PC

Maybe time has come for a new san jose garage build that resets what we think a computer should be / do
 
The iGPU comes up readily for Quicksync VDA using boilerplate framebuffer patch. CPUID is supported no need to patch.

But the typical SMBIOS for z590 Comet Lake is iMac 20,2 which expects a dGPU.

It took me forever to realize that iGPU was never gonna drive a display for this SMBIOS.

So you should explore another SMBIOS, but what's a good choice?

Age of Hackintosh is at precipice of history. Apple has solved entire problem by chucking PC out the Windows!

So to speak
I'd go with iMac19,1 in that case. It can run iGPU only or iGPU+dGPU depending on the patches. See CaseySJ's Z390 Intel vs AMD GPU configs for an example.

I'm running a Z390 Designare off iGPU only, since I couldn't resist selling my RX 580 in this market, and the i9-9900K is a UHD 630 like Comet Lake's i9-10900K. I am able to run an HDMI monitor off the motherboard's HDMI port with no issues, or an LG UltraFine 5K off Thunderbolt by hotplug after boot if I boot with an HDMI monitor first. The requirement to hotplug is not a Hackintosh issue, as the LG UltraFine 5K will not even show the BIOS splash screen or boot at all plugged in. It needs DP-in connection to a dGPU for that, which worked fine with my RX 580.

That question is does that same patch config work on Comet Lake? I got the impression around the internet that nobody got their Comet Lake iGPU to drive a monitor even though it's a UHD 630 and we can do that on i9-9900K.
 
I'd go with iMac19,1 in that case. It can run iGPU only or iGPU+dGPU depending on the patches. See CaseySJ's Z390 Intel vs AMD GPU configs for an example.

I'm running a Z390 Designare off iGPU only, since I couldn't resist selling my RX 580 in this market, and the i9-9900K is a UHD 630 like Comet Lake's i9-10900K. I am able to run an HDMI monitor off the motherboard's HDMI port with no issues, or an LG UltraFine 5K off Thunderbolt by hotplug after boot if I boot with an HDMI monitor first. The requirement to hotplug is not a Hackintosh issue, as the LG UltraFine 5K will not even show the BIOS splash screen or boot at all plugged in. It needs DP-in connection to a dGPU for that, which worked fine with my RX 580.

That question is does that same patch config work on Comet Lake? I got the impression around the internet that nobody got their Comet Lake iGPU to drive a monitor even though it's a UHD 630 and we can do that on i9-9900K.

Just to try to help, I generated a 19,1 SMBIOS config for my generally-working 11.3.1 Comet Lake, 590 Hero build.

I just left the generic framebuffer patch. I pulled the dGPU and it booted into the black screen as so commonly reported. Tried both the HDMI and type-C (DisplayPort) output, but no luck.

Connector patching is the obvious next step, based on WEG FAQ for Comet Lake. I think I'm supposed to attach the dGPU then use Hackintool to look up the proper iGPU connector config?

I never completely understood this step of the Framebuffer patching guide... If anyone can give me a pointer, I'll give it try.

BTW—This was OC 0.6.8 but I could use the latest if that helps. I migrated to it yest... I saw something in the 0.6.9 release notes about updated SMBIOS?
 
Just to try to help, I generated a 19,1 SMBIOS config for my generally-working 11.3.1 Comet Lake, 590 Hero build.

I just left the generic framebuffer patch. I pulled the dGPU and it booted into the black screen as so commonly reported. Tried both the HDMI and type-C (DisplayPort) output, but no luck.

Connector patching is the obvious next step, based on WEG FAQ for Comet Lake. I think I'm supposed to attach the dGPU then use Hackintool to look up the proper iGPU connector config?

I never completely understood this step of the Framebuffer patching guide... If anyone can give me a pointer, I'll give it try.

BTW—This was OC 0.6.8 but I could use the latest if that helps. I migrated to it yest... I saw something in the 0.6.9 release notes about updated SMBIOS?

If you aren't already patching the connectors, you will probably need to do that to make it work, though if there is a Z590 incompatibility like I suspect, it will still fail and not get accelerated graphics (monitor might output though). I never did manage to wrap my head around discovering the right config for connectors on a board with Hackintool either, and it doesn't have any Z590 presets.

For reference, this is my exact config for Intel iGPU UHD 630 on Coffee Lake under DeviceProperties. I don't know if the connector patches vary on Z590 Hero (likely do), so this probably won't work as is, but it gets iGPU driving a monitor on Z390 Designare's HDMI port.

Code:
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>BwCbPg==</data>
                <key>AAPL,slot-name</key>
                <string>Built In</string>
                <key>device_type</key>
                <string>Display Controller</string>
                <key>framebuffer-con0-busid</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con0-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con0-flags</key>
                <data>xwMAAA==</data>
                <key>framebuffer-con0-index</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con0-pipe</key>
                <data>EgAAAA==</data>
                <key>framebuffer-con0-type</key>
                <data>AAQAAA==</data>
                <key>framebuffer-con1-busid</key>
                <data>BgAAAA==</data>
                <key>framebuffer-con1-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con1-flags</key>
                <data>xwMAAA==</data>
                <key>framebuffer-con1-index</key>
                <data>AgAAAA==</data>
                <key>framebuffer-con1-pipe</key>
                <data>EgAAAA==</data>
                <key>framebuffer-con1-type</key>
                <data>AAQAAA==</data>
                <key>framebuffer-con2-busid</key>
                <data>BAAAAA==</data>
                <key>framebuffer-con2-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con2-flags</key>
                <data>xwMAAA==</data>
                <key>framebuffer-con2-index</key>
                <data>AwAAAA==</data>
                <key>framebuffer-con2-pipe</key>
                <data>EgAAAA==</data>
                <key>framebuffer-con2-type</key>
                <data>AAgAAA==</data>
                <key>framebuffer-con3-busid</key>
                <data>AAAAAA==</data>
                <key>framebuffer-con3-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-con3-flags</key>
                <data>IAAAAA==</data>
                <key>framebuffer-con3-index</key>
                <data>/////w==</data>
                <key>framebuffer-con3-pipe</key>
                <data>AAAAAA==</data>
                <key>framebuffer-con3-type</key>
                <data>AQAAAA==</data>
                <key>framebuffer-patch-enable</key>
                <data>AQAAAA==</data>
                <key>igfxfw</key>
                <data>AgAAAA==</data>
                <key>igfxpavp</key>
                <data>AQAAAA==</data>
                <key>model</key>
                <string>Intel UHD Graphics 630</string>
            </dict>
 
The iGPU comes up readily for Quicksync VDA using boilerplate framebuffer patch. CPUID is supported no need to patch.

But the typical SMBIOS for z590 Comet Lake is iMac 20,2 which expects a dGPU.

It took me forever to realize that iGPU was never gonna drive a display for this SMBIOS.

So you should explore another SMBIOS, but what's a good choice?

Age of Hackintosh is at precipice of history. Apple has solved entire problem by chucking PC out the Windows!

So to speak
How about iMac20,1 ? That's what I used with z490 and Comet Lake and the iGPU worked beautifully... both in headless mode as well as the primary GPU. But to use it as the primary GPU, I had to increase DVMT preallocated memory to 96 MB otherwise the system would crash (for 64 MB or 32 MB). Sleep even worked. I only used the iGPU because MacOS 11.0 to 11.3 did not work with my 6800XT.

I haven't tried activating the Comet Lake iGPU framebuffer with z590.

And regarding your point about the Age of Hackintosh probably fading away, I second that. What Apple has done with M1 is amazing, and it serves as a disincentive to the desire or even need of building a Hack.

I saw the new M1 iMacs in the Apple store the other day, I saw the excitement on people's faces, I saw how sleek they look and how beautiful the 4.5K screens look, and thought to myself, am I really going to continue building hacks indefinitely, or am I just going to get a high-performant Apple Silicon mac and call it a day? I like the Hack scene because I'm a tinkerer at heart, i've been tinkering since the 90's. I also like the ability to run Windows/Linux/MacOS on the same box, but unless Intel delivers the performance with Alder Lake/Raptor Lake/Meteor Lake/Lunar Lake there will be little point in me continuing to build a hack anymore. Look at the problems we've had with thunderbolt hotplugging on z590... and the beta bioses from Gigabyte or Asus with their quirks. Whereas macs work well out of the box with no major problems or issues for the most part.

Hackintosh was fun while it lasted, it's been years since I've been doing this, but moving forward, I think I am going to retire in a few years, and I will just build a mini-ITX build to game on in windows, and hook up an ultra-performance Apple Silicon macbook pro (m2 or m3) to my thunderbolt dock and monitors, and just call it a day... I'm waiting to see what happens with Zen4 and Alder/Raptor Lake... but I'm definitely getting a new m2 macbook pro for sure if it drops later this year. No question about it.
 
Last edited:
How about iMac20,1 ? That's what I used with z490 and Comet Lake and the iGPU worked beautifully... both in headless mode as well as the primary GPU. But to use it as the primary GPU, I had to increase DVMT preallocated memory to 96 MB otherwise the system would crash (for 64 MB or 32 MB). Sleep even worked. I only used the iGPU because MacOS 11.0 to 11.3 did not work with my 6800XT.

I haven't tried activating the Comet Lake iGPU framebuffer with z590.

And regarding your point about the Age of Hackintosh probably fading away, I second that. What Apple has done with M1 is amazing, and it serves as a disincentive to the desire or even need of building a Hack.

I saw the new M1 iMacs in the Apple store the other day, I saw the excitement on people's faces, I saw how sleek they look and how beautiful the 4.5K screens look, and thought to myself, am I really going to continue building hacks indefinitely, or am I just going to get a high-performant Apple Silicon mac and call it a day? I like the Hack scene because I'm a tinkerer at heart, i've been tinkering since the 90's. I also like the ability to run Windows/Linux/MacOS on the same box, but unless Intel delivers the performance with Alder Lake/Raptor Lake/Meteor Lake/Lunar Lake there will be little point in me continuing to build a hack anymore. Look at the problems we've had with thunderbolt hotplugging on z590... and the beta bioses from Gigabyte or Asus with their quirks. Whereas macs work well out of the box with no major problems or issues for the most part.

Hackintosh was fun while it lasted, it's been years since I've been doing this, but moving forward, I think I am going to retire in a few years, and I will just build a mini-ITX build to game on in windows, and hook up an ultra-performance Apple Silicon macbook pro (m2 or m3) to my thunderbolt dock and monitors, and just call it a day... I'm waiting to see what happens with Zen4 and Alder/Raptor Lake... but I'm definitely getting a new m2 macbook pro for sure if it drops later this year. No question about it.
I really value the freedom to tinker and pull together a PC as I like it.

Like u, running mac, win and linux all interesting and useful.

Intel seems to have disappeared into a rut.

Microsoft has always taken bank for granted and to me Windows is the Swiss Army Knife of stupid. Plus it never stops updating, to the point that almost the sole self-justifying purpose of a PC is to run Windows Update. And you will never be allowed to forget it. Even the controls designed to get it out of your way wants to keep involved with it. Lately MSFT has been making it ever more clear that your PC is on loan to you as part of an outreach program for Bill Gate's wallet.

Linux is still a vast herds of cats: anything is possible, and anything remains possible. But somehow by time its pulled together into a slick package it's old news. But the freedom is to be treasured. This comes at price of you are never allowed to forget about the kernel. When Linux makes doing anything convenient, I always feel like I'm being pandered to. At the same time — I am not making this up — in most modern Ubuntus you cannot move file to/from the Desktop and a folder window by dragging its icon! The icon will provide a drag animation in the UI but just will not go, with no clue about why. Looking up the explanation brings up endless technical and philosophical diatribes about poking high-entropy text sequences into hidden config files to betray the high-minded semantics of a "true-tablet GUI approach"; then Gnome vs Unity, init vs systemd, cats and dogs vs etc. God help you if you just want to install the latest Radeon driver. And you will be sent to pits of GPU hell if you remove the remnants of a failed installation of the latest Radeon driver!

Mac is my middle ground: corralling the Unix cats and encouraging Intel to evolve while surprising me with attractive and useful designs that at the higher end are very well-designed and long-lived. For me anyway.

I came to Hackintosh late because my macs have been trusty. It was the user-community supporting "unsupported" Macs that won me over. Then I saw how much of this unsupported support is rooted in hackintosh experience. In last couple years it's got to a place were the 2008 Mac Pro is hamstrung by ISA workarounds that wreck virtual machine performance and slow I/O is causing UI to become somewhat tedious. Nevertheless, this 13 year old system is still a very useful daily driver. Then a 590 + Comet Lake fell into my lap so I thought I should give it a go. I'd put together a Mojave Clover Uni-/Multi-Beast brix hack a couple years ago which i still use as a media station to drive a projector. But build felt like a bit more mystical juju than I care for. When I came across Dortania Guide, it felt like linux nerds had finally found Mac and made it their own, and this has won me over.

Why? For simple reason of the support for knowing how things work, combined with the freedom to make them work as we find suitable for ourselves and the community. (Good 'ol Richard Stallman with his pet GNU, eating putty from toes.) Apple lost a sense of this a long while ago, and replaced it with fashion. The hackintosh community brings it back together. So too bad it might be end of era. And for this end I ding Intel. They had all the marbles, but their pocket ripped.

* * *

I'll try some connector iGPU patching and see what happens.
 
Just a little update from my side: Ive returned the Gigabyte Z590 Vision D in favor of the Asrock Z490 Phantom Gaming ITX/TB3! Everything is working for my use case! OWC TB4 Dock is working so the limitation of only 1 TB port does not hinder me. Im a happy camper now!

Oh and TB Hotplug is working flawlessly!

1621946256745.png


All up and running within 2 hours, board swapping and all!!
Who would have guessed that Asrock has taken the throne as a very Hackingtoshable mobo from Gigabyte!
 
I moved ahead with 11.4 update and ran into system hanging during late stage of update, requiring force restart. After a couple of resets it crashed shortly after reaching the 11.4 desktop.

I noted that LAN adapter was not being logged at the usual time during boot, but system didn't last long enough before crashing for me to discover that ethernet was not working. Crash logs showed Little Snitch (firewall) kext bombing.

Happily, on the main page for 11.4 status, the mod brought up that the i225_V renamer patch (it's known as vit9696 binary patch) no longer works with 11.4 due to—possibly—changes coming in a subsequent release to add support for this controller.

The binary patch was mentioned here a a month ago as a simpler (and therefore better) alternative to the FakePCIID patch. It relied on renaming __Z18e1000_set_mac_typeP8e1000_hw: F2150000 to F3150000. Live and learn, in hacking world cleaner is not always better :)

The FakePCIID.kext + FakePCIID_Intel_I225-V.kext patch still works.

To get your i225_V working under 11.4 (and avoid crashing if you use Little Snitch) you must add the above kexts and disable the OC Kernel Patch. DON'T forget to add i225_V DeviceProperties... I had these leftover in my config.plist.

A discussion on this topic is at the following post by @CaseySJ: "FakePCIID approach is not less efficient".
 
Last edited:
Back
Top