Raspberry Pi Kernel Compatibility Issue - Temporary Fix

Hi everyone!

We’ve been getting reports about problems running Raspberry Pi examples after recent kernel updates. We’re aware of this issue and actively working on a permanent solution.

Quick Fix: For now, the easiest workaround is to downgrade your kernel to version 6.12.20 or earlier (or any 6.6.x version). This should get everything working smoothly again.

How to Downgrade Your Raspberry Pi Kernel

Here’s a step-by-step guide to fix this:

# Step 1: Update your package lists first
sudo apt update

# Step 2: (Optional) Check what kernel versions are available
# This helps you confirm the exact version string
apt list -a raspberrypi-kernel raspberrypi-bootloader

# Step 3: Downgrade to kernel version 6.6.74
# This installs the stable version that works with our examples
sudo apt install --reinstall \
  raspberrypi-bootloader=1:6.6.74-1+rpt1 \
  raspberrypi-kernel=1:6.6.74-1+rpt1

# Step 4: Lock these packages to prevent automatic updates
# This stops the system from "helpfully" updating to the broken version
sudo apt-mark hold raspberrypi-bootloader raspberrypi-kernel

# Step 5: Restart your Pi to load the downgraded kernel
sudo reboot

After rebooting, your Raspberry Pi should be running the older, stable kernel and the examples should work properly again.

Alternative Option for Kernel 6.12.20:

If you prefer to use kernel 6.12.20 instead, you can replace step 3 with:

# For kernel 6.12.20 (adjust version string as needed)
sudo apt install --reinstall \
  raspberrypi-bootloader=1:6.12.20-1+rpt1 \
  raspberrypi-kernel=1:6.12.20-1+rpt1

Third option if reinstall doesn’t work , try the solution in here :

We’ll update everyone once we have a permanent fix. Thanks for your patience while we sort this out!

1 Like

I am getting error for using 6.12.20

mobilestack@raspberrypi:~ $ apt list -a raspberrypi-kernel raspberrypi-bootloader
Listing… Done
raspberrypi-bootloader/stable 1:1.20230405-1 arm64

raspberrypi-bootloader/stable 1:1.20230405-1 armhf

raspberrypi-kernel/stable 1:1.20230405-1 arm64

raspberrypi-kernel/stable 1:1.20230405-1 armhf

mobilestack@raspberrypi:~ $ # For kernel 6.12.20 (adjust version string as needed)
sudo apt install --reinstall
raspberrypi-bootloader=1:6.12.20-1+rpt1
raspberrypi-kernel=1:6.12.20-1+rpt1
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Package raspberrypi-kernel is a virtual package provided by:
raspberrypi-kernel:armhf 1:1.20230405-1 (= 1:1.20230405-1)
You should explicitly select one to install.

Package raspberrypi-bootloader is a virtual package provided by:
raspberrypi-bootloader:armhf 1:1.20230405-1 (= 1:1.20230405-1)
You should explicitly select one to install.

E: Version ‘1:6.12.20-1+rpt1’ for ‘raspberrypi-bootloader’ was not found
E: Version ‘1:6.12.20-1+rpt1’ for ‘raspberrypi-kernel’ was not found
mobilestack@raspberrypi:~ $ sudo apt install --reinstall
raspberrypi-bootloader=1:6.6.74-1+rpt1
raspberrypi-kernel=1:6.6.74-1+rpt1
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Package raspberrypi-kernel is a virtual package provided by:
raspberrypi-kernel:armhf 1:1.20230405-1 (= 1:1.20230405-1)
You should explicitly select one to install.

Package raspberrypi-bootloader is a virtual package provided by:
raspberrypi-bootloader:armhf 1:1.20230405-1 (= 1:1.20230405-1)
You should explicitly select one to install.

Hey @Praveen_Gupta try the steps from the 3rd option mentioned above. You can find the link above.

PCI driver is inconsistent - giving error code (1)

dkms: autoinstall for kernel: 6.12.20+rpt-rpi-2712.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.12.20+rpt-rpi-2712
Setting up linux-headers-6.12.20+rpt-common-rpi (1:6.12.20-1+rpt1~bpo12+1) …
Setting up linux-kbuild-6.12.20+rpt (1:6.12.20-1+rpt1~bpo12+1) …
Setting up hailort-pcie-driver (4.21.0) …

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

build-essential/stable,now 12.9 arm64 [installed]
Do you wish to use DKMS? [Y/n]:
Failed. Exited with status 1. See /var/log/hailort-pcie-driver.deb.log
dpkg: error processing package hailort-pcie-driver (–configure):
installed hailort-pcie-driver package post-installation script subprocess retur
ned error exit status 1
Setting up linux-headers-6.12.20+rpt-rpi-2712 (1:6.12.20-1+rpt1~bpo12+1) …
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.12.20+rpt-rpi-2712.
Sign command: /lib/modules/6.12.20+rpt-rpi-2712/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area…
make -j4 KERNELRELEASE=6.12.20+rpt-rpi-2712 -C /lib/modules/6.12.20+rpt-rpi-2712
/build M=/var/lib/dkms/hailo_pci/4.21.0/build/linux/pcie modules…
Signing module /var/lib/dkms/hailo_pci/4.21.0/build/./linux/pcie/hailo_pci.ko
Cleaning build area…
Forcing version override of hailo_pci

hailo_pci.ko.xz:
Running module version sanity check.

  • Original module
  • Installation
    • Installing to /lib/modules/6.12.20+rpt-rpi-2712/updates/dkms/
      depmod…
      dkms: autoinstall for kernel: 6.12.20+rpt-rpi-2712.
      Errors were encountered while processing:
      hailort-pcie-driver
      E: Sub-process /usr/bin/dpkg returned an error code (1)
      mobilestack@raspberrypi:~/hailo-rpi5-examples $

Hey @Praveen_Gupta,

Welcome to the Hailo Community!

It looks like you’re using Driver 4.21, which hasn’t been officially released for Raspberry Pi yet. We recommend sticking with the officially supported version: hailo-all, provided for Raspberry Pi compatibility.

Yes. But, then, there are instruction to perform sudo apt update; sudo apt upgrade

and this cause problems.

Looks like, different instructions for rp5-examples and Frigate installations is making the whole effort inconsistent. Again, I am not trying to be negative. Just, identifying issues that newbie face as they try RP5 with Hailo8L AI HAT.

RP5 example installation work upto “python basic_pipelines/detection.py” and then nothing else for segmentation / Pose detection works.

As one do Frigate installation after RP5 (upto detection), one gets into authentication issue and there are no clean instructions of how to overcome authentication and use RP5 Camera Module-3 with Frigate.

Thanks
-Praveen

FWIW, I managed to fix this by running rpi-update