From: Mike Houston <mikeserv@bmts.com>
To: "Joseph D. Wagner" <technojoecoolusa@charter.net>
Cc: linux-newbie@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.10 Can't Open Initial Console on FC3
Date: Sat, 1 Jan 2005 02:13:08 -0500 [thread overview]
Message-ID: <20050101021308.5a906479.mikeserv@bmts.com> (raw)
In-Reply-To: <3khdbt$ffuljg@mxip05a.cluster1.charter.net>
Hello,
It is because you need to use an initrd. Your device nodes in
FC3 are being managed by udev, and you otherwise won't have a
/dev/console or /dev/hda at that stage of the boot. There's also the
matter of LVM, if your root partition is a logical volume. Another
reason you might need an initrd.
Your mkinitrd script in FC3 will take care of these matters for you.
Mike
On Thu, 30 Dec 2004 23:00:14 -0600
"Joseph D. Wagner" <technojoecoolusa@charter.net> wrote:
> The newly compiled kernel gets through everything OK including
> mounting the root file system as read-only EXT3. However, it
> freezes on the very last line, which says:
>
> Warning: unable to open an initial console
>
> If I switch back over to the kernel that came with the distribution,
> everything boots fine, so I'm assuming the problem lies in the way I
> configured the kernel.
>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs
next prev parent reply other threads:[~2005-01-01 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-31 5:00 Kernel 2.6.10 Can't Open Initial Console on FC3 Joseph D. Wagner
2005-01-01 7:13 ` Mike Houston [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-01 16:05 Joseph D. Wagner
2005-01-03 3:09 ` Colin Charles
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=20050101021308.5a906479.mikeserv@bmts.com \
--to=mikeserv@bmts.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=technojoecoolusa@charter.net \
/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