All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: Lista Openembedded <openembedded-devel@openembedded.org>
Subject: Re: Bootloader problems
Date: Fri, 27 Feb 2009 13:47:07 -0500	[thread overview]
Message-ID: <20090227184707.GA6027@denix.org> (raw)
In-Reply-To: <1235734652.7210.12.camel@ubuntu2>

On Fri, Feb 27, 2009 at 12:37:32PM +0100, Paolo Cremonese wrote:
> Hi all,
> I have problems in generating a bootable device (CF)
> During the setup the CF is connected to the host via an USB adapter.
> 
> These are the steps I do:
> 
> # fdisk /dev/sdb
>    create a linux partition /dev/sdb1 and activate it
> 
> # mkfs.ext3 /dev/sdb1
> 
> # mount -t ext3 /dev/sdb1 /media/disk
> 
> # cd /media/disk
> # tar
> -xvf /home/paolo/oe/stuff/build/gpe-image/deploy/glibc/images/i586-generic/gpe-image-i586-generic.tar
> 
> and the filesystem is correctly on the CF
> 
> # cd boot
> # mkdir grub
> # cd grub
> # < copy of grub files>
> # grub ...
> 
> the menu.lst contains
> 
> title		OpenEmbedded Linux (hda1)
> root		(hd0,0)
> kernel		/boot/bzImage-2.6.21 root=/dev/hda1 ro
> quiet
> 
> 
> The system boots, but when the filesystem is created, the kernel crashes
> with the message:
> 
> VFS: Cannot open root device "(hd0,0)" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: unable to mount root fs or
> unknown-block(0,0)
> 
> but I don't understand what I have to do...

Please verify:

1. Your device, you are trying to boot, maps your CF at /dev/hda (or /dev/sda)
2. Your kernel has the support for the filesystem type you want - ext3/ext2
3. Your filesystem has static /dev/hda and enough /dev/hda? devnodes

-- 
Denys



  reply	other threads:[~2009-02-27 18:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27 11:37 Bootloader problems Paolo Cremonese
2009-02-27 18:47 ` Denys Dmytriyenko [this message]
2009-03-01  9:35   ` Paolo Cremonese
2009-03-02 16:36     ` Anatoly Shipitsin

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=20090227184707.GA6027@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.