1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
\r
2 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
\r
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
\r
5 <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
\r
6 <meta name="generator" content="AsciiDoc 8.6.6" />
\r
7 <title>Psensor Frequently Asked Questions</title>
\r
8 <style type="text/css">
\r
10 padding: 1em 1em 1em 1em;
\r
11 font-family: "Ubuntu", sans-serif;
\r
14 font-weight: normal;
\r
16 background-color: #fff;
\r
23 text-decoration: none;
\r
27 text-decoration: underline;
\r
34 text-transform: uppercase;
\r
44 text-transform: uppercase;
\r
45 margin: 2em 0em 1em 0em;
\r
71 background-color: #000;
\r
81 padding: 0.25em 0.5em 0.25em 0.5em;
\r
83 font-weight: normal;
\r
87 padding: 0.25em 0.25em 0em 0.25em;
\r
93 font-weight: normal;
\r
124 font-style: normal;
\r
128 font-weight: normal;
\r
132 text-transform: uppercase;
\r
136 padding-bottom: 1em;
\r
140 padding: 0 0 0 1em;
\r
144 <script type="text/javascript">
\r
146 var asciidoc = { // Namespace.
\r
148 /////////////////////////////////////////////////////////////////////
\r
149 // Table Of Contents generator
\r
150 /////////////////////////////////////////////////////////////////////
\r
152 /* Author: Mihai Bazon, September 2002
\r
153 * http://students.infoiasi.ro/~mishoo
\r
155 * Table Of Content generator
\r
158 * Feel free to use this script under the terms of the GNU General Public
\r
159 * License, as long as you do not remove or alter this notice.
\r
162 /* modified by Troy D. Hanson, September 2006. License: GPL */
\r
163 /* modified by Stuart Rackham, 2006, 2009. License: GPL */
\r
165 // toclevels = 1..4.
\r
166 toc: function (toclevels) {
\r
168 function getText(el) {
\r
170 for (var i = el.firstChild; i != null; i = i.nextSibling) {
\r
171 if (i.nodeType == 3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
\r
173 else if (i.firstChild != null)
\r
174 text += getText(i);
\r
179 function TocEntry(el, text, toclevel) {
\r
182 this.toclevel = toclevel;
\r
185 function tocEntries(el, toclevels) {
\r
186 var result = new Array;
\r
187 var re = new RegExp('[hH]([2-'+(toclevels+1)+'])');
\r
188 // Function that scans the DOM tree for header elements (the DOM2
\r
189 // nodeIterator API would be a better technique but not supported by all
\r
191 var iterate = function (el) {
\r
192 for (var i = el.firstChild; i != null; i = i.nextSibling) {
\r
193 if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
\r
194 var mo = re.exec(i.tagName);
\r
195 if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
\r
196 result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
\r
206 var toc = document.getElementById("toc");
\r
211 // Delete existing TOC entries in case we're reloading the TOC.
\r
212 var tocEntriesToRemove = [];
\r
214 for (i = 0; i < toc.childNodes.length; i++) {
\r
215 var entry = toc.childNodes[i];
\r
216 if (entry.nodeName == 'div'
\r
217 && entry.getAttribute("class")
\r
218 && entry.getAttribute("class").match(/^toclevel/))
\r
219 tocEntriesToRemove.push(entry);
\r
221 for (i = 0; i < tocEntriesToRemove.length; i++) {
\r
222 toc.removeChild(tocEntriesToRemove[i]);
\r
225 // Rebuild TOC entries.
\r
226 var entries = tocEntries(document.getElementById("content"), toclevels);
\r
227 for (var i = 0; i < entries.length; ++i) {
\r
228 var entry = entries[i];
\r
229 if (entry.element.id == "")
\r
230 entry.element.id = "_toc_" + i;
\r
231 var a = document.createElement("a");
\r
232 a.href = "#" + entry.element.id;
\r
233 a.appendChild(document.createTextNode(entry.text));
\r
234 var div = document.createElement("div");
\r
235 div.appendChild(a);
\r
236 div.className = "toclevel" + entry.toclevel;
\r
237 toc.appendChild(div);
\r
239 if (entries.length == 0)
\r
240 toc.parentNode.removeChild(toc);
\r
244 /////////////////////////////////////////////////////////////////////
\r
245 // Footnotes generator
\r
246 /////////////////////////////////////////////////////////////////////
\r
248 /* Based on footnote generation code from:
\r
249 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
\r
252 footnotes: function () {
\r
253 // Delete existing footnote entries in case we're reloading the footnodes.
\r
255 var noteholder = document.getElementById("footnotes");
\r
259 var entriesToRemove = [];
\r
260 for (i = 0; i < noteholder.childNodes.length; i++) {
\r
261 var entry = noteholder.childNodes[i];
\r
262 if (entry.nodeName == 'div' && entry.getAttribute("class") == "footnote")
\r
263 entriesToRemove.push(entry);
\r
265 for (i = 0; i < entriesToRemove.length; i++) {
\r
266 noteholder.removeChild(entriesToRemove[i]);
\r
269 // Rebuild footnote entries.
\r
270 var cont = document.getElementById("content");
\r
271 var spans = cont.getElementsByTagName("span");
\r
274 for (i=0; i<spans.length; i++) {
\r
275 if (spans[i].className == "footnote") {
\r
277 var note = spans[i].getAttribute("data-note");
\r
279 // Use [\s\S] in place of . so multi-line matches work.
\r
280 // Because JavaScript has no s (dotall) regex flag.
\r
281 note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
\r
282 spans[i].innerHTML =
\r
283 "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
\r
284 "' title='View footnote' class='footnote'>" + n + "</a>]";
\r
285 spans[i].setAttribute("data-note", note);
\r
287 noteholder.innerHTML +=
\r
288 "<div class='footnote' id='_footnote_" + n + "'>" +
\r
289 "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
\r
290 n + "</a>. " + note + "</div>";
\r
291 var id =spans[i].getAttribute("id");
\r
292 if (id != null) refs["#"+id] = n;
\r
296 noteholder.parentNode.removeChild(noteholder);
\r
298 // Process footnoterefs.
\r
299 for (i=0; i<spans.length; i++) {
\r
300 if (spans[i].className == "footnoteref") {
\r
301 var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
\r
302 href = href.match(/#.*/)[0]; // Because IE return full URL.
\r
304 spans[i].innerHTML =
\r
305 "[<a href='#_footnote_" + n +
\r
306 "' title='View footnote' class='footnote'>" + n + "</a>]";
\r
312 install: function(toclevels) {
\r
315 function reinstall() {
\r
316 asciidoc.footnotes();
\r
318 asciidoc.toc(toclevels);
\r
322 function reinstallAndRemoveTimer() {
\r
323 clearInterval(timerId);
\r
327 timerId = setInterval(reinstall, 500);
\r
328 if (document.addEventListener)
\r
329 document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
\r
331 window.onload = reinstallAndRemoveTimer;
\r
335 asciidoc.install(2);
\r
339 <body class="article">
\r
341 <h1>Psensor Frequently Asked Questions</h1>
\r
343 <div id="toctitle">Table of Contents</div>
344 <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
348 <div class="sect1">
\r
349 <h2 id="S_NoSensors">1. No sensors or only cpu usage is displayed</h2>
\r
350 <div class="sectionbody">
\r
351 <div class="paragraph"><p>Psensor is relying on few libraries or softwares for retrieving the information about the computer:</p></div>
\r
352 <div class="ulist"><ul>
\r
355 motherboard and CPUs sensors: the information is retrieved
\r
356 from the lm-sensors library, it requires that
\r
357 ‘sensors-detect’ has been run and the kernel module
\r
358 correctly installed. ‘sensors’ can be used for checking.
\r
363 GPUs: it depends on which driver you are using:
\r
365 <div class="ulist"><ul>
\r
368 Opensource drivers (nouveau for Nvidia GPUs or
\r
369 radeon/ati for ATI GPUs) is used and support sensor
\r
370 monitoring for your GPU, the information is using
\r
371 lm-sensors, same steps than above.
\r
376 proprietary driver Nvidia: run ‘nvidia-settings’ to
\r
377 check that it supports sensors monitoring.
\r
382 proprietary driver Catalyst/fglx: use ‘aticonfig’ to
\r
383 check that it supports sensors monitoring. Important
\r
384 note: it requires that you are using a Psensor
\r
385 binary compiled with the ATI support.
\r
392 HDDs: it uses the hddtemp daemon. Verifies that it is
\r
393 correctly reporting temperature by using the ‘sudo hddtemp
\r
394 /dev/sd?’ command. If hddtemp does not support your disk,
\r
395 you may want to try using the libatasmart support instead
\r
396 (option –use-libatasmart option).
\r
400 <div class="paragraph"><p>If the underlying software is reporting sensors which are not
\r
401 displayed by Psensor, it is probably a bug in Psensor, so please
\r
402 report it. Otherwise, the issue is on the underlying software itself
\r
403 and you should contact the corresponding development team or refer to
\r
404 its documentation.</p></div>
\r
407 <div class="sect1">
\r
408 <h2 id="S_ATIMonitoring">2. How to monitor an ATI card using the Catalyst driver?</h2>
\r
409 <div class="sectionbody">
\r
410 <div class="paragraph"><p>For monitoring ATI card using the proprietary Catalyst driver, Psensor
\r
411 must be compiled with a proprietary library which is not packaged in
\r
412 any Linux distribution.</p></div>
\r
413 <div class="paragraph"><p>Unfortunely, due to the license of this library, I cannot provide a
\r
414 compiled version of Psensor, even in a Ubuntu PPA or Ubuntu/Debian
\r
415 standard repositories. You have to compile Psensor sensor. You can
\r
416 find the instructions in the section “ATI/AMD GPU Support” of the
\r
417 README file available in the Psensor source archives.</p></div>
\r
418 <div class="paragraph"><p>If you are using the ATI OpenSource driver, it is not needed to
\r
419 compile Psensor with this proprietary library.</p></div>
\r
422 <div class="sect1">
\r
423 <h2 id="S_WrongTemperature">3. The reported temperature is obviously wrong</h2>
\r
424 <div class="sectionbody">
\r
425 <div class="paragraph"><p>If the reported temperature is obviously wrong (never change, lower
\r
426 than the ambiant temperature, negative, higher than the sun
\r
427 temperature, etc):</p></div>
\r
428 <div class="ulist"><ul>
\r
431 most of the time it is not a bug in Psensor nor in the
\r
432 underlying monitoring libraries:
\r
434 <div class="ulist"><ul>
\r
437 if the temperature does not change, it might be due
\r
438 to an existent sensor not wired by the hardware
\r
444 the goal of the sensor is to allow the system to
\r
445 detect critical temperature and NOT to report an
\r
446 exact temperature. Most sensors report a relative
\r
447 temperature. The more it differs from the critical
\r
448 temperature , the more it is wrong.
\r
455 It is only a bug in Psensor if the underlying libraries
\r
456 report a different information than Psensor (use the
\r
457 appropriate command or software: ‘sensors’, ‘aticonfig’ or
\r
458 ‘hddtemp’ to check). In this case, please report a bug.
\r
464 <div class="sect1">
\r
465 <h2 id="S_WhatIsTheSensor">4. What is the sensors XXXX?</h2>
\r
466 <div class="sectionbody">
\r
467 <div class="paragraph"><p>Since Psensor v0.7.0.4, open the preferences of the sensor (click on
\r
468 its name in the main window and select the menu item Preferences), and
\r
469 look at the Chip field.</p></div>
\r
470 <div class="paragraph"><p>For older Psensor releases, look at the Id field, if the string is
\r
471 starting with:</p></div>
\r
472 <div class="ulist"><ul>
\r
475 ‘lmsensor coretemp’: Intel CPU.
\r
480 ‘lmsensor k10temp’,'lmsensor k8temp’,'lmsensor fam15h_power’: AMD CPU.
\r
485 ‘nvidia’ or ‘lmsensor nouveau’: NVIDIA GPU.
\r
490 ‘hdd’: hard disk drive.
\r
500 ‘lmsensor C B’: C is the name of the chip, B the name of the adapter.
\r
504 <div class="paragraph"><p>For more information about lmsensor devices, see
\r
505 <a href="http://lm-sensors.org/wiki/Devices">http://lm-sensors.org/wiki/Devices</a>.</p></div>
\r
508 <div class="sect1">
\r
509 <h2 id="S_BugReport">5. How to report a bug?</h2>
\r
510 <div class="sectionbody">
\r
511 <div class="paragraph"><p>Please use <a href="https://bugs.launchpad.net/psensor/+filebug">https://bugs.launchpad.net/psensor/+filebug</a> to report bugs
\r
512 even if it can only reproduced with a non-Ubuntu distribution or a
\r
513 release not available in the standard Ubuntu repositories.</p></div>
\r
514 <div class="paragraph"><p>You can also use
\r
515 <a href="https://bugs.launchpad.net/ubuntu/+source/psensor/+filebug">https://bugs.launchpad.net/ubuntu/+source/psensor/+filebug</a> if the bug
\r
516 can be reproduced with a package from the standard Ubuntu
\r
517 repositories.</p></div>
\r
518 <div class="paragraph"><p>If you don’t want to use the launchpad, you can send me the report by
\r
519 email to <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.</p></div>
\r
520 <div class="paragraph"><p>If the bug is concerning Debian or Ubuntu derivatives distribution,
\r
521 please add in its description the output of the command ‘apt-cache
\r
522 policy psensor’.</p></div>
\r
523 <div class="paragraph"><p>If it is related to the Psensor source compilation, please add the
\r
524 full output of the ‘configure’ command.</p></div>
\r
527 <div class="sect1">
\r
528 <h2 id="S_SubmitIdea">6. How to send ideas, questions or comments?</h2>
\r
529 <div class="sectionbody">
\r
530 <div class="paragraph"><p>Check the FAQ or the TODO pages.</p></div>
\r
531 <div class="paragraph"><p>If you don’t find the information, I am always happy to help, you can
\r
532 contact me:</p></div>
\r
533 <div class="ulist"><ul>
\r
536 by email: (<a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>), please add “[psensor]” in the
\r
537 subject, I speak English and French.
\r
542 or IRC: I am on the #psensor channel of the irc.freenode.net
\r
543 server. My nickname is “jfi”. Even if I am most of the time
\r
544 connected, I may not be in front of the computer or
\r
545 available, be patient!
\r
551 <div class="sect1">
\r
552 <h2 id="S_Contribute">7. How to contribute?</h2>
\r
553 <div class="sectionbody">
\r
554 <div class="paragraph"><p>See <a href="http://wpitchoune.net/blog/psensor/how-to-contribute/">http://wpitchoune.net/blog/psensor/how-to-contribute/</a>.</p></div>
\r
557 <div class="sect1">
\r
558 <h2 id="S_UbuntuInstall">8. How to install Psensor on Ubuntu?</h2>
\r
559 <div class="sectionbody">
\r
560 <div class="paragraph"><p>Psensor is in the official repository, search “psensor” in the software center and install it. More information at: <a href="http://wpitchoune.net/blog/psensor/ubuntu-integration/">http://wpitchoune.net/blog/psensor/ubuntu-integration/</a>.</p></div>
\r
563 <div class="sect1">
\r
564 <h2 id="S_DebianInstall">9. How to install Psensor on Debian?</h2>
\r
565 <div class="sectionbody">
\r
566 <div class="paragraph"><p>Psensor will be in the official repository since Debian 7.0. You can get the last packaged version from the sid repository. More information at: <a href="http://packages.qa.debian.org/p/psensor.html">http://packages.qa.debian.org/p/psensor.html</a>.</p></div>
\r
569 <div class="sect1">
\r
570 <h2 id="S_PPA">10. What is the difference between the 3 Ubuntu PPAs?</h2>
\r
571 <div class="sectionbody">
\r
572 <div class="ulist"><ul>
\r
575 ppa:jfi/ppa: last stable version.
\r
580 ppa:jfi/psensor-unstable: last development version, no major
\r
586 ppa:jfi/psensor-daily-trunk: build each day directly from
\r
587 the SVN source repository. It may contain major bugs or
\r
588 incomplete features. Useful for contributors or testing
\r
589 whether a bug is fixed.
\r
595 <div class="sect1">
\r
596 <h2 id="S_ArchLinuxInstall">11. How to install Psensor on ArchLinux?</h2>
\r
597 <div class="sectionbody">
\r
598 <div class="paragraph"><p>See <a href="http://aur.archlinux.org/packages.php?ID=37807">http://aur.archlinux.org/packages.php?ID=37807</a>.</p></div>
\r
601 <div class="sect1">
\r
602 <h2 id="S_OtherInstall">12. How to install Psensor on my Linux distribution?</h2>
\r
603 <div class="sectionbody">
\r
604 <div class="paragraph"><p>Psensor packages are available in the standard repositories of Ubuntu
\r
605 (since Oneiric) and Debian (since v7) distributions.</p></div>
\r
606 <div class="paragraph"><p>For other distributions, you will find the compilation and
\r
607 installation instructions in the section ‘Installation from source
\r
608 archive’ in the README file of the source archive. Psensor should
\r
609 compile in any modern distribution.</p></div>
\r
612 <div class="sect1">
\r
613 <h2 id="S_LOG">13. How to log sensors temperatures?</h2>
\r
614 <div class="sectionbody">
\r
615 <div class="paragraph"><p>The best way is probably to use sensord or a custom script based on
\r
616 the output of the different commands like sensors.</p></div>
\r
617 <div class="paragraph"><p>Anyway, as I received several requests about such feature, since the
\r
618 0.7.0.4 release it is implemented in both psensor ( menu preferences >
\r
619 sensors > enable log of measures) and psensor-server (–sensor-log-file
\r
623 <div class="sect1">
\r
624 <h2 id="S_SimilarSoft">14. Is there any other similar softwares?</h2>
\r
625 <div class="sectionbody">
\r
626 <div class="paragraph"><p>Here is a list of few well-known sensors monitoring softwares:</p></div>
\r
627 <div class="ulist"><ul>
\r
630 for X11: <a href="http://freecode.com/projects/xsensors">http://freecode.com/projects/xsensors</a>
\r
635 for GNOME2: <a href="http://sensors-applet.sourceforge.net/">http://sensors-applet.sourceforge.net/</a>
\r
640 for Ubuntu Unity: <a href="https://launchpad.net/indicator-sensors">https://launchpad.net/indicator-sensors</a>
\r
645 more general, but can be configured to display sensors
\r
646 information: <a href="http://conky.sourceforge.net/">http://conky.sourceforge.net/</a>
\r
653 <div id="footnotes"><hr /></div>
\r
655 <div id="footer-text">
\r
656 Last updated 2012-09-15 16:54:46 CEST
\r