[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Fixing the missing serial console after installation issue


John Paul Adrian Glaubitz, on sam. 30 sept. 2017 20:17:19 +0200, wrote:
> On 09/30/2017 07:19 PM, Frank Scheiner wrote:
> > Not sure, but [1] says that it should be sufficient to add all console devices
> > to the kernel command line for systemd to detect and activate them, e.g.
> > `console=ttyS0,9600n8` - which includes port and configuration.
> Yes, I'm aware of that and that's what people usually use to enable the serial
> console post installation. However, it's most likely not what we would want to
> use as adding it to the kernel command line assumes that you know what type
> of bootloader is being used and you would have to add case-matching for the
> various bootloader types.

Well, debian-installer already needs to know about that, to be able to
pass to the installed system the parameters which were given to boot the
installer itself.

> Please be aware that I am not talking about just fixing the serial console issue
> on SPARC machines but on all architectures supported by Debian. Hence, I want
> to use a generic and robust solution, not a quick hack.

Well, your solution is somehow a "quick hack": enabling serial console
automatically already works "for all archs", there is just something
which doesn't happen to work in your case, and AIUI it's writing on the
installed system the kernel parameters which were passed to boot d-i.
And that does need to be fixed for a lot more things than just the
serial console, so it should really be worked on.

Or is there really no way on your system for d-i to be able to write
down the parameters to be passed to the kernel for the installed system?


Reply to: