i've just noticed that apm says : Performance Ajustment mode: normal (520 Mhz)
is it true that openbsd runs at 520 Mhz speed on the Zaurus ???
or does it go from 416 to 520 itself ?
is it the normal behavoiur ?
Full Version: 520 Mhz ?
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > OpenBSD
I guess it's because OBSD runs a bit slower than other distros, and the overclocking is intended to compensate for this.
btw I've just succeeded in swapping the internal MD with a Sandisk Extreme III 16GB CF. The system does feel faster in general. Now I need more time to set up everything again.
btw I've just succeeded in swapping the internal MD with a Sandisk Extreme III 16GB CF. The system does feel faster in general. Now I need more time to set up everything again.
QUOTE(jpmatrix @ Jun 1 2007, 08:55 PM)
i've just noticed that apm says : Performance Ajustment mode: normal (520 Mhz)
is it true that openbsd runs at 520 Mhz speed on the Zaurus ???
or does it go from 416 to 520 itself ?
is it the normal behavoiur ?
is it true that openbsd runs at 520 Mhz speed on the Zaurus ???
or does it go from 416 to 520 itself ?
is it the normal behavoiur ?
You can make the Zaurus processor run at 520Mhz via etc/sysctl.conf using:
machdep.maxspeed=520
If you comment out or change the above to 416 then it should run at the standard 416Mhz.
However, if you want the speed to be adjusted automatically then you'll have to utilize the following apm option:
QUOTE
-A Set apmd(8) to automatic performance adjustment mode. In this
mode, when CPU idle time falls below 10%, or if the AC power is
connected and the battery is more than 15% charged, apm raises
hw.setperf as much as possible. Otherwise, when the CPU idle
time is above 30% and the system is running on battery power, apm
lowers hw.setperf as much as possible to reduce power consump-
tion.
mode, when CPU idle time falls below 10%, or if the AC power is
connected and the battery is more than 15% charged, apm raises
hw.setperf as much as possible. Otherwise, when the CPU idle
time is above 30% and the system is running on battery power, apm
lowers hw.setperf as much as possible to reduce power consump-
tion.
Supposedly you can run the Zaurus at 624MHz, but I haven't tried this. (I don't want to fry my Z)
Sidetracking:
The original Afterboot procedure in gen2's page suggests applying
apmd_flags=""
i.e. without any special flag to instruct how apmd behaves.
Then mathemajikian in another thread suggests using apmd_flags="-t 300" to make the power usage report more accurate.
And then the official man page apm(8) has these two interesting options:
-A Set apmd(8) to automatic performance adjustment mode. In this
mode, when CPU idle time falls below 10%, or if the AC power is
connected and the battery is more than 15% charged, apm raises
hw.setperf as much as possible. Otherwise, when the CPU idle
time is above 30% and the system is running on battery power, apm
lowers hw.setperf as much as possible to reduce power consump-
tion.
-C Set apmd(8) to cool running performance adjustment mode. In this
mode, when CPU idle time falls below 10%, apm raises hw.setperf
as much as necessary. Otherwise, when idle time is above 30% apm
reduces hw.setperf as much as possible to reduce heat, noise, and
power consumption.
Given now the suspend/resume issue is gone, I just wonder which flag(s) would be most useful to Z?
The original Afterboot procedure in gen2's page suggests applying
apmd_flags=""
i.e. without any special flag to instruct how apmd behaves.
Then mathemajikian in another thread suggests using apmd_flags="-t 300" to make the power usage report more accurate.
And then the official man page apm(8) has these two interesting options:
-A Set apmd(8) to automatic performance adjustment mode. In this
mode, when CPU idle time falls below 10%, or if the AC power is
connected and the battery is more than 15% charged, apm raises
hw.setperf as much as possible. Otherwise, when the CPU idle
time is above 30% and the system is running on battery power, apm
lowers hw.setperf as much as possible to reduce power consump-
tion.
-C Set apmd(8) to cool running performance adjustment mode. In this
mode, when CPU idle time falls below 10%, apm raises hw.setperf
as much as necessary. Otherwise, when idle time is above 30% apm
reduces hw.setperf as much as possible to reduce heat, noise, and
power consumption.
Given now the suspend/resume issue is gone, I just wonder which flag(s) would be most useful to Z?
QUOTE(ZDevil @ Jun 5 2007, 07:10 PM)
Sidetracking:
The original Afterboot procedure in gen2's page suggests applying
apmd_flags=""
i.e. without any special flag to instruct how apmd behaves.
Then mathemajikian in another thread suggests using apmd_flags="-t 300" to make the power usage report more accurate.
And then the official man page apm(8) has these two interesting options:
-A Set apmd(8) to automatic performance adjustment mode. In this
mode, when CPU idle time falls below 10%, or if the AC power is
connected and the battery is more than 15% charged, apm raises
hw.setperf as much as possible. Otherwise, when the CPU idle
time is above 30% and the system is running on battery power, apm
lowers hw.setperf as much as possible to reduce power consump-
tion.
-C Set apmd(8) to cool running performance adjustment mode. In this
mode, when CPU idle time falls below 10%, apm raises hw.setperf
as much as necessary. Otherwise, when idle time is above 30% apm
reduces hw.setperf as much as possible to reduce heat, noise, and
power consumption.
Given now the suspend/resume issue is gone, I just wonder which flag(s) would be most useful to Z?
The original Afterboot procedure in gen2's page suggests applying
apmd_flags=""
i.e. without any special flag to instruct how apmd behaves.
Then mathemajikian in another thread suggests using apmd_flags="-t 300" to make the power usage report more accurate.
And then the official man page apm(8) has these two interesting options:
-A Set apmd(8) to automatic performance adjustment mode. In this
mode, when CPU idle time falls below 10%, or if the AC power is
connected and the battery is more than 15% charged, apm raises
hw.setperf as much as possible. Otherwise, when the CPU idle
time is above 30% and the system is running on battery power, apm
lowers hw.setperf as much as possible to reduce power consump-
tion.
-C Set apmd(8) to cool running performance adjustment mode. In this
mode, when CPU idle time falls below 10%, apm raises hw.setperf
as much as necessary. Otherwise, when idle time is above 30% apm
reduces hw.setperf as much as possible to reduce heat, noise, and
power consumption.
Given now the suspend/resume issue is gone, I just wonder which flag(s) would be most useful to Z?
it's a matter of daring to try
QUOTE(ZDevil @ Jun 5 2007, 07:10 PM)
Sidetracking:
The original Afterboot procedure in gen2's page suggests applying
apmd_flags=""
i.e. without any special flag to instruct how apmd behaves.
Then mathemajikian in another thread suggests using apmd_flags="-t 300" to make the power usage report more accurate.
And then the official man page apm(8) has these two interesting options:
-A Set apmd(8) to automatic performance adjustment mode. In this
mode, when CPU idle time falls below 10%, or if the AC power is
connected and the battery is more than 15% charged, apm raises
hw.setperf as much as possible. Otherwise, when the CPU idle
time is above 30% and the system is running on battery power, apm
lowers hw.setperf as much as possible to reduce power consump-
tion.
-C Set apmd(8) to cool running performance adjustment mode. In this
mode, when CPU idle time falls below 10%, apm raises hw.setperf
as much as necessary. Otherwise, when idle time is above 30% apm
reduces hw.setperf as much as possible to reduce heat, noise, and
power consumption.
Given now the suspend/resume issue is gone, I just wonder which flag(s) would be most useful to Z?
The original Afterboot procedure in gen2's page suggests applying
apmd_flags=""
i.e. without any special flag to instruct how apmd behaves.
Then mathemajikian in another thread suggests using apmd_flags="-t 300" to make the power usage report more accurate.
And then the official man page apm(8) has these two interesting options:
-A Set apmd(8) to automatic performance adjustment mode. In this
mode, when CPU idle time falls below 10%, or if the AC power is
connected and the battery is more than 15% charged, apm raises
hw.setperf as much as possible. Otherwise, when the CPU idle
time is above 30% and the system is running on battery power, apm
lowers hw.setperf as much as possible to reduce power consump-
tion.
-C Set apmd(8) to cool running performance adjustment mode. In this
mode, when CPU idle time falls below 10%, apm raises hw.setperf
as much as necessary. Otherwise, when idle time is above 30% apm
reduces hw.setperf as much as possible to reduce heat, noise, and
power consumption.
Given now the suspend/resume issue is gone, I just wonder which flag(s) would be most useful to Z?
i'm testing -A
now apm gives me :
Performance adjustment mode: auto (520 MHz)
let's wait & see... battery state is high, 56% remaining, A/C not connected
EDITED: after some minutes idle, apm now gives me :
Battery state: high, 87% remaining !!!!
a/c is still not connected
apparently since i'm running with the -A option in apmd, the Z orange charging light seems to stay always lit... or is it since i plugged my CF WIFI card.....
by the way i could not find a cardctl command to type before ejecting the CF card. is it unuseful under openbsd ??
by the way i could not find a cardctl command to type before ejecting the CF card. is it unuseful under openbsd ??
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.