Changeset 1102
- Timestamp:
- 05/31/01 04:20:50 (8 years ago)
- Files:
-
- lm-sensors/trunk/doc/FAQ (modified) (9 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
lm-sensors/trunk/doc/FAQ
r1055 r1102 12 12 1.1 What sensors are available on my PC? 13 13 1.2 What can a sensor chip like the "LM78" do? 14 1.3 Where do I find out more about any of these LMxxchips?14 1.3 Where do I find out more about any of these sensor chips? 15 15 16 16 2. Sensor and Bus Basics … … 35 35 3.4C The min and max settings in /etc/sensors.conf didn't take effect! 36 36 3.4D One sensor isn't hooked up on my board! 37 3.4E I need help with sensors.conf! 37 38 3.5 What about the 'No such file or directory' warnings when I compile it? 38 39 3.6 I get all kind of weird compilation errors? … … 66 67 4.17B Bad readings from the VIA 686A! 67 68 4.17C Bad readings from the MTP008! 69 4.17D Bad temperature readings from the SIS5595! 68 70 4.18 How do I configure two chips (LM87) differently? 69 71 4.19 Dmesg says Upgrade BIOS! I don't want to! … … 79 81 4.24B Sensors-detect says "Can't open /dev/i2c[-/]0" 80 82 4.24C Sensors-detect doesn't find any sensors 83 4.25 Sensors says 'Error: Line xxx: zzzzzzz' 81 84 82 85 5 How to Ask for Help … … 184 187 it is simply a memory-mapped area, 64KB in size (0x0000 - 0xFFFF) 185 188 where many "legacy" functions, such as keyboard and interrupt controllers, 186 are found. See the file /proc/ioports for a list of devices living on 187 the "ISA Bus" in your system. 189 are found. It isn't necessarily a separate physical bus. 190 See the file /proc/ioports for a list of devices living on 191 the "ISA Bus" in your system. If you don't like the term "ISA Bus" 192 think "I/O Space". 188 193 189 194 … … 357 362 358 363 364 3.4E I need help with sensors.conf! 365 366 There is detailed help at the top of that file. 367 368 359 369 3.5 What about the 'No such file or directory' warnings when I compile it? 360 370 … … 614 624 615 625 626 4.17D Bad temperature readings from the SIS5595! 627 628 This chip can use multiple thermistor types and there are also 629 two different versions of the chip. We are trying to get the driver 630 working better and develop formulas for different thermistors 631 but we aren't there yet. Sorry. 632 633 616 634 4.18 How do I configure two chips (LM87) differently? 617 635 … … 632 650 is complex. For the ALI M7101 device, there is a solution which uses the 633 651 2.4 kernel's 'hotplug' facility. See prog/hotplug in our package. 634 For other PCI devices, you can try to modify the m7101 solution in prog/hotplug. 652 For other PCI devices, you can try to modify 653 the m7101 solution in prog/hotplug. 635 654 If the problem is a PCI device whose base address is not set, 636 you may be able to set the address with a force parameter. For the via686a 637 driver, use the command line 'modprobe via686a force=9191,0xADDRESS' where 638 ADDRESS is the I/O address (cat /proc/ioports to verify you don't have 639 a conflict). Other drivers (for example sis5595) generally do not 640 support the force parameter. Sorry. You can send us your request. 655 you may be able to set the address with a force parameter. The via686a 656 and sis5595 chip drivers, and some bus drivers, support the command line 657 'modprobe via686a force_addr=0xADDRESS' where ADDRESS 658 is the I/O address (cat /proc/ioports to verify you don't have 659 a conflict). Other drivers generally do not 660 support the force_addr parameter. Sorry. Check the documentation 661 for your driver in doc/[chips,busses] and if we don't suupport it 662 you can send us your request. 641 663 642 664 … … 738 760 3) Check the Motherboard Monitor website 739 761 (see useful_addresses.html) for a good cross-reference. 762 763 4.25 Sensors says 'Error: Line xxx: zzzzzzz' 764 765 These are errors from the libsensors library in 766 reading the /etc/sensors.conf configuration file. Go to that line 767 number and fix it. If you have a parse error, perhaps you have 768 to put the feature name in double quotes. 740 769 741 770
