Nope, mmcblk0 is the full disk, it results in two partitions mmcblk0p1 and mmcblk0p2
What ultimately resolved the issue was looking at lsmod and adding any and all modules that seemed to be related to storage. Does guix look at dependencies and add the modules that listed modules depend on? Seems like I had to add all the modules including the ones depended on by the ones I wanted (it was 6 modules in total) Sep 28, 2025 4:48:01 AM Noé Lopez <noe@noé.eu>: > Daniel Lakeland <[email protected]> writes: > >> Hi all. >> >> I built a raw disk image using guix system image. When I dd it to a USB >> stick it boots my test laptop just fine. But when I dd it to the >> /dev/mmcblk0 on that laptop, the laptop boots the image but it gets >> stuck at >> >> waiting for partition 'UUID-HERE' to appear.... >> >> and then drops into the guile REPL. >> >> I thought it might be because the initrd doesn't have the required >> modules, so I scrolled through the dmesg when it boots off USB and >> decided perhaps sdhci and rpmb_core are required and added this to the >> definition of the image: >> >> (initrd-modules (cons* "sdhci" "rpmb_core" %base-initrd-modules)) >> >> But it still does the same thing. >> >> Any ideas? > > I think the issue here is that the image is a disk image, but you are > writing it on a partition (/dev/mmcblk0), I think you’re supposed to > write it on the whole disk (/dev/mmcblk). > > This will delete your other partitions on that disk. So be careful. > > Good day, > Noé
