The time now is Fri 22 Feb 2019, 01:48
All times are UTC - 4 |
Page 1 of 4 [52 Posts] |
Goto page: 1, 2, 3, 4 Next |
Author |
Message |
tazoc

Joined: 11 Dec 2006 Posts: 1157 Location: Lower Columbia Basin WA US
|
Posted: Tue 26 Oct 2010, 19:08 Post subject:
wcpufreq CPU Frequency Scaling 1.1 Subject description: x2, x4, x8... core support; 4 up_threshold modes |
|
• Supports as many cores as kernel--typically 4 or 8 (thanks to Iguleder)
• Gleans available modules and governors from active kernel. (thanks to Iguleder)
• Displays current core speeds, scaling driver and governor
• For ondemand governor, select frequency range and from 4 up_threshold modes:
95% Powersave, less responsive
80% Default
50% Balanced, more responsive
30% Performance, very responsive
(My personal preference is 50% with AC power, 80% with battery)
• Remove driver option
• Feedback / status panels
• Help dialog
• New icons
• Works from root or 'fido' user in Wary
• Activates during boot up
• Displays $DISTRO_NAME in title bar
Displays active cpufreq driver module and scaling governor, even if loaded by script in /etc/init.d, other pets or in rc.local.
Tested on Slacko 5.4.0.5, Lucid 5.25, Wary 5.1.1.53, Fatdog 64 611 and Lighthouse 64 6.00
Changelog
2013.03.02 1.1 Bugfixed pinstall.sh for Woof build, thanks to 01micko.
gtkdialog icon tweak.
wcpufreq--1.0 130210
Precise bugfix: Expand driver search to new kernel module locations.
More info on the first panel. Support Woof in pinstall.sh.
wcpufreq-0.8 110910
Updated for Fatdog 64-520; account for scaling drivers built-in to kernel instead of compiled modules.
wcpufreq-0.7 110508
Activate at boot up from /etc/init.d/wcpufreq instead of script in ~/Startup.
Removed /home/spot and /etc/skel directories from wcpufreq.
Updated for fido user compatibility in Wary.
Woof/Wary: earlier versions of wcpufreq sometimes failed to activate on reboot--fixed.
wcpufreq-0.6 110424
Bugfix: Jim1911 and taca0 reported that prior scaling module was removed after reboot or second run of wcpufreq. Removed mperf module from driver selection dialog and improved detection of current driver by scanning /proc/modules.
wcpufreq-0.4 101027
Name changed to wcpufreq. Account for /etc/init.d/start_cpu_freq (recent Woof script) when detecting driver. Display current core speeds. up_threshold selection for ondemand governor. Suggest to avoid using p4-clockmod driver. Advise if no acpi or BIOS was released before 2007. Updated help dialogs.
pcpufreq-0.3 Initial release 101023
Credits
Based on pcpufreq 002 by Iguleder 2010-10-15.
Some content from Archlinux cpufrequtils Wiki.
A portion from cpu_freq GUI by Trio Tjandradjaja.
 |
Description |
CPU Frequency Scaling Tool 1.1
|

Download |
Filename |
wcpufreq-1.1-noarch.pet |
Filesize |
40.52 KB |
Downloaded |
963 Time(s) |
Description |
CPU Frequency Scaling Tool 0.8
|

Download |
Filename |
wcpufreq-0.8.pet |
Filesize |
38.96 KB |
Downloaded |
1090 Time(s) |
Description |
CPU Frequency Scaling on Luci-232
|

Download |
Filename |
luci-cpufreq-0.3-II.jpg |
Filesize |
148.62 KB |
Downloaded |
1495 Time(s) |
_________________ lhpup.org Lighthouse 64 6.02
Last edited by tazoc on Fri 08 Mar 2013, 16:49; edited 17 times in total
|
Back to top
|
|
 |
Jim1911
Joined: 19 May 2008 Posts: 2460 Location: Texas, USA
|
Posted: Wed 27 Oct 2010, 10:26 Post subject:
|
|
Quote: | On the off-chance this fails, (current driver is indicated 'unknown') the user is prompted to click 'Remove' in the GUI, reboot and driver setup via the GUI should work with no other intervention required. The help dialog also suggests checking /etc/rc.d/rc.local before rebooting, in case a driver was loaded there manually, e.g., 'modprobe acpi-cpufreq'. | Tried it on Lucid-232 & 233, on both, clicking "Remove" and rebooting did nothing. The original cpu scaling tool is still in control. Apparently, yours does not overwrite the original installation so it needs to be removed for yours to be used. It worked fine on LH 5.00 F.
Thanks,
Jim
|
Back to top
|
|
 |
tazoc

