OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: ZDevil on April 18, 2007, 06:31:27 am
-
Hi pdaX folks,
Chero and I have taken up the job to make new documentation for the pdaXrom releases.
Chero has been working on a template tree of notes, and I am focusing more on taking notes on the new releases.
InSearchOf (as well as the other devs who help building) has been doing great job and he promises to release a public build EVERY OTHER WEEK.
This can be a fantastic idea, IF ...
1) bugs and known issues are tracked systematically
2) fixes are found AND incorporated into the next new build(s)
Although there seem to be quite a few new brave testers being put off by the persistent problems, this shouldn't stop us to make things even better!
So, now, in order to help the development of pdaX, the dev team, and ultimately you the users, it would be great if ...
1) I (and Chero) can keep track of reports of bugs/issues and fixes;
2) Users/Testers can contribute to the refinement of the builds by:
-- submitting reports to the pdaXrom bugtracker (http://www.pdaxrom.org/?q=casetracker) (the link in the pinned post is no longer valid),
-- thru PM or emails to me (dvm DOT zaurus AT gmail DOT com),
-- or right in this thread and/or the threads for the new releases.
Then I can keep track of things in these three sources.
I am preparing a new section Chero's tree: Known issues & solutions in the latest version. There I will put as much useful information as i can find. So if you have got something to say and to fix, please do drop me a line!
As for the new builds, many of us still spot old problems as in the older releases. So if you manage to recall or recover the old fixes (as in Beta3, Beta4, r121 or even r1xx), please go ahead and tell me!
Admittedly I am no linux guru or hacker, but I enjoy sharing and dare to work against my holy RL by wasting time typing out simple short notes to help myself and others. The Documentation will surely become more complete and useful with your contributions.
Come, join us, brave pdaXromers! The making a perfect pdaXrom release is an everlasting battle against the dark side of M$ Lose Mobile. Let's roll out and conquer the small world of dinozaurus!
[To InSearchOf: no, it wasn't meant to be angry, but aggressive! ]
-
Admittedly I am no linux guru or hacker
I see that as a positive benefit, because gurus, however well-meaning, can always find it hard not to take for granted that others will know about things which they see as elementary. The documentation for a project is just as important as the project itself, and is where open source often fails miserably, so you are doing vital work - well done.
-
I will second ever thing he says... but why the angry face?
Keep up the good work (and Chero) with the Docs?
Late
-
Great improvements on this release, thanks
----------- Network settings: -----------------------
using LAN & WIFI GUI
create new profile, name it eth0, fill in required informations, save, press OK
It saves my settings but even pressing OK it still stays on the profile named none
and doesn't reinitialize the Wifi setup like in beta3 where I could see
the light of my card shutting off, the screen stuttering and the led blinking again.
I get "ERROR: dns can't solve www.google.com" in Dillo
It works though on reboot the first time but not after ejecting the CF wifi card and
reinserting it via the matchbox-card-applet
Solution:
pccardctl eject
killall dhcpcd
pccardctl insert
or rm /var/run/dhcpcd-eth0.pid
I guess that was what tombraider was experiencing
I am using r198 on an akita and a symbol spectrum CF Wifi
------------------------------vCore----------------------
I confirm Civil's observation about Wrong default vCore (1.5V, instead of 1.4V. After every reboot you must switch to 104/208/312/520/624MHz, and then back to 416 - then vCore becomes 1.4V) (Note: I was using /sys/devices/system/cpu/cpu0/cpufreq/cpu-voltage )
-
---------------------rxvt-----------------
after maximization, there is still an empty space between rxvt window and fbpanel
------------------------matchbox-card-applet-------------
it doesn't seem reliable. I prefer to use ROX mount/umount feature
----------------------------package manager-------------------
you need to update first in order to see a list of available destinations for installation.
You shouldn't have to especially if you want to install from a local storage.
-
Just adding bugs from other threads:
--------------keyboard messed up after leaving X -------------------
By using following commands , we can fix this bug:
# cd /etc/sysconfig/keyboard
# ln -s Borzoi/keymap.map kernel.map
If your Zaurus is not C3100, replace "Borzoi" with codename of your Z.
the root cause of this bug is:
in /usr/X11R6/bin/startx :
test -f /etc/sysconfig/keyboard/kernel.map -a f /usr/bin/loadkeys && sudo /usr/bin/loadkeys /etc/sysconfig/keyboard/kernel.map
but in r198, /etc/sysconfig/keyboard/kernel.map doesn't exist by default.
-
------------- Sound --------------
By default xmms is set to use esound driver, you have to switch to OSS or Alsa to get sound working in Options/Preferences/Audio I/O Plugins.
-
----------------Start menu key--------------
in /etc/xdg/openbox/rc.xml line169, the Menu key is set to the action mb-start-button but we are using fb-panel and not matchbox-panel
-
----------------Start menu key--------------
in /etc/xdg/openbox/rc.xml line169, the Menu key is set to the action mb-start-button but we are using fb-panel and not matchbox-panel
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=159199\")
And what value do we replace it with? Neither 'fb-panel' nor 'fb-start-button' work, and searching [a href=\"http://fbpanel.sourceforge.net/docs.html]fbpanel docs[/url] doesn't give any hints.
-
---------------------rxvt-----------------
after maximization, there is still an empty space between rxvt window and fbpanel
I think (I'm guessing) that it sizes the window so that it fits an exact number of rows/columns in your chosen font/size.
-
zgcc autoconf/automake/m4 bug:
Problem:
autoconf says:
m4 1.4 or later must be installed (but in zgcc - m4 is 1.4)
Solution:
Recompile autoconf, automake and m4
-
----------------Start menu key--------------
in /etc/xdg/openbox/rc.xml line169, the Menu key is set to the action mb-start-button but we are using fb-panel and not matchbox-panel
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=159199\")
And what value do we replace it with? Neither 'fb-panel' nor 'fb-start-button' work, and searching [a href=\"http://fbpanel.sourceforge.net/docs.html]fbpanel docs[/url] doesn't give any hints.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159209\"][{POST_SNAPBACK}][/a][/div]
I don't know either, sorry.
-
------------------------Fbpanel-------------------
- the start menu doesn't list the same items as matchbox-desktop does.
Solution: recompile fbpanel-4.8
since 4.7 Application menu are builded from *.desktop files but we use 4.3
source here http://downloads.sourceforge.net/fbpanel/f...58&big_mirror=0 (http://downloads.sourceforge.net/fbpanel/fbpanel-4.8.tgz?modtime=1176683958&big_mirror=0)
- some items are not visible cause outside of the screen at the bottom
-
---------------------rxvt-----------------
after maximization, there is still an empty space between rxvt window and fbpanel
I think (I'm guessing) that it sizes the window so that it fits an exact number of rows/columns in your chosen font/size.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159210\"][{POST_SNAPBACK}][/a][/div]
I think you are right, when resizing I can see the geometry displayed 77 x 27 which corresponds to rows and columns apparently. Consequence same problem goes for Aterm.
-
---------------------brightness------------------
above 30% screen is bright
below 30% screen is dimmed
below 25% battery icon is red
below 13% Z shuts off
Problem: if apm indicates around 30% screen is blinking for like 15mins cause battery status
goes up and down around 30%.
I would be better to setup a range of values like dimmed between 10% and 20% instead of just one value
Is it possible to change these values without recompiling ?
I think matchbox-battery-applet was able to do that in beta3
-
Thank you, scheck.r!
Have started recording this in the notes.
Anyone anything else?
Please write more!
The more issues we find in this one, the better build we will have in the NEXT one.
-
When I install & try to run gnupg, I get a 'libiconv.so.2 missing' error. libiconv isn't in the feeds. Can someone please post a package/location? thks
-
libiconv is used in pre-Beta4 releases. I also made a newer build in the "New Package Announcement" thread, together with gettext.
-
libiconv is used in pre-Beta4 releases. I also made a newer build in the "New Package Announcement" thread, together with gettext.[div align=\"right\"][a href=\"index.php?act=findpost&pid=159233\"][{POST_SNAPBACK}][/a][/div]
Got it. Thanks ZDevil
-
libiconv is used in pre-Beta4 releases. I also made a newer build in the "New Package Announcement" thread, together with gettext.[div align=\"right\"][a href=\"index.php?act=findpost&pid=159233\"][{POST_SNAPBACK}][/a][/div]
Got it. Thanks ZDevil[div align=\"right\"][a href=\"index.php?act=findpost&pid=159288\"][{POST_SNAPBACK}][/a][/div]
I installed the bzip2 dependancy, but what about libusb-0.1.so.4? What package has that library?
-
above 30% screen is bright
below 30% screen is dimmed
below 25% battery icon is red
below 13% Z shuts off
Same for me:
Above 30% of battery - everything OK
At 30% - backlight randomly is turns on/off
Below ~15% - Z suspends every few seconds (after around 20-25 suspends - apm just says: apm - device is busy).
-
use smplayer & mplayer to play music
pulg in my head phone,
but the speaker of my Zaurus is still playing music ...
-
use smplayer & mplayer to play music
pulg in my head phone,
but the speaker of my Zaurus is still playing music ...
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=159297\")
I used alsamixer and tried the settings there (you have to use either arrow keys or "." or "m" to flip the switches).
At first there is no sound at all, both in xmms and in games.
Then after turning the last 3rd~5th switches to "00" (= on) (MM = mute).
Both the speaker and the headphone will have sound.
When turning off "Speaker", only headphone has sound, and the speaker is muted.
The man page is not of much help either: [a href=\"http://www.die.net/doc/linux/man/man1/alsamixer.1.html]http://www.die.net/doc/linux/man/man1/alsamixer.1.html[/url]
xmms play gives an error "failed to open audio output: eSound Output Plugin 1.2.10".
-
Two trivial ways to improve the precision of stylus pointer on Cxx0:
-- When (re)calibrating, do it with the stylus upright to the five crosshairs.
(remove the old calibration file with "rm /etc/pointercal" before recalibrating)
-- Tap the GUI buttons faster.
-
Then after turning the last 3rd~5th switches to "00" (= on) (MM = mute).
Works great, although I found a buzzing feedback was produced by un-muting the 3rd from-last (Output Mixer Mic Sidetone Switch), so be warned .
xmms play gives an error "failed to open audio output: eSound Output Plugin 1.2.10".[div align=\"right\"][a href=\"index.php?act=findpost&pid=159301\"][{POST_SNAPBACK}][/a][/div]
I installed the esound package, which is what I remember doing under r121. But even after that I get this as well when running from the command line:
esd: Esound sound daemon already running or stale UNIX socket
/tmp/.esd/socket
This socket already exists indicating esd is already running.but the socket doesn't exist. Strange.
-
xmms play gives an error "failed to open audio output: eSound Output Plugin 1.2.10".[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=159301\")
Of course, looking further back in [a href=\"https://www.oesf.org/forums/index.php?act=ST&f=73&t=23788&hl=xmms&view=findpost&p=159198]this same subject[/url] gives the answer (change xmms's settings to not use esound).
-
xmms play gives an error "failed to open audio output: eSound Output Plugin 1.2.10".[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=159301\")
Of course, looking further back in [a href=\"https://www.oesf.org/forums/index.php?act=ST&f=73&t=23788&hl=xmms&view=findpost&p=159198]this same subject[/url] gives the answer (change xmms's settings to not use esound).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159316\"][{POST_SNAPBACK}][/a][/div]
Yes, i read that post before posting. But the output audio driver is already set to OSS. Changed it to alsa, but still got the same error.
esound is also already installed.
-
One more thing: SCIM cannot run in r197/r198. It seems to have something to do with the gtk library. Have read an old post that installing a Beta3 gtk lib will make it work. But this will come with a bigger cost that many newly updated gtk stuff in the new feeds may not run.
I know this is not a bug, and things like SCIM probably have to be recompiled. I did try to compile SCIM before. It ended up with tons of painful errors ...
-
xmms play gives an error "failed to open audio output: eSound Output Plugin 1.2.10".[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=159301\")
Of course, looking further back in [a href=\"https://www.oesf.org/forums/index.php?act=ST&f=73&t=23788&hl=xmms&view=findpost&p=159198]this same subject[/url] gives the answer (change xmms's settings to not use esound). [div align=\"right\"][a href=\"index.php?act=findpost&pid=159316\"][{POST_SNAPBACK}][/a][/div]
Yes, i read that post before posting. But the output audio driver is already set to OSS. Changed it to alsa, but still got the same error.
esound is also already installed.[div align=\"right\"][a href=\"index.php?act=findpost&pid=159318\"][{POST_SNAPBACK}][/a][/div]
mmm.. I had actually rebooted after changing my setting (which was esound, I changed it to alsa) because I wanted to test out something else. Maybe give that a try.
-
mmm.. I had actually rebooted after changing my setting (which was esound, I changed it to alsa) because I wanted to test out something else. Maybe give that a try.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159323\"][{POST_SNAPBACK}][/a][/div]
Rebooted. Still no luck. Same error in xmms. smplayer no sound.
-
--------------Sound----------------
If OSS driver is selected in xmms, the volume CANNOT be controlled from xmms and the volume applet in fbpanel is too sensitive, not linear enough, sound becomes audible at 2/3 of the max.
If ALSA driver is selected in xmms, volume CAN be controlled from xmms and it's easier to adjust since it increments by 2%. However, volume applet and volume cursor in xmms are no more independent like in beta3.
If you move the volume applet with the stylus you can see the volume cursor in xmms changing also. Volume is also too sensitive with ALSA driver. If you do the reverse i.e if you change volume from xmms, volume settings are not updated in the fbpanel volume applet and neither in zmixer, zmixer and the volume applet keep there previous settings(even if volume is lower).
But at least on akita, putting speaker volume to zero in Zmixer works.
And sound is stuttering like crazy when moving volume control panel with the stylus.
-
Using mplayer from the cli(from r198 feed), I don't have any problems(after adjusting zmixer of course) and I am using OSS default driver. I CAN adjust everything separately(speakers and headphones), tried with mp3 and mpg.
-
One more thing: SCIM cannot run in r197/r198. It seems to have something to do with the gtk library. Have read an old post that installing a Beta3 gtk lib will make it work. But this will come with a bigger cost that many newly updated gtk stuff in the new feeds may not run.
I know this is not a bug, and things like SCIM probably have to be recompiled. I did try to compile SCIM before. It ended up with tons of painful errors ...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159319\"][{POST_SNAPBACK}][/a][/div]
SCIM (from beta3 feed) works fine on my C3100 with r198
(scim , scim-pinyin)
I modified ~/.xinitrc, added :
scim -dbefore openbox/matchbox started
and modified /etc/profile , added:
export GTK_IM_MODULE=scim
export QT_IM_MODULE=scim
export XMODIFIERS="@im=SCIM"
====
Ctrl+Space to call up the SCIM in applications
and I found it was using XIM protocal (not GTK IM MODULE)
so I think
export XMODIFIERS="@im=SCIM"is the most important configuration.
-
Thanks, wellswang.
I have already done exactly what you suggested, also with "gtk-query-immodules-2.0 > /etc/gtk-2.0/gtk.immodules" after installation. I was also using this in all my old setups.
But scim stops working in 860@r197 . Ctrl-Space doesn't call the program in leafpad or GTKTerm2. Neither can i use the scim config tool (scim-setup) to set keys, etc (showing segfault in terminal). Reinstalling them doesn't help.
Can someone using r197 verify this?
-
Thanks, wellswang.
I have already done exactly what you suggested, also with "gtk-query-immodules-2.0 > /etc/gtk-2.0/gtk.immodules" after installation. I was also using this in all my old setups.
But scim stops working in 860@r197 . Ctrl-Space doesn't call the program in leafpad or GTKTerm2. Neither can i use the scim config tool (scim-setup) to set keys, etc (showing segfault in terminal). Reinstalling them doesn't help.
Can someone using r197 verify this?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159357\"][{POST_SNAPBACK}][/a][/div]
I can't run scim-setup on r198. Do you have this problem? Are you using the scim from old beta feed or built by yourself?
-
I use the packages from the r121 feeds, which are supposed to be just the same as the r197/198 feeds.
And yes, scim-setup segfaults and fails to launch. And I don't seem to find its icon in the program menu (i am using icewm).
If my C3200 does not arrive today, then I will have to flash my C860 back to Beta3 to get the working environment back.
-
And yes, scim-setup segfaults and fails to launch. And I don't seem to find its icon in the program menu (i am using icewm).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159367\"][{POST_SNAPBACK}][/a][/div]
So, how difficult it is to re-complie scim? I tried it on my pdaXrom build environment but ended up with the following error:
checking for /usr/share/sgml/docbook/xsl-stylesheets/html/tldp-html.xsl... configure: error: cannot check for files existence when cross compiling
Does this mean scim is not friendly to cross-compiling? I'm using the 1.4.5 source with the following (simple) switches:
CC=armv5tel-cacko-linux-gcc ./configure --host=armv5tel-cacko-linux --build=i686-linux
-
Issue on Akita:
There seems no bvdd support:
# modprobe bvdd
FATAL: Module bvdd not found
-
And yes, scim-setup segfaults and fails to launch. And I don't seem to find its icon in the program menu (i am using icewm).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159367\"][{POST_SNAPBACK}][/a][/div]
So, how difficult it is to re-complie scim? I tried it on my pdaXrom build environment but ended up with the following error:
checking for /usr/share/sgml/docbook/xsl-stylesheets/html/tldp-html.xsl... configure: error: cannot check for files existence when cross compiling
Does this mean scim is not friendly to cross-compiling? I'm using the 1.4.5 source with the following (simple) switches:
CC=armv5tel-cacko-linux-gcc ./configure --host=armv5tel-cacko-linux --build=i686-linux
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159368\"][{POST_SNAPBACK}][/a][/div]
The Docbook thingy is tricky. One thing is the documentation is (again, alas!) confusing. I got to download the source and extract it in the correct paths in order to compile quite a few apps (onboard in Z). I can go back to my mac at home to fish the pointer tonite.
But i remember i got past that and got lots of other make errors.
-
Good news!
Screen rotate DOES work for C860@r197!
This morning i was reading an ebook with JustReader on the train. Then I use the rotate function of JustReader, then flipped the machine into portrait mode, thinking that the screen rotate in the build or icewm was broken.
But ...
No, it worked!
The only small step i had missed before is to pull the screen all the way down to the keyboard.
Perhaps i am mistaken, but it seems for C1000/3000/3100/3200 you just have to turn the screen to rotate the display.
Also in the older Cxx0 devices there are two small "buttons" along the hinge and the swivel and there is only on Cxk switch which does the same thing.
I remember it seems to be the tiny button above and between the number keys "1" and "2" that does the job...?
And it seems my build of icewm 1.2.30 can handle rotate well, in contrast to the current 1.2.20 in the feeds. Maybe someone can verify that.
-
This fix was in the other thread posted by ZDevil. It fixes the mounting of cf and sd cards:
II. Fix the card mounting issue (thanks to louigi600 for providing this)
You will notice that upon reboot after flashing, both SD and CF are not mounted.
To fix this, edit /etc/fstab. Use your favorite editor to do so.
Open the file, in the lines for /dev/hda1 (for CF) and /dev/mmcblk0p1 (for SD), change
CODE
noauto,owner
to
CODE
owner
Save the file, exit the editor.
Reboot.
Then the cards will be mounted automatically.
Hi pdaX folks,
Chero and I have taken up the job to make new documentation for the pdaXrom releases.
Chero has been working on a template tree of notes, and I am focusing more on taking notes on the new releases.
InSearchOf (as well as the other devs who help building) has been doing great job and he promises to release a public build EVERY OTHER WEEK.
This can be a fantastic idea, IF ...
1) bugs and known issues are tracked systematically
2) fixes are found AND incorporated into the next new build(s)
Although there seem to be quite a few new brave testers being put off by the persistent problems, this shouldn't stop us to make things even better!
So, now, in order to help the development of pdaX, the dev team, and ultimately you the users, it would be great if ...
1) I (and Chero) can keep track of reports of bugs/issues and fixes;
2) Users/Testers can contribute to the refinement of the builds by:
-- submitting reports to the pdaXrom bugtracker (http://www.pdaxrom.org/?q=casetracker) (the link in the pinned post is no longer valid),
-- thru PM or emails to me (dvm DOT zaurus AT gmail DOT com),
-- or right in this thread and/or the threads for the new releases.
Then I can keep track of things in these three sources.
I am preparing a new section Chero's tree: Known issues & solutions in the latest version. There I will put as much useful information as i can find. So if you have got something to say and to fix, please do drop me a line!
As for the new builds, many of us still spot old problems as in the older releases. So if you manage to recall or recover the old fixes (as in Beta3, Beta4, r121 or even r1xx), please go ahead and tell me!
Admittedly I am no linux guru or hacker, but I enjoy sharing and dare to work against my holy RL by wasting time typing out simple short notes to help myself and others. The Documentation will surely become more complete and useful with your contributions.
Come, join us, brave pdaXromers! The making a perfect pdaXrom release is an everlasting battle against the dark side of M$ Lose Mobile. Let's roll out and conquer the small world of dinozaurus!
[To InSearchOf: no, it wasn't meant to be angry, but aggressive! ]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159155\"][{POST_SNAPBACK}][/a][/div]
-
No, it's not my fix. louigi600 found it.
-
I know, i thought I said it was "posted" by you in that thread....on the other hand, maybe I just wasn't very clear in how I phrased it.
I wanted to give you credit for posting it.
Sorry for the misunderstanding.
No, it's not my fix. louigi600 found it.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159445\"][{POST_SNAPBACK}][/a][/div]
-
@Sheck.r
For your symbol wifi card, did you have to drop the firmware file someplace?
Thanks
--Fish
-
@Sheck.r
For your symbol wifi card, did you have to drop the firmware file someplace?
Thanks
--Fish
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=159588\")
It's in this thread:
[a href=\"https://www.oesf.org/forums/index.php?showtopic=23753]https://www.oesf.org/forums/index.php?showtopic=23753[/url]
-
Issue on Akita:
There seems no bvdd support:
# modprobe bvdd
FATAL: Module bvdd not found
[div align=\"right\"][a href=\"index.php?act=findpost&pid=159369\"][{POST_SNAPBACK}][/a][/div]
If not mistaken bvdd is only for kernel 2.4 , kernel 2.6 uses pxafb...
-
any news on the clock reset to 1970-01-01 after reboot?
-
any news on the clock reset to 1970-01-01 after reboot?
If you use reboot - it syncs sys clock to hardware. And it'll remain normal till you pull out your battery (then it'll be 1970-01-01-00:00 )
-
---------------------brightness------------------
above 30% screen is bright
below 30% screen is dimmed
below 25% battery icon is red
below 13% Z shuts off
Problem: if apm indicates around 30% screen is blinking for like 15mins cause battery status
goes up and down around 30%.
I would be better to setup a range of values like dimmed between 10% and 20% instead of just one value
Is it possible to change these values without recompiling ?
I think matchbox-battery-applet was able to do that in beta3
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=159224\")
May be this is related to this thread [a href=\"https://www.oesf.org/forums/index.php?showtopic=24103&pid=162427&st=0&#entry162427]https://www.oesf.org/forums/index.php?showt...=0&#entry162427[/url]
However, if you want the speed to be adjusted automatically then you'll have to utilize the following apm option:
-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.