Jump to content

borisbadenov ATI X1000-series Solution

RobNyc

By RobNyc,
in ATi

 Share
1381 posts in this topic

Recommended Posts

Wayland
Wayland
Posted
Posted
[ FINAL UPDATE - SOLVED ]

 

BABLEFISH - I'm in no way {censored}, but I love you man!!!!!! You just made my day!

 

Zip-a-dee-doo-dah, zip-a-dee-ay,

My, oh, my, what a wonderful day.

Plenty of sunshine headin' my way,

Zip-a-dee-doo-dah, zip-a-dee-ay!

Mister Bluebird's on my shoulder,

It's the truth, it's "actch'll"

Everything is "satisfactch'll.

 

Listening To The Song [midi]

 

Thanks to all those who helped!!!! Cheers m8s

 

Edited :: DVI Works!!! yipeeeee :) & QE2D enabled ... I'll be back with the benchies

 

That was truely funny :D

MacSpaces
MacSpaces
Posted
Posted
Regarding ATI X1600 Pro PCI-E.

 

I would concider myself not much of a serious hacker but I did manage to get full compatability with my video card. I have an ASRock 775 Dual 915GL mobo, Celeron D 330J with onboard GMA900 and running 10.4.5. I recently purchased a MSI X1600 Pro PCI-E video card, read tons on this site, made notes, etc and after a good day's work, I finally got my card to work 100% with my set-up. Full QE-CI, refreshrates, resolutions changing, etc and not tearing! Look at my screen shot to prove it.

 

Before I installed my card, I deleted all other ATI files (in the /system/library/extensions), the I edited my plist in each of the ATIRadeonX1000 files to match my device <key>IOPCIMatch</key> <string>0x71C21002</string>

 

Then, inside my ATINDRV.kext, change <string>IONDRVDevice</string> to <string>IOPCIDevice</string> and change this line <key>IONameMatch</key> <string>ATY,WORMY</string> to read <key>IONameMatch</key><string>display</string>

 

In the ATIRadeonX1000GA.plugin, you need to change your device ID twice and do note that it need to be backwards, <key>100271C2-0000-0000-0000-000a27898d3e</key> and <string>100271C2-0000-0000-0000-000a27898d3e</string>

 

In all the plists, I just dele=ted all other references to other device ID's After this, I deleted the mext and kext.cache, and ran: sudo kext.cache -k /System/Library/Extentions AFter that, fix permissions, rebooted and smiled as my system worked as it should.post-14928-1147909028_thumb.png

 

 

Are you using dvi or vga?

i currently have gma950 board so everything works but want to beef up my rig with a dedicatred video card

i might just purchase the one you have since everything is supported from what it seems...

 

let me know if dvi is working 1005

kuruu
kuruu
Posted
Posted
Are people seeing much increased performance with an ATI card as opposed to, say, a built-in GMA950? I understand games will be a lot faster, but I'm more interested in general GUI snappiness, Xbench scores, and the performance of apps like Lightroom/Aperture.

 

Thanks,

 

/blkblt

just for your curiosity I have attached two xbench results. one with the gma, one with x1600pro and everything enabled. (thanks to borisbadenov)

 

you'll notice that in opengl the gma is strides ahead. I have no explanation. Both are with beamsync disabled and rebooted.

 

as for aperture... there is a definite benefit, but not as big as you might think... personally i think it is still worth it, but it may not be for you.

 

edit: can't seem to attach. but you get the idea.

Black Knight
Black Knight
Posted
Posted

Munky, I haven't tried it yet, but I will later today. I did a reinstall of Jas's 10.4.6 last night and tried with the 10.4.5 kexts and ATINDRV.kext and ran verbose startup; my results were that the blue screen never loaded and left the verbose output on the screen, but I had sound and full control. I couldn't see what I was doing, but I knew that I was controlling Mac. I then made sure that I was using the 10.4.5 OpenGL framework since I had the 10.4.5 ATINDRV.kext, but still got the same result. The only thing that let me have full acceleration, but without res changing, etc was to remove ATINDRV.kext.

WiZMaC
WiZMaC
Posted
Posted

Black Knight-

Why don't you give bablefish's method a try?!

 

It's quite easy and it worked instantly... Download 10.4.6, extract all needed ATI kexts from the extension's directory using pacifist, do the necessary mods - boris's method and reboot.

 

I have DVI and QE/QE2D/CI working here, including res change. I've also updated most of the kexts using this method excluding system.kext ...

Black Knight
Black Knight
Posted
Posted
I had the exact same problem with my ATI xpresss 200 board. I got a 945 board instead.

 

If you're referring to my problem, I can't really do that since I am using an Athlon 64 setup and not an Intel.

bobo2211
bobo2211
Posted
Posted

i have a tip for everyone who stuck after all :

 

if you have the 10.4.6 DVD (JaS), don't choose the 10.4.6 Combo Update in the installation process, it means you will have only 10.4.4 System but you got QE/CI (after this mod-methode).

 

i did it and it WORKS !!!

post-36826-1149534028_thumb.png

