Research on graphics

[glengoyne17]

Just upgraded from 4GB to 8GB and so far no lines, ran FaceTime and sleep several times. How can I test if my machine generates glitches?

 

[leostone]

a few posts up netusername posted his procedure to produce glitches,

me i am running Prime95 + three HIRES Quicktime Movies + http://waterlife.nfb.ca/ + some other FlashMovie playing. Then it's mostly enough to just sit and wait ....

 

[leostone]

Investigation is forthcomming!!!


Everyone!!! I dare you: have you got a line like this in your kernel.log????

AGPM: GPU = GFX0 Initialized, Control ID 16

Well, I didn't until now!!! Does it keep the glitches away????
Definitely NOT !!!

This line shoud appear just shortly after

DSMOS has arrived


How did I manage? Its in the Info.plist of AppleGraphicsPowerManagment.kext
There you'll find a long list of PlatformID's and settings for them.

Now I am using "MacBookPro 8,1" and took special interrest in the Entry for it, who would have thought.

As you will realize, when you look, there are entrys for each possible graphic card, for me there was only one, AND WAS CALLED IGPU!!!

ioreg told me i didn't have an IGPU, but an GFX0, so what did I do?????

Yes!!! just changed the bloody IGPU into GFX0, touched /S*/L*/E* and booted,
AND got this line!!!

No, actually i also added another key:

<key>LogControl</key>
<integer>1</integer>

But I am not sure if this is necessary ....

Hell, if this would be it ...... ?????!!!!!

I FORGOT: please take care to revert to stock AppleIntelSNBGraphicsFB to avoid disturbances, in case you were fiddling around with it

 

[BigDonkey]

In our case stock dsdt comes with GFX0
Patched dsdt.aml has all instances renamed, so we are using IGPU

I'll check my log to see what I get.

EDIT:
Checked my logs, added LogControl

I'm not getting this line
AGPM: GPU = GFX0 Initialized, Control ID 16

Is this in any way significant?

 

[leostone]

In our case stock dsdt comes with GFX0
Patched dsdt.aml has all instances renamed, so we are using IGPU

I'll check my log to see what I get.

EDIT:
Checked my logs, added LogControl

I'm not getting this line
AGPM: GPU = GFX0 Initialized, Control ID 16

Is this in any way significant?

Regarding the glitches, i doubt it, at the moment,
regarding performance, or batterylife maybe ....

 

[mac4mat]

In our case stock dsdt comes with GFX0
Patched dsdt.aml has all instances renamed, so we are using IGPU

I'll check my log to see what I get.

EDIT:
Checked my logs, added LogControl

I'm not getting this line
AGPM: GPU = GFX0 Initialized, Control ID 16

Is this in any way significant?

And with the dsdt patch we see IGPU in IORegistryExplorer, not GFX0.

I think the LogControl key is for logging only, it doesn't change how HP ProBook AGPM behaves. I added the LogControl key and now can get "AGPM: " messages in the log.

AGPM: GPU = IGPU Initialized, Control ID 16
AGPM: GPU = IGPU G-state set to 0 from 3, ControlID = 16

(There is more discussion and some examples of the xml key usage here:
viewtopic.php?t=20367 )

 

[leostone]

out of curiosity, are you guys able to adjust basic RAM frequency and/or RAM voltage in BIOS???


cause i am slowly coming to the conclusion that the artifacts are caused by RAM driven with too low a voltage for the set frequency ....

for example here: i've got 1600 MHZ DDR3 4GB Corsair sticks

while OC'ing CPU running at 4000MHZ i could only get rid of artifacts by running
the RAM at 1066MHZ at the default voltage from bios, 1.47V i think

only by going up to 1.60V for the RAM i was able to run it at 1333MHZ wo artifacts

right now I am running the RAM at 1600MHZ and 1.63V but CPU at the default 3300MHZ
and still be without artifacts

Edit: not even! switching back to 1333MHZ
Edit: never mind, all statements made in this post not true anymore ....

 

[BigDonkey]

@mac4mat
OK I found my log error. My key was setup as string rather than number. Thanks.

@leostone
Nothing in BIOS related for memory. Not a single option to change.

 

[leostone]

@everyone who has still glitches:

Are you by any chance using AppleHDARollback, as I understand the driver from 10.6.2 ???

I just moved investigation towards wether if my onBoardAudio disabled/or not does make
any difference. I realized that the QuicktimePlayer won't even open without working Audio, so I came to have closer look at my audio driver setup. The idea of using the driver from 10.6.2 felt a bit to be prone for causing problems.

... so I just installed Toleda's driver which I understand is an edit of a later version of
AppleHDA.

Just trying it now, and of course I wouldn't mention it, if I had already gotten glitches ....

 

[BigDonkey]

@everyone who has still glitches:

Are you by any chance using AppleHDARollback, as I understand the driver from 10.6.2 ???

I just moved investigation towards wether if my onBoardAudio disabled/or not does make
any difference. I realized that the QuicktimePlayer won't even open without working Audio, so I came to have closer look at my audio driver setup. The idea of using the driver from 10.6.2 felt a bit to be prone for causing problems.

... so I just installed Toleda's driver which I understand is an edit of a later version of
AppleHDA.

Just trying it now, and of course I wouldn't mention it, if I had already gotten glitches ....

This doesn't apply to us. We are using IDT codec which is patched each time new AppleHDA version is released.