Ubuntu :: GKrellM Not Sensing Voltage/Fan Sensors?
Jan 13, 2011
GKrellM worked fine under 9.04.W/ 10.04 it works but does not sense the Fan or Voltage sensors.I transplanted the old folder over to /home after downloading GKrellM, hddtemp, and lm-sensors thru Synaptic.Ran the hddtemp and lm sensors in terminal w/ no problems.Running sensors revealed all inputs: cpu temps, fan speeds, andmobo voltages.GKrellM downloaded was ver 2.3.4 while my old folder data was 2.3.2. Sensor config file is same format just that the old config file has all the voltage/fan pointers assigned as well.
Weird thing is that GKrellM will overwrite the sensor-config file (that has ALL the sensor defined inputs pasted into it) after going into the program and selecting Configuration. It reverts to the sensor-config file created after running lm-sensors and hddtemp under 10.04.So it's autowriting itself and not picking up the fan/voltage inputs.Displaying the data thru the Sensor Applet in the Desktop panel is OK but I prefer having everything on GKrellM. It's a much cleaner, easy to view system. Anybody got a clue why GKrellM is overwriting the sensor-config file. That should be static, unlike the user-config file.
I run F15 on my desktop PC. I've run gkrellm on my desktop since FC5. This week I tried to add the gkrellm plugin gkrellm-freq via "Yum extender". The install appeared to be successful, but when I invoke gkrellm configuration gkrellm-freq does not appear on my list of gkrellm plugins. Also, gkrellm is not displaying the cpu frequency info.I use other gkrellm plugins (weather, sun) and they work fine.
I have been trying to configure the mailcheck in gkrellm to check and notify for new mail on my gmail account. I have activated pop of course...
These are the pop info taken from gmail:
Server for incoming mail (IMAP) - needs SSL: imap.gmail.com Use SSL: Yes Port: 993 Server outgoing mail (SMTP) - needs TLS: smtp.gmail.com (use verification) Use verifiering: Yes Use STARTTLS: Yes(some clients call this SSL) Port: 465 or 587
I can't for the life of me get the xsensors to work. I installed lm-sensors, the applet and also xsensors.I followed everything on this guide:URl... Went through it more than twice and a couple of restarts. I just can't figure out what's wrong.When I run "sensors" nothing is found. I ran the sensors configuration and it only found one device to add to /etc/modules. Please see the trace below, I would be very grateful if you can help me find the fix for this! The desktop is an HP Pavilion a730n with a Pentium4 processor.
I would like to use lm-sensors with my new PC.With my old one lm-sensors showed all sensors of CPU, GPU, wattage and Fan.With the new AMD64 (kernel 2.6.32-5 on Debian Squeeze) I get only the temperature of the GPU and the HDD.The only found sensor is "Fintek F71882FG/F71883FG Super IO Sensors"No embedded "AMD [...] thermal sensors" found in sensors-detect How can I fix it?sensors-detect
I am doing a project on how power consumption of a CPU can be improved by underclocking the lower P-states and overclocking the highest p-state.In this way you can increase both the performance of the chip and it's average power usage (assuming you don't run the chip at 100% 24/7).
To do this project I need to be able to change the voltage and frequency of the chip for all of the different p-states of the chip. On Windows I can use k10stat, RMClock or AMD Overdrive.
What can I use in Linux? I found k10ctl, but it always complained about not being able to find /dev/cpu/0, so I looked in /dev and noticed that their isn't even a cpu directory in there!
I have a moderate amount of experience so I don't mind changing kernels or doing other hard tasks to get this to work.
how to enable transparent themes on Gkrellm and KDE 4. AND ASK FOR HELP WITH A PROBLEM FURTHER DOWN THE PAGE. Libsensors is THE program for gathering sensor data for use in various applets. Some few (mostly older) sensors have their output sent to a system file, where it can be picked-up and used by the system, but the best way to get sensor data, especially for newer sensor chips, is directly from libsensor. Since 2007 libsensor support has been built out of Gkrellm in Ubuntu (perhaps all of Debian, though I'm unclear on that). From some cursory research on the internet, I discovered that in 2007 libsensors did a major update, and Gkrellm did not. Problems insued. Support for libsensors was dropped in Gkrellm. Even though a patch was produced fairly quickly, support for libsensors in Gkrellm was never re-allowed. There is a bug on this here.
To enable support for libsensors in Gkrellm you have to build Gkrellm from source (EGADS!!) It's really pretty easy with this package and mine went off without a hitch (and I now have WONDERFUL readouts from my atk0110 sensors on my asus mb.). You can find the source package for Gkrellm here, and you can find some easy instructions for building it here. Piece of cake (really!). Okay, on to invisibility.... Gkrellm invisibility doesn't happen in KDE 4 (without a little tinkering...). I discovered the fix by looking for insights in pages discussing the same problem in conky. I found a good one, and thinking the same situation might apply to gkrellm, I tried it and IT WORKED! Here's the original post. My gratitude to the author. I'm going to reproduce the process here for posterity's sake, and because the command has changed slightly with the location of the plasma-desktop-appletsrc file.
So, gkrellm uses fake transparency. It samples the desktop at its coordinates and reproduces the image as its background. Gkrellm doesn't use the user's desktop to sample from - it uses the root desktop image - hence the strange-looking colors I got whenever I tried one of the transparent themes. Okay, so first you need to make your current desktop image your root desktop image. To do this you need to install "feh" (copy and paste these commands into terminal)
sudo apt-get install feh After that's done, enter this in terminal:
Okay, now it needs to be set-up so that it'll load automatically. The feh documentation recommends setting this in ~/.xsessionrc (if you don't have one, make one with kate - and don't forget the dot before the name [ the expression ~/ is shorthand for your home directory path, /home/username, so the aforementioned path in full would be /home/username/.xsessionrc ]):
That done, we arrive at a problem. I could use some help here, if anyone has any idea how to fix it. It's not a deal-breaker, but it's definitely inconvenient if you like to change your wallpaper a lot. The feh program creates a file called ~/.fehbg to store the actual path of the image used as 'wallpaper'. Unfortunately, it stores it like this:
The two single quotes enclosing the path are unfortunately read as part of the path, so when feh (or if it hands it off to bash or kde) looks for the image file it can't find it. You get a no such file error in feh. I created a bug report here. The only way I know of to fix it (I tried removing various sets of quotation marks from the original feh command to no avail) is to open the ~/.fehbg file in kate and remove the two single quotations, so it looks like this:
But you must still do one more thing. You must change the permissions on ~/.fehbg to root, or the image's path will be overwritten the next time it's opened (at next login), with the single quotes included. Doing so fixes the issue in the short term, but when you change desktop images you'll have to reinstate your user privileges on the file, and re-run the original command to allow the file to be written to by feh (with the new image path), then edit the file again to remove the single quotes.
I can't get Gkrellm to show my fan speeds anymore since reinstalling Ubuntu.I have tried 9.10 and 10.04 and tried installing packages to maybe get the drop down to show up for fan speed but still nothing.I have installed Xsensors and that shows fan speeds correctly but I want to show them in Gkrellm like I used to have. Now every other temp gauge is working like it used to but the fan speed monitor.
I recently installed a server with Software RAID. I tested by powering it down, unplugging one drive and powering it up. Magically, it worked!I found out later that I have to manually add individual devices like md1 to sda2 md2 to sda4. I got all of them added and rebuilt but my question is: Is there a way to make it so that if I "removed" a drive and put it back, the system will senses the new drive and rebuilds based on some internal table?
I have been trying to add more sensors for hdd drives temperatures but i see only one and no place/options to add more.I know they all work,(i have 4 physical hdd) if i use the hhdtemp command (dev/sdXX) it show the temp for all of them (one at time). Any way to make gkrellm display all of them ? I,ve been googling around and searching on various forums but haven't found anything about that (other than how to make it work,or troubleshooting to make it work). I've tried conky ..but gives me more errors than info and i gave up.
I'm looking for any power monitoring devices for Linux to allow monitoring power quality, voltage changes, and outages. This would be for North American three phase power system. I want to have this data fed live to my own program. It should be something much better than just jury-rigging a circuit to fee the power waveform into 2 or 3 audio cards.
gkrellm process starts automatically without me indicate. In auto-run system preferences kde is not configured to start automatically, set at the time but removed it and just beginning the process continues in the background
This morning gkrellm updated from 2.3.4-1 to 2.3.5-2 and now the CPU temperatures aren't displayed. I've rerun sensors-detect and restarted module-init-tools, but the temperatures still don't display. If I run sensors from a terminal, the CPU core temperatures are displayed correctly. Has anyone else seen this?
i was just wondering if there is a way to change the gkrellm text size, ^^ it's just its too little for me, i have to get closer to be able to see what graphic is what. so... is there a way to make the text bigger? a theme maybe?
i was wondering if it is possible to put gkrellm (system monitor with temp) inside of the top or bottom taskbar. my laptop overheats and i would like to be able to see my temps somewhere on my screen permanently. im sure there is a plugin or something of that nature i dont know about, if there is,
Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `k10temp' (autoloaded): * Chip `AMD Family 10h thermal sensors' (confidence: 9) No modules to load, skipping modules configuration. Unloading i2c-dev... OK
There is a debugging panel on my motherboard, and I think that that displays the CPU temperature, although I am not sure.
I had previously installed lm-sensors and the associated files on my Lattitude 2100 when I was running 8.10 and got a great little bargraph readout thing at the bottom of the screen that helped me monitor system temperatures. Now that I've upgraded to lucid lynx netbook, I can't seem to get the same thing going. I installed the lm-sensors etc. but the applet/readout/display whatever you want to call it, is nowhere to be found.
I installed lm_sensors via Synapt & the Sensors Applet on the panel, but that applet shows me an invariable 40�C for 2 temperatures - 'CPU' & 'temp1'.Now I know it can't read the CPU temperature (long story, the CPU fan is hard-wired to 6v & there is no temperature feedback...) but it should be able to find a couple of other useful temperatures.The same PC in XP uses Speedfan which indicates plausible temperatures for (I think) Case & Hard Drive. (Temp2 & HD0 in the attached)I wonder what I have failed to do & why I cannot see Case or HD temps in Ubuntu?In terminal, I ran sensors-detect which went OK until the last bit where it said:
"~$ /etc/init.d/module-init-tools start Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service module-init-tools start...etc" I don't follow that, but I have checked that I have it87 in both /etc/modules & in lib/modules/.../hwmon
I installed Sensors Applet & hddtemp. Installation was smooth, all of my devices were automatically detected and all seemed good.Then I restart the computer, and when everything comes back up, the processor, MB, and GPU are all working (showing a temperature) but none of the (6) hard drives are showing a temperature. After fiddling around with it I found that removing the applet from the panel, and then adding it back again fixes the problem. But then the next time I restart the computer it breaks again.
I installed Karmic 64-bit on a new Phenom X4 Quad-Core PC. I've replaced the stock CPU cooler with a Cooler Master Hyper TX3, enabled all fan control settings in the BIOS, switched their profiles on silent, enabled the Cool n' Quiet option as well but my CPU fan is still noisy and seem to be running up to the max number of RPM, thus ignoring BIOS specifications. Besides this I can tell there is something wrong with it since even the CPU is on idle or with just the regular browsing, media player operations, PC sometimes freezes or is automatically rebooted .
I installed lm-sensors and went through all the sensors-detect operations (output attached to this post) but it doesn't show anything else but the CPU and HDD temperature which is always 40 Celsius degrees.
After several attempts, the Hardware Sensors Monitor cannot detect hdd. The following is what was done. I originally installed gnome sensor applet through ubuntu software center and without paying much attention I also proceeded not to have the hddtemp boot up. After adding to the panel the hardware sensors monitor, the hddtemp was not there so..ive proceeded to do the following in the terminal:
sudo dpkg-reconfigure hddtemp sudo chmod u+s /usr/sbin/hddtemp sudo sensors-detect and yes to all sudo modprobe..there were two chip drivers
when i did sudo hddtemp /dev/sda the temp is detected.I added back the applet to the panel but the sensor is still not there.
sudo dpkg -s hddtemp also returned the status that everything was installed. i rebooted i double checked in the synpatics manager if all the programs are installed. I have lm-sensors, hddtemp and sensors-applet. in the command line..i did dmesg removing and re-adding the applet to the panel proved futile and still cannot see hdd temps. Where did I go wrong?
I'm running ubuntu 9.10 64 bit on a Dell Latitude E6400 with the following configuration:
Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz, 3MB L2 Cache 1066 MHz Intel Graphics Media Accelerator x4500HD 4GB RAM 250 GB Hard Drive SATA 7200RPM
I'm experiencing overheating problems, after just 15-20 minutes of minimal use (surfing the internet, not even watching flash vids or any other vids). The same laptop under Windows 7 64 bit stayed really cool.
I've read several posts here and followed this manual: [URL] to try to control the fans (I only installed the lm-sensors and ran the sensors command, I didn't do anything beyond that). Specifically what I did was install lm-sensors (via apt-get), ran sensors-detect which advised me to add the coretemp module to /etc/modules, which I did.
However when running sensors the only information I get is the overall temperature and the temperature of each of the cores.
why I'm not getting fan speed info when running sensors? Also is there a way to find out if more modules needs to be added to /etc/modules?
I am having difficulty setting up lm-sensors so that I can monitor fan speed and temps. I have been following theHow-To on the forums, but it appears I don't have the sensors detected/loaded properly.
This is the current output: Code: ronald@ronald-Satellite-L505:~$ sensors acpitz-virtual-0 Adapter: Virtual device temp1: +69.0C (crit = +114.0C) coretemp-isa-0000 Adapter: ISA adapter Core 0: +63.0C (high = +105.0C, crit = +105.0C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +57.0C (high = +105.0C, crit = +105.0C)
Below is a copy of what I have been trying in terminal. Here is a walkthrough of sensors-detect: Code: ronald@ronald-Satellite-L505:~$ sudo sensors-detect [sudo] password for ronald: # sensors-detect revision 5818 (2010-01-18 17:22:07 +0100) # System: TOSHIBA Satellite L505 (laptop) # Board: TOSHIBA Portable PC ..... Monitoring programs won't work until the needed modules are loaded. You may want to run '/etc/init.d/module-init-tools start' to load them.
Possibly necessary info: 10.10 64-bit Intel T4300 dual core Western Digital WD3200BEKT HDD
atlast i downloaded 64 bit version of natty. (i m currently using 10.10 32 bit). before i go for a clean install, i wished to test natty (the stable release) by running it from my usb stick. i was able to boot into it and natty identified my wi-fi with a breeze. i wanted to test some configurations that i had customized in maverick. i installed conky in natty and copied the conky script that i used in maverick. i also installed the necessary sensors. now the hitch is the sensors are unable to detect the temperature. is it coz i am running natty from a usb stick or some bug is there in this part ?
After I ran sensors-detect, it said that İ needed k10temp module to be compiled, so I searched some forums and got required stuff. However, before compiling it, I added the gnome applet for sensors to the panel, and surprisingly it shows the cpu and motherboard temperatures. How reliable it is? Do I still need to compile k10temp? (I will compile it since I don't want to use a kernel from experimental repo).My kernel is 2.6.32-5-amd64, TestingCPU: AMD Phenom 2 x4 955 BE
just downloaded gkrellm and I go to set the temperature sensors and I get "No Sensors Detected" now I've never dealt with something of this nature before so can anyone tell me where I might begin with this one?
I have just recently installed opensuse 11.3 on my computer. I have switched from Ubuntu and have been trying to get things configured similar to what it was. One problem I have encountered is with installing sensors and k10temp, the module needed to monitor my CPU temp. within Linux. I have an AMD sempron and a biostar mcp6p m2+ motherboard. I have installed package "sensors" and have run the sensors-detect and it went through and found k10temp that I would need to load within the kernel for this to work properly. I had this working in Ubuntu, but not sure how to do it in openSuse. I have tried compiling the k10temp source, running modprobe k10temp and received no output, and looked around the conf files, but not sure how to go about doing it?