Jump to content

R9 290x support in mavricks


TechGuru
 Share

64 posts in this topic

Recommended Posts

  • 2 weeks later...

hello

 

take a look here

 

http://www.insanelymac.com/forum/topic/294498-amd-r9-270-problem/?do=findComment&comment=1975032

 

anyway u should enable the graphics in the usual way

 

editing the kext

 

good hack

that kinda worked but now mavericks won't boot in -x or at all i was using 10.9.2 which is the one with the drivers for my 290x

Link to comment
Share on other sites

hello

 

take a look here

 

http://www.insanelymac.com/forum/topic/294498-amd-r9-270-problem/?do=findComment&comment=1975032

 

anyway u should enable the graphics in the usual way

 

editing the kext

 

good hack

 

Does this method apply to the R9 290X as well? As far as I can see the thread you linked to dealt with problems on a R9 270. These are just re-labelled Radeon 7xxx. The 290(X) is a different GPU architecture (Hawaii). I am not sure if those are supported in any way in Mavericks by now.

Link to comment
Share on other sites

I'm not all all sure that 10.9.2 has drivers for Hawaii (r9 290x/290).

 

My R9 290 has a device id:  0x67b11002

 

In AMDRadeonX4000.kext I found a device id: 0x67b01002 in the Hawaii section.

 

This device id isn't present in AMD7000Controller.kext

 

 

Link to comment
Share on other sites

I'm not all all sure that 10.9.2 has drivers for Hawaii (r9 290x/290).

 

My R9 290 has a device id:  0x67b11002

 

In AMDRadeonX4000.kext I found a device id: 0x67b01002 in the Hawaii section.

 

This device id isn't present in AMD7000Controller.kext

i added the device id but i need a framebuffer name and a framebuffer set up before i can get a kext loaded to make the device work if anyone can provide me with that info from it's bios i can make the 290x work 

Link to comment
Share on other sites

well, you sure that not is a problem with the caches and permissions? you can try extract .rom vgabios, and rename and add UseAtiRom=Yes to the boot plist, install the kext lspci.kext and run this: then post here, and a Darwin Dumper report, you can use GPUZ to .rom vgabios

 

ioreg | grep ATY

 

 sudo kextstat | grep AMD

 

 

lspci -nnvd 0x1002: | grep -B2 Subsystem

Link to comment
Share on other sites

  • 2 weeks later...

well, you sure that not is a problem with the caches and permissions? you can try extract .rom vgabios, and rename and add UseAtiRom=Yes to the boot plist, install the kext lspci.kext and run this: then post here, and a Darwin Dumper report, you can use GPUZ to .rom vgabios

 

ioreg | grep ATY

 

 sudo kextstat | grep AMD

 

 

lspci -nnvd 0x1002: | grep -B2 Subsystem

what do i name the rom to?

Link to comment
Share on other sites

  • 1 month later...

I built a hackintosh with dual 280x a while ago. One card burned up, more or less (after one month of 24/7 mining it just stopped working). I got it replace on warranty for a 290x, but now when booting with the 290x installed (all monitor connected to the 280x board) OS X freezes about 10-20 seconds after booting to desktop. Console shows some errors with CI, so probably graphics related (GPU shows up as "unknown" in system info).

 

Is there any way to disable the gpu completely until compatible drivers appear, to be able to boot without physically removing the card? Also, alpha.delta, what FakeID are you using? It's my understanding the the current drivers offer no Hawaii support at all, so even if you trick the OS into using the standard ATI driver, it wouldn't work at all.

 

Hoping for hawaii support in 10.9.2!

Link to comment
Share on other sites

  • 2 weeks later...

Update: Installed 10.9.2 today and tried the 290X - OS X still only recognizes it as "Unknown" in system profiler. It does not freeze anymore when booting with the 290x connected (always something), but it seems the 10.9.2 drivers are not supporting the Hawaii chip yet. Tried adding the device ID to the AMD kexts, but that didn't help.

Link to comment
Share on other sites

  • 2 weeks later...
  • 3 weeks later...

the current beta i did not test as my ssd is out of order but i did snoop through the drivers on vmware and can say with pride it's looking good and since amd released the w9100 work station cards we will get drivers very soon maybe by 10.9.3 release or 10.9.4 a new ssd will be here soon maybe by next friday and i shall continue my work 

Link to comment
Share on other sites

<key>AMDHawaiiGraphicsAccelerator</key>

<dict>

<key>ATIEnableWideBlitSupport</key>

<true/>

<key>ATIUseTearingWideBlit</key>

<false/>

<key>CFBundleIdentifier</key>

<string>com.apple.AMDRadeonX4000</string>

<key>GpuDebugPolicy</key>

<integer>0</integer>

<key>IOClass</key>

<string>AMDHawaiiGraphicsAccelerator</string>

<key>IODVDBundleName</key>

<string>AMDRadeonVADriver</string>

<key>IOKitDebug</key>

<integer>0</integer>

<key>IOMatchCategory</key>

<string>IOAccelerator</string>

<key>IOPCIMatch</key>

<string>0x67B01002</string>

<key>IOProbeScore</key>

<integer>200</integer>

<key>IOProviderClass</key>

<string>IOPCIDevice</string>

<key>IOSourceVersion</key>

<string>0.0.0.0.0</string>

<key>IOVARendererID</key>

<integer>16908288</integer>

<key>sensor-properties</key>

<array>

<dict>

<key>device_type</key>

<data>

Z3B1LXNlbnNvcg==

</data>

<key>location</key>

<string>GPU</string>

<key>name</key>

<string>gpu-sensor</string>

<key>polling-period</key>

<data>

AAAAAQAAAAA=

</data>

<key>reg</key>

<data>

AAAAAg==

</data>

<key>sample-period</key>

<data>

AAAAAACYmAA=

</data>

<key>sensor-id</key>

<data>

AAAABg==

</data>

<key>version</key>

<data>

AAAAAg==

</data>

<key>zone</key>

<data>

AAAAAg==

</data>

</dict>

</array>

</dict>

it's there ......and more great news the device id is in amd7000controller.kext driver hmm but what i need to know is the framebuffer in the right place and working 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...