On Mon, Apr 28, 2003 at 01:55:22PM -0700, Greg KH wrote:
> On Sun, Apr 27, 2003 at 09:56:44PM +1000, CaT wrote:
> > I keep a-lookin but I can't find any data. Have I missed something?
> >
> > # find | grep -i pii
> > ./bus/pci/drivers/piix4 smbus
> > ./bus/pci/drivers/piix4 smbus/00:07.3
> > ./bus/pci/drivers/PIIX IDE
> > ./bus/pci/drivers/PIIX IDE/00:07.1
> > # find | grep -i i2c
> > ./bus/i2c
> > ./bus/i2c/drivers
> > ./bus/i2c/drivers/lm75
> > ./bus/i2c/drivers/IT87xx
> > ./bus/i2c/drivers/dev driver
> > ./bus/i2c/devices
>
> No devices? Does 2.5.68 work for you?
Does not look like it:
# find | grep -i pii
./bus/pci/drivers/piix4 smbus
./bus/pci/drivers/piix4 smbus/00:07.3
./bus/pci/drivers/PIIX IDE
./bus/pci/drivers/PIIX IDE/00:07.1
# find | grep -i i2c
./bus/i2c
./bus/i2c/drivers
./bus/i2c/drivers/lm75
./bus/i2c/drivers/dev driver
./bus/i2c/devices
./devices/pci0/00:07.3/i2c-0
./devices/pci0/00:07.3/i2c-0/power
./devices/pci0/00:07.3/i2c-0/name
# uname -a
Linux theirongiant 2.5.68 #5 Sun May 4 23:59:51 EST 2003 i686 unknown
# grep '\(I2C\|SENSORS\)' .config
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_PIIX4=y
CONFIG_SENSORS_LM75=y
CONFIG_I2C_SENSOR=y
--
Martin's distress was in contrast to the bitter satisfaction of some
of his fellow marines as they surveyed the scene. "The Iraqis are sick
people and we are the chemotherapy," said Corporal Ryan Dupre. "I am
starting to hate this country. Wait till I get hold of a friggin' Iraqi.
No, I won't get hold of one. I'll just kill him."
- http://www.informationclearinghouse.info/article2479.htm
On Mon, May 05, 2003 at 06:34:58PM +1000, CaT wrote:
> On Mon, Apr 28, 2003 at 01:55:22PM -0700, Greg KH wrote:
> > On Sun, Apr 27, 2003 at 09:56:44PM +1000, CaT wrote:
> > No devices? Does 2.5.68 work for you?
>
> Does not look like it:
*snip*
Same deal with 2.5.69.
--
Martin's distress was in contrast to the bitter satisfaction of some
of his fellow marines as they surveyed the scene. "The Iraqis are sick
people and we are the chemotherapy," said Corporal Ryan Dupre. "I am
starting to hate this country. Wait till I get hold of a friggin' Iraqi.
No, I won't get hold of one. I'll just kill him."
- http://www.informationclearinghouse.info/article2479.htm
On Mon, May 05, 2003 at 06:34:58PM +1000, CaT wrote:
> On Mon, Apr 28, 2003 at 01:55:22PM -0700, Greg KH wrote:
> > On Sun, Apr 27, 2003 at 09:56:44PM +1000, CaT wrote:
> > > I keep a-lookin but I can't find any data. Have I missed something?
> > >
> > > # find | grep -i pii
> > > ./bus/pci/drivers/piix4 smbus
> > > ./bus/pci/drivers/piix4 smbus/00:07.3
> > > ./bus/pci/drivers/PIIX IDE
> > > ./bus/pci/drivers/PIIX IDE/00:07.1
> > > # find | grep -i i2c
> > > ./bus/i2c
> > > ./bus/i2c/drivers
> > > ./bus/i2c/drivers/lm75
> > > ./bus/i2c/drivers/IT87xx
> > > ./bus/i2c/drivers/dev driver
> > > ./bus/i2c/devices
> >
> > No devices? Does 2.5.68 work for you?
>
> Does not look like it:
Ok, but 2.5.67 worked for you, right? Care to do a binary search
through the different -bk trees inbetween to find where it stopped
working for you?
thanks,
greg k-h
hey guys. Notice a missing proc driver? hint: i2c. That's why
sensors wont work even when you load the modules. At least that's what i
can tell from what the lm_sensors page mentions and what not.
Greg KH wrote:
> On Mon, May 05, 2003 at 06:34:58PM +1000, CaT wrote:
>
>>On Mon, Apr 28, 2003 at 01:55:22PM -0700, Greg KH wrote:
>>
>>>On Sun, Apr 27, 2003 at 09:56:44PM +1000, CaT wrote:
>>>
>>>>I keep a-lookin but I can't find any data. Have I missed something?
>>>>
>>>># find | grep -i pii
>>>>./bus/pci/drivers/piix4 smbus
>>>>./bus/pci/drivers/piix4 smbus/00:07.3
>>>>./bus/pci/drivers/PIIX IDE
>>>>./bus/pci/drivers/PIIX IDE/00:07.1
>>>># find | grep -i i2c
>>>>./bus/i2c
>>>>./bus/i2c/drivers
>>>>./bus/i2c/drivers/lm75
>>>>./bus/i2c/drivers/IT87xx
>>>>./bus/i2c/drivers/dev driver
>>>>./bus/i2c/devices
>>>
>>>No devices? Does 2.5.68 work for you?
>>
>>Does not look like it:
>
>
> Ok, but 2.5.67 worked for you, right? Care to do a binary search
> through the different -bk trees inbetween to find where it stopped
> working for you?
>
> thanks,
>
> greg k-h
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On Mon, May 05, 2003 at 02:14:25PM -0400, Ed Sweetman wrote:
> hey guys. Notice a missing proc driver? hint: i2c. That's why
> sensors wont work even when you load the modules. At least that's what i
> can tell from what the lm_sensors page mentions and what not.
Huh?
The i2c code now interacts to userspace through sysfs, not /proc
anymore. CaT is properly looking for his sensors in sysfs.
Here's what happens when looking through sysfs on my box running 2.5.69:
# find /sys/ | grep -i i2c
/sys/bus/i2c
/sys/bus/i2c/drivers
/sys/bus/i2c/drivers/lm75
/sys/bus/i2c/drivers/lm75/0-0048
/sys/bus/i2c/devices
/sys/bus/i2c/devices/0-0048
/sys/devices/pci0/00:1f.3/i2c-0
/sys/devices/pci0/00:1f.3/i2c-0/0-0048
/sys/devices/pci0/00:1f.3/i2c-0/0-0048/temp_input
/sys/devices/pci0/00:1f.3/i2c-0/0-0048/temp_min
/sys/devices/pci0/00:1f.3/i2c-0/0-0048/temp_max
/sys/devices/pci0/00:1f.3/i2c-0/0-0048/power
/sys/devices/pci0/00:1f.3/i2c-0/0-0048/name
/sys/devices/pci0/00:1f.3/i2c-0/power
/sys/devices/pci0/00:1f.3/i2c-0/name
Which is what should be showing up on CaT's machine (of the lm75 device
is on his hardware.)
Hope this helps,
greg k-h
Ok, then the sensors program that is part of the lm_sensors package is
just not up to date with the drivers since it complains about no
i2c-proc and has no options for looking at sysfs.
My via686a sensors seem to be working just fine in .69
Greg KH wrote:
> On Mon, May 05, 2003 at 02:14:25PM -0400, Ed Sweetman wrote:
>
>>hey guys. Notice a missing proc driver? hint: i2c. That's why
>>sensors wont work even when you load the modules. At least that's what i
>>can tell from what the lm_sensors page mentions and what not.
>
>
> Huh?
> The i2c code now interacts to userspace through sysfs, not /proc
> anymore. CaT is properly looking for his sensors in sysfs.
>
> Here's what happens when looking through sysfs on my box running 2.5.69:
>
> # find /sys/ | grep -i i2c
> /sys/bus/i2c
> /sys/bus/i2c/drivers
> /sys/bus/i2c/drivers/lm75
> /sys/bus/i2c/drivers/lm75/0-0048
> /sys/bus/i2c/devices
> /sys/bus/i2c/devices/0-0048
> /sys/devices/pci0/00:1f.3/i2c-0
> /sys/devices/pci0/00:1f.3/i2c-0/0-0048
> /sys/devices/pci0/00:1f.3/i2c-0/0-0048/temp_input
> /sys/devices/pci0/00:1f.3/i2c-0/0-0048/temp_min
> /sys/devices/pci0/00:1f.3/i2c-0/0-0048/temp_max
> /sys/devices/pci0/00:1f.3/i2c-0/0-0048/power
> /sys/devices/pci0/00:1f.3/i2c-0/0-0048/name
> /sys/devices/pci0/00:1f.3/i2c-0/power
> /sys/devices/pci0/00:1f.3/i2c-0/name
>
> Which is what should be showing up on CaT's machine (of the lm75 device
> is on his hardware.)
>
> Hope this helps,
>
> greg k-h
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On Mon, May 05, 2003 at 03:34:55PM -0400, Ed Sweetman wrote:
>
> Ok, then the sensors program that is part of the lm_sensors package is
> just not up to date with the drivers since it complains about no
> i2c-proc and has no options for looking at sysfs.
Yes, the libsensors code has not been updated yet, sorry. I'm hoping
for some unification with the acpi/power management people too, as they
too care about power and temperature and fan settings.
> My via686a sensors seem to be working just fine in .69
Glad to hear it.
greg k-h
On Mon, May 05, 2003 at 11:26:48AM -0700, Greg KH wrote:
> Which is what should be showing up on CaT's machine (of the lm75 device
> is on his hardware.)
Yes. And ofcourse it isn't so I feel like a right boob. Now, compiling
the right sensor (adm) gets it registered and promptly crashes the
kernel. Once this happened whilst in the kernel, either mid scroll of
the fb or mid write of a new line on screen and another time this
happened mid-fsck (no partitions needed fscking). Witht he wrong/no
sensors module in the kernel runs just fine.
My experience with the sensors code is evolving. :)
--
Martin's distress was in contrast to the bitter satisfaction of some
of his fellow marines as they surveyed the scene. "The Iraqis are sick
people and we are the chemotherapy," said Corporal Ryan Dupre. "I am
starting to hate this country. Wait till I get hold of a friggin' Iraqi.
No, I won't get hold of one. I'll just kill him."
- http://www.informationclearinghouse.info/article2479.htm
On Tue, 2003-05-06 at 04:39, Greg KH wrote:
> On Mon, May 05, 2003 at 03:34:55PM -0400, Ed Sweetman wrote:
> >
> > Ok, then the sensors program that is part of the lm_sensors package is
> > just not up to date with the drivers since it complains about no
> > i2c-proc and has no options for looking at sysfs.
>
> Yes, the libsensors code has not been updated yet, sorry. I'm hoping
> for some unification with the acpi/power management people too, as they
> too care about power and temperature and fan settings.
>
> > My via686a sensors seem to be working just fine in .69
>
> Glad to hear it.
Thats strange. Mine don't, and never have in 2.5 - works in FreeBSD just
fine though.
On Tue, May 06, 2003 at 05:00:16PM +0800, Wade wrote:
> On Tue, 2003-05-06 at 04:39, Greg KH wrote:
> > On Mon, May 05, 2003 at 03:34:55PM -0400, Ed Sweetman wrote:
> > >
> > > Ok, then the sensors program that is part of the lm_sensors package is
> > > just not up to date with the drivers since it complains about no
> > > i2c-proc and has no options for looking at sysfs.
> >
> > Yes, the libsensors code has not been updated yet, sorry. I'm hoping
> > for some unification with the acpi/power management people too, as they
> > too care about power and temperature and fan settings.
> >
> > > My via686a sensors seem to be working just fine in .69
> >
> > Glad to hear it.
>
> Thats strange. Mine don't, and never have in 2.5 - works in FreeBSD just
> fine though.
Does the 2.4 packages from the lmsensors web page work for you? And if
so, are the drivers your hardware needs currently in the 2.5 tree yet?
If not, want to port them? If so, please let us know.
thanks,
greg k-h