Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Temperature doesn't support tempN properly #17

Closed
divansantana opened this issue May 28, 2014 · 8 comments
Closed

Temperature doesn't support tempN properly #17

divansantana opened this issue May 28, 2014 · 8 comments
Assignees
Labels

Comments

@divansantana
Copy link

Hi,

Firstly this is awesome so thank you.

Secondly, I think the temperature component is not working correctly.
By default it's set to:
[temp: $temp0°C]

However on my system I need it set to temp1 as temp0 doesn't exist:

# /usr/bin/sensors -u    
asus-isa-0000
Adapter: ISA adapter
temp1:
  temp1_input: 48.000

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:
  temp1_input: 50.000
  temp1_max: 100.000
  temp1_crit: 100.000
  temp1_crit_alarm: 0.000
Core 0:
  temp2_input: 50.000
  temp2_max: 100.000
  temp2_crit: 100.000
  temp2_crit_alarm: 0.000
Core 1:
  temp3_input: 48.000
  temp3_max: 100.000
  temp3_crit: 100.000
  temp3_crit_alarm: 0.000

When I set it to

[temp: $temp1°C]

It literally displays

[temp: $temp1°C]

Instead of converting $temp1 to a variable as expected.

@arcan1s
Copy link
Owner

arcan1s commented May 28, 2014

No, it is not. Numbering of elements of temperature, hdd usage, hdd speed, hdd temperature refers to elements from second tab (advanced settings). You should add item to the required listWidget (temperature device in your case) first. And the first element in the listWidget will be $temp0.

In my case (see the attached screenshot) Physical_id_0 is $temp0 and temp1 is $temp1.
screenshot
And here is my sensors -u:

thinkpad-isa-0000
Adapter: ISA adapter
fan1:
  fan1_input: 0.000

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:
  temp1_input: 57.000
  temp1_max: 86.000
  temp1_crit: 100.000
  temp1_crit_alarm: 0.000
Core 0:
  temp2_input: 57.000
  temp2_max: 86.000
  temp2_crit: 100.000
  temp2_crit_alarm: 0.000
Core 1:
  temp3_input: 57.000
  temp3_max: 86.000
  temp3_crit: 100.000
  temp3_crit_alarm: 0.000

@arcan1s arcan1s self-assigned this May 28, 2014
@arcan1s
Copy link
Owner

arcan1s commented May 28, 2014

hm, I think it should be added to the README

@divansantana
Copy link
Author

Oh dear, it works just fine as per your comment.
Thanks for the feedback and apologies.
I looked (too) briefly on the site and should have definitely looked into it more before reporting an issue.
Github makes things a little too easy to complain ;)

@arcan1s
Copy link
Owner

arcan1s commented May 28, 2014

Don't worry about it. Some things in my applications really are not obvious =) And that's why there is a special label for issues (question).

@danieledipompeo
Copy link

Hi,
First, I have finally found the best status bar :) thanks.

I cannot show the $temp0 value. I'm using the awesome widget on KUbuntu 20.04, and the GUI is quite different from the example above.

Can you help me to configure the status bar?

here below my sensors -u

Adapter: PCI adapter
vddgfx:
  in0_input: 0.725
fan1:
  fan1_input: 814.000
  fan1_min: 0.000
  fan1_max: 3200.000
edge:
  temp1_input: 35.000
  temp1_crit: 94.000
  temp1_crit_hyst: -273.150
power1:
  power1_average: 31.160
  power1_cap: 155.000

acpitz-acpi-0
Adapter: ACPI interface
temp1:
  temp1_input: 6.800
  temp1_crit: 18.800
temp2:
  temp2_input: 27.800
  temp2_crit: 119.000
temp3:
  temp3_input: 29.800
  temp3_crit: 119.000

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:
  temp1_input: 37.000
  temp1_max: 82.000
  temp1_crit: 100.000
  temp1_crit_alarm: 0.000
Core 0:
  temp2_input: 35.000
  temp2_max: 82.000
  temp2_crit: 100.000
  temp2_crit_alarm: 0.000
Core 1:
  temp3_input: 37.000
  temp3_max: 82.000
  temp3_crit: 100.000
  temp3_crit_alarm: 0.000
Core 2:
  temp4_input: 35.000
  temp4_max: 82.000
  temp4_crit: 100.000
  temp4_crit_alarm: 0.000
Core 3:
  temp5_input: 36.000
  temp5_max: 82.000
  temp5_crit: 100.000
  temp5_crit_alarm: 0.000
Core 4:
  temp6_input: 36.000
  temp6_max: 82.000
  temp6_crit: 100.000
  temp6_crit_alarm: 0.000
Core 5:
  temp7_input: 35.000
  temp7_max: 82.000
  temp7_crit: 100.000
  temp7_crit_alarm: 0.000

Here below the advanced tab, where I cannot find what you have suggested.

image

@arcan1s
Copy link
Owner

arcan1s commented Jan 7, 2021

temperature tags are now generating automatically from system dataengine. Do you have plasmaengineexplorer installed (it should be in plasma-sdk package or something like that)? It should have something like

изображение

also you can check parsed lmsensors devices from cache file (~/.cache/awesomewidgets.ndx, section called temp) or alternatively from widget settings you can ask for popup:

изображение

@danieledipompeo
Copy link

Thx...
I haven't yet installed plasmaengineexplorer.
Reading the ~/.cache/awesomewidgets.ndx I can get data about cpu, mem, and hdd (mounted partitions). However, I still have problem with the GPU usage and temp.
Here below the output of sensors
image

and here the output of ~/.cache/awesomewidgets.ndx
image

As far as I understood, I have updated the widget in this way
[cpu: $cpu% $temp6°C] [gpu: $gpu% $gputemp2°C] [mem: $memgbGB ($mem%)] [swap: $swap%] [/: $hddgb1GB ($hdd1%)] [/opt: $hddgb3GB ($hdd3%)] [$netdev: $down/$upKB/s] [uptime: $cuptime]

and the output is below
image

Can you understand where I use wrong setting?

Meanwhile, I play with different configurations.

BR
D.

@arcan1s
Copy link
Owner

arcan1s commented Jan 9, 2021

temperature seems to be alright, but for gpu there are several limitations

  • it only has $gpu and $gputemp tags and supposes that there is only 1 gpu for which you can measure things
  • it only supports amd and nvidia
  • it requires to have aticonfig and nvidia-smi executables respectively
  • I'm not even sure if it works with amdgpu, this part has been written for old fglrx driver (at least GPUDEV=auto will not recognize ati in this case). Also sadly I don't have access to device with amdgpu, so I can't even adapt the code (thou it should be easy probably)

At least I can say that in your case you can use $temp2 as "gpu temperature" because it is in sensors output and has been already parsed by kde dataengine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants