X-Git-Url: http://git.wpitchoune.net/gitweb/?a=blobdiff_plain;f=doc%2Ffaq.html;h=b55a4b586d55288a31ebd2450e2915a4d11ec370;hb=c7219e09905fdd0a8b61de9b889777d38117f9e8;hp=5ce6393f150b87a793323cf6ea500e9fe61506e3;hpb=b3a843564deac2c2e054a5cfd732a44204390827;p=psensor.git

diff --git a/doc/faq.html b/doc/faq.html
index 5ce6393..b55a4b5 100644
--- a/doc/faq.html
+++ b/doc/faq.html
@@ -3,7 +3,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
 <head>
 <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.7" />
+<meta name="generator" content="AsciiDoc 8.6.9" />
 <title>Psensor Frequently Asked Questions</title>
 <style type="text/css">
 
@@ -177,6 +177,8 @@ table {
     -webkit-box-shadow: 0 2px 2px 0 #C2C2C2;
     box-shadow: 0 2px 2px 0 #C2C2C2;
 }
+
+
 </style>
 <script type="text/javascript">
 /*<![CDATA[*/
@@ -382,17 +384,23 @@ asciidoc.install(2);
 </div>
 </div>
 <div id="content">
+<div id="preamble">
+<div class="sectionbody">
+<div class="paragraph"><p>The last version of this FAQ is available at <a href="http://wpitchoune.net/gitweb/?p=psensor.git;a=blob_plain;f=doc/faq.html;hb=HEAD">http://wpitchoune.net/gitweb/?p=psensor.git;a=blob_plain;f=doc/faq.html;hb=HEAD</a>.</p></div>
+</div>
+</div>
 <div class="sect1">
 <h2 id="S_NoSensors">1. No sensors or only cpu usage is displayed</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>Psensor is relying on few libraries or softwares for retrieving the information about the computer:</p></div>
+<div class="paragraph"><p>Psensor is relying on few libraries or softwares for retrieving the
+information about the computer:</p></div>
 <div class="ulist"><ul>
 <li>
 <p>
 motherboard and CPUs sensors: the information is retrieved
           from the lm-sensors library, it requires that
-          âsensors-detectâ has been run and the kernel module
-          correctly installed. âsensorsâ can be used for checking.
+          <code>sensors-detect</code> has been run and the kernel module
+          correctly installed. <code>sensors</code> can be used for checking.
 </p>
 </li>
 <li>
@@ -410,13 +418,13 @@ Opensource drivers (nouveau for Nvidia GPUs or
 </li>
 <li>
 <p>
-proprietary driver Nvidia: run ânvidia-settingsâ to
+proprietary driver Nvidia: run <code>nvidia-settings</code> to
                   check that it supports sensors monitoring.
 </p>
 </li>
 <li>
 <p>
-proprietary driver Catalyst/fglx: use âaticonfigâ to
+proprietary driver Catalyst/fglx: use <code>aticonfig</code> to
                   check that it supports sensors monitoring. Important
                   note: it requires that you are using a Psensor
                   binary compiled with the ATI support.
@@ -424,13 +432,26 @@ proprietary driver Catalyst/fglx: use âaticonfigâ to
 </li>
 </ul></div>
 </li>
+</ul></div>
+<div class="paragraph"><p>For hard disk drives, psensor can use:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+udisks2: added since 1.1.2 release. It is the default and
+      recommended provider.
+</p>
+</li>
 <li>
 <p>
-HDDs: it uses the hddtemp daemon. Verifies that it is
-          correctly reporting temperature by using the âsudo hddtemp
-          /dev/sd?â command. If hddtemp does not support your disk,
-          you may want to try using the libatasmart support instead
-          (option âuse-libatasmart option).
+hddtemp: verify that it is correctly reporting temperature by
+      using the command: <code>sudo hddtemp /dev/sda</code>. It is the default
+      provider until 1.1.2 release.
+</p>
+</li>
+<li>
+<p>
+atasmart library: before the 1.1.2 release it can be enabled
+      by using the command line option <code>--use-libatasmart</code>.
 </p>
 </li>
 </ul></div>
@@ -439,6 +460,8 @@ displayed by Psensor, it is probably a bug in Psensor, so please
 report it. Otherwise, the issue is on the underlying software itself
 and you should contact the corresponding development team or refer to
 its documentation.</p></div>
+<div class="paragraph"><p>Since the release 1.1.2, the providers can be enabled or disabled directly
+from the user interface (<code>Preferences&gt;Provider</code>).</p></div>
 </div>
 </div>
 <div class="sect1">
@@ -450,7 +473,7 @@ any Linux distribution.</p></div>
 <div class="paragraph"><p>Unfortunely, due to the license of this library, I cannot provide a
 compiled version of Psensor, even in a Ubuntu PPA or Ubuntu/Debian
 standard repositories. You have to compile Psensor sensor. You can
-find the instructions in the section âATI/AMD GPU Supportâ of the
+find the instructions in the section <code>ATI/AMD GPU Support</code> of the
 README file available in the Psensor source archives.</p></div>
 <div class="paragraph"><p>If you are using the ATI OpenSource driver, it is not needed to
 compile Psensor with this proprietary library.</p></div>
@@ -491,8 +514,8 @@ the goal of the sensor is to allow the system to
 <p>
 It is only a bug in Psensor if the underlying libraries
           report a different information than Psensor (use the
-          appropriate command or software: âsensorsâ, âaticonfigâ or
-          âhddtempâ to check). In this case, please report a bug.
+          appropriate command or software: <code>sensors</code>, <code>aticonfig</code> or
+          <code>hddtemp</code> to check). In this case, please report a bug.
 </p>
 </li>
 </ul></div>
