Page 2 of 3
Posted: Fri 08 Apr 2011, 03:32
by taca0
Problems :
I have Via C3 and I select longhaul mod and its accepted I finish the selection but when I boot the computer again the cpufreq scaling not activate again.
What its the problem??
Thanks!
Posted: Fri 08 Apr 2011, 04:04
by tazoc
Hi taca0,
The script at
/root/Startup/cpu-frequency-scaling.sh should activate scaling when X starts. If not, please let us know which Puppy/puplet and version you have. I don't have a Via C3 to test with but I can at least see if wcpufreq works with the Pup you are using.
Opening the above script with a text editor should look similar to this, but specific to your hardware:
Code: Select all
#!/bin/busybox ash
## To activate at bootup copy rest of code ##
## below this comment to /etc/rc.d/rc.local ##
modprobe powernow-k8
modprobe cpufreq-ondemand
cd /sys/devices/system/cpu
for i in `ls -d1 cpu[0-9]*`; do
echo ondemand > $i/cpufreq/scaling_governor
echo 1350000 > $i/cpufreq/scaling_min_freq
echo 2700000 > $i/cpufreq/scaling_max_freq
done
Copy and paste the lines after the ## comments (from your cpu-frequency-scaling.sh) into a terminal and if there appear to be errors, please post the o/p.
Thanks,
TazOC
Posted: Sun 10 Apr 2011, 05:17
by taca0
tazoc:
I have test in wary 511 and lupu525 and both write on the root/Startup/cpu-frequency-scaling.sh this >
#!/bin/busybox ash
echo 50 > cpufreq/ondemand/up_threshold
So its activate in the first time but when reboot , nothing...
Maybe I should do it manual like you shows.
I just inform , maybe its a problem with my hardware or the kernel (I use the 3.6.33.git7 from Barry)
Thanks!
Bug confirmed, will work on it
Posted: Mon 11 Apr 2011, 02:11
by tazoc
taca0,
Thanks for the info. My last post was missing the line you have;
Code: Select all
echo 50 > cpufreq/ondemand/up_threshold
but you'll need the modprobes for your hardware as well. I'm not familiar with the kernel you are using, but you might try
Code: Select all
modprobe acpi-cpufreq
modprobe cpufreq-ondemand
cd /sys/devices/system/cpu
for i in `ls -d1 cpu[0-9]*`; do
echo ondemand > $i/cpufreq/scaling_governor
done
echo 50 > cpufreq/ondemand/up_threshold
I've been testing wcpufreq in Fatdog64 and have a similar problem where it works the first time, but later running wcpufreq reports scaling driver 'mperf' instead of my selection, powernow-k8. So for now I'm manually editing
/root/cpu-frequency-scaling.sh.
I will work on wcpufreq soon and post an update if I can squash these bugs.
-TazOC
Wcpufreq-0.6 released
Posted: Fri 06 May 2011, 21:11
by tazoc
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.
-TazOC
wcpufreq-0.7 released
Posted: Mon 09 May 2011, 00:46
by tazoc
wcpufreq-0.7 updates
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 5.1.1.53
Woof/Wary: earlier versions of wcpufreq sometimes failed to activate on reboot--fixed.
-TazOC
Posted: Thu 12 May 2011, 18:36
by technosaurus
Edit, oops too many alt tabs
meant to post these really light tray apps that use xcb
http://sourceforge.net/projects/wmc2d/
http://sourceforge.net/projects/wmcpumon/
some pups may need to upgrade xcb and/or xcb-utils for it to compile though ... maybe for the next pup series though
(he also has an xcb rewrite of jwm that looks extremely promising)
Posted: Sun 17 Jul 2011, 16:26
by playdayz
tazoc, Any reason I should not use version 0.7 in Lucid 5.2.6? Thanks.
Posted: Mon 18 Jul 2011, 17:25
by tazoc
HI playdayz,
Not that I know of. Have not received any bug reports on v. 0.7 so it should be fine.
-TazOC
wcpufreq-0.8 updated for Fatdog 64-520
Posted: Wed 14 Sep 2011, 03:49
by tazoc
wcpufreq-0.8
Updated for Fatdog 64-520 support; account for scaling drivers built-in to kernel instead of compiled modules.
-TaZoC
Posted: Wed 12 Oct 2011, 16:43
by playdayz
Hey tazoc, I am about to add wcpufreq 0.8 to Instant Update 002 for Lucid 5.2.8. Please let me know if you see any issues with that. I had already added it to Three-Headed Dog with no apparent problems. Thank you.
Posted: Sun 03 Feb 2013, 18:31
by playdayz
http://www.murga-linux.com/puppy/viewto ... 210#682210
Hello again tazoc. wcpufreq does not seem to be working correctly in Lxpup. Best, Larry
Posted: Fri 08 Feb 2013, 01:28
by BarryK
linuxcbon posted a bug report for wcpufreq, in Precise Puppy:
http://murga-linux.com/puppy/viewtopic. ... &start=255
I fixed it, bumped the version to 0.8.1 (40K):
http://distro.ibiblio.org/quirky/pet_pa ... -0.8.1.pet
wcpufreq-1.0 released
Posted: Sun 10 Feb 2013, 18:22
by tazoc
Hi Playdayz and BarryK,
Thank you for your feedback. New Pet is updated for recent kernels.
Changelog
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.
-TaZoC
wcpufreq CPU Frequency Scaling 1.1 released
Posted: Fri 08 Mar 2013, 20:54
by tazoc
1.1 Bugfixed pinstall.sh for Woof build, thanks to 01micko.
gtkdialog icon tweak.
-TaZoC
wcpufreq in wary 5.5 won't let me change minimum cpu freq
Posted: Sat 25 Jan 2014, 05:25
by sindi
DELL D600 max cpu freq 1.6GHz min 600Mhz which because of a broken wire on the board runs at minimum all the time unless you use acpi-cpufreq to set it to min 1.6GHz. In puppy 4.1.2 and 4.3.1 and 4.3.2 I can modprobe acpi-cpufreq and echo the correct minimum frequency to a file created by acpi-cpufreq (which is what the scripts do) and it changes the minimum to 1.6GHz and the computer runs at at full speed all the time. (No point in running it slowly since the same broken wire keeps it from charging the battery - Dell's way of forcing you to buy their OEM power supply with the matching wire). In wary 5.5 with wcpufreq the file does not change value - I cannot change either min or max frequencies using the wizard (it tells me I have a fixed frequency 600MHz) or with echo 1600 > /..... (on a different computer right now, don't have the file).
The BIOS is somehow involved. Maybe wcpufreq consults it and refuses to go above 600MHz?
What do I need to replace to get cpufreq working as in 4.3.1?
Posted: Fri 22 Sep 2017, 08:09
by peebee
CPU frequency determination
changes in kernel 4.13
The attached .pets include
a fix developed by @radky for PupSysInfo.
The
woof-ce noarch-official repo currently has version 0.8.1 and has been updated to 0.8.2
Version 1.1 never seems to have got out into the wider world - version 1.2 is attached for testing and possible inclusion in the woof-ce repo and builds.
version 1.2 question
Posted: Fri 22 Sep 2017, 13:34
by sheldonisaac
peebee or others, will this work correctly with tahr 6.0.6? I usually use that 32-bit tahr.
Version 1.1 never seems to have got out into the wider world - version 1.2 is attached for testing and possible inclusion in the woof-ce repo and builds.
I installed the 1.2 no-arch. Its help says 1.1.
Seems to work; how could I tell whether it's working correctly?
Thanks a lot,
Sheldon
Posted: Fri 22 Sep 2017, 15:02
by Marv
Installed the 1.2 no-arch. As sheldonisaac said its help says 1.1.
Switched governors back and forth and checked CPU speeds with my cpuwatch script, wcpufreq itself, and PupSysInfo while running glxgears on my i5 based laptop. Operation seems normal, as did the patched 0.8.1. It would be nice to get a test by someone with LOTS of cores.
@sheldonisaac The changes in the patched versions just (in bash) test for the kernel version and read the cpu speed from a different location if a kernel newer than 4.13.x is detected. Since the information at both those locations is kernel written it should work on all the pups that the unpatched versions worked on. All
Posted: Fri 22 Sep 2017, 16:32
by ally
lenovo x230 running xenialpup64, unable to set scaling using either 0.8x or 1.2
