Raspberry Pi Kernels (2.0)

Linux joel-mantest 6.6.6-1-MANJARO-RPI5 #1 SMP PREEMPT Tue Dec 12 12:13:18 UTC 2023 aarch64 GNU/Linux

inxi
CPU: quad core Model N/A (-MCP-) speed/min/max: 1000/1000/2400 MHz
Kernel: 6.6.6-1-MANJARO-RPI5 aarch64 Up: 9m Mem: 1.77/7.86 GiB (22.5%)
Storage: 59.48 GiB (21.8% used) Procs: 220 Shell: Bash inxi: 3.3.31

Update

[2023-12-13T10:39:38+1000] [ALPM] installed linux-rpi5-mainline-headers (6.6.6-1)
[2023-12-13T10:39:38+1000] [ALPM] transaction completed
[2023-12-13T10:39:39+1000] [ALPM] running '30-systemd-update.hook'...
[2023-12-13T10:39:39+1000] [ALPM] running '60-depmod.hook'...
[2023-12-13T10:39:40+1000] [ALPM] running '60-linux-rpi5-mainline.hook'...
[2023-12-13T10:39:42+1000] [ALPM] running '90-linux-rpi5-mainline.hook'...
[2023-12-13T10:39:42+1000] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-rpi5-mainline.preset: 'default'
[2023-12-13T10:39:42+1000] [ALPM-SCRIPTLET] ==> Using configuration file: '/etc/mkinitcpio.conf'
[2023-12-13T10:39:42+1000] [ALPM-SCRIPTLET]   -> -k 6.6.6-1-MANJARO-RPI5 -c /etc/mkinitcpio.conf -g /boot/initramfs_2712
[2023-12-13T10:39:42+1000] [ALPM-SCRIPTLET] ==> Starting build: '6.6.6-1-MANJARO-RPI5'
[2023-12-13T10:39:42+1000] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2023-12-13T10:39:42+1000] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2023-12-13T10:39:43+1000] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2023-12-13T10:39:43+1000] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2023-12-13T10:39:43+1000] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
[2023-12-13T10:39:43+1000] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2023-12-13T10:39:43+1000] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2023-12-13T10:39:43+1000] [ALPM-SCRIPTLET] loadkeys: Unable to open file: au: No such file or directory
[2023-12-13T10:39:44+1000] [ALPM-SCRIPTLET]   -> Running build hook: [consolefont]
[2023-12-13T10:39:44+1000] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2023-12-13T10:39:44+1000] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2023-12-13T10:39:44+1000] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2023-12-13T10:39:44+1000] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2023-12-13T10:39:45+1000] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2023-12-13T10:39:45+1000] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: '/boot/initramfs_2712'
[2023-12-13T10:39:46+1000] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
[ray@jellyfin ~]$ inxi
CPU: quad core Model N/A (-MCP-) speed/min/max: 1000/1000/2800 MHz
Kernel: 6.6.6-1-MANJARO-RPI5 aarch64 Up: 29m Mem: 2.23/7.86 GiB (28.4%)
Storage: 111.8 GiB (79.6% used) Procs: 242 Shell: Bash inxi: 3.3.31

These kernel / device related packages has been pushed to the unstable branch when the mirrors sync.

The rpi5-eeprom default image has been updated. It requires the latest kernels, rpi-overlays and firmware that only lives in the unstable branch. I have also upgraded the rpi5-rc kernel so if one wants to bounce back and forth testing the kernels on the unstable branch.

https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware-2712/release-notes.md

Here is the rpi5-eeprom flash procedure. Commands issued is in bold on the command lines:

Pi 5 eeprom upgrade

CHECK IF UPGRADE IS NEEDED:

[ray@jellyfin packages]$ sudo rpi-eeprom-update
*** UPDATE AVAILABLE ***
BOOTLOADER: update available
CURRENT: Mon Oct 30 04:45:10 PM UTC 2023 (1698684310)
LATEST: Wed Dec 6 06:29:25 PM UTC 2023 (1701887365)
RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)

