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
11 background: #e2e2e2;
\r
13 font-family: Ubuntu,Arial,sans-serif;
\r
15 font-weight: lighter;
\r
16 margin: 1em 2em 2em 2em;
\r
22 margin: 0 0 0.267em 0;
\r
24 font-weight: normal;
\r
29 margin: 0 0 0.375em;
\r
31 font-weight: normal;
\r
36 margin: 0 0 0.522em;
\r
38 font-weight: normal;
\r
43 margin: 0 0 0.615em;
\r
45 font-weight: normal;
\r
56 font-weight: normal;
\r
58 letter-spacing: 0.1em;
\r
59 margin: 0 0 0.923em;
\r
60 text-transform: uppercase;
\r
80 text-decoration: none;
\r
84 text-decoration: underline;
\r
88 font-family: "Ubuntu Mono","Courier New",Courier,monospace;
\r
89 font-weight: normal;
\r
94 background: none repeat scroll 0 0 #e0e0e0;
\r
96 padding: 0.5em 0.5em;
\r
98 white-space: pre-wrap;
\r
99 word-wrap: break-word;
\r
110 font-weight: lighter;
\r
121 background: #ffffff;
\r
123 -moz-box-sizing: border-box;
\r
125 padding: 2em 2em 2em 2em;
\r
127 -moz-border-radius: 4px;
\r
128 -webkit-border-radius: 4px;
\r
129 border-radius: 4px;
\r
131 -webkit-box-shadow: 0 2px 2px 0 #C2C2C2;
\r
132 box-shadow: 0 2px 2px 0 #C2C2C2;
\r
136 background: #ffffff;
\r
137 -moz-box-sizing: border-box;
\r
138 padding: 2em 2em 2em 2em;
\r
140 -moz-border-radius: 4px;
\r
141 -webkit-border-radius: 4px;
\r
142 border-radius: 4px;
\r
144 -webkit-box-shadow: 0 2px 2px 0 #C2C2C2;
\r
145 box-shadow: 0 2px 2px 0 #C2C2C2;
\r
148 #menu-list, #menu-list > li > ul {
\r
149 list-style-type: none;
\r
152 /* menu on left col, content on right col */
\r
167 margin: 0em 0em 2em 0em;
\r
169 background: #ffffff;
\r
170 -moz-box-sizing: border-box;
\r
171 padding: 2em 2em 2em 2em;
\r
173 -moz-border-radius: 4px;
\r
174 -webkit-border-radius: 4px;
\r
175 border-radius: 4px;
\r
177 -webkit-box-shadow: 0 2px 2px 0 #C2C2C2;
\r
178 box-shadow: 0 2px 2px 0 #C2C2C2;
\r
181 <script type="text/javascript">
\r
183 var asciidoc = { // Namespace.
\r
185 /////////////////////////////////////////////////////////////////////
\r
186 // Table Of Contents generator
\r
187 /////////////////////////////////////////////////////////////////////
\r
189 /* Author: Mihai Bazon, September 2002
\r
190 * http://students.infoiasi.ro/~mishoo
\r
192 * Table Of Content generator
\r
195 * Feel free to use this script under the terms of the GNU General Public
\r
196 * License, as long as you do not remove or alter this notice.
\r
199 /* modified by Troy D. Hanson, September 2006. License: GPL */
\r
200 /* modified by Stuart Rackham, 2006, 2009. License: GPL */
\r
202 // toclevels = 1..4.
\r
203 toc: function (toclevels) {
\r
205 function getText(el) {
\r
207 for (var i = el.firstChild; i != null; i = i.nextSibling) {
\r
208 if (i.nodeType == 3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
\r
210 else if (i.firstChild != null)
\r
211 text += getText(i);
\r
216 function TocEntry(el, text, toclevel) {
\r
219 this.toclevel = toclevel;
\r
222 function tocEntries(el, toclevels) {
\r
223 var result = new Array;
\r
224 var re = new RegExp('[hH]([1-'+(toclevels+1)+'])');
\r
225 // Function that scans the DOM tree for header elements (the DOM2
\r
226 // nodeIterator API would be a better technique but not supported by all
\r
228 var iterate = function (el) {
\r
229 for (var i = el.firstChild; i != null; i = i.nextSibling) {
\r
230 if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
\r
231 var mo = re.exec(i.tagName);
\r
232 if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
\r
233 result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
\r
243 var toc = document.getElementById("toc");
\r
248 // Delete existing TOC entries in case we're reloading the TOC.
\r
249 var tocEntriesToRemove = [];
\r
251 for (i = 0; i < toc.childNodes.length; i++) {
\r
252 var entry = toc.childNodes[i];
\r
253 if (entry.nodeName.toLowerCase() == 'div'
\r
254 && entry.getAttribute("class")
\r
255 && entry.getAttribute("class").match(/^toclevel/))
\r
256 tocEntriesToRemove.push(entry);
\r
258 for (i = 0; i < tocEntriesToRemove.length; i++) {
\r
259 toc.removeChild(tocEntriesToRemove[i]);
\r
262 // Rebuild TOC entries.
\r
263 var entries = tocEntries(document.getElementById("content"), toclevels);
\r
264 for (var i = 0; i < entries.length; ++i) {
\r
265 var entry = entries[i];
\r
266 if (entry.element.id == "")
\r
267 entry.element.id = "_toc_" + i;
\r
268 var a = document.createElement("a");
\r
269 a.href = "#" + entry.element.id;
\r
270 a.appendChild(document.createTextNode(entry.text));
\r
271 var div = document.createElement("div");
\r
272 div.appendChild(a);
\r
273 div.className = "toclevel" + entry.toclevel;
\r
274 toc.appendChild(div);
\r
276 if (entries.length == 0)
\r
277 toc.parentNode.removeChild(toc);
\r
281 /////////////////////////////////////////////////////////////////////
\r
282 // Footnotes generator
\r
283 /////////////////////////////////////////////////////////////////////
\r
285 /* Based on footnote generation code from:
\r
286 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
\r
289 footnotes: function () {
\r
290 // Delete existing footnote entries in case we're reloading the footnodes.
\r
292 var noteholder = document.getElementById("footnotes");
\r
296 var entriesToRemove = [];
\r
297 for (i = 0; i < noteholder.childNodes.length; i++) {
\r
298 var entry = noteholder.childNodes[i];
\r
299 if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
\r
300 entriesToRemove.push(entry);
\r
302 for (i = 0; i < entriesToRemove.length; i++) {
\r
303 noteholder.removeChild(entriesToRemove[i]);
\r
306 // Rebuild footnote entries.
\r
307 var cont = document.getElementById("content");
\r
308 var spans = cont.getElementsByTagName("span");
\r
311 for (i=0; i<spans.length; i++) {
\r
312 if (spans[i].className == "footnote") {
\r
314 var note = spans[i].getAttribute("data-note");
\r
316 // Use [\s\S] in place of . so multi-line matches work.
\r
317 // Because JavaScript has no s (dotall) regex flag.
\r
318 note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
\r
319 spans[i].innerHTML =
\r
320 "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
\r
321 "' title='View footnote' class='footnote'>" + n + "</a>]";
\r
322 spans[i].setAttribute("data-note", note);
\r
324 noteholder.innerHTML +=
\r
325 "<div class='footnote' id='_footnote_" + n + "'>" +
\r
326 "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
\r
327 n + "</a>. " + note + "</div>";
\r
328 var id =spans[i].getAttribute("id");
\r
329 if (id != null) refs["#"+id] = n;
\r
333 noteholder.parentNode.removeChild(noteholder);
\r
335 // Process footnoterefs.
\r
336 for (i=0; i<spans.length; i++) {
\r
337 if (spans[i].className == "footnoteref") {
\r
338 var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
\r
339 href = href.match(/#.*/)[0]; // Because IE return full URL.
\r
341 spans[i].innerHTML =
\r
342 "[<a href='#_footnote_" + n +
\r
343 "' title='View footnote' class='footnote'>" + n + "</a>]";
\r
349 install: function(toclevels) {
\r
352 function reinstall() {
\r
353 asciidoc.footnotes();
\r
355 asciidoc.toc(toclevels);
\r
359 function reinstallAndRemoveTimer() {
\r
360 clearInterval(timerId);
\r
364 timerId = setInterval(reinstall, 500);
\r
365 if (document.addEventListener)
\r
366 document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
\r
368 window.onload = reinstallAndRemoveTimer;
\r
372 asciidoc.install(2);
\r
376 <body class="article">
\r
378 <h1>Psensor Frequently Asked Questions</h1>
\r
380 <div id="toctitle">Table of Contents</div>
381 <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
385 <div class="sect1">
\r
386 <h2 id="S_NoSensors">1. No sensors or only cpu usage is displayed</h2>
\r
387 <div class="sectionbody">
\r
388 <div class="paragraph"><p>Psensor is relying on few libraries or softwares for retrieving the information about the computer:</p></div>
\r
389 <div class="ulist"><ul>
\r
392 motherboard and CPUs sensors: the information is retrieved
\r
393 from the lm-sensors library, it requires that
\r
394 ‘sensors-detect’ has been run and the kernel module
\r
395 correctly installed. ‘sensors’ can be used for checking.
\r
400 GPUs: it depends on which driver you are using:
\r
402 <div class="ulist"><ul>
\r
405 Opensource drivers (nouveau for Nvidia GPUs or
\r
406 radeon/ati for ATI GPUs) is used and support sensor
\r
407 monitoring for your GPU, the information is using
\r
408 lm-sensors, same steps than above.
\r
413 proprietary driver Nvidia: run ‘nvidia-settings’ to
\r
414 check that it supports sensors monitoring.
\r
419 proprietary driver Catalyst/fglx: use ‘aticonfig’ to
\r
420 check that it supports sensors monitoring. Important
\r
421 note: it requires that you are using a Psensor
\r
422 binary compiled with the ATI support.
\r
429 HDDs: it uses the hddtemp daemon. Verifies that it is
\r
430 correctly reporting temperature by using the ‘sudo hddtemp
\r
431 /dev/sd?’ command. If hddtemp does not support your disk,
\r
432 you may want to try using the libatasmart support instead
\r
433 (option –use-libatasmart option).
\r
437 <div class="paragraph"><p>If the underlying software is reporting sensors which are not
\r
438 displayed by Psensor, it is probably a bug in Psensor, so please
\r
439 report it. Otherwise, the issue is on the underlying software itself
\r
440 and you should contact the corresponding development team or refer to
\r
441 its documentation.</p></div>
\r
444 <div class="sect1">
\r
445 <h2 id="S_ATIMonitoring">2. How to monitor an ATI card using the Catalyst driver?</h2>
\r
446 <div class="sectionbody">
\r
447 <div class="paragraph"><p>For monitoring ATI card using the proprietary Catalyst driver, Psensor
\r
448 must be compiled with a proprietary library which is not packaged in
\r
449 any Linux distribution.</p></div>
\r
450 <div class="paragraph"><p>Unfortunely, due to the license of this library, I cannot provide a
\r
451 compiled version of Psensor, even in a Ubuntu PPA or Ubuntu/Debian
\r
452 standard repositories. You have to compile Psensor sensor. You can
\r
453 find the instructions in the section “ATI/AMD GPU Support” of the
\r
454 README file available in the Psensor source archives.</p></div>
\r
455 <div class="paragraph"><p>If you are using the ATI OpenSource driver, it is not needed to
\r
456 compile Psensor with this proprietary library.</p></div>
\r
459 <div class="sect1">
\r
460 <h2 id="S_WrongTemperature">3. The reported temperature is obviously wrong</h2>
\r
461 <div class="sectionbody">
\r
462 <div class="paragraph"><p>If the reported temperature is obviously wrong (never change, lower
\r
463 than the ambiant temperature, negative, higher than the sun
\r
464 temperature, etc):</p></div>
\r
465 <div class="ulist"><ul>
\r
468 most of the time it is not a bug in Psensor nor in the
\r
469 underlying monitoring libraries:
\r
471 <div class="ulist"><ul>
\r
474 if the temperature does not change, it might be due
\r
475 to an existent sensor not wired by the hardware
\r
481 the goal of the sensor is to allow the system to
\r
482 detect critical temperature and NOT to report an
\r
483 exact temperature. Most sensors report a relative
\r
484 temperature. The more it differs from the critical
\r
485 temperature , the more it is wrong.
\r
492 It is only a bug in Psensor if the underlying libraries
\r
493 report a different information than Psensor (use the
\r
494 appropriate command or software: ‘sensors’, ‘aticonfig’ or
\r
495 ‘hddtemp’ to check). In this case, please report a bug.
\r
501 <div class="sect1">
\r
502 <h2 id="S_WhatIsTheSensor">4. What is the sensors XXXX?</h2>
\r
503 <div class="sectionbody">
\r
504 <div class="paragraph"><p>Since Psensor v0.7.0.4, open the preferences of the sensor (click on
\r
505 its name in the main window and select the menu item Preferences), and
\r
506 look at the Chip field.</p></div>
\r
507 <div class="paragraph"><p>For older Psensor releases, look at the Id field, if the string is
\r
508 starting with:</p></div>
\r
509 <div class="ulist"><ul>
\r
512 ‘lmsensor coretemp’: Intel CPU.
\r
517 ‘lmsensor k10temp’,'lmsensor k8temp’,'lmsensor fam15h_power’: AMD CPU.
\r
522 ‘nvidia’ or ‘lmsensor nouveau’: NVIDIA GPU.
\r
527 ‘hdd’: hard disk drive.
\r
537 ‘lmsensor C B’: C is the name of the chip, B the name of the adapter.
\r
541 <div class="paragraph"><p>For more information about lmsensor devices, see
\r
542 <a href="http://lm-sensors.org/wiki/Devices">http://lm-sensors.org/wiki/Devices</a>.</p></div>
\r
545 <div class="sect1">
\r
546 <h2 id="S_BugReport">5. How to report a bug?</h2>
\r
547 <div class="sectionbody">
\r
548 <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
549 even if it can only reproduced with a non-Ubuntu distribution or a
\r
550 release not available in the standard Ubuntu repositories.</p></div>
\r
551 <div class="paragraph"><p>You can also use
\r
552 <a href="https://bugs.launchpad.net/ubuntu/+source/psensor/+filebug">https://bugs.launchpad.net/ubuntu/+source/psensor/+filebug</a> if the bug
\r
553 can be reproduced with a package from the standard Ubuntu
\r
554 repositories.</p></div>
\r
555 <div class="paragraph"><p>If you don’t want to use the launchpad, you can send the report by
\r
556 email to:</p></div>
\r
557 <div class="ulist"><ul>
\r
560 <a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a> (require registration at:
\r
561 <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
566 or <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.
\r
570 <div class="paragraph"><p>If the bug is concerning Debian or Ubuntu derivatives distribution,
\r
571 please add in its description the output of the command ‘apt-cache
\r
572 policy psensor’.</p></div>
\r
573 <div class="paragraph"><p>If it is related to the Psensor source compilation, please add the
\r
574 full output of the ‘configure’ command.</p></div>
\r
577 <div class="sect1">
\r
578 <h2 id="S_SubmitIdea">6. How to send ideas, questions or comments?</h2>
\r
579 <div class="sectionbody">
\r
580 <div class="paragraph"><p>Check the FAQ or the TODO pages.</p></div>
\r
581 <div class="paragraph"><p>If you don’t find the information, you can send an email to the public
\r
582 mailing-list <a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a> (require registration at:
\r
583 <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
584 or send an email directly to me: <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.</p></div>
\r
587 <div class="sect1">
\r
588 <h2 id="S_Contribute">7. How to contribute?</h2>
\r
589 <div class="sectionbody">
\r
590 <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
593 <div class="sect1">
\r
594 <h2 id="S_UbuntuInstall">8. How to install Psensor on Ubuntu?</h2>
\r
595 <div class="sectionbody">
\r
596 <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
599 <div class="sect1">
\r
600 <h2 id="S_DebianInstall">9. How to install Psensor on Debian?</h2>
\r
601 <div class="sectionbody">
\r
602 <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
605 <div class="sect1">
\r
606 <h2 id="S_PPA">10. What is the difference between the 3 Ubuntu PPAs?</h2>
\r
607 <div class="sectionbody">
\r
608 <div class="ulist"><ul>
\r
611 ppa:jfi/ppa: last stable version.
\r
616 ppa:jfi/psensor-unstable: last development version, no major
\r
622 ppa:jfi/psensor-daily-trunk: build each day directly from
\r
623 the SVN source repository. It may contain major bugs or
\r
624 incomplete features. Useful for contributors or testing
\r
625 whether a bug is fixed.
\r
631 <div class="sect1">
\r
632 <h2 id="S_ArchLinuxInstall">11. How to install Psensor on ArchLinux?</h2>
\r
633 <div class="sectionbody">
\r
634 <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
637 <div class="sect1">
\r
638 <h2 id="S_OtherInstall">12. How to install Psensor on my Linux distribution?</h2>
\r
639 <div class="sectionbody">
\r
640 <div class="paragraph"><p>Psensor packages are available in the standard repositories of Ubuntu
\r
641 (since Oneiric) and Debian (since v7) distributions.</p></div>
\r
642 <div class="paragraph"><p>For other distributions, you will find the compilation and
\r
643 installation instructions in the section ‘Installation from source
\r
644 archive’ in the README file of the source archive. Psensor should
\r
645 compile in any modern distribution.</p></div>
\r
648 <div class="sect1">
\r
649 <h2 id="S_LOG">13. How to log sensors temperatures?</h2>
\r
650 <div class="sectionbody">
\r
651 <div class="paragraph"><p>The best way is probably to use sensord or a custom script based on
\r
652 the output of the different commands like sensors.</p></div>
\r
653 <div class="paragraph"><p>Anyway, as I received several requests about such feature, since the
\r
654 0.7.0.4 release it is implemented in both psensor ( menu preferences >
\r
655 sensors > enable log of measures) and psensor-server (–sensor-log-file
\r
659 <div class="sect1">
\r
660 <h2 id="S_NO_GRAPH_DISPLAYED">14. No graphs are displayed, but the table of the main window is displaying sensors</h2>
\r
661 <div class="sectionbody">
\r
662 <div class="paragraph"><p>In the sensors table of the main window, switch on the checkbox of the last
\r
663 column (named "Enabled" or "Graph" depending on the Psensor version).</p></div>
\r
666 <div class="sect1">
\r
667 <h2 id="S_SimilarSoft">15. Is there any other similar softwares?</h2>
\r
668 <div class="sectionbody">
\r
669 <div class="paragraph"><p>Here is a list of few well-known sensors monitoring softwares:</p></div>
\r
670 <div class="ulist"><ul>
\r
673 for X11: <a href="http://freecode.com/projects/xsensors">http://freecode.com/projects/xsensors</a>
\r
678 for GNOME2: <a href="http://sensors-applet.sourceforge.net/">http://sensors-applet.sourceforge.net/</a>
\r
683 for Ubuntu Unity: <a href="https://launchpad.net/indicator-sensors">https://launchpad.net/indicator-sensors</a>
\r
688 more general, but can be configured to display sensors
\r
689 information: <a href="http://conky.sourceforge.net/">http://conky.sourceforge.net/</a>
\r
696 <div id="footnotes"><hr /></div>
\r
698 <div id="footer-text">
\r
699 Last updated 2014-04-10 01:57:33 CEST
\r