lm_sensors not working. No sensors found!

Kramer · 09-12-2004, 11:37 AM

Yes it detects that I should use the via686 driver, the same one as the other guy in this thread uses, but it still doesnt start at boot, and when I do 'sensors' in the shell, I still get no sensors found.

mdg · 09-12-2004, 11:39 AM

What is the output of lsmod?

Kramer · 09-12-2004, 11:43 AM

Quote:

Module Size Used by
nls_iso8859-1 3776 0
isofs 30968 0
zlib_inflate 21568 1 isofs
vfat 11584 0
fat 41088 1 vfat
md5 3712 1
ipv6 223168 6
sg 34588 0
st 36440 0
sr_mod 14820 0
sd_mod 15264 0
scsi_mod 105784 4 sg,st,sr_mod,sd_mod
snd-seq-midi 6688 0
snd-seq-oss 31360 0
snd-seq-midi-event 6208 2 snd-seq-midi,snd-seq-oss
snd-seq 49936 5 snd-seq-midi,snd-seq-oss,snd-seq-midi-event
snd-pcm-oss 49124 0
snd-mixer-oss 17088 1 snd-pcm-oss
snd-via82xx 22432 2
snd-pcm 85348 3 snd-pcm-oss,snd-via82xx
snd-timer 21508 2 snd-seq,snd-pcm
snd-ac97-codec 60036 1 snd-via82xx
gameport 3520 1 snd-via82xx
snd-page-alloc 9604 2 snd-via82xx,snd-pcm
snd-mpu401-uart 5888 1 snd-via82xx
snd-rawmidi 20000 2 snd-seq-midi,snd-mpu401-uart
snd-seq-device 6664 4 snd-seq-midi,snd-seq-oss,snd-seq,snd-rawmidi
snd 46820 16 snd-seq-midi,snd-seq-oss,snd-seq-midi-event,snd-seq,snd-pcm-oss,snd-mixer-oss,snd-via82xx,snd-pcm,snd-timer,snd-ac97-codec,snd-mpu401-uart,snd-rawmidi,snd-seq-device
soundcore 7072 1 snd
af_packet 16456 6
via686a 18440 0
i2c-sensor 2368 1 via686a
i2c-isa 1664 0
i2c-core 19268 3 via686a,i2c-sensor,i2c-isa
hid 52736 0
raw 6016 1
ide-floppy 17280 0
ide-tape 34448 0
ide-cd 38660 0
cdrom 36832 2 sr_mod,ide-cd
floppy 56084 0
prism54 46936 0
firmware_class 6720 1 prism54
ds 11524 2
yenta_socket 14592 1
pcmcia_core 58208 2 ds,yenta_socket
supermount 36052 1
via-agp 5888 1
agpgart 26472 1 via-agp
evdev 7872 1
uhci-hcd 27792 0
usbcore 89820 4 hid,uhci-hcd
rtc 9784 0
ext3 118056 2
jbd 57368 1 ext3

I see the modules there, but I dont know why its not working.

cyclocommuter · 09-12-2004, 11:49 AM

Quote:

Originally posted by Kramer
Ok, I have everything compiled in like that, but I did 'urpmi' to get lm_sensors off the Mandrake cd's. It is version 2.8.4 I think. How can I find where it installed it to, and is there anything else I can do? The 2.8.5 I downloaded doesnt compile at all.

Here is a good Linux Journal article on how to enable health monitoring with lm_sensors:

Linux Journal Article

I actually just used the article as a guide as installing lm_sensors. I did not follow all the steps outlined specifically editing the config files as these seem to have been done automatically by running sensors-detect.

In Mandrake 10 here is what I did from my recollection (both for my Intel PERLK motherboard and on my ASUS A7N8X D motherboard):

1. Use Mandrake's built in GUI install utility (rpmdrake) to look for and then install lm_sensors.
2. On the console, log in as SU then type "sensors-detect" and hit return.
3. Follow the prompts mostly accepting defaults. If I recall right on my A7N8X D motherboard I had to install the ISA options so the Temps would register.
4. I think sensors-detect will automatically update the config files.
5. To test if sensors work, just type sensors on the console.
6. Updated gkrellm which now shows sensors options.

Kramer · 09-12-2004, 11:54 AM

Ive done all of that, but when I type in 'sensors' in the shell, I get 'no sensors found!'
Gkrellm still has all of the sensor stuff grayed out

