[SOLVED] New firmware, no more overclocking...

[harroxelas]

Hello all,

After running pacman -Suy today and rebooting my raspberry pi no longer overclocks. I've made no changes on my /boot/config.txt. Here's what was updated:

$this->bbcode_second_pass_code('', '
[2012-12-22 21:13] Running 'pacman -Syu'
[2012-12-22 21:13] synchronizing package lists
[2012-12-22 21:13] starting full system upgrade
[2012-12-22 21:17] upgraded freetype2 (2.4.10-1 -> 2.4.11-2)
[2012-12-22 21:17] upgraded gmp (5.0.5-1 -> 5.1.0-1)
[2012-12-22 21:17] upgraded krb5 (1.10.3-1 -> 1.11-1)
[2012-12-22 21:17] upgraded raspberrypi-firmware (20121206-1 -> 20121221-1)
[2012-12-22 21:17] upgraded libcec-rpi (2.0.4-1 -> 2.0.5-1)
[2012-12-22 21:17] upgraded libmysqlclient (5.5.28-1 -> 5.5.29-1)
[2012-12-22 21:18] upgraded linux-headers-raspberrypi (3.2.27-17 -> 3.2.27-18)
[2012-12-22 21:18] >>> Updating module dependencies. Please wait ...
[2012-12-22 21:18] upgraded linux-raspberrypi (3.2.27-17 -> 3.2.27-18)
[2012-12-22 21:18] upgraded sqlite (3.7.15-1 -> 3.7.15.1-1)
')

Here's my complete /boot/config.txt
$this->bbcode_second_pass_code('', '
# SETS GPU RAM AND RESOLUTION!

gpu_mem=128
hdmi_group=1
hdmi_mode=4
disable_overscan=1
overscan_left=37
overscan_right=37
overscan_top=23
overscan_bottom=23

#---------------------------------------------------------------------------
# Overclock
arm_freq=1000
core_freq=500
sdram_freq=500
over_voltage=6

#---------------------------------------------------------------------------

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

#uncomment to force turbo mode
#force_turbo=1

# for more options see http://elinux.org/RPi_config.txt
')

Can anyone help me out?

Thanks in advance.

[pepedog]

Hmm, I was sure I tested this, what does this say
$this->bbcode_second_pass_code('', 'cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor')
For me it's powersave. Got to be ondemand. Could have swore it was that.
Easiest way is to
$this->bbcode_second_pass_code('', 'echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
')
We switched to the same config as raspbian, reasoning is they get more config requests and probably keep up with this, then no one can say raspbian does this, arch doesn't. Also laziness involved.
I'm looking for an easy way to do on boot, maybe in cmdline.txt or sysctl.conf
Anyone else wat to experiment?

[harroxelas]

Hi pepedog,

$this->bbcode_second_pass_code('', '
[xxx@arch-rpi ~]$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
powersave
')

I should have suspected it was the scaling governor's fault.

pepedog, don't worry man. We're grateful to you enough already.

My temporary fix will be an alias to the echo "ondemand" command so I can easily run it at startup.

Thanks mate.

[pepedog]

The (correct) soloution was incredibly easy
$this->bbcode_second_pass_code('', 'echo "w /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor - - - - ondemand" > /etc/tmpfiles.d/scaling-govenor.conf')
No messing with rc.local

[harroxelas]

Cheers, pepedog! Worked like a charm. Thread mark as solved.

[flagos]

I was facing the same problem. After a fresh install, scaling_governor is not set to it's correct value and no parameters for overclocking are into /boot/config.txt.