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 21:03:29 +0000 [thread overview]
Message-ID: <bug-11766-163-TBebZII79s@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 #4 from Peter Seiderer <ps.report@gmx.net> ---
Tested with buildroot master and raspberrypi3_64_defconfig with the following
changes:
- change to glibc
- channge to init systemd
No login on HDMI, double Buildroot login on serial.
After changing cmdline.txt from:
root=/dev/mmcblk0p2 rootwait console=tty1 console=ttyAMA0,115200
to (as described in [1]):
root=/dev/mmcblk0p2 rootwait console=ttyAMA0,115200 console=tty1
everything worked fine...
Login from serial, getty for HDMI console runs:
/sbin/agetty -o -p -- \u --noclear --keep-baud console 115200,38
Login from HMDI conole, getty for serial runs:
/sbin/agetty -o -p -- \u --keep-baud 115200,38400,9600 ttyS0 vt220
Mind to share your config/defconfig file?
[1] https://patchwork.ozlabs.org/patch/668134
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-07-21 21:03 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
2019-07-21 21:03 ` bugzilla at busybox.net [this message]
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-TBebZII79s@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