Puppy Linux Discussion Forum

[prehistoric]

@tempestuous,

I apologize if this post is verbose, but I'm trying to avoid misunderstanding. I went back and downloaded those pets just before I ran this yesterday to get that depmod_FULL change you mention. I'm holding the installation which showed the problem on an SD card, so I can slip it in and exactly reproduce things. I'm hoping this will keep it from being contaminated by separate experiments.

First, results of modinfo:

[01micko]

Ok, sorry for getting a little off topic here.. but my pain with the p4-clockmod module does not exist, that is because the module is non-existent in 430-small.iso...(a bug reported in 430-small) (thanks anyway dawnsboy). The current compile of SHE is just not working on Puppy with the Eee-pc-701SD.

Back to the gui, which is the point here.. where are the other Celeron testers? I suppose this is an Atom thread so some are scared off. I will start a new thread to see if some folks with Celerons want to run some commands so I get a better picture. I may provide a minor upgrade in the meantime, with a few refinements.

Cheers.

[tempestuous]

prehistoric, the result from your "modinfo eee" command confirms that the eee module is loaded on your system.
So the fan control script should not complain about the /proc/eee directory being missing.

[01micko]

Ok testers,

Here is 0.4
Changelog
-changed "OK" button to close
-added a splash which shows up for a few seconds letting the user know something is happening
-changed the pinstall script to detect "stepping :6" (older Celerons) and will install the appropriate invoking script to /usr/bin... newer Celerons will use the atom GUI now (*rhadon's and my 701SD)

To Do
-there is no built in mechanism to detect what mode the machine is in at boot.
-it seems later Celerons are in "Normal" mode at boot, older Celerons "Powersave" and I'm not sure about Atoms.

I'm making a new thread for Celeron users, no older Celeron users have posted here so I'm just relying on tempestuous info and google.
Please offer any feedback

Enjoy

SEE NEWER POST V-0.5

[prehistoric]

[rhadon]

@ 01micko

Please, can you tell me which scripts I must delete manually to uninstall your eee-cpucontrol-03.pet? I can't find it in PPM.

Don't know what was going wrong, sometimes at shutdown the screen freezes and shows a lot of small squares in different grey colours and the only chance to go out is the poweroff button. Posted first by aarf here. I know you've read this post. Perhaps this was the reason.

Or can I just install the newer one over the old one?

~ Rolf

[01micko]

[dawnsboy]

@01micko

I downloaded and installed eee-cpucontrol-04.pet on my 701 4G, Intel Celeron 900MHz, 100MHz FSB Eeepc. It works quite well on Puppy Linux 4.3 k-2.6.25.16. Thank you.

cat /proc/eee/fsb echoes 70 24 1 in power save mode and 100 24 1 in performance mode. I believe that this version should work very well on all of the 701/900's that have a 100MHz FSB.

[01micko]

Thanks for report dawnsboy, that's the one I was looking for One thing, when you boot your machine is the fsb 70 or the last chosen mode?

Cheers

[dawnsboy]

@01micko

You are welcome. My machine reboots to default mode.

[01micko]

Thanks for prompt response dawnsboy. It looks as if all eeepcs boot into default mode. That being the case, the gui should reflect that. If it isn't I can fix it.

Cheers

[cthisbear]

01micko"

PM to you again in Puppy.

Chris.

[dawnsboy]

The gui does reflect that on this machine. Well done.

[tempestuous]

prehistoric,
Your problem might be that the eee module takes time to fully load, and the fan control script needs to wait a bit.
Please try adding "sleep 5" between the two commands; open /etc/rc.d/rc.local in Geany, and modify it to look like this -

[prehistoric]

@tempestuous,

Tried a "sleep 10" with no luck. Time to go back and make sure I'm testing what I intend. I would have done this today, if other tasks had not intervened.

-------

Latin motto for Puppy: