• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

[solved] Laptop y510p auf openSUSE im Leerlauf sehr warm

F

f33l

Newbie
Hallo zusammen,


ich habe es geschafft, auf meinem Lenovo Ideapad y510y openSUSE Tumbleweed (basierend auf 13.1) zu installieren. Nachdem ich zunaechst Probleme mit dem nvidia chip, dem kernel Treiber fuer das lan und zuletzt die Backlight Steuerung behoben habe, versuche ich jetzt etwas mehr Batterielaufzeit rauszuholen, die in jetziger Form leider unterirdisch ist.

Zunaechst habe ich den nouveau Treiber auf die blacklist gesetzt, damit nur die Intel Grafikkarte verwendet wird (im Moment habe ich ein Dual-boot fuer Spiele). Leider ist der Laptop selbst im Leerlauf (idle) relativ warm, d.h. der Luefter laeuft und es kommt spuerbar warme Luft aus dem Schacht. Darauf hin habe ich ueberprueft, ob die CPUs heruntergetaktet werden, musste aber feststellen, dass diese NIE unter 2400MHz gehen, obwohl sie bis auf 800MHz runter koennten:

Code: 
cpufreq-info 
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to http://bugs.opensuse.org, please.
analyzing CPU 0:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.40 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.40 GHz (asserted by call to hardware).
analyzing CPU 1:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.40 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.40 GHz (asserted by call to hardware).
analyzing CPU 2:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.40 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.40 GHz (asserted by call to hardware).
analyzing CPU 3:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.40 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.61 GHz (asserted by call to hardware).
analyzing CPU 4:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 4
  CPUs which need to have their frequency coordinated by software: 4
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.40 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.40 GHz (asserted by call to hardware).
analyzing CPU 5:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 5
  CPUs which need to have their frequency coordinated by software: 5
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.40 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.54 GHz (asserted by call to hardware).
analyzing CPU 6:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 6
  CPUs which need to have their frequency coordinated by software: 6
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.40 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.40 GHz (asserted by call to hardware).
analyzing CPU 7:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 7
  CPUs which need to have their frequency coordinated by software: 7
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.40 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.40 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.40 GHz (asserted by call to hardware).

Kann das sein? Was koennte man noch checken um den Fehler einzugrenzen?

Vielen Dank,
Chris

P.S. For the record:
Code: 
hwinfo --short
cpu:                                                            
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 2525 MHz
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 2785 MHz
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 2562 MHz
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 2804 MHz
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 2433 MHz
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 2817 MHz
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 2480 MHz
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 2766 MHz
keyboard:
  /dev/input/event0    AT Translated Set 2 keyboard
mouse:
  /dev/input/mice      SynPS/2 Synaptics TouchPad
graphics card:
                       Intel VGA compatible controller
                       nVidia VGA compatible controller
sound:
                       Intel Audio device
                       Intel Audio device
storage:
                       Intel SATA controller
network:
                       Attansic Ethernet controller
  wlan0                Intel WLAN controller
network interface:
  wlan0                WLAN network interface
  lo                   Loopback network interface
disk:
  /dev/sda             LITEONIT LSS-24L
  /dev/sdb             ST1000LM024 HN-M
partition:
  /dev/sda1            Partition
  /dev/sdb1            Partition
  /dev/sdb2            Partition
  /dev/sdb3            Partition
  /dev/sdb4            Partition
  /dev/sdb5            Partition
  /dev/sdb6            Partition
  /dev/sdb7            Partition
  /dev/sdb8            Partition
  /dev/sdb9            Partition
  /dev/sdb10           Partition
cdrom:
  /dev/sr0             MATSHITA BD-MLT UJ262
usb controller:
                       Intel USB Controller
                       Intel USB Controller
                       Intel USB Controller
bios:
                       BIOS
bridge:
                       Intel Host bridge
                       Intel PCI bridge
                       Intel PCI bridge
                       Intel PCI bridge
                       Intel PCI bridge
                       Intel ISA bridge
