<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="generator" content="Asciidoctor 1.5.4">
<title>Psensor Frequently Asked Questions</title>
-<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Open+Sans:300,300italic,400,400italic,600,600italic%7CNoto+Serif:400,400italic,700,700italic%7CDroid+Sans+Mono:400,700">
-<link rel="stylesheet" href="./asciidoctor.css">
+<link rel="stylesheet" href="./../style.css">
+<script src="https://ajax.googleapis.com/ajax/libs/jquery/2.2.4/jquery.min.js"></script>
+<script src="nav.js"></script>
+<link rel="stylesheet" href="font-awesome/css/font-awesome.min.css">
</head>
<body class="article">
<div id="header">
<li>
<p>motherboard and CPUs sensors: the information is retrieved
from the lm-sensors library, it requires that
-<code>sensors-detect</code> has been run and the kernel module
-correctly installed. <code>sensors</code> can be used for checking.</p>
+sensors-detect has been run and the kernel module
+correctly installed. sensors can be used for checking.</p>
</li>
<li>
<p>GPUs: it depends on which driver you are using:</p>
lm-sensors, same steps than above.</p>
</li>
<li>
-<p>proprietary driver Nvidia: run <code>nvidia-settings</code> to
+<p>proprietary driver Nvidia: run nvidia-settings to
check that it supports sensors monitoring.</p>
</li>
<li>
-<p>proprietary driver Catalyst/fglx: use <code>aticonfig</code> to
+<p>proprietary driver Catalyst/fglx: use aticonfig to
check that it supports sensors monitoring. Important
note: it requires that you are using a Psensor
binary compiled with the ATI support.</p>
</li>
<li>
<p>hddtemp: verify that it is correctly reporting temperature by
-using the command: <code>sudo hddtemp /dev/sda</code>. It is the default
+using the command: sudo hddtemp /dev/sda. 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>
+by using the command line option --use-libatasmart.</p>
</li>
</ul>
</div>
</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>Provider</code>).</p>
+from the user interface (Preferences>Provider).</p>
</div>
</div>
</div>
<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 <code>ATI/AMD GPU Support</code> of the
+find the instructions in the section ATI/AMD GPU Support of the
README file available in the Psensor source archives.</p>
</div>
<div class="paragraph">
<li>
<p>It is only a bug in Psensor if the underlying libraries
report a different information than Psensor (use the
-appropriate command or software: <code>sensors</code>, <code>aticonfig</code> or
-<code>hddtemp</code> to check). In this case, please report a bug.</p>
+appropriate command or software: sensors, aticonfig or
+hddtemp to check). In this case, please report a bug.</p>
</li>
</ul>
</div>
<div class="ulist">
<ul>
<li>
-<p><code>lmsensor coretemp</code>: Intel CPU.</p>
+<p>lmsensor coretemp: Intel CPU.</p>
</li>
<li>
-<p><code>lmsensor k10temp</code>, <code>lmsensor k8temp</code>, <code>lmsensor fam15h_power</code>: AMD CPU.</p>
+<p>lmsensor k10temp, lmsensor k8temp, lmsensor fam15h_power: AMD CPU.</p>
</li>
<li>
-<p><code>nvidia</code> or <code>lmsensor nouveau</code>: NVIDIA GPU.</p>
+<p>nvidia or lmsensor nouveau: NVIDIA GPU.</p>
</li>
<li>
-<p><code>hdd</code>: hard disk drive.</p>
+<p>hdd: hard disk drive.</p>
</li>
<li>
-<p><code>amd</code>: AMD GPU.</p>
+<p>amd: AMD GPU.</p>
</li>
<li>
-<p><code>lmsensor C B</code>: C is the name of the chip, B the name of the adapter.</p>
+<p>lmsensor C B: C is the name of the chip, B the name of the adapter.</p>
</li>
</ul>
</div>
</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: <code>apt-cache
-policy psensor</code>.</p>
+please add in its description the output of the command: apt-cache
+policy psensor.</p>
</div>
<div class="paragraph">
<p>If it is related to the Psensor source compilation, please add the
-full output of the <code>configure</code> command.</p>
+full output of the configure command.</p>
</div>
</div>
</div>
<h2 id="S_UbuntuInstall">How to install Psensor on Ubuntu?</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>Psensor is in the official repository, search <code>psensor</code> in the
+<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/" class="bare">http://wpitchoune.net/blog/psensor/ubuntu-integration/</a>.</p>
</div>
<div class="ulist">
<ul>
<li>
-<p><code>ppa:jfi/ppa</code>: last stable version.</p>
+<p>ppa:jfi/ppa: last stable version.</p>
</li>
<li>
-<p><code>ppa:jfi/psensor-unstable</code>: last development version, no
+<p>ppa:jfi/psensor-unstable: last development version, no
major bug is expected.</p>
</li>
<li>
-<p><code>ppa:jfi/psensor-daily-trunk</code>: build each day directly from
+<p>ppa:jfi/psensor-daily-trunk: 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>
</div>
<div class="paragraph">
<p>For other distributions, you will find the compilation and
-installation instructions in the section <code>Installation from source
-archive</code> in the README file of the source archive. Psensor should
+installation instructions in the section Installation from source
+archive in the README file of the source archive. Psensor should
compile in any modern distribution.</p>
</div>
</div>
<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 <code>sensors</code>.</p>
+the output of the different commands like sensors.</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 >
sensors > 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>
+(--sensor-log-file option). For psensor the log file is
+$HOME/.psensor/sensors.log.</p>
</div>
</div>
</div>
<div class="sectionbody">
<div class="paragraph">
<p>In the sensors table of the main window, switch on the checkbox of the last
-column (named <code>Enabled</code> or <code>Graph</code> depending on the Psensor version).</p>
+column (named Enabled or Graph depending on the Psensor version).</p>
</div>
</div>
</div>
<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>
+<p>Open the Preferences window, select the Startup tab and switch on
+the option Launch on session startup.</p>
</div>
<div class="paragraph">
<p>This feature is requiring that the Desktop Environment supports the
</div>
</div>
<div class="sect1">
-<h2 id="S_disk">How to monitor the temperature of a disk with <code>hddtemp</code>?</h2>
+<h2 id="S_disk">How to monitor the temperature of a disk with hddtemp?</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>Until the release 1.1.2, Psensor is using <code>hddtemp</code> by default to
+<p>Until the release 1.1.2, Psensor is using hddtemp 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>.
+<p>If hddtemp is installed but no disk temperature is reported, check
+that the daemon is running by using for example the command ps
+-eaf|grep hddtemp.
It should output something like:</p>
</div>
<div class="listingblock">
</div>
</div>
<div class="paragraph">
-<p>Depending on the Linux distribution, the installation of the <code>hddtemp</code>
+<p>Depending on the Linux distribution, the installation of the hddtemp
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>. After edition, it should contain the
+<p>In this case, edit the file /etc/default/hddtemp and set
+RUN_DAEMON to "true". After edition, it should contain the
following line:</p>
</div>
<div class="listingblock">
</div>
</div>
<div class="paragraph">
-<p>and reply <code>yes</code> when asked whether hddtemp daemon must be
+<p>and reply yes when asked whether hddtemp daemon must be
run during the startup.</p>
</div>
</div>
</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>
+'Display sensor in the list of sensors' in the sensor preferences.</p>
</div>
</div>
</div>
</div>
<div id="footer">
<div id="footer-text">
-Last updated 2016-06-10 11:21:52 CEST
+Last updated 2016-06-14 10:13:47 CEST
</div>
</div>
</body>
projects / www.git / blobdiff