Skip to contentSkip to conversation

Speedstep on a Pentium4 630 (2.6.13)

DISCUSSION celtune-gmx 2 participants 4 messages Jan 18, 2006 – Jan 22, 2006 3 messages not in the archive

lore
Share & tools
lore
#0 lore raw

HI!

Does somebody know how to scale a Pentium 630 (3,0 GHz) to another freq. than 2,8 GHz or 3,0 GHz (Slackware10.2)? I use centrino-module and ondemand, or can somebody send me a FID/VID Table for my 630? or is there a Patch for the 2.6.13 kernel.

Thanks cel

#1 lore raw
Quoted 1 line · celtune-gmx

Does somebody know how to scale a Pentium 630 (3,0 GHz) to another freq. than 2,8 GHz or 3,0 GHz (Slackware10.2)?

Just to confirm that on my P4 630 running 2.6.15 with acpi_cpufreq.ko I also see just 2.8GHz and 3.0GHz in cpufreq-applet, I don't know what other speeds EIST could/should offer?

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw
Quoted 1 line · celtune-gmx

i think a cpu with EIST should be scaleable like a Pentium M (my 735 is with EIST scaleable from 600MHz(0,700V) to 1,7 GHz(1,276V))

Would I get better results with speedstep-ich instead of acpi-cpufreq?

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#6 lore raw
Quoted 1 line · cel

I dont know ,I used on the 630 the module for the Pentium4 (dont know the exact name now p4clockmod maybe) and ondemand and at idle i had 375MHz

Hmm, been trying to read up on EIST, seems that 14x (i.e. 2.8GHz) *is* the slowest clock speed P4 630 will throttle to, which kind of makes it a non-feature on a 3.0GHz CPU. What CPU feature does p4clockmod use to go lower than EIST apparently allows?

I'm running rawhide and don't see *p4*.ko did you have to build a custom kernel? I'd like to get idle consumption down on my box to quiet the fans even further ...

Quoted 1 line

and the vcore at about 1,6v (but thats not speedstep!)

lm_sensors reckons my Vcore is 1.35v to start with (perhaps I've got my VRM settings wrong in /etc/sensors.conf)