> INITRAMFS_IMAGE = *"core-image-minimal-initramfs"* > INITRAMFS_IMAGE_BUNDLE = "1" ... > You can find the /var/log/dmesg here: https://pastebin.com/ya7iCtq7I
Some hints... [1] Kernel command line: BOOT_IMAGE=/bzImage root=PARTUUID=71d1d94a-83e8-4895-98eb-35309f58119f break=premount quiet rootwait rootwait rootfstype=ext4 *console=ttyS0,115200 console=tty0* input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7 fbcon: inteldrmfb (fb0) is primary device Console: switching to colour frame buffer device 128x48 *i915 0000:00:02.0: fb0: inteldrmfb frame buffer device* snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Hmmmmm... You are using console and serial, but full i915 GFX kernel driver is still included in the build??? [2] efi: EFI v2.31 by American Megatrends Using AMI BIOS as boot loader FW... OK?! Am I correct? [3] smpboot: CPU0: Intel(R) Atom(TM) CPU E3825 @ 1.33GHz (family: 0x6, model: 0x37, stepping: 0x9) This is CPUID ID 0x30679, which uses MCU... Which MicroCodeUnit? M0130679xxx (info from AMI BIOS)? [4] Using INTEL ATOM BYT E3825 dual core (sans Hyper-threading), implies that you are using 4GB (e820 messages) as single channel (one memory module DDR3 as 4GB)! Am I correct (important)? [5] Dracut phase?! > To my understanding the initramfs should be embedded in /boot/bzImage. > However since I use an intel platform I also have a /boot/microcode.cpio > which gets loaded via "initrd /microcode.cpio". Removing this line in > grub does not enable me to get an initramfs prompt either (again, using > break as option). You are obviously stopping in boot phase called dracut. Please, try to mount by hand /dev/sda(whatever)... You should use fdisk -l command, or do ls -al /dev | grep sda to dig out which partition you need to mount to /tmp dir to see rootfstype=ext4 (HDD/SSD) _______ Just thinking loud... .. . Hope this helps (has very little to do with YOCTO build system, BTW) . ;-) Zoran _______ On Fri, Jun 28, 2019 at 11:22 AM Moritz Porst <moritz.po...@gmx.de> wrote: > Hello, > I currently try to deploy a single rootfs update mechanism for my > embedded device. I can't boot to initramfs using either "break" or > "break=premount" (without quotes...). I tried this in systemd-boot and > grub-efi (always efi boot) but the boot process just continues normally. > If I insert at the same point e.g. "quiet" this argument is recognised. > I boot the .wic image with a separate boot partition from a USB stick. > in local.conf I have set: > INITRAMFS_IMAGE = "core-image-minimal-initramfs" > INITRAMFS_IMAGE_BUNDLE = "1" > > In order to reduce complexity I now use the standard > core-image-minimal-initramfs without .bbappend. I can confirm (from > seeing the task) that bitbake bundled the kernel with the initramfs. > > You can find the /var/log/dmesg here: https://pastebin.com/ya7iCtq7 > > To my understanding the initramfs should be embedded in /boot/bzImage. > However since I use an intel platform I also have a /boot/microcode.cpio > which gets loaded via "initrd /microcode.cpio". Removing this line in > grub does not enable me to get an initramfs prompt either (again, using > break as option). > > Did I forget some configuration or do I have to put the break statement > at a very specific position within the "linux ..." boot command ? Do you > know which bitbake variables to check ? (both set in local.conf do not > get overwritten, already checked this). I got the thud branch checked > out in all my meta-layers except for meta-qt which is currently on > master branch. > > Help is much appreciated ! > > Best regards > Moritz > > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto