X-Git-Url: http://git.wpitchoune.net/gitweb/?a=blobdiff_plain;ds=inline;f=www%2Fpsensor%2Ffaq.html;h=df4e9fd52dcf7b7413b2bdced3274939c2e82d15;hb=9c2528aa24bf669be0c43a4117c9fa80cb19d410;hp=68176355f59bdc83e4e13d90e7c543d03bbdc456;hpb=c280df3b6ae1ab82414895f9a6884272bc7a78de;p=www.git diff --git a/www/psensor/faq.html b/www/psensor/faq.html index 6817635..df4e9fd 100644 --- a/www/psensor/faq.html +++ b/www/psensor/faq.html @@ -6,416 +6,9 @@
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.
GPUs: it depends on which driver you are using:
@@ -455,11 +48,11 @@ monitoring for your GPU, the information is using lm-sensors, same steps than above.proprietary driver Nvidia: run nvidia-settings
to
+
proprietary driver Nvidia: run nvidia-settings to check that it supports sensors monitoring.
proprietary driver Catalyst/fglx: use aticonfig
to
+
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.
@@ -480,12 +73,12 @@ recommended provider.hddtemp: verify that it is correctly reporting temperature by
-using the command: sudo hddtemp /dev/sda
. It is the default
+using the command: sudo hddtemp /dev/sda. It is the default
provider until 1.1.2 release.
atasmart library: before the 1.1.2 release it can be enabled
-by using the command line option --use-libatasmart
.
Since the release 1.1.2, the providers can be enabled or disabled directly
-from the user interface (Preferences>Provider
).
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 ATI/AMD GPU Support of the
README file available in the Psensor source archives.
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.
lmsensor coretemp
: Intel CPU.
lmsensor coretemp: Intel CPU.
lmsensor k10temp
, lmsensor k8temp
, lmsensor fam15h_power
: AMD CPU.
lmsensor k10temp, lmsensor k8temp, lmsensor fam15h_power: AMD CPU.
nvidia
or lmsensor nouveau
: NVIDIA GPU.
nvidia or lmsensor nouveau: NVIDIA GPU.
hdd
: hard disk drive.
hdd: hard disk drive.
amd
: AMD GPU.
amd: AMD GPU.
lmsensor C B
: C is the name of the chip, B the name of the adapter.
lmsensor C B: C is the name of the chip, B the name of the adapter.
If the bug is concerning Debian or Ubuntu derivatives distribution,
-please add in its description the output of the command: apt-cache
-policy psensor
.
If it is related to the Psensor source compilation, please add the
-full output of the configure
command.
Psensor is in the official repository, search psensor
in the
+
Psensor is in the official repository, search psensor in the software center and install it. More information at: http://wpitchoune.net/blog/psensor/ubuntu-integration/.
ppa:jfi/ppa
: last stable version.
ppa:jfi/ppa: last stable version.
ppa:jfi/psensor-unstable
: last development version, no
+
ppa:jfi/psensor-unstable: last development version, no major bug is expected.
ppa:jfi/psensor-daily-trunk
: build each day directly from
+
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.
@@ -722,8 +315,8 @@ whether a bug is fixed.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 Installation from source
+archive in the README file of the source archive. Psensor should
compile in any modern distribution.
The best way is probably to use sensord or a custom script based on
-the output of the different commands like sensors
.
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
-(--sensor-log-file
option). For psensor the log file is
-$HOME/.psensor/sensors.log
.
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).
Enabled
or Graph
depending on the Psenso
Since the version 1.0.1, Psensor is no more started automaticaly by default.
Open the Preferences
window, select the Startup
tab and switch on
-the option Launch on session startup
.
Open the Preferences window, select the Startup tab and switch on +the option Launch on session startup.
This feature is requiring that the Desktop Environment supports the @@ -771,16 +364,16 @@ specification.
hddtemp
?Until the release 1.1.2, Psensor is using hddtemp
by default to
+
Until the release 1.1.2, Psensor is using hddtemp by default to retrieve the temperature of the disks.
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
.
+
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:
Depending on the Linux distribution, the installation of the hddtemp
+
Depending on the Linux distribution, the installation of the hddtemp package does not enable the hddtemp daemon automaticaly.
In this case, edit the file /etc/default/hddtemp
and set
-RUN_DAEMON
to "true"
. After edition, it should contain the
+
In this case, edit the file /etc/default/hddtemp and set +RUN_DAEMON to "true". After edition, it should contain the following line:
and reply yes
when asked whether hddtemp daemon must be
+
and reply yes when asked whether hddtemp daemon must be run during the startup.
Since v1.1.1, it is possible to hide a sensor, uncheck the setting -Display sensor in the list of sensors in the sensor preferences.
+'Display sensor in the list of sensors' in the sensor preferences.