Originally Posted by
rolypolycat
I followed your instructions for adding the ppa to my sources, and downloaded the files; from the info in the terminal, I believe my conky is the latest one. Something got installed, after all. And I followed the instructions for hddtemp with the answers you gave me.
The line you wrote:
${color0}HDD Usage: [${color}${execi 15 hddtemp -n /dev/sda}°C${color0}]
Do I add this to my conky? And the other one command as well? If so, where in the file should they go?
Ran the command:hddtemp -n /dev/sda- got a reply of 37 degrees, so it's holding steady.
I really appreciate you're helping me with this. I've wanted to use this program for some time, but could never get it to work. Thanks!
Do:
and just tell me, yes or no, if you see a line like this saying Conky 1.9.0
Code:
Conky 1.9.0 compiled Fri May 11 15:54:00 UTC 2012 for Linux 2.6.32-5-amd64 (x86_64)
That will tell you for certain.
The HDD line should already be there, look at your conky - about half way down do you see:
Now lets go back to the terminal:
Code:
sensors | grep 'Core 0'
I hope you see some thing like this:
Code:
13 Oct 12 | 09:33:32 ~
$ sensors | grep 'Core 0'
Core 0: +49.0°C (high = +86.0°C, crit = +100.0°C)
IF you see that ... this line that is looking for you CPU temp:
Code:
CPU: ${color}${cpu cpu1}% ${color0}[${color}${hwmon 2 temp 1}C${color0}] ${freq_g}GHz
will be in for a change.
For the sake of speed lets say it does work as seen above.
Since I don't have "Core 1" but I have a 'fan1' I'll use that as a sample:
First: grep gets the line we want (you use 'Core 0')
Code:
13 Oct 12 | 10:27:31 ~
$ sensors | grep 'fan1'
fan1: 2290 RPM
Next we start cutting character we do not need:
... but | cut -c3 is much shorter
that following " - " at the end means: to end of line
Code:
13 Oct 12 | 10:27:36 ~
$ sensors | grep 'fan1' | cut -c3-
n1: 2283 RPM
notice the first 2 characters are cut - we've cut to the third character.
Here you see we are getting closer - spaces count.
Code:
13 Oct 12 | 10:27:42 ~
$ sensors | grep 'fan1' | cut -c10-
2283 RPM
Oops! "| cut -c15-" is one too much:
Code:
13 Oct 12 | 10:27:50 ~
$ sensors | grep 'fan1' | cut -c15-
283 RPM
back it up one space
Code:
13 Oct 12 | 10:27:57 ~
$ sensors | grep 'fan1' | cut -c14-
2283 RPM
Now lets get rid of that RPM we need character 14, 15, 16 & 17 - so add the 17 to the end:
Code:
13 Oct 12 | 10:28:04 ~
$ sensors | grep 'fan1' | cut -c14-17
2340
How would I display that in a conky - Like this:
Code:
${color0}Fan ${color}${execi 8 sensors | grep 'fan1' | cut -c14-17} ${color0}RPM
that line will update the fan speed every 8 seconds
For your CORE it might look like this
Code:
CPU: ${color}${cpu cpu1}% ${color0}[${color}${execi 8 sensors | grep 'Core 0' | cut -c14-15}°C${color0}] ${freq_g}GHz
This part cut -c14-15 will be the deciding factor.
Let me know how it goes ... it works wonderful here. Nice little conky:
BTW; The ending of your first line (your original):
That command doesn't exits in the Conky Variables
you have two options:
freq (n)
Returns CPU #n's frequency in MHz. CPUs are counted from 1. If omitted, the parameter defaults to 1.
freq_g (n)
Returns CPU #n's frequency in GHz. CPUs are counted from 1. If omitted, the parameter defaults to 1.
I think I put it in as GHz for you.
Bookmarks