Re: set root variable for uImage?

[Adam Furmanczuk <afurmanczuk@knowtrek.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03.07.2013 18:58, Sascha Hauer wrote:
> Hi Adam,
> 
> On Wed, Jul 03, 2013 at 05:21:37PM +0200, Adam Furmanczuk wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> Hi,
>> 
>> 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.

Greetings,

Adam



- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlHUbZoACgkQefEEI87R1DcBxQCghNrD+tFbhEy80K01AUhlgAh3
q7MAn1uAF/e06ExOqvm1h9Y9+MLOLOt6
=OrR0
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlHUbbIACgkQefEEI87R1DeJYwCgt14GSG8cW5qAdpxnIUTFfb+E
iDEAmwZNdo9B095CM87WVw37HlcbbONT
=2Kd5
-----END PGP SIGNATURE-----

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox