From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla at busybox.net <bugzilla@busybox.net>
Date: Tue, 10 Dec 2019 20:02:51 +0000
Subject: [Buildroot] [Bug 11766] Console (getty) issues with systemd
In-Reply-To: <bug-11766-163@https.bugs.busybox.net/>
References: <bug-11766-163@https.bugs.busybox.net/>
Message-ID: <bug-11766-163-IYsYd8iqnF@https.bugs.busybox.net/>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net

https://bugs.busybox.net/show_bug.cgi?id=11766

Simon <simon.vanderveldt+buildroot@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|NEEDINFO                    |---
             Status|RESOLVED                    |REOPENED

--- Comment #6 from Simon <simon.vanderveldt+buildroot@gmail.com> ---
I've ran into this issue as well when updating from 2018.11 to 2019.02.

The problem is that systemd automatically picks up the kernel's
console=<console> parameter and creates a serial-console@<console>.service
which collides with the one generated by buildroot.
The solution is to not create a service file for the serial console when using
systemd.

See https://github.com/simonvanderveldt/norns-image/pull/40 for more info.

-- 
You are receiving this mail because:
You are on the CC list for the bug.