matteobp Posted January 25, 2017 Share Posted January 25, 2017 Hi all. I have a Banana Pi M1+ and I want to use it as a NAS using a SATA HDD (1TB). I read this article http://linux-sunxi.org/Cpufreq#Performance.2Ffunctionality_impacts and I want to change the scaling_max_freq. I installed the "Armbian_5.20_Bananapi_Debian_jessie_4.7.3" image. But the maximum frequencies available is 960000. I tried to compile the kernel by myself, changing the file sources\linux-vanilla\v4.9.5\arch\arm\boot\dts\sun7i-a20.dtsi as suggested in other posts. cpu0: cpu@0 { compatible = "arm,cortex-a7"; device_type = "cpu"; reg = <0>; clocks = <&cpu>; clock-latency = <244144>; /* 8 32k periods */ operating-points = < /* kHz uV */ 1200000 1500000 1152000 1500000 1104000 1450000 1056000 1450000 1008000 1450000 960000 1400000 912000 1400000 864000 1300000 720000 1200000 528000 1100000 312000 1000000 144000 1000000 >; I changed also this row in compile.sh file FORCE_CHECKOUT="no" # ignore manual changes to source I verified that the file sources\linux-vanilla\v4.9.5\arch\arm\boot\dts\sun7i-a20.dtsi wasn't changed at the end of the compilation process. This is output of the compialtion: linux-headers-next-sunxi_5.24_armhf.deb linux-image-next-sunxi_5.24_armhf.deb linux-firmware-image-next-sunxi_5.24_armhf.deb linux-u-boot-next-bananapipro_5.24_armhf.deb linux-dtb-next-sunxi_5.24_armhf.deb I copied them on the Banana Pi and installed them with dpkg -i *.deb After rebooting, this is the output of the command "uname -a" Linux bananapi 4.9.5-sunxi #4 SMP Tue Jan 24 11:33:41 CET 2017 armv7l GNU/Linux and this is my "/etc/default/cpufrequtils" ENABLE=true MIN_SPEED=480000 MAX_SPEED=1200000 GOVERNOR=ondemand but the output of the command "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies" is still the same 144000 312000 528000 720000 864000 912000 960000 What is wrong? Can someone help me? Thanks in advance. P.S. During kernel compilation I changed the default configuration to choose the "ondemand" governor as default governor rather than "schedutil". This change was successfully applied after reboot. Link to comment Share on other sites More sharing options...
Recommended Posts