(old)Puppy Linux Discussion Forum

Hello,

- I am using Puppy Linux 5.28 and the fan is really annoying - anyone know how to control the fan on/off and speed?

- Found some tools for Acer/Dell computers... but those i dont think will work on my Samsung X360

Thanks for any help,

Best regads,
Johan

Johan, it looks like fancontrol and lm-sensors are the pkgs you need to tame that beast..

Hello Semme,

- THanks for that - my fan sounds like an old boat engine..

- do you have an url to a pet for that program?

- found a program in puppys puppy package mamager "fancontrol" but no instructions on how to use it... .

THanks for help,

Best regards,
Johan

Divisionmd, like myself, it's possible you'll have to go another route should the following routine not pan out.

With both pkgs installed, open a shell'n issue: sensors

If there's readout, fine. If not: sensors-detect and follow the prompts.

I ran all probes except the final. With readout- copy'n paste.

Failing the above, are there any fan specific options in BIOS?

To note: I suppose the potential for a bad fan bearing exists..

One other possibility you may be able to work with- ESDM!

Hello Semme,

- Many thanks for all the inputs..

- will go through and test this...

- Found no setting in bios...

- By the way when testing "sensors" it tells me i am missing kernel modules?

Best regards,
Johan

Johan, read through this entire page and comment as Micro questioned, when your fan's coming on. Sounds like it might be plenty dirty and have a bad bearing to boot. If it's coming on right away or too often then it may very well be related to heat caused by blocked air passages. And, there isn't *any* software that'll address this condition.

Now about the rest of my previous post, you didn't comment on running: sensors-detect....

Samsung CPU-fan/wifi/backlight control is now supported in the 3.0-series kernels with a new driver called "samsung-laptop". This will apply to recent Puppy versions such as Slacko 5.3.x and Racy.

But with older kernels such as in Puppy Lucid 5.2.8, you need the "easy-slow-down-manager" drivers, which I just posted here -
http://www.murga-linux.com/puppy/viewto ... 345#604345

Great tempestuous,

Will test that right away! now i can hopefully turn off the boat engine...

Over and out,

Best regards,
Johan

I knew Fluppy had it, not 5.28. I saw the mention....

Nice Valentines present Johan. Lucky you...

==

Tempestuous, does depmod-FULL in pinstall handle the loading of these @ boot?

Depmod creates a "Makefile"-like dependency file, based on the symbols it finds in the set of modules mentioned on the command line or from the directories specified in the configuration file. This dependency file is later used by modprobe to automatically load the correct module or stack of modules.

Hmm.. it appears to make it "visible" for modprobe.. but about modules.conf? Nah, mus go like this!

Semme wrote:would you afford me a quick overview on how you built this pkg- so I can learn something for my effort?

The dotpet package creation process is this:
create a directory with the same name that you want the dotpet to named. Let's say that this directory is called "mygreatdotpet-0.1"
Into this put your newly created files, under the correct directory structure.
Add a post-install script at the uppermost level, if required.
Now navigate in a console to where your dotpet directory is located, and run this command; and follow the gui prompts. Voila.

Semme wrote:does depmod-FULL in pinstall handle the loading of these @ boot?

No, depmod-FULL registers the presence of newly-added kernel modules.
To auto-load these new drivers at boot up you should add the appropriate commands to /etc/rc.d/rc.local

tempestuous,

Many thanks now i got the fan under control! and computer is finally usable!! without annoying sound.

Over and out,

Best regards,
Johan

I meant the modules, the easy-slow-down-manager modules. I realized it's a "C" pkg and, since they're modules/drivers, know the 2.6.33.2 kernel src needs to reside in my stable. I've downloaded the patched.sfs and'll see if I can piece together how everything gets executed`cause.. I'd love to be able to do this stuff on my own. I'll keep you posted if I have trouble with the sfs path or duplicating your pet build..

OK. Source path = /usr/src/linux-2.6.33.2. Good! One step closer..