From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Adam Furmanczuk" <afurmanczuk@knowtrek.com>
Cc: barebox@lists.infradead.org
Subject: Re[2]: set root variable for uImage?
Date: Wed, 03 Jul 2013 22:42:23 +0400 [thread overview]
Message-ID: <1372876943.127000271@f219.mail.ru> (raw)
In-Reply-To: <51D46DB2.90002@knowtrek.com>
> >> I restate this question from my previous thread "how to flash and
> >> set root variable". Thanks very much to Sascha and Alexander for
> >> introducing into barebox building and flashing.
> >>
> >> I have a basic scenario. Want to boot uImage and then hand over
> >> to the root partition. With u-Boot this was very easy:
> >>
> >> setenv bootargs "console=tty0 console=ttymxc0,115200n8
> >> root=/dev/mmcblk0p3 rootfstype=ext4 rootwait ro"
> >>
> >> With barebox however, when I boot the uImage, it complains about
> >> not setting correct "root=".:
> >>
> >> [ 1.718527] VFS: Cannot open root device "(null)" or
> >> unknown-block(0,0): error -6 [ 1.726226] Please append a correct
> >> "root=" boot option; here are the available partitions:
> >>
> >> Now what i do in Barbox is the following;
> >>
> >> (hint enter to go into console) barebox@myhost:/ mkdir /media2
> >> barebox@myhost:/ mount /dev/disk0.1 fat /media2 barebox@myhost:/
> >> bootm /media2/uImage root=/dev/mmcblk0p3 rootfstype=ext4
> >
> > the bootm command evaluates the 'bootargs' environment variable,
> > so before executing bootm do a:
> >
> > export bootargs="root=/dev/mmcblk0p3 rootfstype=ext4"
> >
> > (sidenote: This is not documented with 'help bootm', shame on us.
> > Try the 'magicvar' command instead which lists all variables with
> > special meanings)
> >
> > Sascha
> >
>
> Hi Sascha,
>
> it does not seem to work for me, I typed:
>
> mkdir /mnt/disk1
> bootargs="root=/dev/mmcblk0p3 rootfstype=ext4"
> mount /dev/disk0.1 fat /mnt/disk1
> bootm /mnt/disk1/uImage
>
>
> I choose different values for root, like "mmcblk0p3","/dev/mmcblk0p1",
> "b303" ...
>
> I am running MX53QSB with barebox 2013.05 build get this output:
>
> VFS: Cannot open root device "(null)" or unknown-block(2,0)
> Please append a correct "root=" boot option; here are the available
> partitions:
> b300 3872256 mmcblk0 driver: mmcblk
> b301 512 mmcblk0p1
> b302 16384 mmcblk0p2
> b303 3854336 mmcblk0p3
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(2,0)
>
>
> Note: Unknown block is always (2,0) no matter what i try to specify.
>
> This problem might be related to mx53 architecture only.
Probably you need "rootwait" option, same as you specify for u-boot.
---
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-07-03 18:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 16:03 how to flash barebox and set root variable? Adam Furmanczuk
2013-06-06 16:21 ` Sascha Hauer
2013-06-07 5:08 ` Adam Furmanczuk
2013-06-07 10:55 ` Sascha Hauer
2013-06-10 12:24 ` Adam Furmanczuk
2013-06-10 17:01 ` how to flash barebox and set root variable? - barebox is gone :( Adam Furmanczuk
2013-06-10 17:07 ` Re[2]: " Alexander Shiyan
2013-06-10 17:23 ` Adam Furmanczuk
2013-06-10 17:29 ` Sascha Hauer
2013-06-11 8:10 ` Adam Furmanczuk
2013-06-12 6:12 ` Adam Furmanczuk
2013-06-12 7:19 ` Adam Furmanczuk
2013-06-12 8:07 ` Sascha Hauer
2013-06-12 8:22 ` Adam Furmanczuk
2013-06-12 8:48 ` Sascha Hauer
2013-06-12 9:02 ` Adam Furmanczuk
2013-06-12 15:54 ` Sascha Hauer
2013-06-12 16:01 ` Re[2]: " Alexander Shiyan
2013-06-12 16:14 ` Adam Furmanczuk
2013-07-03 13:32 ` set root variable for uImage? Adam Furmanczuk
2013-07-03 15:21 ` Adam Furmanczuk
2013-07-03 16:58 ` Sascha Hauer
2013-07-03 18:30 ` Adam Furmanczuk
2013-07-03 18:42 ` Alexander Shiyan [this message]
2013-07-03 20:26 ` Sascha Hauer
2013-07-04 10:30 ` Adam Furmanczuk
2013-07-04 10:39 ` Sascha Hauer
2013-07-04 10:59 ` set root variable for uImage? - SOLVED Adam Furmanczuk
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=1372876943.127000271@f219.mail.ru \
--to=shc_work@mail.ru \
--cc=afurmanczuk@knowtrek.com \
--cc=barebox@lists.infradead.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.