6.3-rc network fail again.
Odd, it includes the wifi fix the other kernels have: wifi: cfg80211: Partial revert "wifi: cfg80211: Fix use after free fo… · raspberrypi/linux@79d1ed5 · GitHub.
The kernel version was not updated to 6.2.7 but there are some new commits the branch.
now it’s done with the 6.2.7 !
I have some errors when installing v6.2.8:
xzcat : (stdin): Les données compressées sont corrompues
gzip: stdin: invalid compressed data–format violated
od: ‘/boot/vmlinuz-': Aucun fichier ou dossier de ce type
od: '/boot/vmlinuz-’: Aucun fichier ou dossier de ce type
od: ‘/boot/vmlinuz-': Aucun fichier ou dossier de ce type
od: '/boot/vmlinuz-’: Aucun fichier ou dossier de ce type
od: ‘/boot/vmlinuz-': Aucun fichier ou dossier de ce type
od: '/boot/vmlinuz-’: Aucun fichier ou dossier de ce type
cat: '/boot/vmlinuz-': Aucun fichier ou dossier de ce type
gzip: /boot/vmlinuz-.gz: No such file or directory
==> WARNING: Could not find kernel image for version 6.2.8-1-MANJARO-ARM-RPI
We discussed that starting here:
I guess nothing for now. It does not seem to bother anything. It is a Warning though not an error.
mkinitcpio update, fixed.
1 Like
The RPI team has updated all kernel branches:
6.1.23,6.2.10 and 6.3-rc6 are available !
edit : thanks for the releases !
2 Likes
Here we go: the new batch of the week!
6.1.24,6.2.11 and 6.3.0-rc7 are available !
1 Like
Thanks for bird dogging. 2 kernels built and 3rd one is compiling. Will push when all tested. I did push the new code package this mourning.
ADDED:
The latest RPi kernel packages have been built and pushed to the unstable branch when the mirrors sync:
linux-rpi4 6.1.24-1
linux-rpi4-headers 6.1.24-1
linux-rpi4-mainline 6.2.11-1
linux-rpi4-mainline-headers 6.2.11-1
linux-rpi4-rc 6.3.rc7-1
linux-rpi4-rc-headers 6.3.rc7-1
1 Like
A new week and a new batch of available kernels:
6.1.25,6.2.12 and 6.3.0 !!
UPDATED 05-30-23:
The latest RPi kernel packages has been pushed to the unstable branch when the mirrors sync. The linux-rpi kernel packages may be the last of these to show up in the mirrors. I had to wait a few hours for RPi to upgrade their 6.1.y kernel tree.
linux-rpi4 6.1.31-1
linux-rpi4-headers 6.1.31-1
linux-rpi4-mainline 6.3.4-1
linux-rpi4-mainline-headers 6.3.4-1
linux-rpi4-rc 6.4.rc4-1
linux-rpi4-rc-headers 6.4.rc4-1
2 Likes
6.3.5 is ready^^
Wow! They are on a roll today. @Rip2 Packages are built and being pushed to the unstable branch.
linux-rpi4-mainline 6.3.5-1
linux-rpi4-mainline-headers 6.3.5-1
1 Like
I have a question. I saw today a pull request requesting enabling PSI to make waydroid work on the RPi. I have had this enabled for over a year when we were testing OOMD. At that time OOMD would fail but it seems to be working now. Also around about that time waydroid would not work on the RPi.
Since I have been out of the picture with my heart attack for several months has anyone been using waydroid on their KDE wayland install’s?
Theses need to be added to cmdline.txt for PSI to work:
cgroup_enable=memory psi=1
systemd-oomd.service:
● systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer
Loaded: loaded (/usr/lib/systemd/system/systemd-oomd.service; enabled; preset: disabled)
Active: active (running) since Mon 2023-05-08 20:29:46 CDT; 3 weeks 3 days ago
TriggeredBy: ● systemd-oomd.socket
Docs: man:systemd-oomd.service(8)
Main PID: 332 (systemd-oomd)
Status: "Processing requests..."
Tasks: 1 (limit: 3919)
Memory: 1.7M (min: 64.0M low: 64.0M)
CPU: 234ms
CGroup: /system.slice/systemd-oomd.service
└─332 /usr/lib/systemd/systemd-oomd
Update 6-12-23:
I pushed the latest linux-rpi4-rc kernel packages this mourning to the unstable branch when the mirrors sync.
linux-rpi4-rc 6.4.rc6-1
linux-rpi4-rc-headers 6.4.rc6-1
Update 6-16-23:
I pushed the latest linux-rpi4 / linux-rpi4-mainline kernel packages this mourning to the unstable branch when the mirrors sync.
linux-rpi4 6.1.34-1
linux-rpi4-headers 6.1.34-1
linux-rpi4-mainline 6.3.8-1
linux-rpi4-mainline-headers 6.3.8-1
I have spent this week going through the 3 kernel config’s removing @115 lines of bloat. I have been meaning to do this last year before my heart attack but never got around to it. The kernels are now leaner and seems to boot faster now.
[ray@jellyfin ~]$ systemd-analyze
Startup finished in 2.827s (kernel) + 12.578s (userspace) = 15.405s
graphical.target reached after 12.578s in userspace.
I’m using 6.3.8 and I don’t have the same timings:
Startup finished in 4.763s (kernel) + 12.825s (userspace) = 17.588s
It’s almost the double your kernel outcome…
Guessing you are booting on a ssd also. The only thing I can think of is I have the bootsplash stuff disabled here.