Hello!
I recently changed from openSUSE Tumbleweed to 13.1, since my root and home BTRFS had unrecoverable errors.
This means that the fans previously worked on this laptop, with 12.2/12.3-based Tumbleweed versions.
The hardware is a Toshiba Qosmio X770-107.
openSUSE version:
Edit: It probably wouldn't matter in this case, but I am running KDE 4.11.2.
Kernel and parameters:
I tried "acpi_osi=Windows" and 'acpi_osi="Windows 2000"' without success.
The toshiba_acpi module is loaded:
ACPI knows that there is cooling devices:
There is no "fan" or "thermal" entry in /proc/acpi/ or /proc/acpi/toshiba/:
There are cooling devices listed under /sys:
All have cur_state = 0 and max_state = 3.
I can manually write to the /sys cooling devices and stop my laptop from overheating qith 100 degrees Celsius all the time:
pwmconfig says there are no compatible sensor modules installed. I wonder if this is actually true:
sensors-detect finds that 'coretemp' should be used:
coretemp is loaded:
So this is where I just do not get further.
Automatic fan control has worked on this hardware with openSUSE < 13.1. How can I make it work again?
Thank you very much in advance for any hints and help!
Klaus
I recently changed from openSUSE Tumbleweed to 13.1, since my root and home BTRFS had unrecoverable errors.
This means that the fans previously worked on this laptop, with 12.2/12.3-based Tumbleweed versions.
The hardware is a Toshiba Qosmio X770-107.
openSUSE version:
Code:
firefly:/home/klaus # lsb_release -a
LSB Version: n/a
Distributor ID: openSUSE project
Description: openSUSE 13.1 (Bottle) (x86_64)
Release: 13.1
Codename: BottleKernel and parameters:
Code:
Linux version 3.11.6-4-desktop (geeko@buildhost) (gcc version 4.8.1 20130909 [gcc-4_8-branch revision 202388] (SUSE Linux) ) #1 SMP PREEMPT Wed Oct 30 18:04:56 UTC 2013 (e6d4a27)Command line: BOOT_IMAGE=/vmlinuz-3.11.6-4-desktop root=/dev/mapper/system-root resume=/dev/system/swap splash=silent quiet showopts acpi_osi=Linux acpi_backlight=vendor modeset.nouveau=0 vga=0x31bThe toshiba_acpi module is loaded:
Code:
firefly:/home/klaus # lsmod | grep toshiba
toshiba_acpi 22853 0
sparse_keymap 13948 1 toshiba_acpi
toshiba_bluetooth 12852 0
rfkill 26487 5 bluetooth,cfg80211,toshiba_acpi
wmi 19070 2 mxm_wmi,toshiba_acpiCode:
firefly:/home/klaus # acpi -V
Battery 0: Unknown, 99%
Battery 0: design capacity 3200 mAh, last full capacity 2323 mAh = 72%
Adapter 0: on-line
Cooling 0: pkg-temp-0 no state information available
Cooling 1: Processor 0 of 3
Cooling 2: Processor 0 of 3
Cooling 3: Processor 0 of 3
Cooling 4: Processor 0 of 3
Cooling 5: Processor 0 of 3
Cooling 6: Processor 0 of 3
Cooling 7: Processor 0 of 3
Cooling 8: Processor 0 of 3Code:
firefly:/home/klaus # ls /proc/acpi/
ac_adapter battery button event toshiba wakeup
firefly:/home/klaus # ls /proc/acpi/toshiba/
keys versionCode:
firefly:/home/klaus # ls /sys/devices/virtual/thermal/*
/sys/devices/virtual/thermal/cooling_device0:
cur_state device max_state power subsystem type uevent
/sys/devices/virtual/thermal/cooling_device1:
cur_state device max_state power subsystem type uevent
/sys/devices/virtual/thermal/cooling_device2:
cur_state device max_state power subsystem type uevent
/sys/devices/virtual/thermal/cooling_device3:
cur_state device max_state power subsystem type uevent
/sys/devices/virtual/thermal/cooling_device4:
cur_state device max_state power subsystem type uevent
/sys/devices/virtual/thermal/cooling_device5:
cur_state device max_state power subsystem type uevent
/sys/devices/virtual/thermal/cooling_device6:
cur_state device max_state power subsystem type uevent
/sys/devices/virtual/thermal/cooling_device7:
cur_state device max_state power subsystem type uevent
/sys/devices/virtual/thermal/thermal_zone0:
policy power subsystem temp trip_point_0_temp trip_point_0_type trip_point_1_temp trip_point_1_type type ueventI can manually write to the /sys cooling devices and stop my laptop from overheating qith 100 degrees Celsius all the time:
Code:
firefly:/home/klaus # cat bin/fan3
#!/bin/bash
echo 3 > /sys/devices/virtual/thermal/cooling_device0/cur_state;
cat /sys/devices/virtual/thermal/cooling_device0/cur_stateCode:
firefly:/home/klaus # pwmconfig
# pwmconfig revision 6166 (2013-05-01)
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.
We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.
/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installedCode:
firefly:/home/klaus # sensors-detect
# sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
# System: TOSHIBA QOSMIO X770 [PSBY5E-00G014DU] (laptop)
# Board: TOSHIBA PGRAA
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH)
Module i2c-dev loaded successfully.
Next adapter: NVIDIA i2c adapter 0 at 1:00.0 (i2c-0)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: NVIDIA i2c adapter 1 at 1:00.0 (i2c-1)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: NVIDIA i2c adapter 2 at 1:00.0 (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: NVIDIA i2c adapter 5 at 1:00.0 (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: NVIDIA i2c adapter 7 at 1:00.0 (i2c-4)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: NVIDIA i2c adapter 8 at 1:00.0 (i2c-5)
Do you want to scan it? (yes/NO/selectively): yes
Next adapter: NVIDIA i2c adapter 11 at 1:00.0 (i2c-6)
Do you want to scan it? (yes/NO/selectively): yes
Adapter cannot be probed, skipping.
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/sysconfig/lm_sensors? (YES/no):
Copy prog/init/lm_sensors.service to /lib/systemd/system
and run 'systemctl enable lm_sensors.service'
for initialization at boot time.
Unloading i2c-dev... OK
Unloading cpuid... OKCode:
firefly:/home/klaus # lsmod | grep temp
x86_pkg_temp_thermal 14162 0
coretemp 13435 0
thermal_sys 36646 3 x86_pkg_temp_thermal,video,processorAutomatic fan control has worked on this hardware with openSUSE < 13.1. How can I make it work again?
Thank you very much in advance for any hints and help!
Klaus