Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
How to use your hardware sensors with Kernel 2.6
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... 8, 9, 10, 11  Next  
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
Helena
Veteran
Veteran


Joined: 02 Apr 2003
Posts: 1027
Location: De Meern, The Netherlands

PostPosted: Wed Apr 14, 2004 8:01 pm    Post subject: Reply with quote

So I had to find out more about Portage than planned... I used the masked packages FAQ to discover that I had to look in the ebuilds itself. There was the answer:
Code:
KEYWORDS="~amd64 -ppc -sparc -x86"
So, it seems that my problem can't be solved, because lm-sensors versions > 2.8.1 are not supposed to run on an x86 architecture??! I checked this with http://packages.gentoo.org and alas! it's consistent.
Back to top
View user's profile Send private message
WaVeX
Tux's lil' helper
Tux's lil' helper


Joined: 15 Mar 2004
Posts: 102
Location: USA, Michigan or Ohio

PostPosted: Wed Apr 14, 2004 8:45 pm    Post subject: Reply with quote

So what are us x86 people to do then?
Back to top
View user's profile Send private message
Helena
Veteran
Veteran


Joined: 02 Apr 2003
Posts: 1027
Location: De Meern, The Netherlands

PostPosted: Wed Apr 14, 2004 9:51 pm    Post subject: Reply with quote

WaVeX wrote:
So what are us x86 people to do then?
Yes I wonder too. Don't however forget that versions 2.8.1 and below do run on x86.
Back to top
View user's profile Send private message
WaVeX
Tux's lil' helper
Tux's lil' helper


Joined: 15 Mar 2004
Posts: 102
Location: USA, Michigan or Ohio

PostPosted: Thu Apr 15, 2004 12:51 am    Post subject: Reply with quote

2.8.1 works but it requires i2c which won't compile on a 2.6 kernel correct?
Back to top
View user's profile Send private message
JinxterX
n00b
n00b


Joined: 19 Apr 2004
Posts: 59

PostPosted: Mon Apr 19, 2004 5:02 pm    Post subject: Reply with quote

Helena wrote:
WaVeX wrote:
So what are us x86 people to do then?
Yes I wonder too. Don't however forget that versions 2.8.1 and below do run on x86.


Ok I got it working, you don't need to unmask anything. I'm using gentoo-dev-sources 2.6.5 on a KT400 chipset board with a Athlon XP.

