Recent changes to c7rpiMyth_Pi2_overclock

c7rpiMyth_Pi2_overclock modified by Kelsie Flynn

Kelsie Flynn — Thu, 31 Jan 2019 21:24:38 -0000

--- v28
+++ v29
@@ -2,14 +2,16 @@
 Only tested on a Pi2

 config.txt 
-and the kernel governer(s) must be applied?
+and the kernel governer(s) must be applied
+we are working with this :
 (bcm2835-cpufreq: min=600000 max=1000000)

 TESTING, Unconfirmed.
 It appears you can apply just the cpu "performance" governor without config.txt, but to get the 1GHz min freq, you may need
 the config.txt. It appears to me that without the config.txt the min gov will be read only, /sys/devices/system/cpu/cpufreq/policy0/scaling_min_freq

-The previous config.txt method by itself was not changing my cpuinfo as intended, I found the kernel govnr was enabled, though we dont have the actual "cpupower" binary yet. So we can just set our values manually as needed till we get the utility and use /etc/default, etc. If we ever get that. It appears to be part of the kernel-tools package on x86_64 but not here so far in the rpi.
+The previous config.txt method by itself was not changing my cpuinfo as intended, I found the kernel govnr was enabled, though on arm we dont have the actual "cpupower" binary yet.
+So we can just set our values manually as needed till we get the utility and use /etc/default, etc. If we ever get that. It appears to be part of the kernel-tools package on x86_64 but not here so far in the rpi.

@@ -40,7 +42,7 @@

-* a better long term method will be to use cpupower or create a dedicated unit file
+* a better long term method will be to adapt for use cpupower or just create a dedicated unit file with scripts

 References:

c7rpiMyth_Pi2_overclock modified by Kelsie Flynn

Kelsie Flynn — Thu, 31 Jan 2019 20:58:10 -0000

--- v27
+++ v28
@@ -45,3 +45,5 @@
 References:

 https://www.raspberrypi.org/documentation/configuration/config-txt/overclocking.md
+
+https://github.com/raspberrypi/linux/blob/rpi-4.1.y/Documentation/cpu-freq/governors.txt

c7rpiMyth_Pi2_overclock modified by Kelsie Flynn

Kelsie Flynn — Thu, 31 Jan 2019 20:56:04 -0000

--- v26
+++ v27
@@ -41,18 +41,7 @@

 * a better long term method will be to use cpupower or create a dedicated unit file
-or 

-*TESTING WITH BCM2835_CPUFREQ
-for x86_64 arch says to create a udev static file
+References:

-https://wiki.archlinux.org/index.php/CPU_frequency_scaling
-
-
-    Make changes permanent
-    To have the desired scaling enabled at boot, kernel module options and systemd#Temporary files are regular methods. However, in some cases there might be race conditions, as noted in systemd#Temporary files. udev is doing better.
-
-    For example, to set the scaling governor of the CPU core 0 to performance while the scaling driver is acpi_cpufreq, create the following udev rule:
-
-    /etc/udev/rules.d/50-scaling-governor.rules
-    SUBSYSTEM=="module", ACTION=="add", KERNEL=="acpi_cpufreq", RUN+=" /bin/sh -c ' echo performance > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor ' "
+https://www.raspberrypi.org/documentation/configuration/config-txt/overclocking.md

c7rpiMyth_Pi2_overclock modified by Kelsie Flynn

Kelsie Flynn — Thu, 31 Jan 2019 20:45:15 -0000

--- v25
+++ v26
@@ -41,7 +41,11 @@

 * a better long term method will be to use cpupower or create a dedicated unit file
-or arch says to create a udev static file
+or 
+
+*TESTING WITH BCM2835_CPUFREQ
+for x86_64 arch says to create a udev static file
+
 https://wiki.archlinux.org/index.php/CPU_frequency_scaling

c7rpiMyth_Pi2_overclock modified by Kelsie Flynn

Kelsie Flynn — Thu, 31 Jan 2019 20:40:13 -0000

--- v24
+++ v25
@@ -40,4 +40,15 @@

