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.
