Vostro 3700. Others are working on vanilla speedstepping but I wish to get the Voodoo implementation working. I can't really tell what's going on here besides the fact that something else is screwing around with the p-states, and VoodooPowerMini only detects one p-state (0) while many exist and it appears to bounce between them, although the Intel speedstepping kexts have been removed.
Attached is a copy of the vanilla linux-extracted DSDT, if that's of any help at all.
I'm going to try VoodooPowerAcpi soon but just to let you know there's an issue here.
6/27/10 8:27:41 PM kernel Voodoo[0xFFFFFF7F8085BBC5] probe: 96: CPU Family 6 Model 37
6/27/10 8:27:41 PM kernel Voodoo[0xFFFFFF7F8085C6B6] probe: 259: P-state 0 - 0000
6/27/10 8:27:41 PM kernel Voodoo[0xFFFFFF7F8085C71E] probe: 262: Thresholds Upper 375/500 75 % Lower 125/500 25 %
6/27/10 8:27:41 PM kernel VoodooPowerMini 1.2 (C) 2009-10 Superhai, All Rights Reserved. May 1 2010 13:49:35 DEBUG 64 bit
6/27/10 9:04:02 PM kernel VoodooPowerMini: Failed to get full power management control of CPU
6/27/10 9:04:02 PM kernel Voodoo[0xFFFFFF7F8130BD17] event: 366: Lost control: State 0009 expected 0000 (0)
6/27/10 9:04:02 PM kernel Voodoo[0xFFFFFF7F8130BE19] event: 378: Setting P-State to 0
6/27/10 9:04:02 PM kernel Voodoo[0xFFFFFF7F8130BEEA] event: 386: External power connected and battery good
6/27/10 9:04:02 PM kernel Voodoo[0xFFFFFF7F8130C35A] event: 457: Ticks: Idle (447/500) = 89 % Trend Down Current P-State 0
6/27/10 9:04:07 PM kernel Voodoo[0xFFFFFF7F8130BD17] event: 366: Lost control: State 0009 expected 0000 (0)
6/27/10 9:04:07 PM kernel Voodoo[0xFFFFFF7F8130BE19] event: 378: Setting P-State to 0
6/27/10 9:04:07 PM kernel Voodoo[0xFFFFFF7F8130BEEA] event: 386: External power connected and battery good
6/27/10 9:04:07 PM kernel Voodoo[0xFFFFFF7F8130C35A] event: 457: Ticks: Idle (427/500) = 85 % Trend Down Current P-State 0
6/27/10 9:04:12 PM kernel VoodooPowerMini: Failed to get full power management control of CPU
6/27/10 9:04:12 PM kernel Voodoo[0xFFFFFF7F8130BD17] event: 366: Lost control: State 0011 expected 0000 (0)
6/27/10 9:04:12 PM kernel Voodoo[0xFFFFFF7F8130BE19] event: 378: Setting P-State to 0
6/27/10 9:04:12 PM kernel Voodoo[0xFFFFFF7F8130BEEA] event: 386: External power connected and battery good
6/27/10 9:04:12 PM kernel Voodoo[0xFFFFFF7F8130C35A] event: 457: Ticks: Idle (429/500) = 85 % Trend Down Current P-State 0
6/27/10 9:04:17 PM kernel Voodoo[0xFFFFFF7F8130BD17] event: 366: Lost control: State 0011 expected 0000 (0)
6/27/10 9:04:17 PM kernel Voodoo[0xFFFFFF7F8130BE19] event: 378: Setting P-State to 0
6/27/10 9:04:17 PM kernel Voodoo[0xFFFFFF7F8130BEEA] event: 386: External power connected and battery good
6/27/10 9:04:17 PM kernel Voodoo[0xFFFFFF7F8130C35A] event: 457: Ticks: Idle (419/500) = 83 % Trend Down Current P-State 0
6/27/10 9:04:22 PM kernel VoodooPowerMini: Failed to get full power management control of CPU
6/27/10 9:04:22 PM kernel Voodoo[0xFFFFFF7F8130BD17] event: 366: Lost control: State 0009 expected 0000 (0)
6/27/10 9:04:22 PM kernel Voodoo[0xFFFFFF7F8130BE19] event: 378: Setting P-State to 0
6/27/10 9:04:22 PM kernel Voodoo[0xFFFFFF7F8130BEEA] event: 386: External power connected and battery good
6/27/10 9:04:22 PM kernel Voodoo[0xFFFFFF7F8130C35A] event: 457: Ticks: Idle (446/500) = 89 % Trend Down Current P-State 0
6/27/10 9:04:27 PM kernel Voodoo[0xFFFFFF7F8130BD17] event: 366: Lost control: State 0009 expected 0000 (0)
6/27/10 9:04:27 PM kernel Voodoo[0xFFFFFF7F8130BE19] event: 378: Setting P-State to 0
6/27/10 9:04:27 PM kernel Voodoo[0xFFFFFF7F8130BEEA] event: 386: External power connected and battery good
6/27/10 9:04:27 PM kernel Voodoo[0xFFFFFF7F8130C35A] event: 457: Ticks: Idle (433/500) = 86 % Trend Down Current P-State 0