RobertCNelson
commented
7 years ago Use:
uenv_root=/dev/mmcblk0p2Open zatalian opened 7 years ago
RobertCNelson
commented
7 years ago Use:
uenv_root=/dev/mmcblk0p2
Hi,
I'm trying to make my pandaboard-es boot without uuid=... parameters. This used to work, but for some reason is now impossible.
if my /boot/uEnv.txt looks like this:
uname_r=current backup_serial_console=ttyO2,115200n8 set_boot_args=setenv bootargs console=${console} ${optargs} ${cape_disable} ${cape_enable} root=${root} rootfstype=${rootfstype} ${cmdline} uuid=48081c93-1a24-4cf0-a975-1a5e2045447a root=/dev/mmcblk0p2 ro rootfstype=ext4 fixrtc cape_disable= cape_enable= dtb=omap4-panda-es.dtb optargs= cmdline=quiet...then the system boots, but with the following kernel parameters:
debug: [console=ttyO2,115200n8 root=UUID=48081c93-1a24-4cf0-a975-1a5e2045447a ro rootfstype=ext4 rootwait quiet] ... debug: [bootz 0x82000000 0x88080000:9b012a 0x88000000] ...The root parameter from uEnv.txt is ignored and replaced with the root=uuid=...When i remove the uuid line in the file /boot/uEnv.txt, this are the kernel parameters on boot:
debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait quiet] ... debug: [bootz 0x82000000 0x88080000:9b012a 0x88000000] ...... here root does not correspond with the parameter in uEnv.txt. And of course, the system does not boot because of this.
Any idea on how to solve this problem?
Thanks!