Jump to content
1381 posts in this topic

Recommended Posts

Display:

 

Type: VGA-Compatible Controller

Bus: PCI

Slot: PCIE X16 SLOT

VRAM (Total): 256 MB

Vendor: ATI (0x1002)

Device ID: 0x71c0

Revision ID: 0x0000

Displays:

SDM-S74:

Resolution: 1280 x 1024

Depth: 32-bit Color

Core Image: Supported

Main Display: Yes

Mirror: Off

Online: Yes

Quartz 2D Extreme: Supported

Quartz Extreme: Supported

Rotation: Supported

Display:

Resolution: 1024 x 768

Depth: 32-bit Color

Core Image: Supported

Mirror: Off

Online: Yes

Quartz 2D Extreme: Supported

Quartz Extreme: Supported

 

I wonder why mine doesn't say PCIE slot.

 

Display:

 

Type: VGA-Compatible Controller

Bus: PCI

VRAM (Total): 256 MB

Vendor: ATI (0x1002)

Device ID: 0x71c2

Revision ID: 0x0000

Displays:

DELL 2405FPW:

Resolution: 1920 x 1200 @ 60 Hz

Depth: 32-bit Color

Core Image: Supported

Main Display: Yes

Mirror: Off

Online: Yes

Quartz Extreme: Supported

Rotation: Supported

The only problem I have is the resolution during boot is not what I have set it as in my User account. It seems to boot the grey apple in 1024, then change resolution to 640 - or 800 for the "Start Mac OS X" screen, then it changes to 1600x1200 as selected in system preferences when it logs in to my account. Not a major flaw, but really anoyning as one would expect - any fix for this so far? I have removed the "Graphics Mode" line in my com.apple.Boot.plist file I was using before now.

 

There are two files who controls the resolution in the MacOS GUI. /Library/Preferences/com.apple.windowserver.plist and /Users/yourusername/Library/Preferences/ByHost/com.apple.windowserver.????????.plist. The first is for the overall system and the second is for your user account.

 

The bootup resoultion is controlled by the bootup vesa drivers framebuffer. Which is switched off and control given to ATINDRV framebuffer when starting the GUI.

So how would I go about changing these files so the same resulution is used the whole way through?

 

I have removed the

 

<key>Graphics Mode</key>

<string>1600x1200x32</string>

 

section from the com.apple.Boot.plist as it isn't needed anymore????

So how would I go about changing these files so the same resulution is used the whole way through?

 

I have removed the

 

<key>Graphics Mode</key>

<string>1600x1200x32</string>

 

section from the com.apple.Boot.plist as it isn't needed anymore????

 

 

I didnt remove those lines, so I can get the same resolution the whole way through.

Aberracus, about the overclocking thing i dont buy as i said, cause my card is a SAPPHIRE PRO, and i get artifacts when some guys having the same card dont! eheh

i'll try using DVI2VGA who knows!

 

EDITED: nice for finding DVI2VGA gives monitor sleep it works :hysterical: so the main source must be DVI too on MBP else why would it work better, im gonna try ATINDRV 10..4.6...anyone using it without artifacts has a direct VGA plug?

yep munky , u have to use 10.4.4 IOPCIFamily;

about DVI2VGA= now monitor sleep works :hysterical: but artifacts still there with 10.4.6 ATINDRV

 

So if anyone having a Sapphire AGP X1600 256Mb can use ATINDRV 10.4.6 and dont have artifacts (only in games!!!!!!!!!!!!) that cannot be explained by overclocking...best is if some1 can try on his config to switch the video card for an XT and see what it gives. Else this is our configuration and OSX bundle :s

So how would I go about changing these files so the same resulution is used the whole way through?

 

I have removed the

 

<key>Graphics Mode</key>

<string>1600x1200x32</string>

 

section from the com.apple.Boot.plist as it isn't needed anymore????

 

You should keep the Graphcs Mode in Boot.plist, then use Pref Setter or similar tool to edit the .plists i mentioned to give you the same resolution. There will always be a blackout when ATINDRV takes over so it wont remove that.

Maybe it is time to someone clean this topic and point the correct steps to make the x1xxx cards work correctly, isn´t it?

