summaryrefslogtreecommitdiff
path: root/doc/lm_sensors-FAQ.html
blob: 6ceab70a83d9206dadaf11c1ce8c902f90203b90 (plain) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371

<html lang="en">
<head>
<title>Sensors FAQ for lm_sensors version 2.18</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="Sensors FAQ for lm_sensors version 2.18">
<meta name="generator" content="makeinfo 4.8">
<link title="Top" rel="top" href="#Top">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
  pre.display { font-family:inherit }
  pre.format  { font-family:inherit }
  pre.smalldisplay { font-family:inherit; font-size:smaller }
  pre.smallformat  { font-family:inherit; font-size:smaller }
  pre.smallexample { font-size:smaller }
  pre.smalllisp    { font-size:smaller }
  span.sc    { font-variant:small-caps }
  span.roman { font-family:serif; font-weight:normal; } 
  span.sansserif { font-family:sans-serif; font-weight:normal; } 
--></style>
</head>
<body>
<h1 class="settitle">Sensors FAQ for lm_sensors version 2.18</h1>
Copyright (C) 1998 - 2005<br>
Frodo Looijaard,<br>
Philip Edelbrock,<br>
Mark D. Studebaker<br>
and<br>
Jean Delvare<br>

   <div class="shortcontents">
<h2>Short Contents</h2>
<ul>
<li><a href="#toc_Top">lm_sensors</a></li>
<li><a href="#toc_Overview">1 PC and Sensor Overview</a></li>
<li><a href="#toc_Basics">2 Sensor and Bus Basics</a></li>
<li><a href="#toc_Installation">3 Installation and Management</a></li>
<li><a href="#toc_Problems">4 Problems</a></li>
<li><a href="#toc_Help">5 How to Ask for Help</a></li>
<li><a href="#toc_Contribute">6 How to Contribute</a></li>
<li><a href="#toc_Document-Revisions">Appendix A Revision History of This Document</a></li>
</ul>
</div>

   <div class="contents">
<h2>Table of Contents</h2>
<ul>
<li><a name="toc_Top" href="#Top">lm_sensors</a>
<li><a name="toc_Overview" href="#Overview">1 PC and Sensor Overview</a>
<ul>
<li><a href="#Section-1_002e1">1.1 What sensors are available on my PC?</a>
<li><a href="#Section-1_002e2">1.2 What can a sensor chip like the "LM78" do?</a>
<li><a href="#Section-1_002e3">1.3 Where do I find out more about any of these chips?</a>
</li></ul>
<li><a name="toc_Basics" href="#Basics">2 Sensor and Bus Basics</a>
<ul>
<li><a href="#Section-2_002e1">2.1 How are these sensors read?</a>
<li><a href="#Section-2_002e2">2.2 What is the SMBus? And the I2C bus?</a>
<li><a href="#Section-2_002e3">2.3 I don't have an ISA bus!</a>
<li><a href="#Section-2_002e4">2.4 What sensors do processors have?</a>
<li><a href="#Section-2_002e5">2.5 How often are the sensor values updated?</a>
<li><a href="#Section-2_002e6">2.6 How are alarms triggered?</a>
</li></ul>
<li><a name="toc_Installation" href="#Installation">3 Installation and Management</a>
<ul>
<li><a href="#Section-3_002e1">3.1 Why so many modules, and how do I cope with them?</a>
<li><a href="#Section-3_002e2">3.2 How do I know which chips I own?</a>
<ul>
<li><a href="#Section-3_002e2">3.2.1 What chips are on motherboard XYZ?</a>
<li><a href="#Section-3_002e2">3.2.2 Do you support motherboard XYZ?</a>
<li><a href="#Section-3_002e2">3.2.3 Do you support chip XYZ?</a>
<li><a href="#Section-3_002e2">3.2.4 Anybody working on a driver for chip XYZ?</a>
</li></ul>
<li><a href="#Section-3_002e3">3.3 Which modules should I insert?</a>
<li><a href="#Section-3_002e4">3.4 Do I need the configuration file <samp><span class="file">/etc/sensors.conf</span></samp>?</a>
<ul>
<li><a href="#Section-3_002e4">3.4.1 The labels for the voltage and temperature readings in <samp><span class="command">sensors</span></samp> are incorrect!</a>
<li><a href="#Section-3_002e4">3.4.2 The min and max for the readings in <samp><span class="command">sensors</span></samp> are incorrect!</a>
<li><a href="#Section-3_002e4">3.4.3 The min and max settings in <samp><span class="file">/etc/sensors.conf</span></samp> didn't take effect!</a>
<li><a href="#Section-3_002e4">3.4.4 One sensor isn't hooked up on my board!</a>
<li><a href="#Section-3_002e4">3.4.5 I need help with <samp><span class="file">sensors.conf</span></samp>!</a>
<li><a href="#Section-3_002e4">3.4.6 Do you have a database of <samp><span class="file">sensors.conf</span></samp> entries for specific boards?</a>
</li></ul>
<li><a href="#Section-3_002e5">3.5 What about the `<samp><span class="samp">No such file or directory</span></samp>' warnings when I compile?</a>
<li><a href="#Section-3_002e6">3.6 I get all kinds of weird compilation errors?</a>
<ul>
<li><a href="#Section-3_002e6">3.6.1 `<samp><span class="samp">No rule to make target xxxx needed by xxxx</span></samp>' - how to fix?</a>
</li></ul>
<li><a href="#Section-3_002e7">3.7 It still does not compile or patch!</a>
<li><a href="#Section-3_002e8">3.8 <samp><span class="command">make install</span></samp> fails on Mandrake kernels</a>
<li><a href="#Section-3_002e9">3.9 I get unresolved symbols when I <samp><span class="command">modprobe</span></samp> modules (Red Hat especially)</a>
<li><a href="#Section-3_002e10">3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</a>
</li></ul>
<li><a name="toc_Problems" href="#Problems">4 Problems</a>
<ul>
<li><a href="#Section-4_002e1">4.1 My fans report exactly half/double their values compared to the BIOS?</a>
<ul>
<li><a href="#Section-4_002e1">4.1.1 Fans sometimes/always read 0!!</a>
<li><a href="#Section-4_002e1">4.1.2 I doubled the fan divisor and the fan still reads 7000!</a>
</li></ul>
<li><a href="#Section-4_002e2">4.2 Why do my two LM75's report "-48 degrees"?</a>
<li><a href="#Section-4_002e3">4.3 Why do I have two Vcore readings, I have only one processor!</a>
<li><a href="#Section-4_002e4">4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!</a>
<li><a href="#Section-4_002e5">4.5 My voltage readings seem to drift a bit. Is something wrong?</a>
<li><a href="#Section-4_002e6">4.6 Some measurements are way out of range. What happened?</a>
<ul>
<li><a href="#Section-4_002e6">4.6.1 -5V and -12V readings are way out of range!</a>
</li></ul>
<li><a href="#Section-4_002e7">4.7 What are VID lines? Why is the VID reading wrong?</a>
<li><a href="#Section-4_002e8">4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?</a>
<li><a href="#Section-4_002e9">4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?</a>
<li><a href="#Section-4_002e10">4.10 Can I be alerted when an ALARM occurs?</a>
<li><a href="#Section-4_002e11">4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?</a>
<li><a href="#Section-4_002e12">4.12 My BIOS reports a much higher CPU temperature than your modules!</a>
<li><a href="#Section-4_002e13">4.13 I try to read the raw <samp><span class="file">/proc</span></samp> files, but the values are strange?!?</a>
<li><a href="#Section-4_002e14">4.14 How do I set new limits?</a>
<ul>
<li><a href="#Section-4_002e14">4.14.1 I set new limits and it didn't work?</a>
</li></ul>
<li><a href="#Section-4_002e15">4.15 Some sensors are doubly detected?</a>
<li><a href="#Section-4_002e16">4.16 I ran sensors-detect, but now I get very strange readings?!?</a>
<li><a href="#Section-4_002e17">4.17 Bad readings from particular chips</a>
<ul>
<li><a href="#Section-4_002e17">4.17.1 Bad readings from the AS99127F!</a>
<li><a href="#Section-4_002e17">4.17.2 Bad readings from the VIA 686A!</a>
<li><a href="#Section-4_002e17">4.17.3 Bad readings from the MTP008!</a>
<li><a href="#Section-4_002e17">4.17.4 Bad temperature readings from the SIS5595!</a>
<li><a href="#Section-4_002e17">4.17.5 Bad readings from a w8378[12]d!</a>
<li><a href="#Section-4_002e17">4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!</a>
<li><a href="#Section-4_002e17">4.17.7 Bad readings from LM75!</a>
<li><a href="#Section-4_002e17">4.17.8 Bad readings from LM78!</a>
<li><a href="#Section-4_002e17">4.17.9 Bad readings from LM80!</a>
</li></ul>
<li><a href="#Section-4_002e18">4.18 How do I configure two chips (LM87) differently?</a>
<li><a href="#Section-4_002e19">4.19 Dmesg says `<samp><span class="samp">Upgrade BIOS</span></samp>'! I don't want to!</a>
<ul>
<li><a href="#Section-4_002e19">4.19.1 Dmesg says `<samp><span class="samp">use force_addr=0xaddr</span></samp>'! What address do I use?</a>
</li></ul>
<li><a href="#Section-4_002e20">4.20 Sensors says `<samp><span class="samp">Can't access procfs/sysfs file</span></samp>'</a>
<li><a href="#Section-4_002e21">4.21 Sensors says `<samp><span class="samp">No sensors found!</span></samp>'</a>
<li><a href="#Section-4_002e22">4.22 Sensors output is not correct!</a>
<li><a href="#Section-4_002e23">4.23 What is at I2C address XXX?</a>
<ul>
<li><a href="#Section-4_002e23">4.23.1 What is at I2C address 0x69?</a>
<li><a href="#Section-4_002e23">4.23.2 What is at I2C addresses 0x50 - 0x57?</a>
<li><a href="#Section-4_002e23">4.23.3 What is at I2C addresses 0x30 - 0x37?</a>
</li></ul>
<li><a href="#Section-4_002e24">4.24 Sensors-detect doesn't work at all</a>
<ul>
<li><a href="#Section-4_002e24">4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"</a>
<li><a href="#Section-4_002e24">4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"</a>
<li><a href="#Section-4_002e24">4.24.3 Sensors-detect doesn't find any sensors!</a>
</li></ul>
<li><a href="#Section-4_002e25">4.25 Sensors says `<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>'</a>
<li><a href="#Section-4_002e26">4.26 Sensors only gives the name, adapter, and algorithm for my chip</a>
<li><a href="#Section-4_002e27">4.27 Sensors says `<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>'</a>
<li><a href="#Section-4_002e28">4.28 Sensors doesn't find any sensors, just eeproms.</a>
<li><a href="#Section-4_002e29">4.29 Inserting modules hangs my board</a>
<li><a href="#Section-4_002e30">4.30 Inserting modules slows down my board</a>
<li><a href="#Section-4_002e31">4.31 Problems on particular motherboards</a>
<ul>
<li><a href="#Section-4_002e31">4.31.1 Asus P4B</a>
<li><a href="#Section-4_002e31">4.31.2 Tyan 2460, 2462</a>
<li><a href="#Section-4_002e31">4.31.3 Tyan 2466</a>
<li><a href="#Section-4_002e31">4.31.4 Tyan 2688</a>
</li></ul>
<li><a href="#Section-4_002e32">4.32 Problems on particular systems</a>
<li><a href="#Section-4_002e33">4.33 Problems on 2.6 kernels</a>
<ul>
<li><a href="#Section-4_002e33">4.33.1 i2c-viapro and via686a</a>
<li><a href="#Section-4_002e33">4.33.2 Where are my EEPROMs?</a>
</li></ul>
</li></ul>
<li><a name="toc_Help" href="#Help">5 How to Ask for Help</a>
<ul>
<li><a href="#Section-5_002e1">5.1 What to send us when asking for help</a>
<li><a href="#Section-5_002e2">5.2 What to do if a module won't insert?</a>
<li><a href="#Section-5_002e3">5.3 What to do if it inserts, but nothing happens?</a>
<li><a href="#Section-5_002e4">5.4 What to do if I read only bogus information?</a>
<li><a href="#Section-5_002e5">5.5 What to do if you have other problems?</a>
<li><a href="#Section-5_002e6">5.6 What if it just works like a charm?</a>
<li><a href="#Section-5_002e7">5.7 How do I update a ticket?</a>
<li><a href="#Section-5_002e8">5.8 How do I follow up on a ticket?</a>
<li><a href="#Section-5_002e9">5.9 Why did you decide not to support undocumented chips?</a>
</li></ul>
<li><a name="toc_Contribute" href="#Contribute">6 How to Contribute</a>
<ul>
<li><a href="#Section-6_002e1">6.1 How to write a driver</a>
<li><a href="#Section-6_002e2">6.2 How to get SVN access</a>
<li><a href="#Section-6_002e3">6.3 How to donate hardware to the project</a>
<li><a href="#Section-6_002e4">6.4 How to join the project mailing lists</a>
<li><a href="#Section-6_002e5">6.5 How to access mailing list archives</a>
<li><a href="#Section-6_002e6">6.6 How to submit a patch</a>
<li><a href="#Section-6_002e7">6.7 How to REALLY help</a>
<li><a href="#Section-6_002e8">6.8 How to get release announcements</a>
</li></ul>
<li><a name="toc_Document-Revisions" href="#Document-Revisions">Appendix A Revision History of This Document</a>
</li></ul>
</div>

<div class="node">
<p><hr>
<a name="Top"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Overview">Overview</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#dir">(dir)</a>

</div>

<h2 class="unnumbered">lm_sensors</h2>

<p>The lm_sensors package includes a collection of modules for general SMBus
access and hardware monitoring.  NOTE: this requires special support which
is not in standard 2.2-vintage kernels.

<ul class="menu">
<li><a accesskey="1" href="#Overview">Overview</a>:                 PC and Sensor Overview
<li><a accesskey="2" href="#Basics">Basics</a>:                   Sensor and Bus Basics
<li><a accesskey="3" href="#Installation">Installation</a>:             Installation and Management
<li><a accesskey="4" href="#Problems">Problems</a>:                 Problems
<li><a accesskey="5" href="#Help">Help</a>:                     How to Ask for Help
<li><a accesskey="6" href="#Contribute">Contribute</a>:               How to Contribute
<li><a accesskey="7" href="#Document-Revisions">Document Revisions</a>:       Revision History of This Document
</ul>

<div class="node">
<p><hr>
<a name="Overview"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Basics">Basics</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Top">Top</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>

</div>

<h2 class="chapter">1 PC and Sensor Overview</h2>

<ul class="menu">
<li><a accesskey="1" href="#Section-1_002e1">Section 1.1</a>:              What sensors are available on my PC? 
<li><a accesskey="2" href="#Section-1_002e2">Section 1.2</a>:              What can a sensor chip like the "LM78" do? 
<li><a accesskey="3" href="#Section-1_002e3">Section 1.3</a>:              Where do I find out more about any of these chips? 
</ul>

<div class="node">
<p><hr>
<a name="Section-1.1"></a>
<a name="Section-1_002e1"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-1_002e2">Section 1.2</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Overview">Overview</a>

</div>

<h3 class="section">1.1 What sensors are available on my PC?</h3>

<p>Most PC's built since late 1997 now come with a
hardware health monitoring chip. This chip may be accessed via the
ISA bus or the SMBus, depending on the motherboard.

   <p>Some motherboard chipsets, notably the Via 686 and the SiS 5595,
contain hardware monitor functions.

   <p>This FAQ frequently refers to the "LM78". This chip has been
obsoleted by National Semiconductor. Most motherboards today contain
a chip with similar functions.

<div class="node">
<p><hr>
<a name="Section-1.2"></a>
<a name="Section-1_002e2"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-1_002e3">Section 1.3</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-1_002e1">Section 1.1</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Overview">Overview</a>

</div>

<h3 class="section">1.2 What can a sensor chip like the "LM78" do?</h3>

<p>The LM78 is a chip made by National Semiconductor which can monitor 7
voltages (5 positive, 2 negative) from 0 to 4.08V.  The inputs are usually in
series with voltage dividers which lower the +/- 12V and +/- 5V supplies to
measurable range.  Therefore, the readings for such inputs need to be
re-scaled appropriately by software.

   <p>The LM78 also has 3 fan speed monitoring inputs, an internal
temperature sensor, a chassis intrusion sensor, and a couple maskable interrupt
inputs.  The LM78 can also relay the processor's (P6 or Pent II) VID lines
which are hardwired and used to indicate to the power regulator (usually on
the mainboard close to the processor socket/slot) what voltage to supply to
the processor.

   <p>The LM78 can be interfaced to a system via the ISA bus and/or the
SMBus.

   <p>Most other sensor chips have comparable functionality. Each supported
chip is documented in the <samp><span class="file">doc/chips</span></samp> directory.

<div class="node">
<p><hr>
<a name="Section-1.3"></a>
<a name="Section-1_002e3"></a>
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-1_002e2">Section 1.2</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Overview">Overview</a>

</div>

<h3 class="section">1.3 Where do I find out more about any of these chips?</h3>

<p>Most semiconductor companies have comprehensive documentation,
including complete datasheets, on their websites. Analog Devices,
Dallas Semiconductor, Maxim, and National Semiconductor have the widest selection
of sensor chips. Their websites are:

     <ul>
  <li><a href="http://www.analog.com">http://www.analog.com</a>
  <li><a href="http://www.dalsemi.com">http://www.dalsemi.com</a>
  <li><a href="http://www.maxim-ic.com">http://www.maxim-ic.com</a>
  <li><a href="http://www.national.com">http://www.national.com</a>
</ul>

   <p>Please see the file <a href="http://www.lm-sensors.org/wiki/UsefulLinks">http://www.lm-sensors.org/wiki/UsefulLinks</a>
for links to other companies' websites.

<div class="node">
<p><hr>
<a name="Basics"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Installation">Installation</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Overview">Overview</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>

</div>

<h2 class="chapter">2 Sensor and Bus Basics</h2>

<ul class="menu">
<li><a accesskey="1" href="#Section-2_002e1">Section 2.1</a>:              What sensors are available on my PC? 
<li><a accesskey="2" href="#Section-2_002e2">Section 2.2</a>:              What can a sensor chip like the "LM78" do? 
<li><a accesskey="3" href="#Section-2_002e3">Section 2.3</a>:              Where do I find out more about any of these chips? 
<li><a accesskey="4" href="#Section-2_002e4">Section 2.4</a>:              What sensors are available on my PC? 
<li><a accesskey="5" href="#Section-2_002e5">Section 2.5</a>:              What can a sensor chip like the "LM78" do? 
<li><a accesskey="6" href="#Section-2_002e6">Section 2.6</a>:              Where do I find out more about any of these chips? 
</ul>

<div class="node">
<p><hr>
<a name="Section-2.1"></a>
<a name="Section-2_002e1"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-2_002e2">Section 2.2</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>

</div>

<h3 class="section">2.1 How are these sensors read?</h3>

<p>Sensor chips reside on either the ISA bus, the SMBus, or both. 
See the file <samp><span class="file">doc/chips/SUMMARY</span></samp> in our package for a list.

   <p>To communicate with chips on the ISA bus, the software uses
simple I/O reads and writes.

   <p>To communicate with chips on the SMBus, the software must
use an SMBus interface device, explained below.

<div class="node">
<p><hr>
<a name="Section-2.2"></a>
<a name="Section-2_002e2"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-2_002e3">Section 2.3</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e1">Section 2.1</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>

</div>

<h3 class="section">2.2 What is the SMBus? And the I2C bus?</h3>

<p>The SMBus is the "System Management Bus".  More specifically, it is a
2-wire, low-speed serial communication bus used for basic health monitoring
and hardware management. It is a specific implementation of the more
general I2C (pronunciation: I-squared-C) bus. In fact, both I2C devices
and SMBus devices may be connected to the same (I2C) bus.

   <p>The SMBus (or I2C bus) starts at the host controller, used for
starting transactions on the SMBus.  From the host interface, the
devices communicated with are the <dfn>slave</dfn> devices.  Each slave device has a
unique 7-bit address which the host uses to refer to that device.

   <p>For each supported SMBus host, there is a separate kernel module
which implements the communication protocol with the host. Some SMBus hosts
really operate on the SMBus level; these hosts can not cope with pure I2C
devices. Other hosts are in fact I2C hosts: in this case, we implement
the SMBus protocol in terms of I2C operations. But these hosts can also
talk to pure I2C devices.

<div class="node">
<p><hr>
<a name="Section-2.3"></a>
<a name="Section-2_002e3"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-2_002e4">Section 2.4</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e2">Section 2.2</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>

</div>

<h3 class="section">2.3 I don't have an ISA bus!</h3>

<p>We promise, you do, even if you don't have any old ISA slots. 
The "ISA Bus" exists in your computer even if you don't have ISA slots;
it is simply a memory-mapped area, 64KB in size (0x0000 - 0xFFFF)
where many "legacy" functions, such as keyboard and interrupt controllers,
are found. It isn't necessarily a separate physical bus. 
See the file <samp><span class="file">/proc/ioports</span></samp> for a list of devices living on
the "ISA Bus" in your system. If you don't like the term "ISA Bus"
think "I/O Space".

<div class="node">
<p><hr>
<a name="Section-2.4"></a>
<a name="Section-2_002e4"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-2_002e5">Section 2.5</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e3">Section 2.3</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>

</div>

<h3 class="section">2.4 What sensors do processors have?</h3>

<p>Most new processors contain a thermal diode on the die itself. 
The electical properties of all diodes and transistors vary
slightly with temperature. The thermal diode is exceptionally accurate
because it is directly on the die. Newer temperature sensor chips,
like the Analog Devices ADM1021 and clones, and the Winbond chips,
have circuitry for measuring the the electrical properties of
an external diode and converting this data to a temperature. 
Any sensor chip listed in <samp><span class="file">doc/chips/SUMMARY</span></samp> in our package which
has support for more than one temperature supports external temperature sensing.

   <p>Older motherboards and processors without this feature generally use
an LM75 placed close to the processor. This is much less accurate.

   <p>The Pentium 2 'boxed' processor usually has an LM75 very close to the
base of the box. It can be read through the SMBus to report the approximate
temperature of the processor.  The processor also contains an internal
temperature sensor (of low accuracy) used as a fail-safe to disable the
processor in case it gets much too hot (usually around 130 degrees C).  And,
the Pentium 2 also has a hard-wired signal (VID lines) on it's SEC (single
edge connector) which indicates what power supply is required to operate the
processor.

   <p>The P6 (Pentium-Pro) may have an LM75 in or just under the socket. 
P6's also have VID lines.

   <p>Pentiums and Pentium w/ MMX do not have VID lines, and sometimes have
LM75's under the sockets (depends on the mainboard, and how 'modern' the
mainboard is).

   <p>The P2 Xeon was the first Intel processor to include the SMBus
interface on the P2 Xeon SEC.

<div class="node">
<p><hr>
<a name="Section-2.5"></a>
<a name="Section-2_002e5"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-2_002e6">Section 2.6</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e4">Section 2.4</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>

</div>

<h3 class="section">2.5 How often are the sensor values updated?</h3>

<p>The LM78, and most other sensor chips like it, reads its sensors one
by one. A complete scanning sweep will take about 1.5 seconds. The LM78 stops
readings sensors if you try to access it, so if you access it very often
(by reading sensor values; writing new limits is safe) it will not find the
time to update its sensor values at all! Fortunately, the kernel module takes
care not to do this, and only reads new values each 1.5 seconds. If you
read the values again, you will get the 'old' values again.

<div class="node">
<p><hr>
<a name="Section-2.6"></a>
<a name="Section-2_002e6"></a>
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e5">Section 2.5</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>

</div>

<h3 class="section">2.6 How are alarms triggered?</h3>

<p>It is possible to monitor each sensor and have an alarm go off if
it crosses some pre-determined limits.  There are two sorts of interrupts
which can be generated by sensor chips if this happens (it depends a bit on
the actual chip if both are supported; the LM80, for example, has only
IRQ interrupts): IRQ interrupts and SMI interrupts.  IRQ stands for
Interrupt Request and are the interrupt lines you can find in <samp><span class="file">/proc/interrupts</span></samp>. 
SMI stands for System Management Interrupt, and is a special interrupt which
puts the processor in a secure environment independent of any other things
running.  SMI is currently not supported by the Linux kernel.  IRQs are
supported, of course.

   <p>Even if no interrupt is generated, some bits in a status register
will be set until the register is read the next time. If the alarm condition
persists after that, the bits will be set on the next scanning sweep, etc.

   <p>Most drivers in our package do not support interrupts at this time.

