Ati Radeon Hd 5870 For Mac

Mac / PCIe / Mini DisplayPort / DVI / 2560 x 1600 For amazing graphics processing power, the ATI Radeon HD 5870 with 1GB of GDDR5 memory is an ideal choice for visual creative, scientific, and technical applications. ATI Radeon HD 5870 includes three video ports: two Mini DisplayPorts and one dual-link DVI port. Apple still offers the ATI Radeon HD 4870 as an upgrade option for both 2009 and 2008 Mac Pros. The 4870, however, remains priced at $349 but is said to offer similar performance as the 5770 card.

The 'boot to black screen' issue as well as the broken sleep/wake have been fixed! Read below for details.​0.

IntroductionMost of you might have noticed that the Buyer's Guide doesn't list a single compatible AMD Radeon card at the moment. Graphics CardOOBmin.

OSXDevIDReference Port LayoutFramebufferKnown IssuesHD 7750Yes10.8.30x683F??HD 7770 / R7 250XYes10.8.30x683D2x mDP, HDMI, DVIDashimakiBlack screen issue since 10.10.3HD 7850Yes10.8.30x6819??noneHD 7870 / R9 270XYes10.8.30x68102x mDP, HDMI, DVIFutomakinoneR9 270 / R7 370No10.8.30x6811??DevID missingHD 7950 / R9 280Yes10.8.30x679A2x mDP, HDMI, DVIHamachinoneHD 7970 / R9 280XYes10.8.30x67982x mDP, HDMI, DVIHamachinone​ AMD8000Controller.kext (2nd Gen GCN architecture). Graphics CardOOBmin. OSXDevIDReference Port LayoutFramebufferKnown IssuesRX Vega56Yes10.12.60x687F3x DP, HDMIKamarang / Iriri?Needs RadeonDeInit, early driversRX Vega64Yes10.12.60x687F3x DP, HDMIKamarang / Iriri?Needs RadeonDeInit, early drivers​ Notes / Legend:. OOB = No means (unless otherwise stated) you'll have to spoof or add the device ID to enable support. 'Framebuffer' is the framebuffer that matches the reference port layout best.

Non-reference cards might work better with others. 'min OSX' refers to the initial version which first added driver support for a specific chipset. The device ID might have been added in a later release, so your card might not work OOB at this version.Note on XFX cards:Many people are reporting problems with XFX cards, especially HD 7xxx / R9 generation. They're using a custom BIOS which can cause a crash upon booting, which can't be fixed in OS X.A common solution is either flashing a alternate VBIOS on your card (only do if you can recover form a bad flash!) or (without flashing).Note on current AMD cards (3rd & 4th Gen GCN):Many modern AMD GPUs are incorrectly initialized during boot phase, which will can lead to serious issues in OS X (e.g. Boot to black screen or crash after sleep/wake). This was first solved by the Lilu plugin.

Extensive, resulting in a DSDT patch. This knowledge has been incorporated into Clover (starting with rev. 4296) and can be enabled from the config.plist like this. GraphicsRadeonDeInitWe recommend using the Clover solution.Note on Fiji and Polaris 10 based GPUs (Deprecated since 10.12.6):OS X still lacks native graphics acceleration for R9 Nano / Fury / Fury X and RX 470 / 480. However, they can use the 'Baffin' accelerator (e.g.

By spoofing the device ID), which was originally made for Polaris 11 based GPUs (especially the Radeon Pro GPUs in 2016 rMBP).They'll be limited to just 16 Compute Units though, which affects the compute performance notably. It's possible to unlock their full potential with a (alternate way: feature).3. Finding or patching a compatible framebufferAs stated before, choosing a card with reference layout should usually give you a 100% matching framebuffer out of the box.

And even if your card differs from reference design or you've chosen a GPU without any 'reference framebuffers' (e.g. R9 380), RadeonFramebuffer will do the job perfectly fine in most cases. But what to do if it doesn't?Finding the best FramebufferA quite common way to find the best matching framebuffer is injecting every available framebuffer of a GPU family and manually testing the compatibility with each port until you find one that suits your needs. While this might work, it’s obviously a very time-consuming way to test compatibility, so I wouldn't recommend blindly testing to anyone. It's way faster to analyze the compatibility of a specific framebuffer directly by having a look in your graphics cards vBIOS.The mapping of a specific port is defined by four different identifiers: Encoder ID, Transmitter ID, Hotplug ID and Sense ID. All of them have to match for perfect compatibility.

