From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11821] agetty: unrecognized characters after login (systemd)
Date: Thu, 02 May 2019 14:35:06 +0000 [thread overview]
Message-ID: <bug-11821-163-Yv376pwE3k@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11821-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11821
khozaei <iot@iotasoft.ir> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from khozaei <iot@iotasoft.ir> ---
I found the solution finally.
I added `--flow-control` option to agetty in `serial-getty at .service` and this
option fixed my problem.
> **-h, --flow-control**
> Enable hardware (RTS/CTS) flow control. It is left up to the
> application to disable software (XON/XOFF) flow protocol where
> appropriate.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2019-05-02 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 11:28 [Buildroot] [Bug 11821] New: agetty: unrecognized characters after login (systemd) bugzilla at busybox.net
2019-05-02 14:35 ` bugzilla at busybox.net [this message]
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-11821-163-Yv376pwE3k@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox