Collectd-mod-cpufreq unavailable

zwolfp · January 30, 2021, 9:18pm

Hi, collectd-mod-cpufreq is unavailable for the latest snapshots rockchip armv8.
It was available in OpenWrt SNAPSHOT r15404 /LuCI Master (git-20.339.75073-e54708a) but after release was unavailable. Will be released again?

Cheers zWolf

zwolfp · February 27, 2021, 9:09am

Hi, is possible to recompile collectd-mod-cpufreq with R2S (rockchip armv8) support.

Thanks zWolf

hnyman · February 27, 2021, 9:15am

Collectd-mod-cpufreq only reads data from kernel debug file system. It has no knowledge about the chip itself.

hnyman · February 27, 2021, 9:18am

Note that the "last release" is 19.07.7 made from June 2019 code + some patches.

Which exact version you are talking about?

If support for some new device has been added to the development master (and will get into the next future release 21.02), it will likely not be backported to the stable ancient 19.07 branch.

You can use master test builds, the 21.02 test builds, or wait until the 21.02 release.

zwolfp · February 27, 2021, 12:02pm

Thanks a lot hnyman, R2S is on "Development Snapshot builds" and after OpenWrt SNAPSHOT r15404 /LuCI Master (git-20.339.75073-e54708a) the opgk is unavailable for installation.

zWolf

hnyman · February 27, 2021, 12:35pm

Are you talking about specifically just collectd-mod-cpufreq, or is opkg generally unable to install packages?

I guess that you might be suffering the symptoms caused by this commit in mid-December:

github.com/openwrt/openwrt

armvirt/64: change it to cortex-a53 instead of generic

committed 09:38PM - 14 Dec 20 UTC

BKPepe

+3 -2

Package architecture aarch64_generic [1] can be used just with three devices. On…e is NanoPI R2S and then there are two development boards from NXP. Let's change armvirt/64 to Cortex A53 (aarch64_cortex-a53) [2]. It has wider support by multiple devices like NanoPI Neo Plus2/Core2, ESPRESSObin, Pine64, and Raspberry Pi 2&3. While looking at ARMvirt/32 it has set CPU_TYPE and CPU_SUBTYPE to be arm_cortex-a15_neon-vfpv4 [3]. It has support to devices like Linksys EA8500 v1, Linksys EA7500 v1, Netgear D7800, Netgear R7500 and so on. Tested with: qemu-system-aarch64 -m 1024 -smp 2 -cpu cortex-a57 -M virt -nographic \ -kernel openwrt-armvirt-64-Image-initramfs Successfully compiled and booted. Here goes the output: root@OpenWrt:/# uname -a Linux OpenWrt 5.4.82 #0 SMP Sun Dec 13 12:52:10 2020 aarch64 GNU/Linux root@OpenWrt:/# cat /etc/openwrt_release DISTRIB_ID='OpenWrt' DISTRIB_RELEASE='SNAPSHOT' DISTRIB_REVISION='r15207-96fca0f807' DISTRIB_TARGET='armvirt/64' DISTRIB_ARCH='aarch64_cortex-a53' DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r15207-96fca0f807' DISTRIB_TAINTS='no-all' Also, change BOARDNAME to be the same as it is in armvirt/32. [1] https://openwrt.org/docs/techref/instructionset/aarch64_generic [2] https://openwrt.org/docs/techref/instructionset/aarch64_cortex-a53 [3] https://openwrt.org/docs/techref/instructionset/arm_cortex-a15_neon-vfpv4 Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>

I have no idea what is the correct fix for you, but if the package arch used in buildbot has changed for your device, possibly your current opkg download definitions point to wrong directories. You might need to sysupgrade to a current build.

zwolfp · February 27, 2021, 2:30pm

Thanks a lot hnyman, you find the problem

Immagine

zWolf