<div class="node">
<p><hr>
<a name="Installation"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Problems">Problems</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Basics">Basics</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>

</div>

<h2 class="chapter">3 Installation and Management</h2>

<ul class="menu">
<li><a accesskey="1" href="#Section-3_002e1">Section 3.1</a>:      Why so many modules, and how do I cope with them? 
<li><a accesskey="2" href="#Section-3_002e2">Section 3.2</a>:      How do I know which chips I own? 
<li><a accesskey="3" href="#Section-3_002e3">Section 3.3</a>:      Which modules should I insert? 
<li><a accesskey="4" href="#Section-3_002e4">Section 3.4</a>:      Do I need the configuration file <samp><span class="file">/etc/sensors.conf</span></samp>? 
<li><a accesskey="5" href="#Section-3_002e5">Section 3.5</a>:      What about the `<samp><span class="samp">No such file or directory</span></samp>' warnings
<li><a accesskey="6" href="#Section-3_002e6">Section 3.6</a>:      I get all kinds of weird compilation errors? 
<li><a accesskey="7" href="#Section-3_002e7">Section 3.7</a>:      It still does not compile or patch! 
<li><a accesskey="8" href="#Section-3_002e8">Section 3.8</a>:      <samp><span class="command">make install</span></samp> fails on Mandrake kernels
<li><a accesskey="9" href="#Section-3_002e9">Section 3.9</a>:      I get unresolved symbols when I <samp><span class="command">modprobe</span></samp> modules
<li><a href="#Section-3_002e10">Section 3.10</a>:     I2C_DRIVERID_ADM1024 undefined (Red Hat especially)
</ul>

<div class="node">
<p><hr>
<a name="Section-3.1"></a>
<a name="Section-3_002e1"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e2">Section 3.2</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>

</div>

<h3 class="section">3.1 Why so many modules, and how do I cope with them?</h3>

<p>We tried to make this package as modular as possible. This makes it
easy to add new drivers, and unused drivers will take no precious kernel
space. On the other hand, it can be a bit confusing at first.

   <p>Here are two simple guidelines:
     <ul>
  <li>Run <samp><span class="command">sensors-detect</span></samp> and do what it tells you. 
  <li>Always use <samp><span class="command">modprobe</span></samp>, not <samp><span class="command">insmod</span></samp>. 
</ul>

   <p>Further information is in <samp><span class="file">doc/modules</span></samp>.

   <p><a name="How-do-I-know-which-chips-I-own"></a>
<div class="node">
<p><hr>
<a name="Section-3.2"></a>
<a name="Section-3_002e2"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e3">Section 3.3</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e1">Section 3.1</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>

</div>

<h3 class="section">3.2 How do I know which chips I own?</h3>

<p>We have an excellent program that scans all your hardware. 
It is called <samp><span class="file">sensors-detect</span></samp> and is installed in <samp><span class="file">/usr/local/sbin</span></samp>
by <samp><span class="command">make install</span></samp>. Just execute this script, and it will tell you.

   <p>Chip detection in the drivers is fairly good. That means that it is
usually harmless to insert more chip drivers than you need. However, this
can still lead to problems, so we do not recommend it.

   <p>If sensors-detect didn't find any sensors, either you don't have
any, or the ones you have, we don't support. (Look at your motherboard
for candidates, then see <a href="#Help">Help</a>)

   <p><a name="Section-3_002e2_002e1"></a>

<h4 class="subsection">3.2.1 What chips are on motherboard XYZ?</h4>

<p><strong>!!!!!!!!! YES THIS IS THE MOST FREQUENT QUESTION WE GET !!!!!!!!!</strong>

   <p>We have no idea. Here is what you should do:
     <ol type=1 start=1>
  <li>Run sensors-detect.
        </ol>

   <p>If that doesn't work:
     <ol type=1 start=2>
<li>Look at your motherboard. 
<li>Check the manufacturer's website or ask their support
<li>Check the <a href="http://mbm.livewiredev.com/">Motherboard Monitor</a> website and the
<a href="http://www.lm-sensors.org/wiki/UsefulLinks">"links"</a>
page on <a href="http://www.lm-sensors.org">our website</a> some good cross-references.
        </ol>

   <p><a name="Section-3_002e2_002e2"></a>

<h4 class="subsection">3.2.2 Do you support motherboard XYZ?</h4>

<p>We don't support boards, we support chips. See <a href="#Section-3_002e2_002e1">What chips are on motherboard XYZ</a>.

   <p><a name="Section-3_002e2_002e3"></a>

<h4 class="subsection">3.2.3 Do you support chip XYZ?</h4>

<p>This we have good answers for.
     <ul>
<li>Sorted by Manufacturer:   <samp><span class="file">README</span></samp>
<li>Sorted by Manufacturer:   <a href="http://www.lm-sensors.org/wiki/Devices">http://www.lm-sensors.org/wiki/Devices</a>
<li>Sorted by Sensor Driver:  <samp><span class="file">doc/chips/SUMMARY</span></samp>
</ul>

   <p><a name="Section-3_002e2_002e4"></a>

<h4 class="subsection">3.2.4 Anybody working on a driver for chip XYZ?</h4>

<p>Newest Driver Status: <a href="http://www.lm-sensors.org/wiki/Devices">http://www.lm-sensors.org/wiki/Devices</a>

<div class="node">
<p><hr>
<a name="Section-3.3"></a>
<a name="Section-3_002e3"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e4">Section 3.4</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e2">Section 3.2</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>

</div>

<h3 class="section">3.3 Which modules should I insert?</h3>

<p><samp><span class="command">sensors-detect</span></samp> will tell you. Take the <samp><span class="command">modprobe</span></samp> lines it
recommends and paste them into the appropriate <samp><span class="file">/etc/rc.d/xxxx</span></samp> file
to be executed at startup.

   <p>You need one module for each sensor chip and bus adapter you own;
if there are sensor chips on the ISA bus, you also need <samp><span class="file">i2c-isa.o</span></samp>. 
for each type of chip you own. That's all. On my computer, I could use the
following lines:
     <ul>
<li><samp><span class="command">modprobe i2c-isa</span></samp>
<li><samp><span class="command">modprobe i2c-piix4</span></samp>
<li><samp><span class="command">modprobe lm78</span></samp>
<li><samp><span class="command">modprobe lm75</span></samp>
<li><samp><span class="command">modprobe i2c-dev</span></samp>
<li><samp><span class="command">sensors -s</span></samp>
</ul>

<div class="node">
<p><hr>
<a name="Section-3.4"></a>
<a name="Section-3_002e4"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e5">Section 3.5</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e3">Section 3.3</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>

</div>

<h3 class="section">3.4 Do I need the configuration file <samp><span class="file">/etc/sensors.conf</span></samp>?</h3>

<p>Yes, for any applications that use <samp><span class="file">libsensors,</span></samp> including the
<samp><span class="command">sensors</span></samp> application included in our package. 
It tells libsensors how to translate the values the chip
measures to real-world values. This is especially important for voltage
inputs. The default configuration file should usually do the trick. 
It is automatically installed as <samp><span class="file">/etc/sensors.conf</span></samp>, but it will not
overwrite any existing file with that name.

   <p><a name="Section-3_002e4_002e1"></a>

<h4 class="subsection">3.4.1 The labels for the voltage and temperature readings in <samp><span class="command">sensors</span></samp> are incorrect!</h4>

<p>Every motherboard is different. You can customize the labels
in the file <samp><span class="file">/etc/sensors.conf</span></samp>. That's why it exists! 
The default labelling (in <samp><span class="file">lib/chips.c</span></samp> and <samp><span class="file">/etc/sensors.conf</span></samp>) is just
a template.

   <p><a name="Section-3_002e4_002e2"></a>

<h4 class="subsection">3.4.2 The min and max for the readings in <samp><span class="command">sensors</span></samp> are incorrect!</h4>

<p>You can customize them in the file <samp><span class="file">/etc/sensors.conf</span></samp>. See above.

   <p><a name="Section-3_002e4_002e3"></a>

<h4 class="subsection">3.4.3 The min and max settings in <samp><span class="file">/etc/sensors.conf</span></samp> didn't take effect!</h4>

<p>You forgot to run <samp><span class="command">sensors -s</span></samp>. See above.

   <p><a name="Section-3_002e4_002e4"></a>

<h4 class="subsection">3.4.4 One sensor isn't hooked up on my board!</h4>

<p>Use an <samp><span class="command">ignore</span></samp> line in <samp><span class="file">/etc/sensors.conf</span></samp> so it isn't
displayed in <samp><span class="command">sensors</span></samp>.

   <p><a name="Section-3_002e4_002e5"></a>

<h4 class="subsection">3.4.5 I need help with <samp><span class="file">sensors.conf</span></samp>!</h4>

<p>There is detailed help at the top of that file.

   <p><a name="Section-3_002e4_002e6"></a>

<h4 class="subsection">3.4.6 Do you have a database of <samp><span class="file">sensors.conf</span></samp> entries for specific boards?</h4>

<p>No. Good idea though. If you would like to set one up on your website
send us mail and we will set up a link to it.

<div class="node">
<p><hr>
<a name="Section-3.5"></a>
<a name="Section-3_002e5"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e6">Section 3.6</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e4">Section 3.4</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>

</div>

<h3 class="section">3.5 What about the `<samp><span class="samp">No such file or directory</span></samp>' warnings when I compile?</h3>

<p>Don't worry about them. The dependency files (which tell which
files should be recompiled when certain files change) are created
dynamically. They are not distributed with the package. The <samp><span class="command">make</span></samp> program
notices they are not there, and warns about that - and the first thing
it will do is generate them. So all is well.

<div class="node">
<p><hr>
<a name="Section-3.6"></a>
<a name="Section-3_002e6"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e7">Section 3.7</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e5">Section 3.5</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>

</div>

<h3 class="section">3.6 I get all kinds of weird compilation errors?</h3>

<p>Check that the correct i2c header files are used. Depending on
how you installed, they should be under either <samp><span class="file">/usr/local/include</span></samp> or
<samp><span class="file">/usr/src/linux*/include</span></samp>. Try to edit the <samp><span class="file">Makefile</span></samp> for the other setting.

   <p><a name="Section-3_002e6_002e1"></a>