mdg · 09-12-2004, 12:03 PM

I don't see any i2c interface module for your chipset. Try doing "modprobe i2c-viapro" or "modprobe i2c-via".
Load one and run "sensors" after you load it. If there's no change, try the other

edit: after checking lm_sensors site, it looks like you need the i2c-viapro module

Kramer · 09-12-2004, 12:17 PM

Did 'modprobe i2c-viapro' and checked it using 'lsmod'. Its there now, but 'sensors' still yeilds 'No sensors found!' Any other ideas?

EDIT: I should add that I tried it with both of them, and no go.

mdg · 09-12-2004, 12:23 PM

Try running "sensors-detect" again and post the results of the program (beginning to end)

Kramer · 09-12-2004, 12:32 PM

Quote:

[root@localhost matthew]# sensors-detect

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most 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.

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-viapro' for device 00:07.4: VIA Technologies VT82C686 Apollo ACPI
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-viapro' already loaded.
Do you now want to be prompted for non-detectable adapters? (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 already loaded.

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).

Next adapter: ELV Parallel port adaptor (Algorithm unavailable)
Do you want to scan it? (YES/no/selectively): no

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): yes
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 VT82C686 Integrated Sensors'
Trying general detect... Success!
(confidence 9, driver `via686a')
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): no

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `via686a' (should be inserted):
Detects correctly:
* ISA bus, undetermined address (Busdriver `i2c-isa')
Chip `VIA Technologies VT82C686 Integrated Sensors' (confidence: 9)

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)? isa

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 via686a
# 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): yes
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
[root@localhost matthew]#

mdg · 09-12-2004, 12:41 PM

Code:

 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): no

You should do a scan of the I/O ports. There might be a chip that you're not picking up.
Run the program again with the I/O scan and post the results from the following line down

Code:

To make the sensors modules behave correctly, add these lines to /etc/modules.conf:

Kramer · 09-12-2004, 12:47 PM

Ive added those lines exactly to /etc/modules.conf:

Quote:

probeall usb-interface usb-uhci
above snd-via82xx snd-pcm-oss
alias eth0 8139too
alias sound-slot-0 snd-via82xx
alias char-major-89 i2c-dev

Now for the output:

Quote:

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):
Probing for `ITE 8712F Super IO Sensors'
Failed! (0xffff)
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 W83637HF Super IO Sensors'
Failed!
Probing for `Winbond W83697HF Super IO Sensors'
Failed!
Probing for `Winbond W83697UF Super IO PWM'
Failed!

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `via686a' (should be inserted):
Detects correctly:
* ISA bus, undetermined address (Busdriver `i2c-isa')
Chip `VIA Technologies VT82C686 Integrated Sensors' (confidence: 9)

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)? isa

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 via686a
# 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): yes
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
[root@localhost matthew]#

mdg · 09-12-2004, 01:20 PM

I had Mdk 10 working with lm_sensors and I set up the specified code as follows:

This section went to /etc/modules.conf, as you did it

Code:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

This section I put in /etc/rc.d/rc.local

Code:

#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe via686a
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----

Lastly, I copied the lm_sensors.init file from /your/home/dir/lm_sensors-2.8.4/prog/init/lm_sensors.init to
/etc/rc.d/init.d/lm_sensors (note the name change). Make sure the file is executable. Then reboot.

If that doesn't work, I'm pretty much out of ideas. The last thing I can think of to try is run "sensors-detect" again
and include the other test you left out:

Code:

Next adapter: ELV Parallel port adaptor (Algorithm unavailable)
Do you want to scan it? (YES/no/selectively): no

Kramer · 09-12-2004, 01:43 PM

Ok, heres my problem with that

Quote:

Lastly, I copied the lm_sensors.init file from /your/home/dir/lm_sensors-2.8.4/prog/init/lm_sensors.init to
/etc/rc.d/init.d/lm_sensors (note the name change). Make sure the file is executable. Then reboot.

I have no idea where the /prog/init/lm_sensors.init is because I did urpmi, and I dont know where it installed it to. Now, there is an lm_sensors script in the /etc/rc.d/init.d directory. I dont think its the right one though. Any other advice?

mdg · 09-12-2004, 01:51 PM

Try "locate lm_sensors.init"

Kramer · 09-12-2004, 02:33 PM

Did that and couldnt find it. Which version of lm_sensors and kernel are you using just out of curiosity?