fixing "raspi firmware" errors on the official amd64 ISO

Thoughts changed, situation is little more complex.

Hostmot2 firmware is there. Running Axis in a VM using the sample code, apart from the latency error, runs ok.

Now this is something I found rater curious.
Both were builds had the target as Debian Bookworm.

Building on a system running Debian Trixie raspi-firmware IS NOT installed. (built twice on 2 different machines)
Building on a system running Debian Bookworm raspi-firmware IS installed. (single build only attempted)

I will try a build on my Bookworm machine with the live-build package from Trixie and see what the results are.

The firmware "blacklist" is created here
salsa.debian.org/live-team/live-build/-/...h?ref_type=heads#L92

So I will need to see what the difference is between the Bookworm live-bulid package and Trixie.
Simple enough Bookworm doesn't have the firmware blacklist code.

Quick Update.

Using "Trixie" branch from here; salsa.debian.org/live-team/live-build/-/...rixie?ref_type=heads

I built a live-build package on a machine running Bookworm from the above repo. Installed the built package and was able to successfully build a Linuxcnc ISO without the raspi-firmware. As noted above hostmot2 firmwares are installed, a test run of Axis with the default gcode produced no errors, apart from latency due to being run in a virtual machine.

Building live-build packages from the above sources also works for building ISO on Linux Mint 22.1 Xia.

The goal would be to pin Linuxcnc to 2.9.4 during the ISO creation, as there seems to be a few issues reported by users with either the 2.9.5 or 2.9.6 branch.

I installed live-build from the Debian repos for my bookworm machine and had no luck. Upon looking at the firmware function the code to blacklist the firmware was not there.
Building a live-build package from the Trixie branch on my bookworm machine resolved the issue. As I also stated the same procedure as allowed me to successfully build a ISO on my Mint machine.

andypugh wrote:

unknown wrote:

Building on a system running Debian Trixie raspi-firmware IS NOT installed. (built twice on 2 different machines)
Building on a system running Debian Bookworm raspi-firmware IS installed. (single build only attempted)
This is because they fixed it (it's actually fixed in Debian 12.1) 

bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065640

They fixed the Debian release files it never pushed their changes to the Debian builder until Trixie. Very annoying.

The issue has been with the live-build prior to the Trixie release.

The function that installs the firmware prior to Trixie doesn't blacklist unneeded firmware packages depending on the architecture. So when you run the installer from the ISO it installs all firmware packages regardless of architecture. This could have been mitigated by removing the raspi-firmware at the final stage of the installer by adding a line to preseed that instructs the installer to remove the raspi-firmware package. Basically what a user is needs to do when the error pops it's head up during an update.
On my bookworm machine instead of using the package that is in the bookworm repo I built a live-build package on bookworm using the Trixie sources. An extra line is added to the config, indicating that it's amd64 we're building an ISO for and the "blacklist function" kicks in and the raspi-firmware (and some others unrelated to amd64) are never installed when the installer is run from the ISO.

So to conclude:
It comes down to the version of live-build being used.
Bookworm version of live-build is (1:20230502), this causes the issue.
Trixie version of live-build is (1:20250505+deb13u1), this has no issues as long as --architectures amd64 is in the config file used by live build.
To install live-build (1:20250505+deb13u1) on Bookworm you need to build the package from source and install the package you just built. Also the additional line in the config file.

Building an ISO of a machine running Trixie that was successful gave me an idea as what the issue maybe. Installing the package for Trixie on Bookworm was no help, it was required to build from source.

I pretty much describe the issue in this post:
forum.linuxcnc.org/9-installing-linuxcnc...-iso?start=20#336448

The live build gets its code from the host that builds the system so to get a Trixie system, you need to be running Trixie. So I don't see why building for bookworm is not a problem.

In my testing back with the original installer (after some changes were made and committed to the release version), the pi firmware was not installed but it seemed after later bookworm versions were upgraded to, the firmware was  erroneously installed. And yes, I built the builder from source.

Why don't you try changing the architecture to arm64 and give the pi a go?