I always get error tryinf dl of latest b4.I used official beta dl main link.http://superhai.com/beta-darwin.htmlDownloading file?Please do not link directly to my binary files. Use the corresponding download page as link.

Ok.. i got back to Snow test system, this time with minimal patches; just booter, kernel, fakesmc and dsdt. On dsdt the only permanent patch is the one for cmos reset; when using AppleHDA i add the generic injection; occasionally i also use graphics injection there; none of the usual hpet/rtc patches are applied.The driver behaves the same way so, i think we can exclude the patches from the problem too!?

I gave a look at the bios setup; i found a while ago i can get into setup also with F11 (not mentioned by HP any were) instead of F1 and that brings up some more options, mostly on the Power pane. These are the options and default values: - After AC Power Failure: Auto - WOL (wake on LAN) in S4: Enabled - APIC: Enabled (not changeable) - S3: Enabled - XD (Execute Disable): Enabled - C1E (Enhanced Halt State): Enabled - EIST: Enabled - Intel(r) 64: Enabled (not changeable) - Quick Resume Technology: Enabled

I have just minimal knowledge about this stuff and i understand most of it has nothing to do with EIST!? but, i do need to do some reading.. that's what i'm doing atm, checking your stuff about EIST and reading about the other stuff all over the net. I don't use sleep/hibernation (in fact it's not working properly on OS X) or any other related stuff like Quick Resume; the machine is either On or Off, no "gray areas" here; that's why EIST is important to me and why i'd like to have it working properly. 90% of the time, i don't need the CPU running at "full throttle" so the power consumption reduction and consequent lower temperatures are welcome!For now i disabled Quick Resume and C1E. Will post results later but, FID still seems screwed...

Two questions (for now): - are you sure this is caused by something on the system/machine? - are those P-States i got from Leo with vpower the correct ones? (post #7)

Another thing... the only reason why i started using VoodooPowerMini instead of VoodooPower was because, i don't really need the extra functionality present on VoodooPower "all the time" and i still could easily check CPU freq. Now, if future PowerMini will "not update the visible frequency anymore", i'm gonna start "hating" it

Two questions (for now): - are you sure this is caused by something on the system/machine? - are those P-States i got from Leo with vpower the correct ones? (post #7)

Another thing... the only reason why i started using VoodooPowerMini instead of VoodooPower was because, i don't really need the extra functionality present on VoodooPower "all the time" and i still could easily check CPU freq. Now, if future PowerMini will "not update the visible frequency anymore", i'm gonna start "hating" it

I cannot be sure what is the cause, but I can't see why there should be something else. It could also be that there is no BIOS option for some low-level power management. I wouldn't disable C1E unless it breaks something.

And the P-States are not so very interesting, the fid value is correct, but the vid values are more arbitrary.

I guess you should prepare yourself for some hating then. VoodooPowerMini is supposed to be as small as possible, and not really visible in any way. That is also the reasoning for no configuration. No bells -- no whistles -- but just work.