From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9196] raspberry pi 3 default build seem broken
Date: Tue, 20 Sep 2016 20:47:44 +0000 [thread overview]
Message-ID: <bug-9196-163-pXLXgVb1sw@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9196-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9196
--- Comment #6 from Peter Seiderer <ps.report@gmx.net> ---
Tested with buildroot git d4db4277ffbd1fae478ba748c626eddc7c220e67 (including
[1]).
With bare raspberrypi3_defconfig login via serial and login via
hdmi/usb-keyboard
is possible.
With raspberrypi3_defconfig with change to glibc/systemd serial login works out
of the box.
For hdmi/usb-keyboard (tty1) login the following link was necessary (as advised
in [2]):
ln -sf /usr/lib/systemd/system/getty at .service
/etc/systemd/system/getty.target.wants/getty at tty1.service
Additional he file /etc/systemd/system/getty at .service.d/nodisallocate.conf to
avoid clearing the console.
[1]
https://git.buildroot.net/buildroot/commit/?id=1e03cc2290f98fc7434254d2abd9afd504de8360
[2] https://wiki.archlinux.org/index.php/Systemd_FAQ
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-09-20 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 23:28 [Buildroot] [Bug 9196] New: raspberry pi 3 default build seem broken bugzilla at busybox.net
2016-08-26 14:42 ` [Buildroot] [Bug 9196] " bugzilla at busybox.net
2016-08-26 16:01 ` bugzilla at busybox.net
2016-08-27 3:58 ` bugzilla at busybox.net
2016-08-27 3:59 ` bugzilla at busybox.net
2016-08-30 3:34 ` bugzilla at busybox.net
2016-09-20 20:47 ` bugzilla at busybox.net [this message]
2016-09-20 21:44 ` bugzilla at busybox.net
2016-10-08 5:27 ` bugzilla at busybox.net
2016-10-15 15:50 ` 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-9196-163-pXLXgVb1sw@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.