From: "Steven A. DuChene" <linux-clusters@mindspring.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Warning: unable to open an initial console
Date: Wed, 30 Sep 2009 13:24:36 -0400 (EDT) [thread overview]
Message-ID: <12591585.1254331476737.JavaMail.root@elwamui-rubis.atl.sa.earthlink.net> (raw)
Well, according to the research I did looking for my initial
console error message on google it seems it is not a kernel
compile issue but rather an issue with the kernel needing to
find /dev/console before udev is run to create the various
device entries in /dev
To work around this I created an initrd file for my kernel
even though I have all the needed disk device drivers and
filesystems drivers in my kernel. Once I did that and put
it into place my new kernel booted up just fine.
-----Original Message-----
>From: "Steven A. DuChene" <linux-clusters@mindspring.com>
>Sent: Sep 30, 2009 1:05 PM
>To: linux-kernel@vger.kernel.org
>Subject: Warning: unable to open an initial console
>
>Hmm, I tried various combonations of turning off the framebuffer
>support all together and then turning it back on with various
>drivers (nvidia or vesa vga) but still I get the same message
>about "Warning: unable to open an initial console."
>
>Anything else I should be looking at besides the graphics support
>part of the drivers section of the kernel config?
>
>Again this is a fairly standard PCChips A13G motherboard with
>NVidia chipset and AMD Athlon 3600+ CPU that works fine with the
>regular distro supplied FC9 kernel (2.6.25-14.fc9.x86_64) and
>I have the x86_64 version of FC9 installed.
>
next reply other threads:[~2009-09-30 17:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 17:24 Steven A. DuChene [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-26 11:05 Warning: unable to open an initial console Gerard van den Bosch
2017-05-26 11:27 ` 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
2010-10-25 21:30 Timur Tabi
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=12591585.1254331476737.JavaMail.root@elwamui-rubis.atl.sa.earthlink.net \
--to=linux-clusters@mindspring.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 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.