voodoo-power - Project Hosting on Google Code

Earlier this year Nov 10, 2009 issue 29 (mouse movement/keyboard typing slow down on single core CPU) reported by ole2m...@gmail.com - What steps will reproduce the problem? 1.kernel 9.8.0 (but 9.5.0 has same behavior) 2.loaded voodoopower.kext 3.immediately mouse freeze/slowing down moves (mouse lag?) and keyboard typing slowing/not accepting keys What is the expected output? What do you see instead? regular work no freeze/lags What version of the product are you using? On what operating system? 1.2.3 Please provide any additional information below. processor being tested on - AMD Athlon x64 L110. What steps will reproduce the problem? 1.kernel 9.8.0 (but 9.5.0 has same behavior) 2.loaded voodoopower.kext 3.immediately mouse freeze/slowing down moves (mouse lag?) and keyboard typing slowing/not accepting keys What is the expected output? What do you see instead? regular work no freeze/lags What version of the product are you using? On what operating system? 1.2.3 Please provide any additional information below. processor being tested on - AMD Athlon x64 L110. Oct 11, 2009 issue 28 (Kernel Panic only on Shutdown with Battery In... Restart wor...) Status changed by superhaister - This is bug reporting for VoodooPower not VoodooBattery. Status: Invalid This is bug reporting for VoodooPower not VoodooBattery. Status: Invalid Oct 11, 2009 issue 28 (Kernel Panic only on Shutdown with Battery In... Restart wor...) reported by haze295 - What steps will reproduce the problem? 1. Power-On system (everything runs fine) 2. Restart with only battery in works fine... Shutdown will KP 3. This error is only created through battery only shutdown What is the expected output? What do you see instead? I know it's a trip from Voodoo Battery due to it being the only new change on my system. What version of the product are you using? On what operating system? 10.5.8 Please provide any additional information below. Prior to using Voodoo my shutdown would work fine with out KP, but system did not know it was running off the battery. This kext is working @ almost 100% on this system. I have attached the Log below and any help is GREATLY appreciated. Thank you so much for this software and if you can fix this one for me... please point me to a donations page. :) (I'm serious) What steps will reproduce the problem? 1. Power-On system (everything runs fine) 2. Restart with only battery in works fine... Shutdown will KP 3. This error is only created through battery only shutdown What is the expected output? What do you see instead? I know it's a trip from Voodoo Battery due to it being the only new change on my system. What version of the product are you using? On what operating system? 10.5.8 Please provide any additional information below. Prior to using Voodoo my shutdown would work fine with out KP, but system did not know it was running off the battery. This kext is working @ almost 100% on this system. I have attached the Log below and any help is GREATLY appreciated. Thank you so much for this software and if you can fix this one for me... please point me to a donations page. :) (I'm serious) Oct 05, 2009 issue 27 (SL 10.6.1 only on thread visible (and managed ?)) commented on by guy.delathouwer - Tested on Compaq mini 730, N270 cpu Tested on Compaq mini 730, N270 cpu Oct 05, 2009 issue 27 (SL 10.6.1 only on thread visible (and managed ?)) reported by guy.delathouwer - What steps will reproduce the problem? 1. launch GenericCPUPowerMAnagementControl 2. see that only thread2 is visible 3. What is the expected output? What do you see instead? One thread ieo 2 What version of the product are you using? On what operating system? 10.6.1 voodoopower 1.2.1 Please provide any additional information below. If unload the kext and reload in terminal, then works fine (two threads found and managed). But needs to be done at each boot :( What steps will reproduce the problem? 1. launch GenericCPUPowerMAnagementControl 2. see that only thread2 is visible 3. What is the expected output? What do you see instead? One thread ieo 2 What version of the product are you using? On what operating system? 10.6.1 voodoopower 1.2.1 Please provide any additional information below. If unload the kext and reload in terminal, then works fine (two threads found and managed). But needs to be done at each boot :( Sep 28, 2009 issue 24 (macbookpro 13 inch mid2009. frecuency and restarting/shutdow...) Status changed by superhaister - The ability to manually change the frequency was removed. Restart and shutdown problems should I be able to fix. Status: Accepted The ability to manually change the frequency was removed. Restart and shutdown problems should I be able to fix. Status: Accepted Sep 28, 2009 issue 26 (SpeedStep stops working after sleep on Wind U123 and U100 w/...) commented on by superhaister - 10.6 is not a supported configuration. But please check this http://www.superhai.com/forum/viewtopic.php?f=12&t=90 also the term "latest release" is ambiguous. 10.6 is not a supported configuration. But please check this http://www.superhai.com/forum/viewtopic.php?f=12&t=90 also the term "latest release" is ambiguous. Sep 28, 2009 issue 25 (Default options have the potential to cause KPs for the unsu...) changed by superhaister - I am aware of your issues already and you are probably right. The next iteration will not have the t-states at all. Users not reading the manual is not a bug. Status: Accepted Labels: Type-Other −Type-Defect I am aware of your issues already and you are probably right. The next iteration will not have the t-states at all. Users not reading the manual is not a bug. Status: Accepted Labels: Type-Other −Type-Defect Sep 27, 2009 issue 26 (SpeedStep stops working after sleep on Wind U123 and U100 w/...) reported by BobbyDMarriott - What steps will reproduce the problem? 1. Vanilla install with Voodoo power loading from EFI 2. Boot, put computer to sleep, wake. 3. CPU speed locked at max. What is the expected output? What do you see instead? Speedstep continue working after sleep. After sleep no speedstep is what is happening. Speedstep does work after hibernate however. What version of the product are you using? On what operating system? VoodooPower latest release. OS X 10.6.1 on Wind U123 (Atom N280). Same reported on U100 as well. (Atom N270) Please provide any additional information below. What steps will reproduce the problem? 1. Vanilla install with Voodoo power loading from EFI 2. Boot, put computer to sleep, wake. 3. CPU speed locked at max. What is the expected output? What do you see instead? Speedstep continue working after sleep. After sleep no speedstep is what is happening. Speedstep does work after hibernate however. What version of the product are you using? On what operating system? VoodooPower latest release. OS X 10.6.1 on Wind U123 (Atom N280). Same reported on U100 as well. (Atom N270) Please provide any additional information below. Sep 24, 2009 issue 25 (Default options have the potential to cause KPs for the unsu...) reported by gareth.mcclean - What steps will reproduce the problem? 1. Down load the package 2. Check the Info.plist What is the expected out? What do you see instead? Expect 'VoltageProbe' to have its default set to 'false' not true to avoid potential risk of KP's with people who don't read the manual. May also want to change the tstate defaults for battery power as they also seem to cause issues on some systems. What steps will reproduce the problem? 1. Down load the package 2. Check the Info.plist What is the expected out? What do you see instead? Expect 'VoltageProbe' to have its default set to 'false' not true to avoid potential risk of KP's with people who don't read the manual. May also want to change the tstate defaults for battery power as they also seem to cause issues on some systems. Aug 08, 2009 issue 23 (Intel Dynamic FSB not compatible) commented on by lokomsn - OpenInstall.kext (dsmos from psystar) was causing my blue screen loop because protected bynary start to crash after a couple of hours, back to dsmos.kext and no more problems. Another way to have voodoopower working with correct fsb is deactivating IDA from bios. For those who use native speedstep with core2duo and nvidia 8600m gt you must use macbookpro3,1 and add: <key>iGPUThrottle</key> <true/> remove: <key>MacBookPro3,1</key> <string>TA2</string> on GPUThreesholdDict and add: <key>MacBookPro3,1</key> <string>CIA1</string> on GPUControlInfoDict, with this modifications graphics will run smoothly!! without display sleep trick, only works with native speedstep. OpenInstall.kext (dsmos from psystar) was causing my blue screen loop because protected bynary start to crash after a couple of hours, back to dsmos.kext and no more problems. Another way to have voodoopower working with correct fsb is deactivating IDA from bios. For those who use native speedstep with core2duo and nvidia 8600m gt you must use macbookpro3,1 and add: <key>iGPUThrottle</key> <true/> remove: <key>MacBookPro3,1</key> <string>TA2</string> on GPUThreesholdDict and add: <key>MacBookPro3,1</key> <string>CIA1</string> on GPUControlInfoDict, with this modifications graphics will run smoothly!! without display sleep trick, only works with native speedstep. Aug 06, 2009 Barracuda (Flow of new version 1.3.x) Wiki page commented on by MowgliBook - Core i7 support Core i7 support Aug 04, 2009 issue 24 (macbookpro 13 inch mid2009. frecuency and restarting/shutdow...) reported by manu100por100 - What steps will reproduce the problem? 1. install vodoopower in new macbook (mid2009) with kexthelper and repair permisions with diskutil 2. try to change the frecuency or undervolting with genericCpuPower app (i dont know another possible way) or... 3. try to reboot or shut down the unibody macbookpro What is the expected output? What do you see instead? first of all, the macbook never shutsdown neither restart till i delete voodoopower.kext (its happend the same thing with genericCpuPowerManagement Kext) the second problem is that the max and the minimum frecuency and voltage detected in genericCpuPowerManagement app are the same, so i cant change them, at least in this app. It was not the same with the older kext, genericCpuPowerManagement one. With that kext i was able to change the frecuency and the voltage. What version of the product are you using? On what operating system? the newer one: Leopard 10.5.7 and voodoo power updated Tuesday, 07-Apr-2009 01:05 (unknown version) Please provide any additional information below. Please, post what information sould be usefull and the way to get it. Thank you very much. What steps will reproduce the problem? 1. install vodoopower in new macbook (mid2009) with kexthelper and repair permisions with diskutil 2. try to change the frecuency or undervolting with genericCpuPower app (i dont know another possible way) or... 3. try to reboot or shut down the unibody macbookpro What is the expected output? What do you see instead? first of all, the macbook never shutsdown neither restart till i delete voodoopower.kext (its happend the same thing with genericCpuPowerManagement Kext) the second problem is that the max and the minimum frecuency and voltage detected in genericCpuPowerManagement app are the same, so i cant change them, at least in this app. It was not the same with the older kext, genericCpuPowerManagement one. With that kext i was able to change the frecuency and the voltage. What version of the product are you using? On what operating system? the newer one: Leopard 10.5.7 and voodoo power updated Tuesday, 07-Apr-2009 01:05 (unknown version) Please provide any additional information below. Please, post what information sould be usefull and the way to get it. Thank you very much. Jul 23, 2009 issue 23 (Intel Dynamic FSB not compatible) commented on by lokomsn - sorry about that 1292 value was from mercurysquad sysctl wich i had to override voltages too for working correct, however, i need to override voltage in voodoopower for no ovearheating, i dont know why.., maybe min frequency? 1012 mv never goes down temps to 48C and fans doesnt turn off, 940mv does it, but if max freq is right it must not overheat at all, right now im with native speedstep it works great for me and is integrated with saving power features for ex. changing battery preference to max duration do less throtling i think is something like threeshold and hystersis values in voodoopower but automatically and no need to restart, with more time i will try voodoopower again (i got right _PSS and fsb corrected with chameleon smbios inject) and upload a new log if you like. sorry about that 1292 value was from mercurysquad sysctl wich i had to override voltages too for working correct, however, i need to override voltage in voodoopower for no ovearheating, i dont know why.., maybe min frequency? 1012 mv never goes down temps to 48C and fans doesnt turn off, 940mv does it, but if max freq is right it must not overheat at all, right now im with native speedstep it works great for me and is integrated with saving power features for ex. changing battery preference to max duration do less throtling i think is something like threeshold and hystersis values in voodoopower but automatically and no need to restart, with more time i will try voodoopower again (i got right _PSS and fsb corrected with chameleon smbios inject) and upload a new log if you like. Jul 23, 2009 issue 23 (Intel Dynamic FSB not compatible) commented on by superhaister - According to the log, voodoopower found the voltage range to be from VID 0x25 (1175 mV) to VID 0x18 (1012 mV). Where do you find 1292 mV from? And the frequency range is from FID 0x0A (2000 MHz) to FID 0x86 (600 MHz). If IDA was supported you would have an extra P-State of 2200 MHz. You still need to fix the issue with incorrect fsb reported in your system. If mercurysquads speestep kext work better it might be because your laptop is not stable in the SLFM P-States. According to the log, voodoopower found the voltage range to be from VID 0x25 (1175 mV) to VID 0x18 (1012 mV). Where do you find 1292 mV from? And the frequency range is from FID 0x0A (2000 MHz) to FID 0x86 (600 MHz). If IDA was supported you would have an extra P-State of 2200 MHz. You still need to fix the issue with incorrect fsb reported in your system. If mercurysquads speestep kext work better it might be because your laptop is not stable in the SLFM P-States. Jul 22, 2009 issue 23 (Intel Dynamic FSB not compatible) commented on by lokomsn - Ok, i think that maybe was IDA because voodoopower uses 1292 voltage for max freq (2000) and this was causing overheating, even with the right _PSS (dumped with acpidump from linux), but with voltage override 940 min 1175 max works great, i comment again to say that blue screen loop commented previously was not caused by voodoopower because ocurred again with native speedsteep, i dont know what cause this, im testing.. Ok, i think that maybe was IDA because voodoopower uses 1292 voltage for max freq (2000) and this was causing overheating, even with the right _PSS (dumped with acpidump from linux), but with voltage override 940 min 1175 max works great, i comment again to say that blue screen loop commented previously was not caused by voodoopower because ocurred again with native speedsteep, i dont know what cause this, im testing.. Jul 19, 2009 issue 23 (Intel Dynamic FSB not compatible) commented on by superhaister - It is correct that IDA is not supported. But that can't cause overheating. It is correct that IDA is not supported. But that can't cause overheating. Jul 18, 2009 issue 23 (Intel Dynamic FSB not compatible) commented on by lokomsn - Finally i fixed rebuilding _PSS table from SSDT, but voodoopower keep ovearheating because cant handle IDA (Intel Dynamic Acceleration) so i have to override voltage with 940 (min) 1175 (max) and no more overheating, but it doesnt work well for me, not kernel panic but extrange loop rebooting Aqua.. speedsteep from mercurysquad works better for me, but this cant put my clock to 800mhz so finally i patch ACPI_SMC_PlatformPlugin.kext to have native speedsteep, and this works GREAT, no ovearheating, more battery life (like 40 mins) and can use CoolBook to regulate voltages, so if you have a supported intel laptop and vainilla installation use native speedstep!, thats all!, thanks!! bye. Finally i fixed rebuilding _PSS table from SSDT, but voodoopower keep ovearheating because cant handle IDA (Intel Dynamic Acceleration) so i have to override voltage with 940 (min) 1175 (max) and no more overheating, but it doesnt work well for me, not kernel panic but extrange loop rebooting Aqua.. speedsteep from mercurysquad works better for me, but this cant put my clock to 800mhz so finally i patch ACPI_SMC_PlatformPlugin.kext to have native speedsteep, and this works GREAT, no ovearheating, more battery life (like 40 mins) and can use CoolBook to regulate voltages, so if you have a supported intel laptop and vainilla installation use native speedstep!, thats all!, thanks!! bye. Jul 16, 2009 issue 11 (CPU Frequency is wrong print on over 2147MHz) commented on by hokarin86 - hi , yungwesl. sorry, slow reply. I check fixed source , and build it ,then cpu frequency is normal print over 2147MH. http://www39.atwiki.jp/macmini/pub/GCPMC.jpg please, commit cvs. hi , yungwesl. sorry, slow reply. I check fixed source , and build it ,then cpu frequency is normal print over 2147MH. http://www39.atwiki.jp/macmini/pub/GCPMC.jpg please, commit cvs. Jul 07, 2009 issue 22 (L7500 wrong max cpu frequency) commented on by jajocalDAV - i fixed it. reinstalled 10.5.7 combo update, replaced the smbios.kext with the original from 10.5.6, edited the Info.plist of voodoopowermini.kext and seted useefifsb to false, chmod 644 Info.plist, used JaS SPPlatformReporter.spreporter from the "10.5.7 released" thread at insanelymac forum. now it is reporting full speed (1600MHz) an stepping is correct. thanxs for your help! i love voodoopower! :) i fixed it. reinstalled 10.5.7 combo update, replaced the smbios.kext with the original from 10.5.6, edited the Info.plist of voodoopowermini.kext and seted useefifsb to false, chmod 644 Info.plist, used JaS SPPlatformReporter.spreporter from the "10.5.7 released" thread at insanelymac forum. now it is reporting full speed (1600MHz) an stepping is correct. thanxs for your help! i love voodoopower! :) Jul 07, 2009 issue 23 (Intel Dynamic FSB not compatible) Status changed by superhaister - It is the wrong fsb from system issue. No bug, fix it yourself. Status: Invalid It is the wrong fsb from system issue. No bug, fix it yourself. Status: Invalid Jul 06, 2009 issue 23 (Intel Dynamic FSB not compatible) commented on by lokomsn - Sorry, here is my debug log. Sorry, here is my debug log. Jul 06, 2009 issue 23 (Intel Dynamic FSB not compatible) commented on by superhaister - http://www.superhai.com/forum/viewtopic.php?f=12&t=90 http://www.superhai.com/forum/viewtopic.php?f=12&t=90 Jul 06, 2009 issue 22 (L7500 wrong max cpu frequency) Status changed by superhaister - The kext throttles to multi 8x, but your system provides the fsb frequency of 177342340 hz. You will need to fix that. Status: Invalid The kext throttles to multi 8x, but your system provides the fsb frequency of 177342340 hz. You will need to fix that. Status: Invalid Jul 03, 2009 issue 23 (Intel Dynamic FSB not compatible) reported by lokomsn - What steps will reproduce the problem? 1. m1530 - intel ichx, intel c2o t7250 (speedstep and intel dynamic fsb) 2. use voodoopower 3. What is the expected output? What do you see instead? expected to see right freq (2000ghz), i see incorrect freqs with useefifsb true and false What version of the product are you using? On what operating system? 1.2.3 Please provide any additional information below. i think the problem is because voodoopower cant handle Intel dynamic fsb.. (100mhz & 200mhz) What steps will reproduce the problem? 1. m1530 - intel ichx, intel c2o t7250 (speedstep and intel dynamic fsb) 2. use voodoopower 3. What is the expected output? What do you see instead? expected to see right freq (2000ghz), i see incorrect freqs with useefifsb true and false What version of the product are you using? On what operating system? 1.2.3 Please provide any additional information below. i think the problem is because voodoopower cant handle Intel dynamic fsb.. (100mhz & 200mhz) Jul 02, 2009 issue 22 (L7500 wrong max cpu frequency) commented on by superhaister - http://www.superhai.com/forum/viewtopic.php?f=12&t=90 http://www.superhai.com/forum/viewtopic.php?f=12&t=90 Jul 02, 2009 issue 22 (L7500 wrong max cpu frequency) reported by jajocalDAV - What steps will reproduce the problem? using voodopower 1.2.3 on thinkpad x61s with L7500 What is the expected output? What do you see instead? should go up to 1600MHz (8x200) but only goes to up to 1418 (7200) What version of the product are you using? On what operating system? voodoopower 1.2.3, iPC 10.5.7, chameleon 2 rc1, smbios.plist with mabookpro4.1, maxcpufrequency and externalclock Please provide any additional information below. some info about the cpu: http://ark.intel.com/Product.aspx?id=29757 if you need more infos, just ask. :) What steps will reproduce the problem? using voodopower 1.2.3 on thinkpad x61s with L7500 What is the expected output? What do you see instead? should go up to 1600MHz (8x200) but only goes to up to 1418 (7200) What version of the product are you using? On what operating system? voodoopower 1.2.3, iPC 10.5.7, chameleon 2 rc1, smbios.plist with mabookpro4.1, maxcpufrequency and externalclock Please provide any additional information below. some info about the cpu: http://ark.intel.com/Product.aspx?id=29757 if you need more infos, just ask. :) Jun 23, 2009 issue 19 (Gateway Laptop on battery = Kernel Panic) Status changed by superhaister - You could try to restrict the p-states with the lower frequencies and see if it solves it. Other than that I have no idea what causes it. Status: Accepted You could try to restrict the p-states with the lower frequencies and see if it solves it. Other than that I have no idea what causes it. Status: Accepted Jun 23, 2009 issue 21 (Problem: Highest Pstate (0) is multi 9,5 (BIOS) but will set...) Status changed by superhaister - Actually - your CPU has max multi of 10. The kext has no chance of knowing that your computer will fail at that p-state as you have it overclocked above its limits. Your CPU will still report max multi of 10 and that will voodoopower jump to when load is at highest. So no bug. And yet again, please provide version NUMBERS in your bug reports. Status: WontFix Actually - your CPU has max multi of 10. The kext has no chance of knowing that your computer will fail at that p-state as you have it overclocked above its limits. Your CPU will still report max multi of 10 and that will voodoopower jump to when load is at highest. So no bug. And yet again, please provide version NUMBERS in your bug reports. Status: WontFix Jun 22, 2009 issue 21 (Problem: Highest Pstate (0) is multi 9,5 (BIOS) but will set...) commented on by ice...@freenet.de - Thanks, no problem. kext was VoodooPowerMini , aktual dl. I will use that kext only for longtime downloads / long time system up without very much CPU load, by setting PstateLimitHigh=1 for avoid the OC freeze. So it doenst matter really with the Pstate=0 freeze problem because 10333 insted of 9,5333. Thanks, no problem. kext was VoodooPowerMini , aktual dl. I will use that kext only for longtime downloads / long time system up without very much CPU load, by setting PstateLimitHigh=1 for avoid the OC freeze. So it doenst matter really with the Pstate=0 freeze problem because 10333 insted of 9,5333. Jun 21, 2009 issue 19 (Gateway Laptop on battery = Kernel Panic) commented on by michote - Even though the problem is very repeatable. Every time I am in Battery Power, it freezes but no KP. Just frozen. In single user mode no kernel panic. My temp solution was to go back to version 1.2.1 Even though the problem is very repeatable. Every time I am in Battery Power, it freezes but no KP. Just frozen. In single user mode no kernel panic. My temp solution was to go back to version 1.2.1 Jun 21, 2009 issue 19 (Gateway Laptop on battery = Kernel Panic) commented on by superhaister - If you see the kernel panic screen, i need the debug from it. If you see the kernel panic screen, i need the debug from it. Jun 21, 2009 issue 21 (Problem: Highest Pstate (0) is multi 9,5 (BIOS) but will set...) Status changed by superhaister - Status: Accepted Status: Accepted Jun 21, 2009 issue 21 (Problem: Highest Pstate (0) is multi 9,5 (BIOS) but will set...) commented on by superhaister - Please provide version number for your "latest" and also make a debug log as described in the forum. The issue is due to the overclock, if you overclock with multi without .5 it should work. That is because the kext don't expect .5 increments when the cpu don't have highest p-state set to such. Please provide version number for your "latest" and also make a debug log as described in the forum. The issue is due to the overclock, if you overclock with multi without .5 it should work. That is because the kext don't expect .5 increments when the cpu don't have highest p-state set to such. Jun 21, 2009 issue 21 (Problem: Highest Pstate (0) is multi 9,5 (BIOS) but will set...) commented on by ice...@freenet.de - Forgot: Intel E7300 CPU normal at 2.66 GHZ, i OC it to 3.16 (FSB 266>333, Multi 9.0 + 0.5= 9.5) Stable at 3.16 for hours, freezes with BIOS setting 10 also freeze with BIOS setting 9,5 and running power kext without PlimitHigh =1 (avoid 3.33 GHZ= Pstate 0 with 10333) Does power kext overrite the BIOS setting 9,5 (3339,5=3,16 GHZ not 3.33) Forgot: Intel E7300 CPU normal at 2.66 GHZ, i OC it to 3.16 (FSB 266>333, Multi 9.0 + 0.5= 9.5) Stable at 3.16 for hours, freezes with BIOS setting 10 also freeze with BIOS setting 9,5 and running power kext without PlimitHigh =1 (avoid 3.33 GHZ= Pstate 0 with 10333) Does power kext overrite the BIOS setting 9,5 (3339,5=3,16 GHZ not 3.33) Jun 21, 2009 issue 21 (Problem: Highest Pstate (0) is multi 9,5 (BIOS) but will set...) reported by ice...@freenet.de - What steps will reproduce the problem? 1. BIOS Setting Multi 9,5 (333 FSB, max. 3.16 GHZ 2. start Power kext with right Voltsettings, if switches to Pstate 0 = frezze and CPU-Z /MSR Toolshows 3.3 GHZ (to much) 3. What is the expected output? What do you see instead? I set PStateHigh Limit to 1, so no more freezes because the 3.33 GHz didnt can set anymore What version of the product are you using? On what operating system? latest Please provide any additional information below. Perhaps the BIOS settting (GA-EP35-DS3) 9,5 makes the problem ? What steps will reproduce the problem? 1. BIOS Setting Multi 9,5 (333 FSB, max. 3.16 GHZ 2. start Power kext with right Voltsettings, if switches to Pstate 0 = frezze and CPU-Z /MSR Toolshows 3.3 GHZ (to much) 3. What is the expected output? What do you see instead? I set PStateHigh Limit to 1, so no more freezes because the 3.33 GHz didnt can set anymore What version of the product are you using? On what operating system? latest Please provide any additional information below. Perhaps the BIOS settting (GA-EP35-DS3) 9,5 makes the problem ? Jun 07, 2009 issue 11 (CPU Frequency is wrong print on over 2147MHz) commented on by yungwesl - Thanks hokarin86, I made the change you suggested as well as fixed the menu frequency readout as well and compiled the code changes here (with source) http://www.mediafire.com/?sharekey=1b87f3ea5f4c368ee7ba8e3c6e11ce20e04e75f6e8ebb871 Thanks hokarin86, I made the change you suggested as well as fixed the menu frequency readout as well and compiled the code changes here (with source) http://www.mediafire.com/?sharekey=1b87f3ea5f4c368ee7ba8e3c6e11ce20e04e75f6e8ebb871 May 26, 2009 issue 6 (VoodooPower.kext hangs-up Dell Precision M6400 (iPC 10.5.6)) commented on by jazzminos - Hi. I'm using VoodooPower on Toshiba Laptop P100-257. Everything works fine. No issues. I'd like to ask if it is possible to fix the fans issue? When I boot Mac Os fans frequently stop during the boot. I have stock kernel & stock ACPI. This causes great overheating. There is an application i8kfan for Dell laptops but it doesn't work on my Toshi. Thanks for reply. With great respect, jazzminos. Hi. I'm using VoodooPower on Toshiba Laptop P100-257. Everything works fine. No issues. I'd like to ask if it is possible to fix the fans issue? When I boot Mac Os fans frequently stop during the boot. I have stock kernel & stock ACPI. This causes great overheating. There is an application i8kfan for Dell laptops but it doesn't work on my Toshi. Thanks for reply. With great respect, jazzminos. May 14, 2009 issue 19 (Gateway Laptop on battery = Kernel Panic) commented on by michote - Okey, I updated to 10.5.7 still the same problem. The computer freezes without kernel panic (running in -v mode). In single user -s mode it does not freeze. Attached the logs. I don't know what else you want me to do tu help you with the debug. Okey, I updated to 10.5.7 still the same problem. The computer freezes without kernel panic (running in -v mode). In single user -s mode it does not freeze. Attached the logs. I don't know what else you want me to do tu help you with the debug. May 13, 2009 issue 19 (Gateway Laptop on battery = Kernel Panic) commented on by nadims - Okey, I updated to 10.5.7 still the same problem. The computer freezes without kernel panic (running in -v mode). In single user -s mode it does not freeze. Attached the logs. I don't know what else you want me to do tu help you with the debug. Okey, I updated to 10.5.7 still the same problem. The computer freezes without kernel panic (running in -v mode). In single user -s mode it does not freeze. Attached the logs. I don't know what else you want me to do tu help you with the debug. May 10, 2009 issue 18 (VoodooPower locks up system upon load) commented on by superhaister - SLFM is one of the features of the 45nm mobile cpus, so it will be enabled by default. The reason i suspect m/b is because what intel does say is that it is not possible to set the cpu to a non-working p-state as opposed to AMD, hence it has to be some other cause. Some reports that the nvidia mcp chipset has difficulties with the dynamic fsb feature. The VoodooPower calculation is based on comparing many ACPI P-State tables. They all have lower VID's than LFM modes for SLFM. Because linux and vista both uses ACPI to find the P-States, it is no wonder they don't have any issues. Microsoft probably also have access to all docs from intel as well. SLFM is one of the features of the 45nm mobile cpus, so it will be enabled by default. The reason i suspect m/b is because what intel does say is that it is not possible to set the cpu to a non-working p-state as opposed to AMD, hence it has to be some other cause. Some reports that the nvidia mcp chipset has difficulties with the dynamic fsb feature. The VoodooPower calculation is based on comparing many ACPI P-State tables. They all have lower VID's than LFM modes for SLFM. Because linux and vista both uses ACPI to find the P-States, it is no wonder they don't have any issues. Microsoft probably also have access to all docs from intel as well. May 10, 2009 issue 20 (Clock speed limited to 2.3Ghz on a 2.5Ghz C2D) Status changed by superhaister - The kernel reports FSB of 185 MHz, either your system is underclocked or the kernel have the wrong FSB, in case you have to fix it there. No bug. Status: WontFix The kernel reports FSB of 185 MHz, either your system is underclocked or the kernel have the wrong FSB, in case you have to fix it there. No bug. Status: WontFix May 09, 2009 issue 20 (Clock speed limited to 2.3Ghz on a 2.5Ghz C2D) commented on by ludacri...@hotmail.com - Here is the information you needed. I hope it helps. Here is the information you needed. I hope it helps. May 09, 2009 issue 20 (Clock speed limited to 2.3Ghz on a 2.5Ghz C2D) commented on by superhaister - I need some debug information http://www.superhai.com/forum/viewtopic.php?f=12&t=90 I need some debug information http://www.superhai.com/forum/viewtopic.php?f=12&t=90 May 07, 2009 issue 20 (Clock speed limited to 2.3Ghz on a 2.5Ghz C2D) reported by ludacri...@hotmail.com - What steps will reproduce the problem? 1. Install Voodoopower.kext on Toshiba Satellite X205-SLI6 What is the expected output? What do you see instead? I expect my clock speed to vary and to peak at 2500Mhz However no matter what I run it always peaks at 2300Mhz What version of the product are you using? On what operating system? I would think it is the latest version. 10.5.2 vanilla What steps will reproduce the problem? 1. Install Voodoopower.kext on Toshiba Satellite X205-SLI6 What is the expected output? What do you see instead? I expect my clock speed to vary and to peak at 2500Mhz However no matter what I run it always peaks at 2300Mhz What version of the product are you using? On what operating system? I would think it is the latest version. 10.5.2 vanilla Apr 30, 2009 issue 18 (VoodooPower locks up system upon load) commented on by bccspam - Thanks for the info, I was afraid there was no documentation. I'm surprised you were able to do so much without documentation. The lack of docs makes me wonder why you suspect my laptop's motherboard/bios over the way your code is handling super-lfm. I'm largely guessing, since I don't have any documentation, that the super-lfm modes wouldn't be at a lower VID than the 6x p-state. Since your code is using vidstep to set the super-lfm p-states below the 6x VID, those values could be out of bounds and cause the cpu malfunction. It's interesting to note that linux, vista, and windows7 handle the enhanced speedstep stepping without problems on this laptop. Linux picks up the max/min values via ACPI _PSS. Looking forward to your fix. Perhaps if the CPU is type IntelCore45 and mobile, avoid any super-lfm p-states by default. Then you can allow super-lfm to be re-enabled via a config variable as you suggested. Thanks for the info, I was afraid there was no documentation. I'm surprised you were able to do so much without documentation. The lack of docs makes me wonder why you suspect my laptop's motherboard/bios over the way your code is handling super-lfm. I'm largely guessing, since I don't have any documentation, that the super-lfm modes wouldn't be at a lower VID than the 6x p-state. Since your code is using vidstep to set the super-lfm p-states below the 6x VID, those values could be out of bounds and cause the cpu malfunction. It's interesting to note that linux, vista, and windows7 handle the enhanced speedstep stepping without problems on this laptop. Linux picks up the max/min values via ACPI _PSS. Looking forward to your fix. Perhaps if the CPU is type IntelCore45 and mobile, avoid any super-lfm p-states by default. Then you can allow super-lfm to be re-enabled via a config variable as you suggested. Apr 28, 2009 issue 18 (VoodooPower locks up system upon load) commented on by superhaister - I did use the ACPI methods formerly, I actually made an option to use pure ACPI calls for powermanagement (but few used it as the overhead was slightly higher, but worked on all CPU's including AMD). Problem with ACPI is that there are lot more laptops without proper _PSS entries. Some have it missing, some have incorrect or proprietary formats. OS X and ACPI are also not good friends all the time, and using it via "/Extra" will be difficult. About your case, I don't think it is the CPU but the M/B that is the reason why you can't get the lower modes. There is no documentation about powermanagement control for newer intel cpus available for general public. You need to be a related business with an agreement with intel to receive the bios writers manuals. I did use the ACPI methods formerly, I actually made an option to use pure ACPI calls for powermanagement (but few used it as the overhead was slightly higher, but worked on all CPU's including AMD). Problem with ACPI is that there are lot more laptops without proper _PSS entries. Some have it missing, some have incorrect or proprietary formats. OS X and ACPI are also not good friends all the time, and using it via "/Extra" will be difficult. About your case, I don't think it is the CPU but the M/B that is the reason why you can't get the lower modes. There is no documentation about powermanagement control for newer intel cpus available for general public. You need to be a related business with an agreement with intel to receive the bios writers manuals. Apr 27, 2009 issue 18 (VoodooPower locks up system upon load) commented on by bcc24x7 - Well I'd be happy to use super-LFM modes if they worked instead of locking up the whole PC. Do you know how to make those states work for this mobile processor? Yes, I figured I wasn't avoiding the problem in the cleanest way, but I couldn't sort out the semantics, so I resorted to what was safe but not pretty. That's why I was hoping you could point me to some documentation of this stuff that applies to current mobile processors. You say it isn't easy to find the range generically, but I noticed that the xnu-speedstep code is able to get the min&max p-states for my processor with the intel recommended ACPI methods (from _PSS). I guess I don't understand why you're not looking at the ACPI tables when available if the lower level methods are less safe. Well I'd be happy to use super-LFM modes if they worked instead of locking up the whole PC. Do you know how to make those states work for this mobile processor? Yes, I figured I wasn't avoiding the problem in the cleanest way, but I couldn't sort out the semantics, so I resorted to what was safe but not pretty. That's why I was hoping you could point me to some documentation of this stuff that applies to current mobile processors. You say it isn't easy to find the range generically, but I noticed that the xnu-speedstep code is able to get the min&max p-states for my processor with the intel recommended ACPI methods (from _PSS). I guess I don't understand why you're not looking at the ACPI tables when available if the lower level methods are less safe. Apr 27, 2009 issue 18 (VoodooPower locks up system upon load) commented on by superhaister - If you don't want the SLFM mode, it is better to modify the source to ensure Intel_DynamicFSB is false after CPU detection. (It is the same thing) There is no easy way to find the stepping range generically. The kext has two methods, one is for laptops, as mobile cpus is mostly programmed to start in minimum fid & vid, and maximum is easy to read from msr's. The other option is to probe, but the issue here is that during probe you will encounter a state that cpu becomes unstable (i.e. motherboard is not able to provide proper power anymore) If you don't want the SLFM mode, it is better to modify the source to ensure Intel_DynamicFSB is false after CPU detection. (It is the same thing) There is no easy way to find the stepping range generically. The kext has two methods, one is for laptops, as mobile cpus is mostly programmed to start in minimum fid & vid, and maximum is easy to read from msr's. The other option is to probe, but the issue here is that during probe you will encounter a state that cpu becomes unstable (i.e. motherboard is not able to provide proper power anymore) Apr 27, 2009 issue 18 (VoodooPower locks up system upon load) commented on by bcc24x7 - Er, correction to those diffs: Er, correction to those diffs:

issue 24 (macbookpro 13 inch mid2009. frecuency and restarting/shutdow...) reported by manu100por100 - What steps will reproduce the problem? 1. install vodoopower in new macbook (mid2009) with kexthelper and repair permisions with diskutil 2. try to change the frecuency or undervolting with genericCpuPower app (i dont know another possible way) or... 3. try to reboot or shut down the unibody macbookpro What is the expected output? What do you see instead? first of all, the macbook never shutsdown neither restart till i delete voodoopower.kext (its happend the same thing with genericCpuPowerManagement Kext) the second problem is that the max and the minimum frecuency and voltage detected in genericCpuPowerManagement app are the same, so i cant change them, at least in this app. It was not the same with the older kext, genericCpuPowerManagement one. With that kext i was able to change the frecuency and the voltage. What version of the product are you using? On what operating system? the newer one: Leopard 10.5.7 and voodoo power updated Tuesday, 07-Apr-2009 01:05 (unknown version) Please provide any additional information below. Please, post what information sould be usefull and the way to get it. Thank you very much.

What steps will reproduce the problem? 1. install vodoopower in new macbook (mid2009) with kexthelper and repair permisions with diskutil 2. try to change the frecuency or undervolting with genericCpuPower app (i dont know another possible way) or... 3. try to reboot or shut down the unibody macbookpro What is the expected output? What do you see instead? first of all, the macbook never shutsdown neither restart till i delete voodoopower.kext (its happend the same thing with genericCpuPowerManagement Kext) the second problem is that the max and the minimum frecuency and voltage detected in genericCpuPowerManagement app are the same, so i cant change them, at least in this app. It was not the same with the older kext, genericCpuPowerManagement one. With that kext i was able to change the frecuency and the voltage. What version of the product are you using? On what operating system? the newer one: Leopard 10.5.7 and voodoo power updated Tuesday, 07-Apr-2009 01:05 (unknown version) Please provide any additional information below. Please, post what information sould be usefull and the way to get it. Thank you very much.

Earlier this year