Jump to content

borisbadenov ATI X1000-series Solution

RobNyc

By RobNyc,
in ATi

 Share
1,381 posts in this topic

Recommended Posts

quietglow
quietglow
Posted
Posted

Can someone please confirm that they are able to calibrate a monitor via the boris method and an xt1600?

 

System Preferences>Displays>Color>Calibrate

 

When you move the sliders around there should be noticable change in the way your display looks.

Link to comment
Share on other sites
cyclonefr
cyclonefr
Posted
Posted
Can someone please confirm that they are able to calibrate a monitor via the boris method and an xt1600?

 

System Preferences>Displays>Color>Calibrate

 

When you move the sliders around there should be noticable change in the way your display looks.

 

Yes you can.

Link to comment
Share on other sites
cyclonefr
cyclonefr
Posted
Posted

X1600 mobility give grey screen so it's worst...so i dont buy ur theory :) the thing is we faint EFI (removing AY, WORMY) so i guess that's the main problem...

the fact is X1600 mobility (pc version) only work on ext monitor must be the fact we call the VGA output and not the other plug (=lcd laptop screen)

 

btw if someone has a X1600 mobility replace ur VENDOR id ie 71C2 by 71E2 and let me know

Link to comment
Share on other sites
macosxpanther
macosxpanther
Posted
Posted

hello

 

this is my info.plist of atindrv.kext

 

how I modify it?

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">'>http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<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>ATY,Wormy</string>

<key>IOProbeScore</key>

<integer>50000</integer>

<key>IOProviderClass</key>

<string>IONDRVDevice</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>

 

 

and this is my info.plist of atiradeonx1000.kext

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<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>

 

this is the info.plist of my ATIRadeonX1000GA.plugin

 

I must only modify these 3 rows or I must some still modify? ps then as I make to load them? what I must write exactly in finishes them?

Link to comment
Share on other sites
Wig72
Wig72
Posted
Posted
X1600 mobility give grey screen so it's worst...so i dont buy ur theory :) the thing is we faint EFI (removing AY, WORMY) so i guess that's the main problem...

the fact is X1600 mobility (pc version) only work on ext monitor must be the fact we call the VGA output and not the other plug (=lcd laptop screen)

 

btw if someone has a X1600 mobility replace ur VENDOR id ie 71C2 by 71E2 and let me know

 

Hi,

 

I've tried to change VENDOR ID to 71E2 using a desktop PCIe x1600pro.

ID changed in ATIRadeon1000.kext and ATIRadeonX1000GA.plugin.

 

Result: Kernel Panic

 

Still no DVI Output

Link to comment
Share on other sites
homer007
homer007
Posted
Posted
ok, my bad...anyway no report from other X1X00 users?

yeh i have x1400 mobility doesnt work on that gives a kernal panic!!! i did report it earlier but no one seems to care about other x1000 problems!!!

Link to comment
Share on other sites
aberracus
aberracus
Posted
Posted
good,so it means ur using the 10.4.5 ATI drivers + opengl...

did u install the GMA900 update during the installation?

 

 

Cyclonefr... where do you get the idea? im running JAS 10.4.6 disk, havent installed gm900 from the customize section when i installed it, thats any difference?

 

 

Anyway.. I am running my LCD screen in my DVI-D conector, using DVI cables.. so its working wonderfull.

 

 

anyone trie3d the second monitor?

Link to comment
Share on other sites
amalgam
amalgam
Posted
Posted
sherriffbounce: i updated boris' post for clarity, but thanks for the correction ;)

 

munky, would either your or boris be so kind as to edit his first "howto" post to reflect which cards/series of cards are reported working?

 

Just like with with koverg's discovery, it seems there may be specific successes & whehter they are agp/pci-e makes a difference too.

Link to comment
Share on other sites
aberracus
aberracus
Posted
Posted

Ok my plists:

 

 

CONSIDERATIONS

Mine is a ASUS XT1600XT Silent

 

Type: VGA-Compatible Controller

