--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"\r
+ "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">\r
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">\r
+<head>\r
+<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />\r
+<meta name="generator" content="AsciiDoc 8.6.7" />\r
+<title>Psensor Frequently Asked Questions</title>\r
+<style type="text/css">\r
+body {\r
+ padding: 1em 1em 1em 1em;\r
+ font-family: "Ubuntu", sans-serif;\r
+ font-size: 100%;\r
+ font-style: normal;\r
+ font-weight: normal;\r
+ color: #000;\r
+ background-color: #fff;\r
+ margin: 0 0 0 0;\r
+}\r
+\r
+a {\r
+ color: #1982D1;\r
+ font-style: normal;\r
+ text-decoration: none;\r
+}\r
+\r
+a:hover {\r
+ text-decoration: underline;\r
+}\r
+\r
+h1 {\r
+ font-size: 140%;\r
+ font-style: normal;\r
+ font-weight: bold;\r
+ text-transform: uppercase;\r
+ margin: 0 0 1em 0;\r
+ padding: 0 0 0 0;\r
+}\r
+\r
+\r
+h2, #toctitle{\r
+ font-size: 110%;\r
+ font-style: normal;\r
+ font-weight: bold;\r
+ text-transform: uppercase;\r
+ margin: 2em 0em 1em 0em;\r
+ padding: 0 0 0 0;\r
+}\r
+\r
+#footer {\r
+ padding-top: 2em;\r
+ color: #666;\r
+ clear: both;\r
+ text-align: right;\r
+ font-size: 75%;\r
+}\r
+\r
+p {\r
+ font-size: 100%;\r
+ margin-bottom: 8px;\r
+}\r
+\r
+table {\r
+ text-align: left;\r
+ padding: 0 0 0 0;\r
+ min-width: 50%;\r
+ border-spacing: 0;\r
+ border: 0;\r
+}\r
+\r
+thead {\r
+ background-color: #000;\r
+ color: #fff;\r
+ padding: 0 0 0 0;\r
+}\r
+\r
+tbody {\r
+ padding: 0 0 0 0;\r
+}\r
+\r
+th {\r
+ padding: 0.25em 0.5em 0.25em 0.5em;\r
+ font-style: normal;\r
+ font-weight: normal;\r
+}\r
+\r
+td {\r
+ padding: 0.25em 0.25em 0em 0.25em;\r
+}\r
+\r
+#chart {\r
+ color: #000;\r
+ font-style: normal;\r
+ font-weight: normal;\r
+ width: 100%;\r
+ height: 300px;\r
+}\r
+\r
+ul#menu-list li {\r
+ list-style: none;\r
+}\r
+\r
+#menu-list {\r
+ padding: 0 0 0 0;\r
+ margin: 0 0 0 0;\r
+}\r
+\r
+#menu {\r
+ float: left;\r
+ width: 20%;\r
+ padding: 0 0 0 0;\r
+ margin: 0 0 0 0;\r
+}\r
+\r
+#main {\r
+ float: right;\r
+ width: 80%;\r
+ padding: 0 0 0 0;\r
+ margin: 0 0em 0 0;\r
+}\r
+\r
+em {\r
+ font-weight: bold;\r
+ font-style: normal;\r
+}\r
+\r
+#uptime {\r
+ font-weight: normal;\r
+}\r
+\r
+#menu-list em {\r
+ text-transform: uppercase;\r
+}\r
+\r
+#menu ul li {\r
+ padding-bottom: 1em;\r
+}\r
+\r
+#menu-list ul li {\r
+ padding: 0 0 0 0em;\r
+}\r
+\r
+</style>\r
+<script type="text/javascript">\r
+/*<+'])');\r
+ // Function that scans the DOM tree for header elements (the DOM2\r
+ // nodeIterator API would be a better technique but not supported by all\r
+ // browsers).\r
+ var iterate = function (el) {\r
+ for (var i = el.firstChild; i != null; i = i.nextSibling) {\r
+ if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {\r
+ var mo = re.exec(i.tagName);\r
+ if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {\r
+ result[result.length] = new TocEntry(i, getText(i), mo[1]-1);\r
+ }\r
+ iterate(i);\r
+ }\r
+ }\r
+ }\r
+ iterate(el);\r
+ return result;\r
+ }\r
+\r
+ var toc = document.getElementById("toc");\r
+ if (!toc) {\r
+ return;\r
+ }\r
+\r
+ // Delete existing TOC entries in case we're reloading the TOC.\r
+ var tocEntriesToRemove = [];\r
+ var i;\r
+ for (i = 0; i < toc.childNodes.length; i++) {\r
+ var entry = toc.childNodes[i];\r
+ if (entry.nodeName.toLowerCase() == 'div'\r
+ && entry.getAttribute("class")\r
+ && entry.getAttribute("class").match(/^toclevel/))\r
+ tocEntriesToRemove.push(entry);\r
+ }\r
+ for (i = 0; i < tocEntriesToRemove.length; i++) {\r
+ toc.removeChild(tocEntriesToRemove[i]);\r
+ }\r
+\r
+ // Rebuild TOC entries.\r
+ var entries = tocEntries(document.getElementById("content"), toclevels);\r
+ for (var i = 0; i < entries.length; ++i) {\r
+ var entry = entries[i];\r
+ if (entry.element.id == "")\r
+ entry.element.id = "_toc_" + i;\r
+ var a = document.createElement("a");\r
+ a.href = "#" + entry.element.id;\r
+ a.appendChild(document.createTextNode(entry.text));\r
+ var div = document.createElement("div");\r
+ div.appendChild(a);\r
+ div.className = "toclevel" + entry.toclevel;\r
+ toc.appendChild(div);\r
+ }\r
+ if (entries.length == 0)\r
+ toc.parentNode.removeChild(toc);\r
+},\r
+\r
+\r
+/////////////////////////////////////////////////////////////////////\r
+// Footnotes generator\r
+/////////////////////////////////////////////////////////////////////\r
+\r
+/* Based on footnote generation code from:\r
+ * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html\r
+ */\r
+\r
+footnotes: function () {\r
+ // Delete existing footnote entries in case we're reloading the footnodes.\r
+ var i;\r
+ var noteholder = document.getElementById("footnotes");\r
+ if (!noteholder) {\r
+ return;\r
+ }\r
+ var entriesToRemove = [];\r
+ for (i = 0; i < noteholder.childNodes.length; i++) {\r
+ var entry = noteholder.childNodes[i];\r
+ if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")\r
+ entriesToRemove.push(entry);\r
+ }\r
+ for (i = 0; i < entriesToRemove.length; i++) {\r
+ noteholder.removeChild(entriesToRemove[i]);\r
+ }\r
+\r
+ // Rebuild footnote entries.\r
+ var cont = document.getElementById("content");\r
+ var spans = cont.getElementsByTagName("span");\r
+ var refs = {};\r
+ var n = 0;\r
+ for (i=0; i<spans.length; i++) {\r
+ if (spans[i].className == "footnote") {\r
+ n++;\r
+ var note = spans[i].getAttribute("data-note");\r
+ if (!note) {\r
+ // Use [\s\S] in place of . so multi-line matches work.\r
+ // Because JavaScript has no s (dotall) regex flag.\r
+ note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];\r
+ spans[i].innerHTML =\r
+ "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +\r
+ "' title='View footnote' class='footnote'>" + n + "</a>]";\r
+ spans[i].setAttribute("data-note", note);\r
+ }\r
+ noteholder.innerHTML +=\r
+ "<div class='footnote' id='_footnote_" + n + "'>" +\r
+ "<a href='#_footnoteref_" + n + "' title='Return to text'>" +\r
+ n + "</a>. " + note + "</div>";\r
+ var id =spans[i].getAttribute("id");\r
+ if (id != null) refs["#"+id] = n;\r
+ }\r
+ }\r
+ if (n == 0)\r
+ noteholder.parentNode.removeChild(noteholder);\r
+ else {\r
+ // Process footnoterefs.\r
+ for (i=0; i<spans.length; i++) {\r
+ if (spans[i].className == "footnoteref") {\r
+ var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");\r
+ href = href.match(/#.*/)[0]; // Because IE return full URL.\r
+ n = refs[href];\r
+ spans[i].innerHTML =\r
+ "[<a href='#_footnote_" + n +\r
+ "' title='View footnote' class='footnote'>" + n + "</a>]";\r
+ }\r
+ }\r
+ }\r
+},\r
+\r
+install: function(toclevels) {\r
+ var timerId;\r
+\r
+ function reinstall() {\r
+ asciidoc.footnotes();\r
+ if (toclevels) {\r
+ asciidoc.toc(toclevels);\r
+ }\r
+ }\r
+\r
+ function reinstallAndRemoveTimer() {\r
+ clearInterval(timerId);\r
+ reinstall();\r
+ }\r
+\r
+ timerId = setInterval(reinstall, 500);\r
+ if (document.addEventListener)\r
+ document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);\r
+ else\r
+ window.onload = reinstallAndRemoveTimer;\r
+}\r
+\r
+}\r
+asciidoc.install(2);\r
+/*]]>*/\r
+</script>\r
+</head>\r
+<body class="article">\r
+<div id="header">\r
+<h1>Psensor Frequently Asked Questions</h1>\r
+<div id="toc">
+ <div id="toctitle">Table of Contents</div>
+ <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
+</div>\r
+</div>\r
+<div id="content">\r
+<div class="sect1">\r
+<h2 id="S_NoSensors">1. No sensors or only cpu usage is displayed</h2>\r
+<div class="sectionbody">\r
+<div class="paragraph"><p>Psensor is relying on few libraries or softwares for retrieving the information about the computer:</p></div>\r
+<div class="ulist"><ul>\r
+<li>\r
+<p>\r
+motherboard and CPUs sensors: the information is retrieved\r
+ from the lm-sensors library, it requires that\r
+ ‘sensors-detect’ has been run and the kernel module\r
+ correctly installed. ‘sensors’ can be used for checking.\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+GPUs: it depends on which driver you are using:\r
+</p>\r
+<div class="ulist"><ul>\r
+<li>\r
+<p>\r
+Opensource drivers (nouveau for Nvidia GPUs or\r
+ radeon/ati for ATI GPUs) is used and support sensor\r
+ monitoring for your GPU, the information is using\r
+ lm-sensors, same steps than above.\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+proprietary driver Nvidia: run ‘nvidia-settings’ to\r
+ check that it supports sensors monitoring.\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+proprietary driver Catalyst/fglx: use ‘aticonfig’ to\r
+ check that it supports sensors monitoring. Important\r
+ note: it requires that you are using a Psensor\r
+ binary compiled with the ATI support.\r
+</p>\r
+</li>\r
+</ul></div>\r
+</li>\r
+<li>\r
+<p>\r
+HDDs: it uses the hddtemp daemon. Verifies that it is\r
+ correctly reporting temperature by using the ‘sudo hddtemp\r
+ /dev/sd?’ command. If hddtemp does not support your disk,\r
+ you may want to try using the libatasmart support instead\r
+ (option –use-libatasmart option).\r
+</p>\r
+</li>\r
+</ul></div>\r
+<div class="paragraph"><p>If the underlying software is reporting sensors which are not\r
+displayed by Psensor, it is probably a bug in Psensor, so please\r
+report it. Otherwise, the issue is on the underlying software itself\r
+and you should contact the corresponding development team or refer to\r
+its documentation.</p></div>\r
+</div>\r
+</div>\r
+<div class="sect1">\r
+<h2 id="S_ATIMonitoring">2. How to monitor an ATI card using the Catalyst driver?</h2>\r
+<div class="sectionbody">\r
+<div class="paragraph"><p>For monitoring ATI card using the proprietary Catalyst driver, Psensor\r
+must be compiled with a proprietary library which is not packaged in\r
+any Linux distribution.</p></div>\r
+<div class="paragraph"><p>Unfortunely, due to the license of this library, I cannot provide a\r
+compiled version of Psensor, even in a Ubuntu PPA or Ubuntu/Debian\r
+standard repositories. You have to compile Psensor sensor. You can\r
+find the instructions in the section “ATI/AMD GPU Support” of the\r
+README file available in the Psensor source archives.</p></div>\r
+<div class="paragraph"><p>If you are using the ATI OpenSource driver, it is not needed to\r
+compile Psensor with this proprietary library.</p></div>\r
+</div>\r
+</div>\r
+<div class="sect1">\r
+<h2 id="S_WrongTemperature">3. The reported temperature is obviously wrong</h2>\r
+<div class="sectionbody">\r
+<div class="paragraph"><p>If the reported temperature is obviously wrong (never change, lower\r
+than the ambiant temperature, negative, higher than the sun\r
+temperature, etc):</p></div>\r
+<div class="ulist"><ul>\r
+<li>\r
+<p>\r
+most of the time it is not a bug in Psensor nor in the\r
+ underlying monitoring libraries:\r
+</p>\r
+<div class="ulist"><ul>\r
+<li>\r
+<p>\r
+if the temperature does not change, it might be due\r
+ to an existent sensor not wired by the hardware\r
+ manufacturer.\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+the goal of the sensor is to allow the system to\r
+ detect critical temperature and NOT to report an\r
+ exact temperature. Most sensors report a relative\r
+ temperature. The more it differs from the critical\r
+ temperature , the more it is wrong.\r
+</p>\r
+</li>\r
+</ul></div>\r
+</li>\r
+<li>\r
+<p>\r
+It is only a bug in Psensor if the underlying libraries\r
+ report a different information than Psensor (use the\r
+ appropriate command or software: ‘sensors’, ‘aticonfig’ or\r
+ ‘hddtemp’ to check). In this case, please report a bug.\r
+</p>\r
+</li>\r
+</ul></div>\r
+</div>\r
+</div>\r
+<div class="sect1">\r
+<h2 id="S_WhatIsTheSensor">4. What is the sensors XXXX?</h2>\r
+<div class="sectionbody">\r
+<div class="paragraph"><p>Since Psensor v0.7.0.4, open the preferences of the sensor (click on\r
+its name in the main window and select the menu item Preferences), and\r
+look at the Chip field.</p></div>\r
+<div class="paragraph"><p>For older Psensor releases, look at the Id field, if the string is\r
+starting with:</p></div>\r
+<div class="ulist"><ul>\r
+<li>\r
+<p>\r
+‘lmsensor coretemp’: Intel CPU.\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+‘lmsensor k10temp’,'lmsensor k8temp’,'lmsensor fam15h_power’: AMD CPU.\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+‘nvidia’ or ‘lmsensor nouveau’: NVIDIA GPU.\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+‘hdd’: hard disk drive.\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+‘amd’: AMD GPU.\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+‘lmsensor C B’: C is the name of the chip, B the name of the adapter.\r
+</p>\r
+</li>\r
+</ul></div>\r
+<div class="paragraph"><p>For more information about lmsensor devices, see\r
+<a href="http://lm-sensors.org/wiki/Devices">http://lm-sensors.org/wiki/Devices</a>.</p></div>\r
+</div>\r
+</div>\r
+<div class="sect1">\r
+<h2 id="S_BugReport">5. How to report a bug?</h2>\r
+<div class="sectionbody">\r
+<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
+even if it can only reproduced with a non-Ubuntu distribution or a\r
+release not available in the standard Ubuntu repositories.</p></div>\r
+<div class="paragraph"><p>You can also use\r
+<a href="https://bugs.launchpad.net/ubuntu/+source/psensor/+filebug">https://bugs.launchpad.net/ubuntu/+source/psensor/+filebug</a> if the bug\r
+can be reproduced with a package from the standard Ubuntu\r
+repositories.</p></div>\r
+<div class="paragraph"><p>If you don’t want to use the launchpad, you can send the report by\r
+email to:</p></div>\r
+<div class="ulist"><ul>\r
+<li>\r
+<p>\r
+<a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a> (require registration at:\r
+ <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
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+or <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.\r
+</p>\r
+</li>\r
+</ul></div>\r
+<div class="paragraph"><p>If the bug is concerning Debian or Ubuntu derivatives distribution,\r
+please add in its description the output of the command ‘apt-cache\r
+policy psensor’.</p></div>\r
+<div class="paragraph"><p>If it is related to the Psensor source compilation, please add the\r
+full output of the ‘configure’ command.</p></div>\r
+</div>\r
+</div>\r
+<div class="sect1">\r
+<h2 id="S_SubmitIdea">6. How to send ideas, questions or comments?</h2>\r
+<div class="sectionbody">\r
+<div class="paragraph"><p>Check the FAQ or the TODO pages.</p></div>\r
+<div class="paragraph"><p>If you don’t find the information, you can send an email to the public\r
+mailing-list <a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a> (require registration at:\r
+<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
+or send an email directly to me: <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.</p></div>\r
+</div>\r
+</div>\r
+<div class="sect1">\r
+<h2 id="S_Contribute">7. How to contribute?</h2>\r
+<div class="sectionbody">\r
+<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
+</div>\r
+</div>\r
+<div class="sect1">\r
+<h2 id="S_UbuntuInstall">8. How to install Psensor on Ubuntu?</h2>\r
+<div class="sectionbody">\r
+<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
+</div>\r
+</div>\r
+<div class="sect1">\r
+<h2 id="S_DebianInstall">9. How to install Psensor on Debian?</h2>\r
+<div class="sectionbody">\r
+<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
+</div>\r
+</div>\r
+<div class="sect1">\r
+<h2 id="S_PPA">10. What is the difference between the 3 Ubuntu PPAs?</h2>\r
+<div class="sectionbody">\r
+<div class="ulist"><ul>\r
+<li>\r
+<p>\r
+ppa:jfi/ppa: last stable version.\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+ppa:jfi/psensor-unstable: last development version, no major\r
+ bug is expected.\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+ppa:jfi/psensor-daily-trunk: build each day directly from\r
+ the SVN source repository. It may contain major bugs or\r
+ incomplete features. Useful for contributors or testing\r
+ whether a bug is fixed.\r
+</p>\r
+</li>\r
+</ul></div>\r
+</div>\r
+</div>\r
+<div class="sect1">\r
+<h2 id="S_ArchLinuxInstall">11. How to install Psensor on ArchLinux?</h2>\r
+<div class="sectionbody">\r
+<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
+</div>\r
+</div>\r
+<div class="sect1">\r
+<h2 id="S_OtherInstall">12. How to install Psensor on my Linux distribution?</h2>\r
+<div class="sectionbody">\r
+<div class="paragraph"><p>Psensor packages are available in the standard repositories of Ubuntu\r
+(since Oneiric) and Debian (since v7) distributions.</p></div>\r
+<div class="paragraph"><p>For other distributions, you will find the compilation and\r
+installation instructions in the section ‘Installation from source\r
+archive’ in the README file of the source archive. Psensor should\r
+compile in any modern distribution.</p></div>\r
+</div>\r
+</div>\r
+<div class="sect1">\r
+<h2 id="S_LOG">13. How to log sensors temperatures?</h2>\r
+<div class="sectionbody">\r
+<div class="paragraph"><p>The best way is probably to use sensord or a custom script based on\r
+the output of the different commands like sensors.</p></div>\r
+<div class="paragraph"><p>Anyway, as I received several requests about such feature, since the\r
+0.7.0.4 release it is implemented in both psensor ( menu preferences >\r
+sensors > enable log of measures) and psensor-server (–sensor-log-file\r
+option).</p></div>\r
+</div>\r
+</div>\r
+<div class="sect1">\r
+<h2 id="S_NO_GRAPH_DISPLAYED">14. No graphs are displayed, but the table of the main window is displaying sensors</h2>\r
+<div class="sectionbody">\r
+<div class="paragraph"><p>In the sensors table of the main window, switch on the checkbox of the last\r
+column (named "Enabled" or "Graph" depending on the Psensor version).</p></div>\r
+</div>\r
+</div>\r
+<div class="sect1">\r
+<h2 id="S_SimilarSoft">15. Is there any other similar softwares?</h2>\r
+<div class="sectionbody">\r
+<div class="paragraph"><p>Here is a list of few well-known sensors monitoring softwares:</p></div>\r
+<div class="ulist"><ul>\r
+<li>\r
+<p>\r
+for X11: <a href="http://freecode.com/projects/xsensors">http://freecode.com/projects/xsensors</a>\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+for GNOME2: <a href="http://sensors-applet.sourceforge.net/">http://sensors-applet.sourceforge.net/</a>\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+for Ubuntu Unity: <a href="https://launchpad.net/indicator-sensors">https://launchpad.net/indicator-sensors</a>\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+more general, but can be configured to display sensors\r
+ information: <a href="http://conky.sourceforge.net/">http://conky.sourceforge.net/</a>\r
+</p>\r
+</li>\r
+</ul></div>\r
+</div>\r
+</div>\r
+</div>\r
+<div id="footnotes"><hr /></div>\r
+<div id="footer">\r
+<div id="footer-text">\r
+Last updated 2013-05-12 17:54:35 CEST\r
+</div>\r
+</div>\r
+</body>\r
+</html>\r
projects / psensor-pkg-debian.git / blobdiff