|
Home > Archive > Red Hat General > March 2004 > lm_sensors and i2c
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
lm_sensors and i2c
|
|
| ElNoHabido 2004-03-20, 10:38 am |
| Hi guys, I need some help to make gkrellm show temperatures and voltages.
I see that Fedora Core have lm_sensors-2.8.1 installed but I donīt know if
it has i2c support. My kernel is 2.4.22.
I downloaded this two files from the lm_sensors offical site:
- i2c-2.8.4.tar.gz
- lm_sensors-2.8.5.tar.gz
I read the readmes but Iīm confuse about what to do. The lm_sensors readme
says I have 3 way to install, one of those is to patch the kernel and the
others is to install as a modules....I donīt know what to do :-?
Could you, please, give me a step by step to install it?
--
Linux Fedora Core 1 Yarrow - KDE
Athlon XP 2400+
MSI K7N2G - nForce2
ElNoHabido.
| |
| Alexander Dalloz 2004-03-20, 2:37 pm |
| On Sat, 20 Mar 2004 01:03:05 -0500 ElNoHabido wrote:
> Hi guys, I need some help to make gkrellm show temperatures and voltages.
>
> I see that Fedora Core have lm_sensors-2.8.1 installed but I donīt know if
> it has i2c support. My kernel is 2.4.22.
So why did you not check the kernel modules directory?
> Could you, please, give me a step by step to install it?
No need for a self compilation. The FC1 kernel has i2c support. Run
sensors-detect as root.
Alexander
--
Alexander Dalloz | Enger, Germany
PGP key valid: made 13.07.1999
PGP fingerprint: 2307 88FD 2D41 038E 7416 14CD E197 6E88 ED69 5653
| |
| ElNoHabido 2004-03-20, 2:37 pm |
| > No need for a self compilation. The FC1 kernel has i2c support. Run
> sensors-detect as root.
I run $./sensors-detect into /usr/sbin as a root and I got this:
******************************
BIOS vendor (ACPI): Nvidia
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): yes
Probing for PCI bus adapters...
Use driver `i2c-nforce2' for device 00:01.1: nVidia Corporation nForce2
SMBus (MCP)
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-nforce2' (say NO if built into your kernel)? (YES/no): yes
Can't exec "modprobe": No existe el fichero o el directorio at
../sensors-detect line 3896, <STDIN> line 2.
Loading failed... skipping.
Do you now want to be prompted for non-detectable adapters? (yes/NO): yes
Load `i2c-elektor' (say NO if built into your kernel)? (YES/no): no
Load `i2c-elv' (say NO if built into your kernel)? (YES/no): no
Load `i2c-philips-par' (say NO if built into your kernel)? (YES/no): no
Load `i2c-velleman' (say NO if built into your kernel)? (YES/no): 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): yes
Can't exec "modprobe": No existe el fichero o el directorio at
../sensors-detect line 3937, <STDIN> line 8.
Loading failed, expect problems later on.
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. That often
includes address 0x69 (clock chip).
Couldn't open /proc/bus/i2c?!? at ./sensors-detect line 3964, <STDIN>
line 8.
**************************
I don't know exactly what it means but I understand that it didn't find
any modules to load.....
What else can you advise me to do...
Thanks.
| |
| Alexander Dalloz 2004-03-20, 2:37 pm |
| On Sat, 20 Mar 2004 12:43:33 -0500 ElNoHabido wrote:
>
>
> I run $./sensors-detect into /usr/sbin as a root and I got this:
> i2c-dev is not loaded. Do you want to load it now? (YES/no): yes
> Can't exec "modprobe": No existe el fichero o el directorio at
> ./sensors-detect line 3937, <STDIN> line 8.
> Loading failed, expect problems later on.
>
> 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. That often
> includes address 0x69 (clock chip).
> Couldn't open /proc/bus/i2c?!? at ./sensors-detect line 3964, <STDIN>
> line 8.
>
> I don't know exactly what it means but I understand that it didn't find
> any modules to load.....
>
> What else can you advise me to do...
>
> Thanks.
You certainly got root by using "su" instead of "su -"! RTFM
Alexander
--
Alexander Dalloz | Enger, Germany
PGP key valid: made 13.07.1999
PGP fingerprint: 2307 88FD 2D41 038E 7416 14CD E197 6E88 ED69 5653
| |
| ElNoHabido 2004-03-20, 2:37 pm |
|
> You certainly got root by using "su" instead of "su -"! RTFM
Yes, look this:
**************************
[root@localhost sbin]# ./sensors-detect
-----
BIOS vendor (ACPI): Nvidia
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): y
Probing for PCI bus adapters...
Use driver `i2c-nforce2' for device 00:01.1: nVidia Corporation nForce2
SMBus (MCP)
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-nforce2' (say NO if built into your kernel)? (YES/no): y
Can't exec "modprobe": No existe el fichero o el directorio at
../sensors-detect line 3896, <STDIN> line 2.
Loading failed... skipping.
Do you now want to be prompted for non-detectable adapters? (yes/NO): y
Load `i2c-elektor' (say NO if built into your kernel)? (YES/no): y
Can't exec "modprobe": No existe el fichero o el directorio at
../sensors-detect line 3916, <STDIN> line 4.
Loading failed... skipping.
Load `i2c-elv' (say NO if built into your kernel)? (YES/no): y
Can't exec "modprobe": No existe el fichero o el directorio at
../sensors-detect line 3916, <STDIN> line 5.
Loading failed... skipping.
Load `i2c-philips-par' (say NO if built into your kernel)? (YES/no): y
Can't exec "modprobe": No existe el fichero o el directorio at
../sensors-detect line 3916, <STDIN> line 6.
Loading failed... skipping.
Load `i2c-velleman' (say NO if built into your kernel)? (YES/no): y
Can't exec "modprobe": No existe el fichero o el directorio at
../sensors-detect line 3916, <STDIN> line 7.
Loading failed... skipping.
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): y
Can't exec "modprobe": No existe el fichero o el directorio at
../sensors-detect line 3937, <STDIN> line 8.
Loading failed, expect problems later on.
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. That often
includes address 0x69 (clock chip).
Couldn't open /proc/bus/i2c?!? at ./sensors-detect line 3964, <STDIN>
line 8.
*************************
perhaps I need to anwer No/Yes in some question....
What do you think about it?
| |
| ElNoHabido 2004-03-21, 12:34 pm |
| >>>You certainly got root by using "su" instead of "su -"! RTFM
My kernel modules path is /lib/modules/2.4.22-1.2115.nptl/kernel but I
can not find i2c-nforce2 driver or sensor.
In $PATH appear:
/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/restringido/bin
If I run #lsmod I get this entries about i2c:
i2c-dev 5828 0 (unused)
i2c-philips-par 3356 0 (unused)
i2c-algo-bit 8776 0 [i2c-philips-par]
i2c-core 19172 0 [i2c-dev i2c-algo-bit]
I run it again getting this as a result(./sensors-detect from /usr/sbin):
*******************************
BIOS vendor (ACPI): Nvidia
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): y
Probing for PCI bus adapters...
Use driver `i2c-nforce2' for device 00:01.1: nVidia Corporation nForce2
SMBus (MCP)
Probe succesfully concluded.
*******************************
We will now try to load each adapter module in turn.
Load `i2c-nforce2' (say NO if built into your kernel)? (YES/no): y
modprobe: Can't locate module i2c-nforce2
Loading failed... skipping.
*******************************
Do you now want to be prompted for non-detectable adapters? (yes/NO): n
*******************************
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): y
Module loaded succesfully.
*******************************
We are now going to do the adapter probings.....
......
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): y
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... Success!
(confidence 8, driver `w83781d')
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!
*******************************
Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. Do you want to scan for Super I/O sensors? (YES/no): y
Probing for `SMSC 47M10x Super IO Fan Sensors'
Failed!
Probing for `SMSC 47M14x Super IO Fan Sensors'
Failed!
Probing for `VT1211 Super IO Sensors'
Failed!
Probing for `Winbond W83627HF Super IO Sensors'
Failed!
Probing for `Winbond W83627THF Super IO Sensors'
Failed!
Probing for `Winbond W83697HF Super IO Sensors'
Failed!
*******************************
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83781d' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83627HF' (confidence: 8)
*******************************
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)? smbus
To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe w83781d
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----
*******************************
WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.
Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): y
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
*******************************
This is all I got but I do not see anything about i2c-nforce2 as I expected.
I think is something wrong, Alexander, because reading the docs it
refers /usr/local/sbin and it also says this kernel have support to
nforce2 chipset.
I am a newbie in Linux so excuse me if I asking easy questions or if I
getting confuse unnecesarily.
Thanks in advace, Alex.
| |
| Alexander Dalloz 2004-03-21, 1:34 pm |
| On Sun, 21 Mar 2004 12:08:32 -0500 ElNoHabido wrote:
>
>
> My kernel modules path is /lib/modules/2.4.22-1.2115.nptl/kernel but I
> can not find i2c-nforce2 driver or sensor.
>
> In $PATH appear:
> /usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/restringido/bin
Obviously only the $PATH of the normal user, I spoke about the root $PATH
when running sensors-detect!
> This is all I got but I do not see anything about i2c-nforce2 as I
> expected.
>
> I think is something wrong, Alexander, because reading the docs it
> refers /usr/local/sbin and it also says this kernel have support to
> nforce2 chipset.
>
> I am a newbie in Linux so excuse me if I asking easy questions or if I
> getting confuse unnecesarily.
>
> Thanks in advace, Alex.
$ locate nforce2
/usr/share/doc/lm_sensors-2.8.1/doc/busses/i2c-nforce2
The module is there. By the way, upgrade your kernel to latest .2174 as
yours is vulnerable!
Alexander
--
Alexander Dalloz | Enger, Germany
PGP key valid: made 13.07.1999
PGP fingerprint: 2307 88FD 2D41 038E 7416 14CD E197 6E88 ED69 5653
| |
| ElNoHabido 2004-03-22, 7:34 am |
| >>In $PATH appear:
>
>
> Obviously only the $PATH of the normal user, I spoke about the root $PATH
> when running sensors-detect!
/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
| |
| ElNoHabido 2004-03-22, 7:34 am |
| >>In $PATH appear:
>
>
> Obviously only the $PATH of the normal user, I spoke about the root $PATH
> when running sensors-detect!
/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
|
|
|
|
|