Was one of Adrenaline Vaults top shareware games. Got Ernie award for most addictive game. The game is a remake for the PC of my Amiga game Deluxe Galaga. Warblade full version.

A mismatch of the hotplug ID will usually just disable the hot plug detection (you might need to put your computer to sleep to activate the port), while a mismatch of the other 3 IDs will result in a black or garbled screen. Getting this mapping from the BIOS is easy:.

Dump your vBIOS (e.g. With atiflash.exe in DOS or with Clover). Run. This will give you the encoder ID and transmitter ID. Run my fork of radeonbiosdecode (attached to this post). This will return the hotplug ID and sense ID.

Note: Other tutorials claim that the hotplug ID equals the 'Connector index'. This might be true in special cases, but it's definitely not in general. Using my fork will reveal the real hotplug ID of each port.The following screenshot shows the complete port mapping at the example of a Radeon HD 7950 Mac Edition with Hamachi framebuffer. Each line of the framebuffer equals one physical port, and as you can see, Hamachi perfectly matches! You'll certainly have noticed that the framebuffer contains a lot more information than just those 4 identifiers.

I won't cover every single aspect here, just one short note one the connector type which most other tutorials neglect: The first two bytes (byte-swapped!) of each line declare the type of the connector, e.g.:0x4 = DualLink-DVI0x200 = SingleLink-DVI0x400 = (mini)DisplayPort0x800 = HDMIDue to the compatibility (some) of those protocols it is way less important to match the connector type than one would think: For example, the DisplayPort specification guarantees backward compatibility to single-link DVI and HDMI. From my experience it's no problem to have a physical DVI port declared as DisplayPort as long as you don't exceed FullHD resolution. Same applies to some other combinations.Patching the FramebufferIf OS X doesn't offer a matching framebuffer for your card you'll have to patch a existing one.

This is covered in great detail in a.4. Spoofing the Device IDDue to popular demand, here’s a short guide on enabling GPUs with missing device ID in the drivers using Clovers 'FakeID' feature. For the scope of this tutorial, let’s assume you want to enable a Radeon R9 270, which isn’t OOB. The device ID of this card is 0x6811.First you have to find a similar graphics card using the same chipset which is supported OOB (have a look in the chart above).

In our example this could be a Radeon R9 270X (0x6810).The full ID of this graphics card consists of the device ID and the vendor ID (always 0x1002). So the full R9 270X ID is 0x68101002.In Clover, you have to set:- FakeID / ATI = full ID (here: 0x68101002)- Inject / ATI = true- FBName = framebuffer name (here:Futomaki enter some random garbage in case you don’t want to use a framebuffer, the driver will default to RadeonFramebuffer)- FixDisplay = trueOn the next boot, you should have full acceleration with your unsupported GPU!If it didn’t work, you can verify the ID by looking in the System Profiler - Graphics section. If the device ID listed there didn’t change expectedly, you might have a typo somewhere.5. FAQWhere can I download drivers for my Radeon XYZ?AMD Radeon drivers are always provided by Apple as part of their regular system updates.

You might find some dubious patched kexts in the internet which might be binary compatible to your OS if you’re lucky, but I’d advice against using those. Keep your system up to date and you’ll always have the latest drivers. Understand what your problems are and apply the patches yourself with Clover so they’ll survive system updates.On the one hand this policy is a good thing, because you don’t have any hassle comparable to the Nvidia Web Drivers when a new OS X update arrives. On the other hand, it’s totally up to Apple when they include some new Radeons and which they choose to be supported OOB. Nvidia is usually a lot faster updating their Web Drivers to support new GPUs.My Multi-screen setup won't work!

What should I do?!First, make sure all ports work with just one screen attached. If you want to use 3 or more displays, remember that you'll need native DisplayPort screens or active DisplayPort adaptors (see )!If you're using RadeonFramebuffer, try to inject a matching framebuffer (and vice versa).I have found a Mac EFI ROM for my card in the internet.

Will flashing it make my card more compatible / faster / Better?Nope, not at all. Your Hackintosh isn’t able to utilize a MacPro EFI, no matter if your MoBo has a legacy BIOS or a modern UEFI, so it will fall back to the legacy vBIOS on your card either way. It won’t change anything.OS X boots up fine but everything is sluggish and/or the resolution is low!Most certainly the driver didn't load because the device ID of your card isn't in their (check compatibility chart above). Spoof your device ID with Clover to match a similar, supported card or add your device ID to both kexts (not recommended).My GPU shows up as 'HD 7xxx' (or similar)!

