Archlinuxarm.org distro updates

I went through the upgrade with no issues here.

This was done when pacman 7.0 was upgraded for all RPi kernels.

no broadband, so hate play dead duck.
Pi4, thinking move back to PiOS when trixie release.

edit,
Pi4/sway, refuse over 600MB update.
sway is a dead duck anyway.

Successfully upgraded GT King Pro Manjaro-Arm-Gnome on Unstable branch. So far did not notice any visual artifacts on the new updated Chromium just a shot 10 minutes run though.

Will upgrade Manjaro-KDE-opi5plus later.

Oops. Posted at the wrong place it was meant to be on Unstable Updates.

I was going to do a sync with arch-arm and unstable but looks like the mirrors are locked down again since the first of the month. I read on their forums they are going through some sort of rebuild again. So I guess I will wait until they are done.

http://nj.us.mirror.archlinuxarm.org/aarch64/

Had been down for a while. No update since early this month. Had been trying to install Chromium_132 or v133 to check whether v4l2-request vpu hw acceleration works on Opi5-Plus but only Chromium_v131 is available.

In difference to Arch Arch-ARM is pushing updates to mirrors as sets. When a big rebuild is in progress no updates are pushed.

Well they finally posted a reason after nearly a month.

Re: Packages database doesn’t update anymore since few weeks

Post by graysky » Wed Feb 26, 2025 11:02 am
The toolchain was updated and the build farm is cranking on rebuilding. For context, aarch64 has 12,569 packages.

alarm repo packages has been rebuilt. Waiting Manjaro-Arm repo to sync.

Syncing:

:: Status

-------------------------------------------------------------------------------
                            BRANCH                                         JOB
-------------------------------------------------------------------------------
                      arm-unstable            synchronizing packages [52/2668]

What other “rolling” distro options do we have for the Pi5 anyway?

I tried to get alpine up and running with KDE but failed. Even setting it up is a hassle. I did not understand how to install it. It is mainly used as a base for a container type of system. So maybe it is not even intended for desktop use.

There is (or was) endevourOS which is basically the same thing as Manjaro. Both arch arm.

Opensuse is only available for Pi4. It is mind boggling that they do not yet support Pi5 even after more than a year of its release.

Void Linux. Well, that one also caused me headaches.

There are rhino linux (ubuntu based but rolling) which comes with xfce (i hate the gui) and openmamba (independent) which is also available with kde plasma. But of course, being independent means you can only install whatever is available in their repos.

So yeah, arch arm still seems like the most viable option but it seems like it is kept barely alive.

Maybe you may need to find another hobby that does not stress you out.

I am not stressed. I don’t understand. Where did i say i was stressed?

Can you describe what you’re missing on arch/manjaro?

If it’s the chromium package problem. There are several solutions besides spending 15h recompiling the package with the arch forum pkgbuild. First, switch to a more open-source competitor like firefox, whose nightly version with webgpu enabled has little to envy to chromium (no default sync, no faster than firefox nighlty, problem with manifest v2 this summer with lots of ads).
If chromium is imperative, there’s still flatpak, which has chromium 135 and mesa 25, so no more problems with the raspberry.

 flatpak update

Chromium is still faster than Firefox, at least on the Pi.

Anyway, i wasnt really a chromium user. Until Opera switched to webkit in 2013, I was an avid Opera lover and its presto engine was the best web browsing engine i have ever seen (still to this date, i miss it). Calling it “fast” is an understatement. The browser also had a wonderful RSS engine, email extension, it had mouse shortcuts, everything that today’s modern browsers had, had their origins in Opera’s wonderful presto engine. It was one of a kind back then. Once they switched engines, all these features were thrown out the window in one day, the browser lost its wonderful functionality.

The reason i am on chromium is because it is easy to just use the google ecosystem. One account (and password) for everything.

You might try Vivaldi, if you haven’t already. Also, being a past Opera fan, you might be pleasantly surprised after performing some research into Vivaldi’s origins. Cheers.

Do you know whether chromium-135 from flatpak support v4l2request for vpu hardware acceleration support?

No idea, I just know that firefox supports it but not for all devices. There are subtleties that were explained in the firefox github thread on raspberry hardware decoding support for h264 v4l2.
Firefox also needs a capable local ffmepg for this to work.
Nobody has this device, is the decoding chain ok? I understood that a patched ffmpeg and mpv were required? If it’s not the case, I’ll go to the repositories of a distribution that supports the device and then I’ll try to remake the whole chain in pkgbuild from their example.

Yes, I have got mpv to have vpu hw acceleration using ffmpeg-v4l2-request 7.1.1-2 and mpv-full-git 0.9.2.r12860.gef4ef9ec79-1. Thank you @junari

But unfortunately Firefox does not seems to use ffmpeg-v4l2-request 7.1.1-2.

Chromium (deb) from Chromium from debian : JianFeng Liu (by amazinfate) support v4l2request.

So basically mpv and/or ffmpeg decode in hardware?
Which formats would you like to decode in a browser?

for firefox you can try the options

media.hardware-video-decoding.force-enabled

and

media.ffvpx.enabled to false

to use local ffmpeg. (firefox bundled ffvpx library used for vp8/vp9/av1 decode)

Currently v4l2request supports h264 up to 1080p only, on my device.

Well vp9, av1 and h264/265 if possible.

Will try the firefox options you suggested.