Jump to content

VoodooPowerAcpi 1.2.5 for 10.6.x


Superhai
 Share

16 posts in this topic

Recommended Posts

Version 1.2.5

 

ACPI Edition

There are many of you who can't use VoodooPowerMini, and if you are lucky enough to have a ACPI implementation for controlling Performance Stepping, you can try this one. This will also be a part of the 1.3 release, the code was originally part of the ACPI option from GenericCPUPowerManagement. Downloads, and support is to be done at http://www.superhai.com/

 

Doesn't work?

If you have so called FFixedHW or Functional Fixed Hardware implementation, you can't use this edition. You can post bug report at the forum. I usually don't have the chance to check this thread regularly so do not post issues here. Bugs will most likely be fixed for the 1.3.x release, not earlier. It is not necessary to repost bugs already reported on the forum or in Google Code.

 

System Requirements?

  • x86-class CPU with ACPI control of power management (i.e. not FFixedHW)
  • Darwin Kernel 10.x.x

Link to comment
Share on other sites

Version 1.2.5

 

ACPI Edition

There are many of you who can't use VoodooPowerMini, and if you are lucky enough to have a ACPI implementation for controlling Performance Stepping, you can try this one. This will also be a part of the 1.3 release, the code was originally part of the ACPI option from GenericCPUPowerManagement. Downloads, and support is to be done at http://www.superhai.com/

 

Doesn't work?

If you have so called FFixedHW or Functional Fixed Hardware implementation, you can't use this edition. You can post bug report at the forum. I usually don't have the chance to check this thread regularly so do not post issues here. Bugs will most likely be fixed for the 1.3.x release, not earlier. It is not necessary to repost bugs already reported on the forum or in Google Code.

 

System Requirements?

  • x86-class CPU with ACPI control of power management (i.e. not FFixedHW)
  • Darwin Kernel 10.x.x

Thank you superhai, you did a great job!

 

Sorry for my poor English, because I'm Chinese, I've been just installed the VoodooPowerACPI.kext in /E/E and use kext utility rebuild Extensions.mkext, when I reboot the system and use -v to boot, It didn't show any message about loading this kext, and I didn't see the kext show in System Profiler -> Extensions

 

How can I know the Voodoo Power kext loaded sucessfully?

 

My system is 10.6.2.

 

Thanks!

Link to comment
Share on other sites

If it doesn't load is it most likely because you didn't fulfill the system requirements.

Thanks for reply, the system requirement for the VoodooPowerACPI.kext is:

 

x86-class CPU with ACPI control of power management

 

here is my boot log, can you help me to see is my system match the requirement?

 

I saw this:

 

Dec 24 18:46:11 localhost kernel[0]: ACPI: System State [s0 S3 S4 S5] (S3)

 

so,is my system support "x86-class CPU with ACPI control of power management" ???

 

Dec 24 18:46:11 localhost kernel[0]: npvhash=4095

Dec 24 18:46:11 localhost kernel[0]: Darwin Kernel Version 10.2.0: Tue Nov 3 10:35:19 PST 2009; root:xnu-1486.2.11~1/RELEASE_X86_64

Dec 24 18:46:11 localhost kernel[0]: vm_page_bootstrap: 964723 free pages and 83853 wired pages

Dec 24 18:46:11 localhost kernel[0]: kext submap [0xffffff7f80600000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff8000600000]

Dec 24 18:46:11 localhost kernel[0]: standard timeslicing quantum is 10000 us

Dec 24 18:46:11 localhost kernel[0]: mig_table_max_displ = 73

Dec 24 18:46:11 localhost kernel[0]: [sleepEnabler] Registering PowerManagement dispatch table...

Dec 24 18:46:11 localhost kernel[0]: [sleepEnabler] Calling pmInitComplete()...

Dec 24 18:46:11 localhost kernel[0]: NullCPUPowerManagement::init: properties=0xffffff8009bfbb40

Dec 24 18:46:11 localhost kernel[0]: NullCPUPowerManagement::start

Dec 24 18:46:11 localhost kernel[0]: AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled

Dec 24 18:46:11 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled

Dec 24 18:46:11 localhost kernel[0]: calling mpo_policy_init for Quarantine

Dec 24 18:46:11 localhost kernel[0]: Security policy loaded: Quarantine policy (Quarantine)

Dec 24 18:46:11 localhost kernel[0]: calling mpo_policy_init for Sandbox

Dec 24 18:46:11 localhost kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)

Dec 24 18:46:11 localhost kernel[0]: calling mpo_policy_init for TMSafetyNet

Dec 24 18:46:11 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)

Dec 24 18:46:11 localhost kernel[0]: Copyright © 1982, 1986, 1989, 1991, 1993

Dec 24 18:46:11 localhost kernel[0]: The Regents of the University of California. All rights reserved.

