Bug#1026224: Reproduced, needs help from netboot experts

[Roland Clobus]

Control: severity 1026224 normal
Control: tags 1026224 +moreinfo +confirmed +help

Hello Juri, Thomas, Andi,



I've reduced the command line options to a minimal set:

# Native build on amd64
lb config -d bookworm -b netboot

# Cross-build on arm64


Notice the warning at the beginning:




I can force the issue without cross-building by disabling all bootloaders.

# You need to patch out the 'exit 1' in configuration.sh first
# Otherwise the fake value 'none' will be rejected
lb config -d bookworm -b netboot --bootloaders none




You are the experts, can you tell me?

With kind regards,
Roland Clobus

Finally, I've found some time to reproduce your case (using the current git version of live-build). lb config -d bookworm -b netboot --architecture arm64 --bootstrap-qemu-arch arm64 --bootstrap-qemu-static /usr/bin/qemu-aarch64-static [2024-11-03 22:39:37] lb config -d bookworm -b netboot --architecture arm64 --bootstrap-qemu-arch arm64 --bootstrap-qemu-static /usr/bin/qemu-aarch64-static W: You have specified no bootloaders; I predict that you will experience some problems! For arm64 we currently don't activate any bootloader, while for amd64 the BIOS bootloader (syslinux) is defaulted. If any bootloader is selected, the splash-screen is generated, which in the case of netboot happens in the tfpboot directory. I haven't tried netbooting for live images yet, though the manual [1] lists the HOWTO steps. As for the proper fix, it depends on whether a netboot would require the splash screen or not. [1] https://live-team.pages.debian.net/live-manual/html/live-manual/the-basics.en.html#236

OpenPGP_signature.asc
Description: OpenPGP digital signature