An upgraded rpi-eeprom-git 20210112-1 package has been pushed to the unstable branch when the mirrors sync for those who like to live on the edge. The beta firmware folder was updated to a new image yesterday:
[ray@pi4 ~]$ sudo rpi-eeprom-update -r
Removing temporary files from previous EEPROM update
[ray@pi4 ~]$
[ray@pi4 ~]$ sudo rpi-eeprom-update
BCM2711 detected
VL805 firmware in bootloader EEPROM
BOOTLOADER: up-to-date
CURRENT: Mon Jan 11 03:44:33 PM UTC 2021 (1610379873)
LATEST: Mon Jan 11 03:44:33 PM UTC 2021 (1610379873)
FW DIR: /lib/firmware/raspberrypi/bootloader/beta
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1
Hello! I have a quick question–I want to make sure I’m interpreting the output of rpi-eeprom-update
correctly. Here’s my current output:
~]$ sudo rpi-eeprom-update
BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTLOADER: up-to-date
CURRENT: Thu Sep 3 12:11:43 PM UTC 2020 (1599135103)
LATEST: Thu Sep 3 12:11:43 PM UTC 2020 (1599135103)
FW DIR: /lib/firmware/raspberrypi/bootloader/stable
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1
The way I’m reading it, the VL805 firmware has not changed in the beta branch, but the bootloader has?
Correct but you need to be in the beta FW directory to change it instead of stable.
Thanks. I only switched to the stable branch to get USB boot support and the 5.10 kernel. I’m wary of installing beta firmware.
Is there a changelog somewhere for the boot loader?
Thanks!
EDIT: Since installing an SSD and booting from USB to that drive, I have run into the issue of timeouts on restart with the USB drive preventing boot.
I just switch off the Pi, then switch it back on, and it comes up fine.
Is that what the release notes for the boot loader are referring to?
Linuxrpi4-mainline kernel was upgraded again today. So the new kernel related packages has been pushed to the unstable branch when the mirrors sync.
No new activity involving the raspberrypi-bootloader packages as of this post.
linux-rpi4-mainline 5.10.7-1
linux-rpi4-mainline-headers 5.10.7-1
1 Like
These latest kernel/kernel-headers and rpi bootloader packages have been pushed to the unstable branch when the mirrors sync:
linux-rpi4-mainline 5.10.9-1
linux-rpi4-mainline-headers 5.10.9-1
linux-rpi4-rc 5.11.rc4-1
linux-rpi4-rc-headers 5.11.rc4-1
raspberrypi-bootloader 20210121-1
raspberrypi-bootloader-x 20210121-1
1 Like
0n0w1c
22 January 2021 02:47
290
rc and bootloader update were uneventful, thank you.
Edit: I then switch to mainline and it too went smoothly.
1 Like
So is 5.11-rc5. Today was my go to town day for groceries. I just got home.
The latest kernel/kernel-headers/bootloader packages has been pushed to the unstable branch when the mirrors sync.
linux-rpi4-mainline 5.10.10-1
linux-rpi4-mainline-headers 5.10.10-1
linux-rpi4-rc 5.11.rc5-1
linux-rpi4-rc-headers 5.11.rc5-1
raspberrypi-bootloader 20210125-1
raspberrypi-bootloader-x 20210125-1
1 Like
0n0w1c
27 January 2021 00:10
294
Update went smoothly, both kernels tested.
1 Like
Rip2
27 January 2021 02:09
295
PiOS update /lib/firmware/brcm files, which package manjaro concern?
dbeach
27 January 2021 02:46
296
An example for one file:
$ pacman -Qo /lib/firmware/brcm/brcmfmac4329-sdio.bin
/usr/lib/firmware/brcm/brcmfmac4329-sdio.bin is owned by linux-firmware 20201218.646f159-1
firmware-raspberrypi
This package has the latest pi firmware built from the RPi tree and is installed in /usr/lib/firmware/updates/brcm/ so the latest gets picked up first. The linux-firmware package has some but are not always the latest that the RPi folks have.
Wow! They did not let any grass grow from putting out 5.10.10. Will compile tomorrow when I get up. Getting late and I’m sleepy.
These latest kernel/kernel-headers/bootloader packages has been pushed to the unstable branch when the mirrors sync.
linux-rpi4-mainline 5.10.11-1
linux-rpi4-mainline-headers 5.10.11-1
raspberrypi-bootloader 20210128-1
raspberrypi-bootloader-x 20210128-1
2 Likes