Edit org.openembedded.dev/conf/machine/nokia770.conf

replace both (there are 2) instances of "xserver-kdrive-omap" with "xserver-kdrive-xomap"

I'm on the last step, but ipkg is complaining about "en-gb" locale data not being available (weird...) I changed my distro conf file to use "en-us" as I live in the US.

Successfully got a 64MB Angstrom X11 image for Nokia770. Only 75% disk usage too, so there's some free space.

Boots up with the Angstrom splash screen, but seems to hang. If anyone wants a debug copy let me know (it's an ext2 file).

I'll try to debug but don't have a lot of time tonight. (yes this will involve some soldering and a level convert cable for the brave among you http://maemo.org/community/wiki/howt...elcompilation/ look at the heading "Serial Console")

UPDATE: Turned off psplash, seems like GPE display manager doesn't want to start. It's not giving any debug info, just dropping to a login screen. I know dropbear and Ethernet gadget are running, but I've not yet successfully used Ethernet gadget. Can anyone who has experience with angstrom-minimal or angstrom-console on the 770 give me a hand with that? I'm running Ubuntu feisty.

AngstromAndN800.


My steps for install Angstrom on my N800.

1. I have download http://www.angstrom-distribution.org...0.rootfs.jffs2 image and http://www.angstrom-distribution.org...20070814113427 kernel image.
2. Flashed the images to my N800
./flasher-3.0-static -r armstrong/Angstrom-x11-image-glibc-test-20070814-nokia800.rootfs.jffs2 -f -R
./flasher-3.0-static -k zImage-2.6.18-osso40-nokia800-20070814113427 -f -R

3. Boot my N800.I see window with register formfor new users But my touchscreen is not responding. Joystik worked. Ok Button worked.

[

Has there been any progress on this?

same question here.
there are now newer autobuild for N770 and N800:
http://www.angstrom-distribution.org...ble/autobuild/

Try with a USB mouse, see if that works? just a thought...

Hmm, I'm not keen on flashing my os2008 rootfs for something that probably will not work.

Better option is to make ext2 partition and mount jffs2 rootfs in desktop linux and tar the files inside the jffs2 image to your ext2 partition. at least you may be able to edit files in angstrom.

The thing is that Angstrom (in fact the OE metadata) supports a pretty wide range of applications - if it has source, then it can be added to the metadata and built for whichever machine you want. The fact that some things are not included by default in a given image (e.g. the N800 one) means little. You can install it from the repo using ipkg, or edit the conf file to ensure it's included in the rootfs.

Interesting. It used to work in the image I tried (which I thought was for the N800). I'd be tempted to ask on #angstrom.

Basically Angstrom is the best thing going for the Zaurus, and assuming that power management could be sorted for the ITs, it would be equally good for those (i.e. there was certainly some work for enterprising hackers to do if they so desire). In GPE for example and when I last tried last year, the desktop applets weren't too aware of power-saving. The maemo applets are supposed to stop timer events when they are covered or the screen is locked, which allows dyntick to do it's thing. This wasn't enforced in GPE (for good reason as the other devices tend to suspend rather than slowing the tick rate), but with some patches could be made so.

Anyway, the point of my post is to say that this is an evolving and well supported build system and set of build metadata and that it should certainly not be written off but rather give it a go, send bugs and patches and make it better, if it's the sort of thing you're after.

Has anybody tried Angstrom recently? I'm hoping to get it booting on my N810, but the image I made from the online image builder just reboots after a while.

you probably need to ensure it "kicks" the watchdog regularly which catches lockups.