Robert, I really can't remember what the original image file was that I started with. I only have the /etc/dogtag info.
The image "file" I am using is one I created using the /opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh script. This was done after installing the original image and then installing just what I needed for some Qt development. I did remember to remove the "quiet" from the command line after installing the image again. I then tried doing an 'apt install ..' for individual packages that needed updated. It appears one of the openssh packages is what is breaking the boot. I got this after updating openssh-client, openssh-server, openssh-sftp-server, and openssl: [ 3.270685] Freeing unused kernel memory: 1024K Loading, please wait... [ 3.311056] usb 1-1.1: new full-speed USB device number 3 using musb-hdrc starting version 232 [ 3.367799] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 3.384045] random: systemd-udevd: uninitialized urandom read (16 bytes read) [ 3.393865] random: udevadm: uninitialized urandom read (16 bytes read) [ 3.425391] usb 1-1.1: New USB device found, idVendor=046d, idProduct=c534 [ 3.439037] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.455036] usb 1-1.1: Product: USB Receiver [ 3.463011] usb 1-1.1: Manufacturer: Logitech [ 3.492331] input: Logitech USB Receiver as /devices/platform/ocp/47400000.usb/47401c00.usb/musb-hdrc.1/usb1/1-1/1-1.1/1-1.1:1.0/0003:046D:C534.0001/input/input1 [ 3.587187] hid-generic 0003:046D:C534.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-musb-hdrc.1-1.1/input0 [ 3.629415] input: Logitech USB Receiver as /devices/platform/ocp/47400000.usb/47401c00.usb/musb-hdrc.1/usb1/1-1/1-1.1/1-1.1:1.1/0003:046D:C534.0002/input/input2 [ 3.722058] hid-generic 0003:046D:C534.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-musb-hdrc.1-1.1/input1 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mmcblk1p1 does not exist. Dropping to a shell! (initramfs) A quick google search says that there may be a problem with the UUID. Isn't the SDcard flasher supposed to set that? Hartley On Friday, October 23, 2020 at 2:53:22 PM UTC-7, RobertCNelson wrote: > > On Fri, Oct 23, 2020 at 4:12 PM Hartley Sweeten <[email protected] > <javascript:>> wrote: > > > > Ok, this happened again. I forgot that an 'apt upgrade' breaks my setup. > > > > I reinstalled my default image on the BBB. For reference: > > > > ~$ cat /etc/dogtag > > BeagleBoard.org Debian Image 2018-01-21 > > Can you share the "file" name of this image? Such that i can test. > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- 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/533a7b98-4a67-477b-bdf7-206435922a99o%40googlegroups.com.
