sakaki- / bcmrpi3-kernel Goto Github PK

Automated weekly build of the default branch 64-bit bcmrpi3_defconfig Linux kernel for the Raspberry Pi 3 model B and B+

License: GNU General Public License v2.0

64-bit kernel bcmrpi3-kernel kernel-tarball rpi3 rpi3b rpi3b-plus raspberry-pi

bcmrpi3-kernel's Introduction

bcmrpi3-kernel

Automated build of the latest 64-bit bcmrpi3_defconfig Linux kernel for the Raspberry Pi 3 model B and B+, updated weekly.

Description

This project contains a weekly autobuild of the default branch (currently, rpi-5.4.y) of the official Raspberry Pi Linux source tree, for the 64-bit Raspberry Pi 3 Model B and B+.

NB: (8 June 2020) the transition from rpi-4.19.y to rpi-5.4.y has not yet happened upstream, but as it will do shortly, I have elected to pre-emptively migrate.

Builds are performed with the standard bcmrpi3_defconfig, with the only change being that the first 12 hex digits of the tip commit SHA1 hash are appended to CONFIG_LOCALVERSION (with a separating hyphen) before building.

Please note that as the purpose of this project is to provide a 'vanilla' build of the upstream bcmrpi3_defconfig, PRs requesting config changes will be rejected. Instead, please see the sister bcmrpi3-kernel-bis project, which has a weekly autobuild (with versions mirroring this one, using a tweaked bcmrpi3_defconfig), and where such PRs will be accepted for review.

A new build tarball is automatically created and uploaded as a release asset each week (unless the tip of the default branch is unchanged from the prior week, or an error occurs during the build process).

The default branch is used, as that is generally given most attention for e.g. VC4 backports.

As an (historical) example, on 1 June 2017, the default branch was rpi-4.9.y (NB, it is rpi-5.4.y now) and the latest commit was e5bd734340e6871e4e9ef5ff66e61197eb8ece30 (the short form of which is e5bd734340e6). The created release was 4.9.30.20170601, within which the kernel tarball was bcmrpi3-kernel-4.9.30.20170601.tar.xz, and the corresponding kernel release name was 4.9.30-v8-e5bd734340e6+.

Each kernel release tarball currently provides the following files:

/boot/kernel8.img (this is the bootable 64-bit kernel);
/boot/COPYING.linux (the kernel's license file);
/boot/config (the configuration used to build the kernel);
/boot/Module.symvers.xz (a table mapping exported symbols to provider, compressed);
/boot/System.map.xz (the kernel's symbol table, compressed);
/boot/bcm-2710-rpi-3-b.dtb, /boot/bcm-2710-rpi-3-b-plus.dtb and /boot/bcm-2837-rpi-3-b.dtb (and, from 5.4.69.20201006 onwards, /boot/bcm2710-rpi-cm3.dtb) (the device tree blobs);
/boot/overlays/... (the device tree blob overlays) (from 5.4.69.20201006);
/lib/modules/<kernel release name>/... (the module set for the kernel);
/lib/firmware/... (the kernel-built firmware, for < 4.14 only).

The /boot/bcm-2710-rpi-3-b-plus.dtb file is only included in more recent builds.

The /boot/Module.symvers.xz file is only included in more recent builds. The /boot/System.map.xz is supplied in compressed form only in recent builds.

The current kernel tarball may be downloaded from the link below (or via wget, or via the corresponding bcmrpi-kernel-bin ebuild, per the instructions following):

Variant	Version	Most Recent Image
Kernel, dtbs, modules and (kernel) firmware	5.4.69.20201006	bcmrpi3-kernel-5.4.69.20201006.tar.xz

The corresponding kernel configuration (derived via make bcmrpi3_defconfig) may be viewed here.

A list of all releases may be seen here. For an equivalent kernel autobuild for the RPi4B, please see here.

Installation

To deploy (assuming that your RPi3's micro SD-card's first partition is mounted as /boot, and you are already running a 64-bit RPi3 image, such as my gentoo-on-rpi3-64bit) simply download, untar into the root directory, and reboot:

pi64 ~ # cp /boot/kernel8.img{,.old}
pi64 ~ # wget -c https://github.com/sakaki-/bcmrpi3-kernel/releases/download/5.4.69.20201006/bcmrpi3-kernel-5.4.69.20201006.tar.xz
pi64 ~ # tar -xJf bcmrpi3-kernel-5.4.69.20201006.tar.xz -C /
pi64 ~ # sync && reboot

Alternatively, if you have my rpi3 overlay installed (it is pre-installed on the gentoo-on-rpi3-64bit image), you can simply emerge the bcmrpi3-kernel-bin package (a new ebuild is automatically created to mirror each release here). For example, to install the latest available version (and start using it):

pi64 ~ # emaint sync --repo rpi3
pi64 ~ # emerge -av bcmrpi3-kernel-bin
pi64 ~ # reboot

Or, to install a particular version (e.g.):

pi64 ~ # emaint sync --repo rpi3
pi64 ~ # emerge -av =bcmrpi3-kernel-bin-4.9.30.20170601
pi64 ~ # reboot

NB: these prebuilt kernels and ebuilds are provided as a convenience only. Use at your own risk! Given that the releases in this project are created automatically, there is no guarantee that any given kernel will boot correctly. A 64-bit kernel is necessary, but not sufficient, to boot the RPi3 in 64-bit mode; you also need the supporting firmware, configuration files, and userland software (see for example my gentoo-on-rpi3-64bit project, or NeddySeagoon's Raspberry Pi 3 64 bit Install page on the Gentoo wiki, for more information).

bcmrpi3-kernel's People

Contributors

Stargazers

Watchers

Forkers

openfans-community-offical danigy skulko genpi64

bcmrpi3-kernel's Issues

kernel BUG at arch/arm64/kernel/fpsimd.c:282! AND other issues

I'm making use of this kernel on Arch Linux ARM with the AUR package https://aur.archlinux.org/packages/linux-aarch64-raspberrypi-bin/ I've been seeing some strange messages in my dmesg output and I'm worried it could lead to data corruption. Does anyone know what it is and how it could be fixed if it's serious?

These messages appear when there is high I/O. Such as when I'm attempting to move data from one USB hard drive to another.

All of my devices are encrypted including the rootfs. I'm able to remotely decrypt it using a initram hook and dropbear ssh.

Following snippets of logs where the messages show.
https://gist.github.com/ShapeShifter499/df184265fbf0672140d396d89510d184
https://gist.github.com/ShapeShifter499/3af51b6c3d87c07e300110f81e162df8
https://gist.github.com/ShapeShifter499/8c43fca9b6404126c6971564d695be4b

Reuesting AppArmor settings to be compiled.

Last time you said you were planning on adding a -bis build including some extra options that would be useful. Can I ask that AppArmor be added to the regular build or the -bis build? This would be for security purposes.

CONFIG_SECURITY_APPARMOR=y
CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
CONFIG_DEFAULT_SECURITY_APPARMOR=y
CONFIG_AUDIT=y

Enable CONFIG_BCM2835_DEVGPIOMEM in config?

Hi!

Thanks for the kernel builds! I am using them with my ArchLinux ARM and wanted to use GPIO functionality, but can't do it without root. This is because CONFIG_BCM2835_DEVGPIOMEM config option is not set. Can you set it to the y or m please - it won't hurt anybody, but will make possible to use your kernel with GPIO devices. If not, I will need to build my own kernel :(

Preparations for 4.19.y?

Hi Sakaki. Firstly, thanks for this project. It's really great, and I have been using it on my arch sytem using the AUR package https://aur.archlinux.org/packages/linux-aarch64-raspberrypi-bin/

I was just wondering if you had done any preparation for the imminent migration by the Pi people to the 4.19.y branch of the linux kernel for the standard stable branch? According to their forums and a few posts in their GitHub issues, the switch is looking likely to occur in the next month or two. The problem is, I believe the switch could cause issues for 64-bit kernels on the Pi. I have been building and testing the standard 64-bit bcmrpi3_defconfig from the rpi-4.19.y branch, and I have had a lot of issues with not being able to reboot, and sometimes not being able to boot at all, with lots of kernel panics etc. Have you done any testing of the 4.19.y branch and experienced any issues? Will you hold this package on 4.14.y when Rpi switch, or will it automatically switch to 4.19.y once they make that the stable branch?

Requesting CONFIG_DM_CACHE=m and CONFIG_DM_CACHE_SMQ=m

I'm requesting these two modules because they are required for the 'sd-lvm2' and 'lvm2' mkinitcpio modules. Can you please add these to the kernel config and compile?

I'm trying to set up a full disk encryption on my Raspberry Pi 3B+ and I need these modules so I can setup a ssh init and decrypt remotely. This kernel is picked up by the AUR package here https://aur.archlinux.org/packages/linux-aarch64-raspberrypi-bin/

Where do I find the kernel headers for this build?

I was looking into building "cryptodev-linux" but that requires kernel headers, where would I find them for this particular build?

Unable to boot Rasperry Pi 3B+ with bcmrpi3-kernel-4.19.69.20190903

Hello all,

So I have been running Arch Linux ARM (the aarch64 version) for a long time on my raspberry pi 3B+. All was well with the world, until I updated the linux-aarch64-raspberrypi-bin package. The update went well, no error message. I went to reboot the RPI and ... nothing.
When I say nothing, what I mean is that the red led is ON, so power is good. The green (act) led flashes in a fixed pattern of 7 flashes, followed by a pause, then again 7 flashes. According to this lovely website, this seems to indicate that the kernel.img file was not found. If I plug a screen via HDMI it stays on the rainbow and nothing else appear, no messages no nothing.
I checked both file systems and SD card. Everything seem fine. So now I am a bit at a loss as to what I should do/try next? Can I simply copy a kernel image from a previous release, paste it in the /boot folder and call it a day? Or should I just re-install everything? Finally, am I the only one in a pickle here? Or are others experiencing the same issue?
Thank you very much in advance for any help you can provide.

Sincerely.

by the way I'm on Archlinuxarm on Raspberry pi 3B

Thanks in advance