<h4 class="subsection">3.6.1 `<samp><span class="samp">No rule to make target xxxx needed by xxxx</span></samp>' - how to fix?</h4>

     <ul>
<li>See <a href="#Section-3_002e6">I get all kinds of weird compilation errors</a>, also try <samp><span class="command">make clean</span></samp> in <samp><span class="file">lm_sensors</span></samp>. 
<li>If that doesn't work, try <samp><span class="command">make clean</span></samp> in <samp><span class="file">i2c</span></samp>. 
<li>If that doesn't work, try <samp><span class="command">make clean</span></samp> in the kernel. 
<li>Also make sure <samp><span class="file">/usr/include/linux</span></samp> points to <samp><span class="file">/usr/src/linux/include/linux</span></samp>. 
</ul>

<div class="node">
<p><hr>
<a name="Section-3.7"></a>
<a name="Section-3_002e7"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e8">Section 3.8</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e6">Section 3.6</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>

</div>

<h3 class="section">3.7 It still does not compile or patch!</h3>

<p>Have you installed the matching version of the i2c package? Remember,
compilation is not enough, you also need to install it for the header
files to be found!

   <p>If you want to patch the kernel, you will have to apply the i2c
patches first!

<div class="node">
<p><hr>
<a name="Section-3.8"></a>
<a name="Section-3_002e8"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e9">Section 3.9</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e7">Section 3.7</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>

</div>

<h3 class="section">3.8 <samp><span class="command">make install</span></samp> fails on Mandrake kernels</h3>

<p>Mandrake uses a non-standard <samp><span class="file">version.h</span></samp> file which confuses our <samp><span class="file">Makefile</span></samp>. 
Edit our <samp><span class="file">Makefile</span></samp> on the <code>MODDIR :=</code> line to hard-code the module directory.

<div class="node">
<p><hr>
<a name="Section-3.9"></a>
<a name="Section-3_002e9"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e10">Section 3.10</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e8">Section 3.8</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>

</div>

<h3 class="section">3.9 I get unresolved symbols when I <samp><span class="command">modprobe</span></samp> modules (Red Hat especially)</h3>

<p>Example:
<pre class="example">     *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/i2c/i2c-i810.o
     i2c_bit_add_bus_R8c3bc60e
     i2c_bit_del_bus_R92b18f49
</pre>
   <p>You can also run <samp><span class="command">depmod -a -e</span></samp> to see all unresolved symbols.

   <p>These are module versioning problems. Generally you did not compile
against the kernel you are running. Sometimes the Red Hat source you
have is not for the kernel you are running. 
You must compile our package against the source for the kernel you
are running with something like <samp><span class="command">make LINUX=/usr/src/linux-2.4.14</span></samp>.

   <p>Try the following to be sure:

     <ul>
<li><samp><span class="command">nm --extern MODULE.o</span></samp>
Filter out the kernel symbols, like <code>kmalloc</code>, <code>printk</code> etc. and note the
number code behind them, like <code>printk_R1b7d4074</code>. If there is no numeric
code after them, note this too. 
<li><samp><span class="command">grep SYMBOL /proc/ksyms</span></samp>
Substitute SYMBOL by the basename of the symbols above, like <code>kmalloc</code>,
<code>printk</code> etc. Note the number code behind them, or the lack thereof. 
<li>Compare both sets of symbols. Are they the same? If so, the problem
lies somewhere else. Are they different? If so, you have a module
versioning problem. 
</ul>

<div class="node">
<p><hr>
<a name="Section-3.10"></a>
<a name="Section-3_002e10"></a>
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e9">Section 3.9</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>

</div>

<h3 class="section">3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</h3>

<p>In some versions of Redhat, an RPM is included to provide i2c support. 
However, this RPM does not place the header files in the kernel directory
structure.  When you update kernels, they may persist.  To get rid of
these obsolete header files, at a command prompt:

     <ol type=1 start=1>
<li><samp><span class="command">rpm -qa | grep i2c</span></samp>
<li>Look for <samp><span class="file">kernel-i2c,</span></samp> or a similar rpm in the output
<li>&lt;as root&gt;
<samp><span class="command">rpm -ev kernel-i2c</span></samp> (or the name of the similar package)
If this complains about dependencies, you can try adding
<samp><span class="command">--nodeps</span></samp>, but this *MAY* break something else.  Not likely,
as you have upgraded kernels, and nothing should be using the
old i2c stuff anymore anyway.  Just don't use it with abandon. 
<li>Try (in the build directory of <samp><span class="file">lm_sensors)</span></samp>
     <pre class="example">          <samp><span class="command">make clean</span></samp>
          <samp><span class="command">make</span></samp>
     </pre>
     <li><em>If</em> you still have problems, you may have to replace the include
paths in the <samp><span class="file">.c/.h</span></samp> files with absolute paths to the header files. 
More of a workaround than a real fix, but at least you can get it
to work.
        </ol>

<div class="node">
<p><hr>
<a name="Problems"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Help">Help</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Installation">Installation</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>

</div>

<h2 class="chapter">4 Problems</h2>

<ul class="menu">
<li><a accesskey="1" href="#Section-4_002e1">Section 4.1</a>:          My fans report exactly half/double their values? 
<li><a accesskey="2" href="#Section-4_002e2">Section 4.2</a>:          Why do my two LM75's report "-48 degrees"? 
<li><a accesskey="3" href="#Section-4_002e3">Section 4.3</a>:          Why do I have two Vcore readings? 
<li><a accesskey="4" href="#Section-4_002e4">Section 4.4</a>:          How do those ALARMS work? 
<li><a accesskey="5" href="#Section-4_002e5">Section 4.5</a>:          My voltage readings seem to drift a bit. What's wrong? 
<li><a accesskey="6" href="#Section-4_002e6">Section 4.6</a>:          Some measurements are way out of range. What happened? 
<li><a accesskey="7" href="#Section-4_002e7">Section 4.7</a>:          What are VID lines? Why is the VID reading wrong? 
<li><a accesskey="8" href="#Section-4_002e8">Section 4.8</a>:          Sensor are only updated each second or so. Why? 
<li><a accesskey="9" href="#Section-4_002e9">Section 4.9</a>:          It takes a second before reading sensor results. Why? 
<li><a href="#Section-4_002e10">Section 4.10</a>:         Can I be alerted when an ALARM occurs? 
<li><a href="#Section-4_002e11">Section 4.11</a>:         SMBus transactions on my PIIX4 simply don't work. Why? 
<li><a href="#Section-4_002e12">Section 4.12</a>:         My BIOS reports a higher CPU temperature than you! 
<li><a href="#Section-4_002e13">Section 4.13</a>:         I read strange values from the raw <samp><span class="file">/proc</span></samp> files! 
<li><a href="#Section-4_002e14">Section 4.14</a>:         How do I set new limits? 
<li><a href="#Section-4_002e15">Section 4.15</a>:         Some sensors are doubly detected? 
<li><a href="#Section-4_002e16">Section 4.16</a>:         I ran sensors-detect, but now I get strange readings?! 
<li><a href="#Section-4_002e17">Section 4.17</a>:         Bad readings from particular chips
<li><a href="#Section-4_002e18">Section 4.18</a>:         How do I configure two chips (LM87) differently? 
<li><a href="#Section-4_002e19">Section 4.19</a>:         Dmesg says `<samp><span class="samp">Upgrade BIOS</span></samp>'! I don't want to! 
<li><a href="#Section-4_002e20">Section 4.20</a>:         Sensors says `<samp><span class="samp">Can't access procfs/sysfs file</span></samp>'
<li><a href="#Section-4_002e21">Section 4.21</a>:         Sensors says `<samp><span class="samp">No sensors found!</span></samp>'
<li><a href="#Section-4_002e22">Section 4.22</a>:         Sensors output is not correct! 
<li><a href="#Section-4_002e23">Section 4.23</a>:         What is at I2C address XXX? 
<li><a href="#Section-4_002e24">Section 4.24</a>:         Sensors-detect doesn't work at all
<li><a href="#Section-4_002e25">Section 4.25</a>:         Sensors says `<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>'
<li><a href="#Section-4_002e26">Section 4.26</a>:         Sensors only gives the name, adapter, and algorithm! 
<li><a href="#Section-4_002e27">Section 4.27</a>:         Sensors says `<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>'
<li><a href="#Section-4_002e28">Section 4.28</a>:         Sensors doesn't find any sensors, just eeproms. 
<li><a href="#Section-4_002e29">Section 4.29</a>:         Inserting modules hangs my board
<li><a href="#Section-4_002e30">Section 4.30</a>:         Inserting modules slows down my board
<li><a href="#Section-4_002e31">Section 4.31</a>:         Problems on particular motherboards
<li><a href="#Section-4_002e32">Section 4.32</a>:         Problems on particular systems
<li><a href="#Section-4_002e33">Section 4.33</a>:         Problems on 2.6 kernels
</ul>

<div class="node">
<p><hr>
<a name="Section-4.1"></a>
<a name="Section-4_002e1"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e2">Section 4.2</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.1 My fans report exactly half/double their values compared to the BIOS?</h3>

<p>The problem with much of the sensor data is that it is impossible to
properly interpret some of the readings without knowing what the hardware
configuration is.  Some fans report one 'tick' each rotation, some report
two 'ticks' each rotation. It is easy to resolve this through the
configuration file <samp><span class="file">/etc/sensors.conf</span></samp>:

<pre class="example">     chip lm78-*             # Or whatever chip this relates to
     compute fan1 2*@,@/2    # This will double the fan1 reading
                             # -- or --
     compute fan1 @/2,2*@    # This will halve the fan1 reading
</pre>
   <p>See <samp><span class="file">doc/fan-divisors</span></samp> in our package for further information.

   <p><a name="Fans-sometimes_002falways-read-0_0021"></a>

<h4 class="subsection">4.1.1 Fans sometimes/always read 0!!</h4>

<p>You may not have a three-wire fan, which is required.

   <p>You may need to increase the 'fan divisor'. See <samp><span class="file">doc/fan-divisors</span></samp>
in our package for further information.

   <p><a name="I-doubled-the-fan-divisor-and-the-fan-still-reads-7000"></a>

<h4 class="subsection">4.1.2 I doubled the fan divisor and the fan still reads 7000!</h4>

<p>Believe it or not, doubling the 'fan divisor' will not halve
the fan reading. You have to add a compute line in <samp><span class="file">/etc/sensors.conf</span></samp>. 
See <a href="#Section-4_002e1">My fans report exactly half/double their values compared to the BIOS</a>,
and see <samp><span class="file">doc/fan-divisors</span></samp> in our package for further information.

<div class="node">
<p><hr>
<a name="Section-4.2"></a>
<a name="Section-4_002e2"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e3">Section 4.3</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e1">Section 4.1</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.2 Why do my two LM75's report "-48 degrees"?</h3>

<p>For starters, those aren't LM75's.  Your mainboard actually has the
Winbond W83781D which emulates two LM75's, but many systems which use the
Winbond chip (such as the Asus P2B) don't have the thermo-resisters connected
to the chip resulting in these strange -48 degree readings.

   <p>In upcoming versions, you will be able to disable non-interesting
readings.

<div class="node">
<p><hr>
<a name="Section-4.3"></a>
<a name="Section-4_002e3"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e4">Section 4.4</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e2">Section 4.2</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.3 Why do I have two Vcore readings, I have only one processor!</h3>

<p>The LM78 has seven voltage sensors. The default way of
connecting them is used in the configuration file. This includes a VCore2,
even if you do not have one. You can easily edit the configuration file
to give it another name, or make this reading disappear using
an <samp><span class="command">ignore</span></samp> line.

   <p>Note that Vcore2 is often the same as Vcore on motherboards which
only support one processor. Another possibility is that Vcore2 is not
connected at all and will not have a valid reading at all. 
A third possibility, is that Vcore2 monitors something
else, so you should not be too surprised if the values are completely
different.

<div class="node">
<p><hr>
<a name="Section-4.4"></a>
<a name="Section-4_002e4"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e5">Section 4.5</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e3">Section 4.3</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!</h3>

<p>The ALARM indications in <samp><span class="command">sensors</span></samp> are those reported by the
sensor chip itself. They are NOT calculated by <samp><span class="command">sensors</span></samp>. <samp><span class="command">sensors</span></samp>
simply reads the ALARM bits and reports them.

   <p>An ALARM will go off when a minimum or maximum limit is crossed. 
The ALARM is then latched - that is, it will stay there until the
chip's registers are next accessed - which will be the next time
you read these values, but not within (usually) 1.5 seconds since the last
update.

   <p>Reading the registers clears the ALARMS, unless the current
value is still out of range.

   <p>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 <samp><span class="file">doc/chips</span></samp> and the
chip datasheet for more information.

<div class="node">
<p><hr>
<a name="Section-4.5"></a>
<a name="Section-4_002e5"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e6">Section 4.6</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e4">Section 4.4</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.5 My voltage readings seem to drift a bit. Is something wrong?</h3>

<p>No, probably not. If your motherboard heats up a bit, the sensed
voltages will drift a bit. If your power supply is loaded (because a disk
gets going, for example), the voltages may get a bit lower. Heavy
processor activity, in particular, dramatically increases core voltage
supply load which will often cause variation in the other supplies. 
As long as they stay within a sensible range (say 5% of the nominal value
for CPU core voltages, and 10% for other voltages), there is no
reason to worry.

<div class="node">
<p><hr>
<a name="Section-4.6"></a>
<a name="Section-4_002e6"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e7">Section 4.7</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e5">Section 4.5</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.6 Some measurements are way out of range. What happened?</h3>

<p>Each module tries to set limits to sensible values on initialization,
but a module does not know how a chip is actually connected. This is
described in the configuration file, which is not read by kernel modules. 
So limits can be strange, if the chip is connected in a non-standard way.

   <p>Readings can also be strange; there are several reasons for this. 
Temperature sensors, for example, can simply not be present, even though
the chip supports them. Also, it can be that the input is used in a
non-standard way. You can use the configuration file to describe how this
measurement should be interpreted; see the comments the example file for
more information.

   <p><a name="g_t_002d5V-and-_002d12V-readings-are-way-out-of-range_0021"></a>

<h4 class="subsection">4.6.1 -5V and -12V readings are way out of range!</h4>

<p>It's very frequent that negative voltage lines are not wired because
motherboard manufacturers don't think they're worth monitoring
(they are mostly unused these days). You can just add
<samp><span class="command">ignore inN</span></samp> lines to <samp><span class="file">/etc/sensors.conf</span></samp> to hide them.

   <p>Another possibility is that these lines are used to monitor different
voltages. Only the motherboard manufacturer can tell for sure. Taking
a look at what voltage values the BIOS displays may provide valuable
hints though.

