Re: arm64/aarch64 graphical debian-installer
On 11/18/25 17:11, Emanuele Rocca wrote:
Self-built as follows:
$ git clone https://salsa.debian.org/live-team/live-build/ # under /home/ema
$ export LIVE_BUILD=/home/ema/live-build/
$ lb --version
807c43bbf69301c9c0a20a83f52179045eb9b989_2025-11-10T14:41:39+01:00
# In a temporary directory:
$ lb config --source true --distribution sid --updates false --archive-areas 'main' --bootloaders grub-efi --debian-installer live
$ sudo lb build
Emanuele, thanks for this excellent clarification!
Indeed, going back to the mere fundamental basics i do get the very same
result.
But now try to put a valid preseed.cfg into config/includes.installer/
and rebuild the ISO. Here is the minimal content i used:
#_preseed_V1
d-i debian-installer/country string other
When you try booting the resulting ISO image you will have been able to
reproduce the error:
Once there is a preseed.cfg file, the graphical installer stops showing
up and automatically resorts to the newt frontend on the serial console.
This is the perfect complement to bug 1116551 where using the
DEBIAN_FRONTEND=gtk boot parameter to force the graphical frontend
completely ignores any present pressed.cfg file. Apparently, this is one
and the same issue. It doesn't happen with an equal build procedure in
amd64, but only in arm64.
So when i build my own ISO project without adding any preseed.cfg file,
the graphical installer comes up flawlessly. But since there is no other
way to make use of the preseed/late_command string this is no solution
for the actual issue.
Anybody knows where in the debian-installer sources this unfortunate
mutual exclusion between graphical frontend and a present pressed.cfg
might be decided?
Thanks for all the insight given so far!
Paul
Reply to: