Jump to content

Radeon R9 Nano/Fury X Support Question

TopHatProductions115

By TopHatProductions115,
in ATi

 Share
8 posts in this topic

Recommended Posts

TopHatProductions115
TopHatProductions115
Posted
Posted (edited)

I have a Mac Pro (Mid 2010) running macOS Mojave 10.14.6. I picked up a Radeon R9 Nano a while ago, and now want to see if I can get it running. When I looked around online, I encountered multiple sources stating that they were able to get the Fiji cards working, to varying degrees:

 

From what I've seen in these threads, it appears as though I need to make a modified kext for this card to work. The first source (10.12.X) suggested adding device ID 0x73001002 (Fury/Nano), under the "Baffin" family, to info.plist in [AMDRadeonX4000.kext]. There was also some discussion of whether this info came from Netkas or Rominator. The second source stated that one should install RadeonDeInit and add device ID 0x7300 to [AMD9000Controller.kext]. The third source (Darwin 16.4.0 => ~10.12.X ?) provided a script for enabling all CUs on the card, and the OP was using a MacPro5,1 with an R9 Fury X. They linked a thread where someone added device ID 0x7300 to [AMDRadeonX4100.kext]. I'm wondering if the script does something similar to what was described in this thread:

 

Which kext(s) should I modify for this task?

 


EDIT 0: I also found this page, which showed device ID 0x73001002 under the section for [AMD9000Controller.kext]. This was for MacOS Mojave, Beta 11.

EDIT 1: I just found this file on GitHub. It's supposed to be applicable for macOS Catalina, which succeeds Mojave. It mentions device ID 0x7300 for [AMD9000Controller.kext].

Edited by TopHatProductions115
Added another additional source.
  • Like 1
Link to comment
Share on other sites
TopHatProductions115
TopHatProductions115
Posted
  • Author
Posted

After a bit of deliberation, I decided to forgo editing [AMD9000Controller.kext] by hand. I instead grabbed Kext Wizard and used it to load the following:

I will post the final results in a week or two, once my new monitor cable(s) arrive.

  • Like 1
Link to comment
Share on other sites
  • 1 year later...
TopHatProductions115
TopHatProductions115
Posted
  • Author
Posted (edited)

While the Lilu and WhateverGreen kexts worked on Mojave, they didn't work after upgrading to Monterey. Loading them caused the machine to stop here during boot up:
image.thumb.png.826ba127dbf0d355d9e2e73a13922972.png

Of all kexts mentioned in the OP, only AMDRadeonX4000.kext is present in /Library/Extensions for me after upgrading to Monterey. Most recent sources seem to point to AMD9000Controller.kext, but this thread post seems to suggest that it was removed with or before Ventura. I'm wondering if I need to get a recent version of that kext, to test it on Monterey. Will update if I make further progress...

EDIT 0: After digging around a bit more, I found AMD9000Controller.kext in /System/Library/Extensions instead. Searching loaded kexts revealed this: 

➜  ~ kextstat | grep -E -i "AMD"                                               
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
  107    1 0xffffff7f97824000 0xc6000    0xc6000    com.apple.kext.AMDSupport (4.0.8) C919BF91-96AD-3A3E-BBBB-F1BECC768979 <102 101 16 15 9 7 6 3 1>
  108    0 0xffffff7f80f19000 0x55000    0x55000    com.apple.kext.AMD9000Controller (4.0.8) C4AFA166-E56E-357D-AD96-44921A9286BC <107 102 101 16 15 7 6 3 1>
  142    0 0xffffff7f81025000 0x3000     0x3000     com.apple.kext.AMDRadeonServiceManager (4.0.8) B06BAA15-E36A-31B3-91A4-44A2B7EF2CB0 <16 6 3 1>
  143    0 0xffffff7f814d5000 0x4000     0x4000     com.apple.kext.AMDRadeonX4000HWServices (4.0.8) 7767D80D-039C-3E51-AD82-A4AE6C69988F <101 16 15 9 7 6 3 1>
  147    0 0xffffff7f8102b000 0x453000   0x453000   com.apple.kext.AMDRadeonX4000 (4.0.8) 21F52BE8-8669-3EDD-936C-CBD3BEC33ADE <146 101 69 16 9 7 6 3 1>
  148    0 0xffffff7f814e0000 0x2fe000   0x2fe000   com.apple.kext.AMDRadeonX4000HWLibs (1.0) AE66D5A2-D1AF-3BDA-A610-C5173B99C704 <16 7 6 3 1>

 

It's loaded. The R9 Fury is listed in System Information, but there's less info listed than when the card was previously working (Lilu+WhateverGreen).

 

 

EDIT 1: Also not getting anywhere when I (attempt to) use Open Core Legacy Patcher - no patches to apply? I'm in for a tough one...

Edited by TopHatProductions115
Added more information for users of macOS, after Mojave
Link to comment
Share on other sites
jalavoui
jalavoui
Posted
Posted

take a look at https://github.com/ChefKissInc

 

there are a few projects that might help, for instance in nootred you have this (seems related to your old cu patch)

  

void X5000::wrapGFX9SetupAndInitializeHWCapabilities(void *that) {

    setHWCapability<UInt32>(that, HWCapability::SECount, gpuInfo->gcNumSe);
    setHWCapability<UInt32>(that, HWCapability::SHPerSE, gpuInfo->gcNumShPerSe);
    setHWCapability<UInt32>(that, HWCapability::CUPerSH, gpuInfo->gcNumCuPerSh);
}

if you're skilled with xcode this might help start a new project

  • Like 2
Link to comment
Share on other sites
TopHatProductions115
TopHatProductions115
Posted
  • Author
Posted
16 hours ago, jalavoui said:

take a look at https://github.com/ChefKissInc

 

there are a few projects that might help, for instance in nootred you have this (seems related to your old cu patch)

  

void X5000::wrapGFX9SetupAndInitializeHWCapabilities(void *that) {

    setHWCapability<UInt32>(that, HWCapability::SECount, gpuInfo->gcNumSe);
    setHWCapability<UInt32>(that, HWCapability::SHPerSE, gpuInfo->gcNumShPerSe);
    setHWCapability<UInt32>(that, HWCapability::CUPerSH, gpuInfo->gcNumCuPerSh);
}

if you're skilled with xcode this might help start a new project

 

I'm not skilled in xcode (at least not yet). But I would be willing to contribute sometime in 2024. Can't do anything major this year, due to upcoming certification exam :( 

Link to comment
Share on other sites
  • 1 month later...
 Share
Go to topic listing
×
×
  • Create New...