From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12811] New: bootstrap stuck and no login prompt
Date: Thu, 23 Apr 2020 10:29:59 +0000 [thread overview]
Message-ID: <bug-12811-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12811
Bug ID: 12811
Summary: bootstrap stuck and no login prompt
Product: buildroot
Version: 2020.02.1
Hardware: Other
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: cristovao.cordeiro at sixsq.com
CC: buildroot at uclibc.org
Target Milestone: ---
Hi guys,
Setup: RPi 3 B+
with 2020.02.1, I've simply `make raspberrypi3_defconfig`, `make menuconfig` -
here I've just done some basic stuff like: use glibc, use systemd init,
increase the fs image size, and installed docker-cli, docker-engine and
open-ssh. Then `make`
Config: https://pastebin.com/q2qx4wNq
when booting my RPi 3B+, the last message on the splash screen is "IPv6:
ADDRCONF(NETDEV_UP): docker0: link is not read", and I cannot move from there.
there's no login prompt
and if I try to SSH remotely, it asks for password...even though I've left it
default (should be none)
Any ideas?
Thanks in advance
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-04-23 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 10:29 bugzilla at busybox.net [this message]
2020-04-23 19:51 ` [Buildroot] [Bug 12811] bootstrap stuck and no login prompt bugzilla at busybox.net
2020-04-24 6:55 ` bugzilla at busybox.net
2020-04-24 19:02 ` 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-12811-163@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