Dec 24 18:46:11 localhost kernel[0]: MAC Framework successfully initialized

Dec 24 18:46:11 localhost kernel[0]: using 16384 buffer headers and 4096 cluster IO buffer headers

Dec 24 18:46:11 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87

Dec 24 18:46:11 localhost kernel[0]: ACPI: System State [s0 S3 S4 S5] (S3)

Dec 24 18:46:11 localhost kernel[0]: netkas presents fakesmc, a kext which emulates smc device

Dec 24 18:46:11 localhost kernel[0]: RTC: Only single RAM bank (128 bytes)

Dec 24 18:46:11 localhost kernel[0]: mbinit: done (64 MB memory set for mbuf pool)

Dec 24 18:46:11 localhost kernel[0]: From path: "uuid",

Dec 24 18:46:11 localhost kernel[0]: Waiting for boot volume with UUID C163E721-5176-370F-9CBF-5F4932B7E96B

Dec 24 18:46:11 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>

Dec 24 18:46:11 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib load succeeded

Dec 24 18:46:11 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IDE1@1F,2/AppleIntelPIIXATARoot/SECD@1/AppleIntelICHxSATA/ATADeviceNub@0/AppleATADiskDriver/IOATABlockStorageDevice/IOBlockStorageDriver/Hitachi HDS721616PLA380 Hitachi HDS721616PLA380/IOGUIDPartitionScheme/Macintosh@2

Dec 24 18:46:11 localhost kernel[0]: BSD root: disk1s2, major 14, minor 5

Dec 24 18:46:11 localhost kernel[0]: Kernel is LP64

Dec 24 18:46:12 localhost kernel[0]: systemShutdown false

Dec 24 18:46:25 localhost kernel[0]: Waiting for DSMOS...

Dec 24 10:46:26 Mac-OS-X-Snow-Leopard-1062 kernel[0]: NTFS driver 3.1 [Flags: R/W].

Dec 24 10:46:26 Mac-OS-X-Snow-Leopard-1062 kernel[0]: NTFS volume name Vista, version 3.1.

Dec 24 10:46:26 Mac-OS-X-Snow-Leopard-1062 kernel[0]: IPv6 packet filtering initialized, default to accept, logging disabled

Dec 24 10:46:28 Mac-OS-X-Snow-Leopard-1062 kernel[0]: Previous Shutdown Cause: 0

Dec 24 10:46:28 Mac-OS-X-Snow-Leopard-1062 kernel[0]: NVDANV50HAL loaded and registered.

Dec 24 10:46:29 Mac-OS-X-Snow-Leopard-1062 kernel[0]: DSMOS has arrived

Dec 24 10:46:29 Mac-OS-X-Snow-Leopard-1062 kernel[0]: AppleRTL8169Ethernet: Ethernet address 00:04:2e:02:0c:1a

Dec 24 10:46:35 061093076080 kernel[0]: ACPI_SMC_PlatformPlugin::start - waitForService(resourceMatching(AppleIntelCPUPowerManagement) timed out

 

I use Netkas SleepEnabler.kext for 10.6.2,OpenHaltRestart.kext,FakeSMC.kext,NullCPUPowerManagement.kext,Pla

tformUUID.kext and VoodooPowerAcpi.kext to boot the system!

 

Thank you!

 

and my system shutdown,sleep,reboot normally...

Link to comment
Share on other sites

This kext stopped my SL 10.6.2 on my Eee 901 from working. It somehow messed up the whole system. Maybe it was just me who did sth wrong but after reinstalling (couldn't get my system working) i'll stick with voodoopowermini.

Link to comment
Share on other sites

Hi,

 

this might be a stupid question, but how do I check if P-state changing is actually happening?

Can I trust CPU-X for this? Because if I can, then nothing is changing.

With Voodoopowermini I did see changes in CPU-x.

Link to comment
Share on other sites

Hi,

 

this might be a stupid question, but how do I check if P-state changing is actually happening?

Can I trust CPU-X for this? Because if I can, then nothing is changing.

With Voodoopowermini I did see changes in CPU-x.

 

You could also use the command sysctl from within the command line/terminal.

You could use : sysctl|grep -i freq

 

the value corresponding to curfreq will give the current frequency of the CPU,by varying the load,this should vary and hence you can validate if frequency scaling is occuring or not.

Link to comment
Share on other sites

I agree it's too bad there's no 10.5.x support. My P4 Hackintosh would like it.

 

Another question in the 'may be stupid' category:

 

Is disabling of AppleIntelCPUPowermanagement.kext required to use VoodooPowerACPI? (I'm guessing that's a yes).

Link to comment
Share on other sites

  • 3 weeks later...
  • 1 month later...
 Share

×
×
  • Create New...