This is hhhhuuuuugggggeee! One of the biggest updates to end the year. It might take a while to get it actually stable. So we recommend to switch over to arm-testing branch if you need a working machine!
Some highlights, which partly might break your system:
Python 3.9 update rolled in. We hope to rebuild all needed packages real soon. If you use AUR packages, we recommend to install rebuild-detector before applying this update.
Boost got updated, which need some rebuilds of our packages too
Package changes from Fri Dec 11 10:41:49 CET 2020 can be found here.
Testers needed on arm-unstable branch
We are in need of testers for our arm-testing and arm-unstable branches.
So if you are adventurous and want newer software quicker, we would love for you to help us test out the new packages in arm-unstable branch.
All you have to do to switch to this branch is:
Edit /etc/pacman-mirrors.conf and change Branch = arm-stable to Branch = arm-unstable.
Run this command: sudo pacman-mirrors -f5 && sudo pacman -Syyu. This will generate a new mirrorlist for you, sync your databases with the new mirror and update your system using the arm-unstable branch.
We would then love for you to give feedback in our update posts in #manjaro-arm:arm-unstable-updates. That way we can better find and fix bugs, before they hit arm-stable branch. Thank you!
No issue, everything went smoothly
Yes there was an issue. I was able to resolve it myself.(Please post your solution)
Yes i am currently experiencing an issue due to the update. (Please post about it)
Broke my wifi. I have the network settings but no device. This was after updating the rpi bootloader update. But restoring previous version does not fix the issue. Still investigating.
Edit: I just went through a wild ride to get may system back up. A crazy set of events that do not add up in my mind. But I am now in sync with arm-unstable and everything seems to be working again. tl;dr ZFS from the AUR was removed from my system.
The cause of the wifi failure was this, but it is not occurring now:
I noticed that my Plasma desktop is no longer āacceleratedā (meaning Kwin crashes, disabling OpenGL stuff) on my Pinebook Pro after the update to mesa 20.3. It used to be.
I found this MR on the Mesa gitlab, which looks like it could be related.
If it is, it will be fixed when Mesa 20.3.1 releases on the 16th.
kinda switched over to unstable, but hit a snag, fixed it then hit a road block, then it just fell off a cliff.
Note 1) Pinephone screen too small for window layout I recommend for small screen users to use nano to edit $sudo nano /etc/pacman-mirros.conf (I think this is fixed in later beta versions)
note 2) sudo pacman-mirrors -f5 && sudo pacman -Syyu
seemed to go ok, but ā¦ the snagā¦ kept getting āunable to lock databaseā, so per a different thread. visone
Hi!
You need to delete de db file and regenerate again
sudo rm /var/lib/pacman/db.lck
sudo pacman -Syyu
note 3) back on track packages were downloading then it could not update geary, nothing updated and sent back to terminal prompt. I donāt have more details on this becauseā¦ cat trying to eat icecream, got icecream away from catā¦ Pinephone locked screen, and now lock screen password not working. Tried the startup 123456 didnāt work.
So ā¦ I just plan on downloading the latest unstable beta version and reloading with that.
Beta3 (2020-12-11) Download
Hummā¦ something is going on. canāt boot any image of Manjaro. the Jumpdrive works great, so I have access to the emmC. I flashed images successfully before, but now i have tried several different images and nothing will boot Manjaro. It loads the Logo, with the spinner below, goes a few cycles, and hangs. What do i need to change in the boot script to not boot silent, but watch what is getting loaded?
8GB & 4GB RPi4 updated to arm-unstable booting on SD and NFS.
I do not know when it began, the issue likely predates my first use of the net HOOK.
But if the hook is activated in your mkinitcpio.conf, the wifi driver crashes and you end up with no wifi device. The net hook is required for booting via NFS.
Dec 14 18:20:36 client kernel: ------------[ cut here ]------------
Dec 14 18:20:36 client kernel: WARNING: CPU: 0 PID: 123 at crypto/rsa-pkcs1pad.c:540 pkcs1pad_verify+0x154/0x180
Dec 14 18:20:36 client kernel: Modules linked in: cfg80211(+) rfkill brcmutil overlay zram zsmalloc
Dec 14 18:20:36 client kernel: CPU: 0 PID: 123 Comm: systemd-udevd Not tainted 5.10.0-rc7-1-MANJARO-ARM #1
Dec 14 18:20:36 client kernel: Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
Dec 14 18:20:36 client kernel: pstate: 00000005 (nzcv daif -PAN -UAO -TCO BTYPE=--)
Dec 14 18:20:36 client kernel: pc : pkcs1pad_verify+0x154/0x180
Dec 14 18:20:36 client kernel: lr : public_key_verify_signature+0x204/0x334
Dec 14 18:20:36 client kernel: sp : ffff800011d9b6d0
Dec 14 18:20:36 client kernel: x29: ffff800011d9b6d0 x28: ffff80001146b020
Dec 14 18:20:36 client kernel: x27: 000000001f030000 x26: 000000000000010e
Dec 14 18:20:36 client kernel: x25: ffff0001045ff800 x24: ffff000103c90d00
Dec 14 18:20:36 client kernel: x23: ffff0001045ff000 x22: ffff000103e6dac0
Dec 14 18:20:36 client kernel: x21: ffff800011d9b788 x20: ffff000100890480
Dec 14 18:20:36 client kernel: x19: ffff0001045ff000 x18: 0000000000000002
Dec 14 18:20:36 client kernel: x17: 0000000000000007 x16: 0000000000000000
Dec 14 18:20:36 client kernel: x15: ffff800010bb28a0 x14: 0000000000000004
Dec 14 18:20:36 client kernel: x13: ffff0001045ff7ff x12: ffff80001067e8d8
Dec 14 18:20:36 client kernel: x11: 0000000000000007 x10: 0101010101010101
Dec 14 18:20:36 client kernel: x9 : ffff8000105bc834 x8 : 0000000000000100
Dec 14 18:20:36 client kernel: x7 : 0000000000000000 x6 : 0000000000000600
Dec 14 18:20:36 client kernel: x5 : 0000000000000000 x4 : fffffe0003ef2400
Dec 14 18:20:36 client kernel: x3 : 000001ffffe00002 x2 : 0000000000000600
Dec 14 18:20:36 client kernel: x1 : 0000000000000000 x0 : 0000000000000000
Dec 14 18:20:36 client kernel: Call trace:
Dec 14 18:20:36 client kernel: pkcs1pad_verify+0x154/0x180
Dec 14 18:20:36 client kernel: public_key_verify_signature+0x204/0x334
Dec 14 18:20:36 client kernel: x509_check_for_self_signed+0xb8/0x13c
Dec 14 18:20:36 client kernel: x509_cert_parse+0x16c/0x1e4
Dec 14 18:20:36 client kernel: x509_key_preparse+0x30/0x1b0
Dec 14 18:20:36 client kernel: asymmetric_key_preparse+0x6c/0xb0
Dec 14 18:20:36 client kernel: key_create_or_update+0x184/0x434
Dec 14 18:20:36 client kernel: regulatory_init+0x194/0x294 [cfg80211]
Dec 14 18:20:36 client kernel: cfg80211_init+0x80/0xe8 [cfg80211]
Dec 14 18:20:36 client kernel: do_one_initcall+0x54/0x2d0
Dec 14 18:20:36 client kernel: do_init_module+0x60/0x29c
Dec 14 18:20:36 client kernel: load_module+0x21e4/0x2820
Dec 14 18:20:36 client kernel: __do_sys_finit_module+0xb8/0xfc
Dec 14 18:20:36 client kernel: __arm64_sys_finit_module+0x2c/0x40
Dec 14 18:20:36 client kernel: el0_svc_common.constprop.0+0x84/0x1f0
Dec 14 18:20:36 client kernel: do_el0_svc+0x30/0xa0
Dec 14 18:20:36 client kernel: el0_svc+0x20/0x30
Dec 14 18:20:36 client kernel: el0_sync_handler+0x1a4/0x1b0
Dec 14 18:20:36 client kernel: el0_sync+0x174/0x180
Dec 14 18:20:36 client kernel: ---[ end trace 0f472a12ddda9418 ]---
Well, after hunting this down, it turns out the dump is not what breaks wifi. The dump is caused by the kernel attempting to load the regulatory.db but it is not loading the required /usr/lib/crda/pubkeys/sforshee.key.pub.pem. The kernel config sets CONFIG_CFG80211_REQUIRE_SIGNED_REGDB=y which requires validating but .pem is not used. I think libnl should validate, I do not know enough on this topic.
Will this prevent nfsroot over wifi? Maybe, untested.
But this is not the cause of the missing wifi devices, and so what is? I am not exactly sure. But the good news is I know a āfixā. It seems adding net to HOOKS causes the need for:
But now I can nfsboot on wired without breaking wifi.
Edit: Adding another group of files cleans up another boot error but it does not seem to effect anything. I believe user space applies the required configurations.
I messed with this a for a while. I loaded both the regulatory dbs and several other things into the initramfs. I could get the kernel to load the database but it failed to validate it. So I never cleared up the dumps. It could be that I am still missing something else on the initramfs but I donāt see any clues as to what that could be.
I just noticed that I put the databases as binaries, probably should have been as FILES but I donāt think it mattered, as they were placed in the initramfs.
Edit: It feels like maybe a crypto module or something is missing. The dump is harsh for simple failed to validate which should be handled more gracefully anyway. But it could be other things too, like the RPi4 firmware. I donāt have a deep enough understanding.
Next odd issue:
After a fresh install and subsequent update to unstable. On the second reboot my RPi4 experienced a wifi issue which the effect would hang the desktop and very high cpu utilization but nothing of note when running top.
I think the issue is /usr/lib/systemd/system/NetworkManager.service.d/NetworkManager-ovs.conf which has the following:
[Unit]
After=openvswitch.service
I do not have openvswitch installed, so no systemd service. So I changed it to:
[Unit]
#After=openvswitch.service
Then rebooted and wifi reappeared and worked properly.
I got the hint from checking the status of NetworkManager and noticed failed ovs.
Edit: My daily driver which is also on arm-unstable, also without openvswitch, does not have the problem with the setting above.
So I am not sure, maybe a timing issue? The two with the issue are on SD while this one is on SSD.
(3/4) upgrading graphviz [##################] 100%
Warning: Could not load "/usr/lib/graphviz/libgvplugin_gdk.so.6" - It was found, so perhaps one of its dependents was not. Try ldd.
Warning: Could not load "/usr/lib/graphviz/libgvplugin_gtk.so.6" - It was found, so perhaps one of its dependents was not. Try ldd.
Warning: Could not load "/usr/lib/graphviz/libgvplugin_gdk.so.6" - It was found, so perhaps one of its dependents was not. Try ldd.
Warning: Could not load "/usr/lib/graphviz/libgvplugin_gtk.so.6" - It was found, so perhaps one of its dependents was not. Try ldd.
$ ldd /usr/lib/graphviz/libgvplugin_gdk.so.6
libgdk-x11-2.0.so.0 => not found
I guess it needs a dependency added. Installing gtk2 appears to resolve the issue.
Edit: And then I work through my orphan packages and graphviz is removed, so I removed gtk2.
