I have just installed Mavericks and had 5 displays running from my Mac 4.1, 3 x from my flashed XFX 5770 card ( 2x DVI + Display Port ) and 2 x from my GT120 (DVI + Mini DP) . I have tried for hours to get this set up working in Snow Leopard, but cant get it to work, so I am guessing that the drivers have been updated in Mavericks. If I leave all the monitors plugged in to the same ports it just doesnt work when I boot back to SL 10.6.8, it senses the monitor but will not display anything...
Can anybody explain how I could used the Mavericks display driver in Snow Leopard 10.6.8
BTW I need to use SL with my work software, I cant use Mavericks...
I think I've made some progress in understanding why displayport isn't working for non-vanilla 5000 series ATI cards. I have been able to get displayport working with a simple renaming of certain personalities in ATI5000Controller. Furthermore, I have been able to get displayport working when RadeonFramebuffer is loaded.
I have posted previously about how you can get displayport working if you swap in port mappings that are specific for your card into the vanilla framebuffer personalities (such as Hoolock, or Langur): http://forum.netkas.org/index.php/topic,864.0.html
This made me wonder, is there something in ATI5000Controller which determines whether displayport is working? or is it some other kext which is making this happen? I looked into the ATI5000Controller for differences in how the vanilla personalities like Hoolock and Langur were treated relative to the other, non-vanilla, personalities like Vervet and Uakari. I used idapro and hexsys (thanks Netkas for the suggestion!). However, I couldn't find a difference (besides the different port mappings) in how the different personalities were defined in that kext. Weird.
So I decided that it must be another kext which is determining that displayport only works for vanilla framebuffers. What if what's really important is that the card is injected as Hoolock by Chameleon or ATYinit, and not what happens in the ATI5000Controller? To test this, I opened up the ATI5000Controller binary (you can do this in any old text editor), and replaced all instances of Hoolock with Hoolocc (misspelled on purpose) and replaced all instances of Zonalis (the framebuffer personality for my card) with Hoolock. Now instead of using the default code for Hoolock, the code for Zonalis is used , because it is now named Hoolock! This worked beautifully, and displayport worked great even though the code for Zonalis was being used, and the code for Hoolock in wasn't being accessed at all, mainly because it had been renamed to Hoolocc.
The coolness didn't stop there. As has been posted by Netkas on his blog a while ago, if you do not inject your card, these new kexts will load your ports properly using "RadeonFramebuffer", but, at least for 5xxx cards, displayport and active adapters do not work. No doubt several of you have also noticed that if you inject a framebuffer that doesn't exist (for example, AtiConfig=asdf), then RadeonFramebuffer will load, again with the same properties. I found that if you inject Hoolock (AtiConfig=Hoolock) when Hoolock is misspelled in ATI5000Controller (i.e. rename all instances from Hoolock to Hoolocc) then it defaults to RadeonFramebuffer and loads all the ports correctly. But in this case, displayport also works! This is exciting because it enables dispalyport for 5xxx cards without the user having to manually determine what framebuffer is best and whether port mappings need to be edited. Unfortunately, this does not solve the geekbench/steam crashing issue seen with RadeonFramebuffer.
All this means that ATI5000Controller does not determine whether displayport works for 5xxx cards. Instead, it must be another kext which requires that a vanilla framebuffer personality is injected. What this kext is I don't know, does anyone have a guess?
I have attached links to two edited ATI5000Controller files from 10.6.8.
The first one will load RadeonFramebuffer if you specifiy AtiConfig=Hoolock or AtiConfig=Langur. This should work for any 5xxx card but will have the geekbench crashing issue.
The second will load the code for Vervet if you specify AtiConfig=Hoolock and the code for Uakari if you specify AtiConfig=Langur This should work for the standard 5770 and 5870 cards (respectively).
I hope this rather painlessly gets displayport working for people in 10.6.8 as it was working in 10.6.7. Let me know if it works for you.http://www.mediafire.com/?u5f9b8yb0yc8vewhttp://www.mediafire.com/?uzzvs2glyomlbs7