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

[taconugget]

I'll report back in a couple days. From the research Ive done so far, it seems fine to run the liquid cooler like this. So nice having a machine that will sleep

on another matter @CaseySJ you have any idea about the strange bluetooth settings Ive been seeing??

If I go to my mouse settings, I see a message saying "Wait for a Bluetooth mouse to be discovered, or connect a USB mouse". I have a wired Microsoft mouse in that is working great so not sure why this comes up. Continuity works great as well. I have the recommended YOUBO wifi/Bluetooth card installed.

It's not the end of the world, but would be nice to be able to select that I want "natural" mode mouse and not have to fix it in the command line.


~Thanks

 

[XStylus]

Ladies and gentlemen, may I present the first (to my knowledge) W480 Vision D running MacOS.

All the installation steps went smooth as butter except for a minor catch with Step 12, specifically regarding QuickSync HEVC and H.264 hardware acceleration. VideoProc gave me a thumbs down, which I somewhat expected for reasons that I'll get into.

--Edit: FIXED! See link:

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

Also try the other supported device IDs: 9BC4 and 9BC8 (but reverse the byte order: C49B and C89B). Tried 9BC4, no dice. Device path is correct. Although I'm optimistic this board won't deviate too much from the Z490 version, it doesn't hurt to verify. Been doing a lot of catch-up reading...

www.tonymacx86.com

According to Intel ARK, the iGPU for the I#-10#00 processors is the UHD Graphics 630 and has a device ID of 0x9BC5. On the other hand, the iGPU for the Xeon W-1290P is the UHD Graphics P630 and has a device ID of 0x9BC6.

My thought is that the graphics adapters are likely extremely similar and the P630 would likely work with the regular 630 driver, but it likely doesn't recognize the device ID and therefore does not load. (Edit: A quick tweak in OpenCore as referenced at the link above will fix this.)



I dunno if Sleep functionality is supposed to work on Hackintoshes, but it does not in my case at present.

--EDIT: FIXED! Disabling memory XMP in the BIOS was the solution in my case. Also, I've since switched to four sticks of ECC memory since that's the main benefit of using a Xeon chip anyway.



