Jump to content

New ATI Drivers


438 posts in this topic

Recommended Posts

Well, my ADD2-N board is supposed to arrive in three days. I figure by then, it will be time to order an ATI x1600 because people will have them working perfectly... :(

 

 

Any concensus yet about which x1*'s are supported (QE & CI) in OS X? I'd hate to plunk down some hard earned dollars only to find that the x1300 or x1800 I got are hampered - like the :hysterical: x800...

Link to comment
Share on other sites

(crosspost)

 

can someone with a radeon X1600/X1800 please test 2048x1536 graphics mode?

 

F8 on boot, type "Graphics Mode"="2048x1536x32" (including the quotes) and let me know if it works, whether CI, QE and OpenGL accelleration still work etc.

 

Muchos Gracias.

Link to comment
Share on other sites

(crosspost)

 

can someone with a radeon X1600/X1800 please test 2048x1536 graphics mode?

 

F8 on boot, type "Graphics Mode"="2048x1536x32" (including the quotes) and let me know if it works, whether CI, QE and OpenGL accelleration still work etc.

 

Muchos Gracias.

 

or just do ?video and see if that mode is supported :withstupid:

Link to comment
Share on other sites

actually no... my GeForce 6800 reports some video modes with ?video which dont actually work. 1600x1280 is in there, but it will not boot at that res (it just falls back to 1280x1024).

 

i'm really keen to know if the X1800 (or, failing that, the X1600) can do that resolution, cos I mainly want to build a new hackintosh for iPhoto and eventually Aperture work.

Link to comment
Share on other sites

Wasn't there a topic telling that when you use "? video" all mode ending in "ba" are not working for your vesa card (and the bb ones should be working)?

 

I checked some of these myself and all "ba" ones are indeed not working on my laptop...

Link to comment
Share on other sites

In respect to my post about using the 10.4.4 kexts.

 

I've found its just the OpenGL executable that stops the system from booting, all other files can be replaced with the new versions.

 

I don't know if it can go higher than 1280x1024 as thats the max for my flat panel so can't test any higher.

Link to comment
Share on other sites

Hi :pirate2:

 

@munky:

 

I found some interesting possible reasons for the PCIe > PCI issue.

 

In the PCIe specs they wrote that PCIe accepts also PCI drivers. Nvidia even has a

translation chip for that on their graphics devices. Ati does not have that, but works,

too.

 

The kext you were searching for, where to enter the PCIe bus, is the

IOPCIFamily.kext. If you enter your own value in the PCI2PCI bus, it

will also detect the PCIe bus, but it is still displayed as PCI.

 

Second thing was about the IONameMatch values. You can find them in the plists of

the Ati-bundle files, for examle in Extensions/AppleNDRV/

 

They are always matching just "ATY,*". But if you install the Ati driver from the

website, the tool does not detect the card as an ATI, but as an ADP2,1.

 

Now the IONameMatch does the same thing than the IOPCIMatch, but for

OpenFirmware. So it is like our Vendor/Device ID, but not in hex value.

 

We all changed our ressources to match, but i wonder what would happen, if we

would change ATY to ADP2,1.

Link to comment
Share on other sites

Danman, (or anyone else)

 

Do you have an updated link for the Extensions? I got the framework ok, but the link from uploading.com is failing...

 

I'd love to test out my X1600 Pro...

 

TIA

 

I found it on another site...Thanks...

 

It's working now!!!

 

OpenGL is working now, and it looks purtty!!!!

 

Thanks Danman.

Link to comment
Share on other sites

ADP2,1 is the platform ID, not the video card ID.

 

on PPCs, the card shows up as a chip number doesn't it? like ATY, RV300. Don't know what wormy is, probably the "code" for the iMacs card in EFI. Could try changing to it match your card's chip.

Link to comment
Share on other sites

@xtraa: in the days of 10.4.1 and the macvidia alpha 1, i remember getting the bus detected (properly) as AGP after fiddling around. i'm sure we could fiddle plists to get the same thing to happen for PCIe. i'm not sure how much it would help, but IIRC it seemed to be a *tiny* bit faster.

 

then again, AGP is a specialised PCI slot, whereas PCI-E is kinda a new thing altogether (anyone know much about this? correct me if im wrong).

 

all I really want to know is if X1800s work, cos i'll go order one now if they do :lol:

Link to comment
Share on other sites

ADP2,1 is the platform ID, not the video card ID.

 

Yes thanks, i know :)

 

What i wanted to know was: when you install the ATI-driver-tool from the ATI website, (it will not work of course),

but after install, I was able to take a look in the options, and the ATI-tool detected the graphics card simply as

ADP2,1, too. :)

 

@xtraa: in the days of 10.4.1 and the macvidia alpha 1, i remember getting the bus detected (properly) as AGP after fiddling around. i'm sure we could fiddle plists to get the same thing to happen for PCIe. i'm not sure how much it would help, but IIRC it seemed to be a *tiny* bit faster.

 

Hmm, yes as I can remember it was a workaround with the AppleI386PCI.

 

