mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: umesh chandak <chandak_pict@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Waring in kernel 2.6.10
Date: Wed, 5 Oct 2005 21:47:47 +0200	[thread overview]
Message-ID: <9a8748490510051247m477b1693i3fcb65271e500e23@mail.gmail.com> (raw)
In-Reply-To: <20051005192754.11115.qmail@web35905.mail.mud.yahoo.com>

On 10/5/05, umesh chandak <chandak_pict@yahoo.com> wrote:
> hi,
>            I have compiled a kernel 2.6.10 on FC3 it
> gives me the warning like this
>
>
>
> Warning: unable to open an initial console.
>

Did you remember to enable the proper console related options in your
kernel; like CONFIG_VGA_CONSOLE, CONFIG_FRAMEBUFFER_CONSOLE etc.
I guess it could also be problem with an old or incorrectly configured
udev so it can't find /dev/console or it could be a problem with your
initrd.

And if you could be bothered to stick "Warning: unable to open an
initial console." in google you'll see that you are not the first to
have a problem like that and there is *lots* of help available out
there.
Do a little research please (and if you've already done some research,
then letting people know what you've already checked when posting your
question is usually a good idea).

May I recommend this document :
http://www.catb.org/~esr/faqs/smart-questions.html

--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

      parent reply	other threads:[~2005-10-05 19:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05 19:27 umesh chandak
2005-10-05 19:40 ` Arjan van de Ven
2005-10-05 19:42 ` Valdis.Kletnieks
2005-10-05 19:47 ` Jesper Juhl [this message]

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=9a8748490510051247m477b1693i3fcb65271e500e23@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=chandak_pict@yahoo.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®