aberracus
aberracus
Posted
Posted
just for your curiosity I have attached two xbench results. one with the gma, one with x1600pro and everything enabled. (thanks to borisbadenov)

 

you'll notice that in opengl the gma is strides ahead. I have no explanation. Both are with beamsync disabled and rebooted.

 

as for aperture... there is a definite benefit, but not as big as you might think... personally i think it is still worth it, but it may not be for you.

 

edit: can't seem to attach. but you get the idea.

 

Motion and apperture are much better over gm900 with ati x1600xt, but i really cant say over 950, AND it was a 1 procesor against 2 dual processors, so maybe teh difference isnt in the video card.

Nuno Maia
Nuno Maia
Posted
Posted
Black Knight-

 

Why don't you give bablefish's method a try?!

 

It's quite easy and it worked instantly... Download 10.4.6, extract all needed ATI kexts from the extension's directory using pacifist, do the necessary mods - boris's method and reboot.

 

I have DVI and QE/QE2D/CI working here, including res change. I've also updated most of the kexts using this method excluding system.kext ...

 

 

Hi!

 

Got a new Sapphire X1600XT, finally got my new 2005FPW Dell.

Using Myzar's 10.4.5 everythink working except DVI :hysterical:

 

tried with 10.4.5 Kext's, tried the method Bablefish and you (TeKKi) sugested and no luck...

Although Im now using 10.4.6 Kext's that didnt work with my previous display adapter (GeCube X1600Pro)

 

here are my kext's:

 

ATINDRV.kext

 

<dict>

<key>CFBundleDevelopmentRegion</key>

<string>English</string>

<key>CFBundleExecutable</key>

<string>ATINDRV</string>

<key>CFBundleGetInfoString</key>

<string>ATINDRV 1.4.26.11 (1.0f204)</string>

<key>CFBundleIdentifier</key>

<string>com.apple.kext.ATINDRV</string>

<key>CFBundleInfoDictionaryVersion</key>

<string>6.0</string>

<key>CFBundleName</key>

<string>com.apple.driver.ATINDRV</string>

<key>CFBundlePackageType</key>

<string>KEXT</string>

<key>CFBundleShortVersionString</key>

<string>1.4.26</string>

<key>CFBundleSignature</key>

<string>????</string>

<key>CFBundleVersion</key>

<string>4.2.6</string>

<key>IOKitPersonalities</key>

<dict>

<key>FirstPersonality</key>

<dict>

<key>CFBundleIdentifier</key>

<string>com.apple.kext.ATINDRV</string>

<key>IOClass</key>

<string>ATICLASS</string>

<key>IOMatchCategory</key>

<string>IOFramebuffer</string>

<key>IONameMatch</key>

<string>display</string>

<key>IOProbeScore</key>

<integer>50000</integer>

<key>IOProviderClass</key>

<string>IOPCIDevice</string>

</dict>

</dict>

<key>OSBundleLibraries</key>

<dict>

<key>com.apple.iokit.IOGraphicsFamily</key>

<string>1.3</string>

<key>com.apple.iokit.IONDRVSupport</key>

<string>1.3</string>

<key>com.apple.kernel.iokit</key>

<string>1.0.0b1</string>

</dict>

<key>OSBundleRequired</key>

<string>Safe Boot</string>

</dict>

</plist>

 

 

 

ATIRadeonX1000.kext

 

<dict>

<key>CFBundleDevelopmentRegion</key>

<string>English</string>

<key>CFBundleExecutable</key>

<string>ATIRadeonX1000</string>

<key>CFBundleGetInfoString</key>

<string>ATIRadeonX1000 1.4.26.11 (3493)</string>

<key>CFBundleIdentifier</key>

<string>com.apple.ATIRadeonX1000</string>

<key>CFBundleInfoDictionaryVersion</key>

<string>6.0</string>

<key>CFBundleName</key>

<string>ATI RadeonX1000 Kernel Extension</string>

<key>CFBundlePackageType</key>

<string>KEXT</string>

<key>CFBundleShortVersionString</key>

<string>1.4.26</string>

<key>CFBundleSignature</key>

<string>????</string>

<key>CFBundleVersion</key>

<string>4.2.6</string>

<key>IOKitPersonalities</key>

<dict>

<key>ATIRadeonX1000</key>

<dict>

<key>ATIEnableWideBlitSupport</key>

<true/>

<key>ATIUseTearingWideBlit</key>

<false/>

<key>CFBundleIdentifier</key>

<string>com.apple.ATIRadeonX1000</string>

<key>IOCFPlugInTypes</key>

<dict>

<key>ACCF0000-0000-0000-0000-000a2789904e</key>

<string>ATIRadeonX1000GA.plugin</string>

</dict>

<key>IOClass</key>

<string>ATIRadeonX1000</string>

<key>IODVDBundleName</key>

<string>ATIRadeonX1000VADriver</string>

<key>IOMatchCategory</key>

<string>IOAccelerator</string>

<key>IOPCIMatch</key>

<string>0x71091002 0x71C51002 0x71C01002</string>

<key>IOProviderClass</key>

<string>IOPCIDevice</string>