FLASH EEPROM:

[ray@jellyfin packages]$ sudo rpi-eeprom-update -a
*** PREPARING EEPROM UPDATES ***

BOOTLOADER: update available
CURRENT: Mon Oct 30 04:45:10 PM UTC 2023 (1698684310)
LATEST: Wed Dec 6 06:29:25 PM UTC 2023 (1701887365)
RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)
CURRENT: Mon Oct 30 04:45:10 PM UTC 2023 (1698684310)
UPDATE: Wed Dec 6 06:29:25 PM UTC 2023 (1701887365)
BOOTFS: /boot
‘/tmp/tmp.dHxnoXD4kN’ → ‘/boot/pieeprom.upd’
Copying recovery.bin to /boot for EEPROM update

EEPROM updates pending. Please reboot to apply the update.
To cancel a pending update run “sudo rpi-eeprom-update -r”.

REBOOT TO FINISH FLASH:

[ray@jellyfin packages]$ sudo reboot

AFTER REBOOT:

Remove temp files from /boot:
[ray@jellyfin ~]$ sudo rpi-eeprom-update -r
Removing temporary files from previous EEPROM update

VERIFY NEW FLASH:

[ray@jellyfin ~]$ sudo rpi-eeprom-update
BOOTLOADER: up to date
CURRENT: Wed Dec 6 06:29:25 PM UTC 2023 (1701887365)
LATEST: Wed Dec 6 06:29:25 PM UTC 2023 (1701887365)
RELEASE: default (/lib/firmware/raspberrypi/bootloader/default)
[ray@jellyfin ~]$

linux-rpi5-rc 6.7.rc5-1
linux-rpi5-rc-headers 6.7.rc5-1
rpi5-eeprom 20231212-1

Added 12-14-2023:

These rpi new kernel packages has been pushed to the unstable branch when the mirrors sync.

linux-rpi4 6.1.68-1
linux-rpi4-headers 6.1.68-1
linux-rpi5 6.1.68-1
linux-rpi5-headers 6.1.68-1
rpi-overlays 6.1.68-1

Additional:

The finally got the 6.6.7 kernels fixed where they would compile.

linux-rpi4-mainline 6.6.7-1
linux-rpi4-mainline-headers 6.6.7-1
linux-rpi5-mainline 6.6.7-1
linux-rpi5-mainline-headers 6.6.7-1

rpi-overlays updated, firefox can not start only safety mode?

Firefox ok here.

Added:

I just checked the firmware git and the overlays has not changed since kernel 6.1.66 but they have not updated the kernels their either. I only built the package because of a ton of changes was made in today’s kernel and they are slow sometimes updating their firmware git for me to make sure. I built the overlays that was in the latest kernel (which they do and move to their firmware git). So the rpi-overlays package does not seemed to have changed. Must be some other issue there maybe your mesa version?

@Rip2 I have been testing mesa-23.3.1 all day today. Here it is if you want to give it a go.

mesa-23.3.1

ok, update mesa, done & thanks.
but don’t know why, only thing is update rpi-overlays?

I believe I am going to push 23.3.1 to unstable. I have had issues here with 23.3.0. Mine was a little bit different I was using firefox but all of a sudden I lost all of my desktop / taskbar icons and clicking on things gave me an error. I had to cut the power to reboot.

What is the situation for Why to run 16k page size for RPi5? - Raspberry Pi Forums

In Pios Pi5 by default use kernel_2712.img (16k) and will use kernel8.img (4k) with the addition of kernel=kernel8.img to config.txt if you have some issue : Pi5 16K PageSize Kernel Incompatible Software · Issue #107 · raspberrypi/bookworm-feedback · GitHub

Arch has release a second kernel Arch Linux ARM • View topic - New kernel package for RPi5: linux-rpi-16k