then again, AGP is a specialised PCI slot, whereas PCI-E is kinda a new thing altogether (anyone know much about this? correct me if im wrong).

 

all I really want to know is if X1800s work, cos i'll go order one now if they do ;)

 

I can recomment you this here, this is all about pcie:

 

http://arstechnica.com/articles/paedia/hardware/pcie.ars/1

 

And context is: They made PCIe in that way, that the driver really don't care if it is PCIe or PCI. It just works, but much faster.

Link to comment
Share on other sites

For various reasons I have gone a step back to Windows XP on my frankenmac (and I already other thoro'bred Macs to play with). As I was completing the XP driver install with the Sapphire X600XT, which never worked under 10.4.3g, I noticed that Windows was installing a PCI to PCIe bridge chip driver. Perhaps this explains some of the problems with these PCIe cards—the lack of drivers for the onboard bridge. I notice a few people have had luck with some ATi X series cards from different vendors and wonder if this because some vendors don't use bridge chips. The X1600Pro seems to be working OK—does it have an onboard bridge or not?

Link to comment
Share on other sites

i think the PCI to PCI-E bridge is just the PCI-Express equivalent of the old CPU to AGP bridge - basically the piece of hardware which allows the CPU to talk to the bus. (EDIT: now having had a look at the arstechnica article (cheers xtraa), i know this is technically wrong, but i think the pcie 'switch' object is the equivalent of the AGP bridge)

 

if you find your device and vendor IDs and put them in a plist somewhere (IOPCIFamily.kext or something?) i'm sure you could get System Profiler to report Bus: PCIe. this, combined with the 10.4.4 drivers installed via the danman method would kick ass. or crash horribly. whatever :poster_oops:

 

EDIT2: aha!

 

"ATI, in contrast, has cards that support PCIe natively and therefore don't need the bridge chip."

 

So we know the X1600s *should not* need bridging in this way, therefore adding to IOPCIFamily might work....? (ok, learning as i go here, bear with me)

Link to comment
Share on other sites

the 10.4.4 ones, which this thread is all about.

 

they have been made to work on 10.4.3 for X1300, X1600 and X1800 cards. X1900 afaik is untested so far.

 

the thread on the 'other' forum explaining how to do it was lost in the DB corruption issue they had, so im not sure how im going to go about it when my X1800XL arrives...

Link to comment
Share on other sites

So can the above mentioned cards change their resolutions using the new drivers? Or do the files that are purposely not overwritten prevent that feature from appearing in the preference pane?

 

Even if it's less than 1280x1024, I'd like to know if there are ANY resolutions listed aside from the one your desktop is currently set to.

 

Anybody?

Link to comment
Share on other sites

the 10.4.4 ones, which this thread is all about.

 

they have been made to work on 10.4.3 for X1300, X1600 and X1800 cards. X1900 afaik is untested so far.

 

I look around in forum and can't find any positive report with X1300. Can you post link to this thread. If it really work I buy one.

Link to comment
Share on other sites

you're right - i cant find confirmation either. i apologise for the accidental misinformation. X1600 and X1800 are known to work (independantly reported). i would assume the X1300 is likely to work, given the kext name contains X1000, suggesting it would support the whole line.

 

i wouldnt touch an X1300 if i were you. even X1600s are a bit pants. i bought an X1800XL off ebay for £160 last night :D

 

@takuro: afaik no you cannot change resolution with those drivers, so its back to the "Graphics Mode" tweak at startup. even my GeForce 6800 AGP can do 2048x1536x32 on my old box, tho strangely it never managed 1600x1280. (NB: anyone having problems hitting 1600x1280, i advise trying for even higher - it worked for me :P im hoping my X1800XL (when it arrives) will do that resolution with full QE and CI too...)

 

anyway, np_ reported that to do resolution changing etc you'd need to write a new ATINDRV.kext, or get the 10.4.4 one working (not easy as it depends on EFI)

Link to comment
Share on other sites

All you need to do is add the extra AGL.Framework and OpenGL.Framework files (don't replace any) from the 10.4.4 framework

 

And add all the RadeonX1000 files into the Extensions folder from the 10.4.4 Extensions

 

Note: Both of these are on rapid share - check the osx86project thread for links.

 

repair the permissions (I did this through disk utility)

 

open terminal and type:

 

sudo -s

<enter your password>

 

chown -R root:wheel /System/Library/Extensions

chmod -R 755 /System/Library/Extensions

 

kextload ATIRadeonX1000.kext (just to check it has worked)

 

Reboot and enjoy CI & QE

 

Now the bad news...

 

Can't change the resolution (use the com.apple.Boot.plist flag instead)

There are very minor mouse artifacts (so far only noticed in safari)

 

but you can't have everything.....yet!

 

 

In moving the frameworks you say 'don't replace any' - I think I know what you mean but how exactly was that done? Finder or Terminal? More explicit instructions for that step would be greatly appreciated.

 

-Thanks

Link to comment
Share on other sites

 Share

×
×
  • Create New...