Skip to contentSkip to conversation

Sensors and linux 2.6.0-test4-bk8 question

DISCUSSION Nicolas Mailhot 3 participants 6 messages Sep 7, 2003 – May 19, 2005 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

Hi,

Please bear with me and enlighten me a bit. I've been fiddling with 2.5/2.6 for some time, and got most of my hardware working (including acpi...) better than in 2.4. (in fact now I'm using only 2.6). So now I got to the point where I'm looking at nice-to-have stuff like sensors.

I know libsensors is not yet 2.6 aware, but I thought sensed values where available in sysfs if one wanted to manually read them. Since I have via hardware:

00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge 00:0a.0 RAID bus controller: CMD Technology Inc PCI0680 (rev 02) 00:0c.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] (rev 01) 00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06)
00:13.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04)

I build-in via-pro and VIA686A:
CONFIG_I2C_VIAPRO=y
CONFIG_SENSORS_VIA686A=y

Now there is no sensor-related message as far as I can see in my dmesg, and I do not seem to find any temperature/fan related info in /sys:

root@rousalka root]# find /sys/| grep i2c /sys/class/i2c-dev
/sys/class/i2c-dev/i2c-3 /sys/class/i2c-dev/i2c-3/dev /sys/class/i2c-dev/i2c-3/driver /sys/class/i2c-dev/i2c-3/device /sys/class/i2c-dev/i2c-2 /sys/class/i2c-dev/i2c-2/dev /sys/class/i2c-dev/i2c-2/driver /sys/class/i2c-dev/i2c-2/device /sys/class/i2c-dev/i2c-1 /sys/class/i2c-dev/i2c-1/dev /sys/class/i2c-dev/i2c-1/driver /sys/class/i2c-dev/i2c-1/device /sys/class/i2c-dev/i2c-0 /sys/class/i2c-dev/i2c-0/dev /sys/class/i2c-dev/i2c-0/driver /sys/class/i2c-dev/i2c-0/device /sys/class/i2c-adapter /sys/class/i2c-adapter/i2c-3 /sys/class/i2c-adapter/i2c-3/driver /sys/class/i2c-adapter/i2c-3/device /sys/class/i2c-adapter/i2c-2 /sys/class/i2c-adapter/i2c-2/driver /sys/class/i2c-adapter/i2c-2/device /sys/class/i2c-adapter/i2c-1 /sys/class/i2c-adapter/i2c-1/driver /sys/class/i2c-adapter/i2c-1/device /sys/class/i2c-adapter/i2c-0 /sys/class/i2c-adapter/i2c-0/driver /sys/class/i2c-adapter/i2c-0/device /sys/bus/i2c
/sys/bus/i2c/drivers /sys/bus/i2c/drivers/dev_driver /sys/bus/i2c/drivers/i2c_adapter /sys/bus/i2c/devices /sys/devices/pci0000:00/0000:00:11.0/i2c-3 /sys/devices/pci0000:00/0000:00:11.0/i2c-3/name /sys/devices/pci0000:00/0000:00:11.0/i2c-3/power /sys/devices/pci0000:00/0000:00:11.0/i2c-3/power/state /sys/devices/pci0000:00/0000:00:11.0/i2c-3/detach_state /sys/devices/legacy/i2c-2 /sys/devices/legacy/i2c-2/name /sys/devices/legacy/i2c-2/power /sys/devices/legacy/i2c-2/power/state /sys/devices/legacy/i2c-2/detach_state /sys/devices/legacy/i2c-1 /sys/devices/legacy/i2c-1/name /sys/devices/legacy/i2c-1/power /sys/devices/legacy/i2c-1/power/state /sys/devices/legacy/i2c-1/detach_state /sys/devices/legacy/i2c-0 /sys/devices/legacy/i2c-0/name /sys/devices/legacy/i2c-0/power /sys/devices/legacy/i2c-0/power/state /sys/devices/legacy/i2c-0/detach_state /sys/cdev/major/i2c

So I'd like to know how I'm supposed to check if the kernel sensors part works (and eventualy get some useful info out of it)

Regards,

Signature · 1 line
Nicolas Mailhot
#1 lore raw

In article <[email protected]>,

Quoted 6 lines · Nicolas Mailhot

--=-scQmpSv1XJXK2Qdu4l48
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi,

Quoted 8 lines

Please bear with me and enlighten me a bit. I've been fiddling with 2.5/2.6 for some time, and got most of my hardware working (including acpi...) better than in 2.4. (in fact now I'm using only 2.6). So now I got to the point where I'm looking at nice-to-have stuff like sensors.

I know libsensors is not yet 2.6 aware, but I thought sensed values where available in sysfs if one wanted to manually read them. Since I have via hardware:

If there is any interest, I have a perl program that does a configurable display for 2.6

Quoted 4 lines

Now there is no sensor-related message as far as I can see in my dmesg, and I do not seem to find any temperature/fan related info in /sys:

You still need the bus and chip drivers before anything appears. Which ones is basically the same as with the old lmsensors stuff, so look in their docs.

#2 lore raw
Quoted 13 lines · Ton Hospel

In article <[email protected]>,

Quoted 11 lines · Nicolas Mailhot

--=-scQmpSv1XJXK2Qdu4l48
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi,

Please bear with me and enlighten me a bit. I've been fiddling with 2.5/2.6 for some time, and got most of my hardware working (including acpi...) better than in 2.4. (in fact now I'm using only 2.6). So now I got to the point where I'm looking at nice-to-have stuff like sensors.

Quoted 7 lines
Quoted 3 lines

I know libsensors is not yet 2.6 aware, but I thought sensed values where available in sysfs if one wanted to manually read them. Since I have via hardware:

If there is any interest, I have a perl program that does a configurable display for 2.6

That perl script would be nice. You could send it to me privately or the list if its not to big then it would be in the archives.

Thanks

Signature · 6 lines
Josh McKinney		     |	Webmaster: http://joshandangie.org
--------------------------------------------------------------------------
                             | They that can give up essential liberty
Linux, the choice       -o)  | to obtain a little temporary safety deserve 
of the GNU generation    /\  | neither liberty or safety. 
                        _\_v |                          -Benjamin Franklin

A message that is not in the archive (sent off-list or not yet received): 20030907173515.GA15338@_orming

#4 lore raw

In article <20030907173515.GA15338@_orming>,

Quoted 8 lines · Josh McKinney
Quoted 3 lines

If there is any interest, I have a perl program that does a configurable display for 2.6

That perl script would be nice. You could send it to me privately or the list if its not to big then it would be in the archives.

Thanks

See http://www.xs4all.nl/~thospel/ASIS/bin/psensors

#6 lore raw
In reply to Nicolas Mailhot

Ton Hospel replied to me

|> I know libsensors is not yet 2.6 aware, but I thought sensed values
|> where available in sysfs if one wanted to manually read them. Since I
|> have via hardware:

|If there is any interest, I have a perl program that does a configurable |display for 2.6.

Sure there is interest:)

|> 
|> Now there is no sensor-related message as far as I can see in my dmesg,
|> and I do not seem to find any temperature/fan related info in /sys:
|> 
|You still need the bus and chip drivers before anything appears.
|Which ones is basically the same as with the old lmsensors stuff, so
|look in their docs.

But how can I check the damn things work ? Sensors writers seem to have eschewed the nice messages every other driver writer put in dmesg to tell me their stuff is correctly loaded.

For example I have :
"SMBus Via Pro adapter at 5000"

in "/sys/devices/pci0000:00/0000:00:11.0/i2c-3/name" so I suppose via-pro at least is loaded (fully ?). Which should be the bus stuff I think. For the chip stuff that would be VIA686A (?) But how am I supposed to check the darn thing works with nothing in dmesg ? I've already combed sysfs for clues and found nothing.

Regards,

Signature · 8 lines
Nicolas Mailhot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Ceci est une partie de message
	=?ISO-8859-1?Q?numériquement?= =?ISO-8859-1?Q?_signée?Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20030907/729e67e5/attachment.bin