after the 2 last D-U at boot the cooling fan is started and remain started for ever.
root@sidbox1:~# acpi -c
Cooling 0: LCD 0 of 10
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: Fan 1 of 1
Cooling 4: Fan 1 of 1
Cooling 5: Fan 1 of 1
Cooling 6: Fan 1 of 1
Cooling 7: Fan 1 of 1
Cooling 8: Fan 1 of 1
Cooling 9: Fan 1 of 1
Cooling 10: Fan 1 of 1
Cooling 11: Fan 1 of 1
Cooling 12: Fan 1 of 1
Cooling 13: Fan 1 of 1
the command : 7588 echo 0 | sudo tee /sys/class/thermal/cooling_device3/cur_state
7589 echo 0 | sudo tee /sys/class/thermal/cooling_device4/cur_state
7590 echo 0 | sudo tee /sys/class/thermal/cooling_device5/cur_state
7591 echo 0 | sudo tee /sys/class/thermal/cooling_device6/cur_state
7592 echo 0 | sudo tee /sys/class/thermal/cooling_device7/cur_state
7593 echo 0 | sudo tee /sys/class/thermal/cooling_device8/cur_state
yesterday stop the fan
today seems to not work at all
root@sidbox1:~# acpi -c
Cooling 0: LCD 0 of 10
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: Fan 1 of 1
Cooling 4: Fan 1 of 1
Cooling 5: Fan 0 of 1
Cooling 6: Fan 0 of 1
Cooling 7: Fan 0 of 1
Cooling 8: Fan 0 of 1
Cooling 9: Fan 0 of 1
Cooling 10: Fan 0 of 1
Cooling 11: Fan 0 of 1
Cooling 12: Fan 0 of 1
Cooling 13: Fan 1 of 1
is there some file to check to controll this behavior?
Regards
Massimo
I check this:
root@sidbox1:~# /etc/init.d/lm-sensors status
● lm-sensors.service - Initialize hardware monitoring sensors
Loaded: loaded (/lib/systemd/system/lm-sensors.service; enabled)
Active: active (exited) since Tue 2014-12-16 09:48:51 CET; 58min ago
Process: 1203 ExecStart=/usr/bin/sensors (code=exited, status=0/SUCCESS)
Process: 1128 ExecStart=/usr/bin/sensors -s (code=exited, status=0/SUCCESS)
Main PID: 1203 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/lm-sensors.service
Dec 16 09:48:51 sidbox1 sensors[1203]: temp2: +45.0°C (crit = +256.0°C)
Dec 16 09:48:51 sidbox1 sensors[1203]: temp3: +37.0°C (crit = +105.0°C)
Dec 16 09:48:51 sidbox1 sensors[1203]: temp4: +24.0°C (crit = +105.0°C)
Dec 16 09:48:51 sidbox1 sensors[1203]: temp5: +20.1°C (crit = +105.0°C)
Dec 16 09:48:51 sidbox1 sensors[1203]: temp6: +100.0°C (crit = +110.0°C)
Dec 16 09:48:51 sidbox1 sensors[1203]: coretemp-isa-0000
Dec 16 09:48:51 sidbox1 sensors[1203]: Adapter: ISA adapter
Dec 16 09:48:51 sidbox1 sensors[1203]: Core 0: +47.0°C (high = +100.0°C, crit = +100.0°C)
Dec 16 09:48:51 sidbox1 sensors[1203]: Core 1: +44.0°C (high = +100.0°C, crit = +100.0°C)
Dec 16 09:48:51 sidbox1 systemd[1]: Started Initialize hardware monitoring sensors.
But for what I know seems it's ok
the Laptop is HP Compaq 8510w, and is running siduction from more that 2 years without this problem at all
Anyone experience the same problem?
Regards
MAssimo
please provide the output of
inxi -v3
as normal user, not root
Hi,
thanks, here the output
massimo@sidbox1:~$ inxi -v3
System: Host: sidbox1 Kernel: 3.18-0.towo.3-siduction-amd64 x86_64 (64 bit gcc: 4.9.2)
Desktop: Enlightenment 0.17.6 Distro: siduction 12.2.0 Riders on the Storm - rqt - (201212092240)
Machine: System: Hewlett-Packard product: HP Compaq 8510w v: F.05
Mobo: Hewlett-Packard model: 30C5 v: KBC Version 71.32
Bios: Hewlett-Packard v: 68MVD Ver. F.05 date: 07/25/2007
CPU: Dual core Intel Core2 Duo T7500 (-MCP-) cache: 4096 KB
flags: (lm nx sse sse2 sse3 ssse3 vmx) bmips: 8780
clock speeds: max: 2201 MHz 1: 2201 MHz 2: 2201 MHz
Graphics: Card: NVIDIA G84GLM [Quadro FX 570M] bus-ID: 01:00.0
Display Server: X.Org 1.16.2.901 driver: nvidia Resolution: 1680x1050@59.88hz
GLX Renderer: Quadro FX 570M/PCIe/SSE2 GLX Version: 3.3.0 NVIDIA 340.65 Direct Rendering: Yes
Network: Card-1: Intel 82566MM Gigabit Network Connection driver: e1000e v: 2.3.2-k port: 5040 bus-ID: 00:19.0
IF: eth0 state: down mac: 00:17:a4:e9:17:42
Card-2: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection
driver: iwl4965 v: in-tree: bus-ID: 10:00.0
IF: wlan0 state: up mac: 00:13:e8:93:57:89
Drives: HDD Total Size: 120.0GB (81.3% used) ID-1: model: ST9120823AS
Info: Processes: 153 Uptime: 29 min Memory: 456.7/3895.0MB Init: systemd runlevel: 5 Gcc sys: 4.9.2
Client: Shell (bash 4.3.301) inxi: 2.2.16
So, now that we know the graphics card, what driver are you using for that and was it upgraded at the time of the fan going wild?
Please, for the future, provide enough information from the start, so we can better support you.
greetz
devil
Hi Devil,
thanks for your help!
I apologise for the long time to provide the informations!
There is a document or link where I can find the basic list of command to run for provide all the information from the start?
I'm not sure to understand your question, but I think Yes because, I tipically run:
apt-get update ; apt-get dist-upgrade -d -y
look if there is a new kernel-image, if YES i run:
apt-get install linux-headers-3.LAST_VERSION_MATCHING the previous check
systemctl isolate multi-user.target
apt-get dist-upgrade
reboot
So the system restart in graphical.target mode
Can you please tell me if this is correct ot not?
Regards
I perfomed more test:
the FAN start fully and immediatly during boot (before X is started)
the command:
root@sidbox1:~# acpi -c
Cooling 0: LCD 0 of 10
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: Fan 1 of 1
Cooling 4: Fan 1 of 1
Cooling 5: Fan 1 of 1
Cooling 6: Fan 1 of 1
Cooling 7: Fan 1 of 1
Cooling 8: Fan 0 of 1
Cooling 9: Fan 1 of 1
Cooling 10: Fan 1 of 1
Cooling 11: Fan 1 of 1
Cooling 12: Fan 1 of 1
Cooling 13: Fan 1 of 1
root@sidbox1:~# echo 0 | sudo tee /sys/class/thermal/cooling_device0/cur_state
0
root@sidbox1:~# echo 0 | sudo tee /sys/class/thermal/cooling_device1/cur_state
0
root@sidbox1:~# acpi -c
Cooling 0: LCD 0 of 10
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: Fan 1 of 1
Cooling 4: Fan 1 of 1
Cooling 5: Fan 1 of 1
Cooling 6: Fan 1 of 1
Cooling 7: Fan 1 of 1
Cooling 8: Fan 0 of 1
Cooling 9: Fan 1 of 1
Cooling 10: Fan 1 of 1
Cooling 11: Fan 1 of 1
Cooling 12: Fan 0 of 1
Cooling 13: Fan 0 of 1
root@sidbox1:~# echo 0 | sudo tee /sys/class/thermal/cooling_device2/cur_state
0
root@sidbox1:~# acpi -c
Cooling 0: LCD 0 of 10
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: Fan 1 of 1
Cooling 4: Fan 1 of 1
Cooling 5: Fan 1 of 1
Cooling 6: Fan 1 of 1
Cooling 7: Fan 1 of 1
Cooling 8: Fan 0 of 1
Cooling 9: Fan 1 of 1
Cooling 10: Fan 1 of 1
Cooling 11: Fan 0 of 1
Cooling 12: Fan 0 of 1
Cooling 13: Fan 0 of 1
root@sidbox1:~# echo 0 | sudo tee /sys/class/thermal/cooling_device3/cur_state
0
root@sidbox1:~# echo 0 | sudo tee /sys/class/thermal/cooling_device4/cur_state
0
root@sidbox1:~# echo 0 | sudo tee /sys/class/thermal/cooling_device5/cur_state
0
root@sidbox1:~# acpi -c
Cooling 0: LCD 0 of 10
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: Fan 1 of 1
Cooling 4: Fan 1 of 1
Cooling 5: Fan 1 of 1
Cooling 6: Fan 1 of 1
Cooling 7: Fan 1 of 1
Cooling 8: Fan 0 of 1
Cooling 9: Fan 0 of 1
Cooling 10: Fan 0 of 1
Cooling 11: Fan 0 of 1
Cooling 12: Fan 0 of 1
Cooling 13: Fan 0 of 1
root@sidbox1:~# echo 0 | sudo tee /sys/class/thermal/cooling_device6/cur_state
0
root@sidbox1:~# echo 0 | sudo tee /sys/class/thermal/cooling_device7/cur_state
0
root@sidbox1:~# acpi -c
Cooling 0: LCD 0 of 10
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: Fan 1 of 1
Cooling 4: Fan 1 of 1
Cooling 5: Fan 1 of 1
Cooling 6: Fan 0 of 1
Cooling 7: Fan 0 of 1
Cooling 8: Fan 0 of 1
Cooling 9: Fan 0 of 1
Cooling 10: Fan 0 of 1
Cooling 11: Fan 0 of 1
Cooling 12: Fan 0 of 1
Cooling 13: Fan 0 of 1
After the last echo 0 on device 7, the fan start to run slowly, and with this:
root@sidbox1:~# echo 0 | sudo tee /sys/class/thermal/cooling_device8/cur_state
0
root@sidbox1:~# acpi -c
Cooling 0: LCD 0 of 10
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: Fan 1 of 1
Cooling 4: Fan 1 of 1
Cooling 5: Fan 0 of 1
Cooling 6: Fan 0 of 1
Cooling 7: Fan 0 of 1
Cooling 8: Fan 0 of 1
Cooling 9: Fan 0 of 1
Cooling 10: Fan 0 of 1
Cooling 11: Fan 0 of 1
Cooling 12: Fan 0 of 1
Cooling 13: Fan 0 of 1
root@sidbox1:~# echo 0 | sudo tee /sys/class/thermal/cooling_device9/cur_state
0
\root@sidbox1:~#acpi -c
Cooling 0: LCD 0 of 10
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: Fan 1 of 1
Cooling 4: Fan 0 of 1
Cooling 5: Fan 0 of 1
Cooling 6: Fan 0 of 1
Cooling 7: Fan 0 of 1
Cooling 8: Fan 0 of 1
Cooling 9: Fan 0 of 1
Cooling 10: Fan 0 of 1
Cooling 11: Fan 0 of 1
Cooling 12: Fan 0 of 1
Cooling 13: Fan 0 of 1
root@sidbox1:~# echo 0 | sudo tee /sys/class/thermal/cooling_device10/cur_state
0
root@sidbox1:~# acpi -c
Cooling 0: LCD 0 of 10
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: Fan 0 of 1
Cooling 4: Fan 0 of 1
Cooling 5: Fan 0 of 1
Cooling 6: Fan 0 of 1
Cooling 7: Fan 0 of 1
Cooling 8: Fan 0 of 1
Cooling 9: Fan 0 of 1
Cooling 10: Fan 0 of 1
Cooling 11: Fan 0 of 1
Cooling 12: Fan 0 of 1
Cooling 13: Fan 0 of 1
root@sidbox1:~#
all seems to return normally, as with kernel 3.17.x .
But obviously i'm not sure if this is a correct way to solve the problem.
regards
Massimo
please do not force-stop the cooler, otherwise you risk overheating and death of components
inxi output already reveals the nvidia driver in its version 340.65... the question remains which package version that actually is. most probably it is 340.65-0.siduction.2 from siduction/fixes/
MaxStone, please provide the output of
dpkg -l | grep nvidia
interestingly to note is that nvidia seems to work fine with 3.17.xx but not with 3.18.xx for you. I suppose that this situation will require towo to look at it.
Hi Absolut
Regarding overheating I'm sure that this not happens because the Laptop have an external base with fan and the termal is controlled until I wait to solve the problem definitively:
root@sidbox1:~# acpi -t
Thermal 0: ok, 30.0 degrees C
Thermal 1: ok, 28.1 degrees C
Thermal 2: ok, 40.0 degrees C
Thermal 3: ok, 54.0 degrees C
Thermal 4: ok, 55.0 degrees C
Thermal 5: ok, 45.0 degrees C
root@sidbox1:~# dpkg -l | grep nvidia
ii glx-alternative-nvidia 0.5.1 amd64 allows the selection of NVIDIA as GLX provider
ii libegl1-nvidia:amd64 340.65-1 amd64 NVIDIA binary EGL libraries
ii libgl1-nvidia-glx:amd64 340.65-1 amd64 NVIDIA binary OpenGL libraries
ii libgl1-nvidia-glx:i386 340.65-1 i386 NVIDIA binary OpenGL libraries
ii libgl1-nvidia-glx-i386 340.65-1 i386 NVIDIA binary OpenGL 32-bit libraries
ii libnvidia-eglcore:amd64 340.65-1 amd64 NVIDIA binary EGL core libraries
ii libnvidia-ml1:amd64 340.65-1 amd64 NVIDIA Management Library (NVML) runtime library
ii nvidia-alternative 340.65-1 amd64 allows the selection of NVIDIA as GLX provider
ii nvidia-driver 340.65-1 amd64 NVIDIA metapackage
ii nvidia-driver-bin 340.65-1 amd64 NVIDIA driver support binaries
ii nvidia-glx 340.65-1 amd64 transition to nvidia-driver
ii nvidia-installer-cleanup 20141201+1 amd64 cleanup after driver installation with the nvidia-installer
ii nvidia-kernel-common 20141201+1 amd64 NVIDIA binary kernel module support files
ii nvidia-kernel-dkms 340.65-1 amd64 NVIDIA binary kernel module DKMS source
ii nvidia-modprobe 340.46-1 amd64 utility to load NVIDIA kernel modules and create device nodes
ii nvidia-settings 340.46-2 amd64 tool for configuring the NVIDIA graphics driver
ii nvidia-support 20141201+1 amd64 NVIDIA binary graphics driver support files
ii nvidia-vdpau-driver:amd64 340.65-1 amd64 Video Decode and Presentation API for Unix - NVIDIA driver
ii xserver-xorg-video-nvidia 340.65-1 amd64 NVIDIA binary Xorg driver
Hi guys,
due to a problem on nvidia driver crash, I install a different
nvidia-kernel-dkms
as suggested by this threadth
http://forum.siduction.org/index.php?topic=5233.msg42833#msg42833 (http://forum.siduction.org/index.php?topic=5233.msg42833#msg42833)
this solve the Driver crash, but the FAN cooling remain always!
now the system is in this state:
root@sidbox1:~# dpkg -l | grep nvidia
ii glx-alternative-nvidia 0.5.1 amd64 allows the selection of NVIDIA as GLX provider
ii libegl1-nvidia:amd64 340.65-1 amd64 NVIDIA binary EGL libraries
ii libgl1-nvidia-glx:amd64 340.65-1 amd64 NVIDIA binary OpenGL libraries
ii libgl1-nvidia-glx:i386 340.65-1 i386 NVIDIA binary OpenGL libraries
ii libgl1-nvidia-glx-i386 340.65-1 i386 NVIDIA binary OpenGL 32-bit libraries
ii libnvidia-eglcore:amd64 340.65-1 amd64 NVIDIA binary EGL core libraries
ii libnvidia-ml1:amd64 340.65-1 amd64 NVIDIA Management Library (NVML) runtime library
ii nvidia-alternative 340.65-1 amd64 allows the selection of NVIDIA as GLX provider
ii nvidia-driver 340.65-1 amd64 NVIDIA metapackage
ii nvidia-driver-bin 340.65-1 amd64 NVIDIA driver support binaries
ii nvidia-glx 340.65-1 amd64 transition to nvidia-driver
ii nvidia-installer-cleanup 20141201+1 amd64 cleanup after driver installation with the nvidia-installer
ii nvidia-kernel-common 20141201+1 amd64 NVIDIA binary kernel module support files
ii nvidia-kernel-dkms 340.65-0.siduction.2 amd64 NVIDIA binary kernel module DKMS source
ii nvidia-modprobe 340.46-1 amd64 utility to load NVIDIA kernel modules and create device nodes
ii nvidia-settings 340.46-2 amd64 tool for configuring the NVIDIA graphics driver
ii nvidia-support 20141201+1 amd64 NVIDIA binary graphics driver support files
ii nvidia-vdpau-driver:amd64 340.65-1 amd64 Video Decode and Presentation API for Unix - NVIDIA driver
ii xserver-xorg-video-nvidia 340.65-1 amd64 NVIDIA binary Xorg driver
regards
Hi guys,
I perform more tests and I see this:
boot using kernel 3.18.1:
root@sidbox1:~# uname -a
Linux sidbox1 3.18-1.towo.3-siduction-amd64 #1 SMP PREEMPT siduction 3.18-7 (2015-01-06) x86_64 GNU/Linux
root@sidbox1:~# sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +40.0°C (crit = +105.0°C)
temp2: +70.0°C (crit = +256.0°C)
temp3: +46.0°C (crit = +105.0°C)
temp4: +39.0°C (crit = +105.0°C)
temp5: +28.6°C (crit = +105.0°C)
temp6: +100.0°C (crit = +110.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +49.0°C (high = +100.0°C, crit = +100.0°C)
Core 1: +49.0°C (high = +100.0°C, crit = +100.0°C)
And FAN run Always!!!
Conversely if I boot with kernel 3.17-4:
root@sidbox1:~# sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +40.0°C (crit = +105.0°C)
temp2: +70.0°C (crit = +256.0°C)
temp3: +46.0°C (crit = +105.0°C)
temp4: +39.0°C (crit = +105.0°C)
temp5: +28.6°C (crit = +105.0°C)
temp6: +30.0°C (crit = +110.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +49.0°C (high = +100.0°C, crit = +100.0°C)
Core 1: +49.0°C (high = +100.0°C, crit = +100.0°C)
And the fan run correctly !!
So I think this maybe a sort of bug in sensor temperature read performed by the new kernel 3.18.1
Can anyone help me ?
This is my HW:
# sensors-detect revision 6209 (2014-01-14 22:51:58 +0100)
# System: Hewlett-Packard HP Compaq 8510w [F.05] (laptop)
# Board: Hewlett-Packard 30C5
Regards
Massimo
Genaueres zu Konfigurationsunterschieden müsste towo wissen, aber Du könntest ja mal in den beiden Kernelconfigs auf Spurensuche gehen und nach Begriffen wie fan, acpi, sensors greppen ob es da konkrete Unterschiede gibt.
grep -i fan /boot/config-3.18-1.towo.3-siduction-amd64
Hi der_bud
I don't know so mutch ... LANG=de :D
but many thanks for you kindly reply!!
Regarding your request:
root@sidbox1:~# grep -i fan /boot/config-3.18-1.towo.3-siduction-amd64
CONFIG_RCU_FANOUT=64
CONFIG_RCU_FANOUT_LEAF=16
# CONFIG_RCU_FANOUT_EXACT is not set
CONFIG_ACPI_FAN=m
# CONFIG_SENSORS_W83795_FANCTRL is not set
CONFIG_FANOTIFY=y
# CONFIG_FANOTIFY_ACCESS_PERMISSIONS is not set
the same for 3.17-4
root@sidbox1:~# grep -i fan /boot/config-3.17-4.towo-siduction-amd64
CONFIG_RCU_FANOUT=64
CONFIG_RCU_FANOUT_LEAF=16
# CONFIG_RCU_FANOUT_EXACT is not set
CONFIG_ACPI_FAN=m
# CONFIG_SENSORS_W83795_FANCTRL is not set
CONFIG_FANOTIFY=y
# CONFIG_FANOTIFY_ACCESS_PERMISSIONS is not set
How can I ask help to towo?
regards
Massimo
ups, sorry for posting the wrong language, had been in a german thread in another browsertab ;). But you certainly got me right, I proposed to compare differences in kernel configs in regards to fan, acpi or sensors.
You could probably ask towo directly in irc chat at oftc-channel #siduction, and I'll ask him to take a look at this thread.
Hello Max,
Sensors has me this output: ~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +24.0°C (crit = +127.0°C)
temp2: +28.0°C (crit = +100.0°C)
thinkpad-isa-0000
Adapter: ISA adapter
fan1: 0 RPM
temp1: +24.0°C
temp2: +26.0°C
temp3: +26.0°C
temp4: -1.0°C
temp5: +23.0°C
temp6: N/A
temp7: +23.0°C
temp8: N/A
temp9: +26.0°C
temp10: +29.0°C
temp11: +33.0°C
temp12: N/A
temp13: N/A
temp14: N/A
temp15: N/A
temp16: N/A
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +29.0°C (high = +105.0°C, crit = +105.0°C)
Core 1: +25.0°C (high = +105.0°C, crit = +105.0°C)
I wonder, have you ever sensors-detect
executed?
My system
~$ inxi -SG
System: Host: siduction Kernel: 3.18-1.towo.3-siduction-amd64 x86_64 (64 bit)
Desktop: LXDE (Openbox 3.5.2)
Distro: siduction 12.1 Desperado - lxde - (201205212234)
Graphics: Card: Intel Mobile 4 Series Integrated Graphics Controller
Display Server: X.Org 1.16.2.901 drivers: intel (unloaded: fbdev,vesa)
Resolution: 1680x1050@59.98hz
GLX Renderer: Mesa DRI Mobile Intel GM45 Express
GLX Version: 2.1 Mesa 10.3.2