<key>IOSourceVersion</key>

<string>1.4.26.11</string>

<key>sensor-properties</key>

<array>

<dict>

<key>device_type</key>

<data>

Z3B1LXNlbnNvcg==

</data>

<key>location</key>

<string>GPU</string>

<key>name</key>

<string>gpu-sensor</string>

<key>polling-period</key>

<data>

AAAAAQAAAAA=

</data>

<key>reg</key>

<data>

AAAAAg==

</data>

<key>sample-period</key>

<data>

AAAAAACYmAA=

</data>

<key>sensor-id</key>

<data>

AAAABg==

</data>

<key>version</key>

<data>

AAAAAg==

</data>

<key>zone</key>

<data>

AAAAAg==

</data>

</dict>

</array>

</dict>

</dict>

<key>OSBundleLibraries</key>

<dict>

<key>com.apple.iokit.IOGraphicsFamily</key>

<string>1.0.0b1</string>

<key>com.apple.iokit.IONDRVSupport</key>

<string>1.0.0b1</string>

<key>com.apple.iokit.IOPCIFamily</key>

<string>1.0.0b1</string>

<key>com.apple.kernel.iokit</key>

<string>1.0.0b1</string>

</dict>

</dict>

</plist>

 

 

 

ATIRadeonX1000GA.plugin

 

<dict>

<key>CFBundleDevelopmentRegion</key>

<string>English</string>

<key>CFBundleExecutable</key>

<string>ATIRadeonX1000GA</string>

<key>CFBundleGetInfoString</key>

<string>ATIRadeonX1000GA 1.4.26.11 (3493)</string>

<key>CFBundleIdentifier</key>

<string>com.apple.ATIRadeonX1000GA</string>

<key>CFBundleName</key>

<string>ATI RadeonX1000 Graphics Driver</string>

<key>CFBundleShortVersionString</key>

<string>1.4.26</string>

<key>CFBundleVersion</key>

<string>4.2.6</string>

<key>CFPlugInDynamicRegistration</key>

<string>NO</string>

<key>CFPlugInFactories</key>

<dict>

<key>1002514c-0000-0000-0000-000a27898d3e</key>

<string>ATIRadeonX1000GAFactory</string>

</dict>

<key>CFPlugInTypes</key>

<dict>

<key>ACCF0000-0000-0000-0000-000a2789904e</key>

<array>

<string>1002514c-0000-0000-0000-000a27898d3e</string>

</array>

</dict>

<key>NSExecutable</key>

<string>ATIRadeonX1000GA</string>

<key>Personality</key>

<dict>

<key>IOProviderClass</key>

<string>IONDRVFramebuffer</string>

</dict>

</dict>

</plist>

 

 

Im using the OpenGL.framework from the update (used Pacifist like sugested)

 

Any1 can help?

Its a shame not using DVI in a Display like this... :hysterical:

 

Nuno Maia

Nuno Maia
Nuno Maia
Posted
Posted
I think Boris is deserving of some sort of serious recognition for his effort. I've got a used copy of Oblivion if he wants it.

 

He shure does, I got a almost perfect system due to Him. Just missing DVI-out...

 

Boris, setup a wishlist and get a paypall account ;-)

 

Nuno Maia

RobNyc
RobNyc
Posted
  • Author
Posted

I don't know if its only me, but for the past week I been noticing tearing .

 

Look at these images

 

Different days

post-34649-1149567362_thumb.jpg

post-34649-1149567460_thumb.jpg

gwprod12
gwprod12
Posted
Posted

No one's gotten it to work yet. you'll have to use 9700 for the X600 card. Good luck!

 

 

On a side note... I recently hexedited ATI's ROM update for their mac cards... there's a LOT of ATY style data in there. I dunno if we've already determined that ATINDRV requests some sort of signing with ATY,WORMY from the card, but... It looks like it might.

 

I thought, if anyone can tell me how to dump the rom from my card, and we could get a dump from a Imac/MBPs rom, we could see where the differences are.

 

Obviously it wouldnt do us much good, but it might be fun.

 

If anyone knows a way to dump the x1600 rom in windows, email me, I'd love to know!

Superhai
Superhai
Posted
Posted
On a side note... I recently hexedited ATI's ROM update for their mac cards... there's a LOT of ATY style data in there. I dunno if we've already determined that ATINDRV requests some sort of signing with ATY,WORMY from the card, but... It looks like it might.

 

If anyone knows a way to dump the x1600 rom in windows, email me, I'd love to know!

 

ATY,Wormy is Apple code for the x1600. Apple has lots of strange names for all the ATI cards. I have a hunch that there exists a driver embedded in the Apple ATI BIOS who makes the class ATY,Wormy. Or it is the EFI driver who makes it (there exists no reference to ATY, in the efi as i can see).

 

http://www.techpowerup.com/atitool/ can be used to dump bios from windows, but i am not sure if it works from a macbookpro windows.

 

ATINDRV has a reference to com.apple.ATY_Wormy.

 

And for you with older ATI cards, have you tried using AppleNDRV as your framebuffer?

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...