Hi Dennis, Please see my remarks below
On Thursday, August 27, 2020 at 2:48:16 AM UTC+2, Dennis Bieber wrote: > > On Wed, 26 Aug 2020 15:50:56 -0700 (PDT), in > gmane.comp.hardware.beagleboard.user Pavel Yermolenko > <py.ohayo-fowrgoyegzlydzi6cay...@public.gmane.org <javascript:>> wrote: > > > I suspect someone will point out where my interpretation is faulty > but... > > > >** Unable to read "/boot/uboot.env" from mmc0:1 ** > > mmc0 is, I believe, the SD card; I presume the :1 is "partition > 1"; at > least mine booted with a standard image on SD card shows as being > /dev/mmcblk0p1. And standard images don't have a uboot.env file. > > debian@beaglebone:~$ ls -l /boot > total 20108 > -rw-r--r-- 1 root root 162601 Aug 19 13:38 config-4.19.94-ti-r48 > drwxr-xr-x 3 root root 4096 Aug 19 17:14 dtbs > -rw-r--r-- 1 root root 6617852 Aug 19 17:20 initrd.img-4.19.94-ti-r48 > -rw-r--r-- 1 root root 542 Aug 19 21:34 SOC.sh > -rw-r--r-- 1 root root 3626463 Aug 19 13:38 System.map-4.19.94-ti-r48 > drwxr-xr-x 2 root root 4096 Aug 19 17:23 uboot > -rw-r--r-- 1 debian debian 2062 Aug 19 21:34 uEnv.txt > -rwxr-xr-x 1 root root 10158592 Aug 19 13:38 vmlinuz-4.19.94-ti-r48 > debian@beaglebone:~$ > > ... so did you create any such uboot.env file and place that on the SD > care? > No, sd-card was empty, ext4-fromatted with single partition rootfs. >mmc0 is current device > >gpio: pin 54 (gpio 54) value is 1 > >Checking for: /uEnv.txt ... > >Checking for: /boot.scr ... > >Checking for: /boot/boot.scr ... > >Checking for: /boot/uEnv.txt ... > > Do ANY of these files exist on the SD card? > No, sd-card was empty I prepared it for transferring u-boot files. I've onlly one sd-card, so after regenerating the image in eMMC I plan to use it for u-boot exploring. My comprehension is as follows: at that stage I had to create in some way boot partition in order to transfer there *MLO* and *u-boot.img* on host machine. > >mmc1(part 0) is current device > >Scanning mmc 1:1... > > And here it appears it gave up on the SD card and switched to the > eMMC > > >Found /boot/extlinux/extlinux.conf > >Retrieving file: /boot/extlinux/extlinux.conf > >256 bytes read in 13 ms (18.6 KiB/s) > >1: Linux 4.19.94-ti-r42 > >Retrieving file: /boot/vmlinuz-4.19.94-ti-r42 > >10095592 bytes read in 648 ms (14.9 MiB/s) > >append: console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 > > ... though that line looks, to this neophyte, like... after loading the > core image from eMMC, it is setting up the SD card to be the root file > system. > > >[ 1.004670] Kernel panic - not syncing: No working init found. Try > >passing init= option to kernel. See Linux > >Documentation/admin-guide/init.rst for guidance. > > Unfortunately, that page doesn't seem too helpful. > > >[ 1.097330] ---[ end Kernel panic - not syncing: VFS: Unable to mount > >root fs on unknown-block(0,0) ]--- > > Now, that message is at > https://www.kernel.org/doc/Documentation/admin-guide/init.rst with this > advice: > > """ > 1) **Unable to mount root FS**: Set "debug" kernel parameter (in > bootloader > config file or CONFIG_CMDLINE) to get more detailed kernel messages. > """ > > > > -- > Dennis L Bieber > > -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/1e211965-020e-4739-8aef-699082351cc5o%40googlegroups.com.
