Creating a distro on a sim card

Christopher J. White chris at
Sun Nov 30 03:03:08 CET 2008

On Sun, 2008-11-30 at 02:32 +0300, Evgeniy Karyakin wrote:
> Christopher J. White:
> > With Debian on a 2GB microSD card, here's my boot cmdline
> > (cat /proc/cmdline):
> > 
> > glamo_mci.sd_max_clk=10000000 rootfstype=jffs2 root=/dev/mtdblock6
> > console=ttySAC2,115200 console=tty0 loglevel=8 regular_boot
> > mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0000(rootfs) rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5
>     Don't anybody see a problem with this settings? There's two pairs of 
> parameters rootfstype and root; who get the priority? This redundancy is 
> because environment has the following variables:
> bootargs_base=rootfstype=jffs2 root=/dev/mtdblock6 
> console=ttySAC2,115200 console=tty0 loglevel=4 regular_boot
> menu_1=Boot from microSD (FAT+ext2): setenv bootargs ${bootargs_base} 
> rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 ${mtdparts} ro; mmcinit; 
> fatload mmc 1 0x32000000 ${sd_image_name}; bootm 0x32000000
>     bootargs_base has one pair, menu_1 has another. So, who's in charge 
> here?

LOL....I didn't even notice that.  After several *hours* of working on
it (and dumping the 8GB card I bought that just would not work), I
finally found a combo that worked.

Needless to say the above works fine for me with my Debian distro, so it
must just take the last assignment as the final and go from there.

You are right that it's a combo of boot_args plus the indirection from
menu_1 using boot_args.


More information about the community mailing list