Mageia forum

I have a Samsung NP350 laptop. Since I started using Mageia I've been having overheating issues, but it's gotten to extremes lately. The temperature slowly rises up to 105°C, at which point the computer shuts down.

Here's the output of sensors:

Code: Select all

$ sensors
radeon-pci-0100
Adapter: PCI adapter
temp1:        +93.0°C 

acpitz-virtual-0
Adapter: Virtual device
temp1:        +97.0°C  (crit = +210.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +97.0°C  (high = +87.0°C, crit = +105.0°C)
Core 0:         +92.0°C  (high = +87.0°C, crit = +105.0°C)
Core 1:         +97.0°C  (high = +87.0°C, crit = +105.0°C)
Core 2:         +92.0°C  (high = +87.0°C, crit = +105.0°C)
Core 3:         +94.0°C  (high = +87.0°C, crit = +105.0°C)


And cpupower

Code: Select all

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: 1.20 GHz - 2.40 GHz
  available frequency steps: 2.40 GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.10 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 1.90 GHz and 1.90 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1.90 GHz (asserted by call to hardware).
  boost state support:
    Supported: yes
    Active: yes
    25500 MHz max turbo 4 active cores
    25500 MHz max turbo 3 active cores
    25500 MHz max turbo 2 active cores
    25500 MHz max turbo 1 active cores


I double-boot Windows 7 and I don't have an overheating problem with windows (even when gaming). But with Mageia I overheat even if the cpu usage stays at an average of 20%.

I think it is running full speed all the time. It seems to be using performance instead of ondemand. After you change it, reboot.

Here are previous posts about the subject: https://forums.mageia.org/en/search.php?keywords=ondemand&fid%5B0%5D=7

The answer may be a few posts down in this thread: https://forums.mageia.org/en/viewtopic.php?f=7&t=5808&p=39041&hilit=ondemand#p39041

It's not running full speed, according to cpupower. As you can see in the original post, it's running at 1.9 GHz out of 2.4 GHz. It's also not using performance:

Code: Select all

$ cat /etc/sysconfig/cpupower
# See 'cpupower help' and cpupower(1) for more info
CPUPOWER_START_OPTS="frequency-set -g ondemand"
CPUPOWER_STOP_OPTS="frequency-set -g ondemand"

I seen it was running 1.9 so I thought anything above that was turbo.

hers an output from mine as a comparison.

Code: Select all

[root@localhost ~]# sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +47.0°C  (crit = +108.0°C)

asus-isa-0000
Adapter: ISA adapterregards peter
temp1:        +47.0°C 

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +46.0°C  (high = +87.0°C, crit = +105.0°C)
Core 0:         +46.0°C  (high = +87.0°C, crit = +105.0°C)
Core 1:         +40.0°C  (high = +87.0°C, crit = +105.0°C)

[root@localhost ~]# cat /etc/sysconfig/cpupower
# See 'cpupower help' and cpupower(1) for more info
CPUPOWER_START_OPTS="frequency-set -g ondemand"
CPUPOWER_STOP_OPTS="frequency-set -g ondemand"
[root@localhost ~]#

I also add the following to my rc.local

echo deadline > /sys/block/sda/queue/scheduler
echo 1 > /sys/block/sda/queue/iosched/fifo_batch
iw wlan0 set power_save on
echo 5 > /proc/sys/vm/laptop_mode
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 10 > /sys/module/snd_hda_intel/parameters/power_save
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
for i in /sys/bus/usb/devices/*/power/autosuspend; do echo 1 > $i; done
# those sysctl's are only available if you have an AHCI compatible SATA
# controler and use kernel > 2.6.24-rc2 (or use Kristen ALPM patchset) :
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
echo min_power > /sys/class/scsi_host/host1/link_power_management_policy
echo min_power > /sys/class/scsi_host/host2/link_power_management_policy
echo min_power > /sys/class/scsi_host/host3/link_power_management_policy
echo min_power > /sys/class/scsi_host/host4/link_power_management_policy
echo min_power > /sys/class/scsi_host/host5/link_power_management_policy


and i have a custom udev rule

root@localhost ~]# cat /etc/udev/rules.d/10-runtime-pm.rules
SUBSYSTEM!="pci", GOTO="power_runtime_rules_end"
ACTION!="add", GOTO="power_runtime_rules_end"

KERNEL=="????:??:??.?"
PROGRAM="/bin/sleep 0.1"

ATTR{power/control}=="*", ATTR{power/control}="auto"

LABEL="power_runtime_rules_end"
[root@localhost ~]#


regards peter

The issue is probably more related to the fan and ACPI controls.
Maybe you should read up on that, e.g. http://whitequark.org/blog/2011/09/04/f ... sung-n250/

What about the fan, is it running at all?

Apart from that didn't find anything useful for your model, seems pretty rare :/

Hi.

You can try a manual override of the bios fan controls ...

All you need is the lm-sensors package ...

as root do

Code: Select all

sensors-detect

then restart. Now we start the config script:

Code: Select all

pwmconfig

If this script detects fancontrol devices, you have won. Then it will test the control possibilites - it will stop and start your fans, so only do this with a cooled down laptop. After that, you have the possibility to generate a config-file for fancontrol (/etc/fancontrol). Basically pwmconfig now needs the temp., when the fan should increase the speed and the temp. of full speed. If all is done, you can start your new fancontrol with

Code: Select all

fancontrol &

.

I did this with a small but powerful Shuttle DS61 with a 45W i5 cpu, which is sitting next to me on my desktop, so the fans were a little too loud under normal circumstances. With fancontrol now the harddisk is the loudest until a core temp of 45 degrees C, but if the core temp should ever reach 80 degrees C, the fans will produce a real hurricane ...

hope this helps,
cheers,

Bernd

Hello all,

I like to hook into this old thread because it perfectly matches my topic.
I have done all the steps above, and starting "fancontrol &" manually will bring the desired silence.

Now, with the systemd based Mageia 4 distro, what is the preferred approach to get this automated for each boot?
-- Do I have to write my own systemd job, or is there anything where I can hook into?

Thanks in advance and kind regards,
Marcus