* sensors vs 2.6
@ 2003-12-09 7:58 Gene Heskett
2003-12-09 10:33 ` Sebastian Kaps
0 siblings, 1 reply; 9+ messages in thread
From: Gene Heskett @ 2003-12-09 7:58 UTC (permalink / raw)
To: linux-kernel
It seems we are not going to have working hardware sesnors in time for
2.6. Its my understanding that the data locations for the i2c stuffs
in the new kernel have been moved. I've got all that turned on in my
kernel, 2.6.0-test11, and have dilligently searched the /proc and
/sys directories, and seem to have come up blank.
Does it take an external program to trigger the storage of such data
as the cpu temps etc in one of these pseudo dirs? If not, how would
I go about decodeing whats there?
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: sensors vs 2.6
2003-12-09 7:58 sensors vs 2.6 Gene Heskett
@ 2003-12-09 10:33 ` Sebastian Kaps
2003-12-09 12:41 ` Gene Heskett
0 siblings, 1 reply; 9+ messages in thread
From: Sebastian Kaps @ 2003-12-09 10:33 UTC (permalink / raw)
To: gene.heskett; +Cc: linux-kernel
Hi Gene!
On Tue, 9 Dec 2003 02:58:01 -0500 you wrote:
> kernel, 2.6.0-test11, and have dilligently searched the /proc and
> /sys directories, and seem to have come up blank.
I have configured "I2C support", "I2C device interface", "Intel PIIX4"
and "Winbond ...". I get all sensor readings in /sys/bus/i2c/devices/*,
e.g.:
,----
| # cat /sys/bus/i2c/devices/0-002d/fan_input1
| 5400
`----
--
Ciao, Sebastian
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: sensors vs 2.6
2003-12-09 10:33 ` Sebastian Kaps
@ 2003-12-09 12:41 ` Gene Heskett
2003-12-09 14:18 ` Tomasz Torcz
2003-12-09 14:54 ` Stian Jordet
0 siblings, 2 replies; 9+ messages in thread
From: Gene Heskett @ 2003-12-09 12:41 UTC (permalink / raw)
To: Sebastian Kaps; +Cc: linux-kernel
On Tuesday 09 December 2003 05:33, Sebastian Kaps wrote:
>Hi Gene!
>
>On Tue, 9 Dec 2003 02:58:01 -0500 you wrote:
>> kernel, 2.6.0-test11, and have dilligently searched the /proc and
>> /sys directories, and seem to have come up blank.
>
>I have configured "I2C support", "I2C device interface", "Intel
> PIIX4" and "Winbond ...". I get all sensor readings in
> /sys/bus/i2c/devices/*, e.g.:
I have this:
-----------------------
[root@coyote linux-2.6]# grep I2C .config
# I2C support
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y
# I2C Algorithms
CONFIG_I2C_ALGOBIT=y
# CONFIG_I2C_ALGOPCF is not set
# I2C Hardware Bus support
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_I810 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_PHILIPSPAR is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_PROSAVAGE is not set
# CONFIG_I2C_SAVAGE4 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
CONFIG_I2C_VIA=y
CONFIG_I2C_VIAPRO=y
# CONFIG_I2C_VOODOO3 is not set
# I2C Hardware Sensors Chip support
CONFIG_I2C_SENSOR=y
----------------
and this:
-----------------
[root@coyote linux-2.6]# grep SENSORS .config
# CONFIG_SENSORS_ADM1021 is not set
CONFIG_SENSORS_EEPROM=y
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM85 is not set
CONFIG_SENSORS_VIA686A=y
CONFIG_SENSORS_W83781D=y
---------------------
set for a Biostar M7VIB mobo. It all works for 2.4.
No errors were noted during the build other than the advansys
deprecated "check_region" calls that have been noted here previously.
But:
--------------------
[root@coyote linux-2.6]# tree /sys/bus/i2c/devices/
/sys/bus/i2c/devices/
|-- 0-0050 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0050
|-- 0-0051 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0051
|-- 0-0052 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0052
|-- 0-0053 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0053
|-- 0-0054 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0054
|-- 0-0055 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0055
|-- 0-0056 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0056
|-- 0-0057 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0057
|-- 0-0061 -> ../../../devices/pci0000:00/0000:00:09.0/i2c-0/0-0061
|-- 1-0050 -> ../../../devices/pci0000:00/0000:00:11.0/i2c-1/1-0050
`-- 1-0051 -> ../../../devices/pci0000:00/0000:00:11.0/i2c-1/1-0051
11 directories, 0 files
-----------------------
And ALL of that is related to the various eeproms in the system.
Mostly on my bt979 card.
To back out and do a tree on /sys/devices gets me 171 directories and
583 files, none of which are named 'input_fan1'.
So obviously something didn't get built, and it looks like its the
winbond stuff. The question is why? Is there some method that can
be used to interrogate the kernel and determine if the stuff is
actually in there?
>,----
>
>| # cat /sys/bus/i2c/devices/0-002d/fan_input1
>| 5400
>
>`----
No such subdir in the devices dir...
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: sensors vs 2.6
2003-12-09 12:41 ` Gene Heskett
@ 2003-12-09 14:18 ` Tomasz Torcz
2003-12-09 16:00 ` Gene Heskett
2003-12-09 14:54 ` Stian Jordet
1 sibling, 1 reply; 9+ messages in thread
From: Tomasz Torcz @ 2003-12-09 14:18 UTC (permalink / raw)
To: LKML
On Tue, Dec 09, 2003 at 07:41:31AM -0500, Gene Heskett wrote:
> So obviously something didn't get built, and it looks like its the
> winbond stuff. The question is why? Is there some method that can
> be used to interrogate the kernel and determine if the stuff is
> actually in there?
Maybe related: via sensors stuff is very picky about order of module
loading.
It does NOT work when i2c-dev, i2c-algo-bit and rest of sensors stuff
(isa bus, via modules) are built INTO kernel.
When everything is in modules, iw works ONLY when via modules are
modprobed _before_ anything using i2c.
Loading other i2c modules (bttv, lirc or sth else) before via modules
makes sensors unusable - there is no /sys/[...]/via directory,
or this directory is empty.
--
Tomasz Torcz "Funeral in the morning, IDE hacking
zdzichu@irc.-nie.spam-.pl in the afternoon and evening." - Alan Cox
|> Playing: stream1.jungletrain.net:8000 ...
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: sensors vs 2.6
2003-12-09 14:18 ` Tomasz Torcz
@ 2003-12-09 16:00 ` Gene Heskett
0 siblings, 0 replies; 9+ messages in thread
From: Gene Heskett @ 2003-12-09 16:00 UTC (permalink / raw)
To: Tomasz Torcz, LKML
On Tuesday 09 December 2003 09:18, Tomasz Torcz wrote:
>On Tue, Dec 09, 2003 at 07:41:31AM -0500, Gene Heskett wrote:
>> So obviously something didn't get built, and it looks like its the
>> winbond stuff. The question is why? Is there some method that
>> can be used to interrogate the kernel and determine if the stuff
>> is actually in there?
>
>Maybe related: via sensors stuff is very picky about order of module
>loading.
>It does NOT work when i2c-dev, i2c-algo-bit and rest of sensors
> stuff (isa bus, via modules) are built INTO kernel.
>When everything is in modules, iw works ONLY when via modules are
>modprobed _before_ anything using i2c.
>Loading other i2c modules (bttv, lirc or sth else) before via
> modules makes sensors unusable - there is no /sys/[...]/via
> directory, or this directory is empty.
Humm, I've got a bt878 tv card thats rather noisey when eeprom inits.
This sounds like a change in the order the kernel inits this stuff
might be in order but I've NDI howto go about that... According to
dmesg, all that bttv stuff is found about 1000 lines before the first
mention of i2c... I assume that means I'd have to modularize the
bttv stuffs too so the init order can be conmtrolled?
If I make all that into modules, do you have a working modules.conf I
can obtain so that this stuff is brought in in the proper order?
I tried it without the VIA686, didn't see anything missing that wasn't
before, then found I had both VIA and VIAPRO set=y. I don't have a
VIA 586 chipset, so I turned that off and its remaking now for
effects. Somehow I think its gonna be a wasted reboot from what you
are telling me.
Thanks a bunch for any further assistance you can render.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: sensors vs 2.6
2003-12-09 12:41 ` Gene Heskett
2003-12-09 14:18 ` Tomasz Torcz
@ 2003-12-09 14:54 ` Stian Jordet
2003-12-09 15:21 ` Gene Heskett
1 sibling, 1 reply; 9+ messages in thread
From: Stian Jordet @ 2003-12-09 14:54 UTC (permalink / raw)
To: gene.heskett; +Cc: Sebastian Kaps, linux-kernel
tir, 09.12.2003 kl. 13.41 skrev Gene Heskett:
> I have this:
> -----------------------
> [root@coyote linux-2.6]# grep I2C .config
> # I2C support
> CONFIG_I2C=y
> CONFIG_I2C_CHARDEV=y
> # I2C Algorithms
> CONFIG_I2C_ALGOBIT=y
> # CONFIG_I2C_ALGOPCF is not set
> # I2C Hardware Bus support
> # CONFIG_I2C_ALI1535 is not set
> # CONFIG_I2C_ALI15X3 is not set
> # CONFIG_I2C_AMD756 is not set
> # CONFIG_I2C_AMD8111 is not set
> # CONFIG_I2C_I801 is not set
> # CONFIG_I2C_I810 is not set
> # CONFIG_I2C_NFORCE2 is not set
> # CONFIG_I2C_PHILIPSPAR is not set
> # CONFIG_I2C_PIIX4 is not set
> # CONFIG_I2C_PROSAVAGE is not set
> # CONFIG_I2C_SAVAGE4 is not set
> # CONFIG_I2C_SIS5595 is not set
> # CONFIG_I2C_SIS630 is not set
> # CONFIG_I2C_SIS96X is not set
> CONFIG_I2C_VIA=y
> CONFIG_I2C_VIAPRO=y
> # CONFIG_I2C_VOODOO3 is not set
> # I2C Hardware Sensors Chip support
> CONFIG_I2C_SENSOR=y
You seem to be missing support for a sensor chip.
Best regards,
Stian
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: sensors vs 2.6
2003-12-09 14:54 ` Stian Jordet
@ 2003-12-09 15:21 ` Gene Heskett
2003-12-09 15:32 ` Stian Jordet
0 siblings, 1 reply; 9+ messages in thread
From: Gene Heskett @ 2003-12-09 15:21 UTC (permalink / raw)
To: Stian Jordet; +Cc: Sebastian Kaps, linux-kernel
On Tuesday 09 December 2003 09:54, Stian Jordet wrote:
>tir, 09.12.2003 kl. 13.41 skrev Gene Heskett:
>> I have this:
>> -----------------------
>> [root@coyote linux-2.6]# grep I2C .config
>> # I2C support
>> CONFIG_I2C=y
>> CONFIG_I2C_CHARDEV=y
>> # I2C Algorithms
>> CONFIG_I2C_ALGOBIT=y
>> # CONFIG_I2C_ALGOPCF is not set
>> # I2C Hardware Bus support
>> # CONFIG_I2C_ALI1535 is not set
>> # CONFIG_I2C_ALI15X3 is not set
>> # CONFIG_I2C_AMD756 is not set
>> # CONFIG_I2C_AMD8111 is not set
>> # CONFIG_I2C_I801 is not set
>> # CONFIG_I2C_I810 is not set
>> # CONFIG_I2C_NFORCE2 is not set
>> # CONFIG_I2C_PHILIPSPAR is not set
>> # CONFIG_I2C_PIIX4 is not set
>> # CONFIG_I2C_PROSAVAGE is not set
>> # CONFIG_I2C_SAVAGE4 is not set
>> # CONFIG_I2C_SIS5595 is not set
>> # CONFIG_I2C_SIS630 is not set
>> # CONFIG_I2C_SIS96X is not set
>> CONFIG_I2C_VIA=y
>> CONFIG_I2C_VIAPRO=y
>> # CONFIG_I2C_VOODOO3 is not set
>> # I2C Hardware Sensors Chip support
>> CONFIG_I2C_SENSOR=y
>
>You seem to be missing support for a sensor chip.
That wasn't covered by this: ??
[root@coyote linux-2.6]# grep SENSORS .config
# CONFIG_SENSORS_ADM1021 is not set
CONFIG_SENSORS_EEPROM=y
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM85 is not set
CONFIG_SENSORS_VIA686A=y
CONFIG_SENSORS_W83781D=y
I just rebuilt, but haven't rebooted to test it yet, a kernel without
the VIA686 stuff just in case that was getting in the way. I should
reboot and see what I've got now.
>
>Best regards,
>Stian
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: sensors vs 2.6
2003-12-09 15:21 ` Gene Heskett
@ 2003-12-09 15:32 ` Stian Jordet
0 siblings, 0 replies; 9+ messages in thread
From: Stian Jordet @ 2003-12-09 15:32 UTC (permalink / raw)
To: gene.heskett; +Cc: Sebastian Kaps, linux-kernel
tir, 09.12.2003 kl. 16.21 skrev Gene Heskett:
> [root@coyote linux-2.6]# grep SENSORS .config
> # CONFIG_SENSORS_ADM1021 is not set
> CONFIG_SENSORS_EEPROM=y
> # CONFIG_SENSORS_IT87 is not set
> # CONFIG_SENSORS_LM75 is not set
> # CONFIG_SENSORS_LM78 is not set
> # CONFIG_SENSORS_LM85 is not set
> CONFIG_SENSORS_VIA686A=y
> CONFIG_SENSORS_W83781D=y
Sorry, I'm stupid. I didn't notice you just grepped after i2c, I just
thought you had copied the entire i2c section from .config. Sorry. That
should cover it.
Best regards,
Stian
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: sensors vs 2.6
@ 2003-12-09 15:43 Matt
0 siblings, 0 replies; 9+ messages in thread
From: Matt @ 2003-12-09 15:43 UTC (permalink / raw)
To: zdzichu; +Cc: Linux Kernel Mailing List
Any reason why the via modules need this weird ass loading dependancy?
Is it fixable?
Matt
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2003-12-09 16:00 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-12-09 7:58 sensors vs 2.6 Gene Heskett
2003-12-09 10:33 ` Sebastian Kaps
2003-12-09 12:41 ` Gene Heskett
2003-12-09 14:18 ` Tomasz Torcz
2003-12-09 16:00 ` Gene Heskett
2003-12-09 14:54 ` Stian Jordet
2003-12-09 15:21 ` Gene Heskett
2003-12-09 15:32 ` Stian Jordet
2003-12-09 15:43 Matt
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).