linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>
To: lm78@stimpy.netroedge.com
Cc: linux-kernel@vger.kernel.org
Subject: Sensors and linux 2.6.0-test4-bk8 question
Date: Sun, 07 Sep 2003 13:27:14 +0200	[thread overview]
Message-ID: <1062934034.7923.2.camel@rousalka.dyndns.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3661 bytes --]

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,

-- 
Nicolas Mailhot

[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-09-07 11:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-07 11:27 Nicolas Mailhot [this message]
2003-09-07 15:09 ` Sensors and linux 2.6.0-test4-bk8 question Ton Hospel
2003-09-07 17:35   ` Josh McKinney
     [not found]   ` <20030907173515.GA15338@_orming>
2003-09-07 20:17     ` Ton Hospel
2003-09-09 17:06       ` Ton Hospel
2003-09-07 16:38 Nicolas Mailhot
2003-09-08  6:20 "Andrey Borzenkov" 

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1062934034.7923.2.camel@rousalka.dyndns.org \
    --to=nicolas.mailhot@laposte.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm78@stimpy.netroedge.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).