https://wiki.archlinux.org/api.php?action=feedcontributions&user=Valentt&feedformat=atomArchWiki - User contributions [en]2024-03-29T07:30:42ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Media_Transfer_Protocol&diff=285070Media Transfer Protocol2013-11-28T12:29:00Z<p>Valentt: /* go-mtpfs */</p>
<hr />
<div>[[Category:Sound]]<br />
MTP is the "Media Transfer Protocol" and is used by many mp3 players (e.g. Creative Zen) and mobile phones (e.g. Android 3+ devices). It is part of the "Windows Media" Framework and has close relationship with Windows Media Player.<br />
<br />
==Installation==<br />
MTP support is provided by [http://libmtp.sourceforge.net/ libmtp], [[pacman|installable]] with the {{Pkg|libmtp}} package from the [[official repositories]].<br />
<br />
==Usage==<br />
After installation, you have several MTP tools available.<br />
Upon connecting your MTP device, you use:<br />
# mtp-detect<br />
to see if your MTP device is detected.<br />
<br />
To connect to your MTP device, you use:<br />
# mtp-connect<br />
<br />
If connection is successful, you will be given several switch options in conjunction with {{ic|mtp-connect}} to access data on the device.<br />
<br />
There are also several stand alone commands you can use to access your MTP device such as,<br />
{{Warning | Some commands may be harmful to your MTP device!!! }}<br />
<br />
mtp-albumart mtp-emptyfolders mtp-getplaylist mtp-reset mtp-trexist<br />
mtp-albums mtp-files mtp-hotplug mtp-sendfile<br />
mtp-connect mtp-folders mtp-newfolder mtp-sendtr<br />
mtp-delfile mtp-format mtp-newplaylist mtp-thumb<br />
mtp-detect mtp-getfile mtp-playlists mtp-tracks<br />
<br />
==Using media players==<br />
You can also use your MTP device in music players such as Amarok. To do this you may have to edit {{ic|/etc/udev/rules.d/51-android.rules}} (the MTP device used in the following example is a Galaxy Nexus):<br />
To do this run:<br />
$ lsusb<br />
and look for your device, it will be something like:<br />
Bus 003 Device 011: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-P7500 [Galaxy Tab 10.1]<br />
in which case the entry would be:<br />
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0666", OWNER="[username]"<br />
Then, reload udev rules:<br />
# udevadm control --reload<br />
<br />
{{Note|After installing MTP you may have to reboot for your device to be recognised}}<br />
<br />
==mtpfs==<br />
Mtpfs is FUSE filesystem that supports reading and writing from any MTP device. Basically it allows you to mount your device as an external drive.<br />
<br />
Mtpfs can be installed with the packge {{Pkg|mtpfs}}, available from the [[official repositories]].<br />
*First edit your {{ic|/etc/fuse.conf}} and uncomment the following line:<br />
user_allow_other<br />
<br />
*To mount your device <br />
$ mtpfs -o allow_other /media/YOURMOUNTPOINT<br />
*To unmount your device<br />
$ fusermount -u /media/YOURMOUNTPOINT<br />
*To unmount your device as root<br />
# umount /media/YOURMOUNTPOINT<br />
<br />
Also, you can put them into your ~/.bashrc:<br />
alias android-connect="mtpfs -o allow_other /media/YOURMOUNTPOINT"<br />
alias android-disconnect="fusermount -u /media/YOURMOUNTPOINT"<br />
Or, with sudo <br />
alias android-disconnect="sudo umount -u /media/YOURMOUNTPOINT"<br />
{{Note|if you want not be asked for password when using sudo, please refer to [[USB Storage Devices#Mounting USB devices]]}}<br />
<br />
==jmtpfs==<br />
[http://research.jacquette.com/jmtpfs-exchanging-files-between-android-devices-and-linux/ jmtpfs] is a FUSE and libmtp based filesystem for accessing MTP (Media Transfer Protocol) devices. It was specifically designed for exchanging files between Linux systems and newer Android devices that support MTP but not USB Mass Storage.<br />
jmtpfs is available as {{aur|jmtpfs}} in the [[AUR]].<br />
<br />
Use these commands to mount and unmount your device :<br />
$ jmtpfs ~/mtp<br />
<br />
$ fusermount -u ~/mtp<br />
<br />
==go-mtpfs==<br />
{{Note|Go-mtpfs gives a better performance while writing files to some devices than mtpfs/jmtpfs. Try it if you have slow speeds.}}<br />
{{Note|Mounting with Go-mtpfs fails if external SD Card is present. If you have also external SD Card please remove it and then try mounting again.}}<br />
If the above instructions don't show any positive results one should try {{aur|go-mtpfs-git}} from the [[AUR]].<br />
The following has been tested on a Samsung Galaxy Nexus GSM, Asus/Google Nexus 7 (2012 1st gen model) and Samsung Galaxy S 3 mini. (This is the only mtp software which worked for me on nexus 4. Settings are usb debugging enabled, connected as media device.)<br />
<br />
If you want do it simpler, install {{Pkg|go}}, {{Pkg|libmtp}} and {{Pkg|git}} from the [[official repositories]]. After that install {{AUR|go-mtpfs-git}} from the [[AUR]].<br />
<br />
<br />
As in the section above install {{aur|android-udev}} which will provide you with "/usr/lib/udev/rules.d/51-android.rules" edit it to apply to <br />
your vendorID and productID, which you can see after running mtp-detect. To the end of the line add with a comma OWNER="yourusername". Save the file.<br />
<br />
*Add yourself to the "fuse" group:<br />
gpasswd -a [user] fuse<br />
<br />
*If the group "fuse" doesn't exist create it with:<br />
groupadd fuse<br />
<br />
Logout or reboot to apply these changes. <br />
<br />
*To create a mount point called "Android" issue the following commands:<br />
mkdir Android<br />
<br />
*To mount your phone use:<br />
go-mtpfs Android<br />
<br />
*To unmount your phone:<br />
fusermount -u Android<br />
<br />
You can create a .bashrc alias as in the example above for easier use.<br />
<br />
==gvfs-mtp==<br />
<br />
Philip Langdale is has implemented native MTP support for gvfs. The weaknesses of gphoto2 and mtpfs are listed in his [http://intr.overt.org/blog/?p=153 blog post]. <br />
*The native mtp implementation for gvfs [https://bugzilla.gnome.org/show_bug.cgi?id=666195 has been merged upstream] and has been released in gvfs [http://git.gnome.org/browse/gvfs/commit/?id=d6c8e3a4910ee2c5968886328ebe9456b445796b 1.15.2]. <br />
* You can grab the stable {{Pkg|gvfs-mtp}} package from extra. You may want to reboot your PC to make it actually working.<br />
<br />
*Devices will have gvfs paths like this<br />
gvfs-ls mtp://[usb:002,013]/<br />
<br />
==simple-mtpfs==<br />
<br />
This is another FUSE filesystem for MTP devices. You may find this to be more reliable than {{Pkg|mtpfs}}. {{aur|simple-mtpfs}} is available in the AUR or can be built from source. Remember '''do not''' run the following commands as root.<br />
<br />
* To list MTP devices run<br />
simple-mtpfs --list-devices<br />
<br />
* To mount a MTP devices (in this example device 0) run<br />
simple-mtpfs /path/to/your/mount/point<br />
<br />
* To un mount run<br />
fusermount -u /path/to/your/mount/point<br />
<br />
==KDE MTP KIO Slave==<br />
There is a MTP KIO Slave built upon libmtp availiable as package {{Pkg|kio-mtp}}. <br />
<br />
Using KIO makes file access in KDE seamless, in principle any KDE application would be able read/write files on the device.<br />
<br />
===Usage===<br />
The device will be available under the path mtp:/<br />
<br />
===Workaround if the KDE device actions doesn't work===<br />
If you are not able to use the action "Open with File Manager", you may work around this problem by editing the file /usr/share/apps/solid/actions/solid_mtp.desktop<br />
<br />
Change the line<br />
Exec=kioclient exec mtp:udi=%i/<br />
To<br />
Exec=dolphin "mtp:/"<br />
<br />
==GNOME gMTP==<br />
gMTP is a native Gnome application used for MTP access.<br />
<br />
{{aur|gmtp}} is currently located in the [[AUR]] .<br />
<br />
==Workarounds for Android==<br />
* HTC Phones automatically enter usb debugging mode on usb connect. Manually turn it off once connected to give libmtp access to the device.<br />
<br />
MTP is still buggy and may crash despite the best efforts of developers. The following are alternatives:<br />
* AirDroid - an Android app to access files via your web browser.<br />
* FTP client on Android - If you run a local FTP server on Arch (such as [[Vsftp]]), there are many FTP clients available on the Play Store which will give read/ write access to your device's files.<br />
* FTP Server on Android. Note: since FTP client using passive transfer (server connect to client) do not forget to disable firewall or adding rules for allowing FTP server connect to your PC.<br />
** Ftp Server (by The Olive Tree) app in Play Store acts as FTP server on Android and allows RW access to pretty much all your storage.<br />
*** Pro: Doesn't require root and just works!<br />
*** Cons: Doesn't work with tethering network.<br />
** FTPServer (by Andreas Liebig) - Just work.<br />
* SSH server on Android.<br />
** For example, SSHelper, available on the Play Store, just works without requiring root access. Assuming SSHelper is listening on port 20 and the phone's IP address is 192.168.0.20, the following command will synchronise a local directory with the external SD card of the Android device:<br />
rsync --rsh="ssh -p 20" --modify-window=1 ~/local_files 192.168.0.20:/mnt/extSdCard/remote_files<br />
Note the {{ic|--modify-window}} option, which is often used when rsyncing to a FAT filesystem (such as the one used by Android devices for their internal memory and external SD cards).<br />
* Samba - an Android app to share your SD card as a windows fileshare. Pros: Your desktop apps work as before (since the SD card appears as a windows fileshare). Cons: you need to root your phone.<br />
* adb - Part of the Android development kit is adb android debug bridge. It can be used to push and pull files from an Android device.<br />
** The device need USB debbuging to be active and later connected to the computer with usb.<br />
** To send a file to the device use {{ic|adb push /what-to-copy /where-to-place-it}}<br />
** To receive a file {{ic|adb pull /what-you-want-to-copy /where-you-want-it}}<br />
*** Pro: Stable, can be used for a lot more then just copy files back and forth.<br />
*** Cons: Can be somewhat slow.<br />
<br />
==Security features on android==<br />
If you use android 4.x please unlock phone (screen unlock) and then connect phone to USB.<br />
<br />
If you not unlock you have in KDE "No Storages found. Maybe you need to unlock your device?" or error 02fe in console.</div>Valentthttps://wiki.archlinux.org/index.php?title=Lm_sensors&diff=201810Lm sensors2012-05-16T20:22:42Z<p>Valentt: Automatic lm-sensors deployment</p>
<hr />
<div>[[Category:Mainboards and BIOS]]<br />
[[Category:CPU]]<br />
[[Category:Daemons and system services]]<br />
{{i18n|lm sensors}}<br />
{{lowercase title}}<br />
[http://www.lm-sensors.org/ lm_sensors] (Linux monitoring sensors) is a free and open-source application that provides tools and drivers for monitoring temperatures, voltage, and fans. This document explains how to install, configure, and use lm_sensors so that you can monitor CPU temperatures, motherboard temperatures, and fan speeds.<br />
<br />
== Usage ==<br />
=== Installation ===<br />
Install the {{Pkg|lm_sensors}} package from the [[Official Repositories|official repositories]].<br />
<br />
=== Setting up lm_sensors ===<br />
Use '''sensors-detect''' to detect and generate a list of kernel modules:<br />
# sensors-detect<br />
This will create the {{ic|/etc/conf.d/lm_sensors}} configuration file which is used by the {{ic|sensors}} daemon to automatically load kernel modules on boot. You will be asked if you want to probe for various hardware. The "safe" answers are the defaults, so just hitting {{Keypress|Enter}} to all the questions will generally not cause any problems. <br />
<br />
When the detection is finished, you will be presented with a summary of the probes. Here is an example summary from my system:<br />
{{hc|# sensors-detect|<nowiki><br />
Now follows a summary of the probes I have just done.<br />
Just press ENTER to continue:<br />
Driver `it87':<br />
* ISA bus, address 0x290<br />
Chip `ITE IT8718F Super IO Sensors' (confidence: 9)<br />
Driver `coretemp':<br />
* Chip `Intel Core family thermal sensor' (confidence: 9)<br />
</nowiki>}}<br />
If you plan on using the daemon, be sure to answer '''YES''' when asked if you want to to generate {{ic|/etc/conf.d/lm_sensors}}.<br />
<br />
To automatically load the kernel modules at boot time, add {{ic|sensors}} to the {{ic|DAEMONS}} array in {{ic|/etc/rc.conf}}<br />
DAEMONS=(syslog-ng crond ... sensors ...)<br />
<br />
Alternatively, instead of using the daemon, you can add the modules to the {{ic|MODULES}} array in {{ic|/etc/rc.conf}}:<br />
MODULES=(coretemp it87 acpi-cpufreq)<br />
<br />
=== Automatic lm_sensors deployment ===<br />
If you wish to deploy lm-sensors on multiple diferent linux machines issue is that sensors-detect ask you quite a few questions. There are few tricks that you can use to automate replies.<br />
<br />
First one is if you wish to accept defaults which sensors-detect suggest you need just to press [ENTER] all the time. To automate this use this one liner:<br />
<br />
# (while :; do echo ""; done ) | sensors-detect<br />
<br />
If you wish to override defaults and answer YES to all questions then use this oneliner:<br />
<br />
# yes "" | sensors-detect<br />
<br />
=== Testing your lm_sensors ===<br />
To test your setup, load the kernel modules manually or by using the {{ic|/etc/rc.d/sensors}} init script. You do '''NOT''' have to do both.<br />
Example manually adding them<br />
# modprobe it87<br />
# modprobe coretemp<br />
Example using the script<br />
# rc.d start sensors<br />
<br />
You should see something like this when you run sensors<br />
{{hc|$ sensors|<nowiki><br />
coretemp-isa-0000<br />
Adapter: ISA adapter<br />
Core 0: +30.0°C (high = +76.0°C, crit = +100.0°C) <br />
<br />
coretemp-isa-0001<br />
Adapter: ISA adapter<br />
Core 1: +30.0°C (high = +76.0°C, crit = +100.0°C) <br />
<br />
coretemp-isa-0002<br />
Adapter: ISA adapter<br />
Core 2: +32.0°C (high = +76.0°C, crit = +100.0°C) <br />
<br />
coretemp-isa-0003<br />
Adapter: ISA adapter<br />
Core 3: +30.0°C (high = +76.0°C, crit = +100.0°C) <br />
<br />
it8718-isa-0290<br />
Adapter: ISA adapter<br />
in0: +1.17 V (min = +0.00 V, max = +4.08 V) <br />
in1: +1.31 V (min = +1.28 V, max = +1.68 V) <br />
in2: +3.28 V (min = +2.78 V, max = +3.78 V) <br />
in3: +2.88 V (min = +2.67 V, max = +3.26 V) <br />
in4: +2.98 V (min = +2.50 V, max = +3.49 V) <br />
in5: +1.34 V (min = +0.58 V, max = +1.34 V) ALARM<br />
in6: +2.02 V (min = +1.04 V, max = +1.36 V) ALARM<br />
in7: +2.83 V (min = +2.67 V, max = +3.26 V) <br />
Vbat: +3.28 V<br />
fan1: 1500 RPM (min = 3245 RPM) ALARM<br />
fan2: 0 RPM (min = 3245 RPM) ALARM<br />
fan3: 0 RPM (min = 3245 RPM) ALARM<br />
temp1: +18.0°C (low = +127.0°C, high = +64.0°C) sensor = thermal diode<br />
temp2: +32.0°C (low = +127.0°C, high = +64.0°C) sensor = thermistor<br />
temp3: +38.0°C (low = +127.0°C, high = +64.0°C) sensor = thermistor<br />
cpu0_vid: +2.050 V<br />
<br />
acpitz-virtual-0<br />
Adapter: Virtual device<br />
temp1: +18.0°C (crit = +64.0°C)<br />
</nowiki>}}<br />
<br />
=== Reading SPD values from memory modules (optional) ===<br />
<br />
To read the SPD timing values from your memory modules, install {{AUR|i2c-tools}} from [[AUR]]. Once you have i2c-tools installed, you will need to load the {{ic|eeprom}} [[Kernel_modules|kernel module]].<br />
# modprobe eeprom<br />
Finally, you can view your memory information with {{ic|decode-dimms}}.<br />
<br />
Here is partial output from one machine:<br />
{{hc|$ decode-dimms|<nowiki><br />
# decode-dimms version 5733 (2009-06-09 13:13:41 +0200)<br />
<br />
Memory Serial Presence Detect Decoder<br />
By Philip Edelbrock, Christian Zuckschwerdt, Burkart Lingner,<br />
Jean Delvare, Trent Piepho and others<br />
<br />
<br />
Decoding EEPROM: /sys/bus/i2c/drivers/eeprom/0-0050<br />
Guessing DIMM is in bank 1<br />
<br />
---=== SPD EEPROM Information ===---<br />
EEPROM CRC of bytes 0-116 OK (0x583F)<br />
# of bytes written to SDRAM EEPROM 176<br />
Total number of bytes in EEPROM 512<br />
Fundamental Memory type DDR3 SDRAM<br />
Module Type UDIMM<br />
<br />
---=== Memory Characteristics ===---<br />
Fine time base 2.500 ps<br />
Medium time base 0.125 ns<br />
Maximum module speed 1066MHz (PC3-8533)<br />
Size 2048 MB<br />
Banks x Rows x Columns x Bits 8 x 14 x 10 x 64<br />
Ranks 2<br />
SDRAM Device Width 8 bits<br />
tCL-tRCD-tRP-tRAS 7-7-7-33<br />
Supported CAS Latencies (tCL) 8T, 7T, 6T, 5T<br />
<br />
---=== Timing Parameters ===---<br />
Minimum Write Recovery time (tWR) 15.000 ns<br />
Minimum Row Active to Row Active Delay (tRRD) 7.500 ns<br />
Minimum Active to Auto-Refresh Delay (tRC) 49.500 ns<br />
Minimum Recovery Delay (tRFC) 110.000 ns<br />
Minimum Write to Read CMD Delay (tWTR) 7.500 ns<br />
Minimum Read to Pre-charge CMD Delay (tRTP) 7.500 ns<br />
Minimum Four Activate Window Delay (tFAW) 30.000 ns<br />
<br />
---=== Optional Features ===---<br />
Operable voltages 1.5V<br />
RZQ/6 supported? Yes<br />
RZQ/7 supported? Yes<br />
DLL-Off Mode supported? No<br />
Operating temperature range 0-85C<br />
Refresh Rate in extended temp range 1X<br />
Auto Self-Refresh? Yes<br />
On-Die Thermal Sensor readout? No<br />
Partial Array Self-Refresh? No<br />
Thermal Sensor Accuracy Not implemented<br />
SDRAM Device Type Standard Monolithic<br />
<br />
---=== Physical Characteristics ===---<br />
Module Height (mm) 15<br />
Module Thickness (mm) 1 front, 1 back<br />
Module Width (mm) 133.5<br />
Module Reference Card B<br />
<br />
---=== Manufacturer Data ===---<br />
Module Manufacturer Invalid<br />
Manufacturing Location Code 0x02<br />
Part Number OCZ3G1600LV2G <br />
<br />
...<br />
</nowiki>}}<br />
<br />
== Using sensor data ==<br />
=== Graphical Front-ends ===<br />
There are a variety of front-ends for sensors data.<br />
*{{Pkg|ksensors}} - ksensors is nice lm_sensors front-end for [[KDE]]<br />
*{{Pkg|xsensors}} - X11 interface to lm_sensors<br />
*{{Pkg|xfce4-sensors-plugin}} - A lm_sensors plugin for the [[Xfce]] panel<br />
*[[conky]] - Conky is an advanced, highly configurable system monitor for X based on torsmo<br />
*{{Pkg|kdeutils-superkaramba}} - Superkaramba is a tool which gives posibility to create different widgets for KDE desktop. Check the [http://www.kde-look.org/index.php?xcontentmode=38 karamba section on kde-look.org] for examples of making karamba front-ends for sensors data.<br />
*{{pkg|sensors-applet}} - applet for the [[GNOME]] Panel to display readings from hardware sensors, including CPU temperature, fan speeds and voltage readings.<br />
<br />
=== sensord ===<br />
There is an optional daemon called sensord (included with the {{Pkg|lm_sensors}} package) which can log your data to a round robin database (rrd) and later visualize graphically. See the sensord man page for details.<br />
<br />
==Troubleshooting==<br />
=== Renumbering Cores for Multi-CPU Systems ===<br />
In rare cases, the actual numbering of physical cores on multi-processor motherboards can be incorrect. Consider the following HP Z600 workstation with dual Xeons:<br />
{{hc|$ sensors|<nowiki><br />
coretemp-isa-0000<br />
Adapter: ISA adapter<br />
Core 0: +65.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core 1: +65.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core 9: +66.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core 10: +66.0°C (high = +85.0°C, crit = +95.0°C)<br />
<br />
coretemp-isa-0004<br />
Adapter: ISA adapter<br />
Core 0: +54.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core 1: +56.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core 9: +60.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core 10: +61.0°C (high = +85.0°C, crit = +95.0°C)<br />
<br />
smsc47b397-isa-0480<br />
Adapter: ISA adapter<br />
fan1: 1730 RPM<br />
fan2: 1746 RPM<br />
fan3: 1224 RPM<br />
fan4: 2825 RPM<br />
temp1: +46.0°C<br />
temp2: +37.0°C<br />
temp3: +23.0°C<br />
temp4: -128.0°C<br />
</nowiki>}}<br />
<br />
Note the cores are numbered 0, 1, 9, 10 which is repeated into the second CPU. Most users want the core temperatures to report out in sequential order, i.e. 0,1,2,3,4,5,6,7. Fixing the order is accomplished in two steps.<br />
<br />
====Step 1. ID what each chip is reporting ====<br />
<br />
Run {{ic|sensors}} with the {{ic|-u}} switch to see what options are available for each physical chip:<br />
<br />
{{hc|$ sensors -u coretemp-isa-0000|<nowiki><br />
coretemp-isa-0000<br />
Adapter: ISA adapter<br />
Core 0:<br />
temp2_input: 61.000<br />
temp2_max: 85.000<br />
temp2_crit: 95.000<br />
temp2_crit_alarm: 0.000<br />
Core 1:<br />
temp3_input: 61.000<br />
temp3_max: 85.000<br />
temp3_crit: 95.000<br />
temp3_crit_alarm: 0.000<br />
Core 9:<br />
temp11_input: 62.000<br />
temp11_max: 85.000<br />
temp11_crit: 95.000<br />
Core 10:<br />
temp12_input: 63.000<br />
temp12_max: 85.000<br />
temp12_crit: 95.000<br />
</nowiki>}}<br />
<br />
{{hc|$ sensors -u coretemp-isa-0004|<nowiki><br />
coretemp-isa-0004<br />
Adapter: ISA adapter<br />
Core 0:<br />
temp2_input: 53.000<br />
temp2_max: 85.000<br />
temp2_crit: 95.000<br />
temp2_crit_alarm: 0.000<br />
Core 1:<br />
temp3_input: 54.000<br />
temp3_max: 85.000<br />
temp3_crit: 95.000<br />
temp3_crit_alarm: 0.000<br />
Core 9:<br />
temp11_input: 59.000<br />
temp11_max: 85.000<br />
temp11_crit: 95.000<br />
Core 10:<br />
temp12_input: 59.000<br />
temp12_max: 85.000<br />
temp12_crit: 95.000<br />
</nowiki>}}<br />
<br />
==== Step 2. Redefine the cores ====<br />
<br />
Create {{ic|/etc/sensors.d/cores.conf}} wherein the new definitions are defined based on the output of step 1:<br />
<br />
{{hc|/etc/sensors.d/cores.conf|<nowiki><br />
chip "coretemp-isa-0000"<br />
<br />
label temp2 "Core 0"<br />
label temp3 "Core 1"<br />
label temp11 "Core 2"<br />
label temp12 "Core 3"<br />
<br />
chip "coretemp-isa-0004"<br />
<br />
label temp2 "Core 4"<br />
label temp3 "Core 5"<br />
label temp11 "Core 6"<br />
label temp12 "Core 7"</nowiki>}}<br />
<br />
Problem solved. Output after completing these steps:<br />
<br />
{{hc|$ sensors|<nowiki><br />
coretemp-isa-0000<br />
Adapter: ISA adapter<br />
Core0: +64.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core1: +63.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core2: +65.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core3: +66.0°C (high = +85.0°C, crit = +95.0°C)<br />
<br />
coretemp-isa-0004<br />
Adapter: ISA adapter<br />
Core4: +53.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core5: +54.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core6: +59.0°C (high = +85.0°C, crit = +95.0°C)<br />
Core7: +60.0°C (high = +85.0°C, crit = +95.0°C)<br />
<br />
smsc47b397-isa-0480<br />
Adapter: ISA adapter<br />
fan1: 1734 RPM<br />
fan2: 1726 RPM<br />
fan3: 1222 RPM<br />
fan4: 2827 RPM<br />
temp1: +45.0°C <br />
temp2: +37.0°C <br />
temp3: +23.0°C <br />
temp4: -128.0°C <br />
</nowiki>}}<br />
<br />
=== Sensors not working since Linux 2.6.31 ===<br />
A change in version 2.6.31 has made some sensors stop working. See [http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31 this FAQ entry] for a detailed explanation and for some example errors. To fix sensors, add the following to your kernel boot line (e.g. in your [[GRUB]]/[[GRUB2]] configuration file) and reboot your machine:<br />
acpi_enforce_resources=lax<br />
{{Warning|In some situations, this may be dangerous. Consult the FAQ for details.}}<br />
<br />
Note that in most cases the information is still accessible via other modules (e.g. via ACPI modules) for the hardware in question. Many utilities and monitors (e.g. {{ic|/usr/bin/sensors}}) can gather information from either source. Where possible, this is the preferred solution.<br />
<br />
===K10Temp Module===<br />
<br />
Some K10 processors have issues with their temperature sensor. From the kernel documentation ({{ic|linux-&lt;version&gt;/Documentation/hwmon/k10temp}}):<br />
:''All these processors have a sensor, but on those for Socket F or AM2+, the sensor may return inconsistent values (erratum 319). The driver will refuse to load on these revisions unless you specify the {{ic|1=force=1}} module parameter.''<br />
<br />
:''Due to technical reasons, the driver can detect only the mainboard's socket type, not the processor's actual capabilities. Therefore, if you are using an AM3 processor on an AM2+ mainboard, you can safely use the {{ic|1=force=1}} parameter.''<br />
<br />
On affected machines the module will report "unreliable CPU thermal sensor; monitoring disabled". If you still want to use the module you can:<br />
# rmmod k10temp<br />
# modprobe k10temp force=1<br />
Confirm with [[Lm_sensors#Testing your lm_sensors]] that the sensor is in fact valid and reliable. If it is, you can edit {{ic|/etc/modprobe.d/k10temp.conf}} and add:<br />
options k10temp force=1<br />
This will allow the module to load at boot.<br />
<br />
==See also==<br />
*[[hddtemp]] - Software to read temperatures of hard drives.<br />
*[[monitorix]] - Monitorix is a free, open source, lightweight system monitoring tool designed to monitor as many services and system resources as possible.</div>Valentt