From: "Mark M. Hoffman" <mhoffman@lightlink.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] dme1737 0-002e: Write to register 0x30 failed!
Date: Sun, 21 Oct 2007 18:40:58 +0000 [thread overview]
Message-ID: <20071021184058.GA30539@jupiter.solarsys.private> (raw)
In-Reply-To: <1642847378@web.de>
Hi:
> > Von: Jean Delvare <khali@linux-fr.org>
> > Gesendet: 17.10.07 23:32:28
> >
> > This can only happen on a multi-master I2C bus, which is rather rare on
> > consumer PCs. Juergen, do you have detailed technical documentation
> > about your system? It would be interesting to find out what chip the
> > other master is talking to. If it's the DME1737 chip, this could lead
> > to problems.
* Juergen Bausa <Juergen.Bausa@web.de> [2007-10-20 21:28:02 +0200]:
> No. I dont have detailes information. Its an asus barebone.
>
> Asus borads have a feature called 'ASUS Q-Fan Technology'. Its a BIOS-based controller for the
> FAN/CPU-temperature. This is turned on in the bios. However, when booting linux, the script
> 'fancontrol' is started and then controls cpu-temperature. Maybe the Q-fan still tries to access
> the fan and this is the reason for the collision?
Unlikely. I have several Asus boards... in all cases, "Q-fan" is merely their
rebranding of whatever automatic fan control is supported by the sensor chip.
I.e. the BIOS may allow you to set up some automatic fan control of the sensor
chip, but after initialization the BIOS has nothing more to do with it.
Of course it's *possible* that your board is different than all of mine and
that there is active BIOS control. But again, *unlikely*.
Regards,
--
Mark M. Hoffman
mhoffman@lightlink.com
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2007-10-21 18:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 19:08 [lm-sensors] dme1737 0-002e: Write to register 0x30 failed! Juergen Bausa
2007-10-01 17:44 ` Juerg Haefliger
2007-10-01 19:22 ` Juergen Bausa
2007-10-01 21:39 ` Juerg Haefliger
2007-10-01 21:50 ` Jean Delvare
2007-10-08 18:31 ` Juergen Bausa
2007-10-09 7:03 ` Jean Delvare
2007-10-09 16:08 ` Juerg Haefliger
2007-10-09 19:41 ` Juergen Bausa
2007-10-10 17:12 ` Juerg Haefliger
2007-10-11 7:45 ` Jean Delvare
2007-10-17 18:56 ` Juergen Bausa
2007-10-17 19:43 ` Juerg Haefliger
2007-10-17 21:32 ` Jean Delvare
2007-10-18 4:53 ` Juerg Haefliger
2007-10-19 15:07 ` Jean Delvare
2007-10-20 19:28 ` Juergen Bausa
2007-10-20 19:39 ` Juergen Bausa
2007-10-21 18:40 ` Mark M. Hoffman [this message]
2007-10-21 19:14 ` Jean Delvare
2007-10-21 19:37 ` Jean Delvare
2007-10-22 16:02 ` Juerg Haefliger
2007-10-22 16:05 ` Juerg Haefliger
2007-10-23 12:08 ` Jean Delvare
2007-10-23 12:22 ` Jean Delvare
2007-10-23 20:44 ` Juergen Bausa
2007-10-23 21:54 ` Rudolf Marek
2007-10-24 8:48 ` Jean Delvare
2007-10-29 21:23 ` Rudolf Marek
2007-10-30 2:52 ` Juerg Haefliger
2007-10-31 2:40 ` Juerg Haefliger
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=20071021184058.GA30539@jupiter.solarsys.private \
--to=mhoffman@lightlink.com \
--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.