Bus: PCI

Slot: PCIE X16 SLOT

VRAM (Total): 256 MB

Vendor: ATI (0x1002)

Device ID: 0x71c0

Revision ID: 0x0000

 

ATINDRV.KEXT info.plist

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">'>http://www.apple.com/DTDs/PropertyList-1.0.dtd">'>http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<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>IONDRVFramebuffer</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>

 

 

ATI RADEON X1000.KEXT info.plist

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<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>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>

 

ATI RADEON X1000 PLUGIN KEXT info.plist

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<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>100271c0-0000-0000-0000-000a27898d3e</key>

<string>ATIRadeonX1000GAFactory</string>

</dict>

<key>CFPlugInTypes</key>

<dict>

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

<array>

<string>100271c0-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>

 

 

Hey PPL, is ther a way to tell OSX i have a SONY TFT screen?

 

 

cheers

 

Aberracus

Link to comment
Share on other sites
amalgam
amalgam
Posted
Posted
Question for you then. When loading, it sems that, if the card has the correct crack applied to it, the delay in boot time is it (or the OS) looking to boot the card in EFI? Is there a way to input the vaules into the card (via plist, etc) so that it will not have to do this search? Or maybe an EFI buffer perhaps? Or is there a way to tie it into Darwin boot loader? I have XP and Linux also on my box, I do not want anything too compicated to boot, etc.

 

There is nothing "special" about the ATi chips used in the Intel Macs. The EFI firmware process is so straight forward: It loads everything into straight, 32bit memory. That would include the ati.efi firmware, which is part of the motherboards firmware, NOT the video card's.

 

I say there is nothing "special" and that must be true, or the cards would not respond to the other hacks & tweaks this forum's members have come up with.

 

You gave an important clue yourself, when you discovered the boot delay time that occured once the higher level OS driver recognized a valid video card, and then appropriately began searching for the code the ati.efi would have had placed in conventional memory.

 

I guess the next thing is to pull out the BIOS from either the Firmware Restore CD, or the Firmware Update files, and carve off just the ati.efi part. Getting it loaded into conventional memory as part of a pre-boot ought not be beyond reason, & doesn't seem like a "too complicated" fix. I agree with you & wouldn't want to have a "close your eyes & pull the trigger" system, every time I went for a reboot!

Link to comment
Share on other sites
borisbadenov
borisbadenov
Posted
Posted

Ok, yes, that all makes sense to me. Now, if I had access to an Intell Mac, it there a way to grab the info it collects from the video card and "patch it" into my system so that it is on file, so that it does not have to go searching for the info every time? And hence, maybe giving us all 100% usability? Or is the best way, as you said, from a Firmware Restore CD or Firmware Update? I have downloaded the firmware Restoration files and looking at them tonight.

 

There is nothing "special" about the ATi chips used in the Intel Macs. The EFI firmware process is so straight forward: It loads everything into straight, 32bit memory. That would include the ati.efi firmware, which is part of the motherboards firmware, NOT the video card's.

 

I say there is nothing "special" and that must be true, or the cards would not respond to the other hacks & tweaks this forum's members have come up with.

 

You gave an important clue yourself, when you discovered the boot delay time that occured once the higher level OS driver recognized a valid video card, and then appropriately began searching for the code the ati.efi would have had placed in conventional memory.

 

I guess the next thing is to pull out the BIOS from either the Firmware Restore CD, or the Firmware Update files, and carve off just the ati.efi part. Getting it loaded into conventional memory as part of a pre-boot ought not be beyond reason, & doesn't seem like a "too complicated" fix. I agree with you & wouldn't want to have a "close your eyes & pull the trigger" system, every time I went for a reboot!

Link to comment
Share on other sites
amalgam
amalgam
Posted
Posted
Ok, yes, that all makes sense to me. Now, if I had access to an Intell Mac, it there a way to grab the info it collects from the video card and "patch it" into my system so that it is on file, so that it does not have to go searching for the info every time? And hence, maybe giving us all 100% usability? Or is the best way, as you said, from a Firmware Restore CD or Firmware Update? I have downloaded the firmware Restoration files and looking at them tonight.

 

