From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
by nuthatch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-embedded+bounces-1070-garchives=archives.gentoo.org@gentoo.org>)
id 1G2qmr-0007jw-H0
for garchives@archives.gentoo.org; Tue, 18 Jul 2006 14:43:03 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k6IEfEwd022037;
Tue, 18 Jul 2006 14:41:14 GMT
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191])
by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k6IEfCRP009833
for <gentoo-embedded@lists.gentoo.org>; Tue, 18 Jul 2006 14:41:13 GMT
Received: by nf-out-0910.google.com with SMTP id y25so198603nfb
for <gentoo-embedded@lists.gentoo.org>; Tue, 18 Jul 2006 07:41:12 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
b=QCAJAIWtyi6G9BdMXx2ReZy9FMPoCQOqeGBJqXCepJQOPCgBziRr3CYnU3/qZhQLqeOjurxF45ufq3Ti1wdWro9vs18BQBszUPVb3TkNfT5Ahutt5NVwONwAoKHYe+13mE4Pgad1ZLO2kugrEA5QI/rdoGY1G1DhVKwFlNAqsK8=
Received: by 10.78.151.3 with SMTP id y3mr1552749hud;
Tue, 18 Jul 2006 07:41:12 -0700 (PDT)
Received: by 10.78.97.14 with HTTP; Tue, 18 Jul 2006 07:41:12 -0700 (PDT)
Message-ID: <7c0c64ac0607180741u69b9a21die535f7477e29690d@mail.gmail.com>
Date: Tue, 18 Jul 2006 15:41:12 +0100
From: "Tim Barker" <tim@tbarker.com>
Sender: timbar@gmail.com
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] TinyGentoo Boot Issue
In-Reply-To: <9735eb9b0607180723q25365624ue2844855ec08f065@mail.gmail.com>
Precedence: bulk
List-Post: <mailto:gentoo-embedded@lists.gentoo.org>
List-Help: <mailto:gentoo-embedded+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-embedded+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-embedded+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-embedded.gentoo.org>
X-BeenThere: gentoo-embedded@gentoo.org
Reply-to: gentoo-embedded@lists.gentoo.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_15660_10161460.1153233672283"
References: <F23B2C80E3825F47B93655363249D0570C78B1@0695-its-exmp01.us.saic.com>
<9735eb9b0607180723q25365624ue2844855ec08f065@mail.gmail.com>
X-Google-Sender-Auth: 0069a14877b9c5e9
X-Archives-Salt: fd7a676b-b821-44a1-86f9-3bd1f451d67a
X-Archives-Hash: 81d197a3567f22757bf8e6fa3efa9c75
------=_Part_15660_10161460.1153233672283
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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
>
>
------=_Part_15660_10161460.1153233672283
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi Chad,<br><br>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 '
<span class="q" id="q_10c7dc5f5106f5fa_0">VFS: Cannot open root device' error. <br><br>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'.
<br><br>HTH,<br><br>Tim<br></span><br><br><div><span class="gmail_quote">On 7/18/06, <b class="gmail_sendername">Chad Files</b> <<a href="mailto:cpfiles@gmail.com">cpfiles@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 7/17/06, Morgan, Austin D. <<a href="mailto:AUSTIN.D.MORGAN@saic.com">AUSTIN.D.MORGAN@saic.com</a>> wrote:<br>> Try creating a symlink from /init to /bin/busybox, worked for me...<br><br>I tried your suggestion and now I get the same message with a
<br>different block set (3,2) instead of (0,0).<br><br>Could it be something in the kernel that I missed?<br><br>-- Chad<br>--<br><a href="mailto:gentoo-embedded@gentoo.org">gentoo-embedded@gentoo.org</a> mailing list<br>
<br></blockquote></div><br>
------=_Part_15660_10161460.1153233672283--
--
gentoo-embedded@gentoo.org mailing list