Conky and LM-Sensors

Hi!
I installed and ran LM-Sensors as described in the wiki article. Now I don't quite understand what I'm supposed to do to make Conky display my CPU temperature (and fanspeed if possible)? Here's the output of sensors:
Sorry about the screenshot, but I can't seem to copy and paste from URxvt, nor Xterm.
I also found this thread but I don't quite understand it. :S My motherboard is a Gigabyte GA-945GCM-S2L with an Intel Core 2 Duo 2.2 GHz processor.
Any ideas? Thanks in advance.

Thoht wrote:Sorry about the screenshot, but I can't seem to copy and paste from URxvt, nor Xterm.
google is your friend...
http://jhm.cotren.net/node/325
and there is even more about it

Similar Messages

[solved] Issue with conky and Kde 4

I have a small issue with conky and KDE 4.2. I start conky with a script which I stored under ~/.kde/Autostart. The script is simple and looks like this..
conky -c ~/.conkyrc_kde4
This works fine. But when I restart the first KDE and check with ps, I have 2 instances of conky running. The instances keep on growing with the number of restarts.
I think kde tries to restart all the apps which were running when the session was terminated. Is there a way to change this behavior in general or all the programs or for only a specific program like conky ?
Last edited by rangalo (2009-07-28 19:02:17)

I did
Systemsettings > Advanced > Session Manager > Start with an empty session
and put everything you want in Autostart

Can I use more than one blue-tooth device at the same time on IPhone 4S? Like a wireless headsets and speed and cadence sensor for cycling computer, receive the data and listen music simultaneously

Can I use more than one blue-tooth device at the same time on IPhone 4S? Like a wireless headsets and speed and cadence sensor for cycling computer, receive the data and listen music simultaneously

As long as the profiles are different (ex. HID vs AD2P) you will not have any issues. But say if you try to use 2 keyboards at once, it won't work. Or 2 headsets at once. Your scenario seems fine.

HT1665 i have an apple IPhone4. I am experiencing certain problem with my iphone4. The problems are as follows a. my ear piece and proximity sensor is not working while making a call. 2. It cannot reproduce sound without earphone but rings if gets any cal

Hi folks,
i have an apple IPhone4. I am experiencing certain problem with my iphone4. The problems are as follows a. my ear piece and proximity sensor is not working while making a call. 2. It cannot reproduce sound without earphone but rings normally if gets any call.
Can any one help me in this regard??

Try to reset the phone by holding the sleep and home button for about 10sec, until the Apple logo comes back again. You will not lose data by resetting, but it can cure some glitches after installing new software or apps.

How do I reinstall HP SImplepas and Validiy sensor on Win 8.1

Hi
I reinstalled HP SImplepass and validity sensor driver once before by doing it in a particular order i can no longer remember and running it under compatibility settings. I had to refresh my machine and I cant get the snesor to work
Can anyone advise on the correct order of installing driver and simple pass and advise on the correct HP SP file names for both for a dv7 7332earunning win 8.1 64 bit.
Thanks

Foxes_17
Welcome bacl to the HP Community Forum.
See the following:
Instructions to Upgrade HP SimplePass
Follow the procedure (Page 2 at writing):
Procedure - Update / (Re) Install HP SimplePass
1. Driver First
2. Reboot
3. Software Next
4. Reboot
NOTE:
You will likely want to use / stay with Series 6 / version 6.x HP SimplePass.
Ignore references to Series 8 HP SimplePass.
Click the Kudos Thumbs-Up to say Thank You!
And...Click Accept as Solution when my Answer provides a Fix or Workaround!
I am pleased to provide assistance on behalf of HP. I do not work for HP.
Kind Regards,
Dragon-Fur

Conky and top reporting differently

