It seems that we have been 3 months without Manjaro ARM updates, at least for Pinebook Pro. And this is strange, can I start to suspect that development is being left a bit neglected?
2 Likes
- understaffed is the more correct description
- the dependency on archlinuxarm does not speed anything up
2 Likes
There have been delay from Arch linux arm project so we have to wait for the update.
They have updated recently so soon there will be a stable update. Plus there have been a huge kde plasma 6 release which have bugs on arm side so that is causing further delay.
No. not neglected. Instead there is more work but not much time as we all do handle this project during our free time without anything in return. I request some more patience and hopefully things will go back to normal.
Thank you for reporting the delay in update.
5 Likes
Thank you so much. You’re very kind. This reassures me. We’ll be patient. I hope the staffing issues can be resolved
3 Likes
@spikerguy Is there somewhere where we could follow the development of the next Stable: e.g. do you keep a dev diary? or mention the current status on social media?
1 Like
Hi,
Nice, Manjaro-arm-tools updated today , Manjaro ARM is alive 
What’s new with this up date, is Plasma 6 available ?
[nls@lap ~]$ date -u
jeu. 25 juil. 2024 20:55:50 UTC
[nls@lap ~]$ pamac update -a
Download of manjaro-arm-tools (2.11.3+7+g480f843-1) started
Download of manjaro-arm-tools (2.11.3+7+g480f843-1) finished
Checking keyring... [1/1]
Checking integrity... [1/1]
Loading package files... [1/1]
Checking file conflicts... [1/1]
Checking available disc space... [1/1]
==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
Upgrading manjaro-arm-tools (2.11.2-1 -> 2.11.3+7+g480f843-1)... [1/1]
Running post-transaction hooks...
Arming ConditionNeedsUpdate... [1/2]
Refreshing PackageKit... [2/2]
1 Like
Yes will update all kernels this weekend.
I have been busy with personal life.
Plus the delay is cause of kde plasma and panfrost breaking plasma de.
Needed kcm tweak. So with updated panfrost and plasma i hope it gets resolved.
Pushing untested update should break many installs thats why it was help for so long, plus we need more testers using it on testing and unstable branch.
Thanks for all the support who have been with manjaro arm project since so long.
3 Likes
You can follow our gitlab.
There you will see regular kernel updates.
I try to update the kernel as soon as they’re released but been lagging behind since few weeks now.
Unstable and testing branches are updated frequently but stable is not cause here have been a lot of changing happening in kernel, panfrost and plasma where we have been informed by the users that the de breaks on newer update so we had to hold back stable updates until it is well tested.
As adviced before we need more testers on testing and unstable branch as we cannot test so many hardware regularly. With arm every single model number is unique in its own way.
2 Likes
That’s something I hadn’t considered; for example, it seems there are significant differences between the PinePhone (which a good friend has) and the PinePhone Pro (which I have)?
1 Like
Well, yes. The main SoC is different, so one could argue that those are completely different devices. Some hardware is identical, e.g., the modem (Quectel EG-25G), or at least similar enough for the difference not to matter, e.g., the LCD panels have the same size (but I think they are not exactly identical), but some is completely different, not just the SoC, but also, e.g., the cameras.
2 Likes
manjaro-arm-tools need qemu-user-static-binfmt for dependency, how do you update?
1 Like
As I recall it is only required if building on X86_64 hardware.
pacman asked qemu-user-static-binfmt error.
1 Like
Strange
$ pamac search qemu-user --no-aur
qemu-user-binfmt 9.0.2-1 extra
Binary format rules for QEMU user mode emulation
qemu-user-static-binfmt 9.0.2-1 [Installed] extra
Binary format rules for QEMU static user mode emulation
qemu-user-static 9.0.2-1 [Installed] extra
QEMU static user mode emulation
qemu-user 9.0.2-1 [Installed] extra
QEMU user mode emulation
Is this message on aarch64 ?
I am not an experienced maintainer of crossplatform packages - perhaps @Yochanan build on x86_64 and copied the same package to aarch64 ?
I think that is what has happened - the package exist for both arm and x86 where the latter depends on qemu-user-static-binfmt to support cross architecture chroot and pkgbuild
$ uname -rm
6.6.41-1-MANJARO-RPI5 aarch64
$ sudo pacman -S manjaro-arm-tools
resolving dependencies...
warning: cannot resolve "qemu-user-static-binfmt", a dependency of "manjaro-arm-tools"
:: The following package cannot be upgraded due to unresolvable dependencies:
manjaro-arm-tools
The PKGBUILD arch=(“any”) is misleading should likely be arch=(“aarch64”, “x86_64”)
It’s an architecture independent package as there are no ELF files. I’ve moved qemu-user-static-binfmt to optional dependencies.
manjaro-arm-tools 2.11.3+7+g480f843-2 will be coming along shortly.
3 Likes
Hi,
2024.08.13
manjaro-arm-tools-2.11.3+13+g7856299-1 is up to date, thanks :-)
Edit 1 : I built yesterday 08/12 (before this manjaro-arm-tools update 08/13) an unstable image for the Odrod C4, black screen on boot. Odroid c4 running with the last stable update.
Edit 2 (2024.08.14) :
[nls@lap ~]$ date -u
mer. 14 août 2024 20:47:54 UTC
[nls@lap ~]$ sudo pacman -Syu
[sudo] password for nls:
:: Synchronising package databases...
core 140,1 KiB 824 KiB/s 00:00 [###########################################] 100%
extra 7,8 MiB 26,5 MiB/s 00:00 [###########################################] 100%
multilib 145,9 KiB 879 KiB/s 00:00 [###########################################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (1) manjaro-arm-tools-2.11.3+17+g2f50087-1
Total Download Size: 0,05 MiB
Total Installed Size: 0,13 MiB
Net Upgrade Size: 0,00 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
manjaro-arm-tools-2.11.3+17+g2f50087-1-any 53,0 KiB 688 KiB/s 00:00 [###########################################] 100%
(1/1) checking keys in keyring [###########################################] 100%
(1/1) checking package integrity [###########################################] 100%
(1/1) loading package files [###########################################] 100%
(1/1) checking for file conflicts [###########################################] 100%
(1/1) checking available disk space [###########################################] 100%
:: Running pre-transaction hooks...
(1/1) Creating Timeshift snapshot before upgrade...
==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
:: Processing package changes...
(1/1) upgrading manjaro-arm-tools [###########################################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Refreshing PackageKit...
[nls@lap ~]$
1 Like
Hi.
I am using testing and the kernel 6.8.9 is from 2nd of May.
Is this as expected or should I have received an update since then?
I am just asking to check if my update works or there is something missing.
No problems as such with the system.
I just randomly checked plasma-desktop and on archlinuxarm.org that is on 6.1.4.1 and on my PBP it’s 6.0.4.1.
Is my update not working or does testing need an update at some point. There was also no forum post that new updates have been implemented. So I guess there was nothing new ?
There has not been any updates in testing for a while and I have no clue when it will happen.
You can not compare arch-arm versions with our testing branch. Our unstable branch is equivalent to arch-arm but at the same time we maintain our own kernels so they will not be the same as arch-arm’s kernels.
Thanks for the update.
Is there something that needs to be unblocked to enable more updates ?
can you share which kernel is used ?
uname -a output please
Yes a lot of things, Mesa updated, Plasma got updated so we have many devices which have black screen issue,
I am looking into it but as we have so many device it is taking longer.
Hopefully we should have some update on stable soon.
2 Likes