Transition of Arch and linux-firmware-* to individual packages

Env: Manjaro stable repo
AMD CPU/GPU

Hello everyone,

Arch Linux has converted the linux-firmware package into a virtual one and created individual, concrete linux-firmware packages.

News: https://archlinux.org/news/linux-fir…l-intervention/
Packages: https://archlinux.org/packages/?sort…ainer=&flagged=

How does Manjaro handle linux-firmware, or rather, the individual packages now?

Best regards,
Kyrindor

See here: [Unstable Update] June 2025 - #74 by philm

Individual firmware packages were created on Arch 2 days ago (2025-06-21) and have been released to Manjaro Unstable branch

Branch compare for Manjaro - linux-firmware

Hi @nikgnomic,

I’ve read the news on the Arch page, and a friend of mine mentioned the transition regarding linux-firmware-* packages.

My main question is concerning the upcoming stable repository update: Are there any actions required from my side, either before or after the update, or will Manjaro manage the linux-firmware-* packages automatically (e.g., as a metapackage or similar)?

For the stable repo path :slight_smile:

See the fix: PKGBUILD · master · Packages / core / linux-firmware · GitLab

Archlinux doesn’t create a meta package: PKGBUILD · main · Arch Linux / Packaging / Packages / linux-firmware · GitLab

So no, no user intervention is required with Manjaro.

2 Likes

:point_down:

2 Likes

Thank you folks!

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.