ATI X1600 options.

I believe you can run the ATI Catalyst Control Panel under Windows/Vista to make those changes.

The Vista version (ATI Catalyst Display Driver (Windows Vista 32-bit) 7.1 (01/29/2007)) is here
http://downloads.cnet.co.uk/0,39100207,39220199s,00.htm
And the Windows XP here
http://www.techspot.com/drivers/index/file/information/3690

This worked with older Macs
http://thomas.perrier.name/graphiccelerator.html

"The Radeon X1600 and X1900 in Intel-based Macs aren't supported yet."

This works very well. No overclock, though.

BB



MBP 2.0, week 13 Mac OS X (10.4.9) No chickenheads!

hmm I can't get the Installer hack to work for me :-\

How'd you get this to work?
I got the utility installed, but it detects "Non ATI Graphics"
Is there anything else you did for yours to work?
Best regards,
-fobis

I backed up and copied the original file, "sysctl", using the terminal command

sudo cp /usr/sbin/sysctl /usr/sbin/sysctl.real

Then opened the copy (the original is now called "sysctl.real") in BB Edit, deleted its contents and replaced them, using BB Edit, with

#!/bin/sh
echo "PowerMac11,2"

and then saved the file. Made this "new" sysctl an executable with

sudo chmod +x /usr/sbin/sysctl

then ran the X1900 installer.

After the install, I got rid of the copy and put the original back, using the terminal

sudo mv /usr/sbin/sysctl.real /usr/sbin/sysctl

BB

P.S. Normally, "sysctl" and its directories are invisible. You may need a utility such as Deeper to make them visible. Also, I left the prompt, "$", out of the terminal commands as this appears in the terminal and will screw things up if you copy here and enter it into the terminal.

P.P.S Made bold the terminal commands for clarity.


MBP 2.0, week 13 Mac OS X (10.4.9) No chickenheads!

Well, I did exactly that, and still get the 'Only on G5' installer message so I dunno what I'm doing wrong here ...

Well, I did exactly that, and still get the 'Only on
G5' installer message so I dunno what I'm doing wrong
here ...

What are you using to edit "sysctl" with?

BB

MBP 2.0, week 13 Mac OS X (10.4.9) No chickenheads!

> What are you using to edit "sysctl" with?

I've used Pico and BBEdit as posted. The new sysctl file is created and permissions are right (and I've done this like 7 times now in different ways LOL) but the installer still rejects. All this and no overclock at the end of it, I'm going to move on to something else now ...

I did all of this and it successfully installed.
However, the utility still doesn't detect my card...

I don't know what to tell you guys. As you can see, it's a pretty straight forward procedure: it worked for me the first time I did it.

Maybe it's a permissions thing, Core2Duo vs. CoreDuo, 128 MB VRAM vs. 256, or alignment of the stars? I'll see what I can find out.

BB



MBP 2.0, week 13 Mac OS X (10.4.9) No chickenheads!

I saw on some Italian forum (IIRC) that someone said it didn't work with their "Rev B" MBP. Maybe that has something to do with it.
This is my "Graphics/Display" output in System Profiler:

ATI Radeon X1600:

Chipset Model: ATY,RadeonX1600
Type: Display
Bus: PCIe
VRAM (Total): 256 MB
Vendor: ATI (0x1002)
Device ID: 0x71c5
Revision ID: 0x0000
ROM Revision: 113-xxxxxx-158
EFI Driver Version: 01.00.158
Displays:
Color LCD:
Display Type: LCD
Resolution: 1440 x 900
Depth: 32-bit Color
Built-In: Yes
Core Image: Supported
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Display:
Status: No display connected

What's yours look like?

MacBook Pro | 2.33GHz Core2 Duo | 2GB DDR2-677 | 120GB HDD Mac OS X (10.4.9)

The main difference I see is the Driver version ...

ATI Radeon X1600:

Chipset Model: ATY,RadeonX1600
Type: Display
Bus: PCIe
VRAM (Total): 256 MB
Vendor: ATI (0x1002)
Device ID: 0x71c5
Revision ID: 0x0000
EFI Driver Version: 01.00.068
Displays:
Color LCD:
Display Type: LCD
Resolution: 1440 x 900
Depth: 32-bit Color
Built-In: Yes
Core Image: Supported
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Display:
Status: No display connected

Did you not get a ROM revision version?
And I wonder why there are different EFI driver versions... you have the latest firmware update, right?