elemental-toolkit: Kernel stuck after initrd

cos-toolkit version: cos-system 0.7.0-7

CPU architecture, OS, and Version: aarch64 on rpi4 cos-green

Describe the bug

When trying to boot a rpi4 using u-boot with a chain-loaded grub, the kernel gets stuck without any output after loading the initrd. (see logs section below for output)

To Reproduce

Partition an SD-Card into two partions, one formatted with FAT containing the boot data created using https://github.com/dragonchaser/pi-bootbuilder the second one formatted with ext4 containing the cos-system from quay.io (quay.io/costoolkit/releases-green-arm64:cos-system-0.7.0-7)

Expected behavior cOS should be booting or there should be at least an output why the kernel is stuck/failing.

Logs

Loading Linux 5.3.18-59.24-default ...
Loading initial ramdisk ...
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 16 (15 by maintainers)

Commits related to this issue

Most upvoted comments

I’m actually seeing the same thing when running the JeOS image for Odroid c2, and images created with openSUSE in #867