On 21/04/2020 14:23, Marcin Juszkiewicz wrote:
W dniu 21.04.2020 o 13:14, Alper Nebi Yasak pisze:An alternative that occurred to me later is putting console=tty0 on the "Graphical install" grub entries (in grub-gencfg), but that'd mean debian-installer wouldn't run on serial consoles when launched from those entries (probably OK, not sure).D-I runs on each available console. So you would get it on tty0 and on ttyAMA0.
I'm seeing different behaviour on a QEMU VM and my chromebook when I add console=tty0 to the kernel commandline, where the /proc/consoles contents end up being:
| "console=tty0" | no console arg |
-----------+------------------+----------------+
QEMU VM | tty0 and ttyAMA0 | ttyAMA0 only |
-----------+------------------+----------------+
Chromebook | tty0 only | ttyS2 and tty0 |
-----------+------------------+----------------+
The essential difference between the two devices is:
- the QEMU VM has a ACPI SPCR table for the serial port
- the chromebook has a "chosen stdout-path" dt node for the serial port
I expect the installer will launch on both consoles in the QEMU VM as
you said, I momentarily forgot that ttyAMA0 persists on the VM even with
"console=tty0". What I meant is it will only launch on tty0 on the
chromebook, where ttyS2 might be working but won't be in /proc/consoles
(if that makes sense).