Slackware - ARM This forum is for the discussion of Slackware ARM. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
10-04-2022, 10:30 AM
|
#1
|
LQ Guru
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 5,057
|
Conky Working But No Core Sensors?
The latest version of Conky on Slackbuilds.org finally complied correctly and with a only slight modifications to ~/.conkyrc displays correctly with transparency and clear fonts (no ghosting) but I can't yet figure out how to display core usage. My x86 version uses
Code:
## EXCERPT from .conkyrc
${offset 380}${color magenta}${execi 1000 cat /proc/cpuinfo | grep 'model name' | cut -d " " -f "3-13" | sort -u}
${offset 350}${color red} CPU Frequency:${color white} $freq ${color yellow} Maximum:${color lightgreen} $freq_g
${offset 360}${color cyan}CPU:${color } $cpu% ${color steel blue}${execi 30 sensors |grep "CPU Temperature" |cut -d " " -f6}${hr 2}$color
${offset 380}${color slate grey}${cpugraph 20,200}
${offset 400}${color red}${exec sensors | grep 'Core 0' | awk '{print $0,$1,$2,$3}'| cut -c1-24}
${offset 410}${color red}${exec sensors | grep 'Core 1' | awk '{print $0,$1,$2,$3}'| cut -c1-24}
${offset 420}${color red}${exec sensors | grep 'Core 2' | awk '{print $0,$1,$2,$3}'| cut -c1-24}
${offset 430}${color red}${exec sensors | grep 'Core 3' | awk '{print $0,$1,$2,$3}'| cut -c1-24}
${offset 440}${color red}${exec sensors | grep 'Core 4' | awk '{print $0,$1,$2,$3}'| cut -c1-24}
${offset 450}${color red}${exec sensors | grep 'Core 5' | awk '{print $0,$1,$2,$3}'| cut -c1-24}
but goes blank as seen in the attached screenie
Note: sensors-detect fails to locate any sensors
Any suggestions?
Last edited by enorbet; 10-04-2022 at 10:32 AM.
|
|
|
10-04-2022, 12:14 PM
|
#2
|
LQ Veteran
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: antiX 23, MX 23
Posts: 7,279
|
Might help. Might not. If sensors-detect sees nothing. What is conky going to read?
Anyways. That statement made me think of hwinfo
https://www.hwinfo.com/forum/threads...lanation.5597/
|
|
|
10-04-2022, 12:22 PM
|
#3
|
Member
Registered: Jan 2021
Distribution: Sway WM running on Minimal Xubuntu 24.04 with SDDM as login manager
Posts: 127
Rep: 
|
Quote:
Originally Posted by enorbet
...
Note: sensors-detect fails to locate any sensors
Any suggestions?
|
What does just
show?
Also,
Code:
sensors | awk '/Core 0/ {print $1": "$3}'
works, eliminating grep and cut.
Last edited by hish2021; 10-04-2022 at 12:28 PM.
|
|
|
10-04-2022, 08:58 PM
|
#4
|
LQ Guru
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,766
|
Or you could try
You may have to run the command as root.
|
|
|
10-05-2022, 12:11 PM
|
#5
|
LQ Guru
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 5,057
Original Poster
|
First, thank you, rokytnji, for the reminder of hwinfo.
Quote:
Originally Posted by rokytnji
|
Obviously I don't expect Conky once directed to read "sensors" to display anything if no sensors are detected. My understanding is that sensors are chipsets that require kernel support like any other chipsets PLUS the precise name and associated command must be known. For example, seeking bandwidth data from eth0 when eth1 is the only active network device (not to mention the systemd en0 or whatever the hell that ensp nonsense was) is useless. Since I am a rank n00b at ARM I don't know and have yet to find what any sensor chipsets are called or how they are accessed.
I will play with hwinfo and see what that may reveal. Thanks again.
|
|
|
10-05-2022, 12:31 PM
|
#6
|
LQ Guru
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 5,057
Original Poster
|
Thank you hish2021.
I get
Code:
##bash sesnsors (as root)
##
cpu_thermal-virtual-0
Adapter: Virtual device
temp1: +30.1C (crit = +95.0C)
tcpm_source_psy_4_0022-i2c-4-22
Adapter: rk3x-i2c
in0: 0.00 V (min = +0.00V, max = =0.00V)
curr1: 0.00 A (max = 0.00 A)
gpu_thermal_virtual-0
Adapter: Virtual device
temp1: +39.4C (crit = 95.0C)
So far I don't know what to do with that but lookup support for "rk3x-i2c". I'm not having any luck with removing grep and cut yet, but it looks a neat trick so I will keep messing about.
|
|
|
10-05-2022, 12:41 PM
|
#7
|
LQ Guru
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 5,057
Original Poster
|
Thanks frankbell but I am very familiar with lm_sensors, just not on ARM devices yet, but I did run sensors-detect as root as noted. FWIW I actually once had a Next motherboard back when DEC Alpha CPUs were humiliating Intel 200 Pro CPUs and that was how I started researching good heatsinks AND fans to get the most out of a CPU. Next CPU had a radial heatsink with a reversed fan operation pulling air from the base and exhausting from above CPU the heat spreader. I filled several pages of a notebook on Cooling Solutions with that HS/Fan combo. I used a common thermal sensor with a Digital Multimeter back then. I didn't yet use Linux back then (I was TeamOS2) but it wasn't very long afterwards. Thanks.
Last edited by enorbet; 10-05-2022 at 12:42 PM.
|
|
|
10-05-2022, 04:35 PM
|
#8
|
SARPi Maintainer
Registered: Nov 2012
Distribution: Slackware ARM, AArch64
Posts: 1,067
|
Quote:
Originally Posted by enorbet
Since I am a rank n00b at ARM I don't know and have yet to find what any sensor chipsets are called or how they are accessed.
|
I don't have any Conky solutions for the X windows system on ARM architecture. What I do have is a rudimentary bash script, ran on command line, which outputs various system clock, and temperature sensor information. I've used it for testing, comparisons, curiosity, etc. mainly on the Raspberry Pi devices. View it here: https://sarpi.penthux.net/files/extra/cpu_status.sh
Hope its useful and/or gives you some idea(s).
|
|
|
10-06-2022, 05:40 AM
|
#9
|
Slackware Contributor
Registered: Apr 2008
Distribution: Slackware
Posts: 1,624
|
Quote:
Originally Posted by enorbet
T
but goes blank as seen in the attached screenie
Note: sensors-detect fails to locate any sensors
Any suggestions?
|
You're running one of the earliest Kernels which had limited hardware support. The latest Kernel configuration has wider support.
That said, on the latest Kernel:
Code:
root@bladswede:~/tmp/build-kernel_armv8/kernel-src/linux-5.19.14# sensors-detect
# sensors-detect version 3.6.0
# Kernel: 5.19.14-armv8 aarch64
# Cannot show processor info on aarch64 architecture.
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
modprobe: FATAL: Module cpuid not found in directory /lib/modules/5.19.14-armv8
Failed to load module cpuid.
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 16h thermal sensors... No
AMD Family 17h thermal sensors... No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Hygon Family 18h thermal sensors... No
Intel digital thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
Intel 5500/5520/X58 thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): ^C
root@bladswede:~/tmp/build-kernel_armv8/kernel-src/linux-5.19.14
I had a quick look at the sensor configuration in the Kernel and didn't see anything that was labeled as 'Rockchip' which wasn't selected.
There could be some missing support but most of the de-selected drivers don't look like they'd support hardware found on the RockPro64.
|
|
1 members found this post helpful.
|
All times are GMT -5. The time now is 06:23 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|