So, to get the new configs, I’d just need to delete the two files (just before upgrading) the next time a linux_rpi4-mainline update becomes available? I’m guessing it won’t boot if I delete them now.
You have the defaults so no need. Since the old way removed the config files on every kernel install they got replaced with the default when the new kernel got installed because they were not present.
But yes if something in the future changes I will post to remove a config first so it can be upgraded with the new.
Could you set up the installer to create *.pacnew files where the originals have been altered? Kind of analogous to what grub does with /etc/default/grub when a new config is released.
Will deal with it if and when the situation arises.
New set of raspberry kernels available on GitHub - raspberrypi/linux: Kernel source tree for Raspberry Pi Foundation-provided kernel builds. Issues unrelated to the linux kernel should be posted on the community forum at https://www.raspberrypi.org/forum
- 5.10.31
- 5.11.15
- 5.12.0-rc8
Sounds like Linux 5.12 will be stable next Sunday Linux 5.12 Diverted From Release To Allow An Extra Week Of Testing - Phoronix
I know. They are being compiled as I type.
2 Likes
All pi4 kernels/kernel headers, bootloader, eeprom and raspberrypi-userland packages have been upgraded and pushed to the unstable branch when the mirrors sync.
The linux-rpi4-rc kernel still has configs to boot with UEFI.
The rpi-eeprom package has been switched over to pull from git. The only change is that the March image that was in “stable” is now been promoted to “critical”. The rpi-eeprom-git package has been removed from all branches.
The raspberrypi-userland-aarch64-git package had boardflags added for the pi 400 and the pi-cm4.
linux-rpi4 5.10.31-1
linux-rpi4-headers 5.10.31-1
linux-rpi4-mainline 5.11.15-1
linux-rpi4-mainline-headers 5.11.15-1
linux-rpi4-rc 5.12.rc8-1
linux-rpi4-rc-headers 5.12.rc8-1
raspberrypi-bootloader 20210419-1
raspberrypi-bootloader-x 20210419-1
raspberrypi-userland-aarch64-git r813.3fd8527-1
rpi-eeprom 20210419-1
2 Likes
Next week, the current RC kernel should go mainline. Will the EFI kernel settings also go to mainline or will they remain limited to the RC kernel?
And since there is no voting for RPi kernel updates, to comply with the desire for only issues and fixes to be posted in update threads, I’ll give a thumbs up when the update goes smoothly and I’ll comment only when I hit a snag.
Guess we can try both and see how it works out for you since it does not seem to affect the kernel with the config so far booting normally.
1 Like
Did a fresh install of manjaro recently and while the graphics driver problem persisted on the linux-rpi4-rc kernel, both linux-rpi4 and linux-rpi4-mainline work fine. I’m using mainline for now.
The latest linux-rpi4 & linux-rpi4-mainline kernel and the 2 latest raspberrypi-bootloader packages have been pushed to the unstable branch when the mirrors sync.
The linux-rpi4-mainline kernel is now version 5.12.0-1. The version 5.11 is history. Kernel 5.12.0-1 has UEFI boot modules enabled.
Latest raspberrypi-bootloader changes:
https://github.com/raspberrypi/firmware/commit/616dde8bc8a16dbd524e74ab84f3d3d5663a1641
linux-rpi4 5.10.32-1
linux-rpi4-headers 5.10.32-1
linux-rpi4-mainline 5.12.0-1
linux-rpi4-mainline-headers 5.12.0-1
raspberrypi-bootloader 20210427-1
raspberrypi-bootloader-x 20210427-1
2 Likes
The latest linux-rpi4 kernel/headers, raspberrypi-bootloader and rpi-eeprom packages has been pushed to the unstable branch when the mirrors sync.
The rpi-eeprom has upgraded to pieeprom-2021-04-29.bin in “critical” and also what appears to be an ethernet probing fix for the pi400.
[ray@pi4 ~]$ sudo rpi-eeprom-update
BOOTLOADER: up to date
CURRENT: Thu Apr 29 04:11:25 PM UTC 2021 (1619712685)
LATEST: Thu Apr 29 04:11:25 PM UTC 2021 (1619712685)
RELEASE: critical (/lib/firmware/raspberrypi/bootloader/critical)
Use raspi-config to change the release.
VL805_FW: Using bootloader EEPROM
VL805: up to date
CURRENT: 000138a1
LATEST: 000138a1
Latest files:
linux-rpi4 5.10.33-1
linux-rpi4-headers 5.10.33-1
raspberrypi-bootloader 20210430-1
raspberrypi-bootloader-x 20210430-1
rpi-eeprom 20210430-1
1 Like
plasma update to 5.21.5, wayland-session.
kms, youtube halt and no audio same issue.
fkms work.
I have given up on kms on the RPi4, it is beyond hope at this point.
but kms/sway is work.
i use kms on my rpi400.
i have a xfce4 & gnome 40 installs on usb drives.
my config.txt
# See /boot/overlays/README for all available options
arm_freq=2000
over_voltage=6
gpu_mem=24
initramfs initramfs-linux.img followkernel
kernel=kernel8.img
arm_64bit=1
disable_overscan=1
#enable sound
dtparam=audio=on
hdmi_drive=2
#enable vc4
dtoverlay=vc4-kms-v3d
max_framebuffers=2
disable_splash=1KMS has not worked with KDE Plasma since early on with 5.10 kernel. Now two full kernel versions later and still broken… I do not expect it will work.
Edit:
I tried the latest Plasma on kms and I still receive the same errors:
[ 138.458964] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
[ 138.458963] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_done timed out
These result in temporary system hangs rendering the system pretty much unusable, open a youtube video in a browser and you end up pulling the power to reboot.
Good news and I’ll keep my fingers crossed. Thanks for finding the link, I’ll keep an eye on it.
These latest rpi4 kernels/headers, bootloader and rpi-eeprom packages has been pushed to the unstable branch when the mirrors sync.
@chainofflowers both kernels now have CONFIG_CRYPTO_SERPENT=m
The rpi-eeprom package has some typo fixes in rpi-eeprom-update.
https://github.com/raspberrypi/rpi-eeprom/commit/f7402923bc2f5e0c4e9058eb15050dd1e2bd6c9c
linux-rpi4 5.10.35-1
linux-rpi4-headers 5.10.35-1
linux-rpi4-mainline 5.12.1-1
linux-rpi4-mainline-headers 5.12.1-1
raspberrypi-bootloader 20210507-1
raspberrypi-bootloader-x 20210507-1
rpi-eeprom 20210504-1