From: Juergen Bausa <Juergen.Bausa@web.de>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] dme1737 0-002e: Write to register 0x30 failed!
Date: Mon, 01 Oct 2007 19:22:17 +0000 [thread overview]
Message-ID: <1659445316@web.de> (raw)
In-Reply-To: <1642847378@web.de>
Hi Juerg,
> Von: "Juerg Haefliger" <juergh@gmail.com>
>
> On 9/25/07, Juergen Bausa <Juergen.Bausa@web.de> wrote:
> > What does this mean (taken from /var/log/messages)?
> >
> > Sep 23 12:11:22 lisa kernel: dme1737 0-002e: Write to register 0x30 failed! Please report to the driver maintainer.
>
> What exactly is unclear about the message? The write fails (for
> whatever reason). I should probably print out the return value as
> well...
> More interestingly is the register address. 0x30 is the current PWM
> duty-cycle. It only gets written during driver initialization or if
> userland does manual PWM control.
>
> > I get this sometimes (every some hours). I use the dme1737.ko without on my asus system
> > (Pundit P1-AH2) with Athlon BE-2350.
>
> What apps are you running that touch the driver? Are you doing manual
> PWM control?
>
I use the script fancontrol from lm-sensors, that controls the cpu-fan by pwm. It works
fine. Maybe it somtimes fails in setting the fan speed, but can set in the next cycle.
I newer got error messages from fancontrol.
Juergen
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc\x100071&distributionid\00000000066
_______________________________________________
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-01 19:22 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 [this message]
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
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=1659445316@web.de \
--to=juergen.bausa@web.de \
--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.