From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9196] New: raspberry pi 3 default build seem broken
Date: Thu, 25 Aug 2016 23:28:21 +0000 [thread overview]
Message-ID: <bug-9196-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9196
Bug ID: 9196
Summary: raspberry pi 3 default build seem broken
Product: buildroot
Version: 2016.05
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: mikhail_tchernychev at yahoo.com
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 6626
--> https://bugs.busybox.net/attachment.cgi?id=6626&action=edit
config file
Hi,
I was able to compile build root for RPi 3 default configuration and it
apparently boots but when I enter login "root" and blank password id does
allow me to login. So far whatever I did I was not able to login, even
I specified "root" password in the configuration. My .config file is
attached.
Also I tried to compile systemd for RPi3 but I even did not get login screen
(I had to disable post-build script because it was not finding inittab)
I am willing to troubleshoot, but don't know how :(
thank you
Mikhail
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-08-25 23:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 23:28 bugzilla at busybox.net [this message]
2016-08-26 14:42 ` [Buildroot] [Bug 9196] raspberry pi 3 default build seem broken 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
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@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.