OverDrive wrote:Update: It actually gets down to 48c after I move from the warm outside (82f/27.7c) to the cool inside. So the kernel is *not* a problem then.
OverDrive wrote:Update: It actually gets down to 48c after I move from the warm outside (82f/27.7c) to the cool inside. So the kernel is *not* a problem then.
Overdrive
Agreed
Not so fast:
Try it with a Hulu stream.
With the fix my Laptop is at 73c; compared to 63c on my 4.12 install.
Still better than before though.
Someone should lobby Barry to include this in the sysinit script. Every other distro that I know of handles this without user intervention. It gives the impression that Puppy sucks power and runs hot. I'd wager that the majority of Puppy users are running it on laptops.
---
If you want to keep your cpu cool under load, you need to use the powersave governor instead of ondemand. But your performance will suffer.
Not so fast:
Try it with a Hulu stream.
With the fix my Laptop is at 73c; compared to 63c on my 4.12 install.
Still better than before though.
Well... I've spent about a hour on Hulu @480p full screen (1280x800x24bit) and the temp did not go over 63c for my t2310 low end dual core cpu so I guess it's working ok for me.
I am too lazy to test it on my three laptops, I hate their keyboards and get bewildered when the temp goes up.
But sooner or later I will change to your suggestions too. Good that we all care about it.
I had a suspicion that the problem might be related to shinobar's 'acpid' package that I have in Quirky. The tweak I posted was to disable the 'acpid' daemon from starting.
OverDrive responded that it helped for him, but Bèèm responded that it didn't help. DaveS reported success, but I'm not sure what he did that solved it for him.
I am too lazy to test it on my three laptops, I hate their keyboards and get bewildered when the temp goes up.
But sooner or later I will change to your suggestions too. Good that we all care about it.
I had a suspicion that the problem might be related to shinobar's 'acpid' package that I have in Quirky. The tweak I posted was to disable the 'acpid' daemon from starting.
OverDrive responded that it helped for him, but Bèèm responded that it didn't help. DaveS reported success, but I'm not sure what he did that solved it for him.
I replaced start_cpu_freq in /root/startup with the working one from 4.3.1. Total success.
nooby wrote:Dave that is great. We all love total success.
Dare I as the resident Newbie ask how one do it?
I mean replace such things from one to the other?
I guess you use pfind and then just know which thing to delete and which to borrow from Puppy431.
You need to have 4.3* running on your PC. Just go int you /root/ directory and open the Startup folder. In there you will find a file called start_cpu_freq. Copy it to a USB stick then start Quirky and put the file in the startup folder in Quirky. If there is already a file there with that name, delete it first.
DaveS wrote:You need to have 4.3* running on your PC. Just go int you /root/ directory and open the Startup folder. In there you will find a file called start_cpu_freq. Copy it to a USB stick then start Quirky and put the file in the startup folder in Quirky. If there is already a file there with that name, delete it first.
On my 4.3.1 installs, that file is empty by default. Could you please post the contents of yours?
DaveS wrote:You need to have 4.3* running on your PC. Just go int you /root/ directory and open the Startup folder. In there you will find a file called start_cpu_freq. Copy it to a USB stick then start Quirky and put the file in the startup folder in Quirky. If there is already a file there with that name, delete it first.
On my 4.3.1 installs, that file is empty by default. Could you please post the contents of yours?
DaveS wrote:I think it is generated by running the frequency cpu scaling tool?
So is the issue with Quirky overheating just that people have not run the Utility>CPU Frequency Scaling Tool yet?
I dont think so. I ran the utility in quirky and none of the modules would work, though in EVERY other Puppy they do (including Lupu). THAT is where the problem lies. Copying over a known working module file, and having it work, proves the point?
DaveS wrote:I think it is generated by running the frequency cpu scaling tool?
So is the issue with Quirky overheating just that people have not run the Utility>CPU Frequency Scaling Tool yet?
I don't think it's quite that simple.
Cpu scaling does help with Quirky, and the other new releases; but
my 4.1.2 install, when playing dvd or video files runs 10c to 20c
cooler than any newer version starting with 4.3x.
DaveS wrote:I dont think so. I ran the utility in quirky and none of the modules would work, though in EVERY other Puppy they do (including Lupu). THAT is where the problem lies.
That's odd. I ran the utility on several machines and it worked every time.