All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11766] Console (getty) issues with systemd
Date: Sun, 21 Jul 2019 19:16:39 +0000	[thread overview]
Message-ID: <bug-11766-163-dF0SzFUubn@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11766-163@https.bugs.busybox.net/>

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

--- Comment #3 from Peter Seiderer <ps.report@gmx.net> ---
Enabling hardware flow control for a 3-wire serial line (without
the extra wires for the hardware flow control) seems strange, and I believe is
not the solution...

diff -u ~/Downloads/console-getty.service_comparison.txt
~/Downloads/console-getty.fixed.txt 
--- /home/seiderer/Downloads/console-getty.service_comparison.txt      
2019-04-09 19:02:33.570689557 +0200
+++ /home/seiderer/Downloads/console-getty.fixed.txt    2019-07-21
21:03:18.299974466 +0200
@@ -32,7 +32,7 @@
     # The '-o' option value tells agetty to replace 'login' arguments with an
     # option to preserve environment (-p), followed by '--' for safety, and
then
     # the entered username.
-    ExecStart=-/sbin/getty -L %I 115200 vt100
+    ExecStart=-/sbin/getty -h %I 115200 vt100
     Type=idle
     Restart=always
     UtmpIdentifier=%I

You seem to have fixed the already working file (marked by you with
'console-getty.service from Buildroot 2018.11 (Working):' and not the one
marked by your with 'console-getty.service from Buildroot 2019.02.1 (Not
working):'.

The real diff between the two versions is:

-    ExecStart=-/sbin/getty -L %I 115200 vt100
+    ExecStart=-/sbin/getty -L console 115200 vt100

Can you check which console/%I the working version is using on a running
system?

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

  parent reply	other threads:[~2019-07-21 19:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 13:01 [Buildroot] [Bug 11766] New: Console (getty) issues with systemd bugzilla at busybox.net
2019-05-02 14:32 ` [Buildroot] [Bug 11766] " bugzilla at busybox.net
2019-05-02 14:33 ` bugzilla at busybox.net
2019-07-20 18:05 ` bugzilla at busybox.net
2019-07-21 19:16 ` bugzilla at busybox.net [this message]
2019-07-21 21:03 ` bugzilla at busybox.net
2019-09-29 15:50 ` bugzilla at busybox.net
2019-12-10 20:02 ` bugzilla at busybox.net
2019-12-10 21:00   ` Adam Duskett
2019-12-10 21:39 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-11766-163-dF0SzFUubn@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.