OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #gemini-pda chat on Freenode | #zaurus and #alarmz chat on Freenode | ELSI (coming soon) | Ibiblio


Welcome Guest ( Log In | Register )

> Post-flash Angstrom Problems
post Jan 20 2009, 11:54 AM
Post #1

Group: Members
Posts: 156
Joined: 29-March 05
From: Virginia
Member No.: 6,736


I flashed my Collie with the Angstrom-altboot-console-image-glibc-ipk-2007.12-r19-collie-installkit.tgz after verifying the md5sum. The flash was successful, and when I reset and replaced the battery case it came up to prompt me for the altboot password, as expected.


After entering the altboot password, I get the Angstrom boot screen, and the loading bar goes to 50% and stops. It has been sitting in this state for well over an hour.

Did I miss a step here? Is there a fix? I don't know if it is related, I am an Angstrom n00b, but I hit the reset button and had a key depressed (since I could not seem to get a response when it asked to hit a key to enter the altboot menu, and it started booting from the command line. It hung on boot at the following point:

udhcpc (v1.2.1) started
udhcpc[947]: (v1.2.1) started
SIOCGIFINDEX failed!: No such device
Starting portmap daemon: portmap.

And there it stopped.

I also used Koen's (very cool) online image builder to create an image. I created an ext2 filesystem on a 2GB SD card, then tried to boot SD from the altboot menu. It loaded the locomo_spi and mmc_block modules from /lib/modules/, then gave me an error:

ERROR: insmod failed
/bin/sh: can't acess tty; job control turned off
/etc/altboot-menu $

Can someone help me get the Z back up and running?

Go to the top of the page
+Quote Post
Start new topic
post Jan 21 2009, 11:29 AM
Post #2

Group: Members
Posts: 2,342
Joined: 30-July 06
Member No.: 10,575

Trying my favorite redownload the files, (reformat the card, probably not necessary), reflash might work for you. It looks like a flashing error to me.

The second error looks like it's missing a module. Also, it seems like there should be a newer kernel available than 2.6.20. All the other models are on 2.6.24 for the stable branch.

Trying the unstable branch may be another thing to try, if all else fails. Asking on the Angstrom mailing list isn't a bad idea either, as the devs don't check these forums.
Go to the top of the page
+Quote Post

Posts in this topic

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:


RSS Lo-Fi Version Time is now: 26th May 2018 - 09:49 AM