All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: "Matheus Izvekov" <mizvekov@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cannot open initial console
Date: Thu, 23 Feb 2006 15:28:48 +1000	[thread overview]
Message-ID: <200602231528.52605.ncunningham@cyclades.com> (raw)
In-Reply-To: <305c16960602221818h69de46cfpa06027b44c2e07e8@mail.gmail.com>

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

Hi.

On Thursday 23 February 2006 12:18, Matheus Izvekov wrote:
> Hi all
>
> When i tried kernel 2.6.15.4, i noticed i cant boot it, i get
> "warning: cannot open initial console" then it reboots. I've searched
> for it and found the breakage occurs from 2.6.15.1 to 2.6.15.2
>
> Before i start to bisect to find the culpirit, and as there were few
> changes, anyone has a good guess about what broke it?

My guess would be that /dev/console doesn't exist on an initrd/initramfs 
you're using. If you're not using one, my second guess would be that 
something did a nasty and deleted the node on you. Only a guess, mind you.

Regards,

Nigel

> Thanks all in advance.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-02-23  5:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23  2:18 cannot open initial console Matheus Izvekov
2006-02-23  5:27 ` Matheus Izvekov
2006-02-23  5:25   ` Willy Tarreau
2006-02-23  5:28 ` Nigel Cunningham [this message]
2006-02-23  6:41 ` Matheus Izvekov
2006-02-23  6:46   ` Matheus Izvekov
2006-02-23  7:07     ` Chris Wright
2006-02-24 10:33     ` Vitaly Fertman

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=200602231528.52605.ncunningham@cyclades.com \
    --to=ncunningham@cyclades.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mizvekov@gmail.com \
    /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.