Brief intro to Distros/ROMs here.
something
something
something
something
something
something
something
something
something
something
something
something
something
something
something
something
-Predecessor to Angstrom
-Stable/mature
-Supports all (?) Z models
-GPE and OPIE variants
something
something
something
something
someting
something
something
something
something
-Builds for devices other than the Zaurus (Pandora, iPAQs, Simpads, etc.)
-Quite up-to-date
-Optimized on a per-device basis
-Large number of pre-built packages
-2.6.x kernel
Installed via the "normal" method (OK, option 4, yes, SD, etc.)
something
something
Please disregard any HTML tags present (< HTML_TAG >, is what they look similar to) in this tutorial. They are NOT meant to be there and apparently can't be removed. They are NOT part of the commands and should NOT be typed!
Yes, you DO need a Linux box (not necessarily x86, but I assume the fastest box you have is x86, and that's what you want to use, or at least one with decent specs). I know Ubuntu works for this. Debian Sid had some issues, but sort of worked.
Note that I assume you're following these directions pretty much to the letter (ie, step 2 assumes you are in /OE)
0. Install the necessary stuff:
apt-get install python m4 patch build-essential make python-psyco ccache perl diffstat git bison
You may want to manually make sure you get the right stuff installed:
http://wiki.openembedded.net/index.php/Required_Software
1a. Make the directory /OE (you can use a different directory, but it's something of a pain) and allow normal users to write to it (you could chown it, for example)
sudo mkdir /OE<br /> sudo chown yourusername:users /OE
1b. Download Bitbake:
cd /OE<br /> wget http://download.berlios.de/bitbake/bitbake-1.8.10.tar.gz
2. Install Bitbake:
tar -xf bitbake-1.8.10.tar.gz
3. Get the OE data and update it (you may want to make a script for the last two lines, calling it "update.sh" or something):
git clone git://git.openembedded.net/openembedded.git org.openembedded.stable<br /> cd org.openembedded.stable<br /> git checkout -b org.openembedded.stable origin/org.openembedded.stable<br /> cd /OE/org.openembedded.stable<br /> git pull
4. Set up the environment file:
cd /OE<br /> wget http://www.angstrom-distribution.org/files/source-me.txt
5. Set up the build config (if /OE/build/conf/ doesn't exist, create it):
mkdir -p /OE/build/conf/<br /> yourfavoriteeditor /OE/build/conf/local.conf
Contents:
# Where to store sources<br />
DL_DIR = "/OE/downloads"</p>
<p># Which files do we want to parse<br />
BBFILES := "/OE/org.openembedded.stable/packages/*/*.bb"<br />
BBMASK = ""</p>
<p># ccache always overfill $HOME....<br />
CCACHE=""</p>
<p># What kind of images do we want?<br />
IMAGE_FSTYPES = "jffs2 tar.gz "</p>
<p># Set TMPDIR instead of defaulting it to $pwd/tmp<br />
TMPDIR = "/OE/${DISTRO}-stable/"</p>
<p># For multicore CPU boxes:<br />
#PARALLEL_MAKE="-j4"<br />
#BB_NUMBER_THREADS = "2"<br />
#for single-core boxes:<br />
PARALLEL_MAKE="-j2"<br />
BB_NUMBER_THREADS = "1"</p>
<p># Set the Distro<br />
DISTRO = "angstrom-2007.1"</p>
<p># 'uclibc' or 'glibc' or 'eglibc'<br />
ANGSTROM_MODE = "glibc"</p>
<p>MACHINE = "akita"
6a. Start building your kernel module:
source /OE/source-me.txt<br /> cd /OE/org.openembedded.stable<br /> ./update.sh<br /> bitbake whatever
6b. Wait a good chunk of time (several hours; don't try to do anything useful on this box while it's working)
---------------------------OLD-------------------------------------
I don't know if this should be kept or not....
This is almost a direct copy & paste from the Angstrom website, yet the readability and clarity updates are in progress.
Step 1
Obtain BitBake and OpenEmbedded These (compressed for now) files can go anywhere for now.
Step 2
Install BitBake and OE:
mkdir /OE && cd /OE<br />
tar zxf /path/to/bitbake-1.8.8.tar.gz<br />
bunzip2 /path/to/OE.mtn.bz2<br />
mtn --db=/path/to/OE.mtn pull monotone.openembedded.org org.openembedded.{angstrom-2007.12-stable,dev}<br />
mtn --db=/path/to/OE.mtn checkout --branch=org.openembedded.angstrom-2007.12-stable<br />
cd /path/to/org.openembedded.angstrom-2007.12-stable ; mtn pull monotone.openembedded.org org.openembedded.angstrom-2007.12-stable ; mtn update
Make sure /OE and its subdirectories are read/writable by standard users, as BitBake won't work as root.
You should probably also install psyco (called "python-psyco" in Debian, IIRC, Homepage)
Make a file in /OE to setup the environment variables (ex, /OE/sources-me.txt):
BBPATH=/OE/:/OE/build/:/OE/org.openembedded.angstrom-2007.12-stable/<br />
PKGDIR=/OE/build/<br />
DL_DIR=/OE/downloads<br />
echo Setting up dev env for Ångström</p>
<p>if [ -z ${ORG_PATH} ]<br />
then<br />
ORG_PATH=${PATH}<br />
export ORG_PATH<br />
fi</p>
<p> if [ -z ${ORG_LD_LIBRARY_PATH} ]<br />
then<br />
ORG_LD_LIBRARY_PATH=${LD_LIBRARY_PATH}<br />
export ORG_LD_LIBRARY_PATH<br />
fi<br />
PATH=/OE/bitbake-1.8.8/bin:${ORG_PATH}<br />
cd $PKGDIR<br />
LD_LIBRARY_PATH=<br />
export PATH LD_LIBRARY_PATH BBPATH<br />
export LANG=C<br />
echo "Altered environment for OE Development"
Step 3
Add the following to your local.conf. It doesn't currently exist. Make it in /OE/build/conf.
# Where to store sources<br />
DL_DIR = "/OE/downloads"</p>
<p># Which files do we want to parse:<br />
BBFILES := "/OE/org.openembedded.angstrom-2007.12-stable/packages/*/*.bb"<br />
BBMASK = ""</p>
<p># ccache always overfill $HOME....<br />
CCACHE=""</p>
<p># What kind of images do we want?<br />
IMAGE_FSTYPES = "jffs2 tar.gz "</p>
<p># Set TMPDIR instead of defaulting it to $pwd/tmp<br />
TMPDIR = "/OE/build/tmp/${DISTRO}"</p>
<p># Uncomment the following two lines if you have a multi-core CPU<br />
#PARALLEL_MAKE="-j4"<br />
#BB_NUMBER_THREADS = "2"</p>
<p># Set the Distro<br />
DISTRO = "angstrom-2007.1"</p>
<p># 'uclibc' or 'glibc' or 'eglibc'<br />
#ANGSTROM_MODE = "glibc"</p>
<p>MACHINE = "YOURMACHINE"
Substitute "YOURMACHINE" with the machine you want to build for, e.g.:
* c7x0 - For pxa25x zaurus clamshells (SL-C700, SL-C750, SL-C760, SL-C860, SL-7500)
* spitz - For pxa27x zaurus clamshells with a microdrive (SL-C3000, SL-C3100, SL-C3200)
* akita - For pxa27x zaurus clamshells without a microdrive (SL-C1000)
* tosa - For the SL-C6000
Note that the only difference between Spitz and Akita is that Akita will install to NAND and Spitz will install to the microdrive. You can use an Akita image on C3100 and C3200 machines. Spitz images cannot access the NAND AFAICT.
Step 4
Start building:
source source-me.txt ; cd /path/to/org.openembedded.angstrom-2007.12-stable ; mtn pull ; mtn update ; bitbake IMAGE_OR_PACKAGE_NAME
Where IMAGE_OR_PACKAGE_NAME is the name of the install image or package you want to build. Building the first package/image will take a good while, as EVERYTHING needs to be built (cross tools, all of the packages in the image, deps, etc.)
Step 5
Building for a different machine or C library is just a matter of changing the MACHINE= or ANGSTROM_MODE statement in local.conf to a new value. There is ABSOLUTELY no need for using different directories for that; Angstrom takes care of all the details, it was specifically designed for this.
Other notes
*These files take up a lot of space. If you intend to build more than a couple of packages/images, have some 10-20GB of space available.
something
something
something
something
something
Q: (Jon_J) Can "pdaXii13-custom.tgz (patching only)" be used on a pdaxii13-akita5.3 installation to update it to pdaxii13-akita5.3.2 ?
A: (from a post by Meanie)
upgrading works for all versions (of course you won't get the new apps installed which you need to install yourself)
hdimage-custom.tgz != pdaXii13-custom.tgz
Q: What is the pdaXii13 boot sequence on a C3000?
A: (from a post by Meanie)
pdaXii13 boot sequence...
The boot and startup process on pdaXii13 Spitz is a bit different from the standard pdaXrom because of its small flash:
1. load kernel from NAND
2. read and mount NAND partitions
3. load /sbin/init interceptor from rootfs on NAND
4. initialize and mount MicroDrive
5. pivot rootfs to MicroDrive
6. execute /sbin/init from MicroDrive
7. initialise core hardware
9. mount internal filesystems
8. load kernel modules
10. load inittab and rc subsystem
11. run rc.local
12. run scripts in /etc/rc.d/rc3.d or /etc/rc.d/rc5.d
13. /etc/rc.d/init.d/local is run from either rc3.d or rc5.d
14. start X if runlevel 5
15. if using openbox/matchbox (default) load mb-applet-tasks
16. task applet will run /home/root/.matchbox/autoexec
17. once X is exited, console login is loaded
18. /etc/issue is displayed
19. when reboot is issued, scripts in /etc/rc.d/rc6.d are run
20. /etc/rc.d/init.d/halt is last script to be run before reboot
something
How to set up TCP/IP over USB with Win XP
How to set up TCP/IP over USB with Linux
something
-Currently being re-built from scratch (2008/10/25)
something
something
something
something
pdaXii13 overview/info site
- http://www.users.on.net/~hluc/myZaurus/pdaxii13.html
- http://zaurus.daemons.gr/menaie/mirror/pdaxii13.html
pdaXii13 main (C3000) downloads
- http://www.tyrannozaurus.com/feed/pdaXii13/files/index.html
pdaXii13 alpha/beta downloads and release notes
- http://www.tyrannozaurus.com/feed/pdaXii13/tmp/index.html
pdaXii13 for C1000/C3100/C3200
- http://www.tyrannozaurus.com/feed/pdaXii13/akita/index.html
pdaXii13 5.3.x upgrade/info page
- http://www.tyrannozaurus.com/?q=node/210 (need to fix link)
pdaXii13 build/development files
- http://www.tyrannozaurus.com/feed/pdaXii13/build/index.html
pdaXii13 updates/development info
- http://www.tyrannozaurus.com/?q=node/74 (need to fix link)
zgcc image for pdaXrom/pdaXii13 info
- http://www.tyrannozaurus.com/?q=node/75 (need to fix link)
pdaXrom and pdaXii13 development info
- http://www.tyrannozaurus.com/?q=node/214 (need to fix link)
new packages for pdaXrom/pdaXii13
- http://www.tyrannozaurus.com/?q=node/141 (need to fix link)
installation/upgrade instructions
Antikx's pdaXii13 5.3.3 Akita Full install on SD Instructions
-Flash your Akita to 5.3.3 ( http://www.tyrannozaurus.com/feed/pdaXii13/akita/ )
-backup your card and then fdisk it so that you have two primary partitions (vfat first then ext2)
-download the latest hdimage-full file ( http://www.tyrannozaurus.com/feed/pdaXii13/tmp/hdimage-full.tgz )
-copy it over to your ext2 partition
-extract the tar/gzip file, and then move all the stuff in the hdd1 directory into the root of your ext2 partition
-at the root of your ext2 partition tar up the "home" and "etc" directories
-copy the tar files to the root of your flash
-copy the files /etc/rc.d/rc.rofilesys, /etc/rc.d/rc.sysinit, /etc/rc.d/init.d/halt and /etc/issue from etc and put them somewhere safe
-extract the tar files
-copy those four files you saved back to where you found them
-reboot
Meanie's pdaXii13 (5.3.x) Upgrade Instructions
You can use the upgrade process to upgrade from pdaXrom beta1/beta3 to pdaXii13 or upgrade an existing pdaXii13 to the latest release/build.
pdaXii13 starting from build 5.3.1 is available in 3 different editions:
Alice (pdaXii13 Spitz) for C3000 - this exists as base and full and can be installed via the flash installer. Alice for C3000 cannot be upgraded from pdaXrom since there is no official pdaXrom beta1/beta3 for C3000. Upgrading an existing Alice install can be done by simply reflashing hdimage-full.tgz or hdimage-base.tgz (full upgrade) or by using pdaXii13-custom.tgz (patching only). When using the patching only method, new or updated packages will need to be manually added and replaced. See the release notes for a list of newly added packages which you need to install manually and updated packages which need to be replaced, ie uninstall existing package and install new package. C3100/C3200 can also use Alice, but it is recommended for C3100/C3200 to use Sally instead. To install a new copy of Alice on C3100/C3200, you first need to either flash pdaXrom beta3 or pdaXii13 Akita base before flashing pdaXii13 Spitz. C3100/C3200 with Spitz installed can upgrade to latest version of Alice just like upgrading Alice for C3000.
Sally (pdaXii13 Akita) for C1000/C3100/C3200 - this exists as base only and can be installed via the flash installer. It can be extended to the full edition by additionally flashing the hdimage-full.tgz file for Alice on the C3100/C3200. Upgrading the base edition can be done by simply reflashing the NAND (full upgrade) or by using pdaXii13-custom.tgz (patching only). Upgrading the full edition requires both reflashing with hdimage-full.tgz and using pdaXii13-custom.tgz. pdaXrom beta1/beta3 can be upgraded to pdaXii13 Akita base using pdaXii13-custom.tgz as well
Charlie (pdaXii13 Corgi) for C7x0/C8x0 - this edition does not have a flash installer. It requires pdaXrom beta1 installed first and then can be upgraded using pdaXii13-custom.tgz
using pdaXii13-custom.tgz (make sure you have a backup in case something goes wrong)
1. download and extract http://www.tyrannozaurus.com/feed/pdaXii13/build/pdaXii13-custom.tgz (preferably to CF rather than SD)
2. exit X if you have not already done so
3. shutdown all unneccesary services including SD service (/etc/rc.d/init.d/sd stop)
4. change directory to where the files have been extracted (eg. cd /mnt/cf/custom)
5. run ./install-fix-beta3.sh / upgrade
6. reboot
For full install instructions see the following links:
http://www.users.on.net/~hluc/myZaurus/pdaxii13.html#install
http://www.tyrannozaurus.com/feed/pdaXii13/akita/
Alice vs Sally on C3100/C3200
Alice runs completely off the internal MicroDrive and is intended for C3000 since its NAND is too small. C3100/C3200 can pretend to be a C3000 and install to the MicroDrive as well and not use the NAND. The Alice installer puts a C3000 specific kernel and a small pivot rootfs onto the NAND. The Alice installer cannot do this for C3100/C3200, hence they need to have pdaXrom beta3 or pdaXii13 Akita base installed first which will provide the kernel and initial rootfs. Then using the Alice installer, the rootfs is patched to pivot to the MicroDrive just like for the C3000 and the hdimage is extracted to the MicroDrive.
Sally runs from the NAND and is intended for C1000/C3100/C3200 since they all have a 128MB NAND. But because the C3100/C3200 also have a MicroDrive in addition to the NAND, the hdimage used for Alice can be installed to the MicroDrive on C3100/C3200. The Sally installer has an option to install the hdimage for C3100/C3200. The difference to running Alice on C3100/C3200 is that the NAND is used to hold the rootfs and it is not pivoted to the MicroDrive, rather it extends /usr to the MicroDrive using the bind feature instead.
Danboid's Pdaxii13 (5.2) On C3100, Install Instructions
This is an unofficial method of installing pdaXii13 full on a c3100 or c3200 as first discovered by Archimark.
Note that there is now a pdaXii13 Akita which is a bug fixed and improved pdaXrom b3 for c1000, c3100 and c3200 models which in the future may let you upgrade to pdaXii13 full by storing /usr on the Microdrive but this install method isn't known to be working currently. pdaXii13 Akita is unsupported by Meanie and the pdaXrom team have moved onto a kernel 2.6 based distro.
Neither Meanie, Archimark, myself or anybody else will take any responsibility for any damage or loss of data that may arise as a result of following these instructions. You follow these instructions entirely at your own risk! Make sure to read all the bugs (it is not perfect yet - it has a 10m+ boot time for one) and that you know how to get restore a working OS in case you find you can't switch or prefer Sharp/Cacko/OZ. If you have any corrections let me know and I'll update this post.
pdaXii13 5.2 full installation on c3100/c3200
c3100 (and c3200) owners must use v0.25 of the pdaXii13 updater.sh and build 15 of updater-tools.bin which are available on the pdaXii13 alpha/beta page here
http://www.tyrannozaurus.com/feed/pdaXii13/tmp/
In addition to having all the files required to install pdaXii13 on a c3000, you will also need pdaXrom beta3, which you can download from
http://mail.pdaxrom.org/download/1.1.0beta...beta3-akita.zip
Install that first as per the instructions on the pdaXrom.org site. I don't think it matters what size you flash the NAND to, the point is just to get b3 installed before pdaXii13, but I'd recommend going for the maximum size of 121 and why not?
Then install pdaXii13 as per Meanies instructions for c3000 but you need to install the kernel and bootloader TWICE, once before and one after installing the hdimage.
Reboot and enjoy the joys of having a full, truly portable Linux workstation!
BUGS in 5.2, using this install method:
1. On the initial boot after install, it will pause and the MD light will flash for around 15 minutes just after it says
EXT3-fs: mounted filesystem with ordered data mode
On subsequent boots it pauses on this message for a while, 5-10m.
2. Shortly after that it will produce a few, if not a few hundred
invalidate:dirty buffer
errors but meanie says this is harmless- YMMV!
3. To mount your vfat hda3 partition as a USB disk, choose the device
Compact Flash (0,3)
under the USB settings tool- this option is the equivalent of what would show up as 'Internal Storage' on a c3000. You should find that you will have one SD card option and six CF slot options so if CF (0,3) doesn't work for you can try CF (0.2) or (1,3).
BUGS PRESENT ON pdaXii13 C3000 5.2 ALSO
1. Firefox crashes when accessing websites with Flash. Fix: remove the flash plugin library called libnpflash.so under /usr/lib/firefox/lib/firefix-1.5/plugins
2. The Cancel key on the side of the Zaurus doesn't seem to do anything when running xmms. To fix this, edit /etc/X11/kb/spitz.xmodmap and uncomment
keycode 92 = Return
keycode 102 = c
to make the OK button play and the cancel key pause. This also applies when installing on c3000
3. There are some unwanted keybindings remaining (in the openbox config file /etc/xdg/openbox/rc.xml I think) which could cause problems to those using USB keyboards. Below is a list of USB keys and their current actions under 5.2
KEY | ACTION
Alt_Gr (Right Alt) | Starts Stardict
Right Windows Key | Starts rox
Print Screen | Starts xmms
F5 | Starts mrxvt
F6 | Startx xmms
F7 | Starts rox
F9 | Starts dillo
ESSENTIAL TIPS
* Uninstall all the scim packages if you don't need Chinese input support! I used a stopwatch to time how long gnumeric took to load- it took 34s when it had to load scim and only SEVEN seconds to load when I uninstalled scim! Just turning off SCIM support in the pdaXii13 config file isn't enough.
* If you want to change the font size of GTK2 based apps like rox, abiword, gthumb, gnumeric (most X apps used under pdaXrom are GTK2 based) then edit this file
/usr/share/themes/Default/gtk-2.0/gtkrc
TO ADD/DUNNO LIST
Working instructions for upgrading pdaXii13 Akita to use the hdimage
How to fix the module dependencies error under pdaXii13 Akita
A comparison of the two pdaXii13 full install methods for c3100/c3200 owners
something
something
someting
something
something
something
something
something
something
something
something
something
something
something
something
something
something
something
something
something
something
-Huge number or available packages (all of the Debian armel packages)
-Very up-to-date (as up-to-date as Debian)
-Not optimized for the Zaurus
-Fairly bug-free/supports most hardware
-Runs Angstrom or custom (yonggun/other) kernels
something
something
something
something
something
something