Been running the new kernel and bootloader files for a day now and no issues here.
Hmm, interesting.
I re-installed the kernel and headers, and rebooted. All is good.
I then reinstalled mesa-git and rebooted. All is good.
I then say to myself, ah hah!.. the bootloaders are the cause.
So I then reinstalled the bootloaders. All is good.
Go figure.
Looks like one of those days… lol
Sometimes after an upgrade on a reboot things are still in memory and do not get flushed.
The kwin compositor still crashes for me in X11. After this update, it is a little more ugly now. The background shrinks and moves to the upper left corner along with mntray notifications. Apps open normally, so still mostly a cosmetic issue.
Are you using kms in KDE manjaro arm alongside kernel 5.10 and v3dv enabled? I think the spin or lxde manjaro has become a mess…
Is it on the Raspberry pi?
Yes, KDE Plasma on Wayland (X11 not so good) with
gpu_mem=64
dtoverlay=vc4-kms-v3d-pi4
max_framebuffers=2
Also, I have the current eeprom installed, not sure if a particular version is required.
An HDMI 2.0 cable or accurate hdmi_mode and hdmi_group settings are required.
linux-rpi4-rc (5.10-rc7)
mesa-git
Note: make sure xf86-video-fbturbo is not installed.
With the above, v3dv with Vulkan support does work on my 8GB RPi4.
They finally upgraded the bootloader files to kernel 5.4.81. I have pused the new packages to the unstable branch when it syncs.
raspberrypi-bootloader 20201207-1
raspberrypi-bootloader-x 20201207-1
Quite a few changes actually:
https://github.com/raspberrypi/firmware/commit/919aee0ed75f7db48a38b8b96c13228a7584cfd7
1 Like
It seems mesa-20.3 does not contain Vulkan support.
$ vulkaninfo
Cannot create Vulkan instance.
This problem is often caused by a faulty installation of the Vulkan driver or attempting to use a GPU that does not support Vulkan.
ERROR at /build/vulkan-tools/src/Vulkan-Tools-1.2.159/vulkaninfo/vulkaninfo.h:666:vkCreateInstance failed with ERROR_INCOMPATIBLE_DRIVER
$ pacman -Qi mesa
Name : mesa
Version : 20.3.0-3
Description : An open-source implementation of the OpenGL specification
Architecture : aarch64
URL : https://www.mesa3d.org/
Licenses : custom
Groups : None
Provides : mesa-libgl opengl-driver
Depends On : libdrm wayland libxxf86vm libxdamage libxshmfence libelf libomxil-bellagio
libunwind llvm-libs lm_sensors libglvnd zstd vulkan-icd-loader
Optional Deps : opengl-man-pages: for the OpenGL API man pages
mesa-vdpau: for accelerated video playback
libva-mesa-driver: for accelerated video playback
Required By : gst-plugins-base-libs gtk3 libglvnd mpv qt5-base
Optional For : None
Conflicts With : mesa-libgl
Replaces : mesa-libgl
Installed Size : 54.92 MiB
Packager : Arch Linux ARM Build System <builder+n1@archlinuxarm.org>
Build Date : Tue 08 Dec 2020 02:50:10 PM CST
Install Date : Sat 12 Dec 2020 05:09:25 AM CST
Install Reason : Explicitly installed
Install Script : No
Validated By : None
The 5.10 kernel is officially out on RPI github : Linux 5.10 · raspberrypi/linux@2c85ebc · GitHub
There already are a lot of patches since this commit…
Wa have to wait for @Darksky now. I hope it will compile correctly…
On the tail end of compiling right now. I will test then push if all is good.
Here are the latest kernels/headers that are in the unstable branch when the mirrors sync.
Kernel 5.10 is now out of the -rc stage. As a result the linux-rpi4-mainline kernel is now 5.10.0 so if you are on the linux-rpi4-rc kernel you need to install the linux-rpi4-mainline kernel package to be up to date. At this time there is no 5.11.0-rc kernel until kernel.org releases it and the RPi folks add it to their tree.
Also the RPi people have not upgraded the bootloader packages as of this post. I will be out of pocket the rest of the day but will check when I get back home tonight.
linux-rpi4 5.4.83-1
linux-rpi4-headers 5.4.83-1
linux-rpi4-mainline 5.10.0-1
linux-rpi4-mainline-headers 5.10.0-1
2 Likes
They went ahead and updated the bootloader packages although they have a typo with the commit message. They have 2 kernel bumps in a row with the same kernel version. lol
They have been pushed to the unstable branch.
raspberrypi-bootloader 20201214-1
raspberrypi-bootloader-x 20201214-1
1 Like
New kernel and bootloader are working for me, thank you!
1 Like
Lately there has been questions when people look at the rpi-eeprom git and see things has been updated and think their rpi-eeprom package is out of date. I have not been following the rpi-eeprom git as it is a WIP and can be buggy. They make commits from time to time and then have to either revert or fix issues with their commits. When they get things where they want it then they put out what they call their “Current production bootloader and VLI EEPROM release” and that is what I follow. To be honest they regularly make commits to their git and it could be a long string of having to build new packages to keep up and at the same time there will have the chance of being buggy. This is what I use to package which will always be their latest release:
https://github.com/raspberrypi/rpi-eeprom/releases/tag/v2020.09.03-138a1
Having said all of that I am not opposed to making an rpi-eeprom-git package from time to time if they have made a commit to fix a bug or if a new feature is added that can not wait for it get into their stable release.
Today I put a rpi-eeprom-git package in the unstable branch as it has some pi 400 related commits. I also put a new rpi-eeprom package in all branches as I added a rpi-eeprom-git conflict in it in case people want to switch back and forth between the 2 packages.
rpi-eeprom 2020.09.03-2 # Added to all branches
rpi-eeprom-git 20201214-1 # Added to the unstable branch
I am also wondering how these packages is going to get along with the new python version in the unstable branch since it uses python scripts. I have not upgraded here to the unstable branch as I like to build everything from the stable branch so if some one is using the unstable branch let me know how things go.
After upgrading the eeprom:
[ray@pi4 ~]$ sudo rpi-eeprom-update
BCM2711 detected
VL805 firmware in bootloader EEPROM
BOOTLOADER: up-to-date
CURRENT: Fri Dec 11 11:15:17 AM UTC 2020 (1607685317)
LATEST: Fri Dec 11 11:15:17 AM UTC 2020 (1607685317)
FW DIR: /lib/firmware/raspberrypi/bootloader/stable
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1
[ray@pi4 ~]$
[ray@pi4 ~]$ sudo rpi-eeprom-update -r
Removing temporary files from previous EEPROM update
1 Like
I am on unstable, all packages up to date. This is on a Raspberry Pi 400.
$ sudo rpi-eeprom-update
BCM2711 detected
VL805 firmware in bootloader EEPROM
*** UPDATE AVAILABLE ***
BOOTLOADER: update available
CURRENT: Thu 16 Jul 15:15:46 UTC 2020 (1594912546)
LATEST: Thu 3 Sep 12:11:43 UTC 2020 (1599135103)
FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1
$ sudo rpi-eeprom-update -a
BCM2711 detected
VL805 firmware in bootloader EEPROM
*** INSTALLING EEPROM UPDATES ***
BOOTLOADER: update available
CURRENT: Thu 16 Jul 15:15:46 UTC 2020 (1594912546)
LATEST: Thu 3 Sep 12:11:43 UTC 2020 (1599135103)
FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1
BOOTFS /boot
EEPROM updates pending. Please reboot to apply the update.
Reboot
$ sudo rpi-eeprom-update
BCM2711 detected
VL805 firmware in bootloader EEPROM
BOOTLOADER: up-to-date
CURRENT: Thu 3 Sep 12:11:43 UTC 2020 (1599135103)
LATEST: Thu 3 Sep 12:11:43 UTC 2020 (1599135103)
FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1
$ sudo rpi-eeprom-update -r
Removing temporary files from previous EEPROM update
So all is well on my end 
1 Like
Great! Thanks for testing.
No problem!
But I just noticed mine that it didn’t update to the same version as you. Do I need to do something specific for the Pi400 ?
Mine was testing the new rpi-eeprom-git package I pushed. It had a commit to add a [pi400] section in /boot/config.txt. It is only really good if you want a special config for the pi400 and want to keep separate if you use the same image to boot on another pi device.
They said if you use that then you have to put a [all] section afterwards (Can have nothing in the all section)
[pi400]
some
configs
here
[all]
If you do not need the above then the version you are on is fine.
It is the rpi-eeprom-git package that I tested actually.