[FS#4075] Cpufreq is missing on kirkwood target, so the cpu is stuck at lowest frequency

OpenWrt Bugs openwrt-bugs at lists.openwrt.org
Sun Oct 10 00:38:59 PDT 2021


A new Flyspray task has been opened.  Details are below. 

User who did this - Edoardo Liverani (EdoaLive) 

Attached to Project - OpenWrt/LEDE Project
Summary - Cpufreq is missing on kirkwood target, so the cpu is stuck at lowest frequency
Task Type - Bug Report
Category - Kernel
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - High
Priority - Very Low
Reported Version - openwrt-21.02
Due in Version - Undecided
Due Date - Undecided
Details - Hello, I installed openwrt on a Zyxel NSA-310 device. Everything seems good but when I went to test the performance it was not so good.
So I noticed that the cpu frequency is stuck on 200MHz and cpufreq is missing (also can't find it as a kmod package).

I am running on original u-boot because of a bad block and the wiki suggested not to flash it. Maybe openwrt's u-boot has a workaround on this or there is some setting to apply on boot?

BTW I think the wiki does not include a safer, less invasive method as this device can boot entirely from usb without flashing anything, but to do so you need to have a kernel/initramfs w/usbstorage included.

I might try to compile openwrt from sources to include cpufreq. Should I then submit a pull request or a patch?

More information can be found at the following URL:

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.

More information about the openwrt-bugs mailing list