Angstrom Status On Tosa, Updated March 12, 2008 Options

[xjqian]

Get it here: Get Angstrom Unstable Release for tosa The latest tested release is r8 (kernel 2.6.23).

Working out-of-box

altboot with loopback image or direct fs
Kernel 2.6.23 (testing 2.6.24 for >= r9) Tosa kernel status from Dmitry
Images: Opie 1.2.3 (core opie application feed, other opie or qt applications not in the feed yet) and GPE 2.8 (x11-image) with match-box as default WM
Keyboard (keymap changed in 2.6.24)
Internal Wifi (wlan-ng-modules-usb 2.8) 802.11b WEP only, no WPA
SD: non-sdhc or sdhc (tested with 4GB card of both)
CF and 2nd CF on sled

OE Tosa Meta-Bug

Outstanding critical bugs:

1. suspend/resume OE bug 2134
[Closed] 2. sound system OE bug 3518 Speaker/Headphone tested working. Mic/phone untested

Major bugs:

[Hacked kdrive in x11-image to overcome the problem, still an issue in opie-image] 1. frame buffer (a.k.a, screen corruption or the famous yellow vertical lines) : occurs "occasionally" with 2.6.23 kernel, much better than "often" with 2.6.17 kernel OE bug 490

Opie bugs: file Opie bug tracker

GPE bugs: file GPE bug tracker

Kernel, roofs or packaging bugs: file OE bug tracker


Not tested yet:
?USB host
?Speaker/Headphone/Headset/Mic (need to fix the alsa state in r9)
USB client
USB network
Mic (the one on the back of the device) / PhoneMic (2.5mm jack used with a headset)
etc.

This post has been edited by xjqian: Jun 19 2008, 12:17 AM

[AsLan^]

Okay, two more problems have arisen...

1. Building base-image or console-image fails at the wlan-ng packages. Here is the log for wlan-ng modules.

NOTE: make CC=ccache arm-angstrom-linux-gnueabi-gcc -march=armv5te -mtune=xscale -mno-thumb-interwork -mno-thumb LD=arm-angstrom-linux-gnueabi-ld PARALLEL_MAKE= -C src all
make: Entering directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src'
set -e; for d in mkmeta shared p80211 prism2; do make WLAN_SRC=/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/ -C $d ; done
make[1]: Entering directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/mkmeta'
mkdir -p obj
make[1]: Leaving directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/mkmeta'
make[1]: Entering directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/shared'
Nothing to do...
make[1]: Leaving directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/shared'
make[1]: Entering directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/p80211'
make -C /home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/linux-2.6.29-r4/linux-2.6.29 M='/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/p80211' WLAN_SRC=/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/ modules
make: Entering an unknown directory
make: *** /home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/linux-2.6.29-r4/linux-2.6.29: No such file or directory. Stop.
make: Leaving an unknown directory
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/p80211'
make: *** [all] Error 2
make: Leaving directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src'
FATAL: oe_runmake failed

It appears to be a file not found error but I haven't modified the tree at all and I did a "git pull" before building.

2. Two kernels were built (2.6.24-r13 and 2.6.29-r5) as well as updater.sh.tosa. Only 2.6.24-r13 can be flashed using updater.sh.tosa, 2.6.29-r5 gives the error message that the file is too big. This is a problem because as you know, the reason I am trying to get this all up and running is so I can take a shot at installing Android and I believe Android requires a 2.6.25 or higher kernel to work.