Jump to content

Radeon R9 270x Framebuffer/ID problem?


conorgill
 Share

8 posts in this topic

Recommended Posts

Hi all! My first post here  :)

 

First of all, I want to say a warm hello & thank you to everyone on here! InsanelyMac has pulled me out of the s**t many a time before now!  :rofl:

 

On the topic of this graphics card - I have followed Vlada's InsanelyMac post (Here) regarding this GPU & I haven't had much luck!

 

Basically, I have the Sapphire Radeon R9 270x running on (Niresh) Mavericks 10.9.2 - it's displaying as 'Radeon HD 7xxx 2048 MB'.. I am getting full resolution, and I assume QE/CI is working as I can make a move in Chess. However, running a LuxMark benchmark I am getting a "clBuildProgram -11" error, and in Unigine Heaven I am barely scraping 10fps with the settings on Extreme  :(

 

I have tried installing Vlada's driver package and it just gives me nothing (Black screen on DVI, screen goes off completely on HDMI). I have tried the Terminal method too, still no luck. The only section I could not follow properly was the DSDT section - I couldn't find the "PEGP" device in MaciASL, my Graphics Card is on PC02 according to IORegistryExplorer.

 

So I guess my question is, has my n00b level reached a new extreme & I'm missing something completely obvious? Or should everything be working?

 

BTW, I have another Mac installation on my second HDD, so copying/restoring {censored}-ups is easy enough for me!

 

 

Thanks in advance!  ^_^

Conor

 

 

Link to comment
Share on other sites

Hello everybody. I`ve just successfully patched my Asus R9 280X. Everything is OK. BUT!

I can`t understand why pushing on "monitors" in settings, system settings freeze. 

Before patching i had same situation.

Yosemite DP6.

 

Anybody know why it happens?

Does system preferences freeze or does your entire computer freeze? You should check if you can see any Console messages when it happens.

 

I don't know how many displays you are using, but try booting with a single display at a time from each port, and see if there's a particular port that's causing it. If you can find that only 1 port is causing it, maybe try different control flags for that port.

Link to comment
Share on other sites

 Share

×
×
  • Create New...