Shaj Posted November 28, 2009 Share Posted November 28, 2009 Wow. Thanks guys (especially mastershredder & FormerlyKnownAs). Ok shredder, I had a look at my FACP dump and it gives me the following values: [05Fh 0095 1] _CST Support : 00 [060h 0096 2] C2 Latency : 005A [062h 0098 2] C3 Latency : 0384 I hope that 00 for CST support isn't a bad thing Now I changed this bit in my DSDT: Method (_CST, 0, NotSerialized) { Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, 0x9D, 0x03E8 } }) } to this: Method (_CST, 0, NotSerialized) { Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, 0x5A, 0x0384 } }) } Is that correct? I wasn't sure if I was supposed to use '005A' or just '5A' so I chose the latter. Link to comment Share on other sites More sharing options...
MacUser2525 Posted November 28, 2009 Share Posted November 28, 2009 to this: Method (_CST, 0, NotSerialized) { Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, 0x5A, 0x0384 } }) } Is that correct? I wasn't sure if I was supposed to use '005A' or just '5A' so I chose the latter. Same as mine I went with 005A and don't forget the second part he mentions in CPU1. Method (_CST, 0, NotSerialized) { Return (Package (0x04) { 0x03, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address ,) }, One, Zero, 0x0384 // C3 latency - replace with value in your FACP table. }, Link to comment Share on other sites More sharing options...
FKA Posted November 28, 2009 Author Share Posted November 28, 2009 Same as mine I went with 005A and don't forget the second part he mentions in CPU1. Method (_CST, 0, NotSerialized) { Return (Package (0x04) { 0x03, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address ,) }, One, Zero, 0x0384 // C3 latency - replace with value in your FACP table. }, Hi MacUser2525 That's C1 latency, no? which isn't listed in my FACP? Just 2and 3. D Link to comment Share on other sites More sharing options...
MacUser2525 Posted November 29, 2009 Share Posted November 29, 2009 Hi MacUser2525 That's C1 latency, no? which isn't listed in my FACP? Just 2and 3. D Not sure I went with what mastershreder had posted earlier using my values. I too only have the C2 and C3 in the FACP so who knows perhaps that needs to be changed all I know it appears to work for my test machine, my main install always had the cstate working using the generic code.. Link to comment Share on other sites More sharing options...
FKA Posted November 29, 2009 Author Share Posted November 29, 2009 Not sure I went with what mastershreder had posted earlier using my values. I too only have the C2 and C3 in the FACP so who knows perhaps that needs to be changed all I know it appears to work for my test machine, my main install always had the cstate working using the generic code.. Ive tried leaving C1 as is and with the C2 value from FACP. No temp change with either - then again I've never had c-states working and no native cst table. D. Link to comment Share on other sites More sharing options...
mitch_de Posted November 29, 2009 Share Posted November 29, 2009 I hope that 00 for CST support isn't a bad thing "[05Fh 0095 1] _CST Support : 00" () Hi, i also have that CST support = zeros . My CST FACP GA-EP35-DS3 part is: [05Fh 0095 1] _CST Support : 00 [060h 0096 2] C2 Latency : 0065 [062h 0098 2] C3 Latency : 03E9 What could this _CST Support : 00 mean in practice ? I found an entry [037h 0055 1] P-State Control : 34 - what could that mean ? Link to comment Share on other sites More sharing options...
blackosx Posted November 29, 2009 Share Posted November 29, 2009 I have just realised I have Phase LED on my mobo. I will have to try it out when I get a chance. I had a go with this but running OS X leaves the Phase LED disabled. I see the lights active when I first boot and in the BIOS only. My mobo manual states 'To enable the Phase LED display function, please first enable Dynamic Energy Saver Advanced' which is a Windows app I hope that 00 for CST support isn't a bad thing "[05Fh 0095 1] _CST Support : 00" () Hi, i also have that CST support = zeros . My CST FACP GA-EP35-DS3 part is: [05Fh 0095 1] _CST Support : 00 [060h 0096 2] C2 Latency : 0065 [062h 0098 2] C3 Latency : 03E9 What could this _CST Support : 00 mean in practice ? I found an entry [037h 0055 1] P-State Control : 34 - what could that mean ? My FACP table contains... [05Fh 0095 1] _CST Support : 00 [060h 0096 2] C2 Latency : 005A [062h 0098 2] C3 Latency : 0384 and [037h 0055 1] P-State Control : 34 I don't how to interpret that either. Link to comment Share on other sites More sharing options...
mastershredder Posted November 29, 2009 Share Posted November 29, 2009 Wow. Thanks guys (especially mastershredder & FormerlyKnownAs). Ok shredder, I had a look at my FACP dump and it gives me the following values: [05Fh 0095 1] _CST Support : 00 [060h 0096 2] C2 Latency : 005A [062h 0098 2] C3 Latency : 0384 I hope that 00 for CST support isn't a bad thing Now I changed this bit in my DSDT: Method (_CST, 0, NotSerialized) { Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, 0x9D, 0x03E8 } }) } to this: Method (_CST, 0, NotSerialized) { Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, 0x5A, 0x0384 } }) } Is that correct? I wasn't sure if I was supposed to use '005A' or just '5A' so I chose the latter. hey Shaj yes you have got it correct dont forget that you need to input that value a bit lower in the method as well when it looks like this :- One, Zero, 0x03E8 you would need to change it to this :- One, Zero, 0x0384 Also regarding if u need to enter the first value as 005A or 5A it wont matter as when compiled it will be optimized to 5A anyhow. Dont worry about your CST entrie saying 0 either in FACP mine did. i had the cstates working very early on but had strange behaviour when using the default values in the generic scope the combination of entering my values and removing the IRQ values sorted out the strange behaviour. Hi MacUser2525 That's C1 latency, no? which isn't listed in my FACP? Just 2and 3. D FormerlyKnownAs this is a section from my FACP table and the values say C2 and C3 no mention of C1 so i assume those values correspond to C2 and C3 in the CST method [05Eh 094 1] GPE1 Base Offset : 00 [05Fh 095 1] _CST Support : 00 [060h 096 2] C2 Latency : 0065 [062h 098 2] C3 Latency : 03E9 [064h 100 2] CPU Cache Size : 0000 [066h 102 2] Cache Flush Stride : 0000 Am i right in reading that you do not have your Cstates working FormelyKnownAs ? thats a shame but i think you do not need to worry about not having a CST method in any of your tables as i do not either. it is possible that you mite get these cstates working and not have any reduction in temps i saw a reduction of about 4 C from my dsdt with cstates compared with hte one with just pstates working however i am using water cooling it is possible that your HSF just cant reduce the temps for your processor any further if you have the error messages removed from the kernel.log and are not seeing a reduction in temps that doesnt mean that they are not working. Link to comment Share on other sites More sharing options...
Smith@@™ Posted November 29, 2009 Share Posted November 29, 2009 GPE0 Block Length : 10 [05Dh 0093 1] GPE1 Block Length : 00 [05Eh 0094 1] GPE1 Base Offset : 00 [05Fh 0095 1] _CST Support : E3 [060h 0096 2] C2 Latency : 0065 [062h 0098 2] C3 Latency : 03E9 [064h 0100 2] CPU Cache Size : 0400 This is my values, what i change my code? I am using another code (down) because the code in "first page" some upon give me a kernel panic. This is the code that working well: Scope (_PR) { Processor (CPU1, 0x01, 0x00000810, 0x06) { Name (_PSS, Package (0x04) { Package (0x06) { 0x09C2, 0x000157C0, 0x10, 0x10, 0x4720, Zero }, Package (0x06) { 0x091B, 0xE8FB, 0x10, 0x10, 0x071E, One }, Package (0x06) { 0x0875, 0xC7B4, 0x10, 0x10, 0x461C, 0x02 }, Package (0x06) { 0x07CE, 0xA398, 0x10, 0x10, 0x0616, 0x03 } }) Name (_PSD, Package (0x05) { 0x05, Zero, Zero, 0xFC, 0x04 }) Name (_CST, Package (0x04) { 0x03, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address ,) }, One, One, 0x03E8 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000814, // Address ,) }, 0x03, One, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000815, // Address ,) }, 0x03, 0x55, 0xFA } }) } Processor (CPU2, 0x02, 0x00000810, 0x06) { Alias (^CPU1._PSS, _PSS) Alias (^CPU1._PSD, _PSD) Alias (^CPU1._CST, _CST) } Processor (CPU3, 0x03, 0x00000810, 0x06) { Alias (^CPU1._PSS, _PSS) Alias (^CPU1._PSD, _PSD) Alias (^CPU1._CST, _CST) } Processor (CPU4, 0x04, 0x00000810, 0x06) { Alias (^CPU1._PSS, _PSS) Alias (^CPU1._PSD, _PSD) Alias (^CPU1._CST, _CST) } } what changes i must do for the values in my FACP TABLE ? thanks and sorry for my english Link to comment Share on other sites More sharing options...
mastershredder Posted November 29, 2009 Share Posted November 29, 2009 I had a go with this but running OS X leaves the Phase LED disabled. I see the lights active when I first boot and in the BIOS only. My mobo manual states 'To enable the Phase LED display function, please first enable Dynamic Energy Saver Advanced' which is a Windows app My FACP table contains... [05Fh 0095 1] _CST Support : 00 [060h 0096 2] C2 Latency : 005A [062h 0098 2] C3 Latency : 0384 and [037h 0055 1] P-State Control : 34 I don't how to interpret that either. BlackOSX what you need to do to get the phase leds working is to install Dynamic Energy Saver Advanced from gigabyte and install it in windows then it should work always even when in mac. i beleive theres a chip on the board thats reponsible for them working however this chip must remain dormant until this application enables it however i advise against installing it as when i had i started to get major BSODS in windows and no explaination as to what caused them suffice to say uninstalling the app corrected this. however again if you do go ahead and install it and start to recieve BSODS and want to uninstall it make sure you run the app first then disable the energy saver as once the app enables the chip it doesnt need the app to be initialized to make it work this explains why the lights work in OSX the wierd thing is i never had any instability in OSX from the lights being enabled it was jsut crazy harsh BSODS in windows which were unacceptable. SO to sum up if u install it and then you change your mind make sure you disable the energy saver with the app before uninstalling it or you will continue to recieve BSODS in windows it is obviously a poorly written application as i have read if you leave it on for an entire year it will only save you about $3 a year on your electric GPE0 Block Length : 10[05Dh 0093 1] GPE1 Block Length : 00 [05Eh 0094 1] GPE1 Base Offset : 00 [05Fh 0095 1] _CST Support : E3 [060h 0096 2] C2 Latency : 0065 [062h 0098 2] C3 Latency : 03E9 [064h 0100 2] CPU Cache Size : 0400 This is my values, what i change my code? I am using another code (down) because the code in "first page" some upon give me a kernel panic. This is the code that working well: Scope (_PR) { Processor (CPU1, 0x01, 0x00000810, 0x06) { Name (_PSS, Package (0x04) { Package (0x06) { 0x09C2, 0x000157C0, 0x10, 0x10, 0x4720, Zero }, Package (0x06) { 0x091B, 0xE8FB, 0x10, 0x10, 0x071E, One }, Package (0x06) { 0x0875, 0xC7B4, 0x10, 0x10, 0x461C, 0x02 }, Package (0x06) { 0x07CE, 0xA398, 0x10, 0x10, 0x0616, 0x03 } }) Name (_PSD, Package (0x05) { 0x05, Zero, Zero, 0xFC, 0x04 }) Name (_CST, Package (0x04) { 0x03, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address ,) }, One, One, 0x03E8 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000814, // Address ,) }, 0x03, One, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000815, // Address ,) }, 0x03, 0x55, 0xFA } }) } Processor (CPU2, 0x02, 0x00000810, 0x06) { Alias (^CPU1._PSS, _PSS) Alias (^CPU1._PSD, _PSD) Alias (^CPU1._CST, _CST) } Processor (CPU3, 0x03, 0x00000810, 0x06) { Alias (^CPU1._PSS, _PSS) Alias (^CPU1._PSD, _PSD) Alias (^CPU1._CST, _CST) } Processor (CPU4, 0x04, 0x00000810, 0x06) { Alias (^CPU1._PSS, _PSS) Alias (^CPU1._PSD, _PSD) Alias (^CPU1._CST, _CST) } } what changes i must do for the values in my FACP TABLE ? thanks and sorry for my english Can you send me your DSDT.dsl and your FACP table as it curently is and i will have a look also post values for your pstates if known and i will help to intergrate them refer to the initial post by FormerlyKnownAs to find out the values for your pstates. MacUser2525 i assume your main machine which needed no altering to the CST method used the same values in ur FACP table and this is why you have had no complication making this work. I am glad to hear that your cstates work on the second machine by replacing the values present in the FACP table. I am no expert in ACPI i have never even looked at the specification on it as i dont have the time or energy from reading this thread i can safely say Chief seems to know what he is doing regarding ACPI and FormelyKnownAs for writing the guide i tried SSDT tables about 6 months ago from the thread that was using the modified chameleon to use up to 30 ssdts and just plain gave up because the people in that thread at the time were way over my head i beleive the confusion in this thread is a combination of different hardware makers especially laptops the way different comapnys write these tables is causes a lot of confusion fortunatley the gigabyte tables are quite easy to understand compared with some manufacturers . for example i extracted all the tables from my brother laptop made by clevo and the way those tables were written was completely different. Link to comment Share on other sites More sharing options...
Smith@@™ Posted November 29, 2009 Share Posted November 29, 2009 Thank you dsdt_facp.zip Link to comment Share on other sites More sharing options...
mastershredder Posted November 29, 2009 Share Posted November 29, 2009 Thank you hi do you have your pstates currently working? Right try this one also is a copy of my current DSDT.dsl for reference in case this one still doesnt work for you. dsdt.aml.zip my_working_dsdt.dsl.zip Link to comment Share on other sites More sharing options...
MacUser2525 Posted November 29, 2009 Share Posted November 29, 2009 MacUser2525 i assume your main machine which needed no altering to the CST method used the same values in ur FACP table and this is why you have had no complication making this work. I am glad to hear that your cstates work on the second machine by replacing the values present in the FACP table. Could be I was thinking it had to do with it being a quad core processor being close enough to a real MacPro 3,1 processor so that makes sense, thanks for the tip that helped on the second machine. I am no expert in ACPI i have never even looked at the specification on it as i dont have the time or energy from reading this thread i can safely say Chief seems to know what he is doing regarding ACPI and FormelyKnownAs for writing the guide i tried SSDT tables about 6 months ago from the thread that was using the modified chameleon to use up to 30 ssdts and just plain gave up because the people in that thread at the time were way over my head i beleive the confusion in this thread is a combination of different hardware makers especially laptops the way different comapnys write these tables is causes a lot of confusion fortunatley the gigabyte tables are quite easy to understand compared with some manufacturers . for example i extracted all the tables from my brother laptop made by clevo and the way those tables were written was completely different. I'm no expert on this as well I have been following the "DSDT fixes for Gigabyte boards" thread in particular the suggested fixes by MC have been working well so far. And yeah it can damn confusing at times trying to figure out which makes sense for your make/model of board to say the least... Link to comment Share on other sites More sharing options...
Shaj Posted November 29, 2009 Share Posted November 29, 2009 My FACP table contains...[05Fh 0095 1] _CST Support : 00 [060h 0096 2] C2 Latency : 005A [062h 0098 2] C3 Latency : 0384 and [037h 0055 1] P-State Control : 34 Hey, we have the same values!!!! hey Shaj yes you have got it correct dont forget that you need to input that value a bit lower in the method as well when it looks like this :- One, Zero, 0x03E8 you would need to change it to this :- One, Zero, 0x0384 Also regarding if u need to enter the first value as 005A or 5A it wont matter as when compiled it will be optimized to 5A anyhow. Dont worry about your CST entrie saying 0 either in FACP mine did. i had the cstates working very early on but had strange behaviour when using the default values in the generic scope the combination of entering my values and removing the IRQ values sorted out the strange behaviour. Thanks Shredder. After making the changes you recommended, I saw no changes in temp. But I'll stick with your method until someone is able to prove it wrong You say you had cstates working early on. How were you certain that they were working? what you need to do to get the phase leds working is to install Dynamic Energy Saver Advanced from gigabyte and install it in windows then it should work always even when in mac. Wow. I had no idea that was the case. Just assembled a replica system for my brother and noticed the Phase LEDs weren't lit up (was too lazy to open up my system ). Thought this was a sure sign that I had no C-states. Will install the windows app and give it a try. Thanks again!!!!! A question however: Do/Did your phase LEDs work the way they should? Could you give me an example so I know what I'm looking for? Link to comment Share on other sites More sharing options...
MacUser2525 Posted November 29, 2009 Share Posted November 29, 2009 You say you had cstates working early on. How were you certain that they were working? Easy way is with Voodoo Monitor looking at the voltage changes, if you see it drop below the lowest pstate you have then it has entered a cstate. On my quad core I can see it do it on the individual pairs of cores on dual core both should drop below the lowest pstate. Link to comment Share on other sites More sharing options...
mastershredder Posted November 29, 2009 Share Posted November 29, 2009 Hey, we have the same values!!!! Thanks Shredder. After making the changes you recommended, I saw no changes in temp. But I'll stick with your method until someone is able to prove it wrong You say you had cstates working early on. How were you certain that they were working? Wow. I had no idea that was the case. Just assembled a replica system for my brother and noticed the Phase LEDs weren't lit up (was too lazy to open up my system ). Thought this was a sure sign that I had no C-states. Will install the windows app and give it a try. Thanks again!!!!! A question however: Do/Did your phase LEDs work the way they should? Could you give me an example so I know what I'm looking for? i knew i had Cstates working early on becasue of the massively reduced temps with only pstates working i had temps around 35C with out pstates temps 40C and with pstates and cstates temps 28-30C although at the beginning cstates were causing strange issues like i said in the operating system which then lead to me investigating the values in the FACP table and adjusting what was in the CST method Also as pointed out by macuser2525 the voltage was falling to about 1.1 volts in voodoo monitor which is well below what is stated in my pstates the lowest is around 1.2. regarding the Phase leds they are pretty pointless but there are several different colour leds and they light up depending on CPU load but like i said i was getting harsh BSODS in windows because of it so i would recommend against using the Dynamic energy saver application. Link to comment Share on other sites More sharing options...
Smith@@™ Posted November 29, 2009 Share Posted November 29, 2009 hi do you have your pstates currently working? Right try this one also is a copy of my current DSDT.dsl for reference in case this one still doesnt work for you. Thank you so much but i have the same problem with this code, kernel panic: "Should have 2 threads, but only found 3 for die 1" Boh Anyway with this other code instead i don't have the kp and the ss works well, but mastershredder where insert exactly the values of my FACP table in this other code that for my it works? (sorry for my english) Scope (_PR) { Processor (CPU1, 0x01, 0x00000810, 0x06) { Name (_PSS, Package (0x04) { Package (0x06) { 0x09C2, 0x000157C0, 0x10, 0x10, 0x4720, Zero }, Package (0x06) { 0x091B, 0xE8FB, 0x10, 0x10, 0x071E, One }, Package (0x06) { 0x0875, 0xC7B4, 0x10, 0x10, 0x461C, 0x02 }, Package (0x06) { 0x07CE, 0xA398, 0x10, 0x10, 0x0616, 0x03 } }) Name (_PSD, Package (0x05) { 0x05, Zero, Zero, 0xFC, 0x04 }) Name (_CST, Package (0x04) { 0x03, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address ,) }, One, One, 0x03E9 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000814, // Address ,) }, 0x02, 0x65, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (SystemIO, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000815, // Address ,) }, 0x03, 0x03E9, 0xFA } }) } Processor (CPU2, 0x02, 0x00000810, 0x06) { Alias (^CPU1._PSS, _PSS) Alias (^CPU1._PSD, _PSD) Alias (^CPU1._CST, _CST) } Processor (CPU3, 0x03, 0x00000810, 0x06) { Alias (^CPU1._PSS, _PSS) Alias (^CPU1._PSD, _PSD) Alias (^CPU1._CST, _CST) } Processor (CPU4, 0x04, 0x00000810, 0x06) { Alias (^CPU1._PSS, _PSS) Alias (^CPU1._PSD, _PSD) Alias (^CPU1._CST, _CST) } } Master, last question, but why the first code on my mobo causes that particular kernel panic ? thanks for your great understanding and willingness Link to comment Share on other sites More sharing options...
mastershredder Posted November 29, 2009 Share Posted November 29, 2009 @ Smith your code was written quite differently to mine but basically you need to stick the values in here :- Method (_CST, 0, NotSerialized) { Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, 0x65, //Your values were the same as mine so leave as what is here 0x03E9 // and here } }) } also for mine i had a Cst method for CPU1 as well which was actually longer than the one for cpu0 the edit i made looks like this :- Method (_CST, 0, NotSerialized) { Return (Package (0x04) { 0x03, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address ,) }, One, Zero, 0x03E9 // only change this value but yours was the same as mine so leave as 03E9 }, hope that gets yours working also dont forget you might need to remove the IRQ entries for the PIC and TMR devices as well Link to comment Share on other sites More sharing options...
Shaj Posted November 29, 2009 Share Posted November 29, 2009 Easy way is with Voodoo Monitor looking at the voltage changes, if you see it drop below the lowest pstate you have then it has entered a cstate. On my quad core I can see it do it on the individual pairs of cores on dual core both should drop below the lowest pstate. i knew i had Cstates working early on becasue of the massively reduced temps with only pstates working i had temps around 35C with out pstates temps 40C and with pstates and cstates temps 28-30C although at the beginning cstates were causing strange issues like i said in the operating system which then lead to me investigating the values in the FACP table and adjusting what was in the CST method Also as pointed out by macuser2525 the voltage was falling to about 1.1 volts in voodoo monitor which is well below what is stated in my pstates the lowest is around 1.2. regarding the Phase leds they are pretty pointless but there are several different colour leds and they light up depending on CPU load but like i said i was getting harsh BSODS in windows because of it so i would recommend against using the Dynamic energy saver application. Thanks Guys. I just ran Voodoo Monitor to have a look and I think my c-states do work. A little concerned though. Do the values under 'Control' represent the FID/VID values?? Because they are different from the ones I got using PStateChanger. Which one is right? And is there an alternate method to calculate the p-state values for my E8400? Link to comment Share on other sites More sharing options...
Smith@@™ Posted November 29, 2009 Share Posted November 29, 2009 Thanks Link to comment Share on other sites More sharing options...
mastershredder Posted November 29, 2009 Share Posted November 29, 2009 Thanks Did you get it working Smith? Link to comment Share on other sites More sharing options...
Smith@@™ Posted November 29, 2009 Share Posted November 29, 2009 The second code master, the first causes the kp and I don't know why, but there isn't a problem, the important is that one of two working Ciao! Link to comment Share on other sites More sharing options...
msm5 Posted November 30, 2009 Share Posted November 30, 2009 After much reading on this thread and the Gigabyte DSDT thread I wanted to share some success. I truly only know the basics of all this and have learned so much here. Since it was mainly a p-state and c-state victory, I thought I'd post here. First, all of the improvements in this DSDT are due to the advice of many through posts and PM's. I borrowed many of the suggestions from Blackosx's posted DSDT's, so you'll see his annotations throughout the attached file since he has made a wonderful compilation of the recommendations given in both threads. My setup: GA-EP45-UD3P (rev 1.6), Q6600, nvidia 7800GT, netkas 10.5 (no ethernet or video in DSDT). P-states and C-states both work as seen in IOreg, which in addition to temps I understand is the only way to know these have been loaded. Additionally VoodooMonitor shows adjustment to the frequency and voltage. I used p-state calculator for the VID/FID numbers. Sleep works, finally. I found that the key to getting all this to work was: 1. The correct C2 and C3 according to the FACP table 2. The Device (LPCB) being correctly formatted for my motherboard 3. Ticking the "start automatically after power failure" box in system preferences. I've attached my latest DSDT files as well as an IOreg picture. Thanks for the help and hopefully this DSDT will assist someone. I'm also open to suggestions to improving this one. dsdt_EP45_UD3P_Q6600.dsl.zip Link to comment Share on other sites More sharing options...
mitch_de Posted November 30, 2009 Share Posted November 30, 2009 Have you done the same also to your EP-35 Mainboard ? Can you share it if dsdt EP35 is on same "level" as EP45 ? Link to comment Share on other sites More sharing options...
blackosx Posted November 30, 2009 Share Posted November 30, 2009 BlackOSX what you need to do to get the phase leds working is to install Dynamic Energy Saver Advanced from gigabyte and install it in windows then it should work always even when in mac. i beleive theres a chip on the board thats reponsible for them working however this chip must remain dormant until this application enables it however i advise against installing it as when i had i started to get major BSODS in windows and no explaination as to what caused them suffice to say uninstalling the app corrected this. however again if you do go ahead and install it and start to recieve BSODS and want to uninstall it make sure you run the app first then disable the energy saver as once the app enables the chip it doesnt need the app to be initialized to make it work this explains why the lights work in OSX the wierd thing is i never had any instability in OSX from the lights being enabled it was jsut crazy harsh BSODS in windows which were unacceptable. SO to sum up if u install it and then you change your mind make sure you disable the energy saver with the app before uninstalling it or you will continue to recieve BSODS in windows it is obviously a poorly written application as i have read if you leave it on for an entire year it will only save you about $3 a year on your electric Thanks for the advice. I only want to enable the Phase LED's out of curiosity so the next time I install Windows on my hack I will run Dynamic Energy Saver Advanced. And thanks for the tips with regard to the BSOD's. Link to comment Share on other sites More sharing options...
Recommended Posts