[Angstrom-devel] Altboot SD mounting problems after upgrade 2.6.21 -> 2.6.22

[GROG! (Jeff Howie)]

I've gone ahead & reinstalled the latest (090507) X11 image to my
internal flash. I then installed altboot & got the same error as
before when trtying to boot my image:

   /sbin/fsck.ext3: no such device or address while trying to open
/dev/mmcblk0p1
   Possibly non-existant or swap device?
  Mounting /media/card...ERROR: /bin/mount -t auto -o defaults,noatime
/dev/mmblk0p1 /media/card failed

I tried copying the .bin file to another sd card, in case my card is
borked. I got the same error using a freshly formatted (to vfat) card.

Looking at the error message, it seems strange that it's trying to use
fsck.ext3, though. Could this be related to bug 1759 (altboot mounts
vfat SD as ext2)?

On 9/8/07, GROG! (Jeff Howie) <uber.grog at gmail.com> wrote:
> I've done an 'ipkg update; ipkg upgrade' on my Zaurus C860 (it's been
> a while since the last updated) & I noticed that there was a new
> kernel (I was 2.6.21, not 2.6.22). Unfortunately after upgrading the
> kernel (zImage), alboot can no longer mount my sd card, so I can't
> boot into my working install (an image on my sd card). When I select a
> normal (internal) boot at the altboot menu, I can boot into the
> internal console image I have installed there & the sd card is mounted
> correctly without problems. I've also ran the update/upgade on my
> internal image as well, so that it's up to date & shows 2.6.22 running
> just fine.
>
> So I'm assuming it's an altboot problem, but what can I do to fix it?
> Suggestions welcome please. thks

-- 
GROG!