<div class="node">
<p><hr>
<a name="Section-4.7"></a>
<a name="Section-4_002e7"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e8">Section 4.8</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e6">Section 4.6</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.7 What are VID lines? Why is the VID reading wrong?</h3>

<p>These describe the core voltage for your processor. They are
supported for most processors, however they are not always
correctly connected to the sensor chip, so the readings may be invalid. 
A reading of 0V, +3.5V or +2.05V is especially suspect. 
If this is the case, add a line <samp><span class="command">ignore vid</span></samp> to <samp><span class="file">/etc/sensors.conf</span></samp>,
and change the min and max settings for the Processor Core voltage
(often in0_min and in0_max) in that file so that they don't depend on vid.

   <p>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 <samp><span class="file">/etc/sensors.conf</span></samp>. 
See <samp><span class="file">doc/vid</span></samp> for more information.

<div class="node">
<p><hr>
<a name="Section-4.8"></a>
<a name="Section-4_002e8"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e9">Section 4.9</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e7">Section 4.7</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?</h3>

<p>If we would read the registers more often, it would not find the
time to update them. So we only update our readings once each 1.5 seconds
(the actual delay is chip-specific; for some chips, it may not be needed
at all).

<div class="node">
<p><hr>
<a name="Section-4.9"></a>
<a name="Section-4_002e9"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e10">Section 4.10</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e8">Section 4.8</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?</h3>

<p>ISA bus access is fast, but SMBus access is really slow. If you have
a lot of sensors, it just takes a lot of time to access them. Fortunately,
this has almost no impact on the system as a whole, as another job can run
while we are waiting for the transaction to finish.

<div class="node">
<p><hr>
<a name="Section-4.10"></a>
<a name="Section-4_002e10"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e11">Section 4.11</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e9">Section 4.9</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.10 Can I be alerted when an ALARM occurs?</h3>

<p>No, you can't; and it may well be never supported.

   <p>Almost no mainboard we have encountered have actually connected the
IRQ-out pin of sensor chips. That means that we could enable IRQ reporting, but
nothing would happen. Also, even if a motherboard has it connected, it is
unclear what interrupt number would be triggered. And IRQ lines are a scarce
facility, which means that almost nobody would be able to use it anyway.

   <p>The SMI interrupt is only available on a few types of chips. It is
really a very obscure way to handle interrupts, and supporting it under Linux
might be quite hard to do.

   <p>Your best bet would be to poll the alarm file with a user-land daemon
which alerts you if an alarm is raised. I am not aware of any program which
does the job, though you might want to examine one of the graphical monitor
programs under X, see <a href="http://www.lm-sensors.org/wiki/UsefulLinks">http://www.lm-sensors.org/wiki/UsefulLinks</a> for addresses.

<div class="node">
<p><hr>
<a name="Section-4.11"></a>
<a name="Section-4_002e11"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e12">Section 4.12</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e10">Section 4.10</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?</h3>

<p>Some chips which mainboard makers connect to the SMBus are not SMBus
devices.  An example is the 91xx clock generator chips.  When read, these
devices can lock up the SMBus until the next hard reboot.  This is because
they have a similar serial interface (like the I2C), but don't conform to
Intel's SMBus standard.

   <p>Why did they connect these devices to the SMBus if they aren't
compatible?  Good question! :')  Actually, these devices may support being
written to, but lock things up when they are read.

<div class="node">
<p><hr>
<a name="Section-4.12"></a>
<a name="Section-4_002e12"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e13">Section 4.13</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e11">Section 4.11</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.12 My BIOS reports a much higher CPU temperature than your modules!</h3>

<p>We display the actual temperature of the sensor. This may not be the
temperature you are interested in, though.  If a sensor should measure
the CPU temperature, it must be in thermal contact with it.  In practice,
it may be just somewhere nearby. Your BIOS may correct for this (by adding,
for example, thirty degrees to the measured temperature).  The correction
factor is regrettably different for each mainboard, so we can not do this
in the module itself. You can do it through the configuration file, though:

<pre class="example">     chip lm75-*-49                      # Or whatever chip this relates to
     label temp "Processor"
     compute temp @*1.2+13,(@-13)/1.2    # Or whatever formula
</pre>
   <p>However, the offset you are introducing might not be necessary. If you
tried to have Linux idle temperature and BIOS "idle" temperature match,
you may be misguided. 
We have a Supermicro (370DLE) motherboard and we know
that its BIOS has a closed, almost undelayed while(1) loop that
keeps the CPU busy all the time. Linux reads 26 degrees idle, BIOS reads
38 degrees. Linux at full load is in the 35-40 degrees range so this
makes sense.

<div class="node">
<p><hr>
<a name="Section-4.13"></a>
<a name="Section-4_002e13"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e14">Section 4.14</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e12">Section 4.12</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.13 I try to read the raw <samp><span class="file">/proc</span></samp> files, but the values are strange?!?</h3>

<p>Remember, these values do not take the configuration file
<samp><span class="file">compute</span></samp> lines in account. This is especially obvious for voltage readings
(usually called in? or vin?). Use a program linked to libsensors (like
the provided <samp><span class="command">sensors</span></samp> program) instead.

<div class="node">
<p><hr>
<a name="Section-4.14"></a>
<a name="Section-4_002e14"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e15">Section 4.15</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e13">Section 4.13</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.14 How do I set new limits?</h3>

<p>Change the limit values in <samp><span class="file">/etc/sensors.conf</span></samp> and then run
<samp><span class="command">sensors -s</span></samp>.

   <p><a name="I-set-new-limits-and-it-didnt-work"></a>

<h4 class="subsection">4.14.1 I set new limits and it didn't work?</h4>

<p>You forgot to run <samp><span class="command">sensors -s</span></samp>. Put it in a <samp><span class="file">/etc/rc.d/...</span></samp> file
after the modprobe lines to run at startup.

<div class="node">
<p><hr>
<a name="Section-4.15"></a>
<a name="Section-4_002e15"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e16">Section 4.16</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e14">Section 4.14</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.15 Some sensors are doubly detected?</h3>

<p>Yes, this is still a problem. It is partially solved by alias detection
and confidence values in sensors-detect, but it is really tough.

   <p>Double detections can be caused by two things:
sensors can be detected to both the ISA and the SMBus (and if you have
loaded the approprate adapter drivers, it will be detected on both), and
some chips simulate other chips (the Winbond W83781D simulates LM75 chips
on the SMBus, for example). Remove the offending adapter or chip driver, or
run sensors-detect and add the <samp><span class="command">ignore=</span></samp> modprobe parameters it suggests.

<div class="node">
<p><hr>
<a name="Section-4.16"></a>
<a name="Section-4_002e16"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e17">Section 4.17</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e15">Section 4.15</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.16 I ran sensors-detect, but now I get very strange readings?!?</h3>

<p>Your SMBus (PIIX4?) is probably crashed or hung. There are some mainboards
which connect a clock chip to the SMBus. Unfortunately, this clock chip
hangs the PIIX4 if it is read (it is an I2C device, but not SMBus compatible). 
We have found no way of solving this, except for rebooting your computer. 
Next time when you run sensors-detect, you may want to exclude addresses
0x69 and/or 0x6a, by entering <kbd>s</kbd> when you are asked whether you want to
scan the PIIX4.

<div class="node">
<p><hr>
<a name="Section-4.17"></a>
<a name="Section-4_002e17"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e18">Section 4.18</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e16">Section 4.16</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.17 Bad readings from particular chips</h3>

<p>See below for some particularly troublesome chips. 
Also be sure and check <samp><span class="file">doc/chips/xxxxx</span></samp> for the particular driver.

   <p><a name="Bad-readings-from-the-AS99127F"></a>

<h4 class="subsection">4.17.1 Bad readings from the AS99127F!</h4>

<p>The Asus AS99127F is a modified version of the Winbond W83781D. 
Asus will not release a datasheet. The driver was developed by tedious
experimentation. We've done the best we can. If you want to make adjustments
to the readings please edit <samp><span class="file">/etc/sensors.conf.</span></samp> Please don't ask us to
fix the driver. Ask Asus to release a datasheet.

   <p><a name="Bad-readings-from-the-VIA-686A"></a>

<h4 class="subsection">4.17.2 Bad readings from the VIA 686A!</h4>

<p>The Via 686A datasheet is incomplete. 
Via will not release details. The driver was developed by tedious
experimentation. We've done the best we can. If you want to make adjustments
to the readings please edit <samp><span class="file">/etc/sensors.conf.</span></samp> Please don't ask us to
fix the driver. Ask Via to release a better datasheet. 
Also, don't forget to <samp><span class="command">modprobe i2c-isa</span></samp>.

   <p><a name="Bad-readings-from-the-MTP008"></a>

<h4 class="subsection">4.17.3 Bad readings from the MTP008!</h4>

<p>The MTP008 has programmable temperature sensor types. 
If your sensor type does not match the default, you will have to change it. 
See <samp><span class="file">doc/chips/mtp008</span></samp> for details. 
Also, MTP008 chips seem to randomly refuse to respond, for
unknown reasons. You can see this as 'XX' entries in i2cdump.

   <p><a name="Bad-temperature-readings-from-the-SIS5595"></a>

<h4 class="subsection">4.17.4 Bad temperature readings from the SIS5595!</h4>

<p>This chip can use multiple thermistor types and there are also
two different versions of the chip. We are trying to get the driver
working better and develop formulas for different thermistors
but we aren't there yet. Sorry. 
Also, many times the chip isn't really a sis5595 but it was
misidentified. We are working on improving that too.

   <p><a name="Bad-readings-from-a-w8378_005b12_005dd"></a>

<h4 class="subsection">4.17.5 Bad readings from a w8378[12]d!</h4>