Do I have to worry?This just means that you're not injecting anything GPU related, no need to worry. Read the Framebuffer section in chapter 1 again. Other common placeholder strings are 'HD 8xxx' or 'R9 xxx'.Which Device ID does the Radeon XYZ have?The vBIOS Database from TechPowerUp (Link: ) is always a good start.

If you've already installed the card in your machine you might also consult the System Profiler.What about El Capitan and Metal support?As of today, there have been no significant driver changes in El Capitan compared to Yosemite.Metal is supported starting with HD 7xxx series. Older cards are still supported, just without Metal.How to enable dual cable 5K support (e.g. Dell UP2715K)?It's necessary to edit AGDP, details are in.

Thanks for finding that out!You have some additional information which you think should be included here? Found a mistake or an unclear explanation? Feel free to leave some feedback here! I've been building Hackintoshes for the last 6 years or so and I've built 4 now.

I always use Nvidia cards because Im a fan boy and they are easy to get working. (best of all Cuda.) The most recent system I built was on the x99 platform and it deff was the toughest to iron out all the bugs. I built it with a GTX 780ti because it has more cuda cores than the 980 and was $600 CND$.I do a lot of video editing.

It is 80% of my job and so I figured the 780ti would haul through 4k video. Well It never has and although it should be an amazing video editing card it just isn't on OS X no matter what anyone tells me. So I more recently sold it and 'Upgraded' to a GTX 980. Mostly because of all the hype everyone has over how good the 970 and 980 are in OS X. Yes they are easy to get working and Yes Nvidia is awesome to quickly come out with new drivers. But the 980 still struggled with 4k video in OSX. Im not a noob.

I did a fresh install of OS X and clover. Still no improvement. So for kicks I decided to drop in an AMD card.

I found an HD 7970 on craigslist for $120.HOLY CRAP! I can't believe what a difference it makes. Smooth OS X UI. Shreds 4K video editing. I honestly don't get it. Is it because its natively supported in OS X? Is it because it handles OpenCL so much better?

Obviously the 780ti and 980 stomp all over it in gaming on windows but WOW in OS X it is awesome! And I'm an Nvidia fan boy lol. I think I'll try to find another one or crossfire it with 280x since its the same card. At least it'll give me some more power in gaming on windows. But this is my honest opinion! It even runs better than my last system which had a gtx 670 4gb.

And it was natively supported in MLBTW: To get all ports working I on the gigabyte HD 7970 ghz I used 'Radeon' FB and ATI inject. Just throwing my thoughts and experience out there to anyone who is in my shoes. I've been building Hackintoshes for the last 6 years or so and I've built 4 now. I always use Nvidia cards because Im a fan boy and they are easy to get working. (best of all Cuda.) The most recent system I built was on the x99 platform and it deff was the toughest to iron out all the bugs.

I built it with a GTX 780ti because it has more cuda cores than the 980 and was $600 CND$.I do a lot of video editing. It is 80% of my job and so I figured the 780ti would haul through 4k video. Well It never has and although it should be an amazing video editing card it just isn't on OS X no matter what anyone tells me. So I more recently sold it and 'Upgraded' to a GTX 980. Mostly because of all the hype everyone has over how good the 970 and 980 are in OS X.

Yes they are easy to get working and Yes Nvidia is awesome to quickly come out with new drivers. But the 980 still struggled with 4k video in OSX. Im not a noob. I did a fresh install of OS X and clover. Still no improvement.

So for kicks I decided to drop in an AMD card. I found an HD 7970 on craigslist for $120.HOLY CRAP! I can't believe what a difference it makes. Smooth OS X UI. Shreds 4K video editing. I honestly don't get it. Is it because its natively supported in OS X?

Is it because it handles OpenCL so much better? Obviously the 780ti and 980 stomp all over it in gaming on windows but WOW in OS X it is awesome! And I'm an Nvidia fan boy lol. I think I'll try to find another one or crossfire it with 280x since its the same card. At least it'll give me some more power in gaming on windows. But this is my honest opinion! It even runs better than my last system which had a gtx 670 4gb.

And it was natively supported in MLBTW: To get all ports working I on the gigabyte HD 7970 ghz I used 'Radeon' FB and ATI inject. Just throwing my thoughts and experience out there to anyone who is in my shoes.