Changeset 215 for lm-sensors/trunk/INSTALL
- Timestamp:
- 02/12/99 05:56:34 (14 years ago)
- Files:
-
- 1 modified
-
lm-sensors/trunk/INSTALL (modified) (7 diffs)
Legend:
- Unmodified
- Added
- Removed
-
lm-sensors/trunk/INSTALL
r139 r215 39 39 The directory where 'make install' installs all executables. 40 40 * INCLUDEDIR ($(PREFIX)/include) 41 The bas icdirectory where 'make install' installs your include files.41 The base directory where 'make install' installs your include files. 42 42 Actually, SYSINCLUDEDIR ($(INCLUDEDIR)/linux) is used for kernel header 43 43 files, and LIBINCLUDEDIR ($(INCLUDEDIR)/sensors) is used for library 44 44 header files. 45 * MANDIR ($(PREFIX)/man) 46 The base directory where manual pages are installed. 47 * MANOWN, MANGRP (root, root) 48 Owner and group of installed manual pages 45 49 46 Warning! In newer 2.1 kernels, there is support for I2C. This support is47 NOT compatible with this module! Actually, Simon Vogl's modules package50 Warning! In 2.2 and newer 2.1 kernels, there is support for I2C. This support 51 is NOT compatible with this module! Actually, Simon Vogl's modules package 48 52 (which IS compatible) is scheduled to replace the current support. If you 49 53 actually use these modules, you have a problem; they can not coexist … … 51 55 the old modules in the kernel tree with the new stuff in our i2c directory, 52 56 recompile the kernel, and then compile our modules with I2C=0. If you try 53 this, please share the results with us! 57 this, please share the results with us! There have also been some rumors 58 about the peaceful coexistence of both sets of modules, but others found 59 some problems with it. 54 60 55 61 Please make sure that /usr/include/linux and /usr/include/asm are symlinks … … 69 75 If you just want to run a test without installing them, try the following: 70 76 insmod i2c/i2c-core.o 71 insmod src/i2c-proc.o 72 insmod src/smbus.o 73 insmod src/sensors.o 74 insmod src/isa.o 75 insmod src/piix4.o # Or whatever SMBus controller you have 76 insmod src/lm78.o # Or whatever hardware monitoring chip you have 77 insmod kernel/i2c-proc.o 78 insmod kernel/i2c-dev.o 79 insmod kernel/smbus.o 80 insmod kernel/sensors.o 81 insmod kernel/busses/isa.o 82 insmod kernel/busses/piix4.o # Or whatever SMBus controller you have 83 insmod kernel/chips/lm78.o # Or whatever hardware monitoring chip you have 77 84 Now you should have new directories under /proc/sys/dev/sensors and some files 78 85 beginning with i2c in /proc/bus. … … 81 88 do 'modprobe isa && modprobe piix4 && modprobe lm78 && modprobe i2c-proc' 82 89 (the last is optional) from any directory to reach the same situation. 90 91 There is a program 'detect.pl' in prog/detect which should tell you at least 92 what bus driver you should insert. This program is not completely failsafe, 93 but it may at least help. It will be expanded to cover chip detection too, 94 in the future. 83 95 84 96 Do not panic if some (or all) of the values in the /proc/sys/dev/sensors/*/* … … 94 106 (normally /usr/local/lib). It needs a configuration file, which is usually 95 107 called 'sensors.conf', and can be placed in /etc, /usr/lib/sensors, 96 /usr/local/lib/sensors, /usr/lib, or /usr/local/lib. [NOTE: No real 97 config file documentation is written yet. A relatively well-commented 98 example can be found in the etc directory.] 108 /usr/local/lib/sensors, /usr/lib, or /usr/local/lib. 109 110 Note that if you already have a config file, it is NOT overwritten! You 111 may still want to do this by hand (`cp etc/sensors.conf.eg /etc/sensors.conf') 112 as the example config file may be updated. 99 113 100 114 Where version 1 of this package had the human-readable /proc/sensors file, … … 102 116 and displays it in a comparable format. This program is called 'sensors'. 103 117 Everybody can use it to read sensors values; only root can use it to 104 set minimum and maximum values .118 set minimum and maximum values (using the `-s' switch). 105 119 106 120 If you want to run 'sensors' without installing the package, you must … … 111 125 source code. 112 126 113 One of the next releases of this package will have a user-space probe program,114 which tells you which chips and busses are present, and which modules you115 will have to load. At this moment, just try to load the modules; if no chip116 or bus is detected, the module will fail to insert. [NOTE: not true for117 the bit-lp.o and bit-elv.o drivers. Don't try them without expecting118 fake devices]119 120 127 Please examine the files in the doc subdirectory for more information, 121 128 especially about individual driver. You can always mail us at