Ever since the pi5 came out RPi has had the pi5 bcm2712_defconfig configured with 16k pages and the bcm2711_defconfig using 4k pages. The pi5 can boot the pi4 kernel if you specify kernel=kernel8.img in config.txt but the pi4 can not use the pi5 kernel. Arch started out using the pi4 kernel for the pi5 kernel to boot. I am guessing that they did not realize that the bcm2712_defconfig was added. I have seen at certain situations RPi was having users test the pi5 using the pi4 kernel when they ran into some problems.

Since the pi5 came out RPi has changed each device’s firmware to use the correct kernel and initramfs combination automatically when booting when no kernel= is specified and auto_initramfs=1. This is because their image boots several devices using one image. This is also the same for our new DEV images. We do not have these new images yet on the Manjaro Downloads page currently.

https://github.com/manjaro-arm/rpi4-images/releases

I have all new kernel installs modifying the config.txt if needed while booted up on their existing old device (which requires latest firmware also) removing kernel=kernel8.img and replacing initramfs initramfs-linux.img followkernel with auto_initramfs=1 so all one has to do is install one of the linux-rpi5* kernels in their existing image then use it in their new pi5 and have it work right.

The latest -rc kernels has been pushed to the unstable branch when the mirrors sync.

linux-rpi4-rc 6.7.rc6-1
linux-rpi4-rc-headers 6.7.rc6-1
linux-rpi5-rc 6.7.rc6-1
linux-rpi5-rc-headers 6.7.rc6-1

Arch had mkinitcpio rebuild.

Really? People have been complaining about it for ages. I wonder which grump they fixed. Have you tried it yet?

No, not in Alarm repos.

They might have fixed something else then.

I pushed an updated raspberrypi-utils package to unstable. They merged and updated an old hats repo.

The eeptools project replaces eepromutils in the old hats repo. It
supports the HAT+ standard and old V1 HATs. Tools for creating and managing EEPROMs for HAT+ and HAT board.

raspberrypi-utils 20231219-1

Added 12-21-2023:

These kernel packages has been upgraded and pushed to the unstable branch when the mirrors sync.

linux-rpi4 6.1.69-1
linux-rpi4-headers 6.1.69-1
linux-rpi4-mainline 6.6.8-1
linux-rpi4-mainline-headers 6.6.8-1
linux-rpi5 6.1.69-1
linux-rpi5-headers 6.1.69-1
linux-rpi5-mainline 6.6.8-1
linux-rpi5-mainline-headers 6.6.8-1
rpi-overlays 6.1.69-1

Added 12-22-2023:

raspinfo: Add some audio info to debug log

https://github.com/raspberrypi/utils/commit/2cc103f4531a005cadaa8a9d09d6c85523c166bb

raspberrypi-utils 20231221-1

update mkinitcpio, warning message remained :rofl:

And so the saga continues since November 17th. 5 pages now on their forums to no avail.

https://archlinuxarm.org/forum/viewtopic.php?f=15&t=16672

Good afternoon! I installed KDE Plasma on Raspberry Pi 4 - Manjaro and fell in love with this OS. But unfortunately for my needs, I need a real-time kernel on my OS.
I need it for a CNC program - Linux CNC. I am not very familiar with Linux and would like to ask for your help. How can I install a real-time kernel. Perhaps instructions on how to assemble it?
I have already tried to collect one instruction from the Internet, but I got a black screen when downloading. I also did not find a ready-made core and a topic on the forum where this would be discussed.
I will be glad of any help.

Wonder if this will help any.

http://comfilewiki.co.kr/en/doku.php?id=comfilepi:compile_a_real-time_kernel:index

@Kostya I found another link. I compiled both links for my pi5 and I have a better feeling with this link.

https://jaybrockway.us/computer-science/raspberry-pi-kernel-real-time-build/

1 Like

boot from USB stick fine, but very slow(read ext4 root-files).
kernel or eeprom issue?

Everytime I have put an os on a usb stick it never performed as well as a sdcard.