I maintain a few packages for my personal use. Since I keep them up to date I have decided to share them. To avoid this topic being closed and will not be able to update I created a folder on my googledrive and will keep it current.
handbrake: This will work for all arm devices. Needs the 2 packages when installing.
zram-swap: Works on all devices x96 or arm. Uses a compressed portion of device ram. Especially good for arm devices with low ram reducing the chance of lockups and speeds up system if a swap space is currently using a swap to disk. Enable and start zram-swap.service after installing the package. The amount of swap space in ram will vary proportionally to how much ram the device has onboard.
rpi-ffmpeg:
For all RPi devices. Allows h264/h265 HW decoding for RPi4 and below devices. Allows h265 HW decoding for the pi5’s. This is a complete drop in replacement for the ffmpeg in the repo that uses the mpv in the repo. To run on X11 Desktop (I do not know how to run on others. Do not use them. One would have to do some research):
Pop the PKGBUILD’s in the AUR as ARM variants? Just make sure there’s nothing EndeavourOS specific going on in them (which I don’t imagine there would be).
Yer I was thinking more of how Trinity Desktop handle it with their own repo that needs to be added, I update official repos separate from AUR (same as anything else from other sources, helps if any issues arise to figure out where and what) (spellcheck wanted me to change figure to gunfire - a good example of to take note of what is happening)
AUR is for x86 PKGBUILDs. They will allow PKGBUILDs for arm but have to be able to run on x86. They used to allow just arm PKGBUILDs but a while back they purged them all. Even if they did allow PKGBUILDs one would still have to build the package locally to install them.
I can provide all of the PKGBUILDs for my packages if one wants to build them locally.Which would be optimal for the kernels due to 3rd party / DKMS modules some people use. I build them here on my x86 for the sake of speed as I do not use any out of tree modules. I had access to a 128 core build server at manjaro-arm to build them.
I dug out my rockpro64 and installed a new image / kernel on it and compiled the new kernels on it as a master and my x86 as a slave using distcc. So there should not be any issues with getting 3rd party modules to work. @DrYak your battery support is built in the new kernels.
[ray@rpi ~]$ cat /proc/version
Linux version 7.0.4-1-rpi (alarm@alarm) (aarch64-unknown-linux-gnu-gcc (GCC) 15.2.1 20260209, GNU ld (GNU Binutils) 2.46) #1 SMP PREEMPT Fri May 8 02:06:20 UTC 2026
RPi upgraded their kernels again to v7.0.5. I pushed them to my googledrive folder. Also I pushed an upstream kernel packages v7.0.5. Think of it as arch-arm’s upstream linux-aarch64 kernel on steroids. It has about 300 patches from the WARPME minimyth2 repo that enhances and supports all of the many devices that minimyth2 uses.
On my rockpro64:
[alarm@rockpro ~]$ uname -a
Linux rockpro 7.0.5-1-V8-WARPME #1 SMP PREEMPT Sat May 9 17:49:15 UTC 2026 aarch64 GNU/Linux
His patches are listed here in this file. This kernel is good for people who like to experiment. He searches the web for patches that have not made it upstream yet.
