From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9196] raspberry pi 3 default build seem broken
Date: Fri, 26 Aug 2016 16:01:25 +0000 [thread overview]
Message-ID: <bug-9196-163-IG510GFZAW@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 #2 from Mikhail <mikhail_tchernychev@yahoo.com> ---
Yes sorry I could not log with HDMI/keyboard. However I learn that
for RP3 to use serial line blue tooth needs to be disabled; I used
debian stock image and at first could not login via serial, showed
garbage characters along with some valid ones. After I disabled
BT in config.txt stock image worked on serial line.
The same trick with buildroot image did not work.
Regarding systemd I build it just by removing the script. It boots
but getty gets time out 1 m 30 sec, no login prompt is shown.
It is similar to issue described here:
http://buildroot-busybox.2317881.n4.nabble.com/systemd-not-working-properly-td82549.html
But on HDMI/keyboard.
I will reproduce it tonight and send a better report.
Thank you!
Mikhail
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-08-26 16:01 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 [this message]
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
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-IG510GFZAW@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.