WARNING still show up.
What warning. What does it say.
WARNING: errors were encountered during the build. The image may not be complete.
They took out KMS hook but added MODULES=(pcie_brcmstb) which is builtin our kernel. Comment the line MODULES=(pcie_brcmstb) in /etc/mkinitcpio.conf and reinstall linux-rpi4 and see what that does. pcie_brcmstb is needed to boot on a usb drive so RPi and us have it builtin as default but arch-arm has it as a module so they have to load it via the initramfs.
MODULES=(vc4) only.
Your /etc/mkinitcpio.conf did not get overwritten like mine for some reason. See if there is a newer .pacsave or .pacnew
update mkinitcpio-37.1 then kernel rebuild, but mkinitcpio.conf didn’t update.
I messed with it some more and now I am getting what you are. consolefont and KMS hook and all extra modules still need to be removed. I am going to build a new package for you to test. Give me a few minutes.
Uggg. Their latest PKGBUILD will not build.
UPDATED:
ARCH-ARM’s mkinitcpio package build has a patch that enables a check for arch-arm specific file names which results in an error. We have the same naming scheme as RPi so the kernels are automatically detected by each board’s firmware. They also seem to be booting the pi5 with the pi4 kernel config. There is a small difference with modules. That is the reason for RPi’s bcm2712_defconfig in their kernel tree is to generate it’s own config.
I decided to modify their mkinitcpio package’s end result to remove the offensive modules/hooks with the rpi-post-install package:
# Edit mkinitcpio.conf
echo "Editing mkinitcpio.conf..."
- sed -i s/"MODULES=()"/"MODULES=(vc4)"/g /etc/mkinitcpio.conf
+ sed -i 's/kms //' /etc/mkinitcpio.conf
+ sed -i 's/pcie_brcmstb//' /etc/mkinitcpio.conf
+ sed -i 's/vc4//' /etc/mkinitcpio.conf
+ sed -i 's/consolefont //' /etc/mkinitcpio.conf
+
So @Rip2 or any one else that lives on the unstable branch with a pi device wants to test this before I push it to the repo then please do. After installing this package reinstall your current kernel. Also reboot to see if the spinning circle still works.
rpi-overlays package upgraded and pushed to the unstable branch when the mirrors sync.
rpi-overlays 6.1.65-1
Added 12-08-2023:
These latest kernel packages has been pushed to the unstable branch when the mirrors sync.
I did not realize until the other day that RPi’s defconfig’s had BTRFS loading as a module. Starting with these kernels I now have BTRFS built into the kernel.
modinfo btrfs
[ray@jellyfin ~]$ modinfo btrfs
name: btrfs
filename: (builtin)
softdep: pre: blake2b-256
softdep: pre: sha256
softdep: pre: xxhash64
softdep: pre: crc32c
license: GPL
file: fs/btrfs/btrfs
alias: devname:btrfs-control
alias: char-major-10-234
alias: fs-btrfs
linux-rpi4 6.1.66-1
linux-rpi4-headers 6.1.66-1
linux-rpi4-mainline 6.6.5-1
linux-rpi4-mainline-headers 6.6.5-1
linux-rpi5 6.1.66-1
linux-rpi5-headers 6.1.66-1
Added 12-11-2023:
The latest linux-rpi4-rc kernel packages pushed to the unstable branch when the mirrors sync.
linux-rpi4-rc 6.7.rc5-1
linux-rpi4-rc-headers 6.7.rc5-1
I won’t be able to rebuild it until I get back from town grocery shopping.
https://lore.kernel.org/stable/fbd66e83-4aa4-4d48-972a-e41d4ec905f9@manjaro.org/T/#top
Here is the new linux-rpi4-mainline kernel with the WiFi Regression fix and updated rpi-overlays package. I am still waiting on RPi to upgrade to 6.1.67 with it’s fix. Packages pushed to the unstable branch when the mirrors sync.
linux-rpi4-mainline 6.6.6-1
linux-rpi4-mainline-headers 6.6.6-1
rpi-overlays 6.1.66-1
666 looks like lucky number ![]()
RPi started a thread asking for testers on the 6.6.y tree as they are starting to work on moving the 6.1 kernel to the new 6.6 LTS kernel. There are some interesting changes they mentioned in the thread involving the 6.6 kernel.
https://forums.raspberrypi.com/viewtopic.php?p=2166243&hilit=next+lts+kernel#p2166243
I have pushed new linux-rpi5-mainline kernel packages to the unstable branch so they can now be tested as well with the linux-rpi4-mainline kernel.
linux-rpi5-mainline 6.6.6-1
linux-rpi5-mainline-headers 6.6.6-1
I can help with rpi4 if that is of interest, I have a headless on unstable branch.
I sadly do not own a rpi5.
Thanks. The more people who test the faster they can get the bugs worked out. I received my pi5 yesterday and I love it!
By the way did you catch that I moved the BTRFS to the kernel instead of loading as modules in all of the last kernels in unstable branch.
I did not, but my btrfs is on stable, this is ext4 on unstable.
I was going to update it before starting to look for the 66 version (if you added that, you only mention rpi5) but got this:
[2023-12-12T16:23:20+0100] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-rpi4.preset: 'default'
[2023-12-12T16:23:20+0100] [ALPM-SCRIPTLET] ==> Using configuration file: '/etc/mkinitcpio.conf'
[2023-12-12T16:23:20+0100] [ALPM-SCRIPTLET] -> -k 6.1.66-1-MANJARO-RPI4 -c /etc/mkinitcpio.conf -g /boot/initramfs8
[2023-12-12T16:23:34+0100] [ALPM-SCRIPTLET] ==> Starting build: '6.1.66-1-MANJARO-RPI4'
[2023-12-12T16:23:35+0100] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2023-12-12T16:23:40+0100] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2023-12-12T16:23:42+0100] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2023-12-12T16:23:44+0100] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2023-12-12T16:23:44+0100] [ALPM-SCRIPTLET] -> Running build hook: [kms]
[2023-12-12T16:23:45+0100] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2023-12-12T16:23:46+0100] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2023-12-12T16:23:46+0100] [ALPM-SCRIPTLET] -> Running build hook: [consolefont]
[2023-12-12T16:23:47+0100] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2023-12-12T16:23:47+0100] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2023-12-12T16:23:51+0100] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2023-12-12T16:23:52+0100] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2023-12-12T16:23:56+0100] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2023-12-12T16:23:57+0100] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: '/boot/initramfs8'
[2023-12-12T16:24:01+0100] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
[2023-12-12T16:24:11+0100] [ALPM] running '90-mkinitcpio-install.hook'...
[2023-12-12T16:24:12+0100] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-rpi4.preset: 'default'
[2023-12-12T16:24:12+0100] [ALPM-SCRIPTLET] ==> Using configuration file: '/etc/mkinitcpio.conf'
[2023-12-12T16:24:12+0100] [ALPM-SCRIPTLET] -> -k 6.1.66-1-MANJARO-RPI4 -c /etc/mkinitcpio.conf -g /boot/initramfs8
[2023-12-12T16:24:12+0100] [ALPM-SCRIPTLET] ==> Starting build: '6.1.66-1-MANJARO-RPI4'
[2023-12-12T16:24:12+0100] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2023-12-12T16:24:13+0100] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2023-12-12T16:24:14+0100] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2023-12-12T16:24:15+0100] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2023-12-12T16:24:15+0100] [ALPM-SCRIPTLET] -> Running build hook: [kms]
[2023-12-12T16:24:16+0100] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2023-12-12T16:24:16+0100] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2023-12-12T16:24:17+0100] [ALPM-SCRIPTLET] -> Running build hook: [consolefont]
[2023-12-12T16:24:17+0100] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2023-12-12T16:24:17+0100] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2023-12-12T16:24:19+0100] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2023-12-12T16:24:19+0100] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2023-12-12T16:24:20+0100] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2023-12-12T16:24:20+0100] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: '/boot/initramfs8'
[2023-12-12T16:24:24+0100] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
Doesn’t really tell me WHAT went wrong. I’ll reboot it now and find out if it worked anyway.
And the logs call it a warning, my tty showed it as an Error.
So will you throw up linux-rpi4-mainline or should I just install the rpi5 ones and hope for the best? (in the past the rpi5 kernel stuff was included in the update, not the case any more)
Edit
Rebooted just fine.
I just wait for your input wether you want me to use the rpi5 stuff or not.
It has been in unstable since last night (6.6.6-1). Your pi4 will bomb out with the pi5 kernel. It can’t handle 16k pages.
It has been that way for a couple of weeks. Upstream arch-arm has to fix their last mkinitcpio package upgrade. People have been complaining on their forums but they have not fixed it yet. It does not seem to bother anything but not pretty to look at. It can be stopped in a couple of ways. We have discussed it here also.
sudo pacinstall linux-rpi4-mainline linux-rpi4-mainline-headers
resolving dependencies...
looking for conflicting packages...
:: linux-rpi4-mainline and linux-rpi4 are in conflict (kernel26). Remove linux-rpi4? [y/N] y
:: linux-rpi4-mainline-headers and linux-rpi4-headers are in conflict (linux-headers). Remove linux-rpi4-headers? [y/N] y
Packages (4) linux-rpi4-6.1.66-1 [removal] linux-rpi4-headers-6.1.66-1 [removal] linux-rpi4-mainline-6.6.6-1 linux-rpi4-mainline-headers-6.6.6-1
Total Download Size: 40.85 MiB
Total Installed Size: 82.85 MiB
Net Upgrade Size: 2.70 MiB
------------------- cut for useless loginfo ------------------------------
==> Building image from preset: /etc/mkinitcpio.d/linux-rpi4-mainline.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
-> -k 6.6.6-1-MANJARO-RPI4 -c /etc/mkinitcpio.conf -g /boot/initramfs8
==> Starting build: '6.6.6-1-MANJARO-RPI4'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [kms]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs8'
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly
/var/log/pacman.log
[2023-12-12T16:44:42+0100] [PACMAN] Running 'pacman -S linux-rpi4-mainline linux-rpi4-mainline-headers'
[2023-12-12T16:45:13+0100] [PACMAN] Running 'pacman -S linux-rpi4-mainline linux-rpi4-mainline-headers'
[2023-12-12T16:46:13+0100] [ALPM] transaction started
[2023-12-12T16:46:15+0100] [ALPM] removed linux-rpi4-headers (6.1.66-1)
[2023-12-12T16:46:16+0100] [ALPM] removed linux-rpi4 (6.1.66-1)
[2023-12-12T16:46:17+0100] [ALPM] installed linux-rpi4-mainline (6.6.6-1)
[2023-12-12T16:46:17+0100] [ALPM-SCRIPTLET] ===> Modifing config.txt to load for pi3/4/5 kernels
[2023-12-12T16:46:23+0100] [ALPM] installed linux-rpi4-mainline-headers (6.6.6-1)
[2023-12-12T16:46:25+0100] [ALPM] transaction completed
[2023-12-12T16:46:26+0100] [ALPM] running '30-systemd-update.hook'...
[2023-12-12T16:46:26+0100] [ALPM] running '60-depmod.hook'...
[2023-12-12T16:46:29+0100] [ALPM] running '60-linux-rpi4-mainline.hook'...
[2023-12-12T16:46:33+0100] [ALPM] running '90-linux-rpi4-mainline.hook'...
[2023-12-12T16:46:33+0100] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-rpi4-mainline.preset: 'default'
[2023-12-12T16:46:33+0100] [ALPM-SCRIPTLET] ==> Using configuration file: '/etc/mkinitcpio.conf'
[2023-12-12T16:46:33+0100] [ALPM-SCRIPTLET] -> -k 6.6.6-1-MANJARO-RPI4 -c /etc/mkinitcpio.conf -g /boot/initramfs8
[2023-12-12T16:46:35+0100] [ALPM-SCRIPTLET] ==> Starting build: '6.6.6-1-MANJARO-RPI4'
[2023-12-12T16:46:35+0100] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2023-12-12T16:46:36+0100] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2023-12-12T16:46:38+0100] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2023-12-12T16:46:38+0100] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2023-12-12T16:46:38+0100] [ALPM-SCRIPTLET] -> Running build hook: [kms]
[2023-12-12T16:46:39+0100] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2023-12-12T16:46:40+0100] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2023-12-12T16:46:40+0100] [ALPM-SCRIPTLET] -> Running build hook: [consolefont]
[2023-12-12T16:46:40+0100] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2023-12-12T16:46:40+0100] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2023-12-12T16:46:42+0100] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2023-12-12T16:46:42+0100] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2023-12-12T16:46:43+0100] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2023-12-12T16:46:43+0100] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: '/boot/initramfs8'
[2023-12-12T16:46:47+0100] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
Still rebooted just fine though:
$ inxi
CPU: quad core Model N/A (-MCP-) speed/min/max: 600/600/1500 MHz
Kernel: 6.6.6-1-MANJARO-RPI4 aarch64 Up: 0m Mem: 220.6 MiB/7.62 GiB (2.8%)
Storage: 7.44 GiB (50.3% used) Procs: 177 Shell: Bash inxi: 3.3.31
Great. Now test away…