RPi 7.0 kernels

ARM Installation
1

Been testing the RPi 7.0.3 kernel after reading about it’s improvements and am impressed with the memory improvements. Things load better than 6.12 or 6.18 here on my pi4. I can’t test with the pi5 as it died a while back.

Here are the kernel packages for the RPi’s I built if anyone wants to test. I built them from RPi’s 7.0.y tree using their default defconfig’s and added in arch-arm’s modules they add. They are built on my x86 because I can do it in 10 minutes instead of hours on my pi4. One caveat of doing this is if one builds any out of kernel modules they want work because they need to be built with the same toolchain as the kernel. Hardly any one does this though but I am also including the PKGBUILD’s if someone has the need to build their own with the local toolchain for the out of tree modules.

Install with “sudo pacman -U”.

linux-rpi kernel:

https://drive.google.com/file/d/1jdKfxByg0r3aImY7rVhvHqaJMB0Cy0na/view?usp=sharing

linux-rpi-16k for pi5’s:

https://drive.google.com/file/d/1Pm16QSgg0A07HqXY_NP-6TjyfO4_G0Nc/view?usp=sharing

You can go back at any time by installing your previous kernel packages in the repo.

2

Thanks for sharing. I will definitely check it out.

Pudge

3

Giving it a try right now.

Is there something we the community could do?

4

Runs without problem on my Raspberry CM5 16GB RAM Lite + Wifi, inside an Argon One Up laptop shell, with the caveat you mentionned:

…as you predicted, this obviously causes DKMS to complain when trying to rebuild the out-of-kernel community drivers for the One-Up’s battery.

Of other notice, this boot error message is new to 7.0.x:

May 01 12:48:08 archlinux kernel: sdhci-brcmstb 1001100000.mmc: error -EINVAL: invalid resource (null)

I am not expert on RPi hardware, but:

  • Quick web search seems to point that this is the MMC driver?
  • A quick check in the boot logs shows that address belongs to mmc1?
  • Also from the boot logs mmc1 is where the wireless chip is attached?

Wifi, Bluetooth, and SD Card seems all to be working.

5

Thanks for testing on your pi5. Here a new kernel with my attempt to merge the files in the dkms git into the kernel build source tree. I went with my best guess on some unknowns due to not having a pi5 to test on. Probably should temporary disable the dkms trying to build to test the intree module.

https://drive.google.com/file/d/1BsaF9gjFF51DtYv1d3I7WsrPLfSDtuMk/view?usp=sharing

[ray@rpi Desktop]$ modinfo ./oneUpPower.ko.xz
filename: /home/ray/Desktop/./oneUpPower.ko.xz
license: GPL
author: Jeff Curless jeff@thecurlesses.com
description: Power supply driver for Argon40 1UP
alias: of:NTCargon40,oneup-batteryC*
alias: of:NTCargon40,oneup-battery
alias: i2c:oneup-battery
depends:
intree: Y
name: oneUpPower
vermagic: 7.0.3-1-rpi-16k SMP preempt mod_unload aarch64
parm: soc_shutdown:Shutdown system when the battery state of charge is lower than this value. (soc_shutdown)

You should also have the newly built /boot/overlays/argon-oneup-battery.dtbo after the new kernel is installed.

6

Thanks for having added the battery driver in.
I’ll be testing more (now that I don’t risk running out of battery unnoticed).

Do you have any tips how we could investigate and double check the sdhci-brcmstb error message I mentionned above?

7

No clue. My gut feeling is to ignore it. In the past with code changes with ENVAL errors they just remove the code to evaluate. I do not see that on my pi4.

8

Running it today the whole day at a scientific workshop. Worked without any noticeable problem.

You plan to release it on a pacman repository soon?
(Will you still be including the battery driver + dtbo with it?)

9

I am very happy with it also after several days of testing. RPi stopped supporting 6.12 and arch-arm only does 6.18 for the pi’s which I do not care for. I do not have access to any repo anymore so I will continue to put it in my googledrive folder each time RPi updates their kernel tree. I have a patch that adds the battery support to the kernel tree before it compiles so it will always be there as long as it will patch and compile. At some point that guy my have to upgrade his battery git as kernels progress if the patch stops working.

Look each week for kernel upgrades in that folder. Rpi usually upgrades their tree right after kernel.org does.