From: Arjan van de Ven <arjan@infradead.org>
To: "Steven A. DuChene" <linux-clusters@mindspring.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Warning: unable to open an initial console
Date: Wed, 30 Sep 2009 19:44:47 +0200 [thread overview]
Message-ID: <20090930194447.016e66c3@infradead.org> (raw)
In-Reply-To: <31532395.1254330324879.JavaMail.root@elwamui-rubis.atl.sa.earthlink.net>
On Wed, 30 Sep 2009 13:05:24 -0400 (EDT)
"Steven A. DuChene" <linux-clusters@mindspring.com> wrote:
> 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.
on FC9 ....
here's what to do on a successful boot
mkdir /tmp/mnt2
mount /dev/sdaX /tmp/mnt
(where the X is your root device, if you use lvm, mount the lvm thing
there)
cp -a /dev/console /tmp/mnt/dev/console
umount /tmp/mnt2
next prev parent reply other threads:[~2009-09-30 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 17:05 Warning: unable to open an initial console Steven A. DuChene
2009-09-30 17:44 ` Arjan van de Ven [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-30 17:24 Steven A. DuChene
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
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=20090930194447.016e66c3@infradead.org \
--to=arjan@infradead.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox