Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263075AbTIGL1Z (ORCPT ); Sun, 7 Sep 2003 07:27:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262994AbTIGL1V (ORCPT ); Sun, 7 Sep 2003 07:27:21 -0400 Received: from nan-smtp-06.noos.net ([212.198.2.75]:27155 "EHLO smtp.noos.fr") by vger.kernel.org with ESMTP id S263075AbTIGL1Q (ORCPT ); Sun, 7 Sep 2003 07:27:16 -0400 Subject: Sensors and linux 2.6.0-test4-bk8 question From: Nicolas Mailhot To: lm78@stimpy.netroedge.com Cc: linux-kernel@vger.kernel.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-scQmpSv1XJXK2Qdu4l48" Organization: Adresse personnelle Message-Id: <1062934034.7923.2.camel@rousalka.dyndns.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 (1.4.4-5) Date: Sun, 07 Sep 2003 13:27:14 +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4324 Lines: 127 --=-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. 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=3Dy CONFIG_SENSORS_VIA686A=3Dy 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, --=20 Nicolas Mailhot --=-scQmpSv1XJXK2Qdu4l48 Content-Type: application/pgp-signature; name=signature.asc Content-Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA/WxYRI2bVKDsp8g0RAqcvAKC9qYkkSTUD403m+UvJIdXzPCvgxQCeIWGA aUY8iTMYfLP18nRlPisFzDw= =Of0j -----END PGP SIGNATURE----- --=-scQmpSv1XJXK2Qdu4l48-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/