Here is the latest 5.12-rc4 kernel/headers. I also pushed the latest PKGBUILD for it to gitlab.
https://drive.google.com/file/d/1slYC45Ha2rUnlNxEBuNowKo2Lbhp2mZH/view?usp=sharing
This test kernel is for experimenting with uefi boot only mentioned in post #483 below.
Linux abbynormal 5.12.0-rc4-1-MANJARO-ARM #1 SMP PREEMPT Mon Mar 22 09:20:31 CDT 2021 aarch64 GNU/Linux
Module Size Used by
joydev 24576 0
brcmfmac 323584 0
brcmutil 24576 1 brcmfmac
hci_uart 53248 0
sha256_generic 16384 0
btbcm 24576 1 hci_uart
bluetooth 479232 2 hci_uart,btbcm
ecdh_generic 16384 1 bluetooth
ecc 32768 1 ecdh_generic
sha256_arm64 28672 0
cfg80211 868352 1 brcmfmac
rfkill 36864 5 bluetooth,cfg80211
sch_fq_codel 20480 7
fuse 126976 1
ip_tables 32768 0
x_tables 40960 1 ip_tables
crct10dif_ce 20480 1
hid_apple 20480 0
sr_mod 28672 0
cdrom 45056 1 sr_mod
btrfs 1409024 1
blake2b_generic 20480 0
xor 20480 1 btrfs
xor_neon 16384 1 xor
raid6_pq 110592 1 btrfs
vc4 274432 0
snd_soc_core 245760 1 vc4
snd_compress 20480 1 snd_soc_core
snd_pcm_dmaengine 20480 1 snd_soc_core
drm_kms_helper 270336 1 vc4
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
fb_sys_fops 16384 1 drm_kms_helper
drm 565248 2 drm_kms_helper,vc4
backlight 20480 1 drm
cec 69632 1 vc4
snd_bcm2835 28672 0
snd_pcm 126976 5 vc4,snd_bcm2835,snd_compress,snd_soc_core,snd_pcm_dmaengine
snd_timer 36864 1 snd_pcm
snd 98304 5 snd_bcm2835,snd_timer,snd_compress,snd_soc_core,snd_pcm
i2c_bcm2708 16384 0
i2c_dev 20480 0
overlay 122880 0
crypto_user 16384 0
efivarfs 20480 1
ipv6 536576 114
How to test UEFI booting:
Create a new Manjaro installation on a SD card and update it to arm-unstable.
Reboot
Download the test kernel from the link above. Untar it and install the kernel and headers with pacman -U
Reboot
Download the UEFI firmware zip file.
Delete all files from /boot except for the kernel, initramfs and the overlays directory.
Rename the kernel to something like kernel-5.12-rc4.efi and the initramfs to initramfs-5-12-rc4.img
Extract the zip file to /boot
Now create the following file with a single line:
/boot/startup.nsh
kernel-5.12-rc4.efi rw root=LABEL=ROOT_MNJRO initrd=\initramfs-5-12-rc4.img rootwait console=serial0,115200 console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=serial0,115200 usbhid.mousepoll=8 audit=0
(If you chose a desktop image, I recommend switching to multi-user.target)
That is all that is required to make a UEFI bootable installation, reboot and try it.
Note: This is all from memory and imagination. There could be errors and/or omissions.
Also, if you do not have an ethernet connection, the UEFI may try to network boot and you will have to wait for the slow timeouts before it will boot from the SD. This can be changed via the UEFI firmware in the Setup.
Edit: You might need to substitute /dev/mmcblk0p2 for the LABEL=ROOT_MNJRO in the startup.nsh file. I did not test this, I assume using LABEL= works.
As I understand it, since the RPI4 does not have NVRAM, the UEFI settings are stored in the RPI_EFI.fd file. So you can make a backup copy of that file if you want to try messing around with the settings.
I have pushed the latest linux-rpi4/linux-rpi4-mainline kernels to the unstable branch when the mirrors sync. No uefi boot modules are in them.
No upgrade with the 2 raspberrypi-bootloader files as of this post.
linux-rpi4 5.10.25-1
linux-rpi4-headers 5.10.25-1
linux-rpi4-mainline 5.11.8-1
linux-rpi4-mainline-headers 5.11.8-1Iām on the unstable branch but I cannot see these new kernels.
Iāve checked directed on most mirrors and I canāt see them on the corresponding branchā¦
Is there any wrong ?
I installed the linux-rpi4 5.10.25 but had to roll back to 5.10.23.
Xorg would not start, no module fbdev, module not found.
@Dulbi I just rememberedā¦ the firmware does honor the traditional files. Change the name of the kernel and initramfs file too, just to make sure. Rename the kernel to something like kernel-5.12-rc.efi and the same with the initramfs. And then change the names accordingly in the /boot/startup.nsh file.
If you see the rainbow twice, it is trying to load the kernel the traditional way. You should see the rainbow and then the big raspberry of the UEFI firmware.
Edit :
Where did you get this kernel ? I canāt see it anywhere.
for instance : Index of /arm-unstable/core/aarch64/
edit : I hope I can test EFI this eveningā¦
The UEFI firmware?
No. Our answers have crossed. I was speking about the 5.10.25 kernel.
Ah, the normal way. I had no issue with the mirror having the file.
Note that I am on arm-testing and from my mirrorlist file:
Server = https://mirrors.gigenet.com/manjaro/arm-testing/$repo/$arch
Here is the issue. @Darksky you have pushed the new kernel 5.10.25 to the testing branch and not to the unstable one.
I will put these packages on my testing rpi4 to the IgnorePkg line from my /etc/pacman.conf
My xfce started just fine. I do not have plasma installed here and do not have much experience with it so I can not be of much help. What I can say is that it will check first to see if fbturbo is installed and then move on to load v3d if it can so you will always get this if fbturbo is not installed. This is normal in the Xorg log:
I have noticed lately quite a few posts here of plasma not starting after upgrades on different devices.
Re-installing the new kernel now. I will tinker around with it and see what I can get to work. Maybe I need to remove the hdmi_group and hdmi_mode, which I added from the last kernel upgrade.
Edit: I commented them out and rebooted on the new kernel and Xorg is now back. This is with fkms and lightdm.
Is it correct ?
They should be in both now. Looking like I pushed to testing last night by mistake.
pi4, kernel-5.10.25 plasma/wayland no issue.