@@ -509,32 +532,32 @@ starting with:</p></div>
 <div class="ulist"><ul>
 <li>
 <p>
-âlmsensor coretempâ: Intel CPU.
+<code>lmsensor coretemp</code>: Intel CPU.
 </p>
 </li>
 <li>
 <p>
-âlmsensor k10tempâ,'lmsensor k8tempâ,'lmsensor fam15h_powerâ: AMD CPU.
+<code>lmsensor k10temp</code>, <code>lmsensor k8temp</code>, <code>lmsensor fam15h_power</code>: AMD CPU.
 </p>
 </li>
 <li>
 <p>
-ânvidiaâ or âlmsensor nouveauâ: NVIDIA GPU.
+<code>nvidia</code> or <code>lmsensor nouveau</code>: NVIDIA GPU.
 </p>
 </li>
 <li>
 <p>
-âhddâ: hard disk drive.
+<code>hdd</code>: hard disk drive.
 </p>
 </li>
 <li>
 <p>
-âamdâ: AMD GPU.
+<code>amd</code>: AMD GPU.
 </p>
 </li>
 <li>
 <p>
-âlmsensor C Bâ: C is the name of the chip, B the name of the adapter.
+<code>lmsensor C B</code>: C is the name of the chip, B the name of the adapter.
 </p>
 </li>
 </ul></div>
@@ -557,8 +580,7 @@ email to:</p></div>
 <div class="ulist"><ul>
 <li>
 <p>
