Re: Using lm-sensors
The i2c package that's standard in the kernel is (was?) missing some
things. I've always downloaded the latest i2c package and patched the
kernel. I did this on my potato box and its working like a charm.
Mike
> I'm trying to use lm-sensors, so far with no luck. The
Readme.Debian
> is a bit unclear to me. It says:
>
> To use lm-sensors, you need the lm-sensors module package and an
i2c module
> package installed. You will probably need to build the modules
packages
> from source, using the lm-sensors-source and i2c-source packages.
If you
> have a 2.4 kernel or a recent 2.2 kernel, you can instead use the
kernel's
> new built-in i2c support -- just enable it in the kernel config.
>
>
> Questions:
>
> I have a 2.4 kernel with i2c enabled.
> Should I be able to apt-get install lm-sensors and have it work?
> How do I know if I need to build from source?
> What am I doing wrong? :)
>
> Here's some console logs:
> ----------------------------------------------------------
> wheat:/usr/local/rootlog# sensors-detect
> This program will help you to determine which I2C/SMBus modules
you need to
> load to use lm_sensors most effectively.
> You need to have installed lm-sensors modules before you can use
> some functions of this utility.
> Also, you need to be `root', or at least have access to
> the /dev/i2c[-/]* files for some things.
> If you have patched your kernel and have some drivers built-in you
can
> safely answer NO if asked to load some modules. In this case,
things may
> seem a bit confusing, but they will still work.
>
> IF THIS IS AN IBM THINKPAD, PRESS CTRL-C NOW!
> IBM Thinkpads have a severely broken i2c/SMBus implementation,
just scanning
> the bus will break your thinkpad forever!
>
> We can start with probing for (PCI) I2C or SMBus adapters.
> You do not need any special privileges for this.
> Do you want to probe now? (YES/no):
> Probing for PCI bus adapters...
> Use driver `i2c-amd756' for device 00:07.3: AMD-756 Athlon ACPI
> Use driver `i2c-matroxfb' for device 01:05.0: MGA G200 AGP
> Probe succesfully concluded.
>
> We will now try to load each adapter module in turn.
> Load `i2c-amd756' (say NO if built into your kernel)? (YES/no):
> modprobe: Can't locate module i2c-amd756
> Loading failed ()... skipping.
> Load `i2c-matroxfb' (say NO if built into your kernel)? (YES/no):
> modprobe: Can't locate module i2c-matroxfb
> Loading failed ()... skipping.
> Do you now want to be prompted for non-detectable adapters?
(yes/NO):
> To continue, we need module `i2c-dev' to be loaded.
> If it is built-in into your kernel, you can safely skip this.
> i2c-dev is not loaded. Do you want to load it now? (YES/no):
> Module loaded succesfully.
>
>
>
> We are now going to do the adapter probings. Some adapters may hang
halfway
> through; we can't really help that. Also, some chips will be double
detected;
> we choose the one with the highest confidence value in that case.
> If you found that the adapter hung after probing a certain
address, you can
> specify that address to remain unprobed. If you have a PIIX4, that
often
> includes addresses 0x69 and/or 0x6a.
>
> Some chips are also accessible through the ISA bus. ISA probes are
> typically a bit more dangerous, as we have to write to I/O ports to
do
> this. Do you want to scan the ISA bus? (YES/no):
> Probing for `National Semiconductor LM78'
> Trying address 0x0290... Failed!
> Probing for `National Semiconductor LM78-J'
> Trying address 0x0290... Failed!
> Probing for `National Semiconductor LM79'
> Trying address 0x0290... Failed!
> Probing for `Winbond W83781D'
> Trying address 0x0290... Failed!
> Probing for `Winbond W83782D'
> Trying address 0x0290... Failed!
> Probing for `Winbond W83627HF'
> Trying address 0x0290... Failed!
> Probing for `Winbond W83697HF'
> Trying address 0x0290... Failed!
> Probing for `Silicon Integrated Systems SIS5595'
> Trying general detect... Failed!
> Probing for `VIA Technologies VT 82C686 Integrated Sensors'
> Trying general detect... Failed!
> Probing for `ITE IT8705F / IT8712F / SiS 950'
> Trying address 0x0290... Failed!
>
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
>
>
> I will now generate the commands needed to load the I2C modules.
> Sometimes, a chip is available both through the ISA bus and an I2C
bus.
> ISA bus access is faster, but you need to load an additional driver
module
> for it. If you have the choice, do you want to use the ISA bus or
the
> I2C/SMBus (ISA/smbus)?
>
> WARNING! If you have some things built into your kernel, the
> below list will contain too many modules. Skip the appropriate ones!
> To load everything that is needed, edit /etc/modules and add the
modules
> listed here to it:
>
> #----cut here----
> # I2C adapter drivers
> # I2C chip drivers
> #----cut here----
>
> Then, run /etc/init.d/modutils
>
>
> To make the sensors modules behave correctly, add these lines to
> /etc/modutils/local and run update-modules:
>
> #----cut here----
> # I2C module options
> alias char-major-89 i2c-dev
> #----cut here----
>
> # I added the alias to /etc/modutils/alias and ran update-modules
> wheat:/usr/local/rootlog# lsmod
> Module Size Used by
> i2c-dev 3808 0 (unused)
> i2c-core 13168 0 [i2c-dev]
> # etc
>
> wheat:/usr/local/rootlog# sensors
> Can't access /proc file
> /proc/sys/dev/sensors/chips or /proc/bus/i2c unreadable;
> Make sure you have done 'modprobe i2c-proc'!
> wheat:/usr/local/rootlog# modprobe i2c-proc
> modprobe: Can't locate module i2c-proc
> wheat:/usr/local/rootlog# cd /lib/modules/
> wheat:/lib/modules# ls
> 2.4.6
> wheat:/lib/modules# find . -name '*i2c*'
> ./2.4.6/kernel/drivers/i2c
> ./2.4.6/kernel/drivers/i2c/i2c-algo-bit.o
> ./2.4.6/kernel/drivers/i2c/i2c-core.o
> ./2.4.6/kernel/drivers/i2c/i2c-dev.o
> ./2.4.6/kernel/drivers/i2c/i2c-algo-pcf.o
> w
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>
>
>
Reply to: