cosmos321 Posted November 9, 2008 Share Posted November 9, 2008 Hello, I´m new here and i search the newest drivers for my hd3870 ( iDeneb 10.5.5. ) because i get an "error" like this when booting OS-X. : Picture ! I found that topic: http://forum.insanelymac.com/index.php?showtopic=107526 ! And at the end of poste#1 there is a link to an ATI Radeon HD 3870 but the upload is dated to the 05/29/2008 ! Is THIS realy the newest one?? Thanks for help! Link to comment Share on other sites More sharing options...
mitch_de Posted November 9, 2008 Share Posted November 9, 2008 I would try to get an gfxstring boot ! Use therefore the great+easy util EFISTUDIO (netkas) and use the orig. Apple drivers. It has a an Menüe for selecting your GPU. YOu MUST!!! remove any gpu injector (NATIT.KEXT) before reboot. http://www.mediafire.com/?mi2jyme5fxf This efistudion uses the standard Framebuffer plugin Lamna (in ATINDR.KEXT). Maybe it helps (if not working) to use the megadlon FB. To do that, you can also use EFISTUDIO and after selecting your card, change all shown Lamna into the megadlon (also the ..._parent). You cant use an gfxstring from an other ATI 3870 user, because often there are some little differences in the PCI-E Slot Number. Make allways your own! Link to comment Share on other sites More sharing options...
Kuebeker Posted November 9, 2008 Share Posted November 9, 2008 Goto: http://forum.insanelymac.com/index.php?showtopic=107526 look in the title post for : Update: try pkg for 2600 Pro & XT, 3850 & 3870 and maybe ( 2400 series ) also 3650 users try this Report back Download here This is what I tried. I have a Sapphire toxic HD 3870. It works but I am still having erratic fan spin up's an spin downs. especially if the shutdown/restart way botched. Link to comment Share on other sites More sharing options...
zuz_242 Posted November 11, 2008 Share Posted November 11, 2008 first: whats your sys config? amd / intel? motherboard chipset? i had the same "garbled screen" as you do with my 3870 with every driver i tried. in my case the problem got solved by changing the motherboard. (nforce chipset to amd chip) first i had to install without driver support / remove the kexts by hand. then, in vesa mode, i (re)installed the pkg and everthing is fine. Link to comment Share on other sites More sharing options...
Recommended Posts