All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerard van den Bosch <gvandenbosch@gmail.com>
To: yocto@yoctoproject.org
Subject: Warning: unable to open an initial console
Date: Fri, 26 May 2017 19:05:24 +0800	[thread overview]
Message-ID: <CADqNDzo_i22kiy7upOZfD2FoRsFAdJ6_+F7pDATSTonooN1fQQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

Hello,

I have build my vendor custom kernel 2.6.20 with yocto daisy.
Daisy is used because seems to be last release supporting this old kernel.

I tried building core-image-minimal and core-image-base.

The kernel boots and the rootfs is mounted but then I get:

"Warning: unable to open an initial console."

I found on the internet this is because "/dev/console" doesn't exists.
The dev folder in my generated rootfs is empty.

On internet found can do the following commands:
"mknod -m 600 /dev/console c 5 1 "
"mknod -m 666 /dev/null c 1 3"

But if this is the problem how do I add this to my recipe?
Or is there a proper way to populate this devices?

Cheers,
Gerard

[-- Attachment #2: Type: text/html, Size: 1008 bytes --]

             reply	other threads:[~2017-05-26 11:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26 11:05 Gerard van den Bosch [this message]
2017-05-26 11:27 ` Warning: unable to open an initial console Andrea Adami
2017-05-26 13:52   ` Gerard van den Bosch
2017-05-26 14:20     ` Ayoub Zaki
2017-05-26 14:27       ` Gerard van den Bosch
2017-05-26 14:35         ` Ayoub Zaki
2017-05-26 15:07           ` Gerard van den Bosch
  -- strict thread matches above, loose matches on Subject: below --
2010-10-25 21:30 Timur Tabi
2009-09-30 17:24 Steven A. DuChene
2009-09-30 17:05 Steven A. DuChene
2009-09-30 17:44 ` Arjan van de Ven
2007-04-02 19:04 Tom Strader
2007-04-02 22:49 ` Chris Wedgwood
2007-04-02 23:20   ` Tom Strader
2007-04-03  1:34     ` young dave
2007-04-03 18:35       ` Tom Strader
2007-04-04  1:53         ` young dave
2007-04-05 15:57           ` Tom Strader
2000-11-02 15:11 John Jones
2000-11-02 17:33 ` Matthew Locke

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=CADqNDzo_i22kiy7upOZfD2FoRsFAdJ6_+F7pDATSTonooN1fQQ@mail.gmail.com \
    --to=gvandenbosch@gmail.com \
    --cc=yocto@yoctoproject.org \
    /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.