<p>Do you own an ASUS motherboard?  Perhaps your chip is being
misidentified.  Look on the motherboard (or at
<a href="http://mbm.livewiredev.com">http://mbm.livewiredev.com</a>) 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
<samp><span class="command">force_as99127f=BUS,0x2d</span></samp> where <code>BUS</code> is your i2c bus number. 
Cat /proc/bus/i2c to see a list of bus numbers. 
Read the w83781d module documentation (<samp><span class="file">doc/chips/w83781d</span></samp>)
for more details.

   <p><a name="Bus-hangs-on-Ali-1543-on-Asus-P5A-boards"></a>

<h4 class="subsection">4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!</h4>

<p>The SMBus tends to hang on this board and it seems to get worse
at higher temperatures. Use ISA accesses to reliably use the w83781d
monitor chip on this board and use the <samp><span class="command">ignore=1,0x2d</span></samp> or similar option
to the w83781d module to prevent i2c accesses.

   <p><a name="Bad-readings-from-LM75"></a>

<h4 class="subsection">4.17.7 Bad readings from LM75!</h4>

<p>The LM75 detection is poor and other hardware is often misdetected
as an LM75. Figure out what you really have See <a href="#Section-3_002e2_002e1">What chips are on motherboard XYZ</a>.

   <p><a name="Bad-readings-from-LM78"></a>

<h4 class="subsection">4.17.8 Bad readings from LM78!</h4>

<p>The LM78 is no longer manufactured by National Semiconductor. 
You probably don't have a real LM78 but something similar that we
do not recogize or support. Figure out what you really have See <a href="#Section-3_002e2_002e1">What chips are on motherboard XYZ</a>.

   <p><a name="Bad-readings-from-LM80"></a>

<h4 class="subsection">4.17.9 Bad readings from LM80!</h4>

<p>The LM80 detection is poor and other hardware is often misdetected
as an LM80. Figure out what you really have See <a href="#Section-3_002e2_002e1">What chips are on motherboard XYZ</a>.

<div class="node">
<p><hr>
<a name="Section-4.18"></a>
<a name="Section-4_002e18"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e19">Section 4.19</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e17">Section 4.17</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.18 How do I configure two chips (LM87) differently?</h3>

<p>There is a SuperMicro board with two LM87's on it that are
not hooked up in the same way, so they need different defaults. 
For example, both CPU temperatures go to one LM87.

   <p>Make two different sections in <samp><span class="file">/etc/sensors.conf</span></samp> as follows:
<pre class="example">     chip "lm87-i2c-*-2c"
         put configuration for the chip at 0x2c here
     chip "lm87-i2c-*-2d"
         put configuration for the chip at 0x2d here
</pre>
   <p>There is a commented example in <samp><span class="file">sensors.conf.eg</span></samp> which should
be helpful.

<div class="node">
<p><hr>
<a name="Section-4.19"></a>
<a name="Section-4_002e19"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e20">Section 4.20</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e18">Section 4.18</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.19 Dmesg says `<samp><span class="samp">Upgrade BIOS</span></samp>'! I don't want to!</h3>

<p>If the problem is a PCI device is not present in <samp><span class="command">lspci</span></samp>, the solution
is complex. For the ALI M7101 device, there is a solution which uses the
2.4 kernel's <samp><span class="command">hotplug</span></samp> facility. See <samp><span class="file">prog/hotplug</span></samp> in our package. 
For other PCI devices, you can try to modify
the m7101 solution in <samp><span class="file">prog/hotplug</span></samp>.

   <p>If dmesg says `<samp><span class="samp">try force_addr</span></samp>', see below. Other drivers generally do not
support the force_addr parameter. Sorry. Check the documentation
for your driver in <samp><span class="file">doc/[chips,busses]</span></samp> and if we don't support it
you can send us your request.

   <p><a name="Dmesg-says-use-force_005faddr_003d0xaddr_0021-What-address-do-I-use"></a>

<h4 class="subsection">4.19.1 Dmesg says `<samp><span class="samp">use force_addr=0xaddr</span></samp>'! What address do I use?</h4>

<p>If the problem is a PCI device whose base address is not set,
you may be able to set the address with a force parameter. The via686a
and sis5595 chip drivers, and some bus drivers, support the command line
<samp><span class="command">modprobe via686a force_addr=0xADDRESS</span></samp> where ADDRESS
is the I/O address. You must select an address that is not in use. 
<samp><span class="command">cat <samp>/proc/ioports</samp></span></samp> to check (carefully) for conflicts. A high number like
0xf000 is generally safe.

<div class="node">
<p><hr>
<a name="Section-4.20"></a>
<a name="Section-4_002e20"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e21">Section 4.21</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e19">Section 4.19</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.20 Sensors says `<samp><span class="samp">Can't access procfs/sysfs file</span></samp>'</h3>

     <ul>
<li>Linux 2.6
          <ul>
<li>Did you <samp><span class="command">modprobe i2c_sensor</span></samp>? Check <samp><span class="command">lsmod</span></samp>. 
<li>Do you have sysfs support in your kernel and <samp><span class="file">/sys</span></samp> mounted (is <samp><span class="file">/sys</span></samp> there and populated)? 
Create /sys with <samp><span class="command">mkdir /sys</span></samp> if needed. Then add the following line to <samp><span class="file">/etc/fstab</span></samp>:
          <pre class="example">               sys              /sys             sysfs       default          0   0</pre>
          <p>and <samp><span class="command">mount /sys</span></samp>. 
</ul>
     <li>Linux 2.4
          <ul>
<li>Did you <samp><span class="command">modprobe i2c-proc</span></samp>? Check <samp><span class="command">lsmod</span></samp>. 
<li>Do you have procfs support in your kernel and <samp><span class="file">/proc</span></samp> mounted (is <samp><span class="file">/proc</span></samp> there and populated)? 
Create /proc with <samp><span class="command">mkdir /proc</span></samp> if needed. Then add the following line to <samp><span class="file">/etc/fstab</span></samp>:
          <pre class="example">               proc             /proc            proc        defaults         0   0</pre>
          <p>and <samp><span class="command">mount /proc</span></samp>. 
</ul>
     <li>If you did <samp><span class="command">sensors -s</span></samp>, did you run it as root? 
</ul>

<div class="node">
<p><hr>
<a name="Section-4.21"></a>
<a name="Section-4_002e21"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e22">Section 4.22</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e20">Section 4.20</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.21 Sensors says `<samp><span class="samp">No sensors found!</span></samp>'</h3>

     <ul>
<li>Did <samp><span class="command">sensors-detect</span></samp> find sensors? (If not see <a href="#Sensors_002ddetect-doesnt-find-any-sensors">Sensors-detect doesnt find any sensors</a>)
<li>Did you do what <samp><span class="command">sensors-detect</span></samp> said? 
<li>Did you <samp><span class="command">modprobe</span></samp> your sensor modules? 
<li>Did you <samp><span class="command">modprobe</span></samp> your I2C adapter modules? 
<li>Did you <samp><span class="command">modprobe i2c-isa</span></samp> if you have ISA sensor chips? 
<li>Check <samp><span class="command">lsmod</span></samp>. 
</ul>

<div class="node">
<p><hr>
<a name="Section-4.22"></a>
<a name="Section-4_002e22"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e23">Section 4.23</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e21">Section 4.21</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.22 Sensors output is not correct!</h3>

<p>What specifically is the trouble?
     <ul>
<li>Labels: See <a href="#Section-3_002e4_002e1">The labels for the voltage and temperature readings in sensors are incorrect</a>. 
<li>Min/max readings: See <a href="#Section-3_002e4_002e2">The min and max for the readings in sensors are incorrect</a>, and See <a href="#Section-3_002e4_002e3">The min and max settings didnt take effect</a>. 
<li>AS99127F: See <a href="#Section-4_002e16">I ran sensors-detect but now I get very strange readings?</a>. 
<li>Via 686A: See <a href="#Section-4_002e16">I ran sensors-detect but now I get very strange readings?</a>. 
<li>Other specific chips: See <a href="#Section-4_002e16">I ran sensors-detect but now I get very strange readings?</a>. 
<li>No output for a particular sensors chip: See <a href="#Section-5_002e3">What to do if it inserts but nothing happens</a>. 
<li>No output at all: See <a href="#Section-4_002e21">Sensors says No sensors found</a>, See <a href="#Section-5_002e3">What to do if it inserts but nothing happens</a>. 
<li>Completely bad output for a particular sensor chip: See <a href="#Section-5_002e4">What to do if I read only bogus information</a>. 
<li>One particular sensor readings:
          <ul>
<li>Maybe it isn't hooked up? - tell 'sensors' to ignore it. See <a href="#Section-3_002e4_002e4">One sensor isnt hooked up on my board</a>. 
<li>Maybe it is hooked up differently on your motherboard? - adjust <samp><span class="file">sensors.conf</span></samp> calculation. 
</ul>
     </ul>

<div class="node">
<p><hr>
<a name="Section-4.23"></a>
<a name="Section-4_002e23"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e24">Section 4.24</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e22">Section 4.22</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.23 What is at I2C address XXX?</h3>

<p>In general, we don't know. Start by running <samp><span class="command">sensors-detect</span></samp>. 
If it doesn't recognize it, try running <samp><span class="command">i2cdump</span></samp>. A partial list
of manufacturers' IDs are at the bottom of <samp><span class="file">doc/chips/SUMMARY</span></samp>.

   <p><a name="What-is-at-I2C-address-0x69"></a>

<h4 class="subsection">4.23.1 What is at I2C address 0x69?</h4>

<p>A clock chip. Often, accessing these clock chips in the wrong
way will instantly crash your computer. Sensors-detect carefully
avoids these chips, and you should do too.  You have been warned.

   <p><a name="What-is-at-I2C-addresses-0x50-_002d-0x57"></a>

<h4 class="subsection">4.23.2 What is at I2C addresses 0x50 - 0x57?</h4>

<p>EEPROMs on your SDRAM DIMMs. Load the eeprom module to
look at some basic data in <samp><span class="command">sensors</span></samp> or use the program
<samp><span class="command">prog/eeprom/decode-dimms.pl</span></samp> to get more information than you ever wanted.

   <p><a name="What-is-at-I2C-addresses-0x30-_002d-0x37"></a>

<h4 class="subsection">4.23.3 What is at I2C addresses 0x30 - 0x37?</h4>

<p>These are often 'shadows' of your EEPROMs on your SDRAM DIMMs
at addresses 0x50 - 0x57. They are the 'software write-protect'
registers of the SDRAM Serial Presence Detect EEPROMs. 
If you try and
do a <samp><span class="command">i2cdump</span></samp> on them to read the location, you won't get anything,
because they contain a single write-only register. 
This register can be used to permanently
write-protect the contents of the eeprom.

<div class="node">
<p><hr>
<a name="Section-4.24"></a>
<a name="Section-4_002e24"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e25">Section 4.25</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e23">Section 4.23</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.24 Sensors-detect doesn't work at all</h3>

<p>It could be many things. What was the problem? See <a href="#Section-4_002e31">Problems on particular motherboards</a>.

   <p><a name="Sensors_002ddetect-says-_0022Couldnt-open-_002fproc_002fbus_002fi2c_003f_0021_003f_0022"></a>

<h4 class="subsection">4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"</h4>

<p>You don't have i2c support in your kernel, or the i2c-core module
was not loaded and you did not run sensors-detect as root.

   <p><a name="Sensors_002ddetect-says-_0022Cant-open-_002fdev_002fi2c_005b_002d_002f_005d0_0022"></a>

<h4 class="subsection">4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"</h4>

<p>Your <samp><span class="file">/dev/i2c-0,</span></samp> <samp><span class="file">/dev/i2c0</span></samp>, or <samp><span class="file">/dev/i2c/0</span></samp> files do not exist
or you did not run <samp><span class="command">sensors-detect</span></samp> as root. 
Run the script <samp><span class="command">prog/mkdev/mkdev.sh</span></samp> to create the <samp><span class="file">/dev/i2c-x</span></samp> files. 
Run <samp><span class="command">devfs</span></samp> in the kernel to get the <samp><span class="file">/dev/i2c/x</span></samp> files.

   <p><a name="Sensors_002ddetect-doesnt-find-any-sensors"></a>

<h4 class="subsection">4.24.3 Sensors-detect doesn't find any sensors!</h4>

<p>Either
     <ol type=1 start=1>
<li>The board doesn't have any sensors. 
<li>We don't support the sensors on the board. 
<li>The sensors it has are on an I2C bus connected to an I2C bus adapter that we don't support. 
<li>You don't have the latest version of lm_sensors.
        </ol>

   <p>But in any case you should figure out what is on the board:
     <ol type=1 start=1>
<li>Look at your motherboard. 
<li>Check the manufacturer's website. 
<li>Check the <a href="http://mbm.livewiredev.com/">Motherboard Monitor</a> website.
        </ol>

   <p>When you know what chips you have, check the
<a href="http://www.lm-sensors.org/wiki/Devices">Driver Status</a> web page to
see if support has been added for your chip in a later release or in SVN.

<div class="node">
<p><hr>
<a name="Section-4.25"></a>
<a name="Section-4_002e25"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e26">Section 4.26</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e24">Section 4.24</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.25 Sensors says `<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>'</h3>

<p>These are errors from the libsensors library in
reading the <samp><span class="file">/etc/sensors.conf</span></samp> configuration file. Go to that line
number and fix it. If you have a parse error, perhaps you have
to put the feature name in double quotes.

<div class="node">
<p><hr>
<a name="Section-4.26"></a>
<a name="Section-4_002e26"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e27">Section 4.27</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e25">Section 4.25</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.26 Sensors only gives the name, adapter, and algorithm for my chip</h3>

<p>If <samp><span class="command">sensors</span></samp> only says this, for example, and doesn't
provide any actual data at all:

<pre class="example">     it87-isa-0290
     Adapter: ISA adapter
     Algorithm: ISA algorithm
</pre>
   <p>Your chip is not currently supported by <samp><span class="command">sensors</span></samp> and so all it
does is print out that information. Get the latest release
and be sure you are running the <samp><span class="command">sensors</span></samp> program it installed
and not some older <samp><span class="command">sensors</span></samp>.

<div class="node">
<p><hr>
<a name="Section-4.27"></a>
<a name="Section-4_002e27"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e28">Section 4.28</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e26">Section 4.26</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.27 Sensors says `<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>'</h3>

     <ul>
<li>(Linux 2.6) Make sure you are using one of the
<a href="http://www.lm-sensors.org/wiki/Kernel2.6">recommended kernel/lm_sensors combination</a>. 
<li>You have a <samp><span class="file">libsensors</span></samp>/<samp><span class="command">sensors</span></samp> mismatch. 
<samp><span class="command">sensors</span></samp> is unable to
get a data entry from <samp><span class="file">libsensors</span></samp>. You probably have an
old <samp><span class="file">libsensors</span></samp> in your <samp><span class="file">/etc/ld.so.conf</span></samp> path. 
Make sure you did (as root) a <samp><span class="command">make install</span></samp> (Linux 2.4) or
<samp><span class="command">make user_install</span></samp> (Linux 2.6) followed by a <samp><span class="command">ldconfig</span></samp>. 
Then check the output of <samp><span class="command">ldconfig -v | grep libsensors</span></samp> to
verify that there is only ONE <samp><span class="file">libsensors</span></samp> entry and that it matches
the <samp><span class="file">libsensors</span></samp> that was built in the <samp><span class="file">lib/</span></samp> directory in <samp><span class="file">lm_sensors2</span></samp>. 
</ul>

<div class="node">
<p><hr>
<a name="Section-4.28"></a>
<a name="Section-4_002e28"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e29">Section 4.29</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e27">Section 4.27</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.28 Sensors doesn't find any sensors, just eeproms.</h3>

<p>See <a href="#Section-4_002e24">Sensors-detect doesnt work at all</a>, if <samp><span class="command">sensors-detect</span></samp> failed to find any sensors.

   <p>If <samp><span class="command">sensors-detect</span></samp> did find sensors, did you insert your modules? For chips on the ISA
bus, did you insert i2c-isa?

   <p>See <a href="#Section-5_002e2">What to do if a module wont insert</a>, if the modules didn't insert,
also <a href="#Section-4_002e21">Sensors says No sensors found</a>.

<div class="node">
<p><hr>
<a name="Section-4.29"></a>
<a name="Section-4_002e29"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e30">Section 4.30</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e28">Section 4.28</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.29 Inserting modules hangs my board</h3>

<p>There are several possible causes:
     <ol type=1 start=1>
<li>Bus driver problems. Insert the bus driver first, before you have inserted any chip drivers, to verify. 
<li>Wrong chip driver. Verify that you have a chip supported by the chip driver, see <a href="#Section-3_002e2_002e1">What chips are on motherboard XYZ</a>. 
<li>The chip driver is reinitializing the chip, which undoes critical initialization done by the BIOS.  Try the parameter <samp><span class="command">init=0</span></samp> for the w83781d driver; this is the only driver supporting this parameter. 
<li>Some chips on the bus don't like to be probed at all.  After inserting the bus driver (but not the chip drivers), run <samp><span class="command">i2cdetect</span></samp> on the bus, then <samp><span class="command">i2cdump</span></samp> on each address responding to <samp><span class="command">i2cdetect</span></samp>. This may find the culprit.  Do not <samp><span class="command">i2cdump address 0x69</span></samp>, the clock chip. 
<li>The chip driver is incorrectly finding a second chip on the bus and is accessing it. For example, with the Tyan 2688 with a w83781d at 0x29, use <samp><span class="command">modprobe ignore_range=0,0x00,0x28,0,0x2a,0x7f</span></samp> to prevent access to other addresses. (<samp><span class="command">init=0</span></samp> also req'd for the Tyan 2688).
        </ol>

<div class="node">
<p><hr>
<a name="Section-4.30"></a>
<a name="Section-4_002e30"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e31">Section 4.31</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e29">Section 4.29</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.30 Inserting modules slows down my board</h3>

<p>Generally this is caused by an overtemperature alarm output from
the sensor chip. This triggers hardware on the board which
automatically slows down the CPU clock. Be sure that your
temperature limits are above the temperature reading. Put
the new limits in <samp><span class="file">/etc/sensors.conf</span></samp> and run <samp><span class="command">sensors -s</span></samp>.

<div class="node">
<p><hr>
<a name="Section-4.31"></a>
<a name="Section-4_002e31"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e32">Section 4.32</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e30">Section 4.30</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.31 Problems on particular motherboards</h3>

<p>The following boards have unique problems and solutions.

   <p><a name="Asus-P4B"></a>

<h4 class="subsection">4.31.1 Asus P4B</h4>

<p>See <samp><span class="file">prog/hotplug/README.p4b</span></samp> if your SMBus master is not found.

   <p><a name="Tyan-2460-2462"></a>

<h4 class="subsection">4.31.2 Tyan 2460, 2462</h4>

<p>See support tickets 805, 765, 781, 812, 813, and 867 for information.

   <p><a name="Tyan-2466"></a>

<h4 class="subsection">4.31.3 Tyan 2466</h4>

<p>See support tickets 941, 840, and 841 for information.

   <p><a name="Tyan-2688"></a>

<h4 class="subsection">4.31.4 Tyan 2688</h4>

<p>For board hangs, see support ticket 721 for information. 
Also <a href="#Section-4_002e29">Inserting modules hangs my board</a>.

<div class="node">
<p><hr>
<a name="Section-4.32"></a>
<a name="Section-4_002e32"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e33">Section 4.33</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e31">Section 4.31</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.32 Problems on particular systems</h3>

<p>For IBM systems, see <samp><span class="file">README.thinkpad</span></samp>.

<div class="node">
<p><hr>
<a name="Section-4.33"></a>
<a name="Section-4_002e33"></a>
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e32">Section 4.32</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>

</div>

<h3 class="section">4.33 Problems on 2.6 kernels</h3>

<p>Not all drivers have been ported to 2.6. If your favorite driver is not
in 2.6, the reason is that nobody has ported it, or the ported code did
not get a proper review yet. 
If you would like to port the driver, see the file
Documentation/i2c/porting-clients in the 2.6 kernel tree for help,
then send us the ported driver when you are done.

<h4 class="subsection">4.33.1 i2c-viapro and via686a</h4>

<p>Until kernel 2.6.11, there was a PCI resource conflict between
i2c-viapro (the SMBus driver for VIA bridges) and via686a (the integrated
sensors driver for VIA bridges). This caused the second loaded driver to
silently fail working. So do not load both i2c-viapro and via686a together
unless you have a recent kernel.

<h4 class="subsection">4.33.2 Where are my EEPROMs?</h4>

<p>The 2.6.14-rc1 kernel introduced the hwmon class, which groups all
hardware monitoring drivers in a logical way. The goal was to help
libsensors grab the relevant sensors information in /sys. In particular:
     <ul>
<li>libsensors will no more need to know about the underlying bus types
(I2C/SMBus, ISA or other);
<li>libsensors will no more list non-hardware monitoring chips. 
</ul>
   This explains why EEPROMs are no more displayed by <samp><span class="command">sensors</span></samp>:
they are no hardware monitoring chips. The medium term plan is to drop
eeprom support for all Linux 2.6 kernels, as it didn't fit well in
the library code in the first place.

   <p>Note that you can still obtain information about your EEPROMs by using
the dedicated perl scripts in <samp><span class="file">prog/eeprom</span></samp>: <samp><span class="command">ddcmon</span></samp>,
<samp><span class="command">decode-dimms.pl</span></samp>, <samp><span class="command">decode-edid.pl</span></samp> and
<samp><span class="command">decode-vaio.pl</span></samp>.

<div class="node">
<p><hr>
<a name="Help"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Contribute">Contribute</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Problems">Problems</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>

</div>

<h2 class="chapter">5 How to Ask for Help</h2>

<ul class="menu">
<li><a accesskey="1" href="#Section-5_002e1">Section 5.1</a>:   What to send us when asking for help
<li><a accesskey="2" href="#Section-5_002e2">Section 5.2</a>:   What to do if a module won't insert? 
<li><a accesskey="3" href="#Section-5_002e3">Section 5.3</a>:   What to do if it inserts, but nothing happens? 
<li><a accesskey="4" href="#Section-5_002e4">Section 5.4</a>:   What to do if I read only bogus information? 
<li><a accesskey="5" href="#Section-5_002e5">Section 5.5</a>:   What to do if you have other problems? 
<li><a accesskey="6" href="#Section-5_002e6">Section 5.6</a>:   What if it just works like a charm? 
<li><a accesskey="7" href="#Section-5_002e7">Section 5.7</a>:   How do I update a ticket? 
<li><a accesskey="8" href="#Section-5_002e8">Section 5.8</a>:   How do I follow up on a ticket? 
<li><a accesskey="9" href="#Section-5_002e9">Section 5.9</a>:   Why did you decide not to support undocumented chips? 
</ul>

<div class="node">
<p><hr>
<a name="Section-5.1"></a>
<a name="Section-5_002e1"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e2">Section 5.2</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>

</div>

<h3 class="section">5.1 What to send us when asking for help</h3>

<p>We are always willing to answer questions if things don't work out. 
Post your question to our <a href="http://lists.lm-sensors.org/mailman/listinfo/lm-sensors">discussion list</a>,
and not the individual authors,
unless you have something private to say.

   <p>Instead of using email, you can also use the web-based support
area, at <a href="http://www.lm-sensors.org/wiki/FeedbackAndSupport">http://www.lm-sensors.org/wiki/FeedbackAndSupport</a>. You will be helped
just as fast, and others may profit from the answer too. You will be
emailed automatically when your question has been answered.

   <p>Here's what you should send us:

     <ul>
<li>The dmesg or syslog output if applicable
<li>The output of (as root) <samp><span class="command">prog/detect/sensors-detect</span></samp>
<li>The output of <samp><span class="command">lsmod</span></samp>
<li>If a PCI chip problem:
          <ul>
<li>The output of <samp><span class="command">lspci -n</span></samp>
</ul>
     <li>If an I2C sensor chip problem:
          <ul>
<li>The output of (as root) <samp><span class="command">prog/detect/i2cdetect X</span></samp>
where X = the bus number (run <samp><span class="command">i2cdetect</span></samp> with no arguments to list the busses)
(please send this only if it's not all `<samp><span class="samp">XX</span></samp>')
<li>The output of (as root) <samp><span class="command">prog/dump/i2cdump X 0xXX</span></samp>
where XX = the address of each chip you see in the output of <samp><span class="command">i2cdetect</span></samp>. (run once for each chip)
(please send this only if it's not all `<samp><span class="samp">ff</span></samp>')
</ul>
     <li>If an ISA sensor chip problem:
          <ul>
<li>The output of (as root) <samp><span class="command">prog/dump/isadump 0x295 0x296</span></samp> (only if it's not all `<samp><span class="samp">XX</span></samp>')
</ul>
     <li>Part numbers of chips on your motherboard you think are the sensor chips (look at your motherboard)
<li>Motherboard type
<li>Sensors version
<li>Kernel version
</ul>

<div class="node">
<p><hr>
<a name="Section-5.2"></a>
<a name="Section-5_002e2"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e3">Section 5.3</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e1">Section 5.1</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>

</div>

<h3 class="section">5.2 What to do if a module won't insert?</h3>

<p>Did you use <samp><span class="command">modprobe</span></samp> instead of <samp><span class="command">insmod</span></samp>??? Don't use insmod.

   <p>Were there unresolved symbols? Did you run <samp><span class="command">depmod -a</span></samp>? Run
<samp><span class="command">depmod -a -e</span></samp> to see where the symbol problem is.

   <p>ALWAYS inspect the output of <samp><span class="command">dmesg</span></samp>. That's where the error
messages come out!!! Don't rely on the generic message from <samp><span class="command">modprobe</span></samp>. 
If you still can't figure it out, send us the information
listed above.

<div class="node">
<p><hr>
<a name="Section-5.3"></a>
<a name="Section-5_002e3"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e4">Section 5.4</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e2">Section 5.2</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>

</div>

<h3 class="section">5.3 What to do if it inserts, but nothing happens?</h3>

<p>For an ISA sensor chip, did you also <samp><span class="command">modprobe i2c-isa</span></samp>? It must be inserted.

   <p>For an I2C sensor chip, did you also <samp><span class="command">modprobe i2c-xxx</span></samp> where xxx is your
I2C bus adapter? It must be inserted.

   <p>Always inspect the output of <samp><span class="command">dmesg</span></samp>. That's where the error
messages come out. If you still can't figure it out, send us the information
listed above.

<div class="node">
<p><hr>
<a name="Section-5.4"></a>
<a name="Section-5_002e4"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e5">Section 5.5</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e3">Section 5.3</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>

</div>

<h3 class="section">5.4 What to do if I read only bogus information?</h3>

<p>It may be that this was a mis-detection: the chip may not be
present. If you are convinced there is something wrong, verify that you
indeed have the devices on your motherboard that you think you do. 
Look at the motherboard and make sure. If you are still stuck,
please send us the usual information (see <a href="#Help">Help</a>)

<div class="node">
<p><hr>
<a name="Section-5.5"></a>
<a name="Section-5_002e5"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e6">Section 5.6</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e4">Section 5.4</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>

</div>

<h3 class="section">5.5 What to do if you have other problems?</h3>

<p>Again, send the output listed above.

<div class="node">
<p><hr>
<a name="Section-5.6"></a>
<a name="Section-5_002e6"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e7">Section 5.7</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e5">Section 5.5</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>

</div>

<h3 class="section">5.6 What if it just works like a charm?</h3>

<p>Drop us a mail if you feel like it, mentioning the mainboard and
detected chip type. That way, we have some positive feedback, too!

<div class="node">
<p><hr>
<a name="Section-5.7"></a>
<a name="Section-5_002e7"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e8">Section 5.8</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e6">Section 5.6</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>

</div>

<h3 class="section">5.7 How do I update a ticket?</h3>

<p>You can't. Only developers can. Follow up by emailing us
and reference your ticket number
in the subject. Please don't enter a new ticket with
follow-up information, email us instead. Thanks.

<div class="node">
<p><hr>
<a name="Section-5.8"></a>
<a name="Section-5_002e8"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e9">Section 5.9</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e7">Section 5.7</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>

</div>

<h3 class="section">5.8 How do I follow up on a ticket?</h3>

<p>Follow up by emailing us
and reference your ticket number in the subject.

<div class="node">
<p><hr>
<a name="Section-5.9"></a>
<a name="Section-5_002e9"></a>
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e8">Section 5.8</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>

</div>

<h3 class="section">5.9 Why did you decide not to support undocumented chips?</h3>

<p>There are several reasons why we are generally not interested in writing
drivers for undocumented chips:

     <ul>
<li>Writing a driver without a datasheet is much harder, as you have to
guess most things. Remember that, most of the time, we write drivers for fun
and for free, so there is no reason we would write a driver in conditions
that promise more pain than fun. 
<li>If we hit a problem, we are certain never to get any support from the
chip manufacturer. This means that we may spend days on code which will
finally never work. 
<li>There are several chips out there which are fully documented and lack
a driver. This is natural for us to give these the priority when we
finally have some spare time to spend on driver coding. 
<li>Hardware monitoring chips are not toys. Misprogramming them can
result in data loss or hardware breakage. This is obviously more likely
to happen with undocumented chips. This is a responsability we do not
want to endorse (the GPL is pretty clear than we are not legally
liable, but still). 
</ul>

   <p>There are also several reasons why we do not want to support such drivers,
even if they were written by other people:

     <ul>
<li>Problems are much more likely to happen with such drivers. 
This means increased needs of support. User support if very
time-consuming and we are usually short of time. 
<li>Support should be done by the driver author (as only him/her knows
the driver and chip) but in the reality of facts, people will always ask
us for help if the driver is part of our package. Redirecting all user
requests to the driver's author manually is boring. 
<li>The lack of datasheet usually results in an original driver which
works relatively fine for its author, but will happen not to work
completely for other users. This means that the driver will need many
more additions and fixes than other drivers do, resulting in an increased
maitainance workload, which we can hardly afford. Of course this too should
be handled by the original driver author, but we never know whether he/she
will actually do the work. 
</ul>

   <p>Lastly, there are other considerations, some of which are deliberately
political:

     <ul>
<li>We do not want to trick hardware buyers into thinking that a chip is
fully supported under Linux when in fact it is only partly supported by a
driver which was written without a datasheet. Clearly stating that such
chips are not supported makes it much easier for anyone who really needs
fully working hardware monitoring under Linux to avoid motherboards with
these partly supported chips. 
<li>Drivers written without a datasheet are a pain for developers and
users, but are a complete win for the manufacturers of these chips:
they don't have to write the driver, they don't have to help us,
they don't have to support the users, and they still sell their
hardware. We do not want to encourage such a selfish behavior. 
</ul>

   <p>That being said, authors of such drivers can still submit their code to
the Linux kernel folks for inclusion into Linux 2.6. Their driver may be
accepted there, under conditions.

   <p>If such a driver is ever accepted into the Linux 2.6 tree, and someone
provides a patch to libsensors and/or sensors to add support for this
driver, we will apply it. This generic code is unlikely to cause trouble.

<div class="node">
<p><hr>
<a name="Contribute"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Document-Revisions">Document Revisions</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Help">Help</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>

</div>

<h2 class="chapter">6 How to Contribute</h2>

<ul class="menu">
<li><a accesskey="1" href="#Section-6_002e1">Section 6.1</a>:   How to write a driver
<li><a accesskey="2" href="#Section-6_002e2">Section 6.2</a>:   How to get SVN access
<li><a accesskey="3" href="#Section-6_002e3">Section 6.3</a>:   How to donate hardware to the project
<li><a accesskey="4" href="#Section-6_002e4">Section 6.4</a>:   How to join the project mailing list
<li><a accesskey="5" href="#Section-6_002e5">Section 6.5</a>:   How to access mailing list archives
<li><a accesskey="6" href="#Section-6_002e6">Section 6.6</a>:   How to submit a patch
<li><a accesskey="7" href="#Section-6_002e7">Section 6.7</a>:   How to REALLY help
<li><a accesskey="8" href="#Section-6_002e8">Section 6.8</a>:   How to get release announcements
</ul>

<div class="node">
<p><hr>
<a name="Section-6.1"></a>
<a name="Section-6_002e1"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e2">Section 6.2</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>

</div>

<h3 class="section">6.1 How to write a driver</h3>

<p>See <samp><span class="file">doc/developers/new_drivers</span></samp> in our package for instructions.

<div class="node">
<p><hr>
<a name="Section-6.2"></a>
<a name="Section-6_002e2"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e3">Section 6.3</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e1">Section 6.1</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>

</div>

<h3 class="section">6.2 How to get SVN access</h3>

<p>For anonymous SVN read access, see the instructions on our
<a href="http://www.lm-sensors.org/wiki/Download">download page</a>.

   <p>For write access, please contact us.

<div class="node">
<p><hr>
<a name="Section-6.3"></a>
<a name="Section-6_002e3"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e4">Section 6.4</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e2">Section 6.2</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>

</div>

<h3 class="section">6.3 How to donate hardware to the project</h3>

<p><a href="http://www.lm-sensors.org/wiki/FeedbackAndSupport">Contact us</a>.

<div class="node">
<p><hr>
<a name="Section-6.4"></a>
<a name="Section-6_002e4"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e5">Section 6.5</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e3">Section 6.3</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>

</div>

<h3 class="section">6.4 How to join the project mailing lists</h3>

<p>There are two lists you can subscribe to:

     <ul>
<li>A <a href="http://lists.lm-sensors.org/mailman/listinfo/lm-sensors">general discussion list</a>,
meant for both development and user support. You do not need to be subscribed to post. 
<li>A <a href="http://lists.lm-sensors.org/mailman/listinfo/lm-sensors-commit">CVS commits list</a>,
for watching the changes made to the CVS repositories. This list is read-only. 
</ul>

<div class="node">
<p><hr>
<a name="Section-6.5"></a>
<a name="Section-6_002e5"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e6">Section 6.6</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e4">Section 6.4</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>

</div>

<h3 class="section">6.5 How to access mailing list archives</h3>

<p>The primary mailing list archive is at:
<a href="http://lists.lm-sensors.org/pipermail/lm-sensors/">http://lists.lm-sensors.org/pipermail/lm-sensors/</a>. 
It contains messages since October 28, 2001.

   <p>There is another mailing list archive at:
<a href="http://news.gmane.org/gmane.linux.drivers.sensors">http://news.gmane.org/gmane.linux.drivers.sensors</a>. 
It contains messages since December 31, 2004. 
This archive may also be accessed via a news reader:
<a href="nntp://news.gmane.org/gmane.linux.drivers.sensors">nntp://news.gmane.org/gmane.linux.drivers.sensors</a>
and RSS:
<a href="http://rss.gmane.org/gmane.linux.drivers.sensors">http://rss.gmane.org/gmane.linux.drivers.sensors</a>.

   <p>And last there is a legacy archive at:
<a href="http://archives.andrew.net.au/lm-sensors">http://archives.andrew.net.au/lm-sensors</a>. 
It contains messages from October 28, 2001 through May 16, 2005.

<div class="node">
<p><hr>
<a name="Section-6.6"></a>
<a name="Section-6_002e6"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e7">Section 6.7</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e5">Section 6.5</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>

</div>

<h3 class="section">6.6 How to submit a patch</h3>

<p>Check out the latest from CVS, then copy the directory to another
directory, and make your changes. Generate the diff with
<samp><span class="command">diff -u2 -r DIR1 DIR2</span></samp>. Or you can generate the diff in CVS with
<samp><span class="command">cvs diff -u2</span></samp>. Send us the patch in an email and tell us what it does.

<div class="node">
<p><hr>
<a name="Section-6.7"></a>
<a name="Section-6_002e7"></a>
Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e8">Section 6.8</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e6">Section 6.6</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>

</div>

<h3 class="section">6.7 How to REALLY help</h3>

<p>Believe it or not, what we really need help with are:
     <ul>
<li>Answering email
<li>Answering support tickets
<li>Porting drivers to Linux 2.6
<li>Creating a sensors.conf database
<li>Reviewing patches
</ul>

   <p>If you are willing to help, simply join our
<a href="http://lists.lm-sensors.org/mailman/listinfo/lm-sensors">discussion list</a>,
and we'll help you help us.

<div class="node">
<p><hr>
<a name="Section-6.8"></a>
<a name="Section-6_002e8"></a>
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e7">Section 6.7</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>

</div>

<h3 class="section">6.8 How to get release announcements</h3>

<p>We don't have a separate release announcement mailing list;
however, we put all our releases on freshmeat: <a href="http://freshmeat.net">http://freshmeat.net</a>
and you can register on our freshmeat project page  <a href="http://freshmeat.net/projects/lm_sensors">http://freshmeat.net/projects/lm_sensors</a>
to 'subscribe to new releases' and then freshmeat
will email you announcement.

<div class="node">
<p><hr>
<a name="Document-Revisions"></a>
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Contribute">Contribute</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>

</div>

<h2 class="appendix">Appendix A Revision History of This Document</h2>

     <ul>
<li>Rev 2.18 (JD) Removed version 1 specifics part, 2005-12-17
<li>Rev 2.17 (JD) Added 5.9 (why we don't support undocumented chips),
	removed 6.9 (doesn't apply to the new mailing list), 2005-10-05
<li>Rev 2.16 (JD) Added 4.33.2, 2005-09-06
<li>Rev 2.15 (JD) Updates, including mailing-list change, 2005-05-21
<li>Rev 2.14 (MDS) Updated 4.12, 2004-11-26
<li>Rev 2.13 (JD) Added 4.6.1, updated 4.7, 2004-06-23
<li>Rev 2.12 (JD) Updated 4.27, 2004-04-11
<li>Rev 2.11 (JD) Various updates, 2004-01-18
<li>Rev 2.10 (MDS) Various updates, 2004-01-03
<li>Rev 2.9 (CP) Converted to Gnu texinfo format, 2002-09-10
<li>Rev 2.8 (MDS) Minor updates 2002-07-10, released with lm_sensors 2.6.4
<li>Rev 2.7 (MDS) Minor updates 2002-04-25
<li>Rev 2.6 (MDS) Minor updates 2002-01-15, released with lm_sensors 2.6.3
<li>Rev 2.5 (MDS) Minor updates 2001-11-11, released with lm_sensors 2.6.2
<li>Rev 2.4 (MDS) Minor updates 2001-07-22
<li>Rev 2.3 (MDS) General update, 2001-02-24, released with lm_sensors 2.6.0. 
<li>Rev 2.2 (Frodo) Corrections for lm_sensors 2.4, 1999-09-20
<li>Rev 2.1 (Frodo) Corrections for lm_sensors 2.2, 1999-01-12
<li>Rev 2.0 (Frodo) Major revision for lm_sensors 2.1, 1998-12-29
<li>Rev 1.10 (Frodo) Modified 3.8, updated some other things, 1998-09-24
<li>Rev 1.9 (Frodo) Added 3.15, 1998-09-06
<li>Rev 1.8 (Frodo) Added 3.14, 1998-09-05
<li>Rev 1.7 (Phil) Added 3.13 and some other minor changes, 1998-09-01
<li>Rev 1.6 (Frodo) Added 4, 4.1, 4.2, 4.3, 4.4, 4.5, 1998-09-01
<li>Rev 1.5 (Frodo) Added 2.3, 2.4, 3.9, 3.10, 3.11, 1998-08-26
<li>Rev 1.4 (Frodo) Added some more Winbond information, and 3.5-3.8, 1998-08-17
<li>Rev 1.3 (Phil) Added info on the Winbond chip, 1998-08-16
<li>Rev 1.2 (Frodo) Adapation, 1998-08-10
<li>Rev 1.1 (Phil) Modifications, 1998-08-09
<li>Rev 1.0 (Phil) First version, 1998-08-03
</ul>

</body></html>
View Lorry Controller Status