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.7" />
\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
123 font-style: normal;
\r
127 font-weight: normal;
\r
131 text-transform: uppercase;
\r
135 padding-bottom: 1em;
\r
139 padding: 0 0 0 0em;
\r
143 <script type="text/javascript">
\r
145 var asciidoc = { // Namespace.
\r
147 /////////////////////////////////////////////////////////////////////
\r
148 // Table Of Contents generator
\r
149 /////////////////////////////////////////////////////////////////////
\r
151 /* Author: Mihai Bazon, September 2002
\r
152 * http://students.infoiasi.ro/~mishoo
\r
154 * Table Of Content generator
\r
157 * Feel free to use this script under the terms of the GNU General Public
\r
158 * License, as long as you do not remove or alter this notice.
\r
161 /* modified by Troy D. Hanson, September 2006. License: GPL */
\r
162 /* modified by Stuart Rackham, 2006, 2009. License: GPL */
\r
164 // toclevels = 1..4.
\r
165 toc: function (toclevels) {
\r
167 function getText(el) {
\r
169 for (var i = el.firstChild; i != null; i = i.nextSibling) {
\r
170 if (i.nodeType == 3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
\r
172 else if (i.firstChild != null)
\r
173 text += getText(i);
\r
178 function TocEntry(el, text, toclevel) {
\r
181 this.toclevel = toclevel;
\r
184 function tocEntries(el, toclevels) {
\r
185 var result = new Array;
\r
186 var re = new RegExp('[hH]([1-'+(toclevels+1)+'])');
\r
187 // Function that scans the DOM tree for header elements (the DOM2
\r
188 // nodeIterator API would be a better technique but not supported by all
\r
190 var iterate = function (el) {
\r
191 for (var i = el.firstChild; i != null; i = i.nextSibling) {
\r
192 if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
\r
193 var mo = re.exec(i.tagName);
\r
194 if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
\r
195 result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
\r
205 var toc = document.getElementById("toc");
\r
210 // Delete existing TOC entries in case we're reloading the TOC.
\r
211 var tocEntriesToRemove = [];
\r
213 for (i = 0; i < toc.childNodes.length; i++) {
\r
214 var entry = toc.childNodes[i];
\r
215 if (entry.nodeName.toLowerCase() == 'div'
\r
216 && entry.getAttribute("class")
\r
217 && entry.getAttribute("class").match(/^toclevel/))
\r
218 tocEntriesToRemove.push(entry);
\r
220 for (i = 0; i < tocEntriesToRemove.length; i++) {
\r
221 toc.removeChild(tocEntriesToRemove[i]);
\r
224 // Rebuild TOC entries.
\r
225 var entries = tocEntries(document.getElementById("content"), toclevels);
\r
226 for (var i = 0; i < entries.length; ++i) {
\r
227 var entry = entries[i];
\r
228 if (entry.element.id == "")
\r
229 entry.element.id = "_toc_" + i;
\r
230 var a = document.createElement("a");
\r
231 a.href = "#" + entry.element.id;
\r
232 a.appendChild(document.createTextNode(entry.text));
\r
233 var div = document.createElement("div");
\r
234 div.appendChild(a);
\r
235 div.className = "toclevel" + entry.toclevel;
\r
236 toc.appendChild(div);
\r
238 if (entries.length == 0)
\r
239 toc.parentNode.removeChild(toc);
\r
243 /////////////////////////////////////////////////////////////////////
\r
244 // Footnotes generator
\r
245 /////////////////////////////////////////////////////////////////////
\r
247 /* Based on footnote generation code from:
\r
248 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
\r
251 footnotes: function () {
\r
252 // Delete existing footnote entries in case we're reloading the footnodes.
\r
254 var noteholder = document.getElementById("footnotes");
\r
258 var entriesToRemove = [];
\r
259 for (i = 0; i < noteholder.childNodes.length; i++) {
\r
260 var entry = noteholder.childNodes[i];
\r
261 if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
\r
262 entriesToRemove.push(entry);
\r
264 for (i = 0; i < entriesToRemove.length; i++) {
\r
265 noteholder.removeChild(entriesToRemove[i]);
\r
268 // Rebuild footnote entries.
\r
269 var cont = document.getElementById("content");
\r
270 var spans = cont.getElementsByTagName("span");
\r
273 for (i=0; i<spans.length; i++) {
\r
274 if (spans[i].className == "footnote") {
\r
276 var note = spans[i].getAttribute("data-note");
\r
278 // Use [\s\S] in place of . so multi-line matches work.
\r
279 // Because JavaScript has no s (dotall) regex flag.
\r
280 note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
\r
281 spans[i].innerHTML =
\r
282 "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
\r
283 "' title='View footnote' class='footnote'>" + n + "</a>]";
\r
284 spans[i].setAttribute("data-note", note);
\r
286 noteholder.innerHTML +=
\r
287 "<div class='footnote' id='_footnote_" + n + "'>" +
\r
288 "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
\r
289 n + "</a>. " + note + "</div>";
\r
290 var id =spans[i].getAttribute("id");
\r
291 if (id != null) refs["#"+id] = n;
\r
295 noteholder.parentNode.removeChild(noteholder);
\r
297 // Process footnoterefs.
\r
298 for (i=0; i<spans.length; i++) {
\r
299 if (spans[i].className == "footnoteref") {
\r
300 var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
\r
301 href = href.match(/#.*/)[0]; // Because IE return full URL.
\r
303 spans[i].innerHTML =
\r
304 "[<a href='#_footnote_" + n +
\r
305 "' title='View footnote' class='footnote'>" + n + "</a>]";
\r
311 install: function(toclevels) {
\r
314 function reinstall() {
\r
315 asciidoc.footnotes();
\r
317 asciidoc.toc(toclevels);
\r
321 function reinstallAndRemoveTimer() {
\r
322 clearInterval(timerId);
\r
326 timerId = setInterval(reinstall, 500);
\r
327 if (document.addEventListener)
\r
328 document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
\r
330 window.onload = reinstallAndRemoveTimer;
\r
334 asciidoc.install(2);
\r
338 <body class="article">
\r
340 <h1>Psensor Frequently Asked Questions</h1>
\r
342 <div id="toctitle">Table of Contents</div>
343 <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
347 <div class="sect1">
\r
348 <h2 id="S_NoSensors">1. No sensors or only cpu usage is displayed</h2>
\r
349 <div class="sectionbody">
\r
350 <div class="paragraph"><p>Psensor is relying on few libraries or softwares for retrieving the information about the computer:</p></div>
\r
351 <div class="ulist"><ul>
\r
354 motherboard and CPUs sensors: the information is retrieved
\r
355 from the lm-sensors library, it requires that
\r
356 ‘sensors-detect’ has been run and the kernel module
\r
357 correctly installed. ‘sensors’ can be used for checking.
\r
362 GPUs: it depends on which driver you are using:
\r
364 <div class="ulist"><ul>
\r
367 Opensource drivers (nouveau for Nvidia GPUs or
\r
368 radeon/ati for ATI GPUs) is used and support sensor
\r
369 monitoring for your GPU, the information is using
\r
370 lm-sensors, same steps than above.
\r
375 proprietary driver Nvidia: run ‘nvidia-settings’ to
\r
376 check that it supports sensors monitoring.
\r
381 proprietary driver Catalyst/fglx: use ‘aticonfig’ to
\r
382 check that it supports sensors monitoring. Important
\r
383 note: it requires that you are using a Psensor
\r
384 binary compiled with the ATI support.
\r
391 HDDs: it uses the hddtemp daemon. Verifies that it is
\r
392 correctly reporting temperature by using the ‘sudo hddtemp
\r
393 /dev/sd?’ command. If hddtemp does not support your disk,
\r
394 you may want to try using the libatasmart support instead
\r
395 (option –use-libatasmart option).
\r
399 <div class="paragraph"><p>If the underlying software is reporting sensors which are not
\r
400 displayed by Psensor, it is probably a bug in Psensor, so please
\r
401 report it. Otherwise, the issue is on the underlying software itself
\r
402 and you should contact the corresponding development team or refer to
\r
403 its documentation.</p></div>
\r
406 <div class="sect1">
\r
407 <h2 id="S_ATIMonitoring">2. How to monitor an ATI card using the Catalyst driver?</h2>
\r
408 <div class="sectionbody">
\r
409 <div class="paragraph"><p>For monitoring ATI card using the proprietary Catalyst driver, Psensor
\r
410 must be compiled with a proprietary library which is not packaged in
\r
411 any Linux distribution.</p></div>
\r
412 <div class="paragraph"><p>Unfortunely, due to the license of this library, I cannot provide a
\r
413 compiled version of Psensor, even in a Ubuntu PPA or Ubuntu/Debian
\r
414 standard repositories. You have to compile Psensor sensor. You can
\r
415 find the instructions in the section “ATI/AMD GPU Support” of the
\r
416 README file available in the Psensor source archives.</p></div>
\r
417 <div class="paragraph"><p>If you are using the ATI OpenSource driver, it is not needed to
\r
418 compile Psensor with this proprietary library.</p></div>
\r
421 <div class="sect1">
\r
422 <h2 id="S_WrongTemperature">3. The reported temperature is obviously wrong</h2>
\r
423 <div class="sectionbody">
\r
424 <div class="paragraph"><p>If the reported temperature is obviously wrong (never change, lower
\r
425 than the ambiant temperature, negative, higher than the sun
\r
426 temperature, etc):</p></div>
\r
427 <div class="ulist"><ul>
\r
430 most of the time it is not a bug in Psensor nor in the
\r
431 underlying monitoring libraries:
\r
433 <div class="ulist"><ul>
\r
436 if the temperature does not change, it might be due
\r
437 to an existent sensor not wired by the hardware
\r
443 the goal of the sensor is to allow the system to
\r
444 detect critical temperature and NOT to report an
\r
445 exact temperature. Most sensors report a relative
\r
446 temperature. The more it differs from the critical
\r
447 temperature , the more it is wrong.
\r
454 It is only a bug in Psensor if the underlying libraries
\r
455 report a different information than Psensor (use the
\r
456 appropriate command or software: ‘sensors’, ‘aticonfig’ or
\r
457 ‘hddtemp’ to check). In this case, please report a bug.
\r
463 <div class="sect1">
\r
464 <h2 id="S_WhatIsTheSensor">4. What is the sensors XXXX?</h2>
\r
465 <div class="sectionbody">
\r
466 <div class="paragraph"><p>Since Psensor v0.7.0.4, open the preferences of the sensor (click on
\r
467 its name in the main window and select the menu item Preferences), and
\r
468 look at the Chip field.</p></div>
\r
469 <div class="paragraph"><p>For older Psensor releases, look at the Id field, if the string is
\r
470 starting with:</p></div>
\r
471 <div class="ulist"><ul>
\r
474 ‘lmsensor coretemp’: Intel CPU.
\r
479 ‘lmsensor k10temp’,'lmsensor k8temp’,'lmsensor fam15h_power’: AMD CPU.
\r
484 ‘nvidia’ or ‘lmsensor nouveau’: NVIDIA GPU.
\r
489 ‘hdd’: hard disk drive.
\r
499 ‘lmsensor C B’: C is the name of the chip, B the name of the adapter.
\r
503 <div class="paragraph"><p>For more information about lmsensor devices, see
\r
504 <a href="http://lm-sensors.org/wiki/Devices">http://lm-sensors.org/wiki/Devices</a>.</p></div>
\r
507 <div class="sect1">
\r
508 <h2 id="S_BugReport">5. How to report a bug?</h2>
\r
509 <div class="sectionbody">
\r
510 <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
511 even if it can only reproduced with a non-Ubuntu distribution or a
\r
512 release not available in the standard Ubuntu repositories.</p></div>
\r
513 <div class="paragraph"><p>You can also use
\r
514 <a href="https://bugs.launchpad.net/ubuntu/+source/psensor/+filebug">https://bugs.launchpad.net/ubuntu/+source/psensor/+filebug</a> if the bug
\r
515 can be reproduced with a package from the standard Ubuntu
\r
516 repositories.</p></div>
\r
517 <div class="paragraph"><p>If you don’t want to use the launchpad, you can send the report by
\r
518 email to:</p></div>
\r
519 <div class="ulist"><ul>
\r
522 <a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a> (require registration at:
\r
523 <a href="https://groups.google.com/forum/?fromgroups&hl=en#!forum/psensor-users">https://groups.google.com/forum/?fromgroups&hl=en#!forum/psensor-users</a>)
\r
528 or <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.
\r
532 <div class="paragraph"><p>If the bug is concerning Debian or Ubuntu derivatives distribution,
\r
533 please add in its description the output of the command ‘apt-cache
\r
534 policy psensor’.</p></div>
\r
535 <div class="paragraph"><p>If it is related to the Psensor source compilation, please add the
\r
536 full output of the ‘configure’ command.</p></div>
\r
539 <div class="sect1">
\r
540 <h2 id="S_SubmitIdea">6. How to send ideas, questions or comments?</h2>
\r
541 <div class="sectionbody">
\r
542 <div class="paragraph"><p>Check the FAQ or the TODO pages.</p></div>
\r
543 <div class="paragraph"><p>If you don’t find the information, you can send an email to the public
\r
544 mailing-list <a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a> (require registration at:
\r
545 <a href="https://groups.google.com/forum/?fromgroups&hl=en#!forum/psensor-users">https://groups.google.com/forum/?fromgroups&hl=en#!forum/psensor-users</a>)
\r
546 or send an email directly to me: <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.</p></div>
\r
549 <div class="sect1">
\r
550 <h2 id="S_Contribute">7. How to contribute?</h2>
\r
551 <div class="sectionbody">
\r
552 <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
555 <div class="sect1">
\r
556 <h2 id="S_UbuntuInstall">8. How to install Psensor on Ubuntu?</h2>
\r
557 <div class="sectionbody">
\r
558 <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
561 <div class="sect1">
\r
562 <h2 id="S_DebianInstall">9. How to install Psensor on Debian?</h2>
\r
563 <div class="sectionbody">
\r
564 <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
567 <div class="sect1">
\r
568 <h2 id="S_PPA">10. What is the difference between the 3 Ubuntu PPAs?</h2>
\r
569 <div class="sectionbody">
\r
570 <div class="ulist"><ul>
\r
573 ppa:jfi/ppa: last stable version.
\r
578 ppa:jfi/psensor-unstable: last development version, no major
\r
584 ppa:jfi/psensor-daily-trunk: build each day directly from
\r
585 the SVN source repository. It may contain major bugs or
\r
586 incomplete features. Useful for contributors or testing
\r
587 whether a bug is fixed.
\r
593 <div class="sect1">
\r
594 <h2 id="S_ArchLinuxInstall">11. How to install Psensor on ArchLinux?</h2>
\r
595 <div class="sectionbody">
\r
596 <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
599 <div class="sect1">
\r
600 <h2 id="S_OtherInstall">12. How to install Psensor on my Linux distribution?</h2>
\r
601 <div class="sectionbody">
\r
602 <div class="paragraph"><p>Psensor packages are available in the standard repositories of Ubuntu
\r
603 (since Oneiric) and Debian (since v7) distributions.</p></div>
\r
604 <div class="paragraph"><p>For other distributions, you will find the compilation and
\r
605 installation instructions in the section ‘Installation from source
\r
606 archive’ in the README file of the source archive. Psensor should
\r
607 compile in any modern distribution.</p></div>
\r
610 <div class="sect1">
\r
611 <h2 id="S_LOG">13. How to log sensors temperatures?</h2>
\r
612 <div class="sectionbody">
\r
613 <div class="paragraph"><p>The best way is probably to use sensord or a custom script based on
\r
614 the output of the different commands like sensors.</p></div>
\r
615 <div class="paragraph"><p>Anyway, as I received several requests about such feature, since the
\r
616 0.7.0.4 release it is implemented in both psensor ( menu preferences >
\r
617 sensors > enable log of measures) and psensor-server (–sensor-log-file
\r
621 <div class="sect1">
\r
622 <h2 id="S_NO_GRAPH_DISPLAYED">14. No graphs are displayed, but the table of the main window is displaying sensors</h2>
\r
623 <div class="sectionbody">
\r
624 <div class="paragraph"><p>In the sensors table of the main window, switch on the checkbox of the last
\r
625 column (named "Enabled" or "Graph" depending on the Psensor version).</p></div>
\r
628 <div class="sect1">
\r
629 <h2 id="S_SimilarSoft">15. Is there any other similar softwares?</h2>
\r
630 <div class="sectionbody">
\r
631 <div class="paragraph"><p>Here is a list of few well-known sensors monitoring softwares:</p></div>
\r
632 <div class="ulist"><ul>
\r
635 for X11: <a href="http://freecode.com/projects/xsensors">http://freecode.com/projects/xsensors</a>
\r
640 for GNOME2: <a href="http://sensors-applet.sourceforge.net/">http://sensors-applet.sourceforge.net/</a>
\r
645 for Ubuntu Unity: <a href="https://launchpad.net/indicator-sensors">https://launchpad.net/indicator-sensors</a>
\r
650 more general, but can be configured to display sensors
\r
651 information: <a href="http://conky.sourceforge.net/">http://conky.sourceforge.net/</a>
\r
658 <div id="footnotes"><hr /></div>
\r
660 <div id="footer-text">
\r
661 Last updated 2013-05-12 17:54:35 CEST
\r