Changeset 1102

Show
Ignore:
Timestamp:
05/31/01 04:20:50 (12 years ago)
Author:
mds
Message:

minor updates

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • lm-sensors/trunk/doc/FAQ

    r1055 r1102  
    12121.1 What sensors are available on my PC? 
    13131.2 What can a sensor chip like the "LM78" do?  
    14 1.3 Where do I find out more about any of these LMxx chips? 
     141.3 Where do I find out more about any of these sensor chips? 
    1515 
    16162. Sensor and Bus Basics 
     
    3535  3.4C The min and max settings in /etc/sensors.conf didn't take effect! 
    3636  3.4D One sensor isn't hooked up on my board! 
     37  3.4E I need help with sensors.conf! 
    37383.5 What about the 'No such file or directory' warnings when I compile it? 
    38393.6 I get all kind of weird compilation errors? 
     
    6667  4.17B Bad readings from the VIA 686A! 
    6768  4.17C Bad readings from the MTP008! 
     69  4.17D Bad temperature readings from the SIS5595! 
    68704.18 How do I configure two chips (LM87) differently? 
    69714.19 Dmesg says Upgrade BIOS! I don't want to! 
     
    7981  4.24B Sensors-detect says "Can't open /dev/i2c[-/]0" 
    8082  4.24C Sensors-detect doesn't find any sensors 
     834.25 Sensors says 'Error: Line xxx: zzzzzzz' 
    8184 
    82855 How to Ask for Help   
     
    184187it is simply a memory-mapped area, 64KB in size (0x0000 - 0xFFFF) 
    185188where 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. 
     189are found. It isn't necessarily a separate physical bus. 
     190See the file /proc/ioports for a list of devices living on 
     191the "ISA Bus" in your system. If you don't like the term "ISA Bus" 
     192think "I/O Space". 
    188193 
    189194 
     
    357362 
    358363 
     3643.4E I need help with sensors.conf! 
     365 
     366    There is detailed help at the top of that file. 
     367 
     368 
    3593693.5 What about the 'No such file or directory' warnings when I compile it? 
    360370 
     
    614624 
    615625 
     6264.17D Bad temperature readings from the SIS5595! 
     627 
     628    This chip can use multiple thermistor types and there are also 
     629two different versions of the chip. We are trying to get the driver 
     630working better and develop formulas for different thermistors 
     631but we aren't there yet. Sorry. 
     632 
     633 
    6166344.18 How do I configure two chips (LM87) differently? 
    617635 
     
    632650is complex. For the ALI M7101 device, there is a solution which uses the 
    6336512.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. 
     652For other PCI devices, you can try to modify 
     653the m7101 solution in prog/hotplug. 
    635654    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. 
     655you may be able to set the address with a force parameter. The via686a 
     656and sis5595 chip drivers, and some bus drivers, support the command line 
     657'modprobe via686a force_addr=0xADDRESS' where ADDRESS 
     658is the I/O address (cat /proc/ioports to verify you don't have 
     659a conflict). Other drivers generally do not 
     660support the force_addr parameter. Sorry. Check the documentation 
     661for your driver in doc/[chips,busses] and if we don't suupport it 
     662you can send us your request. 
    641663 
    642664 
     
    738760        3) Check the Motherboard Monitor website 
    739761           (see useful_addresses.html) for a good cross-reference. 
     762 
     7634.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. 
    740769 
    741770