Puppy Linux Discussion Forum

[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.

[playdayz]

http://www.murga-linux.com/puppy/viewtopic.php?p=682210#682210
Hello again tazoc. wcpufreq does not seem to be working correctly in Lxpup. Best, Larry

[BarryK]

linuxcbon posted a bug report for wcpufreq, in Precise Puppy:
http://murga-linux.com/puppy/viewtopic.php?t=82092&start=255

I fixed it, bumped the version to 0.8.1 (40K):
http://distro.ibiblio.org/quirky/pet_packages-noarch/wcpufreq-0.8.1.pet

[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

[tazoc]

1.1 Bugfixed pinstall.sh for Woof build, thanks to 01micko.
gtkdialog icon tweak.

-TaZoC

[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?

[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.

[sheldonisaac]

[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

[ally]

lenovo x230 running xenialpup64, unable to set scaling using either 0.8x or 1.2

[Marv]

[ally]

hi marv

yes to Intel_Pstate, set to performance and unable to modify I will try the kernel switch and report back



edit: kernel parameter added to menu.1st, now able to run cpu scaling...nice!

thank you

[Marv]

Great.

Maybe we can test for the Intel_Pstate governor in wcpufreq 1.2 and put a note in to that effect.

I cobbled in an explicit intel_pstate warning to 1.2. Tain't especially pretty yet but I think it is fairly clear. I've tested it in Battleshooters XFCE_XenialPup64 r2 by toggling the kernel parameter and both cases seem ok. I also added support for the cpu current frequency when in intel_pstate. It writes to a different file in the sysfs. I'll attach the script labelled as 1.2a and a diff from 1.2 below. Try it and pretty it up please. Both files are true gzips.

Update: 1.2b does two things. One is (as 1.2a) to support the reading of current speeds from the intel_pstate driver and the other is to clean up a bit (I think) the warning/instructions wrt that driver. I'll replace the 1.2a with it below and pull the diff since there were 0 downloads.

Edit on 5 December 2017: Based on comments and kernel changes 4.13 support pulled and only intel_pstate support added.

[Anniekin]

Hi

[Anniekin]

I'm stupid