Jeez, you'd want a "process watcher", that would be active & writing what it sees to a file - a debugger. Better is a serial console, hmmm, not likely on Itel Macs.

 

Easiest way to get the firmwares: www.macupdate.com

 

In the search box type: firmware

 

Should pull up all 3 individual firmware updates, and "FirmwareRestorationCD.dmg". That will contain all 3 restore firmwares; MacMini, MacBook Pro and iMac.

 

MM11_004B_00B.fd

MBP11_0044_02B.fd

IM41_0039_00B.fd

 

Notice they are all exactly 2048KB (or actually 2,0977,152 bytes). That is the same size as the spiFlash on the IntelMac motherboard. The spiFlash is a serial EEPROM. The notion is, that as the cpu wakes up & queries the first byte address, the spiFlash "serially" spits the info it contains in 32bit conventional memory, and I believe it all gets stuck above the 1st meg on the IntelMac, same wayas done with IA64 & x86 pure Intel EFI platforms. The older conventional BIOS is usually stored in a "parallel" EEPROM. By loading the EEPROM into conventional memory, it's supposed to deliver faster boots.

 

I'm rambling. OK, so the notion is, you got a geniune IntelMac firmware to play with. The next thing would be to load it up in a hexer & look for those delimiters that separate the individual modules. And from there, cleanly pull just the ati.efi (or whatever the EFI Byte Code needs to be called) portion out.

Link to comment
Share on other sites
borez
borez
Posted
Posted
Cyclonefr... where do you get the idea? im running JAS 10.4.6 disk, havent installed gm900 from the customize section when i installed it, thats any difference?

Anyway.. I am running my LCD screen in my DVI-D conector, using DVI cables.. so its working wonderfull.

anyone trie3d the second monitor?

 

Woah. Glad to hear that you managed to get it working with DVI. Am inspired to try mine out (mine is a Xpertvision 1600 Pro, 71C2). Will report back. :thumbsup_anim:

Link to comment
Share on other sites
asapreta
asapreta
Posted
Posted

I´m surprised how many x1600 users are in here!

But no x1300 owners or, x1400, x1800, x1900 giving it a try?

 

And one thought, my x800 card was flashed to work as a x850 card (R480 chipset) but when I´ve tried to use in OSX I got some kernel panic screens. After messing arround the ID´s now I have it working as a x850 perfectly on XP and OSX. Maybe possible to the users of x1600 cards changing their card IDs to make them more compatible with this fix?

Link to comment
Share on other sites
hanschien
hanschien
Posted
Posted

I'm about to give up!!! can't get the damn DVI-I to work in digital mode!!!!

 

BTW, pci1002,71e2 instead of display can be used instead of display

 

<key>IONameMatch</key>

<array>

<string>pci1002,71c2</string>

<string>pci1002,71e2</string>

</array>

 

it's getting late, already had 5 beers, goodnight

Link to comment
Share on other sites
borisbadenov
borisbadenov
Posted
Posted

Very interesting. Does it make any difference?

 

 

 

I'm about to give up!!! can't get the damn DVI-I to work in digital mode!!!!

 

BTW, pci1002,71e2 instead of display can be used instead of display

 

<key>IONameMatch</key>

<array>

<string>pci1002,71c2</string>

<string>pci1002,71e2</string>

</array>

 

it's getting late, already had 5 beers, goodnight

Link to comment
Share on other sites
lorant
lorant
Posted
Posted
BTW

 

Tried a second (a CRT) monior, it worked until sistem (OSX) started, once it stated there was no video out in the VGA standard conector.

 

Any ideas?

 

I looked at your card, the DVI is in top and VGA below. Usually it is the opposite. Thus on this card the DVI is perhaps regarded as first output and VGA like second. So the DVI works.

I think that a card with the same output configuration, or with two DVI output will work.

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...