Trying to get lm_sensors to work with Slack???

Southpaw76 · 12-31-2006, 04:22 PM

Hello all,
I'm in the process of trying to get lm_sensors to work but I'm having some problems...I'm using the lm_sensors package included with Slackware-11...

Code:

lm_sensors-2.10.0-i486-3

I followed the doc's, enabled the modules in my kernel (linux-2.6.17.13), and I ran sensors-detect. After-which I ran "sensors" only to get this...

Code:

# sensors
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!

...heres my /etc/fstab

Code:

/dev/hdb2        swap             swap        defaults         0   0
/dev/hdb1        /                reiserfs    defaults         1   1
/dev/hdb3        /home            reiserfs    defaults         1   2
/dev/cdrom       /mnt/cdrom       auto        noauto,owner,ro  0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
sysfs            /sys             sysfs       defaults         0   0

...if I've left anything out let me know. Btw, I'm trying to use conky with this and not GKlrellm. If anyone has any suggestions please let me know...Thanx

hussar · 12-31-2006, 06:02 PM

Make sure that you have the i2c modules compiled and installed.

If you are certain that you have the i2c modules compiled and installed and you still have this problem, try compiling i2c into the kernel.

I had a similar problem a while back, and I eventually had to just compile i2c into my kernel. Works fine now, but it had me scratching my head for a bit.

Southpaw76 · 12-31-2006, 06:41 PM

Okay, yeah, I have them compiled in as modules. I'll try compiling them directly into the kenel and see what happens

...

Southpaw76 · 12-31-2006, 10:27 PM

Okay, that partially works. What I mean is...

After having re-compiled my kernel with the I2C related stuff built in.I went ahead and ran "sensors-detect",

Code:

 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-i801' for device 00:1f.3: Intel 82801DB ICH4
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no): no
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

 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): no
 Well, you will know best. We will just hope you edited `/etc/modules.conf'
 for automatic loading of this module. If not,
 you won't be able to open any /dev/i2c-* file (unless youhave it built-in
 into your kernel)

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

...the first problem I noticed is when I say yes to the next question nothing happens, which after I do so everything hangs but when I say yes it moves on to the next question...

Code:

Next adapter: PCA9564 ISA Adapter
Do you want to scan it? (YES/no/selectively): no

Next adapter: SMBus I801 adapter at e480
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x08
Client found at address 0x30
Client found at address 0x31
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Client found at address 0x69

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. This is usually safe though.
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 W83627EHF'
  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 IT8712F'
  Trying address 0x0290... Failed!
Probing for `ITE IT8705F / 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. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no): yes
[/Probing for `ITE 8702F Super IO Sensors'
  Failed! (0x5900)
Probing for `ITE 8705F Super IO Sensors'
  Failed! (0x5900)
Probing for `ITE 8712F Super IO Sensors'
  Failed! (0x5900)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (0x59)
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
  Failed! (0x59)
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
  Failed! (0x59)
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
  Failed! (0x59)
Probing for `Nat. Semi. PC87365 Super IO Fan Sensors'
  Failed! (0x59)
Probing for `Nat. Semi. PC87365 Super IO Voltage Sensors'
  Failed! (0x59)
Probing for `Nat. Semi. PC87365 Super IO Thermal Sensors'
  Failed! (0x59)
Probing for `Nat. Semi. PC87366 Super IO Fan Sensors'
  Failed! (0x59)
Probing for `Nat. Semi. PC87366 Super IO Voltage Sensors'
  Failed! (0x59)
Probing for `Nat. Semi. PC87366 Super IO Thermal Sensors'
  Failed! (0x59)
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
  Failed! (0x59)
Probing for `Nat. Semi. PC87373 Super IO Fan Sensors'
  Failed! (0x59)
Probing for `Nat. Semi. PC87591 Super IO'
  Failed! (0x59)
Probing for `Nat. Semi. PC87371 Super IO'
  Failed! (0x59)
Probing for `Nat. Semi. PC97371 Super IO'
  Failed! (0x59)
Probing for `Nat. Semi. PC8739x Super IO'
  Failed! (0x59)
Probing for `Nat. Semi. PC8741x Super IO'
  Failed! (0x59)
Probing for `Nat. Semi. PCPC87427 Super IO'
  Failed! (0x59)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (0x59)
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
  Success... found at address 0x0680
Probing for `SMSC 47M14x Super IO Fan Sensors'
  Failed! (0x59)
Probing for `SMSC 47M15x/192/997 Super IO Fan Sensors'
  Failed! (0x59)
Probing for `SMSC 47S42x Super IO Fan Sensors'
  Failed! (0x59)
Probing for `SMSC 47S45x Super IO Fan Sensors'
  Failed! (0x59)
Probing for `SMSC 47M172 Super IO'
  Failed! (0x59)
Probing for `SMSC LPC47B397-NC Super IO'
  Failed! (0x59)
Probing for `SMSC SCH5307-NS Super IO'
  Failed! (0x59)
Probing for `VT1211 Super IO Sensors'
  Failed! (skipping family)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
  Failed! (skipping family)

Do you want to scan for secondary Super I/O sensors? (YES/no): yes
Probing for `ITE 8702F Super IO Sensors'
  Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
  Failed! (skipping family)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
  Failed! (skipping family)

...Anyway, after completing the procedure and I run "sensors", this what I get...

Code:

# sensors
smsc47m1-isa-0680
Adapter: ISA adapter
fan2:        0 RPM  (min =  640 RPM, div = 8)

...it appears as though I'm missing a sensor or two, what do you think???

hussar · 01-01-2007, 02:39 AM

Here is what I get from running sensors:

Quote:

bash-3.1$ sensors
w83697hf-isa-0290
Adapter: ISA adapter
VCore: +1.66 V (min = +1.71 V, max = +1.89 V) ALARM
+3.3V: +1.55 V (min = +3.14 V, max = +3.47 V) ALARM
+5V: +4.81 V (min = +4.76 V, max = +5.24 V)
+12V: +12.22 V (min = +10.82 V, max = +13.19 V)
-12V: +1.70 V (min = -13.18 V, max = -10.80 V) ALARM
-5V: +0.48 V (min = -5.25 V, max = -4.75 V) ALARM
V5SB: +5.24 V (min = +4.76 V, max = +5.24 V)
VBat: +2.67 V (min = +2.40 V, max = +3.60 V)
fan1: 3245 RPM (min = 964 RPM, div = 8)
fan2: 2678 RPM (min = 712 RPM, div = 8)
temp1: +27°C (high = -68°C, hyst = -34°C) sensor = thermistor ALARM
temp2: +45.5°C (high = +100°C, hyst = +95°C) sensor = thermistor
alarms:
beep_enable:
Sound alarm enabled

I also get different results when I run sensors-detect as root than when I run it as myself. When I run as root, it goes through its detection, and then I am shown this:

Quote:

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

Driver `w83627hf' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83697HF Super IO Sensors' (confidence: 9)

I will now generate the commands needed to load the I2C modules.

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 w83627hf
# 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.

Maybe you should run sensors-detect as root.

BTW, you won't hear from me for a couple of days. We're going to go visit my mother-in-law. I hope in the meantime you get this working for you.