Jump to content
InsanelyMac Forum
TechGuru

R9 290x support in mavricks

Recommended Posts

so today i bought a 290x and tested it in mavericks 10.9.1 and it did not work one bit if anyone has any news about how to get it to work please inform me till then i will try clover bootloader 

 

vu5dhhb.jpg

Share this post


Link to post
Share on other sites
Advertisement

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

Share this post


Link to post
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.

Share this post


Link to post
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

 

 

Share this post


Link to post
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 

Share this post


Link to post
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

Share this post


Link to post
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

what do i name the rom to?

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

new update is out for 10.9.3 which main focus is audio and graphics drivers it's 301mb will report back 


update failed for the 290x sadly will wait for next beta 

Share this post


Link to post
Share on other sites

the update failed for the 290x i tried everything 

 

did you mean the update didn´t work or the 290x after the update !?

i have the 290x too, and installed 10.9 and no graphic-support .. start without any issues, but no graphic is bad :(

Share this post


Link to post
Share on other sites

If anyone can get the card to work, I'll happily buy two and see how well they can work together with Final Cut pro X on my hackintosh. Here's hoping. 

Share this post


Link to post
Share on other sites

Did anyone give the last two betas of 10.9.3 a go? Latest one released just hours ago.

System instantly reboots before desktop...

Share this post


Link to post
Share on other sites

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 

Share this post


Link to post
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 

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Posts

    • It seems nice that chris1111 provided a patch, but I can't -- in good conscience -- download a random binary file from github and run it on my system.    What is so proprietary about his patch that he can't include source? I think I'll wait until the updated driver comes out before I update...  Does anyone know where to look for updates to the webdriver from Nvidia? I've ever found a page that lists them, just links to the actual files to download, and that root is not 'browsable'. I'd like to monitor that site to see when a version is updated for the 17E202 build. Once that is released, I can update OSX and should be fine.  
    • hey MaLd0n  It's been a while since I used clover, so a lot of things went rusty. Can you please look at my setup and guide/help what should be done next?  https://fex.net/354949878474?fileId=441517695   Current setup:  GA-Z97X-UD3H Xeon e3 1245v3  Msi GTX 1050ti Gaming X
    • Hi @fabiosun and thank's for your patience with an old and stubborn man.   I am 100 % sure that my MSR 0xE2 register is unlocked thank's to you.   My system is 100% stable and I haven't had one kp with this configuration in the last two weeks.    I'm now running without TSCAdjustReseat.kext and I can't se any issues in performance with or without that kext. What I however can se is that the amount of total energy consumed during the test-cycle are 10 times higher without the kext (three times Cinebench CPU and two times Luxmark open CL) as you can see in the output from my AppleIntelInfo.kext attached in my earlier post.   I have tested running Cinebench five times in a row with or without TSC kext and have exactly the same performance (see attached files). Temperature is not a problem at all.   Everything seems to be fine so I guess I have to wait and see if upcoming 10.13.5 maybe recognise Intel Xeon w series processor as native.     
    • Tried with HPET enabled and disabled so I don't think it's that. I'd tried with bus ratio before to no effect but wouldn't hurt to try again. The clock runs at the correct speed.
    • could be an HPET / TSC Sync issue. does your system clock slow down or run faster then it should. also check cpu and buss ratios.


×