hub:
                       Linux 3.12.6-5.g080d0df-desktop xhci_hcd xHCI Host Controller
                       Linux 3.12.6-5.g080d0df-desktop xhci_hcd xHCI Host Controller
                       Linux 3.12.6-5.g080d0df-desktop ehci_hcd EHCI Host Controller
                       Hub
                       Linux 3.12.6-5.g080d0df-desktop ehci_hcd EHCI Host Controller
                       Hub
memory:
                       Main Memory
bluetooth:
                       Bluetooth Device
unknown:
                       FPU
                       DMA controller
                       PIC
                       Timer
                       Keyboard controller
                       PS/2 Controller
                       Intel Communication controller
                       Intel SMBus
  /dev/input/event16   Lenovo EasyCamera
 
OP
F

f33l

Newbie
Ich habe das Problem selbst geloest, und zwar geht es mit einem aelteren kernel (3.11 statt 3.12):

Code: 
hwinfo --short
cpu:                                                            
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 800 MHz
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 800 MHz
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 800 MHz
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 800 MHz
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 800 MHz
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 800 MHz
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 800 MHz
                       Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 800 MHz
keyboard:
  /dev/input/event0    AT Translated Set 2 keyboard
mouse:
  /dev/input/mice      SynPS/2 Synaptics TouchPad
graphics card:
                       Intel VGA compatible controller
                       nVidia VGA compatible controller
sound:
                       Intel Audio device
                       Intel Audio device
storage:
                       Intel SATA controller
network:
                       Attansic Ethernet controller
  wlan0                Intel WLAN controller
network interface:
  lo                   Loopback network interface
  wlan0                WLAN network interface
disk:
  /dev/sda             LITEONIT LSS-24L
  /dev/sdb             ST1000LM024 HN-M
partition:
  /dev/sda1            Partition
  /dev/sdb1            Partition
  /dev/sdb2            Partition
  /dev/sdb3            Partition
  /dev/sdb4            Partition
  /dev/sdb5            Partition
  /dev/sdb6            Partition
  /dev/sdb7            Partition
  /dev/sdb8            Partition
  /dev/sdb9            Partition
  /dev/sdb10           Partition
cdrom:
  /dev/sr0             MATSHITA BD-MLT UJ262
usb controller:
                       Intel USB Controller
                       Intel USB Controller
                       Intel USB Controller
bios:
                       BIOS
bridge:
                       Intel Host bridge
                       Intel PCI bridge
                       Intel PCI bridge
                       Intel PCI bridge
                       Intel PCI bridge
                       Intel ISA bridge
hub:
                       Linux 3.11.6-4-desktop xhci_hcd xHCI Host Controller
                       Linux 3.11.6-4-desktop xhci_hcd xHCI Host Controller
                       Linux 3.11.6-4-desktop ehci_hcd EHCI Host Controller
                       Hub
                       Linux 3.11.6-4-desktop ehci_hcd EHCI Host Controller
                       Hub
memory:
                       Main Memory
bluetooth:
                       Bluetooth Device
unknown:
                       FPU
                       DMA controller
                       PIC
                       Timer
                       Keyboard controller
                       PS/2 Controller
                       Intel Communication controller
                       Intel SMBus
  /dev/input/event8    Lenovo EasyCamera

und

Code: 
cpufreq-info 
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to http://bugs.opensuse.org, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.40 GHz
  available frequency steps: 2.40 GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.10 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz
  available cpufreq governors: ondemand, performance
  current policy: frequency should be within 800 MHz and 2.40 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).
analyzing CPU 1:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.40 GHz
  available frequency steps: 2.40 GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.10 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz
  available cpufreq governors: ondemand, performance
  current policy: frequency should be within 800 MHz and 2.40 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.40 GHz (asserted by call to hardware).
analyzing CPU 2:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.40 GHz
  available frequency steps: 2.40 GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.10 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz
  available cpufreq governors: ondemand, performance
  current policy: frequency should be within 800 MHz and 2.40 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).
analyzing CPU 3:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.40 GHz
  available frequency steps: 2.40 GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.10 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz
  available cpufreq governors: ondemand, performance
  current policy: frequency should be within 800 MHz and 2.40 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).
analyzing CPU 4:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 4
  CPUs which need to have their frequency coordinated by software: 4
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.40 GHz
  available frequency steps: 2.40 GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.10 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz
  available cpufreq governors: ondemand, performance
  current policy: frequency should be within 800 MHz and 2.40 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).
analyzing CPU 5:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 5
  CPUs which need to have their frequency coordinated by software: 5
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.40 GHz
  available frequency steps: 2.40 GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.10 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz
  available cpufreq governors: ondemand, performance
  current policy: frequency should be within 800 MHz and 2.40 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).
analyzing CPU 6:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 6
  CPUs which need to have their frequency coordinated by software: 6
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.40 GHz
  available frequency steps: 2.40 GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.10 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz
  available cpufreq governors: ondemand, performance
  current policy: frequency should be within 800 MHz and 2.40 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).
analyzing CPU 7:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 7
  CPUs which need to have their frequency coordinated by software: 7
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.40 GHz
  available frequency steps: 2.40 GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.10 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz
  available cpufreq governors: ondemand, performance
  current policy: frequency should be within 800 MHz and 2.40 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).

Ich frage mich, ob es nun damit zu tun hat, dass beim 3.11 kernel der Treiber acpi-cpufreq verwendet wird vs intel_pstate bei 3.12. Wie dem auch sei, ist meine Frage erstmal [solved].
 
J

josef-wien

Ultimate Guru
Offensichtlich hat sich die Logik zur Auswahl des "besten" Treibers geändert (in den Quellen des Kernel 3.11 steht in /usr/src/linux/drivers/cpufreq/Kconfig.x86 noch "will become the scaling driver and governor for Sandy bridge processors"). Du kannst ihn aber mit der Boot-Option
Code: 
intel_pstate=disable
deaktivieren.

f33l schrieb:
driver: intel_pstate
available cpufreq governors: performance, powersave
Zum Vergrößern anklicken....
bietet zwei Extreme, aber keine "goldene Mitte", dafür fehlt bei
f33l schrieb:
driver: acpi-cpufreq
available cpufreq governors: ondemand, performance
Zum Vergrößern anklicken....
dann "powersave" (wobei aber noch sehr individuell die Frage zu klären wäre, ob der durch eine längere Verarbeitungszeit entstehende Stromverbrauch der anderen Komponenten nicht höher wäre).
 
OP
F

f33l

Newbie
Vielen Dank fuer die Antwort, ich probiere es gleich mal aus, ob sich mit der boot option etwas aendert. Im Moment nutze ich einen alten kernel (bzw. den von opensuse 13.1) um das Problem zu umgehen. Was mich trotzdem ueberrascht, ist dass die Taktung der CPUs konstant hoch ist, obwohl der governor "powersave" zu Verfuegung steht.
 
OP
F

f33l

Newbie
Code: 
intel_pstate=disable

behebt das Problem auch fuer die neueren Kernels. Es sieht so aus als ob nur der governor "ondemand" das gewuenschte Verhalten hat, komisch, dass dieser nicht mit intel_pstate funktioniert.
 
J

josef-wien

Ultimate Guru
f33l schrieb:
obwohl der governor "powersave" zu Verfuegung steht
Zum Vergrößern anklicken....
Den mußt Du aber über ein Energieverwaltungsprogramm (Deiner grafischen Oberfläche) aktivieren.

f33l schrieb:
der governor "ondemand" ... nicht mit intel_pstate funktioniert
Zum Vergrößern anklicken....
Ich verstehe auch nicht, was sich die Kernel-Entwickler dabei gedacht haben, aber ich muß ja nicht alles verstehen.
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
Oben