Coming Soon: Fluppy for netbooks, widescreens, smallscreens
I'm planning on adding it but I'm curious why people want to mess with the fan at all.
Does the kernel not handle your fan properly all by itself? The only time I've even had fan problems was after installing fan-control software. Are you trying to save power by not running the fan, or what?
-------
In case someone else has this problem too, I just wanted to mention that the latest bios update from Asus fixed the issue where the cpus would not go into low power mode after waking from suspend. So it was a firmware issue, not a kernel issue. Awesome!
Does the kernel not handle your fan properly all by itself? The only time I've even had fan problems was after installing fan-control software. Are you trying to save power by not running the fan, or what?
-------
In case someone else has this problem too, I just wanted to mention that the latest bios update from Asus fixed the issue where the cpus would not go into low power mode after waking from suspend. So it was a firmware issue, not a kernel issue. Awesome!
More good news. I got a graphical bluetooth wizard to work on puppy. This is ported from gnome...getting the applet to work will be much harder (if not impossible) as I will have to rip out a couple gnome dependencies.
- Attachments
-
- bluetoothwiz.jpg
- (39.48 KiB) Downloaded 1223 times
If you're looking to conserve power, the fan's specs in BIOS are not your friend, hence the need for manual control. The BIOS specs essentially don't turn the fan off once it's on--the cut-off temperature is 40C, impossible to reach. [I'm using the eee 900 for reference here]
I'm so discouraged by the temperature spiking in the current 4.3 (can't tell if it's the kernel or the puppy) that I've gone back to 4.12 for everyday use.
I have an sd card reserved for 4.3 and the testing of your kernel, but I'm a power junkie--if I have to use an a/c adapter on a netbook, then the battle's lost. Might as well use a regular laptop.
I save 7 seconds on the cold, frugal sd card boot when using 4.3, but suffer a 4 degree Celsius spike. So my fan is on much more in 4.3, and I'm losing battery b/c of it.
I have many fingers crossed for your kernel, but the temperature changes may be within 4.3, not the kernel, I just don't know.
Jake
I'm so discouraged by the temperature spiking in the current 4.3 (can't tell if it's the kernel or the puppy) that I've gone back to 4.12 for everyday use.
I have an sd card reserved for 4.3 and the testing of your kernel, but I'm a power junkie--if I have to use an a/c adapter on a netbook, then the battle's lost. Might as well use a regular laptop.
I save 7 seconds on the cold, frugal sd card boot when using 4.3, but suffer a 4 degree Celsius spike. So my fan is on much more in 4.3, and I'm losing battery b/c of it.
I have many fingers crossed for your kernel, but the temperature changes may be within 4.3, not the kernel, I just don't know.
Jake
Hmmm,
After reading that quote at the top of the page in the Powertop link you would think that the 4.3 kernel would use less power, as it is compiled "tickless". It could be Xorg 7.3. It's been a hassle on some of my old boxes. Maybe I should try ttuuxxx "Puppies 4.3.1.1" on my Eee, it has the same kernel with Xorg 7.0.
Cheers
After reading that quote at the top of the page in the Powertop link you would think that the 4.3 kernel would use less power, as it is compiled "tickless". It could be Xorg 7.3. It's been a hassle on some of my old boxes. Maybe I should try ttuuxxx "Puppies 4.3.1.1" on my Eee, it has the same kernel with Xorg 7.0.
Cheers
Puppy Linux Blog - contact me for access
Jakfish, have you turned on cpu frequency scaling?
Can you run powertop on both 4.3 and 4.1 and tell me what the wattage difference is? Or post schreenshots? The fsb underclocking hack solved the inconsistencies I was seeing on my machine.
Battery life is why I waited to buy a netbook until the 1005ha came out, the advertised 10 hour battery life translates into about 6 actual hours. Not too bad.
Can you run powertop on both 4.3 and 4.1 and tell me what the wattage difference is? Or post schreenshots? The fsb underclocking hack solved the inconsistencies I was seeing on my machine.
Battery life is why I waited to buy a netbook until the 1005ha came out, the advertised 10 hour battery life translates into about 6 actual hours. Not too bad.
01micko--
I'd be very interested to hear your results. I also, belatedly, see that BK relented and released a 4.3 with the older kernel.
I just don't know what's making it burn hotter--the kernel or the OS, or maybe my machine itself.
But at any rate, I'd be grateful for any insight from users more learned than me.
Jake
I'd be very interested to hear your results. I also, belatedly, see that BK relented and released a 4.3 with the older kernel.
I just don't know what's making it burn hotter--the kernel or the OS, or maybe my machine itself.
But at any rate, I'd be grateful for any insight from users more learned than me.
Jake
http://murga-linux.com/puppy/viewtopic.php?t=47267
needed modules for eee keys and fan-control
needed modules for eee keys and fan-control
Is there a link to source code for the eee module somewhere?
-----------
No wonder you're so running so hot, Jakfish! I can cook eggs on mine in performance mode. Can you link me to the relevant discussion?
Have you tried setting it manually?
-----------
No wonder you're so running so hot, Jakfish! I can cook eggs on mine in performance mode. Can you link me to the relevant discussion?
Have you tried setting it manually?
I'm pretty sure my EEE kernel sets it automatically. It should hopefully be up for download by tomorrow.Using Frequency Scaling Governors
You can get a list of available governors with (as root):
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
conservative ondemand powersave userspace performance
Note: If the governors are compiled as modules, load them first:
# modprobe cpufreq_performance cpufreq_ondemand cpufreq_conservative cpufreq_powersave cpufreq_userspace
Now we set our governor: What is our current governor?
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
userspace
Set new governor and watch if it has changed
# echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
conservative
See here for a workaround by ARAN: http://www.murga-linux.com/puppy/viewto ... 082#344082
maybe a better but larger workaround would be to use the larger iso and to merge the content of the zp*.sfs to the main pup-file.
aragon
maybe a better but larger workaround would be to use the larger iso and to merge the content of the zp*.sfs to the main pup-file.
aragon
PUPPY SEARCH: http://wellminded.com/puppy/pupsearch.html
I've heard of the cpu whining thing but either my netbook is quiet or my hearing is not that good.
On my netbook, eee-control does not modify the cpu frequency, strange... Are you seeing P-states and C-states in powertop? I wonder if acpi is working for you at all....
I've attached a screenshot of what powertop output looks like on my machine. How many C-states do you see when you're unplugged?
On my netbook, eee-control does not modify the cpu frequency, strange... Are you seeing P-states and C-states in powertop? I wonder if acpi is working for you at all....
I've attached a screenshot of what powertop output looks like on my machine. How many C-states do you see when you're unplugged?
- Attachments
-
- powertop.jpg
- (140.45 KiB) Downloaded 597 times
jemimah--
I'm no expert, but when using eeecontrol, I think the command to bring up the bona fide speed is this:
# cat /proc/eee/fsb
70 24 0
At least, this is what I use in my conky. Couple that with the increase/decrease whine of cpu speed makes me think that I'm getting genuine change.
As for powertop, I'm not getting your groovy readout:
Powertop
Cn Avg residency P-states (frequencies)
C0 (cpu running) (14.2%)
polling 0.0ms ( 0.0%)
C1 1.7ms ( 1.1%)
C2 2.0ms (15.7%)
C3 3.3ms (69.0%)
Wakeups-from-idle per second : 293.8 interval: 10.0s
no ACPI power usage estimate available
No detailed statistics available; please enable the CONFIG_TIMER_STATS kernel op
This option is located in the Kernel Debugging section of menuconfig
(which is CONFIG_DEBUG_KERNEL=y in the config file)
Note: this is only available in 2.6.21 and later kernels
I'm no expert, but when using eeecontrol, I think the command to bring up the bona fide speed is this:
# cat /proc/eee/fsb
70 24 0
At least, this is what I use in my conky. Couple that with the increase/decrease whine of cpu speed makes me think that I'm getting genuine change.
As for powertop, I'm not getting your groovy readout:
Powertop
Cn Avg residency P-states (frequencies)
C0 (cpu running) (14.2%)
polling 0.0ms ( 0.0%)
C1 1.7ms ( 1.1%)
C2 2.0ms (15.7%)
C3 3.3ms (69.0%)
Wakeups-from-idle per second : 293.8 interval: 10.0s
no ACPI power usage estimate available
No detailed statistics available; please enable the CONFIG_TIMER_STATS kernel op
This option is located in the Kernel Debugging section of menuconfig
(which is CONFIG_DEBUG_KERNEL=y in the config file)
Note: this is only available in 2.6.21 and later kernels
Isn't p4-clockmod found by the cpu scaling gui? I remember seeing that, I think (so much testing, so little progress). As you probably saw in the other threads, in 4.3, scaling/eee appears to produce only powersaving and performance setting, so there's no real scaling. Or at least I didn't get any.
I did get scaling to function in earlier puppies, 4.0/1, I think. And found only a lag in response with no accompanying battery/temperature savings.
Over in the forum.eeeuser.com, there was a general consensus that at least the 700/900 models didn't have a processor that played nice with scaling. It throttles rather than truly drops the CPU speed.
dawnsboy is a real expert at this. I'm just the guy who can't get it to work
I did get scaling to function in earlier puppies, 4.0/1, I think. And found only a lag in response with no accompanying battery/temperature savings.
Over in the forum.eeeuser.com, there was a general consensus that at least the 700/900 models didn't have a processor that played nice with scaling. It throttles rather than truly drops the CPU speed.
dawnsboy is a real expert at this. I'm just the guy who can't get it to work
Here's one for the books, and it connects to the cpu speed problems within the eee.
Background: I had been complaining that 4.3/new kernel was causing temperature spikes. So I went to 4.3/old kernel, but changed one other thing: my startup speed in BIOS. I had been starting at 900mz/Performance to shorten boot time, then w/ eeecontrol, dumbing down to 630 once puppy was up and running.
I decided to change to 630/power saving in BIOS and just keep it there. Lo and behold, my temperature's gone down 5 degrees Celsius. Before, (with 900mh BIOS speed/change in puppy to 600mh), after an hour or so, (no wifi, no fan, medium brightness, cpu between 10-12%), I was idling at about 56C. Same specs now, but I'm at 51C. That's a big drop.
Whiile a 900mh startup/eeecontrol-switch-to-630 may make fsb show the speed at 630, I'm almost convinced that the machine is throttling rather than reducing speed. Even with the cpu whining down, etc.
How else can I account for 5 degree drop? Everything else is the same except for BIOS speed change.
At any rate, I may be able to return to newer kernel and see what's what.
Jake
Background: I had been complaining that 4.3/new kernel was causing temperature spikes. So I went to 4.3/old kernel, but changed one other thing: my startup speed in BIOS. I had been starting at 900mz/Performance to shorten boot time, then w/ eeecontrol, dumbing down to 630 once puppy was up and running.
I decided to change to 630/power saving in BIOS and just keep it there. Lo and behold, my temperature's gone down 5 degrees Celsius. Before, (with 900mh BIOS speed/change in puppy to 600mh), after an hour or so, (no wifi, no fan, medium brightness, cpu between 10-12%), I was idling at about 56C. Same specs now, but I'm at 51C. That's a big drop.
Whiile a 900mh startup/eeecontrol-switch-to-630 may make fsb show the speed at 630, I'm almost convinced that the machine is throttling rather than reducing speed. Even with the cpu whining down, etc.
How else can I account for 5 degree drop? Everything else is the same except for BIOS speed change.
At any rate, I may be able to return to newer kernel and see what's what.
Jake