Here are some screen caps of conky and terminal running top command. The part I am interested in is the processes, one says 85 while the other says 105?
I question this because when I had gnome-system-monitor installed it would always show gnome-keyring-daemon as being open multiple times when I would logout and log back in. But, a fresh reboot would fix the issue.
what exactly is going on? How can I keep uninstalling things and when I reboot my processes in conky keep going up and up?
I am now running xfce and trying to rid myself of things I don't need like gnome based programs. The only thing stopping me from ridding myself of this gnome-keyring is GDM? But what login manager would I use if I don't use GDM, Any suggestions?
How do I post pictures?
Last edited by jacko (2007-12-03 17:37:30)

jacko wrote:I am now running xfce and trying to rid myself of things I don't need like gnome based programs. The only thing stopping me from ridding myself of this gnome-keyring is GDM? But what login manager would I use if I don't use GDM, Any suggestions?
I use Xfce and Slim. Search the wiki for slim.

Conky and frequency scaling

Hello.
I have couple of computers with conky and cpufreq working. All fine there. It was so also on my notebook, which had Ubuntu 9.04 installed. I reinstalled to 9.10 and since then my conky reports full frequency.
There was a lot of other issues, so I decided to finally remove Ubuntu and take the time to install Arch. Things are much better with Arch on this notebook, but I did not get rid of the frequency scaling problem. It is Thinkpad X31 btw.
According to powertop and cpufreq-info, the frequency scaling is working. Conky reports 1400Mhz all the time.
Here is my cpufreq-info:
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to [email protected], please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0
hardware limits: 600 MHz - 1.40 GHz
available frequency steps: 1.40 GHz, 1.20 GHz, 1000 MHz, 800 MHz, 600 MHz
available cpufreq governors: ondemand, performance
current policy: frequency should be within 600 MHz and 1.40 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 600 MHz.
cpufreq.conf
#configuration for cpufreq control
# valid governors:
# ondemand, performance, powersave,
# conservative, userspace
governor="ondemand"
# valid suffixes: Hz, kHz (default), MHz, GHz, THz
min_freq="0.5GHz"
max_freq="3GHz"
lsmod | grep freq
cpufreq_ondemand 7400 1
acpi_cpufreq 8648 0
freq_table 3740 2 cpufreq_ondemand,acpi_cpufreq
processor 36076 2 acpi_cpufreq
Running this script clearly shows that freq is changing
#!/bin/bash
while [ "1"=="1" ]; do
echo `cpufreq-info | grep "current CPU frequency"`
sleep 2
done
conkyrc
update_interval 2
background yes
use_spacer left
double_buffer yes
short_units yes
pad_percents 3
own_window yes
own_window_type normal
own_window_transparent yes
gap_x 4
gap_y 30
draw_shades no
draw_outline no
draw_borders no
stippled_borders 10
color0 black
color1 white
default_shade_color white
default_outline_color white
own_window_hints undecorated, below, skip_taskbar, skip_pager
alignment bottom_left
TEXT
${alignc}${color1}$nodename
${alignc}$sysname $kernel on $machine
${color1}$hr
${color1}CPU: $color0${cpu cpu0}%
${color0}${cpugraph cpu0 15}
${cpubar cpu0 4}
${color1}RAM :$color0 $memperc% ${membar 4}
${color1}Swap :$color0 $swapperc% ${swapbar 4}
${color1}Processes :$color0 ${exec printf "%3d" `ps -A | wc -l`}/$running_processes ${color1}Uptime :$color0 $uptime_short${color1}
${color1}Frequency :$color0 ${exec cpufreq-info | grep "current CPU frequency" | cut -c28-35} ${freq}${color1} ${if_existing /sys/class/power_supply/BAT0}${if_existing /sys/class/power_supply/BAT0/present 1}
${color1}$hr
Battery : $color0${battery_bar 4 BAT0}
${battery_time}${alignr}${battery}${endif}${endif}
${color1}$hr
${if_existing /sys/class/net/eth0/operstate up}${color1}IP :${alignr}${color0}${addr eth0}${color1}
Wired connection
${color0}${downspeedgraph eth0 12,108} ${upspeedgraph eth0 12,108}
${color1}Down : $color0${downspeed eth0} ${color1} Up: $color0${upspeed eth0}${color1}k/s ${else}${if_existing /sys/class/net/wlan0/operstate up}${color1}IP :${alignr}${color0}${addr wlan0}${color1}
Wifi :$color0${wireless_link_qual wlan0}% ${wireless_link_bar 4,0 wlan0}
${color0}${downspeedgraph wlan0 12,108} ${upspeedgraph wlan0 12,108}
${color1}Down : $color0${downspeed wlan0} ${color1} Up : $color0${upspeed wlan0}${color1}${else}
${endif}${endif}
${color1}$hr
${color1}CPU :$color0 ${ibm_temps 0} ${color1}C HDD :$color0 ${ibm_temps 2}${color1} C
${color1}GPU :$color0 ${ibm_temps 3} ${color1}C BAT :$color0 ${ibm_temps 4} ${color1}/${color0} ${ibm_temps 6} ${color1}C
${color1}$hr
${color1}Top: PID CPU% MEM%
${color0 white} ${top name 1} ${top pid 1} ${top cpu 1} ${top mem 1}
${color0 white} ${top name 2} ${top pid 2} ${top cpu 2} ${top mem 2}
${color0 white} ${top name 3} ${top pid 3} ${top cpu 3} ${top mem 3}
${color0 white} ${top name 4} ${top pid 4} ${top cpu 4} ${top mem 4}
As you can see I even put that part of script, which takes values from cpufreq-info into conky, but it still does show wrong values.
When I manually set frequency to 600Mhz, it shows up in conky.
With Ubuntu 9.04 this was working fine, so I wonder what has recently changed that could have resulted in this behaviour.

Archiee wrote:[...]
- Frequency step size is configurable (default to 100MHz/step) (cpufreq doesn't support this)
If I'm not mistaken it's the CPU that tells the utility what frequencies it can switch to; not the other way around. Remember each frequency has a voltage tied to it. Also, he's not asking about a way to manage his cpuf requency management, just about a glitch in actualy frequency reporting.
@ topic starter: why are you grepping cpufreq-info if you can have conky just read it out for you? It's a hardcoded conky feature...
From their documentation:
freq (n) Returns CPU #n's frequency in MHz. CPUs are counted from 1. If omitted, the parameter defaults to 1
@ Archiee: I checked with powernowd:
root@hermes # powernowd -v
powernowd: PowerNow Daemon v1.00, (c) 2003-2008 John Clemens
powernowd: Settings:
powernowd: verbosity: 1
powernowd: mode: 1 (AGGRESSIVE)
powernowd: step: 100 MHz (100000 kHz)
powernowd: lowwater: 20 %
powernowd: highwater: 80 %
powernowd: poll interval: 1000 ms
powernowd: about to return count = 1
powernowd: Found 2 scalable units: -- 1 'CPU' per scalable unit
powernowd: cpu0: 800Mhz - 1200Mhz (2 steps)
powernowd: step1 : 1200Mhz
powernowd: step2 : 800Mhz
powernowd: cpu1: 800Mhz - 1200Mhz (2 steps)
powernowd: step1 : 1200Mhz
powernowd: step2 : 800Mhz
root@hermes # cpufreq-info
cpufrequtils 006: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to [email protected], please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 1.20 GHz
available frequency steps: 1.20 GHz, 800 MHz
available cpufreq governors: userspace, powersave, ondemand, performance
current policy: frequency should be within 800 MHz and 1.20 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 800 MHz (asserted by call to hardware).
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 10.0 us.
hardware limits: 800 MHz - 1.20 GHz
available frequency steps: 1.20 GHz, 800 MHz
available cpufreq governors: userspace, powersave, ondemand, performance
current policy: frequency should be within 800 MHz and 1.20 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 800 MHz (asserted by call to hardware).

Light and Proximity sensors not working

Hello.
Recently, my Z10 hasdeveloped a very strange problem: light and proximity sensors would not work on the device. My Z10 no longer auto-dims the screen, and the screen stays on during calls. According to BBVE, light and proximity services are both listed as unavailable, and tests could not be carried out for them. Restarting the device seems to fix the problem temporarily. I am completely out of ideas what to do next, since this issue is very annoying. So far, I have tried:
Performed hard reset
Performed OS reload via BB Link
Used an autoloader to load developer OS
Did a battery pull
Did a security wipe
I spent a lot of time looking for a solution to this problem, and seems like it is relatively widespread issue - even affecting new devices like Passport. Any assitance would be greatly appreciated. Thank you.

Leslie8120 wrote:
Radishface wrote:
Hello.
Recently, my Z10 hasdeveloped a very strange problem: light and proximity sensors would not work on the device. My Z10 no longer auto-dims the screen, and the screen stays on during calls. According to BBVE, light and proximity services are both listed as unavailable, and tests could not be carried out for them. Restarting the device seems to fix the problem temporarily. I am completely out of ideas what to do next, since this issue is very annoying. So far, I have tried:
Performed hard reset
Performed OS reload via BB Link
Used an autoloader to load developer OS
Did a battery pull
Did a security wipe
I spent a lot of time looking for a solution to this problem, and seems like it is relatively widespread issue - even affecting new devices like Passport. Any assitance would be greatly appreciated. Thank you.
Did this problem occur suddenly or have you donwloaded any apps (android port) before the problem started ?
Hi there!
This problem occured suddenly, during normal operation. I don't have any Android apps installed. I even got the same issue right after I reloaded the OS and after the factory reset. Very strange.

Xcompmgr messing with openbox windows (conky and kde apps only)

here's the involved packages:
openbox 3.4.7.2-1
nvidia 177.82-1
xorg-server 1.5.3-3
xcompmgr 1.1.4-1
kdelibs3 3.5.10-2
conky 1.6.1-2
now the issue is primarily with xcompmgr. when it's running (default options or the whole -cCfF... stuff doesn't make a difference). i have the following:
whenever a kde apps window opens. (i.e. i start amarok or k3b; k3b opens new windows during burn start/stop process) my conky will disappear only to flicker and reappear a few seconds later. (this only happens with kde apps)
when i'm tweaking my conky i will often `pkill conky; sleep 3; conky` to see my changes. when i kill conky, ALL of my active windows on the current desktop disappear and only reappear if a) they are redrawn because of an update to their contents on their own accord, or b) (kinda the same thing) i grab a window and drag it all over the screen resetting whatever i pass over to it's correct visual state. (this only happens when killing conky)
this is annoying me, i love the shadows/fading from xcompmgr but this flickering makes my whole experience feel unstable and i have to turn it off after a few minutes. turn off xcompmgr and it's rock solid just as before... snappier too i think.
this behavior started immediately after the recent xorg update (i saved that for last because i know were all sick of _that_). i changed nothing, but for the -Syu when this happened.
anyways, your thoughts and help is much appreciated.

