Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 22 Sep 2017, 09:21
All times are UTC - 4
 Forum index » Advanced Topics » Hardware
How I learned to control my (Intel CPU-based) Fujitsu fan
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [5 Posts]  
Author Message
Marv


Joined: 04 May 2005
Posts: 858
Location: SW Wisconsin

PostPosted: Fri 20 Jan 2017, 00:48    Post subject:  How I learned to control my (Intel CPU-based) Fujitsu fan  

Finally, a cure for my Fujitsu Laptop hair trigger fan blues. First off, thanks to norgo, LateAdopter, and Billtoo for the pointers and discussion on intel_pstate. Thanks to rcrsn51 and others who had a hand in CPUtemp, I am running v1.9.

The laptops: These are all intel, circa 2004 to 2008, and have Pentium M (Banias), core duo (Yonah), and core 2 duo (Penryn) processors.

The pups: X-slacko 3bx through 4.2, X-Tahr 1bx through 2.0, LxPupSc up to 17.01.25. Probably others but not tested 1:1.

The problem: System fan goes from nothing to full on with the slightest load or sometimes (with the Yonah) completely on its own with no use. acpi-cpufreq & governors are always applied, either ondemand or conservative. CPU temperatures are never over 45 degrees Celsius. All extraneous services have been eliminated and unused ports and services turned off in the BIOS. gvfsd-metadata is under control. CPU use in Lxtask at idle is 3 to 10%, depending on processor and pup.

Background: Intel introduced support for its P-State governor in the SandyBridge processor circa 2011. All of the above processors precede that by a wide margin.

The kernels I have used in these machines: 3.14.20, 3.14.56, 3.15.4, 3.17.x, 4.1.31. and 4.8.x through 4.9.4. All have intel_pstate=y in the DOTCONFIGs as do pretty much all of the post 3.x.x pup kernels I have looked at.

The solution: As suggested by the members above (sorry if I missed any), pass intel_pstate=disable as a kernel parameter as in the following Grub4Dos line.
Code:
kernel /LxPupSc/vmlinuz pmedia=ataflash ignore=usb pdev1=sda1 psubdir=LxPupSc intel_pstate=disable pfix=copy ipv6.disable=1

With that passed, the fans now follow the governor and CPU temperature nicely. CPU temperatures remain in the mid 40 Celsius range in normal use and just enough fan is used to keep them there. Change the governor parameters and the fan use changes with them. No use, no fan!

It won't raise fans from the dead or tame real toasters but for me it made the load/temperature/fan use much more rational. I really don't know the mechanism for the p_state interference but it seems to over-ride my governor settings in the OS even though the processors don't support it.

_________________
Pups currently in kennel Very Happy X-slacko 4.3 and X-tahr 2.0 for my users; LxPupSc and LxPupXenial for me. All good pups indeed, and all running browsers, office etc. solely from SFS.
Back to top
View user's profile Send private message 
april


Joined: 14 Sep 2013
Posts: 974
Location: Water winging it back home to Cairns finally

PostPosted: Tue 24 Jan 2017, 17:53    Post subject:  

I read this with interest having just tipped a machine that was doing funny things with the fan and closing down the machine on next to no workload . All thermal contact paste was replaced to no avail.

Quote:
Thanks to rcrsn51 and others who had a hand in CPUtemp, I am running v1.9.


I see rcrsn51 is involved in some of what you quote and have noticed some shady stuff going on in his threads and posts . "PM me and i'll send you the program" . All executeable binaries only . No source. See Barry Kaulers post on this also
http://murga-linux.com/puppy/viewtopic.php?t=102321&start=65

I would take care there.Did you download any of his fixes prior to the trouble ?
http://murga-linux.com/puppy/viewtopic.php?t=109145&start=6

Last edited by april on Wed 25 Jan 2017, 07:45; edited 7 times in total
Back to top
View user's profile Send private message Yahoo Messenger 
april


Joined: 14 Sep 2013
Posts: 974
Location: Water winging it back home to Cairns finally

PostPosted: Tue 24 Jan 2017, 18:03    Post subject:  

Code:
kernel /LxPupSc/vmlinuz pmedia=ataflash ignore=usb pdev1=sda1 psubdir=LxPupSc intel_pstate=disable pfix=copy ipv6.disable=1


Can you explain at all further what this does please ?
Back to top
View user's profile Send private message Yahoo Messenger 
Marv


Joined: 04 May 2005
Posts: 858
Location: SW Wisconsin

PostPosted: Tue 24 Jan 2017, 20:46    Post subject:  

@april,

Lets deal with two things quite separately.

First with respect to rcrsn51. As I explained in the post, I am using the version 1.9 of a pet publicly available on this forum. He and a number of other members worked on it. It allows a quick look from the panel at the system temperatures and CPU speed. It is a valuable diagnostic tool and has nothing to do with the system problem I'm troubleshooting. Please, let's use the forum as an information exchange and avoid personal attacks.

Second, the kernel parameters. A pretty comprehensive explanation is available here: http://puppylinux.org/wikka/BootParameters/ Specifically in my Grub4Dos line, the parameters work as follows:
pmedia=ataflash sets up puppy so writes to the media are minimized (PUPMODE=13)
ignore=usb is my personal way of dealing with slowness of systems returning a USB ready flag even when not booting from USB. I customize the init script to support it.
pdev1 and psubdir constrain/target puppys search for files and speed up the boot process.
intel_pstate=disable disables a kernel resident intel cpu speed governor which causes problems with many pre 2011 or so CPUs so the CPU governors in puppy can work properly
ipv6.disable=1 constrains pup to use only the older of two network address schemas

The only change made to 'fix' my CPU governors and fan control was to add the intel_pstate=disable parameter. It works a treat on my older all-intel machines, particularly a core duo laptop that was almost unusable before.

_________________
Pups currently in kennel Very Happy X-slacko 4.3 and X-tahr 2.0 for my users; LxPupSc and LxPupXenial for me. All good pups indeed, and all running browsers, office etc. solely from SFS.
Back to top
View user's profile Send private message 
april


Joined: 14 Sep 2013
Posts: 974
Location: Water winging it back home to Cairns finally

PostPosted: Wed 25 Jan 2017, 07:03    Post subject:  

OK thanks .
rcrsn51 won't give out his source code and thats the basis of all open source software . That's why I asked about your use of any of his binary packages before your problems stated above . Its not a personal attack its a pointer to use caution and an information exchange as you mention.

A pet sticks it on your machine as a binary . It does not tell you whats in it. Just because they are public does not mean they are safe. However we all use them trustingly from time to time . They are convenient.

I'm interested in the thermal runaway effect I have suffered on one of my machines.

"ipv6.disable=1" - I don't understand why you would do that.Whats wrong with Puppy's handling of it?
"intel_pstate=disable" - is the interesting one for me and I'll have to reinstate my old machine and play with it but I don't have a command called "intel_pstate" or a constant variable by that name so what are you doing to use this please?

Oh and my name is April not @april not that it matters my friend.
Back to top
View user's profile Send private message Yahoo Messenger 
Display posts from previous:   Sort by:   
Page 1 of 1 [5 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Hardware
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0886s ][ Queries: 13 (0.0102s) ][ GZIP on ]