diff --git a/README b/README index 9fc1862f..0626bbb4 100644 --- a/README +++ b/README @@ -46,7 +46,7 @@ See the lm_sensors download page for further guidance: http://www.lm-sensors.org/wiki/Download -WARNING! If you downloaded this package through our CVS archive, you walk +WARNING! If you downloaded this package through our SVN archive, you walk the cutting edge. Things may not even compile! On the other hand, you will be the first to profit from new drivers and other changes. Have fun! diff --git a/README.directories b/README.directories index cbeb8bdb..8d1e5b3a 100644 --- a/README.directories +++ b/README.directories @@ -1,7 +1,5 @@ The directories within this package: -* CVS - The CVS directories. Do not touch these! * doc Documentation about the modules within this package, and all other things. * etc diff --git a/doc/FAQ b/doc/FAQ index 5263d852..6c5695c8 100644 --- a/doc/FAQ +++ b/doc/FAQ @@ -120,7 +120,7 @@ lm_sensors 5.9 Why did you decide not to support undocumented chips? 6 How to Contribute 6.1 How to write a driver - 6.2 How to get CVS access + 6.2 How to get SVN access 6.3 How to donate hardware to the project 6.4 How to join the project mailing lists 6.5 How to access mailing list archives @@ -192,9 +192,8 @@ selection of sensor chips. Their websites are: * `http://www.national.com' - Please see the file -`http://www2.lm-sensors.nu/~lm78/useful_addresses.html' for links to -other companies' websites. + Please see the file `http://www.lm-sensors.org/wiki/UsefulLinks' for +links to other companies' websites. 2 Sensor and Bus Basics *********************** @@ -358,9 +357,8 @@ for candidates, then *note Help::) 4. Check the Motherboard Monitor (http://mbm.livewiredev.com/) website and the "links" - (http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/useful_addresses.html) - page on our website (http://www2.lm-sensors.nu/~lm78/) some good - cross-references. + (http://www.lm-sensors.org/wiki/UsefulLinks) page on our website + (http://www.lm-sensors.org) some good cross-references. 3.2.2 Do you support motherboard XYZ? ------------------------------------- @@ -375,17 +373,17 @@ This we have good answers for. * Sorted by Manufacturer: `README' * Sorted by Manufacturer: - `http://www2.lm-sensors.nu/~lm78/supported.html' + `http://www.lm-sensors.org/wiki/SupportedDevices' * Sorted by Sensor Driver: `doc/chips/SUMMARY' * Newest Driver Status: - `http://www2.lm-sensors.nu/~lm78/newdrivers.html' + `http://www.lm-sensors.org/wiki/NewDrivers' 3.2.4 Anybody working on a driver for chip XYZ? ----------------------------------------------- -Newest Driver Status: `http://www2.lm-sensors.nu/~lm78/newdrivers.html' +Newest Driver Status: `http://www.lm-sensors.org/wiki/NewDrivers' 3.3 Which modules should I insert? ================================== @@ -738,7 +736,7 @@ Linux might be quite hard to do. 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 -`http://www2.lm-sensors.nu/~lm78/useful_addresses.html' for addresses. +`http://www.lm-sensors.org/wiki/UsefulLinks' for addresses. 4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen). Why? ============================================================================== @@ -1100,8 +1098,8 @@ Either website. When you know what chips you have, check the Newest Driver Status -(http://www2.lm-sensors.nu/~lm78/newdrivers.html) web page to see if -support has been added for your chip in a later release or in CVS. +(http://www.lm-sensors.org/wiki/NewDrivers) web page to see if support +has been added for your chip in a later release or in CVS. 4.25 Sensors says `Error: Line xxx: zzzzzzz' ============================================ @@ -1272,9 +1270,9 @@ Post your question to our discussion list individual authors, unless you have something private to say. Instead of using email, you can also use the web-based support area, -at `http://www.lm-sensors.org/wiki/FeedbackAndSupport'. 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. +at `http://www.lm-sensors.org/wiki/FeedbackAndSupport'. 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. Here's what you should send us: @@ -1448,23 +1446,18 @@ cause trouble. See `doc/developers/new_drivers' in our package for instructions. -6.2 How to get CVS access +6.2 How to get SVN access ========================= -For anonymous CVS read access, see the instructions on our download -page (http://www2.lm-sensors.nu/~lm78/download.html#cvs). -Alternatively, nightly snapshots -(http://www2.lm-sensors.nu/~lm78/download.html#snapshots) of the CVS -repositories are available. +For anonymous SVN read access, see the instructions on our download +page (http://www.lm-sensors.org/wiki/Download). - For write access, run the script `doc/developers/genpasswd.pl' in -our package and follow the instructions. Let us know what part of the -package you would like to work on. + For write access, please contact us. 6.3 How to donate hardware to the project ========================================= -Contact us (http://www2.lm-sensors.nu/~lm78/author.html#contact). +Contact us (http://www.lm-sensors.org/wiki/FeedbackAndSupport). 6.4 How to join the project mailing lists ========================================= diff --git a/doc/busses/i2c-piix4 b/doc/busses/i2c-piix4 index b467d9dc..bf3e29ff 100644 --- a/doc/busses/i2c-piix4 +++ b/doc/busses/i2c-piix4 @@ -97,5 +97,4 @@ Thinkpad laptops, but desktop systems may also be affected. We have no list of all affected systems, so the only safe solution was to prevent access to the SMBus on all IBM systems (detected using DMI data.) -For additional information, read: -http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/README.thinkpad +For additional information, read README.thinkpad. diff --git a/doc/developers/genpasswd.pl b/doc/developers/genpasswd.pl deleted file mode 100755 index 41b31519..00000000 --- a/doc/developers/genpasswd.pl +++ /dev/null @@ -1,34 +0,0 @@ -#!/usr/bin/perl -# -# Use this Perl script to generate a password -# for you to use for CVS access. Then, send -# the output to phil@netroedge.com so Phil -# can add you to the CVS writers group -# (pending approval, of course). - -$salt1=int(65 + rand(115 - 65)); -$salt2=int(65 + rand(115 - 65)); -if ($salt1 > 90) { $salt1+=7; } -if ($salt2 > 90) { $salt2+=7; } -$salt= pack("cc",$salt1, $salt2); -print "This program will generate an encrypted version of your CVS password.\n"; -print "Enter your CVS password below.\n"; -system "stty -echo"; -print "Password: "; -chop($word = ); -print "\n\n"; -print "Please enter it again.\n"; -print "Password: "; -chop($word2 = ); -print "\n"; -system "stty echo"; -if ($word ne $word2) { print "Passwords do not match, action aborted!\n"; exit; } -$passwd=crypt($word, $salt); -print "Here is your encrypted password: $passwd\n"; -print "Send this encrypted password to phil\@netroedge.com\n"; -print "with your requested username.\n"; -print "Please specify whether you want access to i2c, lm_sensors, or both.\n"; -print "Please also indicate what area of the project you wish to work on.\n"; -print "\n"; -print "Please include your username in the CVS comments when you\n"; -print "check in files like so: (username)\n"; diff --git a/doc/developers/makefiles b/doc/developers/makefiles index d5890f77..93bfd2f0 100644 --- a/doc/developers/makefiles +++ b/doc/developers/makefiles @@ -32,7 +32,7 @@ There are several interesting targets defined through this Makefile: Regenerate version.h, using the current date for the date-stamp, and a user-supplied version number. * package - Create a .tar.gz file containing everything except the CVS directories. + Create a .tar.gz file containing everything except the SVN directories. * src/lm78.o, i2c/i2c-core.o, ... You can of course also specify one or more targets to make. diff --git a/doc/developers/new_drivers b/doc/developers/new_drivers index 11a58c7b..cb5d7de5 100644 --- a/doc/developers/new_drivers +++ b/doc/developers/new_drivers @@ -25,7 +25,7 @@ steps apply. * Consider subscribing to the mailing list. -* Check out our latest code from CVS. +* Check out our latest code from SVN. You should use this as a base for your development. See instructions on our download page. @@ -124,14 +124,9 @@ steps apply. (or if applicable your company's name) is at the top of the new driver so we know you are giving it to us under the GPL. -* Get CVS write access if you want to check in your driver yourself. - Do this by running the script doc/developers/genpasswd.pl and following - the instructions it gives you. - -* Submit the changes to us, or check them in. - Do a 'cvs update' to get in sync (things will have changed since - you started), then submit the changes to us as a patch against CVS, - or check them in. +* Submit the changes to us. + Do a 'svn update' to get in sync (things will have changed since + you started), then submit the changes to us as a patch against SVN. * If you want to have your driver integrated to Linux 2.6, you have to port your driver to the new sysfs interface. Once done and preferably diff --git a/doc/fancontrol.txt b/doc/fancontrol.txt index c6cdf1db..90a9f038 100644 --- a/doc/fancontrol.txt +++ b/doc/fancontrol.txt @@ -7,7 +7,7 @@ Introduction fancontrol is a shellscript for use with lm_sensors. It reads its configuration from a file, then calculates fan speeds from temperatures and sets the corresponding pwm outputs to the computed values. It is included in -lm_sensors since 2.8.0, the latest version is always available through CVS or +lm_sensors since 2.8.0, the latest version is always available through SVN or at http://www.hdev.de/fancontrol/ For easy configuration, there's a script named pwmconfig which lets you interactively write your configuration file for fancontrol. Alternatively you can write this file yourself using the diff --git a/doc/lm_sensors-FAQ.html b/doc/lm_sensors-FAQ.html index f1725c61..d62f8740 100644 --- a/doc/lm_sensors-FAQ.html +++ b/doc/lm_sensors-FAQ.html @@ -3,7 +3,7 @@ Sensors FAQ for lm_sensors version 2.18 - + @@ -14,8 +14,9 @@ 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.sc { font-variant:small-caps } + span.roman { font-family:serif; font-weight:normal; } + span.sansserif { font-family:sans-serif; font-weight:normal; } --> @@ -71,23 +72,23 @@ Jean Delvare
  • 3.2.4 Anybody working on a driver for chip XYZ?
  • 3.3 Which modules should I insert? -
  • 3.4 Do I need the configuration file /etc/sensors.conf? +
  • 3.4 Do I need the configuration file /etc/sensors.conf? -
  • 3.5 What about the No such file or directory warnings when I compile? +
  • 3.5 What about the `No such file or directory' warnings when I compile?
  • 3.6 I get all kinds of weird compilation errors?
  • 3.7 It still does not compile or patch! -
  • 3.8 make install fails on Mandrake kernels -
  • 3.9 I get unresolved symbols when I modprobe modules (Red Hat especially) +
  • 3.8 make install fails on Mandrake kernels +
  • 3.9 I get unresolved symbols when I modprobe modules (Red Hat especially)
  • 3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)
  • 4 Problems @@ -111,7 +112,7 @@ Jean Delvare
  • 4.10 Can I be alerted when an ALARM occurs?
  • 4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen). Why?
  • 4.12 My BIOS reports a much higher CPU temperature than your modules! -
  • 4.13 I try to read the raw /proc files, but the values are strange?!? +
  • 4.13 I try to read the raw /proc files, but the values are strange?!?
  • 4.14 How do I set new limits?
  • 4.18 How do I configure two chips (LM87) differently? -
  • 4.19 Dmesg says Upgrade BIOS! I don't want to! +
  • 4.19 Dmesg says `Upgrade BIOS'! I don't want to! -
  • 4.20 Sensors says Can't access procfs/sysfs file -
  • 4.21 Sensors says No sensors found! +
  • 4.20 Sensors says `Can't access procfs/sysfs file' +
  • 4.21 Sensors says `No sensors found!'
  • 4.22 Sensors output is not correct!
  • 4.23 What is at I2C address XXX? -
  • 4.25 Sensors says Error: Line xxx: zzzzzzz +
  • 4.25 Sensors says `Error: Line xxx: zzzzzzz'
  • 4.26 Sensors only gives the name, adapter, and algorithm for my chip -
  • 4.27 Sensors says ERROR: Can't get xxxxx data! +
  • 4.27 Sensors says `ERROR: Can't get xxxxx data!'
  • 4.28 Sensors doesn't find any sensors, just eeproms.
  • 4.29 Inserting modules hangs my board
  • 4.30 Inserting modules slows down my board @@ -185,7 +186,7 @@ Jean Delvare
  • 6 How to Contribute -

    Please see the file http://www2.lm-sensors.nu/~lm78/useful_addresses.html +

    Please see the file http://www.lm-sensors.org/wiki/UsefulLinks for links to other companies' websites.

    -Next: , + +Next: , Previous: Overview, Up: Top -
    +

    2 Sensor and Bus Basics

    @@ -330,15 +340,17 @@ Up: Top

    -Next: , + + +Next: , Up: Basics -
    +

    2.1 How are these sensors read?

    Sensor chips reside on either the ISA bus, the SMBus, or both. -See the file doc/chips/SUMMARY in our package for a list. +See the file doc/chips/SUMMARY in our package for a list.

    To communicate with chips on the ISA bus, the software uses simple I/O reads and writes. @@ -348,10 +360,12 @@ use an SMBus interface device, explained below.

    -Next: , + + +Next: , Previous: Section 2.1, Up: Basics -
    +

    2.2 What is the SMBus? And the I2C bus?

    @@ -376,10 +390,12 @@ talk to pure I2C devices.

    -Next: , + + +Next: , Previous: Section 2.2, Up: Basics -
    +

    2.3 I don't have an ISA bus!

    @@ -389,16 +405,18 @@ 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 /proc/ioports for a list of devices living on +See the file /proc/ioports 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".

    -Next: , + + +Next: , Previous: Section 2.3, Up: Basics -
    +

    2.4 What sensors do processors have?

    @@ -410,7 +428,7 @@ 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 doc/chips/SUMMARY in our package which +Any sensor chip listed in doc/chips/SUMMARY in our package which has support for more than one temperature supports external temperature sensing.

    Older motherboards and processors without this feature generally use @@ -437,10 +455,12 @@ interface on the P2 Xeon SEC.

    -Next: , + + +Next: , Previous: Section 2.4, Up: Basics -
    +

    2.5 How often are the sensor values updated?

    @@ -455,9 +475,11 @@ read the values again, you will get the 'old' values again.

    -Previous: Section 2.5, + + +Previous: Section 2.5, Up: Basics -
    +

    2.6 How are alarms triggered?

    @@ -467,7 +489,7 @@ 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 /proc/interrupts. +Interrupt Request and are the interrupt lines you can find in /proc/interrupts. 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 @@ -481,10 +503,11 @@ persists after that, the bits will be set on the next scanning sweep, etc.

    -Next: , + +Next: , Previous: Basics, Up: Top -
    +

    3 Installation and Management

    @@ -493,20 +516,22 @@ Up: Top
  • Section 3.1: Why so many modules, and how do I cope with them?
  • Section 3.2: How do I know which chips I own?
  • Section 3.3: Which modules should I insert? -
  • Section 3.4: Do I need the configuration file /etc/sensors.conf? -
  • Section 3.5: What about the No such file or directory warnings +
  • Section 3.4: Do I need the configuration file /etc/sensors.conf? +
  • Section 3.5: What about the `No such file or directory' warnings
  • Section 3.6: I get all kinds of weird compilation errors?
  • Section 3.7: It still does not compile or patch! -
  • Section 3.8: make install fails on Mandrake kernels -
  • Section 3.9: I get unresolved symbols when I modprobe modules +
  • Section 3.8: make install fails on Mandrake kernels +
  • Section 3.9: I get unresolved symbols when I modprobe modules
  • Section 3.10: I2C_DRIVERID_ADM1024 undefined (Red Hat especially)

    -Next: , + + +Next: , Up: Installation -
    +

    3.1 Why so many modules, and how do I cope with them?

    @@ -517,26 +542,28 @@ space. On the other hand, it can be a bit confusing at first.

    Here are two simple guidelines:

      -
    • Run sensors-detect and do what it tells you. -
    • Always use modprobe, not insmod. +
    • Run sensors-detect and do what it tells you. +
    • Always use modprobe, not insmod.
    -

    Further information is in doc/modules. +

    Further information is in doc/modules.

    -Next: , + + +Next: , Previous: Section 3.1, Up: Installation -
    +

    3.2 How do I know which chips I own?

    We have an excellent program that scans all your hardware. -It is called sensors-detect and is installed in /usr/local/sbin -by make install. Just execute this script, and it will tell you. +It is called sensors-detect and is installed in /usr/local/sbin +by make install. Just execute this script, and it will tell you.

    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 @@ -562,8 +589,8 @@ for candidates, then see Help)

  • Look at your motherboard.
  • Check the manufacturer's website or ask their support
  • Check the Motherboard Monitor website and the -"links" -page on our website some good cross-references. +"links" +page on our website some good cross-references.

    @@ -578,151 +605,161 @@ page on our website some good cro

    This we have good answers for.

    3.2.4 Anybody working on a driver for chip XYZ?

    -

    Newest Driver Status: http://www2.lm-sensors.nu/~lm78/newdrivers.html +

    Newest Driver Status: http://www.lm-sensors.org/wiki/NewDrivers

    -Next: , + + +Next: , Previous: Section 3.2, Up: Installation -
    +

    3.3 Which modules should I insert?

    -

    sensors-detect will tell you. Take the modprobe lines it -recommends and paste them into the appropriate /etc/rc.d/xxxx file +

    sensors-detect will tell you. Take the modprobe lines it +recommends and paste them into the appropriate /etc/rc.d/xxxx file to be executed at startup.

    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 i2c-isa.o. +if there are sensor chips on the ISA bus, you also need i2c-isa.o. for each type of chip you own. That's all. On my computer, I could use the following lines:

      -
    • modprobe i2c-isa -
    • modprobe i2c-piix4 -
    • modprobe lm78 -
    • modprobe lm75 -
    • modprobe i2c-dev -
    • sensors -s +
    • modprobe i2c-isa +
    • modprobe i2c-piix4 +
    • modprobe lm78 +
    • modprobe lm75 +
    • modprobe i2c-dev +
    • sensors -s

    -Next: , + + +Next: , Previous: Section 3.3, Up: Installation -
    +
    -

    3.4 Do I need the configuration file /etc/sensors.conf?

    +

    3.4 Do I need the configuration file /etc/sensors.conf?

    -

    Yes, for any applications that use libsensors, including the -sensors application included in our package. +

    Yes, for any applications that use libsensors, including the +sensors 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 /etc/sensors.conf, but it will not +It is automatically installed as /etc/sensors.conf, but it will not overwrite any existing file with that name.

    -

    3.4.1 The labels for the voltage and temperature readings in sensors are incorrect!

    +

    3.4.1 The labels for the voltage and temperature readings in sensors are incorrect!

    Every motherboard is different. You can customize the labels -in the file /etc/sensors.conf. That's why it exists! -The default labelling (in lib/chips.c and /etc/sensors.conf) is just +in the file /etc/sensors.conf. That's why it exists! +The default labelling (in lib/chips.c and /etc/sensors.conf) is just a template.

    -

    3.4.2 The min and max for the readings in sensors are incorrect!

    +

    3.4.2 The min and max for the readings in sensors are incorrect!

    -

    You can customize them in the file /etc/sensors.conf. See above. +

    You can customize them in the file /etc/sensors.conf. See above.

    -

    3.4.3 The min and max settings in /etc/sensors.conf didn't take effect!

    +

    3.4.3 The min and max settings in /etc/sensors.conf didn't take effect!

    -

    You forgot to run sensors -s. See above. +

    You forgot to run sensors -s. See above.

    3.4.4 One sensor isn't hooked up on my board!

    -

    Use an ignore line in /etc/sensors.conf so it isn't -displayed in sensors. +

    Use an ignore line in /etc/sensors.conf so it isn't +displayed in sensors.

    -

    3.4.5 I need help with sensors.conf!

    +

    3.4.5 I need help with sensors.conf!

    There is detailed help at the top of that file.

    -

    3.4.6 Do you have a database of sensors.conf entries for specific boards?

    +

    3.4.6 Do you have a database of sensors.conf entries for specific boards?

    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.

    -Next: , + + +Next: , Previous: Section 3.4, Up: Installation -
    +
    -

    3.5 What about the No such file or directory warnings when I compile?

    +

    3.5 What about the `No such file or directory' warnings when I compile?

    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 make program +dynamically. They are not distributed with the package. The make program notices they are not there, and warns about that - and the first thing it will do is generate them. So all is well.

    -Next: , + + +Next: , Previous: Section 3.5, Up: Installation -
    +

    3.6 I get all kinds of weird compilation errors?

    Check that the correct i2c header files are used. Depending on -how you installed, they should be under either /usr/local/include or -/usr/src/linux*/include. Try to edit the Makefile for the other setting. +how you installed, they should be under either /usr/local/include or +/usr/src/linux*/include. Try to edit the Makefile for the other setting.

    -

    3.6.1 No rule to make target xxxx needed by xxxx - how to fix?

    +

    3.6.1 `No rule to make target xxxx needed by xxxx' - how to fix?

      -
    • See I get all kinds of weird compilation errors, also try make clean in lm_sensors. -
    • If that doesn't work, try make clean in i2c. -
    • If that doesn't work, try make clean in the kernel. -
    • Also make sure /usr/include/linux points to /usr/src/linux/include/linux. +
    • See I get all kinds of weird compilation errors, also try make clean in lm_sensors. +
    • If that doesn't work, try make clean in i2c. +
    • If that doesn't work, try make clean in the kernel. +
    • Also make sure /usr/include/linux points to /usr/src/linux/include/linux.

    -Next: , + + +Next: , Previous: Section 3.6, Up: Installation -
    +

    3.7 It still does not compile or patch!

    @@ -736,48 +773,52 @@ patches first!

    -Next: , + + +Next: , Previous: Section 3.7, Up: Installation -
    +
    -

    3.8 make install fails on Mandrake kernels

    +

    3.8 make install fails on Mandrake kernels

    -

    Mandrake uses a non-standard version.h file which confuses our Makefile. -Edit our Makefile on the MODDIR := line to hard-code the module directory. +

    Mandrake uses a non-standard version.h file which confuses our Makefile. +Edit our Makefile on the MODDIR := line to hard-code the module directory.

    -Next: , + + +Next: , Previous: Section 3.8, Up: Installation -
    +
    -

    3.9 I get unresolved symbols when I modprobe modules (Red Hat especially)

    +

    3.9 I get unresolved symbols when I modprobe modules (Red Hat especially)

    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
    -

    You can also run depmod -a -e to see all unresolved symbols. +

    You can also run depmod -a -e to see all unresolved symbols.

    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 make LINUX=/usr/src/linux-2.4.14. +are running with something like make LINUX=/usr/src/linux-2.4.14.

    Try the following to be sure:

      -
    • nm --extern MODULE.o +
    • nm --extern MODULE.o Filter out the kernel symbols, like kmalloc, printk etc. and note the number code behind them, like printk_R1b7d4074. If there is no numeric code after them, note this too. -
    • grep SYMBOL /proc/ksyms +
    • grep SYMBOL /proc/ksyms Substitute SYMBOL by the basename of the symbols above, like kmalloc, printk etc. Note the number code behind them, or the lack thereof.
    • Compare both sets of symbols. Are they the same? If so, the problem @@ -787,9 +828,11 @@ versioning problem.

      -Previous: Section 3.9, + + +Previous: Section 3.9, Up: Installation -
      +

      3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)

      @@ -800,30 +843,31 @@ structure. When you update kernels, they may persist. To get rid of these obsolete header files, at a command prompt:
        -
      1. rpm -qa | grep i2c -
      2. Look for kernel-i2c, or a similar rpm in the output +
      3. rpm -qa | grep i2c +
      4. Look for kernel-i2c, or a similar rpm in the output
      5. <as root> -rpm -ev kernel-i2c (or the name of the similar package) +rpm -ev kernel-i2c (or the name of the similar package) If this complains about dependencies, you can try adding ---nodeps, but this *MAY* break something else. Not likely, +--nodeps, 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. -
      6. Try (in the build directory of lm_sensors) - 
                  make clean
-          make
+
      7. Try (in the build directory of lm_sensors)
+     
                  make clean
+          make
      
        
      
      8. If you still have problems, you may have to replace the include
-paths in the .c/.h files with absolute paths to the header files. 
+paths in the .c/.h 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.

      -Next: , + +Next: , Previous: Installation, Up: Top -
      +

      4 Problems

      @@ -841,21 +885,21 @@ Up: Top
    • Section 4.10: Can I be alerted when an ALARM occurs?
    • Section 4.11: SMBus transactions on my PIIX4 simply don't work. Why?
    • Section 4.12: My BIOS reports a higher CPU temperature than you! -
    • Section 4.13: I read strange values from the raw /proc files! +
    • Section 4.13: I read strange values from the raw /proc files!
    • Section 4.14: How do I set new limits?
    • Section 4.15: Some sensors are doubly detected?
    • Section 4.16: I ran sensors-detect, but now I get strange readings?!
    • Section 4.17: Bad readings from particular chips
    • Section 4.18: How do I configure two chips (LM87) differently? -
    • Section 4.19: Dmesg says Upgrade BIOS! I don't want to! -
    • Section 4.20: Sensors says Can't access procfs/sysfs file -
    • Section 4.21: Sensors says No sensors found! +
    • Section 4.19: Dmesg says `Upgrade BIOS'! I don't want to! +
    • Section 4.20: Sensors says `Can't access procfs/sysfs file' +
    • Section 4.21: Sensors says `No sensors found!'
    • Section 4.22: Sensors output is not correct!
    • Section 4.23: What is at I2C address XXX?
    • Section 4.24: Sensors-detect doesn't work at all -
    • Section 4.25: Sensors says Error: Line xxx: zzzzzzz +
    • Section 4.25: Sensors says `Error: Line xxx: zzzzzzz'
    • Section 4.26: Sensors only gives the name, adapter, and algorithm! -
    • Section 4.27: Sensors says ERROR: Can't get xxxxx data! +
    • Section 4.27: Sensors says `ERROR: Can't get xxxxx data!'
    • Section 4.28: Sensors doesn't find any sensors, just eeproms.
    • Section 4.29: Inserting modules hangs my board
    • Section 4.30: Inserting modules slows down my board @@ -866,9 +910,11 @@ Up: Top

      -Next: , + + +Next: , Up: Problems -
      +

      4.1 My fans report exactly half/double their values compared to the BIOS?

      @@ -877,14 +923,14 @@ Up: Problems 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 /etc/sensors.conf: +configuration file /etc/sensors.conf: 
           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
      -

      See doc/fan-divisors in our package for further information. +

      See doc/fan-divisors in our package for further information.

      @@ -892,7 +938,7 @@ configuration file /etc/sensors.conf:

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

      You may need to increase the 'fan divisor'. See doc/fan-divisors +

      You may need to increase the 'fan divisor'. See doc/fan-divisors in our package for further information.

      @@ -900,16 +946,18 @@ in our package for further information.

      4.1.2 I doubled the fan divisor and the fan still reads 7000!

      Believe it or not, doubling the 'fan divisor' will not halve -the fan reading. You have to add a compute line in /etc/sensors.conf. +the fan reading. You have to add a compute line in /etc/sensors.conf. See My fans report exactly half/double their values compared to the BIOS, -and see doc/fan-divisors in our package for further information. +and see doc/fan-divisors in our package for further information.

      -Next: , + + +Next: , Previous: Section 4.1, Up: Problems -
      +

      4.2 Why do my two LM75's report "-48 degrees"?

      @@ -924,10 +972,12 @@ readings.

      -Next: , + + +Next: , Previous: Section 4.2, Up: Problems -
      +

      4.3 Why do I have two Vcore readings, I have only one processor!

      @@ -936,7 +986,7 @@ Up: Problems 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 ignore line. +an ignore line.

      Note that Vcore2 is often the same as Vcore on motherboards which only support one processor. Another possibility is that Vcore2 is not @@ -947,16 +997,18 @@ different.

      -Next: , + + +Next: , Previous: Section 4.3, Up: Problems -
      +

      4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!

      -

      The ALARM indications in sensors are those reported by the -sensor chip itself. They are NOT calculated by sensors. sensors +

      The ALARM indications in sensors are those reported by the +sensor chip itself. They are NOT calculated by sensors. sensors simply reads the ALARM bits and reports them.

      An ALARM will go off when a minimum or maximum limit is crossed. @@ -972,15 +1024,17 @@ value is still out of range. 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 doc/chips and the +See the specific chip documentation in doc/chips and the chip datasheet for more information.

      -Next: , + + +Next: , Previous: Section 4.4, Up: Problems -
      +

      4.5 My voltage readings seem to drift a bit. Is something wrong?

      @@ -996,10 +1050,12 @@ reason to worry.

      -Next: , + + +Next: , Previous: Section 4.5, Up: Problems -
      +

      4.6 Some measurements are way out of range. What happened?

      @@ -1016,14 +1072,14 @@ 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. -

      +

      4.6.1 -5V and -12V readings are way out of range!

      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 -ignore inN lines to /etc/sensors.conf to hide them. +ignore inN lines to /etc/sensors.conf to hide them.

      Another possibility is that these lines are used to monitor different voltages. Only the motherboard manufacturer can tell for sure. Taking @@ -1032,10 +1088,12 @@ hints though.

      -Next: , + + +Next: , Previous: Section 4.6, Up: Problems -
      +

      4.7 What are VID lines? Why is the VID reading wrong?

      @@ -1044,22 +1102,24 @@ Up: Problems 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 ignore vid to /etc/sensors.conf, +If this is the case, add a line ignore vid to /etc/sensors.conf, 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.

      The CPU nominal voltage is computed from VID lines according to a formula that depends on the CPU type. Most chips that report a VID value can be configured to use either VRM 8.2 (for Pentium III) or VRM 9.0 (for Pentium 4 -and Athlon). You chose which one you want through /etc/sensors.conf. -See doc/vid for more information. +and Athlon). You chose which one you want through /etc/sensors.conf. +See doc/vid for more information.

      -Next: , + + +Next: , Previous: Section 4.7, Up: Problems -
      +

      4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?

      @@ -1071,10 +1131,12 @@ at all).

      -Next: , + + +Next: , Previous: Section 4.8, Up: Problems -
      +

      4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?

      @@ -1086,10 +1148,12 @@ while we are waiting for the transaction to finish.

      -Next: , + + +Next: , Previous: Section 4.9, Up: Problems -
      +

      4.10 Can I be alerted when an ALARM occurs?

      @@ -1109,14 +1173,16 @@ might be quite hard to do.

      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 http://www2.lm-sensors.nu/~lm78/useful_addresses.html for addresses. +programs under X, see http://www.lm-sensors.org/wiki/UsefulLinks for addresses.

      -Next: , + + +Next: , Previous: Section 4.10, Up: Problems -
      +

      4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen). Why?

      @@ -1133,10 +1199,12 @@ written to, but lock things up when they are read.

      -Next: , + + +Next: , Previous: Section 4.11, Up: Problems -
      +

      4.12 My BIOS reports a much higher CPU temperature than your modules!

      @@ -1164,45 +1232,51 @@ makes sense.

      -Next: , + + +Next: , Previous: Section 4.12, Up: Problems -
      +
      -

      4.13 I try to read the raw /proc files, but the values are strange?!?

      +

      4.13 I try to read the raw /proc files, but the values are strange?!?

      Remember, these values do not take the configuration file -compute lines in account. This is especially obvious for voltage readings +compute lines in account. This is especially obvious for voltage readings (usually called in? or vin?). Use a program linked to libsensors (like -the provided sensors program) instead. +the provided sensors program) instead.

      -Next: , + + +Next: , Previous: Section 4.13, Up: Problems -
      +

      4.14 How do I set new limits?

      -

      Change the limit values in /etc/sensors.conf and then run -sensors -s. +

      Change the limit values in /etc/sensors.conf and then run +sensors -s.

      4.14.1 I set new limits and it didn't work?

      -

      You forgot to run sensors -s. Put it in a /etc/rc.d/... file +

      You forgot to run sensors -s. Put it in a /etc/rc.d/... file after the modprobe lines to run at startup.

      -Next: , + + +Next: , Previous: Section 4.14, Up: Problems -
      +

      4.15 Some sensors are doubly detected?

      @@ -1215,14 +1289,16 @@ 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 ignore= modprobe parameters it suggests. +run sensors-detect and add the ignore= modprobe parameters it suggests.

      -Next: , + + +Next: , Previous: Section 4.15, Up: Problems -
      +

      4.16 I ran sensors-detect, but now I get very strange readings?!?

      @@ -1237,16 +1313,18 @@ scan the PIIX4.

      -Next: , + + +Next: , Previous: Section 4.16, Up: Problems -
      +

      4.17 Bad readings from particular chips

      See below for some particularly troublesome chips. -Also be sure and check doc/chips/xxxxx for the particular driver. +Also be sure and check doc/chips/xxxxx for the particular driver.

      @@ -1255,7 +1333,7 @@ Also be sure and check doc/chips/xxxxx for the particu

      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 /etc/sensors.conf. Please don't ask us to +to the readings please edit /etc/sensors.conf. Please don't ask us to fix the driver. Ask Asus to release a datasheet.

      @@ -1265,9 +1343,9 @@ fix the driver. Ask Asus to release a datasheet.

      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 /etc/sensors.conf. Please don't ask us to +to the readings please edit /etc/sensors.conf. Please don't ask us to fix the driver. Ask Via to release a better datasheet. -Also, don't forget to modprobe i2c-isa. +Also, don't forget to modprobe i2c-isa.

      @@ -1275,7 +1353,7 @@ Also, don't forget to modprobe i2c-isa.

      The MTP008 has programmable temperature sensor types. If your sensor type does not match the default, you will have to change it. -See doc/chips/mtp008 for details. +See doc/chips/mtp008 for details. Also, MTP008 chips seem to randomly refuse to respond, for unknown reasons. You can see this as 'XX' entries in i2cdump. @@ -1299,9 +1377,9 @@ misidentified. Look on the motherboard (or at http://mbm.livewiredev.com) for a 'Winbond' or Asus chip. Often the real device is an Asus as99127f. If so, the driver can be forced to recognize the as99127f with -force_as99127f=BUS,0x2d where BUS is your i2c bus number. +force_as99127f=BUS,0x2d where BUS is your i2c bus number. Cat /proc/bus/i2c to see a list of bus numbers. -Read the w83781d module documentation (doc/chips/w83781d) +Read the w83781d module documentation (doc/chips/w83781d) for more details.

      @@ -1310,7 +1388,7 @@ for more details.

      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 ignore=1,0x2d or similar option +monitor chip on this board and use the ignore=1,0x2d or similar option to the w83781d module to prevent i2c accesses.

      @@ -1337,10 +1415,12 @@ as an LM80. Figure out what you really have See

      -Next: , + + +Next: , Previous: Section 4.17, Up: Problems -
      +

      4.18 How do I configure two chips (LM87) differently?

      @@ -1349,103 +1429,111 @@ Up: Problems not hooked up in the same way, so they need different defaults. For example, both CPU temperatures go to one LM87. -

      Make two different sections in /etc/sensors.conf as follows: +

      Make two different sections in /etc/sensors.conf as follows: 

           chip "lm87-i2c-*-2c"
          put configuration for the chip at 0x2c here
      chip "lm87-i2c-*-2d"
          put configuration for the chip at 0x2d here
      -

      There is a commented example in sensors.conf.eg which should +

      There is a commented example in sensors.conf.eg which should be helpful.

      -Next: , + + +Next: , Previous: Section 4.18, Up: Problems -
      +
      -

      4.19 Dmesg says Upgrade BIOS! I don't want to!

      +

      4.19 Dmesg says `Upgrade BIOS'! I don't want to!

      -

      If the problem is a PCI device is not present in lspci, the solution +

      If the problem is a PCI device is not present in lspci, the solution is complex. For the ALI M7101 device, there is a solution which uses the -2.4 kernel's hotplug facility. See prog/hotplug in our package. +2.4 kernel's hotplug facility. See prog/hotplug in our package. For other PCI devices, you can try to modify -the m7101 solution in prog/hotplug. +the m7101 solution in prog/hotplug. -

      If dmesg says try force_addr, see below. Other drivers generally do not +

      If dmesg says `try force_addr', see below. Other drivers generally do not support the force_addr parameter. Sorry. Check the documentation -for your driver in doc/[chips,busses] and if we don't support it +for your driver in doc/[chips,busses] and if we don't support it you can send us your request.

      -

      4.19.1 Dmesg says use force_addr=0xaddr! What address do I use?

      +

      4.19.1 Dmesg says `use force_addr=0xaddr'! What address do I use?

      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 -modprobe via686a force_addr=0xADDRESS where ADDRESS +modprobe via686a force_addr=0xADDRESS where ADDRESS is the I/O address. You must select an address that is not in use. -cat /proc/ioports to check (carefully) for conflicts. A high number like +cat /proc/ioports to check (carefully) for conflicts. A high number like 0xf000 is generally safe.

      -Next: , + + +Next: , Previous: Section 4.19, Up: Problems -
      +
      -

      4.20 Sensors says Can't access procfs/sysfs file

      +

      4.20 Sensors says `Can't access procfs/sysfs file'

      • Linux 2.6
          -
        • Did you modprobe i2c_sensor? Check lsmod. -
        • Do you have sysfs support in your kernel and /sys mounted (is /sys there and populated)? -Create /sys with mkdir /sys if needed. Then add the following line to /etc/fstab: +
        • Did you modprobe i2c_sensor? Check lsmod. +
        • Do you have sysfs support in your kernel and /sys mounted (is /sys there and populated)? +Create /sys with mkdir /sys if needed. Then add the following line to /etc/fstab: 
                         sys              /sys             sysfs       default          0   0
          -

          and mount /sys. +

          and mount /sys.

      • Linux 2.4
          -
        • Did you modprobe i2c-proc? Check lsmod. -
        • Do you have procfs support in your kernel and /proc mounted (is /proc there and populated)? -Create /proc with mkdir /proc if needed. Then add the following line to /etc/fstab: +
        • Did you modprobe i2c-proc? Check lsmod. +
        • Do you have procfs support in your kernel and /proc mounted (is /proc there and populated)? +Create /proc with mkdir /proc if needed. Then add the following line to /etc/fstab: 
                         proc             /proc            proc        defaults         0   0
          -

          and mount /proc. +

          and mount /proc.

        -
      • If you did sensors -s, did you run it as root? +
      • If you did sensors -s, did you run it as root?

      -Next: , + + +Next: , Previous: Section 4.20, Up: Problems -
      +
      -

      4.21 Sensors says No sensors found!

      +

      4.21 Sensors says `No sensors found!'

        -
      • Did sensors-detect find sensors? (If not see Sensors-detect doesnt find any sensors) -
      • Did you do what sensors-detect said? -
      • Did you modprobe your sensor modules? -
      • Did you modprobe your I2C adapter modules? -
      • Did you modprobe i2c-isa if you have ISA sensor chips? -
      • Check lsmod. +
      • Did sensors-detect find sensors? (If not see Sensors-detect doesnt find any sensors) +
      • Did you do what sensors-detect said? +
      • Did you modprobe your sensor modules? +
      • Did you modprobe your I2C adapter modules? +
      • Did you modprobe i2c-isa if you have ISA sensor chips? +
      • Check lsmod.

      -Next: , + + +Next: , Previous: Section 4.21, Up: Problems -
      +

      4.22 Sensors output is not correct!

      @@ -1463,23 +1551,25 @@ Up: Problems
    • One particular sensor readings:
      • Maybe it isn't hooked up? - tell 'sensors' to ignore it. See One sensor isnt hooked up on my board. -
      • Maybe it is hooked up differently on your motherboard? - adjust sensors.conf calculation. +
      • Maybe it is hooked up differently on your motherboard? - adjust sensors.conf calculation.

    -Next: , + + +Next: , Previous: Section 4.22, Up: Problems -
    +

    4.23 What is at I2C address XXX?

    -

    In general, we don't know. Start by running sensors-detect. -If it doesn't recognize it, try running i2cdump. A partial list -of manufacturers' IDs are at the bottom of doc/chips/SUMMARY. +

    In general, we don't know. Start by running sensors-detect. +If it doesn't recognize it, try running i2cdump. A partial list +of manufacturers' IDs are at the bottom of doc/chips/SUMMARY.

    @@ -1488,7 +1578,7 @@ of manufacturers' IDs are at the bottom of doc/chips/SUMMARY<

    A clock chip. Often, accessing these clock chips in the wrong way will instantly crash your computer. Sensors-detect carefully avoids these chips. If you really really want to play with your clock -chip you can look at kernel/chips/icspll.c in our package. But we +chip you can look at kernel/chips/icspll.c in our package. But we do not recommend it. You have been warned.

    @@ -1496,8 +1586,8 @@ do not recommend it. You have been warned.

    4.23.2 What is at I2C addresses 0x50 - 0x57?

    EEPROMs on your SDRAM DIMMs. Load the eeprom module to -look at some basic data in sensors or use the program -prog/eeprom/decode-dimms.pl to get more information than you ever wanted. +look at some basic data in sensors or use the program +prog/eeprom/decode-dimms.pl to get more information than you ever wanted.

    @@ -1507,17 +1597,19 @@ look at some basic data in sensors or use the progr at addresses 0x50 - 0x57. They are the 'software write-protect' registers of the SDRAM Serial Presence Detect EEPROMs. If you try and -do a i2cdump on them to read the location, you won't get anything, +do a i2cdump 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.

    -Next: , + + +Next: , Previous: Section 4.23, Up: Problems -
    +

    4.24 Sensors-detect doesn't work at all

    @@ -1535,10 +1627,10 @@ was not loaded and you did not run sensors-detect as root.

    4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"

    -

    Your /dev/i2c-0, /dev/i2c0, or /dev/i2c/0 files do not exist -or you did not run sensors-detect as root. -Run the script prog/mkdev/mkdev.sh to create the /dev/i2c-x files. -Run devfs in the kernel to get the /dev/i2c/x files. +

    Your /dev/i2c-0, /dev/i2c0, or /dev/i2c/0 files do not exist +or you did not run sensors-detect as root. +Run the script prog/mkdev/mkdev.sh to create the /dev/i2c-x files. +Run devfs in the kernel to get the /dev/i2c/x files.

    @@ -1560,83 +1652,91 @@ Run devfs in the kernel to get the Newest Driver Status web page to +Newest Driver Status web page to see if support has been added for your chip in a later release or in CVS.

    -Next: , + + +Next: , Previous: Section 4.24, Up: Problems -
    +
    -

    4.25 Sensors says Error: Line xxx: zzzzzzz

    +

    4.25 Sensors says `Error: Line xxx: zzzzzzz'

    These are errors from the libsensors library in -reading the /etc/sensors.conf configuration file. Go to that line +reading the /etc/sensors.conf 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.

    -Next: , + + +Next: , Previous: Section 4.25, Up: Problems -
    +

    4.26 Sensors only gives the name, adapter, and algorithm for my chip

    -

    If sensors only says this, for example, and doesn't +

    If sensors only says this, for example, and doesn't provide any actual data at all: 

         it87-isa-0290
      Adapter: ISA adapter
      Algorithm: ISA algorithm
    -

    Your chip is not currently supported by sensors and so all it +

    Your chip is not currently supported by sensors and so all it does is print out that information. Get the latest release -and be sure you are running the sensors program it installed -and not some older sensors. +and be sure you are running the sensors program it installed +and not some older sensors.

    -Next: , + + +Next: , Previous: Section 4.26, Up: Problems -
    +
    -

    4.27 Sensors says ERROR: Can't get xxxxx data!

    +

    4.27 Sensors says `ERROR: Can't get xxxxx data!'

    • (Linux 2.6) Make sure you are using one of the recommended kernel/lm_sensors combination. -
    • You have a libsensors/sensors mismatch. -sensors is unable to -get a data entry from libsensors. You probably have an -old libsensors in your /etc/ld.so.conf path. -Make sure you did (as root) a make install (Linux 2.4) or -make user_install (Linux 2.6) followed by a ldconfig. -Then check the output of ldconfig -v | grep libsensors to -verify that there is only ONE libsensors entry and that it matches -the libsensors that was built in the lib/ directory in lm_sensors2. +
    • You have a libsensors/sensors mismatch. +sensors is unable to +get a data entry from libsensors. You probably have an +old libsensors in your /etc/ld.so.conf path. +Make sure you did (as root) a make install (Linux 2.4) or +make user_install (Linux 2.6) followed by a ldconfig. +Then check the output of ldconfig -v | grep libsensors to +verify that there is only ONE libsensors entry and that it matches +the libsensors that was built in the lib/ directory in lm_sensors2.

    -Next: , + + +Next: , Previous: Section 4.27, Up: Problems -
    +

    4.28 Sensors doesn't find any sensors, just eeproms.

    -

    See Sensors-detect doesnt work at all, if sensors-detect failed to find any sensors. +

    See Sensors-detect doesnt work at all, if sensors-detect failed to find any sensors. -

    If sensors-detect did find sensors, did you insert your modules? For chips on the ISA +

    If sensors-detect did find sensors, did you insert your modules? For chips on the ISA bus, did you insert i2c-isa?

    See What to do if a module wont insert, if the modules didn't insert, @@ -1644,10 +1744,12 @@ also Sensors says No sensors found.

    -Next: , + + +Next: , Previous: Section 4.28, Up: Problems -
    +

    4.29 Inserting modules hangs my board

    @@ -1656,17 +1758,19 @@ Up: Problems
    1. Bus driver problems. Insert the bus driver first, before you have inserted any chip drivers, to verify.
    2. Wrong chip driver. Verify that you have a chip supported by the chip driver, see What chips are on motherboard XYZ. -
    3. The chip driver is reinitializing the chip, which undoes critical initialization done by the BIOS. Try the parameter init=0 for the w83781d driver; this is the only driver supporting this parameter. -
    4. Some chips on the bus don't like to be probed at all. After inserting the bus driver (but not the chip drivers), run i2cdetect on the bus, then i2cdump on each address responding to i2cdetect. This may find the culprit. Do not i2cdump address 0x69, the clock chip. -
    5. 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 modprobe ignore_range=0,0x00,0x28,0,0x2a,0x7f to prevent access to other addresses. (init=0 also req'd for the Tyan 2688). +
    6. The chip driver is reinitializing the chip, which undoes critical initialization done by the BIOS. Try the parameter init=0 for the w83781d driver; this is the only driver supporting this parameter. +
    7. Some chips on the bus don't like to be probed at all. After inserting the bus driver (but not the chip drivers), run i2cdetect on the bus, then i2cdump on each address responding to i2cdetect. This may find the culprit. Do not i2cdump address 0x69, the clock chip. +
    8. 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 modprobe ignore_range=0,0x00,0x28,0,0x2a,0x7f to prevent access to other addresses. (init=0 also req'd for the Tyan 2688).

    -Next: , + + +Next: , Previous: Section 4.29, Up: Problems -
    +

    4.30 Inserting modules slows down my board

    @@ -1675,14 +1779,16 @@ Up: Problems 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 /etc/sensors.conf and run sensors -s. +the new limits in /etc/sensors.conf and run sensors -s.

    -Next: , + + +Next: , Previous: Section 4.30, Up: Problems -
    +

    4.31 Problems on particular motherboards

    @@ -1693,7 +1799,7 @@ Up: Problems

    4.31.1 Asus P4B

    -

    See prog/hotplug/README.p4b if your SMBus master is not found. +

    See prog/hotplug/README.p4b if your SMBus master is not found.

    @@ -1716,21 +1822,25 @@ Also Inserting modules hangs my board.

    -Next: , + + +Next: , Previous: Section 4.31, Up: Problems -
    +

    4.32 Problems on particular systems

    -

    For IBM systems, see README.thinkpad. +

    For IBM systems, see README.thinkpad.

    -Previous: Section 4.32, + + +Previous: Section 4.32, Up: Problems -
    +

    4.33 Problems on 2.6 kernels

    @@ -1760,22 +1870,23 @@ libsensors grab the relevant sensors information in /sys. In particular: (I2C/SMBus, ISA or other);
  • libsensors will no more list non-hardware monitoring chips. - This explains why EEPROMs are no more displayed by sensors: + This explains why EEPROMs are no more displayed by sensors: 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.

    Note that you can still obtain information about your EEPROMs by using -the dedicated perl scripts in prog/eeprom: ddcmon, -decode-dimms.pl, decode-edid.pl and -decode-vaio.pl. +the dedicated perl scripts in prog/eeprom: ddcmon, +decode-dimms.pl, decode-edid.pl and +decode-vaio.pl.

    -Next: , + +Next: , Previous: Problems, Up: Top -
    +

    5 How to Ask for Help

    @@ -1794,9 +1905,11 @@ Up: Top

    -Next: , + + +Next: , Up: Help -
    +

    5.1 What to send us when asking for help

    @@ -1807,8 +1920,7 @@ and not the individual authors, unless you have something private to say.

    Instead of using email, you can also use the web-based support -area, at -http://www.lm-sensors.org/wiki/FeedbackAndSupport. You will be helped +area, at http://www.lm-sensors.org/wiki/FeedbackAndSupport. 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. @@ -1816,24 +1928,24 @@ emailed automatically when your question has been answered.

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

      -Next: , + + +Next: , Previous: Section 5.1, Up: Help -
      +

      5.2 What to do if a module won't insert?

      -

      Did you use modprobe instead of insmod??? Don't use insmod. +

      Did you use modprobe instead of insmod??? Don't use insmod. -

      Were there unresolved symbols? Did you run depmod -a? Run -depmod -a -e to see where the symbol problem is. +

      Were there unresolved symbols? Did you run depmod -a? Run +depmod -a -e to see where the symbol problem is. -

      ALWAYS inspect the output of dmesg. That's where the error -messages come out!!! Don't rely on the generic message from modprobe. +

      ALWAYS inspect the output of dmesg. That's where the error +messages come out!!! Don't rely on the generic message from modprobe. If you still can't figure it out, send us the information listed above.

      -Next: , + + +Next: , Previous: Section 5.2, Up: Help -
      +

      5.3 What to do if it inserts, but nothing happens?

      -

      For an ISA sensor chip, did you also modprobe i2c-isa? It must be inserted. +

      For an ISA sensor chip, did you also modprobe i2c-isa? It must be inserted. -

      For an I2C sensor chip, did you also modprobe i2c-xxx where xxx is your +

      For an I2C sensor chip, did you also modprobe i2c-xxx where xxx is your I2C bus adapter? It must be inserted. -

      Always inspect the output of dmesg. That's where the error +

      Always inspect the output of dmesg. That's where the error messages come out. If you still can't figure it out, send us the information listed above.

      -Next: , + + +Next: , Previous: Section 5.3, Up: Help -
      +

      5.4 What to do if I read only bogus information?

      @@ -1898,10 +2016,12 @@ please send us the usual information (see Help)

      -Next: , + + +Next: , Previous: Section 5.4, Up: Help -
      +

      5.5 What to do if you have other problems?

      @@ -1910,10 +2030,12 @@ Up: Help

      -Next: , + + +Next: , Previous: Section 5.5, Up: Help -
      +

      5.6 What if it just works like a charm?

      @@ -1923,10 +2045,12 @@ detected chip type. That way, we have some positive feedback, too!

      -Next: , + + +Next: , Previous: Section 5.6, Up: Help -
      +

      5.7 How do I update a ticket?

      @@ -1938,10 +2062,12 @@ follow-up information, email us instead. Thanks.

      -Next: , + + +Next: , Previous: Section 5.7, Up: Help -
      +

      5.8 How do I follow up on a ticket?

      @@ -1951,9 +2077,11 @@ and reference your ticket number in the subject.

      -Previous: Section 5.8, + + +Previous: Section 5.8, Up: Help -
      +

      5.9 Why did you decide not to support undocumented chips?

      @@ -2026,17 +2154,18 @@ driver, we will apply it. This generic code is unlikely to cause trouble.

      -Next: , + +Next: , Previous: Help, Up: Top -
      +

      6 How to Contribute

      • Section 6.1: How to write a driver -
      • Section 6.2: How to get CVS access +
      • Section 6.2: How to get SVN access
      • Section 6.3: How to donate hardware to the project
      • Section 6.4: How to join the project mailing list
      • Section 6.5: How to access mailing list archives @@ -2047,52 +2176,56 @@ Up: Top

        -Next: , + + +Next: , Up: Contribute -
        +

        6.1 How to write a driver

        -

        See doc/developers/new_drivers in our package for instructions. +

        See doc/developers/new_drivers in our package for instructions.

        -Next: , + + +Next: , Previous: Section 6.1, Up: Contribute -
        +
        -

        6.2 How to get CVS access

        +

        6.2 How to get SVN access

        -

        For anonymous CVS read access, see the instructions on our -download page. -Alternatively, nightly snapshots -of the CVS repositories are available. +

        For anonymous SVN read access, see the instructions on our +download page. -

        For write access, run the script doc/developers/genpasswd.pl in -our package and follow the instructions. Let us know what part -of the package you would like to work on. +

        For write access, please contact us.

        -Next: , + + +Next: , Previous: Section 6.2, Up: Contribute -
        +

        6.3 How to donate hardware to the project

        -

        Contact us. +

        Contact us.

        -Next: , + + +Next: , Previous: Section 6.3, Up: Contribute -
        +

        6.4 How to join the project mailing lists

        @@ -2108,10 +2241,12 @@ for watching the changes made to the CVS repositories. This list is read-only.

        -Next: , + + +Next: , Previous: Section 6.4, Up: Contribute -
        +

        6.5 How to access mailing list archives

        @@ -2134,25 +2269,29 @@ It contains messages from October 28, 2001 through May 16, 2005.

        -Next: , + + +Next: , Previous: Section 6.5, Up: Contribute -
        +

        6.6 How to submit a patch

        Check out the latest from CVS, then copy the directory to another directory, and make your changes. Generate the diff with -diff -u2 -r DIR1 DIR2. Or you can generate the diff in CVS with -cvs diff -u2. Send us the patch in an email and tell us what it does. +diff -u2 -r DIR1 DIR2. Or you can generate the diff in CVS with +cvs diff -u2. Send us the patch in an email and tell us what it does.

        -Next: , + + +Next: , Previous: Section 6.6, Up: Contribute -
        +

        6.7 How to REALLY help

        @@ -2172,9 +2311,11 @@ and we'll help you help us.

        -Previous: Section 6.7, + + +Previous: Section 6.7, Up: Contribute -
        +

        6.8 How to get release announcements

        @@ -2187,9 +2328,10 @@ will email you announcement.

        -Previous: Contribute, + +Previous: Contribute, Up: Top -
        +

        Appendix A Revision History of This Document

        diff --git a/doc/lm_sensors-FAQ.texi b/doc/lm_sensors-FAQ.texi index f8568e99..76ee4e54 100644 --- a/doc/lm_sensors-FAQ.texi +++ b/doc/lm_sensors-FAQ.texi @@ -118,7 +118,7 @@ of sensor chips. Their websites are: @item @uref{http://www.national.com} @end itemize -Please see the file @uref{http://www2.lm-sensors.nu/~lm78/useful_addresses.html} +Please see the file @uref{http://www.lm-sensors.org/wiki/UsefulLinks} for links to other companies' websites. @@ -318,8 +318,8 @@ If that doesn't work: @item Look at your motherboard. @item Check the manufacturer's website or ask their support @item Check the @uref{http://mbm.livewiredev.com/, Motherboard Monitor} website and the -@uref{http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/useful_addresses.html, "links"} -page on @uref{http://www2.lm-sensors.nu/~lm78/, our website} some good cross-references. +@uref{http://www.lm-sensors.org/wiki/UsefulLinks, "links"} +page on @uref{http://www.lm-sensors.org, our website} some good cross-references. @end enumerate @@ -335,16 +335,16 @@ We don't support boards, we support chips. @xref{Section 3.2.1, What chips are o This we have good answers for. @itemize @item Sorted by Manufacturer: @file{README} -@item Sorted by Manufacturer: @uref{http://www2.lm-sensors.nu/~lm78/supported.html} +@item Sorted by Manufacturer: @uref{http://www.lm-sensors.org/wiki/SupportedDevices} @item Sorted by Sensor Driver: @file{doc/chips/SUMMARY} -@item Newest Driver Status: @uref{http://www2.lm-sensors.nu/~lm78/newdrivers.html} +@item Newest Driver Status: @uref{http://www.lm-sensors.org/wiki/NewDrivers} @end itemize @anchor{Section 3.2.4} @subsection Anybody working on a driver for chip XYZ? -Newest Driver Status: @uref{http://www2.lm-sensors.nu/~lm78/newdrivers.html} +Newest Driver Status: @uref{http://www.lm-sensors.org/wiki/NewDrivers} @node Section 3.3, Section 3.4, Section 3.2, Installation @@ -759,7 +759,7 @@ might be quite hard to do. 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 @uref{http://www2.lm-sensors.nu/~lm78/useful_addresses.html} for addresses. +programs under X, see @uref{http://www.lm-sensors.org/wiki/UsefulLinks} for addresses. @node Section 4.11, Section 4.12, Section 4.10, Problems @@ -1131,7 +1131,7 @@ But in any case you should figure out what is on the board: @end enumerate When you know what chips you have, check the -@uref{http://www2.lm-sensors.nu/~lm78/newdrivers.html, Newest Driver Status} web page to +@uref{http://www.lm-sensors.org/wiki/NewDrivers, Newest Driver Status} web page to see if support has been added for your chip in a later release or in CVS. @@ -1490,7 +1490,7 @@ driver, we will apply it. This generic code is unlikely to cause trouble. @menu * Section 6.1:: How to write a driver -* Section 6.2:: How to get CVS access +* Section 6.2:: How to get SVN access * Section 6.3:: How to donate hardware to the project * Section 6.4:: How to join the project mailing list * Section 6.5:: How to access mailing list archives @@ -1507,22 +1507,18 @@ See @file{doc/developers/new_drivers} in our package for instructions. @node Section 6.2, Section 6.3, Section 6.1, Contribute -@section How to get CVS access +@section How to get SVN access -For anonymous CVS read access, see the instructions on our -@uref{http://www2.lm-sensors.nu/~lm78/download.html#cvs, download page}. -Alternatively, @uref{http://www2.lm-sensors.nu/~lm78/download.html#snapshots, nightly snapshots} -of the CVS repositories are available. +For anonymous SVN read access, see the instructions on our +@uref{http://www.lm-sensors.org/wiki/Download, download page}. -For write access, run the script @command{doc/developers/genpasswd.pl} in -our package and follow the instructions. Let us know what part -of the package you would like to work on. +For write access, please contact us. @node Section 6.3, Section 6.4, Section 6.2, Contribute @section How to donate hardware to the project -@uref{http://www2.lm-sensors.nu/~lm78/author.html#contact, Contact us}. +@uref{http://www.lm-sensors.org/wiki/FeedbackAndSupport, Contact us}. @node Section 6.4, Section 6.5, Section 6.3, Contribute diff --git a/kernel/busses/i2c-sis645.c b/kernel/busses/i2c-sis645.c index f3762f82..52916cf8 100644 --- a/kernel/busses/i2c-sis645.c +++ b/kernel/busses/i2c-sis645.c @@ -26,8 +26,8 @@ The register definitions are based on the SiS630. The method for *finding* the registers is based on trial and error. - A history of changes to this file is available by anonymous CVS: - http://www2.lm-sensors.nu/~lm78/download.html + A history of changes to this file is available by SVN: + http://www.lm-sensors.org/wiki/Download */ /* 25th March 2004 diff --git a/prog/detect/sensors-detect b/prog/detect/sensors-detect index 1d95fade..98e76caa 100755 --- a/prog/detect/sensors-detect +++ b/prog/detect/sensors-detect @@ -5417,8 +5417,8 @@ sub main print "\n Sorry, no chips were detected.\n", " Either your sensors are not supported, or they are\n", " connected to an I2C bus adapter that we do not support.\n", - " See doc/FAQ, doc/lm_sensors-FAQ.html, or\n", - " http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/lm_sensors-FAQ.html\n", + " See doc/FAQ, doc/lm_sensors-FAQ.html, and\n", + " http://www.lm-sensors.org/wiki/FAQ\n", " (FAQ #4.24.3) for further information.\n", " If you find out what chips are on your board, see\n", " http://www.lm-sensors.org/wiki/NewDrivers for driver status.\n"; diff --git a/prog/pwm/fancontrol b/prog/pwm/fancontrol index 0d242d0a..d2c098ac 100755 --- a/prog/pwm/fancontrol +++ b/prog/pwm/fancontrol @@ -15,7 +15,7 @@ # # The latest version of this script is available at: # http://www.hdev.de/fancontrol/fancontrol.html -# or in the CVS version of lm_sensors +# or in the SVN version of lm_sensors # # For configuration instructions and warnings please see fancontrol.txt, which # can be found in the doc/ directory or at the website mentioned above. diff --git a/version.h b/version.h index e413bf15..7021e8e7 100644 --- a/version.h +++ b/version.h @@ -1,2 +1,2 @@ #define LM_DATE "2006?????" -#define LM_VERSION "2.10.0-CVS" +#define LM_VERSION "2.10.0-SVN"