-<a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a> (require registration at:
-        <a href="https://groups.google.com/forum/?fromgroups&amp;hl=en#!forum/psensor-users">https://groups.google.com/forum/?fromgroups&amp;hl=en#!forum/psensor-users</a>)
+<a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a>
 </p>
 </li>
 <li>
@@ -568,10 +590,10 @@ or <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.
 </li>
 </ul></div>
 <div class="paragraph"><p>If the bug is concerning Debian or Ubuntu derivatives distribution,
-please add in its description the output of the command âapt-cache
-policy psensorâ.</p></div>
+please add in its description the output of the command: <code>apt-cache
+policy psensor</code>.</p></div>
 <div class="paragraph"><p>If it is related to the Psensor source compilation, please add the
-full output of the âconfigureâ command.</p></div>
+full output of the <code>configure</code> command.</p></div>
 </div>
 </div>
 <div class="sect1">
@@ -579,9 +601,8 @@ full output of the âconfigureâ command.</p></div>
 <div class="sectionbody">
 <div class="paragraph"><p>Check the FAQ or the TODO pages.</p></div>
 <div class="paragraph"><p>If you donât find the information, you can send an email to the public
-mailing-list <a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a> (require registration at:
-<a href="https://groups.google.com/forum/?fromgroups&amp;hl=en#!forum/psensor-users">https://groups.google.com/forum/?fromgroups&amp;hl=en#!forum/psensor-users</a>)
-or send an email directly to me: <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.</p></div>
+mailing-list <a href="mailto:psensor-users@googlegroups.com">psensor-users@googlegroups.com</a> or directly to me:
+<a href="mailto:jeanfi@gmail.com">jeanfi@gmail.com</a>.</p></div>
 </div>
 </div>
 <div class="sect1">
@@ -593,13 +614,17 @@ or send an email directly to me: <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.
 <div class="sect1">
 <h2 id="S_UbuntuInstall">8. How to install Psensor on Ubuntu?</h2>
 <div class="sectionbody">
-<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>
+<div class="paragraph"><p>Psensor is in the official repository, search <code>psensor</code> 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>
 </div>
 </div>
 <div class="sect1">
 <h2 id="S_DebianInstall">9. How to install Psensor on Debian?</h2>
 <div class="sectionbody">
-<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>
+<div class="paragraph"><p>Psensor is 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>
 </div>
 </div>
 <div class="sect1">
@@ -608,19 +633,19 @@ or send an email directly to me: <a href="mailto:jeanfi@gmail.com">jeanfi@gmail.
 <div class="ulist"><ul>
 <li>
 <p>
-ppa:jfi/ppa: last stable version.
+<code>ppa:jfi/ppa</code>: last stable version.
 </p>
 </li>
 <li>
 <p>
-ppa:jfi/psensor-unstable: last development version, no major
-          bug is expected.
+<code>ppa:jfi/psensor-unstable</code>: last development version, no
+          major bug is expected.
 </p>
 </li>
 <li>
 <p>
-ppa:jfi/psensor-daily-trunk: build each day directly from
-          the SVN source repository. It may contain major bugs or
+<code>ppa:jfi/psensor-daily-trunk</code>: build each day directly from
+          the GIT source repository. It may contain major bugs or
           incomplete features. Useful for contributors or testing
           whether a bug is fixed.
 </p>
@@ -640,8 +665,8 @@ ppa:jfi/psensor-daily-trunk: build each day directly from
 <div class="paragraph"><p>Psensor packages are available in the standard repositories of Ubuntu
 (since Oneiric) and Debian (since v7) distributions.</p></div>
 <div class="paragraph"><p>For other distributions, you will find the compilation and
-installation instructions in the section âInstallation from source
-archiveâ in the README file of the source archive. Psensor should
+installation instructions in the section <code>Installation from source
+archive</code> in the README file of the source archive. Psensor should
 compile in any modern distribution.</p></div>
 </div>
 </div>
@@ -649,22 +674,66 @@ compile in any modern distribution.</p></div>
 <h2 id="S_LOG">13. How to log sensors temperatures?</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>The best way is probably to use sensord or a custom script based on
-the output of the different commands like sensors.</p></div>
+the output of the different commands like <code>sensors</code>.</p></div>
 <div class="paragraph"><p>Anyway, as I received several requests about such feature, since the
 0.7.0.4 release it is implemented in both psensor ( menu preferences &gt;
-sensors &gt; enable log of measures) and psensor-server (âsensor-log-file
-option).</p></div>
+sensors &gt; enable log of measures) and psensor-server
+(<code>--sensor-log-file</code> option). For psensor the log file is
+<code>$HOME/.psensor/sensors.log</code>.</p></div>
 </div>
 </div>
 <div class="sect1">
 <h2 id="S_NO_GRAPH_DISPLAYED">14. No graphs are displayed, but the table of the main window is displaying sensors</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>In the sensors table of the main window, switch on the checkbox of the last
-column (named "Enabled" or "Graph" depending on the Psensor version).</p></div>
+column (named <code>Enabled</code> or <code>Graph</code> depending on the Psensor version).</p></div>
 </div>
 </div>
 <div class="sect1">
-<h2 id="S_SimilarSoft">15. Is there any other similar softwares?</h2>
+<h2 id="S_autostart">15. Launch Psensor automaticaly on session startup</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Since the version 1.0.1, Psensor is no more started automaticaly by default.</p></div>
+<div class="paragraph"><p>Open the <code>Preferences</code> window, select the <code>Startup</code> tab and switch on
+the option <code>Launch on session startup</code>.</p></div>
+<div class="paragraph"><p>This feature is requiring that the Desktop Environment supports the
+<a href="http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
+specification</a>.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_disk">16. How to monitor the temperature of a disk with <code>hddtemp</code>?</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Until the release 1.1.2, Psensor is using <code>hddtemp</code> by default to
+retrieve the temperature of the disks.</p></div>
+<div class="paragraph"><p>If <code>hddtemp</code> is installed but no disk temperature is reported, check
+that the daemon is running by using for example the command <code>ps
+-eaf|grep hddtemp</code>.
+It should output something like:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>root      1433     1  0 May28 ?        00:00:21 /usr/sbin/hddtemp -d -l 127.0.0.1 -p 7634 -s | /dev/sdb</code></pre>
+</div></div>
+<div class="paragraph"><p>Depending on the Linux distribution, the installation of the <code>hddtemp</code>
+package does not enable the hddtemp daemon automaticaly.</p></div>
+<div class="paragraph"><p>In this case, edit the file <code>/etc/default/hddtemp</code> and set
+<code>RUN_DAEMON</code> to <code>"true"</code> like in the following example:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code># hddtemp network daemon switch. If set to true, hddtemp will listen
+# for incoming connections.
+RUN_DAEMON="true"</code></pre>
+</div></div>
+<div class="paragraph"><p>For Debian/Ubuntu, you can use</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><code>dpkg-reconfigure hddtemp</code></pre>
+</div></div>
+<div class="paragraph"><p>and reply <code>yes</code> when asked whether hddtemp daemon must be
+run during the startup.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="S_SimilarSoft">17. Is there any other similar softwares?</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>Here is a list of few well-known sensors monitoring softwares:</p></div>
 <div class="ulist"><ul>
@@ -692,11 +761,21 @@ more general, but can be configured to display sensors
 </ul></div>
 </div>
 </div>
+<div class="sect1">
+<h2 id="S_HideSensor">18. Is it possible to hide sensors in the main window?</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Before v1.1.1, the sensors retrieved from the lm-sensor library can be
+ignored directly in the lm-sensor configuration. See the manpage
+of sensors.conf(5).</p></div>
+<div class="paragraph"><p>Since v1.1.1, it is possible to hide a sensor, uncheck the setting
+<em>Display sensor in the list of sensors</em> in the sensor preferences.</p></div>
+</div>
+</div>
 </div>
 <div id="footnotes"><hr /></div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2014-02-11 08:49:46 CET
+Last updated 2014-10-12 12:23:53 CEST
 </div>
 </div>
 </body>
