From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9196] raspberry pi 3 default build seem broken
Date: Sat, 27 Aug 2016 03:59:46 +0000 [thread overview]
Message-ID: <bug-9196-163-X2SnkmL89h@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 #4 from Mikhail <mikhail_tchernychev@yahoo.com> ---
Here is better report (I think)
This is what I did (latest version)
git pull
make clean
make xconfig raspberrypi3_defconfig
For some reason, it does not show RPi scripts
So I exit (saving) and do it again:
make xconfig
Now RPi scripts in place.
make
OK. write to SD card.
Use RPi3 with display and keyboard attached.
Boots fine.
Welcome to Buildroot
buildroot login:
type: root
Password:
Just press enter.
Shows again:
Password:
press enter
Login timeout after 60 seconds.
No way it let me log in.
I attached latest . config
I hope it helps
I am going to make changes in config to use systemd and submit
another comment.
Best Regards
Mikhail
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-08-27 3:59 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 [this message]
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-X2SnkmL89h@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.