Skip to contentSkip to conversation

New: agetty: unrecognized characters after login (systemd)

Buildroot bugzilla at busybox.net 1 participant 2 messages May 2, 2019

lore
Share & tools
lore
#0 lore raw

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

Bug ID: 11821
Summary: agetty: unrecognized characters after login (systemd)
Product: buildroot
Version: 2019.02.2
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: iot at iotasoft.ir
CC: buildroot at uclibc.org
Target Milestone: ---

I have a problem with agetty. when the login prompt gets the user name, then the password prompt or login shell shows unrecognized characters as below:

=============================

[  OK  ] Started Serial Getty on ttymxc4.
[  OK  ] Reached target Login Prompts.
[  OK  ] Stopped Network Name Resolution.

[FAILED] Failed to start Network Name Resolution. See 'systemctl status systemd-resolved.service' for details. [ OK ] Stopped Network Time Synchronization. [FAILED] Failed to start Network Time Synchronization. See 'systemctl status systemd-timesyncd.service' for details. [ OK ] Stopped Network Name Resolution.
[FAILED] Failed to start Network Name Resolution. See 'systemctl status systemd-resolved.service' for details. [ OK ] Stopped Network Time Synchronization. [FAILED] Failed to start Network Time Synchronization. See 'systemctl status systemd-timesyncd.service' for details. [ OK ] Stopped Network Name Resolution.
[FAILED] Failed to start Network Name Resolution. See 'systemctl status systemd-resolved.service' for details. [ OK ] Stopped Network Time Synchronization. [FAILED] Failed to start Network Time Synchronization. See 'systemctl status systemd-timesyncd.service' for details.

[  OK  ] Started OpenSSH server daemon.
[  OK  ] Reached target Multi-User System.

Starting Update UTMP about System Runlevel Changes...
[ OK ] Started Update UTMP about System Runlevel Changes.

Welcome to F+S i.MX6
fsimx6 login: root
?cs???

===============================
After that any keys that I press will create other random unrecognized characters.

My serial-getty at .service file's content is as below:
===============================
[Unit]
Description=Serial Getty on %I
Documentation=man:agetty(8) man:systemd-getty-generator(8) Documentation=http://0pointer.de/blog/projects/serial-console.html BindsTo=dev-%i.device
After=dev-%i.device systemd-user-sessions.service plymouth-quit-wait.service getty-pre.target
After=rc-local.service

# If additional gettys are spawned during boot then we should make

# sure that this is synchronized before getty.target, even though
# getty.target didn't actually pull it in.
Before=getty.target
IgnoreOnIsolate=yes

# IgnoreOnIsolate causes issues with sulogin, if someone isolates

# rescue.target or starts rescue.service from multi-user.target or
# graphical.target.
Conflicts=rescue.service
Before=rescue.service

[Service]
# 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
Type=idle
Restart=always
UtmpIdentifier=%I
TTYPath=/dev/%I
TTYReset=yes
TTYVHangup=yes
KillMode=process
IgnoreSIGPIPE=no
SendSIGHUP=yes

[Install]
WantedBy=getty.target
==============================

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#1 lore raw

[Buildroot] [Bug 11821] agetty: unrecognized characters after login (systemd)

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

khozaei <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from khozaei <[email protected]> ---
I found the solution finally.

I added --flow-control option to agetty in serial-getty at .service and this option fixed my problem.

Quoted 5 lines

**-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.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.