[opensuse] OpenSUSE 10.2 Laptop runs hot after resume
After upgrading to OpenSUSE 10.2 my HP nx 6125 can finaly hibernate and resume. But I now notice that once I have resumed from a hibernate the machine runs very hot. Normally the CPU temperature is between 40 and 50 deg Celcius. After a resume, it ranges between 65 and 85, averaging around 70. THe machine is not doing any more work than before, the CPU usage is on average 5% If I reboot the machine then it runs at 40-50 again with same CPU usage. Does anybody have similar experience? Any ideas what could cause it? Thanks -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dňa Pi 22. December 2006 08:26 Andre Truter napísal:
After upgrading to OpenSUSE 10.2 my HP nx 6125 can finaly hibernate and resume. But I now notice that once I have resumed from a hibernate the machine runs very hot.
Normally the CPU temperature is between 40 and 50 deg Celcius. After a resume, it ranges between 65 and 85, averaging around 70. THe machine is not doing any more work than before, the CPU usage is on average 5% If I reboot the machine then it runs at 40-50 again with same CPU usage.
Does anybody have similar experience? Any ideas what could cause it?
Hello Andre, can you tell me please what I need to do suspend to ram in nx6125 with suse 10.2. Do you have fglrx driver on XPRESS 200M graphics?? thanks, miso
Dňa Pi 22. December 2006 10:38 Michal Hlavac napísal:
Dňa Pi 22. December 2006 08:26 Andre Truter napísal:
After upgrading to OpenSUSE 10.2 my HP nx 6125 can finaly hibernate and resume. But I now notice that once I have resumed from a hibernate the machine runs very hot.
Normally the CPU temperature is between 40 and 50 deg Celcius. After a resume, it ranges between 65 and 85, averaging around 70. THe machine is not doing any more work than before, the CPU usage is on average 5% If I reboot the machine then it runs at 40-50 again with same CPU usage.
Does anybody have similar experience? Any ideas what could cause it?
Hello Andre,
can you tell me please what I need to do suspend to ram in nx6125 with suse 10.2. Do you have fglrx driver on XPRESS 200M graphics??
I mean resume-from-ram because suspend to ram works for me... m.
On 12/22/06, Michal Hlavac
Hello Andre,
can you tell me please what I need to do suspend to ram in nx6125 with suse 10.2. Do you have fglrx driver on XPRESS 200M graphics??
I mean resume-from-ram because suspend to ram works for me...
I don't have suspend-to-ram working, only suspend-to-disk (Hibernate) with successful resume. I don't think suspend-to-ram works on the HP nx6125 -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2006-12-22 at 11:51 +0200, Andre Truter wrote:
I don't have suspend-to-ram working, only suspend-to-disk (Hibernate) with successful resume. I don't think suspend-to-ram works on the HP nx6125
On a fresh install with only the included drivers it does work very well. Not through the menus, but if you open a console and type: s2ram -f it works and resumes fine. There is a config file somewhere (I think /etc/pm - I'm not in 10.2 now to check) where you can put arguments for s2ram in. I haven't had a chance to start installing drivers for the ATI graphics, ndiswrapper and all the various external bits I have, so I can't say how it works under those conditions. Will report back when I get around to it, which might only be next year. Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2006-12-22 at 09:26 +0200, Andre Truter wrote:
Any ideas what could cause it?
Two ideas. One, check what kernel modules are loaded before and after, and compare. Look for things like fan or acpi. Maybe play removing and reloading some. Another idea is, if your cpu is "throtable", perhaps "after" it is set to maximun speed. I think the state can bee seen somewhere under /proc, perhaps cpuinfo, or /proc/acpi/processor/CPU0/throttling. A third idea, have a look at the values under /proc/acpi/processor/ before and after. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFi9lPtTMYHG2NR9URAhEpAKCLuQVjibWVHcgq0u17XPJjUlOpoACfUL23 uXusvGtakTT8/4OPTxRVnbE= =tNk4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/22/06, Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Friday 2006-12-22 at 09:26 +0200, Andre Truter wrote:
Any ideas what could cause it?
Two ideas. One, check what kernel modules are loaded before and after, and compare. Look for things like fan or acpi. Maybe play removing and reloading some.
No, the modules looks the same. No acpi or fan modules are ever present, but thermal, processor, powernow_k8, cpufreq_* are all there before and after hibernate
Another idea is, if your cpu is "throtable", perhaps "after" it is set to maximun speed. I think the state can bee seen somewhere under /proc, perhaps cpuinfo, or /proc/acpi/processor/CPU0/throttling.
Nope, it is throttling nicely before and after.
A third idea, have a look at the values under /proc/acpi/processor/ before and after.
Looks the same before and after. All files are empty. Now that I think a little more about it, it might be a hardware problem, because I have had the same situation before when I run it on battery power for a while. It runs hot on battery power and when I connect it again to AC, it keeps on running hot. But this does not happen every time I run it on battery. -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 22 December 2006 23:27, Andre Truter wrote:
Now that I think a little more about it, it might be a hardware problem, because I have had the same situation before when I run it on battery power for a while. It runs hot on battery power and when I connect it again to AC, it keeps on running hot. But this does not happen every time I run it on battery.
This isn't one of those exploding battery laptops is it Andre? -- _____________________________________ John Andersen
On Saturday 23 December 2006 00:27, Andre Truter wrote:
...
A third idea, have a look at the values under /proc/acpi/processor/ before and after.
Looks the same before and after. All files are empty.
Are those files actually empty, or is it just that you're looking at the file size reported by "ls -l"? Because the zero size reported by ls is not true for many of the introspective files in /proc. E.g.: % ls -l /proc/acpi total 0 dr-xr-xr-x 2 root root 0 2006-12-23 07:48 ac_adapter/ -rw-r--r-- 1 root root 0 2006-12-23 07:48 alarm dr-xr-xr-x 2 root root 0 2006-12-23 07:48 battery/ dr-xr-xr-x 3 root root 0 2006-12-23 07:48 button/ -r-------- 1 root root 0 2006-12-23 07:48 dsdt dr-xr-xr-x 2 root root 0 2006-12-23 07:48 embedded_controller/ -r-------- 1 root root 0 2006-12-21 11:07 event -r-------- 1 root root 0 2006-12-23 07:48 fadt dr-xr-xr-x 2 root root 0 2006-12-23 07:48 fan/ -r--r--r-- 1 root root 0 2006-12-23 07:48 info dr-xr-xr-x 2 root root 0 2006-12-23 07:48 power_resource/ dr-xr-xr-x 4 root root 0 2006-12-23 07:48 processor/ -rw-r--r-- 1 root root 0 2006-12-23 07:48 sleep dr-xr-xr-x 2 root root 0 2006-12-23 07:48 thermal_zone/ -rw-r--r-- 1 root root 0 2006-12-23 07:48 wakeup % cat /proc/acpi/alarm 2006-12-00 00:03:25 % cat /proc/acpi/dsdt |wc -c 35110 % cat /proc/acpi/fadt 2ACP�A M I OEMFACP MSFT�@ �� ��' % cat /proc/acpi/info version: 20060707 % cat /proc/acpi/sleep S0 S1 S3 S4 S5 Etc. Hmmm... I wonder what that "MSFT" is about. It looks suspiciously like Microsoft's stock symbol.
... Andre Truter
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/23/06, Randall R Schulz
On Saturday 23 December 2006 00:27, Andre Truter wrote:
...
A third idea, have a look at the values under /proc/acpi/processor/ before and after.
Looks the same before and after. All files are empty.
Are those files actually empty, or is it just that you're looking at the file size reported by "ls -l"? Because the zero size reported by ls is not true for many of the introspective files in /proc.
Ah, yes, you are correct. I checked it again and the processor stuff is the same, but I did notice that the fan stuff differ. /proc/acpi/fan/C260/state differ. Before a Hibernate, it says : status : on After the Hibernate, it says: status: off So, it seams that the fan stays off after a hibernate. I tried to reload the powernow_k8 module, but nothing changes. -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 24 December 2006 10:22, Andre Truter wrote:
On 12/23/06, Randall R Schulz
wrote: On Saturday 23 December 2006 00:27, Andre Truter wrote:
...
A third idea, have a look at the values under /proc/acpi/processor/ before and after.
Looks the same before and after. All files are empty.
Are those files actually empty, or is it just that you're looking at the file size reported by "ls -l"? Because the zero size reported by ls is not true for many of the introspective files in /proc.
Ah, yes, you are correct.
I checked it again and the processor stuff is the same, but I did notice that the fan stuff differ. /proc/acpi/fan/C260/state differ.
Before a Hibernate, it says : status : on After the Hibernate, it says: status: off
Very dangerous. You should did thru the hibernate settings to see if you can find something relating to these. In the mean time, you can create a script which you can run as root, or periodically via cron: echo on >/proc/acpi/fan/C260/state -- _____________________________________ John Andersen
On 12/25/06, John Andersen
I checked it again and the processor stuff is the same, but I did notice that the fan stuff differ. /proc/acpi/fan/C260/state differ.
Before a Hibernate, it says : status : on After the Hibernate, it says: status: off
Very dangerous.
The system fan stil comes on at 80 deg and goes off at 75 deg again, so the system does not overheat. It just runs hot and every now and again, the fan comes on.
You should did thru the hibernate settings to see if you can find something relating to these.
I am systematically going through the settings and trying different things, but so far nothing.
In the mean time, you can create a script which you can run as root, or periodically via cron:
echo on >/proc/acpi/fan/C260/state
Nope, this has no effect.
I did notice that when the machine resumes or when powersaved is
restarted, then this message is logged:
--<snip>--
Dec 25 10:01:51 fullyautomatix powersaved[5928]: WARNING
(continueEvent:287) Could not execute program
/usr/lib/powersave/scripts for event daemon.scheme.change: No such
file or directory
--<snip>--
I also noted that I get the following messages during hibernation and
during restore:
--<snip>--
Dec 25 09:47:28 fullyautomatix kernel: mmc0: Card is consuming too much power!
Dec 25 09:47:28 fullyautomatix kernel: mmc0: Unexpected interrupt
0x00800000. Please report this to
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-12-25 at 12:05 +0200, Andre Truter wrote:
The system fan stil comes on at 80 deg and goes off at 75 deg again, so the system does not overheat. It just runs hot and every now and again, the fan comes on.
Then it could be a changed setting in fan triggering, or that it is a different "thing" which is triggering the fan.
I did notice that when the machine resumes or when powersaved is restarted, then this message is logged: --<snip>-- Dec 25 10:01:51 fullyautomatix powersaved[5928]: WARNING (continueEvent:287) Could not execute program /usr/lib/powersave/scripts for event daemon.scheme.change: No such file or directory --<snip>--
I guess that could be classified as a bug. Some script is missing or a misspelled one is called. Bugzilla? Perhaps when the scheme changes temperature settings are changed, and other things. But a part of it is missing. I'm just guessing, of course.
I also noted that I get the following messages during hibernation and during restore:
--<snip>-- Dec 25 09:47:28 fullyautomatix kernel: mmc0: Card is consuming too much power! Dec 25 09:47:28 fullyautomatix kernel: mmc0: Unexpected interrupt
If that is true and a card is consuming too much, it also increase the temperature, but would it affect the cpu? Or is it just a temporary situation while restoring, then the kernel gets control of things? Unless a kernel developper has a look at it :-?
0x00800000. Please report this to
.
You could try that, or report it to bugzilla, so that Novell people do.
Dec 25 09:47:28 fullyautomatix kernel: sdhci: =========================================== --<snip>--
Maybe this has something to do with it?
Who knows? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFj6xstTMYHG2NR9URAvqWAJ9abtHwr5NFkMjur5zVtkT2mKZU2QCfSYfJ Uzs+FoLM3rT50h/SczCcq7Q= =H3fh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/25/06, Carlos E. R.
The system fan stil comes on at 80 deg and goes off at 75 deg again, so the system does not overheat. It just runs hot and every now and again, the fan comes on.
Then it could be a changed setting in fan triggering, or that it is a different "thing" which is triggering the fan.
Yes, it seems that the fan is set to off after a hibernate. /proc/acpi/fan/C263/state changes from "status: on" to "status: off", but I have no idea what is causing it. All powersave settings are the same, and all acpi related modules are the same. Maybe I should try and reload the fan module after a hibernate.. I'll give that a go and see what happens. [...]
Perhaps when the scheme changes temperature settings are changed, and other things. But a part of it is missing.
THe scheme does not change as far as I know. [...]
If that is true and a card is consuming too much, it also increase the temperature, but would it affect the cpu? Or is it just a temporary situation while restoring, then the kernel gets control of things? Unless a kernel developper has a look at it :-?
0x00800000. Please report this to
. You could try that, or report it to bugzilla, so that Novell people do.
I did report it to the given email address. Hopefully the sdhci guys will make some sense of it. -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/25/06, Andre Truter
Yes, it seems that the fan is set to off after a hibernate. /proc/acpi/fan/C263/state changes from "status: on" to "status: off", but I have no idea what is causing it. All powersave settings are the same, and all acpi related modules are the same.
Maybe I should try and reload the fan module after a hibernate.. I'll give that a go and see what happens.
I had to stop acpid and force remove the fan module to get it out. Then, when I restart acpid, it loads the fan module again, but the fan is still set to off. --<snip>-- Dec 25 13:33:13 fullyautomatix kernel: ACPI: Transitioning device [C260] to D3 Dec 25 13:33:13 fullyautomatix kernel: ACPI: Transitioning device [C260] to D3 Dec 25 13:33:13 fullyautomatix kernel: ACPI: Fan [C260] (off) Dec 25 13:33:13 fullyautomatix kernel: ACPI: Transitioning device [C261] to D3 Dec 25 13:33:13 fullyautomatix kernel: ACPI: Transitioning device [C261] to D3 Dec 25 13:33:13 fullyautomatix kernel: ACPI: Fan [C261] (off) Dec 25 13:33:13 fullyautomatix kernel: ACPI: Transitioning device [C262] to D3 Dec 25 13:33:13 fullyautomatix kernel: ACPI: Transitioning device [C262] to D3 Dec 25 13:33:13 fullyautomatix kernel: ACPI: Fan [C262] (off) Dec 25 13:33:13 fullyautomatix kernel: ACPI: Transitioning device [C263] to D3 Dec 25 13:33:13 fullyautomatix kernel: ACPI: Transitioning device [C263] to D3 Dec 25 13:33:13 fullyautomatix kernel: ACPI: Fan [C263] (off) Dec 25 13:33:14 fullyautomatix atieventsd[4264]: acpid connection established --<snip>-- So, something is telling acpi that the fan should not come on again. (Transision to D3) BIOS maybe? But according the the BIOS, this should just be a shutdown and reboot. Suspend-to-disk is not a BIOS function or is it? -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
In a previous post you mentioned an error message which said that /usr/lib/powersave/scripts couldn't be found. Did you check for that directory... to see whether it exists...? and what its permissions and ownership are? Does this directory contain any files? If so, what are the permissions and ownership on them? Does the information gathered from the above correspond to the output of "rpm -ql powersave"? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/25/06, ken
In a previous post you mentioned an error message which said that /usr/lib/powersave/scripts couldn't be found. Did you check for that directory... to see whether it exists...? and what its permissions and ownership are? Does this directory contain any files? If so, what are the permissions and ownership on them?
Does the information gathered from the above correspond to the output of "rpm -ql powersave"?
The directory contains a number of scripts that is part of the rpm and does have read and execute permissions for everyone. So this must be a powersave bug. -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-12-25 at 13:39 +0200, Andre Truter wrote:
Maybe I should try and reload the fan module after a hibernate.. I'll give that a go and see what happens.
I had to stop acpid and force remove the fan module to get it out. Then, when I restart acpid, it loads the fan module again, but the fan is still set to off.
--<snip>--
So, something is telling acpi that the fan should not come on again.
Some configuration that is not acting. I was thinking of something related to this: |> Perhaps when the scheme changes temperature settings are changed, and |> other things. But a part of it is missing. |> | | THe scheme does not change as far as I know. Your scheme may be the same, but after the resume I suppose it has to be applied, and there was an script error reported. It might be that, or not. If you can investigate it, try, if not, perhaps it's bugzilla time.
(Transision to D3) BIOS maybe? But according the the BIOS, this should just be a shutdown and reboot. Suspend-to-disk is not a BIOS function or is it?
Yes, it is, but it can be bypassed. It's an option, in fact, use bios or not. There is a setting for that (or there was). [...] Found these (10.1): - -rwxr-xr-x 1 root root 8125 May 2 2006 /usr/sbin/fancontrol* - -rwxr-xr-x 1 root root 10425 May 2 2006 /usr/sbin/fancontrol.pl* HTH. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFj8JDtTMYHG2NR9URAmD/AJ9CtO7cUAd4too3EogxH8nbxf+HywCeIjF0 4Q9j7gcfL4wU81Tnba0y42o= =HDBI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2006-12-25 at 13:39 +0200, Andre Truter wrote:
Maybe I should try and reload the fan module after a hibernate.. I'll give that a go and see what happens. I had to stop acpid and force remove the fan module to get it out. Then, when I restart acpid, it loads the fan module again, but the fan is still set to off.
--<snip>--
So, something is telling acpi that the fan should not come on again.
Some configuration that is not acting. I was thinking of something related to this:
|> Perhaps when the scheme changes temperature settings are changed, and |> other things. But a part of it is missing. |> | | THe scheme does not change as far as I know.
Your scheme may be the same, but after the resume I suppose it has to be applied, and there was an script error reported. It might be that, or not. If you can investigate it, try, if not, perhaps it's bugzilla time.
(Transision to D3) BIOS maybe? But according the the BIOS, this should just be a shutdown and reboot. Suspend-to-disk is not a BIOS function or is it?
Yes, it is, but it can be bypassed. It's an option, in fact, use bios or not. There is a setting for that (or there was).
[...]
Found these (10.1):
- -rwxr-xr-x 1 root root 8125 May 2 2006 /usr/sbin/fancontrol* - -rwxr-xr-x 1 root root 10425 May 2 2006 /usr/sbin/fancontrol.pl*
HTH.
- -- Cheers, Carlos E. R.
My apologies for butting in but I was just looking for something in the Control Center and came across Power Management option and inside it Power Management Scheme Setup. I wonder if this could have anything to do with what is now being discussed in this thread? If not then accept my sorries. Cheers. -- In a period of great joy and pleasure you are comforted by the thought that tragedy is just around the corner. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/25/06, Carlos E. R.
|> Perhaps when the scheme changes temperature settings are changed, and |> other things. But a part of it is missing. |> | | THe scheme does not change as far as I know.
Your scheme may be the same, but after the resume I suppose it has to be applied, and there was an script error reported. It might be that, or not. If you can investigate it, try, if not, perhaps it's bugzilla time.
I did try to change the scheme to Acourtic and then back to Performance, but that does not make any difference. This seems to be only a problem on my machine. I have not heard any other nx6125 users having the same problem. Anyone out there with similar problems?
[...]
Found these (10.1):
- -rwxr-xr-x 1 root root 8125 May 2 2006 /usr/sbin/fancontrol* - -rwxr-xr-x 1 root root 10425 May 2 2006 /usr/sbin/fancontrol.pl*
I'll look into these, thatnks. -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-12-25 at 21:00 +0200, Andre Truter wrote:
| THe scheme does not change as far as I know.
Your scheme may be the same, but after the resume I suppose it has to be applied, and there was an script error reported. It might be that, or not. If you can investigate it, try, if not, perhaps it's bugzilla time.
I did try to change the scheme to Acourtic and then back to Performance, but that does not make any difference.
Well, if there is a bug somewhere, I wouldn't expect it to work, not for sure.
This seems to be only a problem on my machine. I have not heard any other nx6125 users having the same problem.
Perhaps there are not many users of that system reading this, or they are not so perceptive. It doesn't mean they don't have the problem. Or they may be celebrating Christmas, you know ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFkC9htTMYHG2NR9URAnGhAKCJQuwTSXWGtyU0zmEW4tDbFLgsNQCfab0l Pf/XYFkQsNCAb+RPRjql26w= =LuVp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/25/06, Carlos E. R.
I did try to change the scheme to Acourtic and then back to Performance, but that does not make any difference.
Well, if there is a bug somewhere, I wouldn't expect it to work, not for sure.
The schemes does work when you disconnect AC and it even change the fan state: On AC: ---<snip>-- fullyautomatix:/proc/acpi/fan/C263 # powersave -x Performance active AC_default_scheme Acoustic Presentation Powersave battery_default_scheme fullyautomatix:/proc/acpi/fan/C263 # cat state status: on --<snip>-- On Battery: --<snip>-- fullyautomatix:/proc/acpi/fan/C263 # powersave -x Performance AC_default_scheme Acoustic Presentation Powersave active battery_default_scheme fullyautomatix:/proc/acpi/fan/C263 # cat state status: off --<snip>-- Back on AC: --<snip>-- fullyautomatix:/proc/acpi/fan/C263 # powersave -x Performance active AC_default_scheme Acoustic Presentation Powersave battery_default_scheme fullyautomatix:/proc/acpi/fan/C263 # cat state status: on --<snip>-- Now I wonder if it only fails if the temperature goes above a certain level and you connect the AC again, or maybe it is if it has been on battery for a certain time, because it has happened a few times in the past that when I run on battery and go back to AC, the machine also keeps on running hot.
This seems to be only a problem on my machine. I have not heard any other nx6125 users having the same problem.
Perhaps there are not many users of that system reading this, or they are not so perceptive. It doesn't mean they don't have the problem.
Or they may be celebrating Christmas, you know ;-)
Hmm, yes, I forgot about that.. -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/26/06, Andre Truter
Now I wonder if it only fails if the temperature goes above a certain level and you connect the AC again, or maybe it is if it has been on battery for a certain time, because it has happened a few times in the past that when I run on battery and go back to AC, the machine also keeps on running hot.
OK, I managed to re-create the problem. I ran the machine now for about 20 minutes and managed to get the CPU temperature up to 77 deg C. When I connected AC again, the schema changed back to Performance according to powersave, but the fan is still in an off state. So, the fan state works when you run on battery for a short while, but not for a longer period of time. -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2006-12-25 at 13:39 +0200, Andre Truter wrote:
On 12/25/06, Andre Truter
wrote: Yes, it seems that the fan is set to off after a hibernate. /proc/acpi/fan/C263/state changes from "status: on" to "status: off", but I have no idea what is causing it. All powersave settings are the same, and all acpi related modules are the same.
What other items do you have in /proc/acpi/fan/? It appears that we are looking at more then one fan here. Also the "status" reading may not be a switch that can be changed but only a place holder for what is actually happening. You may have to set a value elsewhere to turn the fan on and off. And the value may only show "on" when the fan is actually running. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/25/06, Kenneth Schneider
On Mon, 2006-12-25 at 13:39 +0200, Andre Truter wrote:
On 12/25/06, Andre Truter
wrote: Yes, it seems that the fan is set to off after a hibernate. /proc/acpi/fan/C263/state changes from "status: on" to "status: off", but I have no idea what is causing it. All powersave settings are the same, and all acpi related modules are the same.
What other items do you have in /proc/acpi/fan/? It appears that we are looking at more then one fan here.
Yes, there are 4 fans (C260 - C263). I only mentioned the last one as the others are always in an off state.
Also the "status" reading may not be a switch that can be changed but only a place holder for what is actually happening. You may have to set a value elsewhere to turn the fan on and off. And the value may only show "on" when the fan is actually running.
Yes, I assume that it is only and indicator. Problem is that I have no idea what to do to control the fan or to just change it's state. I tried the powersave settings, but that have no effect. -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2006-12-25 at 20:57 +0200, Andre Truter wrote:
On 12/25/06, Kenneth Schneider
wrote: On Mon, 2006-12-25 at 13:39 +0200, Andre Truter wrote:
On 12/25/06, Andre Truter
wrote: Yes, it seems that the fan is set to off after a hibernate. /proc/acpi/fan/C263/state changes from "status: on" to "status: off", but I have no idea what is causing it. All powersave settings are the same, and all acpi related modules are the same.
What other items do you have in /proc/acpi/fan/? It appears that we are looking at more then one fan here.
Yes, there are 4 fans (C260 - C263). I only mentioned the last one as the others are always in an off state.
OK. What is under C263, there may be something there to set and get the fan back to normal operation. Sometimes you can echo 1 (or 0) into the "file" to turn something on and off. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/25/06, Kenneth Schneider
Yes, there are 4 fans (C260 - C263). I only mentioned the last one as the others are always in an off state.
OK. What is under C263, there may be something there to set and get the fan back to normal operation. Sometimes you can echo 1 (or 0) into the "file" to turn something on and off.
Only one file : "state" and it contains one of the following: status: on or status: off -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Andre Truter
-
Basil Chupin
-
Carlos E. R.
-
Hans du Plooy
-
John Andersen
-
ken
-
Kenneth Schneider
-
Michal Hlavac
-
Randall R Schulz