You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you are starting with a fresh image the repositories are empty to save space. So sync the genpi64 repository with the command: emaint -r genpi64 sync
after making the edit above.
If you have already synced the repositories I think it is necessary to delete everything under /var/db/repos/genpi64 and use the command above to resync the repository based on the rpi5-kernel branch.
create dist-kernel-6.1.63.ebuild by copying and renaming the latest version
Create the manifest for the 6.1.63 kernel:
ebuild raspberrypi-kernel-6.1.63.ebuild manifest
Create /etc/portage/package.unmask directory
Create a file in the above directory containing the line below to unmask the virtual file
=virtual/dist-kernel-6.1.63
Create a file in /etc/portage/package.keywords containing the lines below to unmask the updated kernel
sys-kernel/raspberrypi-kernel ~arm64
virtual/dist-kernel-6.1.63 ~arm64
These steps should now allow you to emerge the 6.1.63 kernel
emerge -avu —-ignore-default-opts sys-kernel/raspberrypi-kernel
A few hours later you should have the 6.1.63 kernel installed
The edit the /boot/config.txt file and add the following lines
[pi5]
kernel=kernel8-p4.img
dtoverlay=vc4-kms-v3d-pi5
max_framebuffers=2
Expected behavior
Updated image should boot on a RPi 5
The text was updated successfully, but these errors were encountered:
create dist-kernel-6.1.63.ebuild by copying and renaming the latest version
Create the manifest for the 6.1.63 kernel: ebuild raspberrypi-kernel-6.1.63.ebuild manifest
In this first line is dist-kernel-6.1.63 supposed to be raspberrypi-kernel-6.1.63 ?
That line is correct but I missed out an important prior step which is to enable the rpi5-branch of the genpi64 overlay in order to make the raspberrypi-kernel-6.1.63 ebuild available. I’ve updated the instructions about to add the necessary steps.
Describe the bug
Below is an outline of the steps required to enable the GenPi64 image to boot on a Raspberry Pi 5.
To Reproduce
Steps to reproduce the behavior:
Mount a current GenPi64 image as chroot, also mount the /boot partition. Enter the chroot.
/etc/portage/repos.conf/genpi64.conf
and change the line:to read:
emaint -r genpi64 sync
after making the edit above.
If you have already synced the repositories I think it is necessary to delete everything under
/var/db/repos/genpi64
and use the command above to resync the repository based on the rpi5-kernel branch.ebuild raspberrypi-kernel-6.1.63.ebuild manifest
=virtual/dist-kernel-6.1.63
sys-kernel/raspberrypi-kernel ~arm64
virtual/dist-kernel-6.1.63 ~arm64
emerge -avu —-ignore-default-opts sys-kernel/raspberrypi-kernel
A few hours later you should have the 6.1.63 kernel installed
[pi5]
kernel=kernel8-p4.img
dtoverlay=vc4-kms-v3d-pi5
max_framebuffers=2
Expected behavior
Updated image should boot on a RPi 5
The text was updated successfully, but these errors were encountered: