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 -------------- next part -------------- A non-text attachment was scrubbed... Name: fancontrol.patch.bz2 Type: application/octet-stream Size: 905 bytes Desc: not available Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20090327/2183d56d/attachment-0001.obj
