On Manjaro-opi5plus-kde with linux-6.14.3-1 or kernel-6.1.99-armbian-git on boot up it request for me to enter in my password (kde wallet or something) to load/enable wifi and once I enter the password wifi is available.
On Manjaro-opi5plus-kde Samba was disabled.
Edit: Is nmb.service the same as Samba? When on linux-aml-6.12.21-4, wifi is available on system startup.
With linux-aml-6.12.21-4 nmb.service start up much faster <4s
I was able to shave off 30 seconds here on my vim3. Wifi now is active at about 60 seconds now. This is including a shutdown and reboot as I only do ssh here with my vim3. So I am happy with my results.
I saw that in dmesg it was trying to do a:
direct firmware load with a specific file name in various directories and fail
load brcmfmac4359-sdio.clm_blob and fail looking in different directories which did not exist
It finally fell back and loaded firmware it finally found.
I rebuilt the vim3 wifi firmware package:
Added link with firmware name it was originally was looking for
Added brcmfmac4359-sdio.clm_blob file it was looking for that did not exist
Move the install directory in the package from /lib/firmware to /lib/firmware/updates/brcm/ to put it higher in the firmware seach path
This removed all fails in dmesg except for it wants to look first in /lib/firmware/current-kernel-version which I am going to live with that as it does not exist.
Warpme added the 6.15 branch today to his git. This is the patches I use for the linux upstream kernel. He is preparing for when 6.15 leaves the -rc stage.
I am going to give him a few days to work out any bugs if there are any before I post a test kernel.
There has not been any commits to the new warpme 6.15 branch since they added it so I have pushed linux-rc-6.15.rc5-1 kernel packages to unstable when the mirrors sync.
I want to ask a big favor when you test the new kernel. There has been an issue with zram every since the 6.15 kernel came out with rpi devices. RPi thinks it is due to an overhaul of zram but I want to rule out that the issue is upstream and not RPi’s kernel. The whole time you are testing the new kernel run this command in a terminal and leave it open and wait for a kernel stack trace to appear:
dmesg -w
If you see a stack trace then you can reboot and create a swap file and disable zswap-arm.service then reboot. I have no issue with a swapfile and this kernel.
Create a swapfile:
sudo systemctl disable zswap-arm.service
sudo mkswap -U clear --size 4G --file /swapfile
sudo swapon /swapfile
swapon --show # Shows swapfile status
#Finally, edit the fstab configuration to add an entry
# at the bottom of file for the swap file to initialize at
#boot and save/exit:
sudo nano /etc/fstab
#Add
/swapfile none swap defaults 0 0
#Reboot your device
#To remove a swap file, it must be turned off first and then can be removed:
sudo swapoff /swapfile
sudo rm -f /swapfile
#Finally, remove the relevant entry from /etc/fstab.
#Enable back zswap-arm.service and reboot
Here I have been using the swap file for all kernels instead of switching back and forth.
Please let me know how your tests go with this kernel.
Warpme has not modified any patches all week on their new -rc kernel tree. Warpme will remove their 6.14 tree most likely with in the next 2 or 3 weeks as they prepare for 6.15 to be their default.
I have pushed the latest linux-rc-6 to the unstable branch when the mirrors sync.
Added 05-18-2025:
I have pushed the latest linux-6.14.7-1 to the unstable branch when the mirrors sync.
I pushed linux-rc-6.15.rc7-1 to unstable when the mirrors sync.
It is getting time to start considering testing 6.15.rc7-1. It will most likely be out of -rc stage this weekend. Shortly warpme will move to 6.15 and remove their 6.14 tree. Also in the near future Linus will declare 6.14 EOL and stop supporting it.
My Vim3Pro:
OS: Manjaro ARM Linux aarch64
Host: Khadas VIM3
Kernel: Linux 6.15.0-rc7-1-MANJARO-ARM
Uptime: 2 mins
Packages: 1233 (pacman)[arm-unstable]
Shell: bash 5.2.37
Display (E280i-A1): 1360x768 @ 60 Hz in 27" [External]
WM: Xfwm4 (X11)
[Qt]: kvantum
[Qt]: Papirus-Dark-Maia
Font: qt5ct [Qt]
Cursor: Adwaita
Terminal: /dev/pts/0
CPU: a311d (6) @ 2.21 GHz
GPU: Amlogic meson-g12a-mali [Integrated]
Memory: 276.13 MiB / 3.69 GiB (7%)
Swap: 0 B / 5.53 GiB (0%)
Disk (/): 24.19 GiB / 28.38 GiB (85%) - ext4
Local IP (wlan0): 192.168.0.2/24
Locale: en_US.UTF-8
My RockPro64
OS: Manjaro ARM Linux aarch64
Host: Pine64 RockPro64 v2.1
Kernel: Linux 6.15.0-rc7-1-MANJARO-ARM
Uptime: 12 mins
Packages: 915 (pacman)[arm-unstable]
Shell: bash 5.2.37
Display (E280i-A1): 1360x768 @ 60 Hz in 27" [External]
WM: Xfwm4 (X11)
WM Theme: Default
[Qt]: kvantum
[Qt]: Papirus-Dark-Maia
Font: qt5ct [Qt]
Cursor: Adwaita
Terminal: /dev/pts/0
CPU: rockpro64 (6) @ 1.80 GHz
GPU: Rockchip rk3399-mali [Integrated]
Memory: 284.76 MiB / 3.76 GiB (7%)
Swap: 0 B / 5.65 GiB (0%)
Disk (/): 9.12 GiB / 14.30 GiB (64%) - ext4
Local IP (end0): 192.168.0.249/24
Locale: en_US.UTF-8
linux-rc-6.15-rc7-1 boot up successfully on Opi5-Plus.
Gnome don’t have issue with vendor’s bsp-6.1 kernels with Screen Lock.
Operating System: Manjaro ARM Linux
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.15.0-rc7-1-MANJARO-ARM (64-bit)
Graphics Platform: Wayland
Processors: 4 × ARM Cortex-A55, 4 × ARM Cortex-A76
Memory: 15.6 GiB of RAM
Graphics Processor 1: Mali-G610
Graphics Processor 2: Mali-G610
Product Name: Xunlong Orange Pi 5 Plus
Edit: One advantage of mainline kernel linux-6.14.y and linux-rc-6.15-rc7-1 over the vendor’s bsp-6.1.y kernel is Screen Lock does NOT cause screen colour distortion when you reactivate the screen on KDE Plasma-6.3. This issue only apply to QT base DE like KDE Plasma and LXQT running under Wayland session that I have tested. Reported this issue before to LXQT developer and thought it was due to LXQT Wayland session issue. It might be a combination issue between bsp-6.1 and KDE Plasma-Wayland/LXQT-Wayland.
Gnome DE Wayland does not have this lock screen issue with vendor’s bsp-6.1 kernel or mainline kernel.
Overall the vendor’s bsp-6.1 kernel has more functions working on Opi5-Plus when it comes to vpu hardware support via rkmpp. The mainline kernel linux-6.14 and linux-rc-615-rc7-1 has limited vpu hardware acceleration support.
The linux kernel packages has moved from the 6.14.y → 6.15.y tree. The new linux-6.15.0-1 kernel packages has been pushed to the unstable branch when the mirrors sync.
Manjaro-opi5plus-xfce updated successfully to linux-6.15.0-1. Clapper able to play local h264 up to 1080p/60 video and stream some Youtube h264 videos so fart up to 1080p/30.
On Manjaro-opi5plus-kde and linux-6.15.0-1 the newly install Clapper does NOT load any loacal h264/mp4 video (video not recognized by Clapper) or stream any Youtube video.
Edit: Just a feedback. Manjaro-opi5plus-kde/Manjaro-opi5plus-xfce on linux-6.15.0-1 still NO audio/sound output on HDMI1. Audio/sound output on HDMI0 only.
Opi5-Plus-xfce-linux-6.15.1-1 updated to linux-6.15.2-1 successfully. Mainly running on xfce-wayland-session.
Edit: With mainline kernel labwc wayland compositor, power manager/management works as expected where as on vendor’s bsp kernel-6.1.115-armbian-git the power manager doesn’t seem to behave correctly.
