All of lore.kernel.org
 help / color / mirror / Atom feed
From: thijs@thijsbakx.nl (Thijs Bakx)
To: lm-sensors@vger.kernel.org
Subject: Fw: Some very strange problems with lm-sensors
Date: Thu, 19 May 2005 06:23:59 +0000	[thread overview]
Message-ID: <003c01c32fff$1429de40$1200a8c0@twit> (raw)
In-Reply-To: <000501c32ffe$afb61410$1200a8c0@twit>

Just to be sure, The output i gave u  is what i get AFTER that i made
/dev/i2c files by myself.
----- Original Message ----- 
From: "Thijs Bakx" <thijs@thijsbakx.nl>
To: <sensors@stimpy.netroedge.com>
Cc: "Lennard" <lennard.klein@planet.nl>
Sent: Wednesday, June 11, 2003 11:48 AM
Subject: Some very strange problems with lm-sensors


> As i said in the subject in short the problem is that i can?t find any
> sensors
> on my asus a7v8-x with lm-sensors. I have patched my kernel , 2.4.20, with
> the
> correct patches and compiled the kernel with all lmsensors and i2c
support.
> But still no sensors were found, then i tried to compile everything as
> modules
> and now sensors-detect gives us some sensors. Although when I modprobe
them
> and then try ?sensors ? again it still says no sensors found. I even tried
> to
> get those sensors to work with the forced undectable sensors method but
> then ./i2cdetect 0 says it can?t open /dev/i2c-0. And I found out
> that /dev/i2c-0 indeed not exists.
>
> I think I have tried just everything i could so thats why I decided to ask
> it
> here. I hope i gave enough info otherwise you can just mail me.
>
> Is there any irc channel or something were a lot of lm-sensors users hang
> out ?
>
>
> The output of i2cdetect:
>
> fulgor:/home/admin/twit/downloads/lm_sensors-2.7.0/prog/detect#
./i2cdetect
> 0
>   WARNING! This program can confuse your I2C bus, cause data loss and
worse!
>   I will probe file /dev/i2c-0
>   You have five seconds to reconsider and press CTRL-C!
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>  00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
>  10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
>  20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
>  30: 30 31 XX XX XX XX XX 37 XX XX XX XX XX XX XX XX
>  40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
>  50: 50 51 XX XX XX XX XX XX XX XX XX XX XX XX XX XX
>  60: XX XX XX XX XX XX XX XX XX 69 XX XX XX XX XX XX
>  70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
>

      parent reply	other threads:[~2005-05-19  6:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:23 Some very strange problems with lm-sensors Thijs Bakx
2005-05-19  6:23 ` Jean Delvare
2005-05-19  6:23 ` Thijs Bakx [this message]

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='003c01c32fff$1429de40$1200a8c0@twit' \
    --to=thijs@thijsbakx.nl \
    --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.