I'm surprised the patched version in testing hasn't been backported to trixie-backports, but in this case, you should be able to directly install the Forky deb on Trixie after downloading it: https://packages.debian.org/forky/broadcom-sta-dkms
Liquorix headers (and kernel images) are just one package, not counting the optional metapackages if you want automatic upgrades. So no "-common" package is split out.
Thanks, stevepusser.
Then I'll enable the forky repository and download the broadcom package from there, and let you know.A few last questions:
1) I currently have the 6.12.57 kernel with the relative broadcom-sta-dkm package; after downloading the 6.18 kernel, can I install the broadcom-sta-dkms package from forky without removing the existing one (with Arch, I had multiple kernels, each with the broadcom package working).
2) Given the problem of the lack of the optional metapackages for other kernels like liquorix, what do you think about enabling the MX Linux AHS repository (which has liquorix plus always-updated vanilla kernels)?
My recommendation is just to download and install the Forky deb manually from the link at the bottom of https://packages.debian.org/forky/broadcom-sta-dkms.
Yes, the MX repos should be compatible. It just make it hard to get support either from here, or the MX forums, if you combine the two into some hybrid.
I'm the guy that ports over those packages for MX repos, including the AHS section, and I take care to build them on generic Debian platforms as far as possible. (pbuilder and sbuild are way cool, and I barely know any of their tricks) That said, the AHS section includes a lot more than just updated kernels, so you might see a lot more upgrades than you wanted. Just to be safe, you should only install the Forky or MX's deb file https://mxrepo.com/mx/repo/pool/ahs/b/b ... _amd64.deb manually after downloading one. After installing a kernel from trixie-backports, you should also upgrade the firmware-nonfree metapackage from backports, since the updated drivers in a kernel may require different firmware files.
The Liquorix kernel and headers metapackages are always there, in both the MX and Liquorix's own Debian repos--I meant they are optional in that you don't have to install them--they just make the kernel upgrades appear automatically. The older kernels are still there and appear as boot choices in GRUB. They all take up space in your boot partition, so one has to clean out old kernels every so often. Yes, MX has a GUI tool that makes that pretty easy (MX-Cleanup). We still get questions on the forum as to why they can't install a newer kernel--it's usually that they never used Cleanup.
Once in a while, we do get hiccups in AHS, such as when KDE's Discover couldn't handle an upgrade to the Mesa 25.3.3 backport I recently did, when every other apt frontend was fine with it. It was due to the vdpau and va-api packages being removed, as they were merged into mesa-libgallium.
Statistics: Posted by stevepusser — 2026-02-09 17:12