OpenSuse 11.2 x64 - just installed along side Win 7 x64

KL51 · 12-06-2009, 02:53 AM

Hi guys

Today I installed OpenSuse 11.2 64 bit in dual boot with Win 7 64 bit on an HP DV6 1130TX laptop (duo with 4GB memory).

The install went off without a hitch. However, I am a bit concerned about the CPU fan running almost flat out and a large amount of heat being generated by the laptop, considering that system tools show that CPU idling at only a few percent of capacity. On the Windows 7 side when the CPU is in the same state, the fan is off and there is no real heat to be felt from the underside of the laptop.

So, why is it that with the CPU nice and quiet, it seems to be generating a bucket load of heat, requiring the fan to be running at almost break-neck speed, continuously?

TIA

pixellany · 12-06-2009, 08:25 AM

How about the clock speed? Even if there are NO processes running, the CPU running at the full clock speed will consume significant power. In your menus, find the setup for CPU frequency scaling.

KL51 · 12-06-2009, 04:52 PM

Quote:

Originally Posted by pixellany

How about the clock speed? Even if there are NO processes running, the CPU running at the full clock speed will consume significant power. In your menus, find the setup for CPU frequency scaling.

Thanks for that pixellany. I'll look into this this evening, and report back

KL51 · 12-07-2009, 02:48 AM

Well, I have had a look in the Power Management settings and set the CPU scaling for the current profile to 'on demand' and rebooted.

It's unfortunately made no difference - the underside of the laptop is still very warm, and of course the fan is whirring away.

(BTW, I previously had the laptop running both Vista and Ubu 32 bit and had no issues such as this on the Ubu side).

Below is the output from cpufreq-info. It appears that both cores are running at their minimum speed. So why the heat and the fans? Could it be that tools such as this are not reporting properly?

To be continued...

ATB for now.

Code:

linux-crze:/home/user # cpufreq-info -m
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to http://bugs.opensuse.org, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 0
  hardware limits: 800 MHz - 2.13 GHz
  available frequency steps: 2.13 GHz, 1.60 GHz, 800 MHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance
  current policy: frequency should be within 800 MHz and 2.13 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 need to switch frequency at the same time: 1
  hardware limits: 800 MHz - 2.13 GHz
  available frequency steps: 2.13 GHz, 1.60 GHz, 800 MHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance
  current policy: frequency should be within 800 MHz and 2.13 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).

KL51 · 12-07-2009, 03:28 AM

Its been a bit over 30 mins since my post above. In this time, the CPU fan has throttled right back three times for about 5 seconds each time, then arced up again to its current level.

Nothing special going on at any of these times, yet the fan demed it appropriate to have a 5 second breather before re-commencing its weirdness.

Bizarre. FYI only

KL51 · 12-07-2009, 04:10 AM

OK, some more output from cpufreq-info.

Note:
cpufreq-info -w
cpufreq-info -f
cpufreq-info -m

If the human readable output (-m) regarding the current CPU speed is 800MHz, then why the discrepancy with the output using -w ?

If the output using the -w switch is correct, then we at least have a reason for the heat and fan. But if this is the case, then why the difference between this and the -m output?

Code:

linux-crze:/home/user # cpufreq-info -w
2133000
linux-crze:/home/user # cpufreq-info -f
800000
linux-crze:/home/user # cpufreq-info -m
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to http://bugs.opensuse.org, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which need to switch frequency at the same time: 0
  hardware limits: 800 MHz - 2.13 GHz
  available frequency steps: 2.13 GHz, 1.60 GHz, 800 MHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance
  current policy: frequency should be within 800 MHz and 2.13 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 need to switch frequency at the same time: 1
  hardware limits: 800 MHz - 2.13 GHz
  available frequency steps: 2.13 GHz, 1.60 GHz, 800 MHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance
  current policy: frequency should be within 800 MHz and 2.13 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).
linux-crze:/home/user #

Code:

 -f, --freq Get frequency the CPU currently runs at according to the cpufreq core *

  -w, --hwfreq  Get frequency the CPU currently runs at, by reading it from hardware (only available to root) *

-m, --human human-readable output for the -f, -w and -s parameters

To be continued

KL51 · 12-08-2009, 01:36 AM

Well, it's a day later and I am no closer to a solution. I can't seem to find anything to describe a reason for the fan/CPU behaviour under times of no load.

If anyone has any thoughts, I'm all ears

KL51 · 12-11-2009, 05:18 AM

Well, I am stumped - a few days of detective work has turned up nothing. If anyone has any thoughts please share them soon - otherwise my x64 Suse will be whacked and replaced with another distro.

I'd rather not do this, but its looking increasingly like I have no choice