so i'm resurrecting this thread because i hoped, and prayed, that xorg 1.6 in testing would fix this problem. i've been working my ass off to keep my system back in xorg 1.4. my desktop just looks so oldfashioned w/o shadows and transparency.
ok so to re-outline, i'm running:
pacman -Q stuff
xorg-server 1.6.0-1
nvidia 180.29-3
openbox 3.4.7.2-1
xcompmgr 1.1.4-1
with this gpu:
hwd -s | grep video
Video : GeForce 7150 / nForce 630i server: XFree86 (vesa)
i created a minimal xorg.conf via nvidia-xconfig an added a few suggested options (although they _really_ don't seem to affect this bug...):
cat /etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder62) Thu Feb 5 00:08:50 PST 2009
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
Option "NoLogo" "True"
Option "RenderAccel" "True"
Option "TripleBuffer" "True"
Option "BackingStore" "False"
Option "DamageEvents" "True"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
now, here's what happens:
i startx, .xinitrc or autostart.sh bring up xcompmgr, bmpanel, and conky
if i open amarok or k3b, conky and bmpanel (both using transparency) vanish while the splash screen(s) show.
when i burn something with k3b (and new windows appear) i see similar behavior
sometimes it's just for a sec and then it's back, sometimes conky comes back with part of itself missing
also, if you execute `pkill conky` from an xterm, all windows are 'destroyed' until you [blindly] grab that xterm window and move it about your desktop 'revealing' the desktops contents. please see this screenshot for this in action.
killing xcompmgr fixes all this... but it's so ugly. the problems go away if i downgrade to xorg-server 1.4 (and also adjust any related/dependant packages to match).
please please, tell me i'm not alone! a fix would be nice too .
thanks in advance... again
Last edited by brisbin33 (2009-03-05 01:30:10)