Joined: 11 Dec 2006 Posts: 1157 Location: Lower Columbia Basin WA US
|
Posted: Wed 27 Oct 2010, 12:15 Post subject:
|
|
Thanks for testing, Jim. Can you post your processor type (Menu | System | Hardinfo | Processor.) And the contents of any scripts in /root/Startup with 'cpu' in their name. It sounds like a scaling driver module is loading somewhere I haven't checked, or maybe our tool doesn't work with certain CPUs.
Thanks,
TazOC
_________________ lhpup.org Lighthouse 64 6.02
|
Back to top
|
|
 |
tazoc

Joined: 11 Dec 2006 Posts: 1157 Location: Lower Columbia Basin WA US
|
Posted: Wed 27 Oct 2010, 12:28 Post subject:
/etc/init.d/start_cpu_freq |
|
Jim,
Disregard my previous post. I found a script, /etc/init.d/start_cpu_freq dated 3 June 2010 in Woof-based pups that I hadn't seen before. I will update my pet to account for that and do some testing.
Thanks,
TazOC
[Edit] Some Woof history on CPU Scaling in Barry's Blog. Jemimah wrote that p4-clockmod is not desirable for at least EeePCs.
_________________ lhpup.org Lighthouse 64 6.02
|
Back to top
|
|
 |
tazoc

Joined: 11 Dec 2006 Posts: 1157 Location: Lower Columbia Basin WA US
|
Posted: Fri 29 Oct 2010, 12:23 Post subject:
wcpufreq-0.4 released |
|
wcpufreq-0.4 released
Should always detect current driver now, or work from scratch. Please test.
Name changed to wcpufreq.
Accounts for /etc/init.d/start_cpu_freq (recent Woof script) when detecting driver.
Display current core speeds.
'up_threshold' selection for ondemand governor.
Suggest to avoid using p4-clockmod driver.
Advise if no acpi or BIOS was released before 2007.
Updated help dialogs.
Thanks,
TazOC
_________________ lhpup.org Lighthouse 64 6.02
|
Back to top
|
|
 |
Jim1911
Joined: 19 May 2008 Posts: 2460 Location: Texas, USA
|
Posted: Fri 29 Oct 2010, 12:36 Post subject:
|
|
Hi TazOC,
Just happened to see this while testing the new Wary 0.9.4. Installed it and it seems to be working fine.
Incidently, printing with LibreOffice and other applications works fine on this Wary.
Cheers,
Jim
|
Back to top
|
|
 |
tazoc

Joined: 11 Dec 2006 Posts: 1157 Location: Lower Columbia Basin WA US
|
Posted: Fri 29 Oct 2010, 12:56 Post subject:
|
|
Hi Jim,
Thanks for testing. You have 8 cores? That is sweet!
Please PM me preferred user/passwd if you'd like to post the LibreOffice SFS at lhpup.org; or if its already up somewhere.
Thanks,
TazOC
_________________ lhpup.org Lighthouse 64 6.02
|
Back to top
|
|
 |
Jim1911
Joined: 19 May 2008 Posts: 2460 Location: Texas, USA
|
Posted: Fri 29 Oct 2010, 16:29 Post subject:
|
|
tazoc wrote: | Thanks for testing. You have 8 cores? That is sweet!
| Yes, I have 8 cores, however on Luci 233, and LHP 5.00F, only 4 show up, unlike all 8 that showed up in Wary and dpup zen 4.
Cheers,
Jim
PS: Note the difference in size between the attached picts. The smaller one was made with radky's new PupSnap-1.0 which he should be releasing soon. It allows you to snap pictures of individual windows or just segments of a desktop.
Description |
|
Filesize |
43.09 KB |
Viewed |
2832 Time(s) |

|
|
Back to top
|
|
 |
tazoc

Joined: 11 Dec 2006 Posts: 1157 Location: Lower Columbia Basin WA US
|
Posted: Sat 30 Oct 2010, 11:52 Post subject:
Maybe some kernels detect only 4 cores? |
|
Jim1911 wrote: | Yes, I have 8 cores, however on Luci 233, and LHP 5.00F, only 4 show up, unlike all 8 that showed up in Wary and dpup zen 4. | Hmm, I'm curious. Can you post the o/p of Code: | cat /var/log/messages|grep cores | in Luci 233 or Lighthouse? If the kernel detects 8 cores, then try Code: | cat /proc/cpuinfo|grep MHz | Thanks,
TazOC
_________________ lhpup.org Lighthouse 64 6.02
|
Back to top
|
|
 |
Jim1911
Joined: 19 May 2008 Posts: 2460 Location: Texas, USA
|
Posted: Sun 31 Oct 2010, 13:08 Post subject:
|
|
Hi TazOC,
Sorry that it's taken so long to respond. This is output from Lighthouse 5.00 F, not good.
Code: | bash-4.1# cat /var/log/messages|grep cores
<root> ~
bash-4.1#
<root> ~
bash-4.1# cat /proc/cpuinfo|grep MHz
cpu MHz : 1600.000
cpu MHz : 1600.000
cpu MHz : 1600.000
cpu MHz : 1600.000
<root> ~
bash-4.1#
| Hope this helps,
Jim
|
Back to top
|
|
 |
