Changes between Version 3 and Version 4 of FAQ/Chapter3

Timestamp:

06/24/06 11:08:31 (7 years ago)

Author:

ruik

Comment:

Fix trac links

FAQ/Chapter3

@@ -21 +21 @@
 }}}
 
-See [source:lm-sensors/trunk/lm_sensors2/doc/fan-divisors doc/fan-divisors] in our package for further information.
+See [source:lm-sensors/trunk/doc/fan-divisors doc/fan-divisors] in our package for further information.
 
 
@@ -31 +31 @@
 You may not have a three-wire fan, which is required.
 
-You may need to increase the 'fan divisor'. See [source:lm-sensors/trunk/lm_sensors2/doc/fan-divisors doc/fan-divisors] in our package for further information.
+You may need to increase the 'fan divisor'. See [source:lm-sensors/trunk/doc/fan-divisors doc/fan-divisors] in our package for further information.
 
 
@@ -39 +39 @@
 
 
-Believe it or not, doubling the 'fan divisor' will not halve the fan reading. You have to add a compute line in /etc/sensors.conf. See My fans report exactly half/double their values compared to the BIOS, and see [source:lm-sensors/trunk/lm_sensors2/doc/fan-divisors doc/fan-divisors] in our package for further information.
+Believe it or not, doubling the 'fan divisor' will not halve the fan reading. You have to add a compute line in /etc/sensors.conf. See My fans report exactly half/double their values compared to the BIOS, and see [source:lm-sensors/trunk/doc/fan-divisors doc/fan-divisors] in our package for further information.
 
 
@@ -83 +83 @@
 
 
-The purpose of this scheme is to tell you if there has been a problem and report it to the user. Voltage or temperature spikes get detected without having to read the sensor chip hundreds of times a second. The implemetation details depend a bit on the kind of chip. See the specific chip documentation in [source:lm-sensors/trunk/lm_sensors2/doc/chips/ doc/chips/] and the chip datasheet for more information.
+The purpose of this scheme is to tell you if there has been a problem and report it to the user. Voltage or temperature spikes get detected without having to read the sensor chip hundreds of times a second. The implemetation details depend a bit on the kind of chip. See the specific chip documentation in [source:lm-sensors/trunk/doc/chips/ doc/chips/] and the chip datasheet for more information.
 
 
@@ -127 +127 @@
 
 
-The CPU nominal voltage is computed from VID lines according to a formula that depends on the CPU type. Most chips that report a VID value can be configured to use either VRM 8.2 (for Pentium III) or VRM 9.0 (for Pentium 4 and Athlon). You chose which one you want through /etc/sensors.conf. See [source:lm-sensors/trunk/lm_sensors2/doc/vid doc/vid] for more information.
+The CPU nominal voltage is computed from VID lines according to a formula that depends on the CPU type. Most chips that report a VID value can be configured to use either VRM 8.2 (for Pentium III) or VRM 9.0 (for Pentium 4 and Athlon). You chose which one you want through /etc/sensors.conf. See [source:lm-sensors/trunk/doc/vid doc/vid] for more information.
 
 
@@ -247 +247 @@
 
 
-See below for some particularly troublesome chips. Also be sure and check [source:lm-sensors/trunk/lm_sensors2/doc/chips/ doc/chips/xxxx] for the particular driver.
+See below for some particularly troublesome chips. Also be sure and check [source:lm-sensors/trunk/doc/chips/ doc/chips/xxxx] for the particular driver.
 
 
@@ -271 +271 @@
 
 
-The MTP008 has programmable temperature sensor types. If your sensor type does not match the default, you will have to change it. See [source:lm-sensors/trunk/lm_sensors2/doc/chips/mtp008 doc/chips/mtp008] for details. Also, MTP008 chips seem to randomly refuse to respond, for unknown reasons. You can see this as 'XX' entries in i2cdump.
+The MTP008 has programmable temperature sensor types. If your sensor type does not match the default, you will have to change it. See [source:lm-sensors/trunk/doc/chips/mtp008 doc/chips/mtp008] for details. Also, MTP008 chips seem to randomly refuse to respond, for unknown reasons. You can see this as 'XX' entries in i2cdump.
 
 
@@ -287 +287 @@
 
 
-Do you own an ASUS motherboard? Perhaps your chip is being misidentified. Look on the motherboard (or at http://mbm.livewiredev.com) for a 'Winbond' or Asus chip. Often the real device is an Asus as99127f. If so, the driver can be forced to recognize the as99127f with force_as99127f=BUS,0x2d where BUS is your i2c bus number. Cat /proc/bus/i2c to see a list of bus numbers. Read the w83781d module documentation ([source:lm-sensors/trunk/lm_sensors2/doc/chips/w83781d doc/chips/w83781d]) for more details.
+Do you own an ASUS motherboard? Perhaps your chip is being misidentified. Look on the motherboard (or at http://mbm.livewiredev.com) for a 'Winbond' or Asus chip. Often the real device is an Asus as99127f. If so, the driver can be forced to recognize the as99127f with force_as99127f=BUS,0x2d where BUS is your i2c bus number. Cat /proc/bus/i2c to see a list of bus numbers. Read the w83781d module documentation ([source:lm-sensors/trunk/doc/chips/w83781d doc/chips/w83781d]) for more details.
 
 
@@ -353 +353 @@
 
 
-If the problem is a PCI device is not present in lspci, the solution is complex. For the ALI M7101 device, there is a solution which uses the 2.4 kernel's hotplug facility. See prog/hotplug in our package. For other PCI devices, you can try to modify the m7101 solution in [source:lm-sensors/trunk/lm_sensors2/prog/hotplug prog/hotplug].
-
-
-
-If dmesg says try force_addr, see below. Other drivers generally do not support the force_addr parameter. Sorry. Check the documentation for your driver in [source:lm-sensors/trunk/lm_sensors2/doc doc/] and if we don't support it you can send us your request.
+If the problem is a PCI device is not present in lspci, the solution is complex. For the ALI M7101 device, there is a solution which uses the 2.4 kernel's hotplug facility. See prog/hotplug in our package. For other PCI devices, you can try to modify the m7101 solution in [source:lm-sensors/trunk/prog/hotplug prog/hotplug].
+
+
+
+If dmesg says try force_addr, see below. Other drivers generally do not support the force_addr parameter. Sorry. Check the documentation for your driver in [source:lm-sensors/trunk/doc doc/] and if we don't support it you can send us your request.
 
 
@@ -459 +459 @@
 
 
-In general, we don't know. Start by running sensors-detect. If it doesn't recognize it, try running i2cdump. A partial list of manufacturers' IDs are at the bottom of [source:lm-sensors/trunk/lm_sensors2/doc/chips/SUMMARY doc/chips/SUMMARY].
+In general, we don't know. Start by running sensors-detect. If it doesn't recognize it, try running i2cdump. A partial list of manufacturers' IDs are at the bottom of [source:lm-sensors/trunk/doc/chips/SUMMARY doc/chips/SUMMARY].