Fixed my own issue. I moved the "root=/dev/mmcblk0p2" to the end of the "cmdline=" string in the uEnv.txt file on my p2 and it all suddenly seems to work great. So, lesson learned-- position of "root=" matters in the uEnv file. BUT WHY?
Heisenbug Uncertainty Principle: You may know where the bug is but not how to fix it -- or you know how to fix it but not where it is. NEVER shall you know both! Bryan On Monday, July 4, 2016 at 3:49:20 PM UTC-5, Bryan Wilcutt wrote: > I'm NOT using an SD CARD for this, but I have partitioned my mmcblk0 into > two bootable drives. I would like to selectively boot off of one OR the > other. > > I created a uEnv.txt on p1: > > And a uEnv.txt on p2: > > > > > I want to boot from p2 in this instance. Doing so, the boot process > starts up but then hangs with: > > [ 15.466256] Waiting 1 sec before mounting root device... > [ 16.480027] Waiting for root device /dev/mmcblk1p2... > > There is no mmcblk1p2!!! I dumped the env of u-boot and no where in it > does it specifically address mmcblk1p2 but it does reference an mmc device > indirectly. Why is u-boot hell bent on booting off of mmcblk1p2 when the > cmdline clearly states mmcblk0p2??? > > Also, fstab for both p1 and p2 are identical, both referencing the same > device UUID and file system type of ext4 as they should. > > > > Any help would be appreciated! > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/57f5a19b-810c-4c1c-998b-fddc0ad92d48%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
