You are not logged in.
I have fancontrol problem while using linux kernel(4.0.7)
pwmconfig works, i make the settings and after a few reboots fancontrol gives failure.
I tried to use linux-lts kernel, no prblem occurs.
sensors output in linux-LTS:
[levent@asus ~]$ sensors
eeepc-isa-0000
Adapter: ISA adapter
fan1: 4026 RPM
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +55.0°C (crit = +100.0°C)
Core 1: +57.0°C (crit = +100.0°C)
If I use 4.0.7 kernel, there is one more line upperside, showing temp1. BUt when i run pwmconfig with ths kernel, hwmon0/hwmon1 etc.. changes adress after a few reboots.
Is it possible to block this temp1? Or any other solution to be able to use latest kernel?
Last edited by torrasar (2015-07-27 15:47:00)
Offline
Seems noone has an idea
Offline
I really can't speak for anyone else, but for me, I don't think I understand what you're asking. You're not very clear about your problem.
Offline
I have 2 kernels installed.
One is Linux kernel 4.0.7-2 and the other is linux-lts.
If I boot linx-lts, sensors command output is:
[levent@asus ~]$ sensors
eeepc-isa-0000
Adapter: ISA adapter
fan1: 4026 RPM
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +59.0°C (crit = +100.0°C)
Core 1: +60.0°C (crit = +100.0°C)
If I boot linux kernel (4.0.7-2)
[levent@asus ~]$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +64.0°C (crit = +98.0°C)
eeepc-isa-0000
Adapter: ISA adapter
fan1: 3973 RPM
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +59.0°C (crit = +100.0°C)
Core 1: +60.0°C (crit = +100.0°C)
When I boot with linux-lts kernel after making pwmconfig settings, everything is ok; fancontrol works properly.
But if I prefer linux kernel, after pwmconfig for this kernel, fancontrol.service fails at %80 of boots. And whenever I open my PC, I have to pwmconfig again. Because hwmon0 and hwmon1 change adress.
Is there a solution of making pwmconfig settings with linux kernel and go on using it?
I saw difference of temp1 between 2 kernels. So I thought if I can make linux kernel to ignore temp1, maybe it wold be possible go on wih that kernel. What I ask is "how can i disable acpitz-virtual-0?"...
I hope it is more brief now.
Offline
Did you re-run sensors-detect with the new kernel?
Offline
sensors-detect output is same with both kernels:
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)
Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no):
Unloading i2c-dev... OK
Unloading cpuid... OK
But pwmconfig outputs are different:
LTS Kernel (which works properly)
Devices:
hwmon0 is eeepc
hwmon1/device is coretemp
Current temperature readings are as follows:
hwmon1/device/temp2_input 48
hwmon1/device/temp3_input 50
Select a temperature sensor as source for hwmon0/pwm1:
1) hwmon1/device/temp2_input
2) hwmon1/device/temp3_input
3) None (Do not affect this PWM output)
linux kernel 4.0.7 (which gives error and always need reboot or re-pwmconfig)
The fancontrol script can automatically respond to temperature changes
of your system by changing fanspeeds.
Do you want to set up its configuration file now (y)?
What should be the path to your fancontrol config file (/etc/fancontrol)?
Loading configuration from /etc/fancontrol ...
Device path of hwmon0 has changed
Device path of hwmon1 has changed
Device name of hwmon0 has changed
Device name of hwmon1 has changed
Configuration appears to be outdated, discarded
Select fan output to configure, or other action:
1) hwmon1/pwm1 3) Just quit 5) Show configuration
2) Change INTERVAL 4) Save and quit
select (1-n): Devices:
hwmon0 is acpitz
hwmon1 is eeepc
hwmon2 is coretemp
Current temperature readings are as follows:
hwmon0/temp1_input 57
hwmon2/temp2_input 44
hwmon2/temp3_input 47
Select a temperature sensor as source for hwmon1/pwm1:
1) hwmon0/temp1_input
2) hwmon2/temp2_input
3) hwmon2/temp3_input
4) None (Do not affect this PWM output)
select (1-n):
Even if I configure again, it creates same error after a few reboots.
Is there a way to ignore/avoid acpitz output? (to be able to get same configuration in LTS kernel) Seems like the problems source is acpitz virtual sensor..
NOTE : If I use Ubuntu with kernel 3.19, acpitz seems again. But pwmconfig once is enugh. Never loses settings or change adresses.
Last edited by torrasar (2015-07-08 13:12:49)
Offline
It seems I must accept this silence as "there is no solution"..
Last edited by torrasar (2015-07-22 05:05:49)
Offline
When I checked both kernels with lsmod command, i saw difference between modules.
In kernel 4.1 ,thermal module seemed to create the problem. Tried "modprobe -r thermal" and sensors output became same with LTS kernel.
Added thermal module to blacklist, so there is no more problem.
Both kernels work with same settings and Linux kernel doesnt lose settings anymore.
Last edited by torrasar (2015-07-27 15:46:17)
Offline