That issue aside, everything else appears to run okay. Both on-board ethernet ports work (though I have also added an X550 X540 card for 10GbE), every USB port works, and Thunderbolt works (though I haven't done the firmware flash hack to enable extended mode). I have not installed a WiFi adapter so I can't verify Handoff, Bluetooth, or otherwise just yet.

That aside, I haven't done any deep testing to really bang on this thing, nor do I even know where to start to really stress test it. However, I did do a Cinebench R20 run, which came up with 541pts single core, 6336pts multi-core. That seems a bit on the low side, so I'm open to additional tuning suggestions.


In any case though, I see this as an excellent start. Would love to see others join me on this one, once the quirks are ironed out. The W480 Vision D and the Xeon W-1290P are going for $379 and $560 respectively, and given how heavily marked up the i9-10900K is at some stores, you just might come out ahead, and without having to sit in backorder hell.


UPDATE: Five months in, this machine has been working like an absolute champ. I have not tested Handoff since I don't have an iOS mobile device, but I have experienced NO issues of any kind.

 

[Diorama]

Just finished watching test

Max tech where his Mac Pro that he paid 15k is slower then my z490 with 10900k

My result with Radeon VII for is 2:38 for 8 minutes video and his is 2:31 for a 5 minutes long video, which is 3 minutes shorter video.

 

[Dedalos87]

Ladies and gentlemen, may I present the first (to my knowledge) W480 Vision D running MacOS.

View attachment 487894


All the way up to Step 12 everything went smooth as butter.

There are a couple minor catches thus far, as anticipated. The first is HEVC and H.264 hardware acceleration. VideoProc gave me a thumbs down, and I somewhat expected that for reasons that I'll get into.

View attachment 487892


According to Intel ARK, the iGPU for the I#-10#00 processors is the UHD Graphics 630 and has a device ID of 0x9BC5. On the other hand, the iGPU for the Xeon W-1290P is the UHD Graphics P630 and has a device ID of 0x9BC6.

My thought is that the graphics adapters are likely extremely similar and the P630 would likely work with the regular 630 driver, but it likely doesn't recognize the device ID and therefore does not load.

Is there a way to address that? I'm half a decade out of practice on the Hackintosh scene so I'm not clear on how that's done nowdays given how much more locked down MacOS is compared to then. I'd appreciate it if someone could clue me in.

On a related note, I dunno if there's any similar device ID differences between the W480 and the Z490 chipset devices itself, or where I'd go to even check that. Could have an effect on power management, turbo boost, etc.

I dunno if Sleep functionality is supposed to work on Hackintoshes, but it does not in my case at present. (If it is supposed to work on Z490s, then this could be related to chipset device ID differences as I said above). The first time I tried using sleep it did nothing except blank the screen for two seconds. Tried again and the hardware did go into sleep mode, but upon waking MacOS booted fresh and gave a "Your computer was restarted because of a problem" notice.

View attachment 487893

That issue aside, everything else appears to run okay. Both on-board ethernet ports work (though I have also added an X550 card for 10GbE), every USB port works, and Thunderbolt works (though I haven't done the firmware flash hack to enable extended mode). I have not installed a WiFi adapter so I can't verify Handoff, Bluetooth, or otherwise just yet.

That aside, I haven't done any deep testing to really bang on this thing, nor do I even know where to start to really stress test it. However, I did do a Cinebench R20 run, which came up with 541pts single core, 6336pts multi-core. I'm open to additional suggestions.


In any case though, I see this as an excellent start. Would love to see others join me on this one, once the quirks are ironed out. The W480 Vision D and the Xeon W-1290P are going for $379 and $560 respectively, and given how heavily marked up the i9-10900K is at some stores, you just might come out ahead, and without having to sit in backorder hell.

Nice, my W480 Vision D and Xeon W-1290P arrived today
Hopefully, I will have a similar experience

 

[CaseySJ]

Ladies and gentlemen, may I present the first (to my knowledge) W480 Vision D running MacOS.

Congratulations! Which EFI did you use and what changes were necessary?

...
According to Intel ARK, the iGPU for the I#-10#00 processors is the UHD Graphics 630 and has a device ID of 0x9BC5. On the other hand, the iGPU for the Xeon W-1290P is the UHD Graphics P630 and has a device ID of 0x9BC6.

This should be straightforward to fix. WhateverGreen does not yet support 0x9BC6, but version 1.4.0 included these additional devices:

So we could fake your device ID to 0x9BC5. In OpenCore Configurator --> DeviceProperties, we could add the following:

...
I dunno if Sleep functionality is supposed to work on Hackintoshes, but it does not in my case at present. (If it is supposed to work on Z490s, then this could be related to chipset device ID differences as I said above). The first time I tried using sleep it did nothing except blank the screen for two seconds. Tried again and the hardware did go into sleep mode, but upon waking MacOS booted fresh and gave a "Your computer was restarted because of a problem" notice.

Have you customized the USB port SSDT or created a USBPorts.kext tailored to your motherboard? We cannot use SSDT-UIAC-VISION-D-V2.aml directly.

...
In any case though, I see this as an excellent start. Would love to see others join me on this one, once the quirks are ironed out. The W480 Vision D and the Xeon W-1290P are going for $379 and $560 respectively, and given how heavily marked up the i9-10900K is at some stores, you just might come out ahead, and without having to sit in backorder hell.

Looks like someone is about to follow in your footsteps.

A couple photos of the system would be a nice addition to your post! (Just remove EXIF location info from photos.)

CORRECTION: device-id should be C59B0000. Those 4 zeros at the end are necessary.

 

[CaseySJ]

NOTE 5 has been added to the top of Post 1. USBInjectAll 0.7.6 can be downloaded from here.

 

[XStylus]

Congratulations! Which EFI did you use and what changes were necessary?

I used whatever was in OC-061-VISION-D.zip and then followed Step 4 to the letter, thus, no EFI changes whatsoever if Step 4 didn't instruct it. Was I supposed to?

This should be straightforward to fix. WhateverGreen does not yet support 0x9BC6, but version 1.4.0 included these additional devices:

So we could fake your device ID to 0x9BC5.

Excellent! I'll give that a shot. Also, I left a report with the WhateverGreen team. They responded fast and will be putting the Xeon iGPU DevIDs in version 1.4.3.

Have you customized the USB port SSDT or created a USBPorts.kext tailored to your motherboard? We cannot use SSDT-UIAC-VISION-D-V2.aml directly.

What step was that? I have not customized USB port SSDT at all, nor created a USBPorts.kext.

Looks like someone is about to follow in your footsteps.

It'll be nice to have company. I feel like the blind leading the blind.

A couple photos of the system would be a nice addition to your post! (Just remove EXIF location info from photos.)

Gotta make things look pretty first, but will do.

 

[CaseySJ]

...
What step was that? I have not customized USB port SSDT at all, nor created a USBPorts.kext.
...

This is the build guide for Z490 Vision D so there's no step for configuring USB ports for a different motherboard. Sleep will not work unless USB ports are properly configured. Please see:

The New Beginner's Guide to USB Port Configuration

Important Update: June 2023 From Big Sur 11.3 on the built-in OpenCore XhciPortLimit quirk no-longer worked as described. This became a known "bug", though in reality it was Apple changing their internal code, making a simple "peek and poke" to keep it operating, a difficult task. However, with...

www.tonymacx86.com

 

[XStylus]

...we could fake your device ID to 0x9BC5. In OpenCore Configurator --> DeviceProperties

Hrmmmm... That causes the system to hang during boot. So much for simple.

 

[CaseySJ]

Hrmmmm... That causes the system to hang during boot. So much for simple.

Also check that you have the correct PCI path for the iGPU. The path "PciRoot(0x0)/Pci(0x2,0x0)" is common to most Intel desktop processors, but should be confirmed through Hackintool. In the screenshot below we see Device Path in the rightmost column corresponding to Display Controller.

Also try the other supported device IDs: 9BC4 and 9BC8 (but reverse the byte order: C49B and C89B).