Help: z10 stl002 proximity and light sensor issue

Proximity and light sensor not supported message on BBVE, both sensors stop working

I have BlackBerry z10 and I had the same problem ( proximity sensor was not working while being on call) and it started only available the update 10.3.1.1565. Then I noticed that my sensor was working before the update, that meant that hardware was okay. It might be the problem with the update. But I had got a new glass guard for the protection of my phone screen, I thought to remove it and then check. To my surprise, now it is working fine. I suggest you, if you also have some screen guard or glass guard on your phone, remove it and then check if it works. For me it did.

Automation using IP cameras, temperature, motion sensor and smoke sensor Using TCP/IP

Hello people,
My name is andy.
I have right know a project that i must automation a building using TCP/IP.
This building must have IP cameras, temperature, motion sensor and smoke sensor using the TCP/IP with a Sever.
My question is ?
what is IP cameras support Labview ?
and what VI i must Use??????
if any person have experience in this area for me is helpful to help me for some idea's.
please write me
thank you

Hi koeyers,
Are your cameras Gigabit Ethernet? If they are, we have some interfaces that you can use as frame grabbers.
http://sine.ni.com/nips/cds/view/p/lang/es/nid/203245
And you can use our image acquisition driver, NI-IMAQdx, you can download our driver for a 30 days free trial.
http://joule.ni.com/nidu/cds/view/p/id/960/lang/es
NI-IMAQdx installs LabVIEW VI’s that calls the NI-IMAQdx driver to control you camera, example files are install with the driver too!
If you are not using Gigabit Ethernet, you will need to use the driver that ships with the camera. Do you have the data sheet of the camera you are using? Or are you starting to look for cameras?
If you are looking for cameras this is a good link that will help you find cameras that are supported by our drivers:
http://sine.ni.com/apps/utf8/nipc.specs?action=search&asid=1102
Some IP cameras (not Gibabit Ethernet) have ActiveX calls to control them, and LabVIEW can make those ActiveX calls, you just need to have the documentation of those calls that must come with the camera. Other cameras might have DLL’s and you’ll have to make calls to those DLL’s from LabVIEW.
They are more difficult to program that Gigabit Ethernet because they are not a standard, and National Instruments doesn’t have a specific driver for them, but we can make calls to the specific driver of the camera.
Later, if you want to process the images, then you will be interested in NI Vision:
http://www.ni.com/vision/vdm.htm
Please let me know if this helps you or you need more information.
Tania Lozoya | National Instruments

Measuring the one sensor above and one sensor below

Hi
Cn somebody help me in measuring one sensor above and one sensor below and if thy are almost equal must stop.
I tried doing so, but i dont knw whr it is going wrong. I hv attached the program with this query.
In a large cryogenic storage system, we need to find the level of cryogenic fluids. For ths we a immersed PCB consisting of multiplexers and sensors into the storage system. We need to find the level by passing current to the PCB & measuring voltage at each sensor. We can conform the liquid level by measuring one sensor above and one sensor below the actual level.
Thanks in Advance.
Regards,
Sujeep.
Attachments:
liquidlevel1.vi ‏358 KB