maybe it's all written clearly in the beginning of this thread???? maybe this hack is not finished for DVI users??? maybe it's extremely easy with the howto from boris???tzzzz

yes its weel explained in the first page...

 

 

MODIFYING KEXTS -EASY WAY-

my prefered method of editing kexts is, right mouse over the desired kext, show package contents, navigate to info.plist, copy it to your desktop and edit with textedit, save and replace (will ask for password authetication) in the previously opened kext.

 

delete kextcache and the other one ;)

 

then go to disk utilities and repair permisions

 

Cyclonefr, haha the overclocking, you know we both can have the same brand model of video card and one of us can overclock and the other can't , thats overclocking, its not an alwways win situation, revision number qand manufacturing lot are very important; so you can't rule it out so easilly. have you tried direct cooling your video card?

And the ATINDRV 10.4.5 could be working the video card at a slower pace, that doesnt prove anything.

 

MUNKY

I wrote the how to of solving the IOPCIFAMILY issue :D

But till now there is no "compatibility list" and there are new modifications being done in other kexts as I saw in the whole thead.

 

It´s said to be a x1xxx compatible, but only x1600 cards are working. Some x1800 maybe....

yes aberrracus, but normally all the same card of the same brand are manufactured like the others, and i can proove it, cause mine doesnt heat after artifacts eheh

and as i said why the hell would ATINDRV 10.4.4 wont work? eheh when A10.4.6 works for u...And why X1800 which is 2 times more overclocked than X1600 would crash under 10.4.6 ATINDRV that's the point man...

My first idea was overclocking too when i saw this bug, i wanted to bring my card back to the shop but when i saw it worked using 10.4.5 ATINDRV i realised it couldnt be it, but just a conflict between other kexts / fk or MACH_KERNEL

that's my point of view, we will have the answer as soon as someone try the XT in the same configuration....but as i said if it works on some AGP X1600 it should work for all

Ok, we really don't know, anyway. (and x1800 are completly diferent chipsets).

 

We need more testers, and a HCL compatibility list.

 

and we nned to keep on track, we need 100% REAL absolute compatibility.

yeah i totally agree, we need to find out, else we will be f***ed in futher release...

I was looking at disassembler output of ATINDRV (try otools -v -V -t /System/Library/Extensions/ATINDRV.kext/Contents/MacOS/ATINDRV, or something like that, i'm typing from memory), and although I don't quite understand assembler, I can see a number of routines are called something like, InitCard > HWClock > R530SetMClk (again, typing from memory). Maybe someone with skills can take a quick look at it. In other words, it looks to me like maybe there is some kind of clock setting going on.

 

 

yeah i totally agree, we need to find out, else we will be f***ed in futher release...

 

My goal is to get close to 100% functionality now (no crashes, almost all features supported such as sleep etc, compatibility with 3rd party software), and if I can't update my OS beyond 10.4.6 for the next couple of years that's fine - by then it will be time to upgrade again, and I will get a Mac. We will still likely be able to run all major apps on the current release of OS.

 

Now if Apple would only come up with $1200-$1500 minitower they would be very successful with enthusiast market who simply can't afford PowerMac for home use, find MacMini too weak, and iMac too restrictive with it's built in monitor and lack of extra slots.

otools ? wheres it is?

 

It is included as part of Xtools. Download it here. Make sure not to install CHUD tools (in custom installation options), or you will be unable to boot - it replaces the kernel or something like that.

 

Free registration will be required on the webiste to allow download to proceed.

Cardinal, btw, do you rember what we change to get the option to configure 2 screens? iam geting tired of having in my work computer (not my testing platform) a second ficticious or phantom screen wich causes mouse distort when i move the pointer over it.

 

 

do you get what i tried to ask you?

 

 

downloading xtoosl very carefully

Cardinal, btw, do you rember what we change to get the option to configure 2 screens? iam geting tired of having in my work computer (not my testing platform) a second ficticious or phantom screen wich causes mouse distort when i move the pointer over it.

 

I think hanschien posted about that around page 10 of this thread. Don't remember the details.

 

do you get what i tried to ask you?

 

Hmm?

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