strange, that’s the way describe on official docs. This is plain RPI stuff and has nothing special from DietPi side Raspberry Pi Documentation - Raspberry Pi hardware
What version of bootloader you are running?
vcgencmd bootloader_version
2022/04/26 11:24:28
version 507b2360eb46af23c05844b289dc5ae4ecfc3cca (release)
timestamp 1650968668
update-time 1669844545
capabilities 0x0000007f
not the latest one. Can you try to update
sudo rpi-eeprom-update
done everything, rebooted, and firmware still the same
I’m starting to thinking that there’s something else wrong
does sudo rpi-eeprom-update was offering an update?
yes
root@DietPi:~# sudo rpi-eeprom-update -d -a
*** INSTALLING EEPROM UPDATES ***
BOOTLOADER: update available
CURRENT: Tue Apr 26 10:24:28 UTC 2022 (1650968668)
LATEST: Wed Jan 11 17:40:52 UTC 2023 (1673458852)
RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)
Use raspi-config to change the release.
VL805_FW: Using bootloader EEPROM
VL805: up to date
CURRENT: 000138a1
LATEST: 000138a1
CURRENT: Tue Apr 26 10:24:28 UTC 2022 (1650968668)
UPDATE: Wed Jan 11 17:40:52 UTC 2023 (1673458852)
BOOTFS: /boot
Using recovery.bin for EEPROM update
EEPROM updates pending. Please reboot to apply the update.
To cancel a pending update run "sudo rpi-eeprom-update -r".
ok at least the update is detected. What gives following after a reboot
journalctl -u rpi-eeprom-update.service
-- Journal begins at Sat 2023-02-11 19:17:01 GMT, ends at Sat 2023-02-25 08:11:48 GMT. --
Feb 11 19:17:02 DietPi systemd[1]: Starting Check for Raspberry Pi EEPROM updates...
Feb 11 19:17:02 DietPi rpi-eeprom-update[390]: Skipping automatic bootloader upgrade. current 1650968668 >= min 1599135103
Feb 11 19:17:03 DietPi rpi-eeprom-update[390]: BOOTLOADER: up to date
Feb 11 19:17:03 DietPi rpi-eeprom-update[390]: CURRENT: Tue Apr 26 10:24:28 UTC 2022 (1650968668)
Feb 11 19:17:03 DietPi rpi-eeprom-update[390]: LATEST: Wed Jan 11 17:40:52 UTC 2023 (1673458852)
Feb 11 19:17:03 DietPi rpi-eeprom-update[390]: RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)
Feb 11 19:17:03 DietPi rpi-eeprom-update[390]: Use raspi-config to change the release.
Feb 11 19:17:03 DietPi rpi-eeprom-update[390]: VL805_FW: Using bootloader EEPROM
Feb 11 19:17:03 DietPi rpi-eeprom-update[390]: VL805: up to date
Feb 11 19:17:03 DietPi rpi-eeprom-update[390]: CURRENT: 000138a1
Feb 11 19:17:03 DietPi rpi-eeprom-update[390]: LATEST: 000138a1
Feb 11 19:17:03 DietPi systemd[1]: Finished Check for Raspberry Pi EEPROM updates.
interesting. Never have seen this before but looks like your bootloader is not updating because a minimal version has been specified.
can you check following configuration file?
cat /etc/default/rpi-eeprom-update
FIRMWARE_RELEASE_STATUS="default"
Honestly I have no idea where the BOOTLOADER_AUTO_UPDATE_MIN_VERSION should be set or unset. Never have seen this before. @MichaIng maybe you have an idea.
Could you try to update manually
sudo rpi-eeprom-update -a
another idea would be to switch from FIRMWARE_RELEASE_STATUS="default" to FIRMWARE_RELEASE_STATUS="latest" inside /etc/default/rpi-eeprom-update
unfortunately, nothing changed
Would be worth a try to freshly install dietpi on the SD card and try again?
edit: looks like my SD is completely gone, i can’t even format it or flash a new dietpi image, but for some reason dietpi still runs
did you add the -a at the end of sudo rpi-eeprom-update??
bad news. We would need one to continue.
i’ll try again on monday, i’ll keep you updated
Thanks a lot for now!
I’ve no idea idea, such min version sounds nonsense to me: If it is not set to some unknown future version, it basically disables updates, which can be better done by simply disabling the servive.
Since this is outside of DietPi control, and we’ve never seen this before, best to check back with RPi devs.
You can use Raspbery Pi os imager to build a flash card to reflash the eeprom back to boot from SD (or you can use it to build boot from USB as well)
Once inserted the screen goes all wonky…power down and it should boot from SD
Use a different linux os and use gparted to scan the SD card and check for errors on all the partitions
I made some progress.
Just as i thought, the sd was completely broken.
Right now i’m able to boot from USB, restored the backup, but trying to update dietpi gives me an exit code 132
Can you share the entire output of running dietpi-update
Packing upload archive │
│ - Command: 7zr a -m0=lzma2 -mx=9 -spf -x!/var/log/journal/* 254c8748-6517-4183-a20e-027740cfffa1.7z CMD_OUT.txt │
│ G_EXEC_ERROR_REPORT /var/log /boot/config.txt /boot/cmdline.txt /boot/boot.ini /boot/uenv.txt /boot/uEnv.txt │
│ /boot/armbianEnv.txt /boot/boot.cmd /boot/dietpi.txt /boot/dietpi /var/lib/dietpi /var/tmp/dietpi /run/dietpi │
│ /etc/bash.bashrc /etc/bashrc.d /root/.bashrc /etc/profile /etc/profile.d /root/.profile /etc/rc.local │
│ /etc/X11/xorg.conf /etc/X11/xorg.conf.d /etc/asound.conf /etc/network/interfaces /etc/network/interfaces.d │
│ /etc/wpa_supplicant/wpa_supplicant.conf /etc/fstab /etc/sysctl.conf /etc/sysctl.d /etc/init.d /etc/systemd/system │
│ /lib/systemd/system /usr/local/lib/systemd/system /etc/apt/sources.list /etc/apt/sources.list.d /etc/apt/preferences │
│ /etc/apt/preferences.d /etc/apt/apt.conf.d │
│ - Exit code: 132 │
│ - DietPi version: v8.13.2 (MichaIng/master) | HW_MODEL: 4 | HW_ARCH: 3 | DISTRO: 6 │
│ - Image creator: DietPi Core Team │
│ - Pre-image: from scratch │
│ - Error log:
Are you trying to upload a bug report?