Samuel Thibault, le mar. 30 mai 2023 21:21:51 +0200, a ecrit: > Samuel Thibault, le mar. 30 mai 2023 21:16:46 +0200, a ecrit: > > I'm wondering what kind of console aarch64 is using: is that the Linux > > virtual Terminal on an fbdev, or a ttyS console? Something else? The > > kernel boot logs could be useful to determine that. > > Ah, https://openqa.debian.net/tests/151286/logfile?filename=serial0.txt > provides it. > > May 30 06:37:27 init: starting pid 246, tty '/dev/ttyAMA0': > '/sbin/debian-installer' > May 30 06:37:27 init: starting pid 247, tty '/dev/tty1': > '/sbin/debian-installer' > > So it might be "something else" :) Is the shown output from ttyAMA0, or > tty1?
Also, to be noted: May 30 06:37:27 kernel: [ 0.531174] Run /init as init process May 30 06:37:27 kernel: [ 0.531176] with arguments: May 30 06:37:27 kernel: [ 0.531177] /init May 30 06:37:27 kernel: [ 0.531178] --- May 30 06:37:27 kernel: [ 0.531179] with environment: May 30 06:37:27 kernel: [ 0.531180] HOME=/ May 30 06:37:27 kernel: [ 0.531181] TERM=linux May 30 06:37:27 kernel: [ 0.531181] BOOT_IMAGE=/install.a64/vmlinuz So init does get started with TERM=linux, not vt102. So it's something in-between that seems to be setting that. Samuel
