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 ... 7, 8, 9, 10, 11  Next  
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
Master_Of_Disaster
l33t
l33t


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

PostPosted: Thu Mar 04, 2004 2:44 pm    Post subject: Reply with quote

@JWicks
Look at /etc/sensors.conf, you should be able to adjust temperature values there.

@christsong84
Is smbus-arp in 2.6 present already? I don't remember... Please check this first, otherwise let us see the relevant parts of your dmesg, perhaps this will clear up things.
_________________
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
christsong84
Veteran
Veteran


Joined: 06 Apr 2003
Posts: 1003
Location: GMT-8 (Spokane)

PostPosted: Thu Mar 04, 2004 3:27 pm    Post subject: Reply with quote

ah...perhaps that's the problem...I did a locate smbus and didn't find smbus-arp anywhere (except in the lmsensors documentation but I don't tihnk that counts)
_________________
while(true) {self.input(sugar);} :twisted:
Back to top
View user's profile Send private message
psofa
Guru
Guru


Joined: 28 Feb 2004
Posts: 485

PostPosted: Fri Mar 05, 2004 12:06 am    Post subject: Reply with quote

ERROR: Can't get temperature data!

->these problems where fixed for me with lm_sensors cvs :lol:
_________________
psofa
Back to top
View user's profile Send private message
Master One
l33t
l33t


Joined: 25 Aug 2003
Posts: 754
Location: Austria

PostPosted: Sat Mar 06, 2004 12:53 pm    Post subject: Reply with quote

Just found this threat, and could get it run in notime :D

I have a mobo with SiS 735 chipset, this is the output of sensors:

Code:
it87-isa-0290
Adapter: ISA adapter
VCore 1:   +1.77 V  (min =  +1.53 V, max =  +1.87 V)
VCore 2:   +2.44 V  (min =  +2.25 V, max =  +2.75 V)
+3.3V:     +6.42 V  (min =  +2.96 V, max =  +3.60 V)   ALARM
+5V:       +4.89 V  (min =  +4.50 V, max =  +5.48 V)
+12V:     +12.00 V  (min = +11.36 V, max = +13.80 V)
-12V:      -1.59 V  (min = -15.86 V, max = -13.40 V)   ALARM
-5V:       +2.29 V  (min = -10.13 V, max =  -9.44 V)   ALARM
Stdby:     +4.94 V  (min =  +4.50 V, max =  +5.48 V)
VBat:      +3.36 V
fan1:     5400 RPM  (min = 3000 RPM, div = 2)
fan2:        0 RPM  (min = 3000 RPM, div = 2)          ALARM
fan3:        0 RPM  (min = 3000 RPM, div = 2)          ALARM
M/B Temp:    +36°C  (low  =   +20°C, high =   +60°C)   sensor = thermistor
CPU Temp:     +8°C  (low  =   +20°C, high =   +60°C)   sensor = invalid
Temp3:       +48°C  (low  =   +20°C, high =   +60°C)   sensor = thermistor


Looks like I can trust the temperature reading of M/B Temp and Temp3 (which has to be the CPU Temp).

As you can see, some readings are wrong. I already took a look at the sensors.conf, but I am totally lost there.

Maybe someone has a clue how to correct the readings for the SiS 735 ???

The other thing:

I'd like to have the temperature readings posted to a webpage, so that I can check on these data using a webbrowser (apache2 is running on this machine). Can someone please tell me how to manage this in a simple way ???

It's about a webserver with an AMD Duron 1300 CPU, which is located in a small closet (due to the noise, this machine is pretty loud, it has two SCSI HDDs with 10.000 RPM). The temperature inside this closet is about 20°C, when the computer is switched off, and about 33-34°C with the computer running. I want to put another 3 computers inside this closet, and I need to be able to watch mobo- and CPU temperature on these.
_________________
Las torturas mentales de la CIA
Back to top
View user's profile Send private message
calhoun
Tux's lil' helper
Tux's lil' helper


Joined: 14 Nov 2003
Posts: 91
Location: Point Pleasant, NJ

PostPosted: Sat Mar 06, 2004 7:39 pm    Post subject: Reply with quote

bump
Back to top
View user's profile Send private message
Lumen
n00b
n00b


Joined: 17 Sep 2002
Posts: 16
Location: Germany

PostPosted: Thu Mar 11, 2004 5:40 am    Post subject: Re: Compute line for lm_sensors Reply with quote

Hi JWicks,

the temperatures are "nearly" correct (somehow) with a Asus A7M266.
I have such a board.
lm-sensors computes temperatures by factor 10 to high (at least version 2.8.4 in conjunction with a A7M266)
So your output of the command 'sensors' means:
M/B Temp: +300°C -> 30.0°C (of course no real, accurate value)
CPU Temp: +490.0°C -> 49.0°C (of course no real, accurate value)
BTW pretty "nice" values. Mine are idle 33°C Mainboard and 54°C CPU. But this "has" to be, at least because i estimate my little Barton CPU hack has a significant higher thermal load. ;-)

*Older* lm-sensors versions did the job right, regarding the calculation of the temperatures of a A7M266 (at least on my system). So this misbehavior is a relative new quirk! [Please, read my update statement below.]

JWicks wrote:

...
Mobo: Asus A7M266, 1.2 Athalon .
...
Code:

$ sensors
as99127f-i2c-1-2d
Adapter: SMBus Via Pro adapter at e800
Algorithm: Unavailable from sysfs
VCore:     +1.89 V  (min =  +1.74 V, max =  +1.94 V)
+3.3V:     +3.28 V  (min =  +3.14 V, max =  +3.46 V)
+5V:       +4.84 V  (min =  +4.73 V, max =  +5.24 V)
+12V:     +12.52 V  (min = +10.82 V, max = +13.19 V)
-12V:     -12.20 V  (min = -13.18 V, max = -10.88 V)
-5V:       -5.30 V  (min =  -5.25 V, max =  -4.75 V)
fan1:     4891 RPM  (min = 5232 RPM, div = 2)
fan2:        0 RPM  (min =   -1 RPM, div = 2)
fan3:        0 RPM  (min = 4963 RPM, div = 2)
M/B Temp:   +300°C  (high =   +40°C, hyst =   +30°C)
CPU Temp: +490.0°C  (high =   +50°C, hyst =   +45°C)   ALARM  (beep)
temp3:      -5.0°C  (high =   +50°C, hyst =   +45°C)
vid:      +1.850 V
alarms:
beep_enable:
          Sound alarm enabled


Everything looks like its working and in the right value range,
except for the temp sensors.


You can manually correct this misbehavior in /etc/sensors.conf --> entry as99127f-* (or direct in the configuration settings of the possible GUI client - for example ksensors or gkrellm2). If you use older versions of lm-sensors than 2.8.4 the responsible entry in /etc/sensors.conf could have other names - for example w83782d.
Concretely, a example for the MoBo temp compute line:
compute temp1 @/10, @*10
More information in the readme header of /etc/sensors.conf
BTW: The third temperature value in your printout belongs to a not connected temperature sensor on the motherboard. The name of the connector on the MoBo is JTPWR. Asus defines this as the possibility of a temperature sensor for the PSU. You can hook up your own "usual in the trade" foil temperature sensor there, if you want. Then you will also get proper readings on this value slot.

UPDATE:
Just installed lm-sensors 2.8.5. It seems to me, that this version corrects the problem with the factor 10 to high reporting of temperatures on the Asus A7M266, at least on my system! -> So, just unmask and install lm-sensors 2.8.5 if you don't have to fear problems with your tv/video-equipment (e.g. bttv). It could/should somehow be helpful in some way. ;-)

JWicks wrote:

Code:

$  pwd
/sys/bus/i2c/devices/1-002d
$ cat temp_in*
30000
24500
-250


Looks like temp_input1 is cpu, temp_input2 is the mobo, and I have no idea what temp_input3 is but its probably wrong too.

