On 06:18 Mon 24 Sep , Paul Sokolovsky wrote: > Hello Dmitry, > > Sunday, September 23, 2007, 8:55:39 AM, you wrote: > > > On 02:40 Sun 23 Sep , Paul Sokolovsky wrote: > >> Hello, > >> > >> Heh, available from the official Angstrom download area, > >> http://www.angstrom-distribution.org/unstable/images/ . h3900, h4000, > >> hx4700 are tested on a device. I would appreciate feedback for h2200, > >> h5000. > >> > > Just tried on h2200 without any success. All I've got is a messagebox with > > red (X) and message "exepath:\Path to\liveRamdisk.exe" > > I tried to rename file to "a.exe" and put it in various directories, but > > still got this error messagebox. > > That means that debug haret version slipped into some liveramdisks, > which is sad, but not fatal. Once you started exe, you should close > FileExplorer and all other apps, and watch msgboxes/dialogs in > background. Once you click thru them and wait a bit more, load progress > bar will appear.
Oh, yeah! It works. Though it frightened me to death with a lots of following messages scrolling wildly through the screen while booting: ---------------------------------------------------------------------- <5>[ 91.270000] CLEANMARKER node found at 0x014bc000, not first node in block (0x01480000) <5>[ 91.320000] CLEANMARKER node found at 0x014c4000, not first node in block (0x014c0000) <4>[ 91.360000] Empty flash at 0x014c7fc4 ends at 0x014c8000 ...and so on ---------------------------------------------------------------------- I've been patient and my patience was finally rewarded with Angstrom bootup logo and then working GPE. Amazing! I played with it a little - usb networking via cradle and bluetooth (hcitool scan) seem to work fine. As a proof-of-concept it's simply brilliant, though in general it's not very attractive with the current set of applications - usually users want to see more than just gpe-terminal :) And this frightening messages (see above), which certainly caused by this line in fstab: /dev/mtdblock3 / jffs2 defaults 1 1 That's seem to be recurring problem for me every time I try fresh rootfs images - every time I need to change etc/fstab to reflect my real root device and filesystem (/dev/mmcblk0p1 and ext3 usually). I wonder if there's a generic way to avoid this problem. Detecting right root by parsing kernel command line? Or maybe adopting RedHat's strategy with mounting filesystems by its labels? Or something else? Dmitry "MAD" Artamonow _______________________________________________ Angstrom-distro-users mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