All I did was enable ALL I2C options in kernel (making modules didn't work for me) , then after a reboot, check /sys/bus/i2c/devices for entries, if you have something there then you're ok. All you do now is emerge gkrellm,run gkrellm2, configure it and that's it :P
Back to top
View user's profile Send private message
Helena
Veteran
Veteran


Joined: 02 Apr 2003
Posts: 1027
Location: De Meern, The Netherlands

PostPosted: Tue Apr 20, 2004 6:50 am    Post subject: Reply with quote

JinxterX wrote:
Helena wrote:
WaVeX wrote:
So what are us x86 people to do then?
Yes I wonder too. Don't however forget that versions 2.8.1 and below do run on x86.


Ok I got it working, you don't need to unmask anything. I'm using gentoo-dev-sources 2.6.5 on a KT400 chipset board with a Athlon XP.

All I did was enable ALL I2C options in kernel (making modules didn't work for me) , then after a reboot, check /sys/bus/i2c/devices for entries, if you have something there then you're ok. All you do now is emerge gkrellm,run gkrellm2, configure it and that's it :P
Thanks a lot, you helped me out. In fact I didn't even recompile the kernel, so I do have everything compiled as modules. Odd, because this is quite different from the original guide!
Back to top
View user's profile Send private message
Helena
Veteran
Veteran


Joined: 02 Apr 2003
Posts: 1027
Location: De Meern, The Netherlands

PostPosted: Tue Apr 20, 2004 7:26 am    Post subject: Reply with quote

Addition/correction: on another system I did have to recompile to fill /sys/bus/i2c/devices with entries (actually only 1, it's a laptop and apparently I can monitor only the CPU's thermal zone...)
Back to top
View user's profile Send private message
JinxterX
n00b
n00b


Joined: 19 Apr 2004
Posts: 59

PostPosted: Tue Apr 20, 2004 8:04 am    Post subject: Reply with quote

After I discovered which sensors I actually have, I went back and removed the unused ones from the kernel and recompiled. Don't understand why compiling as modules won't work for me tho, hmm. Doesn't matter :P
Back to top
View user's profile Send private message
Wi1d
Apprentice
Apprentice


Joined: 15 Mar 2004
Posts: 282
Location: USA, Iowa

PostPosted: Wed Apr 21, 2004 11:23 am    Post subject: Reply with quote

Hi. I've seen this problem two pages back posted by psofa and was wondering if anybody knows were I went wrong. sensors gives the following output for the asb100 module:
Code:

asb100-i2c-0-2d
Adapter: SMBus I801 adapter at e800
ERROR: Can't get IN data! (0x0001)
ERROR: Can't get IN data! (0x0002)
ERROR: Can't get IN data! (0x0003)
ERROR: Can't get IN data! (0x0004)
ERROR: Can't get IN data! (0x0005)
ERROR: Can't get IN data! (0x0006)
ERROR: Can't get IN data! (0x0007)
ERROR: Can't get FAN data! (0x0031)
ERROR: Can't get FAN data! (0x0032)
ERROR: Can't get FAN data! (0x0033)
ERROR: Can't get TEMP data! (0x0051)
ERROR: Can't get TEMP data! (0x0054)
ERROR: Can't get TEMP data! (0x0057)
ERROR: Can't get TEMP data! (0x005a)
ERROR:Can't get VID data!
alarms:


What's really odd is that gkrellm reading data

Any ideas?


Last edited by Wi1d on Thu Apr 22, 2004 10:03 am; edited 1 time in total
Back to top
View user's profile Send private message
Murph001
n00b
n00b


Joined: 21 Mar 2004
Posts: 13

PostPosted: Thu Apr 22, 2004 8:21 am    Post subject: Reply with quote

I have a problem too with lm-sensors using 2.6.5 and my KT133A (old fashioned board).

sensors do only detect this:
Code:

root@mainframe modules.d # sensors
eeprom-i2c-8-51
Adapter: SMBus Via Pro adapter at 5000
Memory type:            SDR SDRAM DIMM
Memory size (MB):       128
 
eeprom-i2c-8-50
Adapter: SMBus Via Pro adapter at 5000
Memory type:            SDR SDRAM DIMM
Memory size (MB):       128


I tried each combination of modules to load up I could think of, but still now luck. So is there anyone with a KT133A based board, and had luck with 2.6.x kernel ?
It did work back in time with the 2.4.x kernel.

thx a lot
Back to top
View user's profile Send private message
Murph001
n00b
n00b


Joined: 21 Mar 2004
Posts: 13

PostPosted: Thu Apr 22, 2004 10:00 am    Post subject: Reply with quote

Murph001 wrote:
I have a problem too with lm-sensors using 2.6.5 and my KT133A (old fashioned board).

sensors do only detect this:
Code:

root@mainframe modules.d # sensors
eeprom-i2c-8-51
Adapter: SMBus Via Pro adapter at 5000
Memory type:            SDR SDRAM DIMM
Memory size (MB):       128
 
eeprom-i2c-8-50
Adapter: SMBus Via Pro adapter at 5000
Memory type:            SDR SDRAM DIMM
Memory size (MB):       128


I tried each combination of modules to load up I could think of, but still now luck. So is there anyone with a KT133A based board, and had luck with 2.6.x kernel ?
It did work back in time with the 2.4.x kernel.

thx a lot


Solved !

sensors -s do claim about a non accessible /sys , but gkrellm2 reads them correctly out, and they are there.

Modules for KT133A:
i2c_dev
via686a
eeprom
i2c_isa
i2c_sensor

greetz
Back to top
View user's profile Send private message
KenTI
n00b
n00b


Joined: 28 Jan 2004
Posts: 53
Location: Italy

PostPosted: Sat Apr 24, 2004 7:30 pm    Post subject: Reply with quote

i have an ASUS-A7N8XE deluxe with the nforce 2 chipset, i have installed the latest lm-sensors and developmant-sources-2.6.5

this is my "sensors" output, after one hour compiling at 100% usage

Code:

tux linux # sensors
eeprom-i2c-4-52
Adapter: SMBus nForce2 adapter at 5000
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512
 
eeprom-i2c-4-51
Adapter: SMBus nForce2 adapter at 5000
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512
 
asb100-i2c-5-2d
Adapter: SMBus nForce2 adapter at 5500
VCore 1:   +1.63 V  (min =  +1.26 V, max =  +1.90 V)
+3.3V:     +3.33 V  (min =  +2.96 V, max =  +3.63 V)
+5V:       +5.00 V  (min =  +4.49 V, max =  +5.51 V)
+12V:     +11.92 V  (min =  +9.55 V, max = +14.41 V)
-12V (reserved):
          -12.45 V  (min =  -0.00 V, max =  -0.00 V)
-5V (reserved):
           -5.22 V  (min =  -0.00 V, max =  -0.00 V)
CPU Fan:  7848 RPM  (min = 21093 RPM, div = 2)              ALARM
Chassis Fan:
             0 RPM  (min = 21093 RPM, div = 2)              ALARM
Power Fan:   0 RPM  (min = 10546 RPM, div = 2)              ALARM
M/B Temp:    +51 C  (high =   +80 C, hyst =   +75 C)
CPU Temp (Intel):
             +33 C  (high =   +80 C, hyst =   +75 C)
Power Temp:
            +126 C  (high =   +80 C, hyst =   +75 C)
CPU Temp (AMD):
             +25 C  (high =   +80 C, hyst =   +75 C)
vid:      +1.600 V
alarms:


which of these temperatures is the real cpu temp? the CPU temp (AMD) looks too low, and on the other side the 126 C power temp scares me.. although i don't see any flames coming out from my power adapter

is there something wrong with my computer?

----

i opened the chassis, and touched every part, the motherboard is not that hot but my videocard is burning!! it's a nvidia GeForce MX 440, with no fan on it (it came without fan..) shoud i buy a small fan and attach it to the videocard?
Back to top
View user's profile Send private message
Astral_
Tux's lil' helper
Tux's lil' helper


Joined: 24 Mar 2004
Posts: 137
Location: Poland (Tarnów)

PostPosted: Mon May 03, 2004 12:48 pm    Post subject: Reply with quote

I have problem :/


i make configure my Kernel 2.6.4

and i emerged lm-sensors-2.8.5


and look pleas at
Code:

emerge /usr/portage/sys-apps/i2c/i2c-2.8.4.ebuild
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-apps/i2c-2.8.4 to /
>>> md5 src_uri ;-) i2c-2.8.4.tar.gz

 * *****************************************************************
 *
 * This ebuild assumes your *current* kernel is >=2.4.9 && < 2.5+
 *
 * For 2.5+ series kernels, use the support already in the kernel
 * under 'Character devices' -> 'I2C support'.
 *
 * To cross-compile, 'export LINUX="/lib/modules/<version>/build"'
 * or symlink /usr/src/linux to another kernel.
 *
 * *****************************************************************

 * *****************************************************************
 *
 * WARNING: This i2c support is not recommended for things such as
 * WARNING: BTTV
 *
 * *****************************************************************
 *
 * http://www2.lm-sensors.nu/~lm78/cvs/browse.cgi/lm_sensors2/README
 *
 * 35 ADDITIONALLY, i2c-2.8.1 is not API compatible to earlier i2c
 * 36 releases due to struct changes; therefore you must NOT ENABLE
 * 37 any other i2c drivers (e.g. bttv) in the kernel.
 * 38 Do NOT use lm-sensors 2.8.0 or i2c-2.8.0 if you require bttv.
 *
 * Please try out http://www.ensicaen.ismra.fr/~delvare/devel/i2c/
 * for a kernel patch which will fix this problem. Please note that
 * nor the lm_sensors team nor the package maintainers will be able
 * to support you if you encounter problems with I2C when using
 * other modules with requirements on I2C...
 *
 * *****************************************************************

>>> Unpacking source...
>>> Unpacking i2c-2.8.4.tar.gz to /var/tmp/portage/i2c-2.8.4/work
>>> Source unpacked.

  * You are running:- 2.6.4-ck1
  * Using kernel in /usr/src/linux:- 2.6.4-ck1
  * Kernel version in /usr/src/linux is not 2.4.x
  * Please specify a 2.4.x kernel!

!!! ERROR: sys-apps/i2c-2.8.4 failed.
!!! Function src_compile, Line 71, Exitcode 0
!!! Incompatible Kernel



I need i2C , i dont have it
_________________
Pozdrawiam £ukasz
Gentoo 1.4
KDE 3.2.1
Kernel 2.6.4-ck1
Kadu 0.3.8

Electric Universe - The Prayer
Back to top
View user's profile Send private message
Astral_
Tux's lil' helper
Tux's lil' helper


Joined: 24 Mar 2004
Posts: 137
Location: Poland (Tarnów)

PostPosted: Mon May 03, 2004 1:38 pm    Post subject: Reply with quote

b000m


Code:

bash-2.05b# lsmod
Module                  Size  Used by
it87                   20648  -
i2c_sensor              2176  -
i2c_dev                 8384  -
i2c_core               17828  -


i2c-isa no such file :/


why not ?
_________________
Pozdrawiam £ukasz
Gentoo 1.4
KDE 3.2.1
Kernel 2.6.4-ck1
Kadu 0.3.8

Electric Universe - The Prayer
Back to top
View user's profile Send private message
amdunlock
Guru
Guru


Joined: 24 Apr 2004
Posts: 409
Location: Darmstadt Germany

PostPosted: Mon May 03, 2004 3:29 pm    Post subject: Reply with quote

my computer cant load i2c-isa and the w83627hf modul.

is my abit an7 the reason ?
_________________
-2500+ @ 3200+ ---- 512MB-Ram watercooled Htf X Triple @ 3 x 5V - Abit AN7 s*cking microguru - Geforce 6800 - Audigy 2 -=Gentoo Stage 2004.2 @ ext3=-
Back to top
View user's profile Send private message
Stormkings
Guru
Guru


Joined: 27 Sep 2002
Posts: 352
Location: Europe

PostPosted: Sun May 09, 2004 3:56 pm    Post subject: Reply with quote

same here. vanilla-sources 2.6.5, lm-sensors 2.8.6 on epox 8KTA3+PRO with kt133a chipset and no output from sensors:
Code:

via686a-isa-6000
Adapter: ISA adapter
ERROR: Can't get alarm data!
ERROR: Can't get IN0 data!
ERROR: Can't get IN1 data!
ERROR: Can't get IN2 data!
ERROR: Can't get IN3 data!
ERROR: Can't get IN4 data!
ERROR: Can't get FAN1 data!
ERROR: Can't get FAN2 data!
ERROR: Can't get TEMP data!
ERROR: Can't get TEMP2 data!
ERROR: Can't get TEMP3 data!

then i read the warning at:
http://forums.gentoo.org/viewtopic.php?t=101573
but rmmod i2c-viapro did not help.
Back to top
View user's profile Send private message
Master One
l33t
l33t


Joined: 25 Aug 2003
Posts: 754
Location: Austria

PostPosted: Sun May 16, 2004 6:44 pm    Post subject: Reply with quote

I'm totally stuck here. It's about an ASUS P4S533-X mobo.

Examining the mobo, I found the following chips:

LM 78L
SiS 962
IT 8705F

(how strange, why does a mobo need a LM78 and an IT87 ???)

I installed the lastest lm-sensors 2.8.6
i2c-sis96x, eeprom, lm78 & it87 compiled as modules
isa-support enabled
Kernel is actual development-sources 2.6.6-rc1
sensors-detect seemed to work out fine, also reported problems (see below)

This is what I can see in the bios hardware-monitor menu:

Code:
CPU TEMP: 57°C
CPU FAN: 3391 RPM
CHASSIS FAN: 2537 RPM
VCORE: 1.52V
+3.3V: 3.29V
+5V: 5.05V
+12V: 11.90V


No mobo-temp or negative voltages are shown (how strange). The chassis-fan is actually my power-supply-fan.

So this is what I get with sensors:

Code:
root # sensors
it87-isa-0290
Adapter: ISA adapter
VCore 1:   +1.55 V  (min =  +1.42 V, max =  +1.56 V)
VCore 2:   +1.64 V  (min =  +2.40 V, max =  +2.60 V)   ALARM
+3.3V:     +2.99 V  (min =  +3.13 V, max =  +3.45 V)   ALARM
+5V:       +5.02 V  (min =  +4.72 V, max =  +5.24 V)
+12V:      +0.00 V  (min = +11.36 V, max = +12.60 V)   ALARM
-12V:     -27.36 V  (min = -12.63 V, max = -11.41 V)   ALARM
-5V:      -13.64 V  (min =  -5.28 V, max =  -4.81 V)   ALARM
Stdby:     +0.00 V  (min =  +4.72 V, max =  +5.24 V)   ALARM
VBat:      +3.28 V
fan1:     3110 RPM  (min =    0 RPM, div = 2)
fan2:        0 RPM  (min = 2657 RPM, div = 2)          ALARM
fan3:        0 RPM  (min = 2657 RPM, div = 2)          ALARM
M/B Temp:    +33°C  (low  =   +15°C, high =   +40°C)   sensor = diode
CPU Temp:   +127°C  (low  =   +15°C, high =   +45°C)   sensor = thermistor
Temp3:      +127°C  (low  =   +15°C, high =   +45°C)   sensor = thermistor

eeprom-i2c-0-51
Adapter: SiS96x SMBus adapter at 0xe600
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

eeprom-i2c-0-50
Adapter: SiS96x SMBus adapter at 0xe600
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512


As you can see, a lot of problems are shown:

VCore 1: seems to be nearly correct
VCore 2: No idea what that is, as I only have one cpu
+3.3V: not correct (I commented the line that doubles the value in sensors.conf, as it is suggested, but it's not correct anyway)
+5V: seems to be nearly correct
+12V: zero reading, so no value at all
-12V: actually zero reading, the shown value comes from a calculation in sensors.conf
-5V: actually zero reading, the shown value comes from a calculation in sensors.conf
Stdby: zero reading, no idea what this value should be anyway
VBat: may be correct, no idea what this value should tell me
fan1: could be the CPU fan, but not exactly correct
fan2 & fan 3: no reading (what happened to my power-supply-fax ???)
M/B Temp: seems to be a reasonable value, but can't tell if it really is correct, no idea if the sensor-typ is correct
CPU Temp & Temp3: totally wrong, no idea what happened there and why it's two times the same value

I do not care about the voltage readings, but I wanted to be able to monitor the mobo-temp / cpu-temp / cpu-fan / power-supply-fan readings.
I checked the sensors.conf, but I have no idea, what to correct in the it87 section, also what to do for the values that have a zero reading???

This is my sensors-detect output (this is a rerun, with sensors already established):

Code:
root # 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.

It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.

 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-sis96x' for device 00:02.1: Silicon Integrated Systems SMBus Controller
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Load `i2c-sis96x' (say NO if built into your kernel)? (YES/no): YES
Module loaded succesfully.
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): YES
 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. That often
 includes address 0x69 (clock chip).

Next adapter: SiS96x SMBus adapter at 0xe600 (Algorithm unavailable)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x08
Client found at address 0x10
Client at address 0x50 can not be probed - unload all client drivers first!
Client at address 0x51 can not be probed - unload all client drivers first!
Client found at address 0x69
Client found at address 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. This is usually safe though.

Do you want to scan the ISA bus? (YES/no): YES
Probing for `National Semiconductor LM78'
  Trying address 0x0290... Success!
    (confidence 7, driver `lm78')
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... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
  Trying general detect... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'
  Trying address 0x0290... Success!
    (confidence 8, driver `it87')
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! (0x8705)
Probing for `ITE 8705F Super IO Sensors'
  Success... found at address 0x0290
Probing for `ITE 8712F Super IO Sensors'
  Failed! (0x8705)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed!
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
  Failed!
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
  Failed!
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
  Failed!
Probing for `Nat. Semi. PC87365 Super IO Sensors'
  Failed!
Probing for `Nat. Semi. PC87366 Super IO Sensors'
  Failed!
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
  Failed!
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed!
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
  Failed!
Probing for `SMSC 47M14x Super IO Fan Sensors'
  Failed!
Probing for `SMSC 47M15x/192 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!

Do you want to scan for secondary Super I/O sensors? (YES/no): YES
Probing for `ITE 8702F Super IO Sensors'
  Failed!
Probing for `ITE 8705F Super IO Sensors'
  Failed!
Probing for `ITE 8712F Super IO Sensors'
  Failed!
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed!
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
  Failed!
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
  Failed!
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
  Failed!
Probing for `Nat. Semi. PC87365 Super IO Sensors'
  Failed!
Probing for `Nat. Semi. PC87366 Super IO Sensors'
  Failed!
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
  Failed!
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed!
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
  Failed!
Probing for `SMSC 47M14x Super IO Fan Sensors'
  Failed!
Probing for `SMSC 47M15x/192 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 `lm78' (may not be inserted):
  Misdetects:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `National Semiconductor LM78' (confidence: 7)

Driver `it87' (should be inserted but causes problems):
  Detects correctly:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `ITE 8705F Super IO Sensors' (confidence: 9)
  Misdetects:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `ITE IT8705F / IT8712F / SiS 950' (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)? ISA

If you want to load the modules at startup, generate a config file
below and make sure lm_sensors get started (eg. rc-update add lm_sensors default).

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

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
options it87 ignore=-1,0x290
#----end 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.
To load everything that is needed, execute the commands above...

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

Do you want to overwrite /etc/conf.d/lm_sensors? Enter s to specify other file name?
  (yes/NO/s): NO


These are the loaded modules:
Code:
 root # lsmod
Module                  Size  Used by
it87                   19596  0
eeprom                  6408  0
i2c_sensor              2560  2 it87,eeprom
i2c_isa                 1920  0
i2c_sis96x              4484  0
i2c_core               18948  5 it87,eeprom,i2c_sensor,i2c_isa,i2c_sis96x
usbhid                 30016  0
ehci_hcd               23940  0
ohci_hcd               16900  0
usbcore                92508  5 usbhid,ehci_hcd,ohci_hcd


I already tried to install lm-sensors on different computers with different mobo's and kernels. The installation itself never was a problem, but I never could get correct sensor readings, that's really annoying.

It would be so much help, if there would be a website with the correct sensors.conf for various motherboards from people who finally could set it up correctly.

Any suggestions for me?

BTW As suggested in the lm-sensors-FAQ, I took a look at the motherboard-monitor-website (mbm.livewiredev.com), and strangly my mobo is shows there with ASB100 as sensor-chip. But this is not correct, as I could not find that chip on my mobo, and when trying the module asb100.o, there is no sensors output at all.
_________________
Las torturas mentales de la CIA
Back to top
View user's profile Send private message
Master One
l33t
l33t


Joined: 25 Aug 2003
Posts: 754
Location: Austria

PostPosted: Sun May 16, 2004 8:25 pm    Post subject: Reply with quote

Ok, after a lot of research, I came to the following results.

On the lm-sensors self-support ticket system, I found a modified sensors.conf for the P4S533-X, which I modified further to fit for my setup.

Code:
root # cat /etc/sensors.conf
# Sensors configuration file used by ´libsensors´
#------------------------------------------------
# Configuration file for an Asus P4S533-X

chip "it87-*"

# the P4S533-X only reports 5 voltages
    label   in0 "VCore"
    label   in1 "+3.3V"
    label   in2 "+ 12V"
    label   in3 "+  5V"
    ignore  in4
    ignore  in5
    ignore  in6
    ignore  in7
    label   in8 "VBat"

# in0 will depend on your processor VID value, set to voltage specified in
# bios setup screen
    set     in0_min 1.525 * 0.95
    set     in0_max 1.525 * 1.05
    set     in1_min 3.30  * 0.95
    set     in1_max 3.30  * 1.05
    set     in2_min 12.0  * 0.95
    set     in2_max 12.0  * 1.05
    set     in3_min 5.0   * 0.95
    set     in3_max 5.0   * 1.05

# vid not monitored by IT8705F
    ignore  vid

# these were determined emprically (by analogy to other sensor types),
# but do return values which match those reported by the BIOS
    compute in1 (1 + 1)*@      ,  @/(1 + 1)
    compute in2 ((30/10) +1)*@ ,  @/((30/10) +1)
    compute in3 ((6.8/10)+1)*@ ,  @/((6.8/10)+1)

# temperature
#
# 2 = thermistor; 3 = thermal diode; 0 = unused
    set sensor1 3
#   set sensor2 3
#   set sensor3 3
    label   temp1      "CPU Temp"
    compute temp1 (@*30/43)+35 ,  (@-35)*43/30
#   set     temp1_over 40
#   set     temp1_hyst 20
    ignore  temp2
    ignore  temp3

# fans
    label   fan1     "CPU Fan"
#   set     fan1_div 4
    set     fan1_min 2000
    label   fan2     "PSU Fan"
#   set     fan2_div 4
    set     fan2_min 2000
    ignore  fan3

This is what I now get as sensors output:

Code:
root # sensors
it87-isa-0290
Adapter: ISA adapter
VCore:     +1.55 V  (min =  +1.44 V, max =  +1.60 V)
+3.3V:     +3.28 V  (min =  +3.12 V, max =  +3.44 V)
+ 12V:    +11.96 V  (min = +11.36 V, max = +12.60 V)
+  5V:     +5.02 V  (min =  +4.72 V, max =  +5.24 V)
VBat:      +3.28 V
CPU Fan:  3068 RPM  (min = 1997 RPM, div = 4)
PSU Fan:  2537 RPM  (min = 1997 RPM, div = 4)
CPU Temp:    +58°C  (low  =   +45°C, high =   +63°C)   sensor = diode

eeprom-i2c-0-51
Adapter: SiS96x SMBus adapter at 0xe600
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

eeprom-i2c-0-50
Adapter: SiS96x SMBus adapter at 0xe600
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

I am quite unsure about the CPU temp calculation, but it seems to fit.

It looks like this mobo has no M/B-temp sensor, as I am quite sure it would show up in the BIOS hardware-monitor-menu, if it would, that's why I ignore temp2.
_________________
Las torturas mentales de la CIA
Back to top
View user's profile Send private message
Paranoid
Apprentice
Apprentice


Joined: 07 Jan 2004
Posts: 290
Location: Portland, ME

PostPosted: Thu May 20, 2004 5:47 pm    Post subject: Reply with quote

K, here's my modified sensors.conf for an A7N8X-Deluxe rev. 2 board. After doing alot of research most things are giving an accurate reading (see my notes).
Code:
chip "asb100-*"

    set vrm 9.0

    label in0 "VCore 1"
    set in0_min vid * 0.95
    set in0_max vid * 1.05

    # only 1 processor here, ignore
    #label in1 "VCore 2"
    ignore in1
    #set in1_min vid * 0.95
    #set in1_max vid * 1.05

    label in2 "+3.3V"
    set in2_min 3.3 * 0.95
    set in2_max 3.3 * 1.05

    label in3 "+5V"
    compute in3 1.68 * @ ,  @ / 1.68
    set in3_min 5.0 * 0.95
    set in3_max 5.0 * 1.05

    # Had to change compute, voltage reading was low compared to
    # to BIOS. Ran across some info at MBM that says there are 2
    # standards for the ASB100, the only difference being standard 2 has
    # in4 & in5 compute at 4 instead of 3.8 & 3.97. Matches my BIOS
    # values.
    label in4 "+12V"
    compute in4 4 * @ , @ / 4
    set in4_min 12  * 0.90
    set in4_max 12  * 1.10

    # Changed compute, see above note
    label in5 "-12V (reserved)"
    #ignore in5
    compute in5 -@ * 4 , -@ / 4
    set in5_max -12 * 0.90
    set in5_min -12 * 1.10

    label in6 "-5V (reserved)"
    #ignore in6
    compute in6 -@ * 1.666 , -@ / 1.666
    #set in6_max -5  * 0.95
    #set in6_min -5  * 1.05

    # Socket thermistor reading, not an accurate representation
    # of CPU temp without proper compute-working on it...
    # One other thing, temp1 & temp2 were reversed on the A7N8X-D
    # Rev.2 boards. Temp1 should be cpu, Temp2 M/B.
    label temp1 "Socket Thermistor"
    set temp1_over 60
    set temp1_hyst 55

    # This seems to match my BIOS readings, taken from somewhere
    # near the Bach 100 chip
    label temp2 "M/B Temp"
    #ignore temp2
    set temp2_over 45
    set temp2_hyst 40

    # PWRTMP1 connector on A7N8X-will read 126/127 for open connection
    # which is why I am ignoring this because I have an open connection
    #label temp3 "Power Temp"
    ignore temp3
    #set temp3_over 45
    #set temp3_hyst 40


    # Unknown reading, doesn't seem to match with anything nor
    # does it ever change. I read in a few places this should be CPU
    # thermal diode reading but that is BS.
    #label temp4 "CPU Temp (AMD)"
    ignore temp4
    #set temp4_over 60
    #set temp4_hyst 50

    # All fan speeds need to be /2 for correct reading
    label fan1 "CPU Fan"
    compute fan1 @ / 2 , 2 * @
    set fan1_div 2
    set fan1_min 4000

    label fan2 "Chassis Fan"
    compute fan2 @ / 2 , 2 * @
    set fan2_div 4
    set fan2_min 1500

    label fan3 "Power Fan"
    compute fan3 @ / 2 , 2 * @
    set fan3_div 8
    set fan3_min 1000


chip "w83l785ts-*"

    # CPU thermal diode-this reading is what you should be
    # looking at for an accurate CPU temp reading.
    label temp "CPU Thermal Diode"


For your fan_divs you should look at the docs/fan-divisors.

Modules you need loaded are:
i2c-core
i2c-dev
i2c-nforce2
i2c-sensor
asb100
eeprom
w83l785ts

Still working on a couple of things-would be a hell of alot easier is ASUS would release a data sheet.
_________________
A paranoid is someone who knows a little of what's going on.
William S. Burroughs
Back to top
View user's profile Send private message
yeoman
Tux's lil' helper
Tux's lil' helper


Joined: 05 Jan 2004
Posts: 109
Location: Germany

PostPosted: Thu May 27, 2004 5:57 pm    Post subject: Reply with quote

Just to tell you, i have my sensors working on a Shuttle AN35-Ultra with vanilla kernel 2.6.6 and pure udev.
Modules are i2c-nforce2, i2c-isa and it87.
lm-sensors-2.8.6 doesn`t work for me, sensors-detect fails with:
Quote:
root@yeoman root # sensors-detect
No i2c device files found. Use prog/mkdev/mkdev.sh to create them.

I dont mind, sensors show up in gkrellm and I am pleased :D .
Back to top
View user's profile Send private message
rob.sharp
n00b
n00b


Joined: 23 Sep 2003
Posts: 16
Location: Leeds, England

PostPosted: Thu May 27, 2004 8:24 pm    Post subject: Reply with quote

I've created a wee ebuild for gnome hardware monitor 1.0.1, which is bugzilla at

http://bugs.gentoo.org/show_bug.cgi?id=52210

Thoughts?

Rob.
Back to top
View user's profile Send private message
yeoman
Tux's lil' helper
Tux's lil' helper


Joined: 05 Jan 2004
Posts: 109
Location: Germany

PostPosted: Thu May 27, 2004 10:58 pm    Post subject: Reply with quote

rob.sharp wrote:
I've created a wee ebuild for gnome hardware monitor 1.0.1

Works, thank you and good bye gkrellm!
Back to top
View user's profile Send private message
Tazok
Guru
Guru


Joined: 25 Oct 2003
Posts: 310

PostPosted: Mon May 31, 2004 10:34 pm    Post subject: Reply with quote

My CPU-Temp is correctly displayed in gkrellm2, but the voltage measures are always at 0.00.
I have an Abit NF7 Board and the following module loaded: w83781d.
The rest is kernel builtin.

The output of "sensors" is:
Code:
pcf8591-i2c-0-4e
Adapter: SMBus nForce2 adapter at 5000
Chan. 0:    0.00 V
Chan. 1:    0.00 V
Chan. 2:    0.00 V
Chan. 3:    0.00 V
Output:     0.00 V (enabled)
Back to top
View user's profile Send private message
ColinAnderson
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2003
Posts: 89

PostPosted: Thu Jun 03, 2004 8:58 pm    Post subject: Reply with quote

So how do I control various things? Like the fans. I want to check if my system temperature is within a certain range .. if it is, I would like to turn off the case fans to decrease noise. I have my sensors working and everything, but I'm at a loss as to how to do anything with them. :)
_________________
~Colin
Back to top
View user's profile Send private message
Master_Of_Disaster
l33t
l33t


Joined: 28 Feb 2003
Posts: 610
Location: 15.05072° East, 48.13747° North (aka Mauer), Austria

PostPosted: Tue Jun 15, 2004 2:24 pm    Post subject: Reply with quote

@ColinAnderson:
As I said, lm_sensors is still being ported to 2.6, there are still issues and missing features. I want to control my Shuttle's fans too, but fan controlling support in the it87 driver has not yet been implemented/ported.
_________________
post tenebras lux, post fenestras tux
Registered Linux User Nr. 312509
Adopt an unanswered post today!
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Goto page Previous  1, 2, 3 ... 8, 9, 10, 11  Next
Page 9 of 11

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum