Strugling with installation

Sorry just to clarify, when running the installer from the ISO image the raspi-firmware is being installed.
Can confirm upon first login to the newly installed system tuning apt purge removes the offending files. This has been confirmed by running find to look for any files that contain the string raspi prior to running apt purge then after running apt purge.

hi there,

Just for anyone who searches and finds this, as of this writing (October 30 2025), if you have already run sudo apt update and sudo apt upgrade, you can't just run apt purge, you have to run:


And that will remove the error.

In addition, at least on my machine, after you run pncconf, you have to comment out lines 21 and 22 in order for LinuxCNC to launch.

Hmm I wonder why apt purge worked in my situation ?

And why did it work when I created a new ISO and added a line to pressed that ran apt purge to remove the rasp firmware at the end of the installation process ?

As an update this will no longer be an issue with Trixie, as the live build process blacklists the raspi-firmware from being installed.
And just be 100% clear the source of this issue was the live-build utility prior to Debian Trixie.
Unless new Bookworm ISOs are released built with the live-build utility built from the Trixie source it will forever be an issue.
Having delved into this issue and built new ISOs using the live-build that comes with Trixie ( and repackaging and installing on bookworm ) I can say this issue is fixed. It took a bit of delving into the various scripts that do the hard lifting to find the issue.
It could of been fixed a couple of ways, the above mentioned modification to the preseed file on the ISO, but the raspi- firmware would have still been present on a live session, or individually picking the firmware to install, unfortunately I do not think the cause of the issue was fully understood.
From Trixie on this is fixed.

@unknown reflecting on this, I executed

and encountered the error. I did not (as you indicated) execute 

on a fresh installation right after login. So, that is maybe the difference. You are likely entirely correct that executing apt get remove right after login on first install will fix the issue. That said, I suspect most folks are going to come across the error only after trying to do an apt get upgrade, so my note is aimed at those folks, who when searching might come across this discussion.