Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Minnowboard set up problem
Date: Thu, 22 Oct 2020 21:53:43 +0200	[thread overview]
Message-ID: <20201022215343.7acadee4@gmx.net> (raw)
In-Reply-To: <CALbLrU2J46KsUr8b+8U=0M24En3B+w9rwn3YJ6ve=COdZ7RATw@mail.gmail.com>

Hello Facu Ramallo,

On Thu, 22 Oct 2020 15:53:00 -0300, Facu Ramallo <facku24@gmail.com> wrote:

> Hi guys!
>
> I'm brandly new with buildroot. I'm trying to build a system for my
> minnowboard. After a little research, I found out that the basic steps to
> start are:
>
>    - *make minnowboard_max_defconfig*
>    - *make*
>    - *dd if=sdcard.img of=my_sdcard bs=1M*
>
> And I could finally start my linux distribution on my minnowboard. But,
> then I used
>
>    - *make menuconfig*
>
> In order to enable the packages for openssh, I want to send some code
> through  scp. But, after enable those packages, run
>
>    - *make*
>    - *dd if=sdcard.img of=my_sdcard bs=1M*
>
> And the problem is that after my system boots, I don't read the
> messages "*Wellcome
> to Buildroot*" and "*buildroot login:*" anymore.
>
> Can you tell me please, if I did something wrong?

Would suspect a long startup time of the sshd daemon because of lack
of enough random data (search for 'ssh random booting' for details)...

Try to wait longer...

Regards,
Peter

>
> Regards!

  reply	other threads:[~2020-10-22 19:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 18:53 [Buildroot] Minnowboard set up problem Facu Ramallo
2020-10-22 19:53 ` Peter Seiderer [this message]
     [not found]   ` <CALbLrU3i4W9=EhobCX5+g_1ZCKQCzYFPzatz+E-MwxU9OX8tkg@mail.gmail.com>
2020-10-22 21:21     ` Peter Seiderer

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=20201022215343.7acadee4@gmx.net \
    --to=ps.report@gmx.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