From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] lm_sensors 2.9.2 & kernel 2.6.8-24
Date: Fri, 14 Oct 2005 16:46:42 +0000 [thread overview]
Message-ID: <fzUCYolL.1129300517.6487670.khali@localhost> (raw)
In-Reply-To: <434F973D.5080607@scs.co.uk>
Hi Charles,
Please answer to the list, not to me only!
> nport1:~ # i2cdetect 0
> Error: Could not open file `/dev/i2c-0': No such device
> nport1:~ #
modprobe i2c-dev
Sorry for nor telling you, sensors-detect loads it for you and I didn't
figure out you'd have rebooted since.
> > So you have a Super-I/O chip, most probably from National Semiconductor.
> > Do you happen to know what it is? Our script doesn't seem to know.
> > Sometimes Super-I/O chips include hardware monitoring capabilities.
>
> No - I don't - and I don't really want to go digging under the keyboard
> to look for the MB unless I have to!!
Yeah, I understand. I wasn't even able to open my own laptop. But
sometimes you have some technical documentation which states which chips
you have. Unfortunately, more often than not, the Super-I/O chip isn't
listed.
> No - not certain at all. It does support ACPI which was off when I did
> previous results (trying to see if it was causing the problem). I can't
> seem to turn it on again - removing acpi=off from boot loader should do
> it I think - but it hangs the system - maybe this is a clue? Or am I
> being dim?. Therefore no /proc/acpi files at the moment!
I can't say. ACPI is a very complex area, some laptops need it, some
don't like it at all, there are quirks required for half of them.
Depending on the model, it might work on a version and not on another.
We can't help you with this, see with the linux-acpi folks.
--
Jean Delvare
next prev parent reply other threads:[~2005-10-14 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 13:33 [lm-sensors] lm_sensors 2.9.2 & kernel 2.6.8-24 Charles Whittington
2005-10-14 14:04 ` Jean Delvare
2005-10-14 16:46 ` Jean Delvare [this message]
2005-10-17 12:29 ` Charles Whittington
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=fzUCYolL.1129300517.6487670.khali@localhost \
--to=khali@linux-fr.org \
--cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.