Following an install with

  auto console=tty0 console=ttyS0,115200n8

on the command line and using yesterday's amd64 daily jessie
installer, the /etc/default/grub file had GRUB_TERMINAL=serial
enabled, but it does not append the above console parameters to
GRUB_CMDLINE_LINUX.

Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683124

martin f krafft <madduck@debian.org> (2014-11-13):

There's no such version in the archive…
http://www.debian.org/releases/stable/amd64/ch05s04.html.en#problem-report

meaning at the very least the syslog.

Mraw,
KiBi.

Find one attached.

It is from a simular situation:
  Serial Port only system,
  d-i did not setup the serial port.


Groeten
Geert Stappers
Not sure if this BR should be merged with https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769407

Hello,

Geert Stappers, le Wed 03 Dec 2014 22:30:39 +0100, a écrit :

Options to be propagated to the installed kernel have to be put after
--.  With the recent kernel change which lead to #764675, it's actually
now ---, so it'd be something like

How were this console= parameter added precisely?

I have added to the manual's Boot Parameters section an explicit mention
of this.

Samuel

I'm having the exact same problem.
Installing a VM with virt-install installs a debian VM on my jessie host.

HOST (Deb Jessie Fresh Install) -> VM (Debian Jessie Fresh Install)

You're not able to use "virsh console <vmname>" because ttyS0 serial
console is not in default/grub.

One has to add

GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0,115200n8"

explicitly by oneself, otherwise you wont get a serial console spawn and
cant access the virtual machine from kvm using virsh.

Please fix this asap, thanks.

There is a similar issue, especially systemd environment.
The wheezy installer add serial console getty section in inittab,
but jessie's systemd seems no care.

I need to execute "systemctl enable serial-getty@ttyS0.service"
manually to enable serial console login.

On Wed, Dec 03, 2014 at 11:29:00PM +0100, Samuel Thibault wrote:

Hi,

I can confirm that both

	[...] console=ttyS0,115200n8 -- console=ttyS0,115200n8

and

	[...] --- console=ttyS0,115200n8

work as expected.

Part of the problems described here come from #764675.

I think Florian's problems are actually a missing feature. For SysVinit
and upstart there is code in finish-install that enables a serial
console in inittab or upstart when it is detected (_not_ triggered by
the kernel command line)

http://sources.debian.net/src/finish-install/2.56/finish-install.d/90console/

systemd-enabled fresh systems do not have an inittab, so this entire
code is more or less a no-op. systemd systems get a serial console when
a serial console is specified on the kernel command line, which is most
likely either not done by virtinst or used in the wrong way (without
---, see above).

Takatsugu's comment is related to Bug #760947 .

Best Regards,
Bernhard

Laba diena,


Noriu Jus informuoti apie šių metų pasikeitimą dėl atnaujintos visos Lietuvos įmonių bazės 2018 metų sausio vidurio.
Visi juridiniai asmenys pateikti bazėje yra veikiantys, realiai vykdantys veiklą, turintys įdarbintų darbuotojų. Duomenys pagal Sodrą, Registrų centrą.

Bazėje nurodoma ir apyvarta, darbuotojų atlyginimai, darbuotojų skaičius, transporto skaičius ir daug kitų duomenų, kuriuos matysite pavyzdyje.

Duomenis galima filtruoti pagal veiklas, miestus ir kitus duomenis.


Šią bazę verta turėti visoms įmonėms. Pateiksiu priežastis:

1) Kontaktai pateikti bazėje direktorių ir kitų atsakingų asmenų, didelė tikimybė Jums surasti naujų klientų, partnerių, tiekėjų, kai tiesiogiai bendrausite su direktoriais, komercijos vadovais.

2) Konkurentų analizavimas, tiekėjų atsirinkimas pagal Jums reikalingus kriterijus, galite atsifiltruoti pagal įmonės dydį, bazėje nurodoma kiek įmonės skolingos Sodrai.

3) Lengva, greita ir patogu dirbti su šia baze, elektroninius pašto adresus galite importuoti į elektroninių laiškų siuntimo programas ar sistemas iš kurių siunčiate elektroninius laiškus.
Taip pat galite importuoti mobiliųjų telefonų numerius į SMS siuntimo programas.


Išsirinkite iš "Veiklų sąrašo" veiklas kurių Jums reikia.
( Sąrašas prisegtas laiške excel faile )

Parašykite, kurias veiklas išsirinkote
ir atsiųsime pavyzdį ir pasiūlymą su sąlygomis įmonių bazei įsigyti



Pagarbiai,
Tadas Giedraitis
Tel. nr. +37067881041

I've just run headlong into this 10 years later.

I have a script that creates a VM thusly:
virt-install --name ${vm_name} --memory ${mem_size} \
  --disk "size=${disk_size},pool=${disk_pool},discard=unmap" \
  --machine q35 \
  --location 
http://ftp.us.debian.org/debian/dists/${suite}/main/installer-amd64/ \
  --os-variant name=debiantesting \
  --network network=ovs-net,target=ve0-${vm_name} \
  --graphics none --extra-args="console=ttyS0 netcfg/hostname=${vm_name}" \
  --console pty \
  --initrd-inject preseed.cfg

Under both bookworm and trixie, the install completes successfully over
the serial console.

In bookworm it seems systemd was being overly smart and starting a getty
on the serial port when it saw one, as there is no other apparent
configuration to start it. Under trixie this behavior is no longer
present, so I get no way to log into the installed system. (I can't be
certain this is the case as I have not been able to locate a relevant
changelog entry in systemd.) However, since grub does get configured, I
can edit the kernel command line manually on boot and append
"console=ttyS0". systemd sees this kernel argument and starts the getty.

So it seems like the simplest way to fix this in the current environment
is to have the code that sets up the grub serial arguments also go ahead
and tack on a matching "console=" to GRUB_CMDLINE_LINUX.

Kevin Otte <nivex@nivex.net> (2025-08-18):

Let's see what's been documented for 10+ years (see commit below) on
https://www.debian.org/releases/trixie/amd64/ch05s03.en.html#module-parms

    5.3.1. Boot serial console

    […]

        Be sure to specify this option after “---”, so that it is copied into
        the bootloader configuration for the installed system (if supported by
        the installer for the bootloader).

(Arguably it could be moved elsewhere within that section to make it
easier to spot.)

Commit: https://salsa.debian.org/installer-team/installation-guide/-/commit/615fcaa11aa37bfd5b6295d02a9e642e5d2e2f48


Cheers,

"console=ttyS0,115200n8" is the last element on the kernel boot
parameter line and I also use "--boot bios.useserial=on", this is
without the use of "--console pty".

This worked for Bookworm and works for Trixie.

That worked perfectly, thank you!

Does this mean this bug can realistically be closed?