[afd_sg]

Hello - the board and Graphics card you have was part of the original Lifehacker guide and a great deal of work was put into that and it was very successful some months ago. Unlike Aargs DSDT Lifehackers is a lot larger and I cannot recall whether there are any speedstep mods. But it works well and should work with the kexts you are using. If you compare the Graphic inputs in the lifehacker option you might find where you existing 9800 GTX is having problems.

[dantoine]

Can please someone post the speedstep-dsdt-code for a E6550 processor?

[guidorosso]

Hi afd_sg,
Thanks. I can certainly try this out, but I never had this problem with my old DSDT. I started seeing the problem after adding speedstep values and the LPC fix to my DSDT, even before switching to Aargh's DSDT.

I'm trying to think if there's anything else I added in the process that could be causing this. I've deleted VoodooPState.kext, CPUi.kext, CPUInjector.kext, and OpenHaltRestart.kext.

Any other ideas?

[Aargh-a-Knot]

@Elmangomez

Here ya go.

Elmango_DSDT.zip

I'm not sure about the c-states... I think you might have more than one c-state on that processor, but I'm not able to figure that out right now. However, I plugged your p-state info into PSS. I started comparing your raw dsdt to this one, but I just can't devote the attention to it tis second. I maybe got half way through, and it looks the same as mine, so I kinda gave up. I think you should be good. You can see that my dsl is much easier to read if you want to look through it.

Give it a go, and let me know...

[elmangomez]

Knotty thank you!!

My temp went from 64 degrees to 48. A nice drop. It is wild how the dsdt got so different. How did you get it so simplified? How would one go about getting Asere's dsdt's simplified like this?

It is crazy how a one month hiatus from the Chameleon world changes everything so much.

A million thanks for your help, I really appreciate it!

Originally Posted by Aargh-a-Knot

@Elmangomez

Here ya go.

Attachment 738

I'm not sure about the c-states... I think you might have more than one c-state on that processor, but I'm not able to figure that out right now. However, I plugged your p-state info into PSS. I started comparing your raw dsdt to this one, but I just can't devote the attention to it tis second. I maybe got half way through, and it looks the same as mine, so I kinda gave up. I think you should be good. You can see that my dsl is much easier to read if you want to look through it.

Give it a go, and let me know...

[Aargh-a-Knot]

Originally Posted by elmangomez

Knotty thank you!!

My temp went from 64 degrees to 48. A nice drop. It is wild how the dsdt got so different. How did you get it so simplified? How would one go about getting Asere's dsdt's simplified like this?

It is crazy how a one month hiatus from the Chameleon world changes everything so much.

A million thanks for your help, I really appreciate it!

My dsdt is based on mm67's, so many thanks go to him. He maybe able to help with c-states, as his CPU is closer to yours.

You may need to add back in a few things based on your setup... let me know if something specific is not working (ie PATA etc)

To makes Asere's DSDTs like this one, you would just start cutting extraneous stuff until you wound up with what you've got.

[mm67]

Originally Posted by Aargh-a-Knot

My dsdt is based on mm67's, so many thanks go to him. He maybe able to help with c-states, as his CPU is closer to yours.

You may need to add back in a few things based on your setup... let me know if something specific is not working (ie PATA etc)

To makes Asere's DSDTs like this one, you would just start cutting extraneous stuff until you wound up with what you've got.

That Q9650 does support deeper C-states so this is what CST should look like:

        Name (CST, Package (0x04) { // C States - returns a list of supported C-states.    8.4.2.1    p314
                0x03,
                Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x000, 0x0,)},0x01,0x01,0x03E8}
                Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x010, 0x1,)},0x02,0x01,0x01F4}
                Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x030, 0x3,)},0x04,0x39,0x0064}
        }) //End CST

[elmangomez]

Originally Posted by mm67

That Q9650 does support deeper C-states so this is what CST should look like:

        Name (CST, Package (0x04) { // C States - returns a list of supported C-states.    8.4.2.1    p314
                0x03,
                Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x000, 0x0,)},0x01,0x01,0x03E8}
                Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x010, 0x1,)},0x02,0x01,0x01F4}
                Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x030, 0x3,)},0x04,0x39,0x0064}
        }) //End CST

Thank you mm67. I am getting a compile error when replacing the CST package...

34: Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x010, 0x1,)},0x02,0x01,0x01F4}
Error 4095 - syntax error, unexpected PARSEOP_PACKAGE, expecting ',' or '}' ^

[elmangomez]

Originally Posted by Aargh-a-Knot

My dsdt is based on mm67's, so many thanks go to him. He maybe able to help with c-states, as his CPU is closer to yours.

You may need to add back in a few things based on your setup... let me know if something specific is not working (ie PATA etc)

Thanks again Knotty, everything is working fine here. I do not have any PATA drives. Sound work, network works... This is nice. Thanks again.

[Aargh-a-Knot]

Originally Posted by elmangomez

Thank you mm67. I am getting a compile error when replacing the CST package...

34: Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x010, 0x1,)},0x02,0x01,0x01F4}
Error 4095 - syntax error, unexpected PARSEOP_PACKAGE, expecting ',' or '}' ^

I'm guessing that that compile error is from copying and pasting from the forum post. You could try retyping all of the special characters (, } ' " etc), or if that doesn't work, the whole thing. You might be able to c&p back and forth through text edit or something, but I'm not sure. What editor are you using? I'm using BBedit 100% now, as that DSDTSE program is buggy as hell.