From: "Tim Barker" <tim@tbarker.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] TinyGentoo Boot Issue
Date: Tue, 18 Jul 2006 15:41:12 +0100 [thread overview]
Message-ID: <7c0c64ac0607180741u69b9a21die535f7477e29690d@mail.gmail.com> (raw)
In-Reply-To: <9735eb9b0607180723q25365624ue2844855ec08f065@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
Hi Chad,
This may not be the same but a similar thing happened to me when trying to
mount a jffs2 root partition while not having jffs2 compiled into the
kernel, the kernel can't mount the root partition so bails out with a 'VFS:
Cannot open root device' error.
What partition are you using? vfat? Was the partition created/formatted
correctly? Did you include vfat support in the kernel? Did you build support
as a module? Drop me an email if you don't know how to check for the option
in the kernel .config (CONFIG_VFAT_FS in the case of vfat) or when you 'make
menuconfig'.
HTH,
Tim
On 7/18/06, Chad Files <cpfiles@gmail.com> wrote:
>
> On 7/17/06, Morgan, Austin D. <AUSTIN.D.MORGAN@saic.com> wrote:
> > Try creating a symlink from /init to /bin/busybox, worked for me...
>
> I tried your suggestion and now I get the same message with a
> different block set (3,2) instead of (0,0).
>
> Could it be something in the kernel that I missed?
>
> -- Chad
> --
> gentoo-embedded@gentoo.org mailing list
>
>
[-- Attachment #2: Type: text/html, Size: 1482 bytes --]
next prev parent reply other threads:[~2006-07-18 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 18:52 [gentoo-embedded] TinyGentoo Boot Issue Morgan, Austin D.
2006-07-18 14:23 ` Chad Files
2006-07-18 14:41 ` Tim Barker [this message]
2006-07-19 12:35 ` Chad Files
-- strict thread matches above, loose matches on Subject: below --
2006-07-17 18:35 Chad Files
2006-07-17 18:19 Chad Files
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=7c0c64ac0607180741u69b9a21die535f7477e29690d@mail.gmail.com \
--to=tim@tbarker.com \
--cc=gentoo-embedded@lists.gentoo.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