Radeon Compatibility Guide - ATI/AMD Graphics Cards

[velqn]

ATI injection is meant to be used to support old Radeon based cards I believe. I own an Sapphire R9 280x 3gb vapor-x, with or without injecting ATI it makes no difference for me.

What is your card model, vendor, id, version?

The default Radeon framebuffer AMD7000Controller supports quite good most of the R9 280x cards, did you try experimenting with framebuffers as suggested by the first post by Fl0rian?

 

[justr]

Hi Justr, from the forum post you linked i used the HawaiiReader tool to edit the MSI VBios i had successfully booted with.
I played around with it, noting that when i ran my card at the full 1500MHz my graphical glitches were worse than before, it may be the case that it's specifically the higher 1500MHz setting that my hardware/software combination doesn't like (I haven't yet tested this), this bios isn't flashed to the card and it's loaded through Clover.

Awesome! The option to just load the VBios through Clover-- and know that it works-- is great, because it makes it possible to have one VBios for El Capitan that's different from the actual stock VBios on the card for Windows. My flickering only occurs in El Capitan, not in Windows.

It also means one can run a slightly down-clocked/undervolted VBios for El Capitan (where I prefer lower temps, lower fans, and greater stability for video editing or photo editing), while still running the factory OC, or slight overclocked VBios on the card for when booting into Windows (where I'm mainly only ever going for gaming).

The main obstacle is that you can't really test things on the El Cap side regarding seeing frequencies and temps since HWsensors doesn't pick up info on the R9 200-series cards (it always reports 0 C and doesn't show fan RPM).

 

[ThE_MarD]

Heyyo,

ATI injection is meant to be used to support old Radeon based cards I believe. I own an Sapphire R9 280x 3gb vapor-x, with or without injecting ATI it makes no difference for me.

I believe this to be true. I tried "bdmesg" in the terminal when I tried "InjectATi=True" and bdmesg showed that Clover thought my MSI R9 390 Gaming 8G was an Evergreen Cedar GPU... so an AMD HD 5400 series which is probably why it thought I was using a random 7MB GPU.

Awesome! The option to just load the VBios through Clover-- and know that it works-- is great, because it makes it possible to have one VBios for El Capitan that's different from the actual stock VBios on the card for Windows. My flickering only occurs in El Capitan, not in Windows.

It also means one can run a slightly down-clocked/undervolted VBios for El Capitan (where I prefer lower temps, lower fans, and greater stability for video editing or photo editing), while still running the factory OC, or slight overclocked VBios on the card for when booting into Windows (where I'm mainly only ever going for gaming).

The main obstacle is that you can't really test things on the El Cap side regarding seeing frequencies and temps since HWsensors doesn't pick up info on the R9 200-series cards (it always reports 0 C and doesn't show fan RPM).

Interesting! Hmm maybe I'll try to dump my VBIOS in Windows via GPU-Z and try to use Clover with loadVBIOS=true and use mine to see if that fixes the issues I had.

 

[axydas]

Hello!!

I have an old desktop and I installed Yosemite 10.10.4 an it was working perfectly. Last week I installed the newer El Capitan 10.10.3. Everything is working fine except the graphic card - AMD HD 4550 1GB Sapphire. I followed the post 'Radeon Compatibility Guide - ATI/AMD Graphics Cards' and now the card is recognized but with only 5MB of VRAM.

Can you please help me to solve this issue?

 

[ruralarea]

I'm Running Mavericks on an Asus cm6870 MB, I7 3.39GHZ processor with 32 GB Ram. I also have an AMD Sapphire 7950 HD card.
I did the EFI boot Method for the graphics card and it works great for the most part however it would go black after a couple hours or so. Did i miss something i need some help please!

 

[justr]

Heyyo,



I believe this to be true. I tried "bdmesg" in the terminal when I tried "InjectATi=True" and bdmesg showed that Clover thought my MSI R9 390 Gaming 8G was an Evergreen Cedar GPU... so an AMD HD 5400 series which is probably why it thought I was using a random 7MB GPU.


Interesting! Hmm maybe I'll try to dump my VBIOS in Windows via GPU-Z and try to use Clover with loadVBIOS=true and use mine to see if that fixes the issues I had.

I can confirm that loadvbios in clover does work. I flashed my GPU back to the stock vbios, but used Clover to load a modified vbios with my fix at boot (modified so that it never drops the memory clocks, but lets the core clocks fluctuate). Booting from the flashed vbios (unfixed) as is gives me the jumping/flickering screen. Putting my modified vbios in the rom folder and having clover load that modified vbios on boot... no jumping/flickering.

I'm going to make a dedicated thread for this issue soon. We're far enough along to i) solve the issue, and ii) start gathering more experiences to see if there's a way to fix this while still letting memory clocks fluctuate. This is a real step ahead!

 

[Jakoozie]

ATI injection is meant to be used to support old Radeon based cards I believe. I own an Sapphire R9 280x 3gb vapor-x, with or without injecting ATI it makes no difference for me.

What is your card model, vendor, id, version?

The default Radeon framebuffer AMD7000Controller supports quite good most of the R9 280x cards, did you try experimenting with framebuffers as suggested by the first post by Fl0rian?

Hey, I say everything on my topic. I try using different frame buffers but I guess none work because when I do "ioreg | grep ATY" on terminal I got the same thing all the time. In meantime I already reply to Mork_vom_Ork with my bios decoded. Thanks!

 

[yacob841]

Still having issues with my Radeon 7950's giving me the "**GPU Hardware VM is enabled" error. Any new ideas?

 

[Mork_vom_Ork]

Still having issues with my Radeon 7950's giving me the "**GPU Hardware VM is enabled" error. Any new ideas?

That should not be a problem, cause my R9 280x reports the same message but still logs into OS X 10.11.4 Seems more to be a problem with wrong config.plist or wrong framebuffer patch.

Post your infos, so we can take a look at it.

 

[yacob841]

Hmm interesting, that's been the only thing I can link to it lol. Ok, here are my files. If you need anything else let me know.