Iguleder

Joined: 11 Aug 2009 Posts: 2031 Location: Israel, somewhere in the beautiful desert
|
Posted: Sun 31 Oct 2010, 13:16 Post subject:
|
|
The kernel has no Hyperthreading support, that means you see only half of the number of cores. I know the Lupu kernel (which is also the Lighthouse kernel) has no Hyperthreading, that's one of the reasons why I chose to go for our own kernel in Squeeze
That kernel also lacks rfkill and other important things ... but that's just my opinion
_________________ My homepage
My GitHub profile
Last edited by Iguleder on Sun 31 Oct 2010, 13:35; edited 1 time in total
|
Back to top
|
|
 |
tazoc

Joined: 11 Dec 2006 Posts: 1157 Location: Lower Columbia Basin WA US
|
Posted: Sun 31 Oct 2010, 13:26 Post subject:
|
|
Thanks, Jim. Yeah, Iguleder's on to something there. I was just going to say the kernel in LHP 2.6.33.2 (from Quirky 1.2 I think) probably wasn't compiled to support 8 cores.
This should clarify: Code: | cat /var/log/messages|grep processors | I have 2 cores and that gives this o/p: Quote: | # cat /var/log/messages|grep processors
Nov 1 15:55:30 Mariner user.info kernel: Total of 2 processors activated (10844.22 BogoMIPS).
Nov 1 15:55:47 Mariner user.info kernel: powernow-k8: Found 1 AMD Athlon(tm) 7750 Dual-Core Processor processors (2 cpu cores) (version 2.20.00) | I'm thinking about moving toward the next Squeeze or FatDog64 for a future release, if it can support 8 cores.-TazOC
_________________ lhpup.org Lighthouse 64 6.02
|
Back to top
|
|
 |
Jim1911
Joined: 19 May 2008 Posts: 2460 Location: Texas, USA
|
Posted: Sun 31 Oct 2010, 13:33 Post subject:
|
|
tazoc wrote: | I'm thinking about moving toward the next Squeeze or FatDog64 for a future release, if it can support 8 cores.-TazOC | I'll try this code on FatDog64 and post results here.
Code: | # cat /var/log/messages|grep cores
# cat /proc/cpuinfo|grep MHz
cpu MHz : 2672.756
cpu MHz : 2672.756
cpu MHz : 2672.756
cpu MHz : 2672.756
cpu MHz : 2672.756
cpu MHz : 2672.756
cpu MHz : 2672.756
cpu MHz : 2672.756
# |
Last edited by Jim1911 on Sun 31 Oct 2010, 13:42; edited 1 time in total
|
Back to top
|
|
 |
tazoc

Joined: 11 Dec 2006 Posts: 1157 Location: Lower Columbia Basin WA US
|
Posted: Sun 31 Oct 2010, 13:39 Post subject:
LHP kernel only supports 4 cores |
|
I found these entries in Lighthouse 5.00 F
/etc/modules/DOTconfig-K2.6.33.2-5APR2010-SMP-TICKLESS:
CONFIG_X86_HT=y
CONFIG_NR_CPUS=4
[Edit:]
FD64-500: /etc/modules/2.6.34.config
CONFIG_X86_HT=y
CONFIG_NR_CPUS=8
-TazOC
_________________ lhpup.org Lighthouse 64 6.02
Last edited by tazoc on Sun 31 Oct 2010, 13:45; edited 1 time in total
|
Back to top
|
|
 |
Iguleder

Joined: 11 Aug 2009 Posts: 2031 Location: Israel, somewhere in the beautiful desert
|
Posted: Sun 31 Oct 2010, 13:42 Post subject:
|
|
Look at the kernel configuration. Here's an example from the latest Squeeze kernel. It has SMP, Hyperthreading and support for up to 8 cores, since most people don't need more than that and also because more than 8 cores need BIGSMP which results in extra size, while each core doesn't add much when it's up to 8 cores.
That's SMP.
Quote: | CONFIG_SCHED_SMT=y |
That's Hyperthreading.
That's the maximum number of cores supported by the kernel.
Quote: | # CONFIG_X86_BIGSMP is not set |
This is something you need if you want support for more than 8 cores (a CONFIG_NR_CPUS that is higher than .
This kernel sees 2 cores on my Core 2 Duo (2 physical cores) and 2 cores on my Atom (one physical, but it has Hyperthreading).
EDIT: tazoc, do you want me to upload the kernel PET I made so you can replace the Lighthouse kernel (someone wrote a guide for that), to make development easier?
_________________ My homepage
My GitHub profile
|
Back to top
|
|
 |
|
Page 1 of 4 [52 Posts] |
Goto page: 1, 2, 3, 4 Next |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|