From: Jean Delvare <khali@linux-fr.org>
To: Ian Morgan <imorgan@webcon.ca>
Cc: helpdeskie@bencastricum.nl, linux-kernel@vger.kernel.org
Subject: Re: 2.6.5 Sensors & USB problems
Date: Sun, 18 Apr 2004 07:32:10 +0200 [thread overview]
Message-ID: <20040418073210.17898929.khali@linux-fr.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0404171756400.11374@dark.webcon.ca>
> > > 2.6.5-rc1 -> sensors broke (ERROR: Can't get <sensor> data!)
> >
> > Your sensors problem will be resolved as soon as you switch to the
> > just released lm_sensors 2.8.6.
>
> I use the same w83781d and i2c_i801 drivers on my Asus P4PE box, and
> they too went belly up with 2.6.5. However, I HAVE tried lm_sensors
> 2.8.6 and that made no difference. They're just user-space tools that
> don't touch the kernel any more in 2.6.x (right?).
>
> The problem I am seeing now in 2.6.5 is that after loading the w83781d
> module, nothing shows up in /sys or /proc, as though the module had
> not loaded but lsmod says it is loaded.
>
> In 2.6.4, my sensors showed up hare:
> /sys/devices/pci0000:00/0000:00:1f.3/i2c-0/0-002d/* (w83781d)
> /sys/devices/pci0000:00/0000:00:1f.3/i2c-1/1-0050/* (eeprom)
>
> Now in 2.6.5, with both eeprom and w83781d modules loaded, I only get
> the eeprom, and the w83781d is nowhere to be found:
> /sys/devices/pci0000:00/0000:00:1f.3/i2c-1/1-0050/* (eeprom)
This is a different problem, and I agree that upgrading user-space tools
couldn't help in you case. Ben had his chip correctly detected but the
interface exported by the kernel was not known to the (not up-to-date)
user-space tools. In you case this is the kernel driver not supporting
your hardware anymore, that's different.
See my answer to your second post for details about your case.
--
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/
next prev parent reply other threads:[~2004-04-18 5:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 14:56 2.6.5 Sensors & USB problems Jean Delvare
2004-04-17 22:07 ` Ian Morgan
2004-04-17 23:49 ` Ian Morgan
2004-04-18 5:51 ` Jean Delvare
2004-05-04 20:37 ` Greg KH
2004-05-06 17:41 ` Jean Delvare
2004-04-18 5:32 ` Jean Delvare [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-06 16:18 Ben Castricum
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=20040418073210.17898929.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=helpdeskie@bencastricum.nl \
--cc=imorgan@webcon.ca \
--cc=linux-kernel@vger.kernel.org \
/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