talos: Raspberry PI does not boot with 1.9.0

Bug Report

A disk image from the factory with only the raspberry pi sbc selected does not boot.

So I made it using this imager:

This imager profile DOES boot:

arch: arm64
platform: metal
secureboot: false
version: v1.9.0
input:
  kernel:
    path: /usr/install/arm64/vmlinuz
  initramfs:
    path: /usr/install/arm64/initramfs.xz
  baseInstaller:
    imageRef: ghcr.io/siderolabs/installer:v1.9.0
  overlayInstaller:
    imageRef: ghcr.io/siderolabs/sbc-raspberrypi:v0.1.0-beta.2
overlay:
  name: rpi_generic
  image:
    imageRef: ghcr.io/siderolabs/sbc-raspberrypi:v0.1.0-beta.2
output:
  kind: image
  imageOptions:
    diskSize: 1306525696
    diskFormat: raw
  outFormat: .zst

with ghcr.io/siderolabs/sbc-raspberrypi:v0.1.0 it does NOT boot. So i suspect it the raspberry pi firmware.

Sorry I have no better error message as I seem to have misplaced the weird hdmi cable that the Pi4 has.

To be clear, this is when flashing a disk-image. For some reason, I updated to talos 1.9.0-beta.1 with the update image fine from the factory.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 3
  • Comments: 19 (5 by maintainers)

Commits related to this issue

Most upvoted comments

I’ve used the SD boot method removing dtparam=watchdog=on from config.txtand it doesn´t loop reboot anymore. 👍

@95gabor just mount the sddisk in another system its on partition 1

I haven’t been able to replicate this. It does boot from a 1.9.3 freshly created image on a different pi from a thumbdrive, and i have 1.9.3 for a week now on I pi I use in my cluster. So I cannot help you (@simlun , @guilhermewolf , @95gabor ). You would be better of create a new issue

@95gabor I just did a fresh install using the v1.9.1, and it worked like a charm. Thank you for your comment!

Release 1.9.4 boots fine on cm4 again

I tried to boot Talos Linux v1.9.3 in my Raspberry Pi 4B yesterday, and I got the same error that @95gabor.

I can confirm this with v1.9.1, but I got boot loop with v1.9.3. I think this is u-boot related, because when I press a key during u-boot and stay in UEFI console (same with staying in GRUB) my RPi 4B is rebooting before decompressing the kernel.

Currently my cluster is reverted to v1.9.1 and working fine.