fixing "raspi firmware" errors on the official amd64 ISO

More
1 year 2 weeks ago #336529 by andypugh

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

Please Log in or Create an account to join the conversation.

More
1 year 2 weeks ago #336531 by unknown
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.

Please Log in or Create an account to join the conversation.

More
1 year 2 weeks ago #336684 by rodw

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.

Please Log in or Create an account to join the conversation.

More
1 year 1 week ago #336687 by tommylight
What am i missing? Seeing you all jump through so much hoops makes me wonder what are you using as a starting point?
Back when i tested Debian BookWorm 12.2 and 12.5, i downloaded the Live ISO with XFCE, remastered it and tested, it worked and did not have raspi issues. Did the same things with 12.2 Mate edition, also no raspi issues.
Granted i used the LinuxCNC version that was on Debian repos, but still, this should not matter.
Sorry, but i feel really bad seeing you go through all the trouble.
Is there something i can help with?
P.S.
Rob, sorry, i did download your ISO but did not get to testing it.
The following user(s) said Thank You: unknown

Please Log in or Create an account to join the conversation.

More
1 year 1 week ago #336692 by unknown
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 following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
1 year 1 week ago #336819 by rodw
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?

Please Log in or Create an account to join the conversation.

Time to create page: 0.064 seconds
Powered by Kunena Forum