MX Linux Forum

You can probably adjust your sources to use the archived bullseye-backports repo https://archive.debian.org/debian/dists/bullseye-backports/

Some instructions here https://archive.debian.org/debian/README

At some point apt might consider it's release file, gpg key, etc., too be old, there's some ...

And Debian will probably update it in released Bookworm and Bullseye, too, since it's busted there.

dolphin_oracle has stated that MX 23 has symlinks for the usrmerged new firmware locations, so we should not have any problems with that.
I wasn't sure if the added /usr was a problem or not. I've ...

Looking some more, there might be a problem, the firmware (.fw) files are the same as before, but I see differences in the firmware-b43-installer.catalog file.

I mounted the MX-23.6_ahs_x64.iso file I have, it has how the b43 firmware was before the update.
$ cat /media/kent/disk/usr/lib/firmware ...

Concerning the updates to b43-fwcutter, firmware-b43-installer & firmware-b43legacy-installer, I can confirm that trying to downgrade the firmware-b43-installer package back to the earlier version will bork things. The package install process ends in an error after it tries to download the firmware ...

The Cleanup tool removes unused/un-needed dkms packages, so it will remove broadcom-sta-dkms if there's no Broadcom wifi device present.
But it won't remove b43-fwcutter and it's two firmware packages, firmware-b43-installer & firmware-b43legacy-installer.

Synaptic's keeps log files at /root/.synaptic/log/*

example:
root@mx1:/home/demo# cat /root/.synaptic/log/2025-07-22.165244.log
Commit Log for Tue Jul 22 16:52:44 2025


Upgraded the following packages:
b43-fwcutter (1:019-8) to 1:019-14~mx23+1
firmware-b43-installer (1:019-8) to 1:019-14~mx23+1 ...

It would be helpful if would post the QSI report.


There's a dead link in the post install script of the firmware-b43-installer package, which is used along with b43-fwcutter to install the wl firmware. The firmware-b43-installer package won't finish installing because of the deadlink. The URL has ...

I do see the "535.247.01" in the first line in QSI Graphics section.

Maybe post the output of this, it'll show all nvidia packages that are installed (might be some others than just the 470xx packages 18 shown as updates)
dpkg -l | grep ^ii\ \ .*nvidia.*


Also wonder about this in the QSI?
API ...

I think I've added all the amdgpu repos from the QSI in the first post.
$ apt-cache pkgnames | grep -e mesa -e amdgpu | sort | xargs apt-cache madison | grep repo.radeon.com | cut -f1-6 -d\ | column -t
amdgpu |
amdgpu-core | 1:6.4.60400-2147987.22.04 | https://repo.radeon.com/amdgpu/6.4/ubuntu ...

A couple days ago when the mesa updates (25.0.4) first came out there were also some wayland upgrades that caused steam to not launch. A fix for that was posted here: viewtopic.php?p=825458&hilit=steam#p825458, but those wayland updates have been removed from the repos.