From: sergio <mailbox@sergio.spb.ru>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] fancontrol
Date: Fri, 27 Mar 2009 03:03:20 +0000 [thread overview]
Message-ID: <49CC41F8.7010606@sergio.spb.ru> (raw)
In-Reply-To: <1122217880.3578.8.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2542 bytes --]
Jean Delvare wrote:
> Honestly, fan speed control under busybox doesn't strike me as the most
> needed feature.
Why? Many home nas'es and high performance routers have a fan.
>>> A third possibility which was discussed in the thread I mentioned above
>>> is a helper binary, linked with libsensors, which would take care of
>>> translating hwmonN names to libsensors chip names and back.
>> IMHO this is worst way.
> Why that?
It's look like a crutch.
>> ... If k8temp also present in /etc/modules it is
>> don't matter in which order this modules are written in this file.
>> acpitz always will hwmon0, k8temp -> hwmon1, and it8718 -> hwmon1 (if it
>> present in modules)
> I presume you mean it8718 -> hwmon2.
Yes.
>> (Really, on machine with lenny it87 loads via force_load in
>> initramfs-tools hook, so it87 is (always?) first.)
> What is force_load? And why do you need it?
force_load is function for initramfs-tools hook script (which runs at
build time). It adds a module (and its dependencies) to the initramfs
image and also unconditionally loads the module during boot.
I need it for speed down fan, because it very noisy. Why i need do it at
initrd time? This initrd waits for password for encrypted rootfs...
>> So hwmon names jumping it's not very big problem for me.
> Why are you reporting it then?
Because the problem exists. And i would like that it was not.
>> It is never happens unexpectedly. Only when i change or upgrade something.
> "change or upgrade something" is simply too vague for me to do anything
> useful with the information.
I said this in support of the above-said. I understand which my actions
(and real reason) leads to name changing. But i don't memorize it.
> There may be other similar daemons that can be extended.
So, now only fancontrol can manage fan speed.
> Or feel free to start your own, but then pretty please make its
> configuration file much more flexible and clear than fancontrol's one.
> Shouldn't be too hard ;) If you come up with something really good then I
> will be happy to kill the pwmconfig and fancontrol scripts in favor of your work.
OK.
>> May be should add possibility to define real path to device
>> (/sys/devices/platform/it87.552)?
> This is a possibility, yes, and it shouldn't be too hard to implement.
> Want to give it a try?
See attachment.
> Not to say that it can't be done properly for hwmon devices. But do
> you have some concrete proposal? "Let's just use udev" doesn't tell me
> much.
I don't clearly understand how udev works.
--
sergio
[-- Attachment #2: fancontrol.patch.bz2 --]
[-- Type: application/octet-stream, Size: 905 bytes --]
[-- Attachment #3: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-03-27 3:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 17:15 [lm-sensors] Fancontrol Henry
2005-07-25 13:44 ` Jim Cromie
2005-07-26 9:45 ` Rudolf Marek
2005-07-26 18:13 ` Henry
2005-07-27 9:23 ` Rudolf Marek
2005-07-27 16:05 ` Henry
2005-07-28 10:21 ` Rudolf Marek
2005-07-28 15:18 ` Henry
2005-07-28 15:19 ` Henry
2005-07-28 15:41 ` Henry
2005-07-30 7:02 ` Henry
2009-03-25 9:04 ` [lm-sensors] fancontrol Jean Delvare
2009-03-25 15:33 ` sergio
2009-03-25 21:35 ` Jean Delvare
2009-03-27 3:03 ` sergio [this message]
2009-03-27 8:39 ` Jean Delvare
2009-03-27 16:30 ` sergio
2009-05-09 11:43 ` Jean Delvare
2010-03-29 11:46 ` Ioan Rusan
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=49CC41F8.7010606@sergio.spb.ru \
--to=mailbox@sergio.spb.ru \
--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.