public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Carruth, Rusty" <RCarruth@Adtron.com>
To: <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] RedBoot 2.0.0 cannot find files on ext2 partitions formatted with mke2fs 1.41.3 from Ubuntu
Date: Wed, 29 Jul 2009 15:18:00 -0000	[thread overview]
Message-ID: <9EFFCEC257D2B649BCD6495F5C704AA9085E15EF@sr-fre-exch01.smartm.internal> (raw)

Greetings all!

I have a problem with RedBoot - apparently Red Boot 2.0.0 can read ext2
formatted filesystems if you use mke2fs 1.36, but not with mke2fs 1.41.3
(from Ubuntu 8.10).  (I get 'file not found', or something along those
lines, when I try to boot with 1.41.3-formatted ext2 partition, but it
works fine with 1.36-formatted ext2 partition.  And I'm using a script
which does simple 'mke2fs /dev/sda1' commands identically when building
either 1.36-formatted or 1.41.3-formatted CF images).

I looked all over the place for a 'revision history' for RedBoot (and
eCos), but no joy.

I looked all over the mailing lists as well, and had no luck finding any
hint of others having this problem.

So - was this a known problem, and has it been fixed, or do I always
have to format my ext2 compact flash partition with an old mke2fs?

Or, in the alternative, would upgrading to the most recent RedBoot fix
this issue?  (I'd hate to spend the effort upgrading to find it doesn't
fix anything and instead breaks something in our system...)

Thanks!

Rusty 


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2009-07-29 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 15:18 Carruth, Rusty [this message]
2009-07-29 15:55 ` [ECOS] " John Dallaway

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9EFFCEC257D2B649BCD6495F5C704AA9085E15EF@sr-fre-exch01.smartm.internal \
    --to=rcarruth@adtron.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).