sujeep wrote:
Hi
Can somebody help me in measuring one sensor above and one sensor below and if they are almost equal must stop.
I tried doing so, but i don't know where it is going wrong. I have attached the program with this query.
In a large cryogenic storage system, we need to find the level of cryogenic fluids. For this we a immersed PCB consisting of multiplexers and sensors into the storage system. We need to find the level by passing current to the PCB & measuring voltage at each sensor. We can conform the liquid level by measuring one sensor above and one sensor below the actual level.
Thanks in Advance.
Regards,
Sujeep.
You should submit a little more detail as to what is going wrong. Also, what do V1 through V6 represent? They seem to be read from the same analog input channel. You should try passing those value through with wires rather than using local variables. If so, you could eliminate a large number of your sequence frames.
In the 4th frame of your sequence structure, you could have a race condition. You are reading V4 as a local variable around the same time you are assigning a value to V4 through the DaqMX read. You don't know whether it is using the latest V4 value or the one from the previous iteration.
I would also recommend not using the STOP sign VI. If you have a case where the program should end, you should wire the boolean out of the case structures and to the condition node of the while loop. It will allow the code to end much more cleanly. In your situation, the DaxMX close will never execute because the only way the program ends is through the STOP sign which is the equivalent of hitting the ABORT button.

Z10 - Light and proximity Sensor not working

Hi,
unfortunately neither the light Sensor nor the Proximity Sensor are working on my device (Z10). I did reset my device to factory settings yesterday but without success. BBVE tells all sensor services are available and running but the Proximity and Light Sensor tests fail. I tried to reboot the phone but afterwards BBVE claims the Sensor Services to be not even running anymore.
My Phone is currently running on Version 10.2.1.2977.
Is this a software or hardware releated problem? And does there exist any fix to it?
Thanks for your help in advance.
Best regards.

Leslie8120 wrote:
Radishface wrote:
Hello.
Recently, my Z10 hasdeveloped a very strange problem: light and proximity sensors would not work on the device. My Z10 no longer auto-dims the screen, and the screen stays on during calls. According to BBVE, light and proximity services are both listed as unavailable, and tests could not be carried out for them. Restarting the device seems to fix the problem temporarily. I am completely out of ideas what to do next, since this issue is very annoying. So far, I have tried:
Performed hard reset
Performed OS reload via BB Link
Used an autoloader to load developer OS
Did a battery pull
Did a security wipe
I spent a lot of time looking for a solution to this problem, and seems like it is relatively widespread issue - even affecting new devices like Passport. Any assitance would be greatly appreciated. Thank you.
Did this problem occur suddenly or have you donwloaded any apps (android port) before the problem started ?
Hi there!
This problem occured suddenly, during normal operation. I don't have any Android apps installed. I even got the same issue right after I reloaded the OS and after the factory reset. Very strange.

Proximity sensor and light sensor not working

Z10STL100-1/10.2.1.2141
My proximity and light sensors are not working. BlackBerry virtual expert can't detect motion in proximity sensor test and not able to handle light dim or high in light sensor.
What should I do now?
It's very frustrating because I just bought this phone yesterday.

Strange thing happened to me today. When i did security wipe my both sensors started working. Both were working till evening. Then suddenly it stopped working, so what is the problem.?
I am really waiting for solution.

The Multi-touch surface of the Magic Mouse could be more smoother and the sensor could be more sensitive on different kinda surfaces.

The Multi-touch surface of the Magic Mouse could be more smoother and the sensor could be more sensitive on different kinda surfaces.

) I have a ProLink bluetooth mouse with me labelled 2.4GHz wireless mouse with this USB bluetooth stub that is inserted into the USB port in order for the mouse to connect to my iMac. (i'm not a techincal guy)
Is this mouse connected at the same time as the Magic Mouse? If so, unplug it.
Try resetting the PRAM: http://support.apple.com/kb/PH14222
Try putting it on a mouse pad.
Barry

Conky and LM-Sensors

Similar Messages

Maybe you are looking for