Public bug reported:
Welcome to Ubuntu 25.10 (GNU/Linux 6.17.0-1003-raspi aarch64)
* Documentation: https://docs.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/pro
System information as of Wed Feb 18 18:56:08 -03 2026
System load: 0.34
Usage of /: 0.4% of 916.65GB
Memory usage: 11%
Swap usage: 0%
Temperature: 51.1 C
Processes: 176
Users logged in: 0
IPv4 address for wlan0: 192.168.68.94
IPv6 address for wlan0: fd2f:99ca:9858:26c7:dea6:32ff:fe49:8501
* Due to a now-resolved bug in the date command, this system may be unable
to automatically check for updates. Manually install the update using:
sudo apt install --update rust-coreutils
https://discourse.ubuntu.com/t/enabling-updates-on-ubuntu-25-10-systems/
piboot-try:
New boot assets in /boot/firmware/new failed. Fallen back to known good
state. Use piboot-try --reset-new to re-test boot assets. If you are able
to determine the boot failure is due to a bug, please file an issue:
ubuntu-bug flash-kernel
0 updates can be applied immediately.
Last login: Wed Feb 18 18:45:38 2026 from 192.168.68.62
ubuntu@ubuntu:~$ sudo rpi-eeprom-update
[sudo: authenticate] Password:
BOOTLOADER: up to date
CURRENT: Tue Feb 11 17:00:13 UTC 2025 (1739293213)
LATEST: Tue Feb 11 17:00:13 UTC 2025 (1739293213)
RELEASE: default (/usr/lib/firmware/raspberrypi/bootloader-2711/default)
Use raspi-config to change the release.
VL805_FW: Dedicated VL805 EEPROM
VL805: up to date
CURRENT: 000138c0
LATEST: 000138c0
ubuntu@ubuntu:~$
Mostrar menos
19:02
Firmware está atualizado, então não é isso. Vamos verificar o valor do tryboot
diretamente:
bash
od -A n -t u4 --endian big /proc/device-tree/chosen/bootloader/tryboot | tr -d
'[:space:]'
Se retornar 0, significa que o Pi4 não está entrando em modo tryboot durante o
teste — o que explica por que sempre marca como bad. Isso pode ser um bug
conhecido no Ubuntu 25.10 com o piboot-try no Pi 4.
0
19:03
Confirmado — tryboot retorna 0, o que significa que o Pi 4 não está suportando
o mecanismo tryboot corretamente. Esse é o bug real.
O tryboot é um recurso do bootloader do Raspberry Pi, mas no Pi 4 ele
tem limitações comparado ao Pi 5. Veja se há um bug reportado:
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: flash-kernel 3.109ubuntu6
ProcVersionSignature: Ubuntu 6.17.0-1003.3-raspi 6.17.0-rc7
Uname: Linux 6.17.0-1003-raspi aarch64
ApportVersion: 2.33.1-0ubuntu3
Architecture: arm64
CasperMD5CheckResult: unknown
CloudArchitecture: aarch64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: config-disk (/dev/sda1)
Date: Wed Feb 18 19:04:25 2026
ImageMediaBuild: 20251007.1
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: flash-kernel
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: flash-kernel (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug arm64 arm64-image questing raspi-image
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2142169
Title:
Pi4 não está entrando em modo tryboot durante o teste no Ubuntu 25.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2142169/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
