On 2017-04-14 21:10, Hans-J. Ullrich wrote: > Package: fancontrol > Version: 1:3.4.0-4 > Severity: wishlist > > Dear Maintainer, > > it would be nice, if you could add a default configuration file > (/etc/fancontrol) to the package.
This not something possible, actually each machine needs a different configuration file. We do not want to handle the thousands of different configuration which exists in the work, and additionally they might actually conflict and thus break hardware. > This is useful, when used in livefile systems. In my case, I am regularly > building a kali livefile dvd > for my EEEPC, who needs fancontrol and eeepc-acpi-scripts (so fancontrol or > eeepc-acpi-scripts should have the related dependency). > After install, it is necessary to use pwmconfig, to create /etc/fancontrol. > Without it, the fan will not run, > and the cpu can be overheated. > > So, the solution is the following: > > 1. Build the livefile with the command "acpi_osi=Linux" at grub (my part) > 2. Take care of installing fancontrol and eeepc-acpi-scripts (my part) > 3. Create /etc/fancontrol at installation (your part) If your live CD is specific to EEEPC, why can't you actually include it as part of the live CD creation in the step 3? > If you like, you can use mine for example, it is running fine on EEEPC. > > Here it is: > > ----- > > # Configuration file generated by pwmconfig, changes will be lost > INTERVAL=5 > DEVPATH=hwmon0= hwmon2=devices/platform/eeepc > DEVNAME=hwmon0=acpitz hwmon2=eeepc > FCTEMPS= hwmon2/pwm1=hwmon0/temp1_input > FCFANS= hwmon2/pwm1= > MINTEMP= hwmon2/pwm1=55 > MAXTEMP= hwmon2/pwm1=65 > MINSTART= hwmon2/pwm1=50 > MINSTOP= hwmon2/pwm1=35 > MINPWM= hwmon2/pwm1=0 > MAXPWM= hwmon2/pwm1=255 As said above, this is specific to an EEEPC machine, or even one variant of a EEEPC. At best it will make fancontrol to fail to start on all non-EEEPC machine. At worst it might be incompatible with some other variants of EEEPC. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