-* a better long term method will be to use cpupower or create a dedicated unit file if cpupower not avail on arm
+* a better long term method will be to use cpupower or create a dedicated unit file
+or arch says to create a udev static file
+https://wiki.archlinux.org/index.php/CPU_frequency_scaling
+
+
+    Make changes permanent
+    To have the desired scaling enabled at boot, kernel module options and systemd#Temporary files are regular methods. However, in some cases there might be race conditions, as noted in systemd#Temporary files. udev is doing better.
+
+    For example, to set the scaling governor of the CPU core 0 to performance while the scaling driver is acpi_cpufreq, create the following udev rule:
+
+    /etc/udev/rules.d/50-scaling-governor.rules
+    SUBSYSTEM=="module", ACTION=="add", KERNEL=="acpi_cpufreq", RUN+=" /bin/sh -c ' echo performance > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor ' "

c7rpiMyth_Pi2_overclock modified by Kelsie Flynn

Kelsie Flynn — Thu, 31 Jan 2019 20:34:22 -0000

--- v23
+++ v24
@@ -3,6 +3,7 @@

 config.txt 
 and the kernel governer(s) must be applied?
+(bcm2835-cpufreq: min=600000 max=1000000)

 TESTING, Unconfirmed.
 It appears you can apply just the cpu "performance" governor without config.txt, but to get the 1GHz min freq, you may need

c7rpiMyth_Pi2_overclock modified by Kelsie Flynn

Kelsie Flynn — Thu, 31 Jan 2019 20:32:48 -0000

--- v22
+++ v23
@@ -39,3 +39,4 @@

+* a better long term method will be to use cpupower or create a dedicated unit file if cpupower not avail on arm

c7rpiMyth_Pi2_overclock modified by Kelsie Flynn

Kelsie Flynn — Thu, 31 Jan 2019 20:32:00 -0000

--- v21
+++ v22
@@ -1,4 +1,5 @@
 TESTING UPDATED METHOD(s):
+Only tested on a Pi2

 config.txt 
 and the kernel governer(s) must be applied?
@@ -9,9 +10,9 @@

 The previous config.txt method by itself was not changing my cpuinfo as intended, I found the kernel govnr was enabled, though we dont have the actual "cpupower" binary yet. So we can just set our values manually as needed till we get the utility and use /etc/default, etc. If we ever get that. It appears to be part of the kernel-tools package on x86_64 but not here so far in the rpi.

-Only tested on a Pi2

-*You need a config.txt in place with the overclock settings applied as well. One of these methods will not work alone, you must use both. If you uncomment the "double commented" stanza's in the config.txt, then this will work with the settings below.
+
+*You need a config.txt in place with the overclock settings applied as well. One of these methods may not work alone, you may need use both. If you uncomment the "double commented" stanza's in the config.txt, then this will work with the settings below.

 *TEMP, rc.local starts unreliably timed after everything else. THis needs a bettter option.

c7rpiMyth_Pi2_overclock modified by Kelsie Flynn

Kelsie Flynn — Thu, 31 Jan 2019 20:30:54 -0000

--- v20
+++ v21
@@ -14,6 +14,9 @@
 *You need a config.txt in place with the overclock settings applied as well. One of these methods will not work alone, you must use both. If you uncomment the "double commented" stanza's in the config.txt, then this will work with the settings below.

 *TEMP, rc.local starts unreliably timed after everything else. THis needs a bettter option.
+
+If it wont start/restart properly, Just exec it manually with , sh /etc/rc.local
+

 cat >> /etc/rc.local << EOF

c7rpiMyth_Pi2_overclock modified by Kelsie Flynn

Kelsie Flynn — Thu, 31 Jan 2019 20:29:45 -0000

--- v19
+++ v20
@@ -4,7 +4,8 @@
 and the kernel governer(s) must be applied?

 TESTING, Unconfirmed.
-
+It appears you can apply just the cpu "performance" governor without config.txt, but to get the 1GHz min freq, you may need
+the config.txt. It appears to me that without the config.txt the min gov will be read only, /sys/devices/system/cpu/cpufreq/policy0/scaling_min_freq

 The previous config.txt method by itself was not changing my cpuinfo as intended, I found the kernel govnr was enabled, though we dont have the actual "cpupower" binary yet. So we can just set our values manually as needed till we get the utility and use /etc/default, etc. If we ever get that. It appears to be part of the kernel-tools package on x86_64 but not here so far in the rpi.