Regarding /sys/bus/i2c/devices/*: (contrariwise);-)
temp_input1 is MoBo*1000, temp_input2 is CPU*500, and temp_input3 is not defined as long there is no real sensor connected (JTPWR).

So you will get MoBo temp with (temp_input1 div 1000)
and CPU temp with 2*(temp_input2 div 1000).
Okay, that was redundant. ;-)

JWicks wrote:

If anyone can give me some clues as to what I can use for the comput line to get these numbers to something resembling the BIOS, I would greatly appreciate it.

Sincerely,

-Wix

Look at the green "compute line" above in the text (and read the header of /etc/sensors.conf, especially the paragraph "compute lines", it should be there).
BTW Aware of the fact, in which bad manner such motherboards reads the cpu temperature, Asus decided that the BIOS has to report at least 10°C above the value results of the (otherwise) usual measuring procedure. Just now i can't prove this statement nor name a source, but i remember that i read that once a time on some scattered Asus support pages. But, of course you are interpreting the temperature readings at your very own risk! YMMV

Maybe this was kind of useful in some way
Lumen


Last edited by Lumen on Thu Mar 11, 2004 7:56 am; edited 6 times in total
Back to top
View user's profile Send private message
arkane
l33t
l33t


Joined: 30 Apr 2002
Posts: 918
Location: Phoenix, AZ

PostPosted: Thu Mar 11, 2004 6:29 am    Post subject: Reply with quote

Master One wrote:


I'd like to have the temperature readings posted to a webpage, so that I can check on these data using a webbrowser (apache2 is running on this machine). Can someone please tell me how to manage this in a simple way ???


To the same machine, or will another machine be the webserver?

Basically just write a simple shell script that runs the sensors app, wraps it with html tags, and toss it to a file.

like:

#!/bin/sh
MYSTUFF=`sensors`
echo '<html><body>' > /tmp/myhtmlpage.tmp
echo MYSTUFF >> /tmp/myhtmlpage.tmp
echo '</body></html>' >> /tmp/myhtmlpage.tmp
mv /tmp/myhtmlpage.tmp /var/www/localhost/htdocs/index.html


of course, that's if it's on the local machine. If it's on another machine, you'll need to setup either ftp, or scp.
Back to top
View user's profile Send private message
Master One
l33t
l33t


Joined: 25 Aug 2003
Posts: 754
Location: Austria

PostPosted: Thu Mar 11, 2004 10:01 am    Post subject: Reply with quote

Thank's arkane, I thought of such a quick and dirty solution, but in the meanwhile I did a complete reinstall on this machine, and I left out the sensor part, as I came to the conclusion, that it simply gets to hot in that closet, so I moved the server to another room, where no temperature issues are no more.
_________________
Las torturas mentales de la CIA
Back to top
View user's profile Send private message
wizard69
Apprentice
Apprentice


Joined: 22 Sep 2003
Posts: 178
Location: Berlin

PostPosted: Thu Mar 11, 2004 12:38 pm    Post subject: Reply with quote

THX for the howto work a dream if anybody is interested for the Asus A7N8X-E Deluxe or A7N8X Mobo you need the modules nforce2 and asb100

Module Size Used by
i2c_nforce2 4992 0
asb100 21376 1
i2c_sensor 2368 1 asb100
i2c_dev 8128 0
i2c_core 18308 4 i2c_nforce2,asb100,i2c_sensor,i2c_dev



isa module is not needed any more see

http://www2.lm-sensors.nu/~lm78/kernel26.html
Back to top
View user's profile Send private message
crazy-bee
Apprentice
Apprentice


Joined: 03 Jan 2003
Posts: 170

PostPosted: Sat Mar 13, 2004 3:34 pm    Post subject: Reply with quote

Hmm any help on that?

I use lm_sensors CVS with 2.6.4-mm1, and I have no problems. Sensors show correct values (AMD266-D)

as99127f-i2c-0-2d
Adapter: SMBus AMD756 adapter at e4e0
VCore 1: +1.66 V (min = +1.44 V, max = +1.86 V)
VCore 2: +1.66 V (min = +1.44 V, max = +1.86 V)
+3.3V: +3.31 V (min = +2.96 V, max = +3.63 V)
+5V: +4.97 V (min = +4.49 V, max = +5.51 V)
+12V: +12.10 V (min = +9.55 V, max = +14.41 V)
-12V: -3.43 V (min = -4.07 V, max = -0.32 V)
-5V: -0.75 V (min = -1.76 V, max = -0.82 V)
fan1: 4856 RPM (min = 42187 RPM, div = 2)
fan2: 5000 RPM (min = -1 RPM, div = 2)
fan3: 3068 RPM (min = -1 RPM, div = 2)
M/B Temp: +25�C (high = +0�C, hyst = +2�C)
CPU Temp: +39.0�C (high = +100�C, hyst = +75�C) (beep)
temp3: +40.5�C (high = +85�C, hyst = +75�C)
vid: +1.650 V
alarms:
beep_enable:
Sound alarm enabled

Looks great. BUT if I start gkrellm, the temperatures are not correct, they always display around 20-30 degress, while the output of sensors is correct and shows higher values.

Any idea? It must be something with gkrellm, but I dont know what else to do.
Back to top
View user's profile Send private message
MadEgg
l33t
l33t


Joined: 06 Jun 2002
Posts: 678
Location: Netherlands

PostPosted: Tue Mar 16, 2004 11:45 pm    Post subject: Reply with quote

I've got w83781d, i2c-isa, via868a, i2c-sensor and i2c-core loaded.

I do have some sensors now, but they don't do anything...

I get a constant 33 temperature on my CPU and a constant 29 temperature on my mainboard. Even when compiling a kernel or something like that.
It did jump around while I was still using 2.4.x a while ago. Does it just make up these readings?
_________________
Pentium 4 Prescott 3,2 GHz
Asus P4P800 SE, i865PE chipset
1024 MB PC3200 RAM
AOpen Aeolus GeForce 6800 Ultra 256 MB DDR2
Creative Audigy2 ZS
gentoo-sources-2.6.20-r7
nVidia-drivers version 9755
Back to top
View user's profile Send private message
Chilliwilli
n00b
n00b


Joined: 18 Mar 2004
Posts: 1

PostPosted: Thu Mar 18, 2004 4:40 pm    Post subject: Can't pull lm-sensors Reply with quote

Hi all,

Can't seem to pull any version of lm-sensors above 2.8.1 from portage.

Contents of /etc/portage/profile/package.unmask (my package.mask was in this profiles directory so i placed package.unmask here too.. doesn't work eith though if I place it at /usr/portage/package.unmask)
Code:

# allow lm_sensors userspace programs for kernel 2.6
=sys-apps/lm-sensors-2.8.5


Trying emerge with
Code:

#ACCEPT_KEYWORDS="~x86" emerge =lm-sensors-2.8.5


Get the following message
Code:

These are the packages that I would merge, in order:
 
Calculating dependencies
!!! all ebuilds that could satisfy "=lm-sensors-2.8.5" have been masked.
!!! possible candidates are:
- sys-apps/lm-sensors-2.8.5 (masked by: package.mask)
 
!!! Error calculating dependencies. Please correct.


Any ideas?
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: Thu Mar 18, 2004 6:18 pm    Post subject: Reply with quote

Put package.unmask to /etc/portage/package.unmask
_________________
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
m1rage
Tux's lil' helper
Tux's lil' helper


Joined: 11 Feb 2004
Posts: 82

PostPosted: Thu Mar 18, 2004 8:31 pm    Post subject: Reply with quote

Hi,

Been playing with this for the last couple of hours, compiled 4 kernels already :P finally getting some results.

Right now I can get the temp reading that are on LM90 (socket and diode) but not the fan, case and voltage reading.

My mobo is a Soltek SL75 FRN2 L (nForce2) it use (under windows w/ MBM5) :
Sensor chip :W83697HF
Case temp : Winbond 1
LM90 (remote) for diode + LM90 (local) for socket

Kernel version is 2.6.3-gentoo-r1, last compilation I included this :

I2C Support (*)
I2C Device interface (*)
I2C Algo (M) for both choice

I2C Hardware bus support -->
AMD 756/766 (M)
ISA Bus Support (M)
Nvidia nForce (M)

I2C Hardware sensors chip
National semiconductor LM75, LM78, LM83, LM85, LM90 (all as modules)
Winbond (both choice as modules, since I didn't know which I needed for my case temp.)

All went well when compiling and installing modules. I ran sensors got no sensors found. Umerged lm_sensors and emerged the latest version (2.8.5)

Loaded it :
Code:

root@neon jf # /etc/init.d/lm_sensors start
 * Loading lm_sensors modules...
 *   Loading i2c-nforce2...                                               [ ok ] *   Loading i2c-isa...                                                   [ ok ] *   Loading adm1021...                                                   [ !! ]
 *   Loading lm90...                                                      [ ok ] *   Loading eeprom...                                                    [ !! ]
 *   Loading w83627hf...                                                  [ !! ]


Now "sensors" output :

Code:
lm90-i2c-3-4c
Adapter: SMBus nForce2 adapter at 5000
M/B Temp:    +37�C  (low  =    +0�C, high =   +70�C)
CPU Temp:  +42.2�C  (low  =  +0.0�C, high = +70.0�C)
M/B Crit:    +85�C  (hyst =   +75�C)
CPU Crit:    +80�C  (hyst =   +70�C)


Configured gkrellm2, worked like a charm for those sensors...

Only thing I would like to have now is my fans sensors and my case temps. I don't care much about voltage, but it would be a nice addition ;)

Code:
root@neon linux # 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): 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
FATAL: Module i2c_nforce2 already in kernel.
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
FATAL: Module i2c_elektor not found.
Loading failed... skipping.
Load `i2c-elv' (say NO if built into your kernel)? (YES/no): y
FATAL: Module i2c_elv not found.
Loading failed... skipping.
Load `i2c-philips-par' (say NO if built into your kernel)? (YES/no): y
FATAL: Module i2c_philips_par not found.
Loading failed... skipping.
Load `i2c-velleman' (say NO if built into your kernel)? (YES/no): y
FATAL: Module i2c_velleman not found.
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
FATAL: Module i2c_dev not found.
 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).
 
Next adapter: SMBus nForce2 adapter at 5100 (Algorithm unavailable)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x08
 
Next adapter: SMBus nForce2 adapter at 5100 (Algorithm unavailable)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x08
Client at address 0x4c can not be probed - unload all client drivers first!
Client found at address 0x4e
Probing for `National Semiconductor LM75'... Failed!
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Analog Devices ADM1021'... Failed!
Probing for `Analog Devices ADM1021A/ADM1023'... Failed!
Probing for `Maxim MAX1617'... Success!
    (confidence 3, driver `adm1021')
Probing for `Maxim MAX1617A'... Failed!
Probing for `TI THMC10'... Failed!
Probing for `National Semiconductor LM84'... Success!
    (confidence 5, driver `adm1021')
Probing for `Genesys Logic GL523SM'... Failed!
Probing for `Onsemi MC1066'... Failed!
Probing for `National Semiconductor LM82'... Failed!
Probing for `National Semiconductor LM83'... Failed!
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
    (confidence 1, driver `eeprom')
 
 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 `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! (0x52)
Probing for `Winbond W83627HF Super IO Sensors'
  Success... found at address 0x0290
Probing for `Winbond W83627THF Super IO Sensors'
  Failed! (0x52)
Probing for `Winbond W83637HF Super IO Sensors'
  Failed! (0x52)
Probing for `Winbond W83697HF Super IO Sensors'
  Failed! (0x52)
Probing for `Winbond W83697UF Super IO PWM'
  Failed! (0x52)

 
 Now follows a summary of the probes I have just done.
 Just press ENTER to continue:
 
Driver `adm1021' (should be inserted):
  Detects correctly:
  * Bus `SMBus nForce2 adapter at 5100' (Algorithm unavailable)
    Busdriver `i2c-nforce2', I2C address 0x4e
    Chip `National Semiconductor LM84' (confidence: 5)
 
Driver `eeprom' (should be inserted):
  Detects correctly:
  * Bus `SMBus nForce2 adapter at 5100' (Algorithm unavailable)
    Busdriver `i2c-nforce2', I2C address 0x51
    Chip `SPD EEPROM' (confidence: 1)
 
Driver `w83781d' (may not be inserted):
  Misdetects:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `Winbond W83627HF' (confidence: 8)
 
Driver `w83627hf' (should be inserted):
  Detects correctly:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `Winbond W83627HF Super IO 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
 
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
#----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-nforce2
modprobe i2c-isa
# I2C chip drivers
modprobe adm1021
modprobe eeprom
modprobe w83627hf
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----end cut here----


As you can see it detect a Winbond sensor at 0x290 but modprobe w83626HF say that it can't find it...I don't think I got the choice to compile it in my kernel or as a module...could it be that my kernel doesn't support it yet?

Thanks for any help or ideas...I'm a complete linux noob, only been using it for 2 weeks so pardon me if the solution is obvious :wink:
_________________
m1rage
Back to top
View user's profile Send private message
anarka
n00b
n00b


Joined: 23 Mar 2004
Posts: 14
Location: Oporto,Portugal

PostPosted: Tue Mar 23, 2004 9:11 pm    Post subject: Reply with quote

m1rage : try forcing the driver,
run i2cdetect
then i2cdetect n (where n is the number of ur chip - if it ISA u can skip this step)
run: modprobe w83781d force_w83627hf=bus,address (where bus was revealed in the previous step and address == n) if it is ISA bus==9191


try it now.. i hope it works... report please :D
Back to top
View user's profile Send private message
Kow
Apprentice
Apprentice


Joined: 28 Dec 2003
Posts: 227

PostPosted: Wed Mar 24, 2004 3:50 am    Post subject: Reply with quote

NOTE: Anyone who tries using LM Sensors in 2.6.5-rc1 or newer kernels will not be able to retrieve sensor data via libsensors... A patch needs to be applied to lm-sensors because the kernel devels decided to change the whole naming scheme for the drivers and data making libsensor request for data from a name that does not exist... This is noted in the kernels changelog:

Quote:

<khali@linux-fr.org>
[PATCH] I2C: update for sysfs-interface documentation

<khali@linux-fr.org>
[PATCH] I2C: rename sysfs files, part 1 of 2

Here it is. The associated libsensors patch is here:
http://jdelvare.net1.nerim.net/sensors/libsensors-sysfs-names-1.diff
(not applied yet, on purpose)

<khali@linux-fr.org>
[PATCH] I2C: rename sysfs files, part 2 of 2

Here is the second step of my sysfs renaming plan.

This one does the following renames (as I already announced on the
LKML):
temp<n>_hyst -> temp<n>_max_hyst or temp<n>_crit_hyst
sensor<n> -> temp<n>_type
pwm<n> -> fan<n>_pwm
pwm<n>_enable -> fan<n>_pwm_enable
vid -> in<n>_ref

The associated libsensors patch is here:
http://jdelvare.net1.nerim.net/sensors/libsensors-sysfs-names-2.diff
(not applied yet, on purpose)


Note that the w83781d part is a bit more complex, not only because it is
the only driver to require the 5 changes, but also because at some point
the macros assume that the internal variable names match the sysfs
names, so I had to change them too (better than rewriting the macros,
methinks).

For reference, here is the list of changes, by driver:

asb100:
hyst -> max_hyst (4)
pwm -> fan_pwm (1)
pwm_enable -> fan_pwm_enable (1)
vid -> in_ref (1)
fscher:
pwm -> fan_pwm (3)
gl518sm:
hyst -> max_hyst (1)
it87:
sensor -> temp_type (3)
lm75:
hyst -> max_hyst (1)
lm78:
hyst -> max_hyst (1)
vid -> in_ref (1)
lm85:
pwm -> fan_pwm (3)
pwm_enable -> fan_pwm_enable (3)
vid -> in_ref (1)
lm90:
hyst -> crit_hyst (2)
via686a:
hyst -> max_hyst (3)
w83781d:
hyst -> max_hyst (2)
sensor -> temp_type (3)
pwm -> fan_pwm (4)
pwm_enable -> fan_pwm_enable (1)
vid -> in_ref (1)

There's also a documentation update. There will be one more after that
(to make it more readable, no contents change), and a patch to lm83.c to
bring it to compliance with the (new) standard. (If you wonder why I did
not change it with the other drivers: because it was *already* not in
compliance with the old standard. There's some real work to do for this
one.)


It's really up to lm-sensors to get this patch in their source.

I thought i'd heads up those who don't know and plan on using 2.6.5-rc1 or newer using lm-sensors.
_________________
-Kow
Back to top
View user's profile Send private message
m1rage
Tux's lil' helper
Tux's lil' helper


Joined: 11 Feb 2004
Posts: 82

PostPosted: Wed Mar 24, 2004 9:55 pm    Post subject: Reply with quote

Thanks anarka! I tried what you said and now I have reading for everything that I have sensors for.

I've lost my lm_sensors output for some reason and don't have much time to work getting them back yet, but that should be easy since I got them to work once. At least my Winbond sensors are working now thanks to you!

EDIT : reboot messed things up :P

Ok, I followed the step I previously taken to get my other sensors to work and they are working now, but can't get the reading from the Winbond one again following your method that worked a few minutes ago...so there's obviously something I'm missing here.

Here's the output of a few things :

root@neon jf # sensors
lm90-i2c-3-4c
Adapter: SMBus nForce2 adapter at 5000
M/B Temp: +39�C (low = +0�C, high = +70�C)
CPU Temp: +45.0�C (low = +0.0�C, high = +70.0�C)
M/B Crit: +85�C (hyst = +75�C)
CPU Crit: +80�C (hyst = +70�C)

root@neon jf # i2cdetect
Error: No i2c-bus specified!
Syntax: i2cdetect I2CBUS
I2CBUS is an integer
i2cdetect -l lists installed busses only
Installed I2C busses:
i2c-2 dummy ISA main adapter ISA bus algorithm
i2c-1 unknown SMBus nForce2 adapter at 5100 Algorithm unavailable
i2c-0 unknown SMBus nForce2 adapter at 5100 Algorithm unavailable


root@neon jf # i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0
You have five seconds to reconsider and press CTRL-C!

0 1 2 3 4 5 6 7 8 9 a b c d e f
00: XX XX XX XX XX XX XX XX 08 XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX XX XX XX XX XX XX XX XX XX UU XX 4e XX
50: XX 51 XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX

root@neon jf # i2cdetect 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1
You have five seconds to reconsider and press CTRL-C!

0 1 2 3 4 5 6 7 8 9 a b c d e f
00: XX XX XX XX XX XX XX XX 08 XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX

root@neon jf # modprobe w83781d force_w83627hf=5100,0
FATAL: Module w83781d already in kernel.
root@neon jf # modprobe w83781d force_w83627hf=5100,1
FATAL: Module w83781d already in kernel.
root@neon jf # modprobe w83781d force_w83627hf=9191,2
FATAL: Module w83781d already in kernel.

sensors still output the following :
lm90-i2c-3-4c
Adapter: SMBus nForce2 adapter at 5000
M/B Temp: +40�C (low = +0�C, high = +70�C)
CPU Temp: +45.8�C (low = +0.0�C, high = +70.0�C)
M/B Crit: +85�C (hyst = +75�C)
CPU Crit: +80�C (hyst = +70�C)

Now from what I understand (which is very little) the module for my Winbonds sensors are loaded but are not working anymore now that my others are?
_________________
m1rage
Back to top
View user's profile Send private message
m1rage
Tux's lil' helper
Tux's lil' helper


Joined: 11 Feb 2004
Posts: 82

PostPosted: Wed Mar 24, 2004 11:31 pm    Post subject: Reply with quote

Okie,

I got it now I think, thanks anarka for your reply. I added i2c-dev to my /etc/conf.d/lm_sensors manually and restarted lm_sensors and now the command "sensors" output everything. I was using the config file generated by sensors-detect prior to that.

For now it's working ok, now I'll reboot just to make sure I did it right :roll:

----------------------------------------------

EDIT : I finally was able to reboot and keep my sensors (I know this sound trivial to many but not to me being a complete noob to linux and the whole modules thing. Just getting this to work helped me a lot in understanding better how the whole thing is working even though there's so much more to learn. Anyway, I thought I would post my config and how I got it to work resumed in a more concise post so that someone searching the forum would be able to get it to work more quickly, so here it goes :

Motherboard : Soltek 75FRN2
Controller : Nforce2
Sensors : LM90 (for CPU) and Winbonds (For case)

I compiled the relevant part of my kernel as follow :

Code:

# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y
                                                                                                                                                           
#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m
                                                                                                                                                           
#
# I2C Hardware Bus support
#
CONFIG_I2C_AMD756=m
CONFIG_I2C_ISA=m
CONFIG_I2C_NFORCE2=m

#
# I2C Hardware Sensors Chip support
#
CONFIG_I2C_SENSOR=m

CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83L785TS=m


Then I emerged lm-sensors 2.8.5 which was masked. I ran sensors-detect to generate a working /etc/conf.d/lm_sensors

Then started lm_sensors
/etc/init.d/lm_sensors start

With that when running "sensors" I would get the reading from the lm90 sensors (CPU diode and socket)

I then followed anarka's tips and did :

i2cdetect which returned 2 sensors at address 5100.
i2cdetect 0 did it's stuff, i2cdetect 1 did it's stuff (not sure what though, but it seemed to probe the sensor, anarka?)

Then :
modprobe w83781d force_w83627hf=5100,0
modprobe w83781d force_w83627hf=5100,1

Now all sensors should be working using "sensors"

Now I edited my /etc/conf.d/lm_sensors to keep only what I knew I needed
Code:

MODULE_0=i2c-nforce2
MODULE_1=i2c-isa
MODULE_2=lm90
MODULE_3=w83781d


Ran modules-update

Restarted lm_sensors to make sure everything was still working :
/etc/init.d/lm_sensors restart

And voila! finally everything is working and the setting were kept when I rebooted. Millions of thanks to Master_Of_Disaster for such a good thread, thank you also to anarka who solved my problem :)

Hope this will help someone else in with the same board.

P.S. I probably didn't need to compile LM75, LM78, LM83, LM85 and W83L785TS as module but I played it safe and will try removing them when I come to compiling again.

EDIT 2 : I recompiled my kernel yesterday and removed support for LM75, 78, 83, 85 and W83L785TS and it's working still. You only need LM90 and w83781d hardware sensors chip for this board.
_________________
m1rage


Last edited by m1rage on Sun Mar 28, 2004 10:08 pm; edited 1 time in total
Back to top
View user's profile Send private message
kai
n00b
n00b


Joined: 12 Jun 2002
Posts: 53
Location: Oakland, CA

PostPosted: Fri Mar 26, 2004 3:33 am    Post subject: Reply with quote

I apologize in advance if this has been answered somewhere in the middle of this thread. I've scanned the thread, but haven't read all 8 pages 8O

When I try to emerge lm-sensors, i2c is listed as a dependency but it won't emerge b/c I'm using kernel 2.6.

Code:
[root@Gentoo src]$ emerge -p lm-sensors

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild  N    ] sys-apps/i2c-2.8.1
[ebuild  N    ] sys-apps/lm-sensors-2.8.1


Do I need to emerge a later version of lm-sensors? Everything after 2.8.1 is in packages.mask and I am generally uncomfortable emerging those packages.
Back to top
View user's profile Send private message
kai
n00b
n00b


Joined: 12 Jun 2002
Posts: 53
Location: Oakland, CA

PostPosted: Fri Mar 26, 2004 5:47 am    Post subject: Reply with quote

got it working.

I unmasked lm-sensors-2.8.5 and everything worked fine.
Back to top
View user's profile Send private message
BlackB1rd
Tux's lil' helper
Tux's lil' helper


Joined: 13 Aug 2003
Posts: 131
Location: /Europe/Netherlands/Haarlem

PostPosted: Sat Mar 27, 2004 2:48 pm    Post subject: Reply with quote

@ Topicstarter:

Look at this thread for a increase of speed work-around: https://forums.gentoo.org/viewtopic.php?t=51756

It works for me and I guess for all Shuttle XPC owners :)
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: Sat Mar 27, 2004 3:13 pm    Post subject: Reply with quote

It's fixed in 2.6.5-rc2-mm4, it87.c has a parameter which does the trick. I created a patch for earlier kernel versions.
_________________
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
BlackB1rd
Tux's lil' helper
Tux's lil' helper


Joined: 13 Aug 2003
Posts: 131
Location: /Europe/Netherlands/Haarlem

PostPosted: Sat Mar 27, 2004 3:15 pm    Post subject: Reply with quote

Good to hear, didn't know that :) It took a long time to get fixed...
Back to top
View user's profile Send private message
renderedbrian
n00b
n00b


Joined: 22 Mar 2004
Posts: 15

PostPosted: Sat Apr 10, 2004 10:56 pm    Post subject: Reply with quote

I have the it87 module loaded on kernel 2.6.4 - but I seem to be missing pwm control of the fans :-(

Code:

ls /sys/bus/i2c/devices/7-0290/
alarms        fan_min1   in_input5  in_max4  in_min4  sensor3      temp_min2
detach_state  fan_min2   in_input6  in_max5  in_min5  temp_input1  temp_min3
fan_div1      fan_min3   in_input7  in_max6  in_min6  temp_input2
fan_div2      in_input0  in_input8  in_max7  in_min7  temp_input3
fan_div3      in_input1  in_max0    in_min0  name     temp_max1
fan_input1    in_input2  in_max1    in_min1  power    temp_max2
fan_input2    in_input3  in_max2    in_min2  sensor1  temp_max3
fan_input3    in_input4  in_max3    in_min3  sensor2  temp_min1



code]bash-2.05b# lsmod
Module Size Used by
it87 22280 0
i2c_isa 2176 0
i2c_viapro 6412 0
i2c_dev 9216 0
eeprom 6728 0
i2c_sensor 2816 2 it87,eeprom
[/code]

I really wish I could get pwm control enabled, then I could silence my so called "silent" cpu fan (A thermaltake Silent Boost)

--
brian
[
Back to top
View user's profile Send private message
Helena
Veteran
Veteran


Joined: 02 Apr 2003
Posts: 1067
Location: Den Dolder, The Netherlands

PostPosted: Tue Apr 13, 2004 2:46 pm    Post subject: Reply with quote

kai wrote:
got it working.

I unmasked lm-sensors-2.8.5 and everything worked fine.
pls tell me the trick, because I'm stuck at the same point. here's my /etc/portage/package.unmask:
Code:

# new kde versions mask - will clean up shortly
=kde-base/kde-3.2.0
=kde-base/kde-i18n-3.2.0
=kde-base/kdeaccessibility-3.2.0
=kde-base/kdeadmin-3.2.0
=kde-base/kdeaddons-3.2.0
=kde-base/kdeartwork-3.2.0
=kde-base/kdebindings-3.2.0
=kde-base/kdeedu-3.2.0
=kde-base/kdegames-3.2.0
=kde-base/kdegraphics-3.2.0
=kde-base/kdesdk-3.2.0
=kde-base/kdetoys-3.2.0
=kde-base/kdeutils-3.2.0
=kde-base/kdemultimedia-3.2.0
=kde-base/kdepim-3.2.0
=kde-base/kdenetwork-3.2.0
=kde-base/kdelibs-3.2.0
=kde-base/kdebase-3.2.0
=kde-base/arts-1.2.0
=sys-apps/lm-sensors-2.8.4
=sys-apps/i2c-2.8.4
but if i try to emerge I get the following:
Code:
AjaxGentoo root # emerge -pv =lm-sensors-2.8.4

These are the packages that I would merge, in order:

Calculating dependencies
!!! all ebuilds that could satisfy "=lm-sensors-2.8.4" have been masked.
!!! possible candidates are:
- sys-apps/lm-sensors-2.8.4 (masked by: -keyword)

!!! Error calculating dependencies. Please correct.
AjaxGentoo root # emerge -pv lm-sensors

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild  N    ] sys-apps/i2c-2.8.4   134 kB
[ebuild  N    ] sys-apps/lm-sensors-2.8.1   687 kB

Total size of downloads: 821 kB
I need lm-sensors-2.8.2 or greater however, because that supports my ASB100 sensor chip.
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 ... 7, 8, 9, 10, 11  Next
Page 8 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