Contribute
Register

Intel Hades Canyon NUC?

Status
Not open for further replies.
Hey @Gigamaxx, I have a Hades Canyon HVK with Mojave installed. I can test it. Please tell me the instructions.

You can try ATI FakeID:0x69AF1002 or any other ID in the list and turn on inject ATI with 10.14.2

Additional Vega GPUs with the following device IDs are supported in macOS 10.14.2:
-69AF: Radeon Pro Vega 16 & 20 (Vega 12 XLA & XTA)
-69A0: Unknown (Vega 12 GL MXT) (4GB HBM2)
-69A1: Unknown (Vega 12 GL MXL)
-69A3: Unknown (Vega 12 "Reserved")

The following Vega GPUs are listed in the primary AMD10000Controller driver, but are missing in the corresponding AMDRadeonX5000 driver and therefore not yet supported:
-69A2: Unknown (Vega 12 GL XL)
-66A0: Radeon Instinct MI60 (Vega 20)
-66A1: Unknown (Vega 20)
-66A2: Unknown (Vega 20)
-66A3: Unknown (Vega 20) (Custom Apple Radeon Pro)
-66A7: Unknown (Vega 20) (Custom Apple Radeon Pro)
-66AF: Unknown (Vega 20)
 
Hey @Gigamaxx, I have a Hades Canyon HVK with Mojave installed. I can test it. Please tell me the instructions.

If the Clover injection doesn't work you can test this method.

Here's a video tutorial link on how to do manual editing of the info.plist for graphics kexts.
How To: RX 480 8gb in a Apple Mac Pro OS X Sierra // Hackintosh

For the Vega you will need to do this to different kexts but it is the same method. Remember to drag the info.plist to the desktop to edit then save changes and drag it back to the Contents folder and replace and authenticate. ***Make sure to rebuild caches and repair permissions after the edits and before reboot. Kext Wizard is an east tool to do this with and allows you to choose an external disk as the target for rebuild. So if you use a USB to Sata adapter just select the right disk to edit and to repair/rebuild caches. Kext Wizard.zip

Xcode is good for editing the plists, and Textwrangler works as well. Pic below is with xCode.

Here are the kexts you will need to edit.

***Note do this at your own risk and make sure you have a working copy as a backup.***

#1 AMD100000Controllerkext, there are two locations to make the edits.

#2 AMD5000kext, edit both device ID areas ( especially the Vega 12 )

#3 AMDRadeon5000HWServiceskext, edit device IDs there as well.

****Make sure to rebuild caches and repair permissions after the edits and before reboot.

You could also try different framebuffers using Inject ATI = Yes and adding the names. See pic for names.

100000Controiller framebuffer names.png
 

Attachments

  • Kext Wizard.zip
    1.1 MB · Views: 179
Last edited:
@Gigamaxx, I need to add 0x694c1002 right? That is the device id for Polaris 22 aka Vega M GH afaik.
 
I tried both, editing the required kexts to add 0x694C1002 and booting by injecting that ID, as well booting with injecting ids that are already present. Nothing so far. Display still 7MB :( How to change frame-buffer name though ?
 
Please test this with latest Mojave beta (macOS 10.14.2 Developer Beta 3 available since yesterday, November 15, 2018).
 
Great. But I am a bit pessimistic. The announced Vega 12 GPU is the chip inside the Radeon Pro Vega 16 and 20 indeed, available in the new high-end MacBook Pro 15". It has a Vega architecture from start to end (GCN 5.0).

The Radeon RX Vega M in the Hades Canyon is marketed as being a "Vega" GPU, but it is not. It is recognized internally as a Polaris 22 as you know. But it is not a pure Polaris chip neither. It is somewhat a hybrid with a Polaris architecture (GCN 4.0) and a Vega memory controller (to keep things simple).

Still, it is a very good GPU* but Polaris 22Vega 12

So I think it won't work alas. But I'd be pleased to be wrong (especially as I'd like to buy this NUC for macOS!)
Keep up the good work and let us know.

* I notice that the low-end Polaris 22 GPU (Radeon RX Vega M GL) has the same number of shading and texture mapping units as the high-end Vega 12 GPU (Radeon Pro Vega 20).
 
Last edited:
I know right. I so want this to work. Though I can carry out most of my work in Linux and Windows, I'd like to be able to be a pure macOS user just like I was in my previous hackintosh. :( I see less and less hopes of it being able to work as time progress and it gets outdated. I'd try with different framebuffer names though.
 
I tried both, editing the required kexts to add 0x694C1002 and booting by injecting that ID, as well booting with injecting ids that are already present. Nothing so far. Display still 7MB :( How to change frame-buffer name though ?

For framebuffer use inject ATI and add the FBpatcher name below the inject option in clover boot menu.
 
Great. But I am a bit pessimistic. The announced Vega 12 GPU is the chip inside the Radeon Pro Vega 16 and 20 indeed, available in the new high-end MacBook Pro 15". It has a Vega architecture from start to end (GCN 5.0).

The Radeon RX Vega M in the Hades Canyon is marketed as being a "Vega" GPU, but it is not. It is recognized internally as a Polaris 22 as you know. But it is not a pure Polaris chip neither. It is somewhat a hybrid with a Polaris architecture (GCN 4.0) and a Vega memory controller (to keep things simple).

Still, it is a very good GPU* but Polaris 22Vega 12

So I think it won't work alas. But I'd be pleased to be wrong (especially as I'd like to buy this NUC for macOS!)
Keep up the good work and let us know.

* I notice that the low-end Polaris 22 GPU (Radeon RX Vega M GL) has the same number of shading and texture mapping units as the high-end Vega 12 GPU (Radeon Pro Vega 20).

Glad to know!
It very important information so we should try fakeid 0x67DF1002 and inject ATI use amd9500controller.kext
 
Status
Not open for further replies.
Back
Top