From: Colin Charles <byte@aeon.com.my>
To: Development discussions related to Fedora Core
<fedora-devel-list@redhat.com>
Cc: mikeserv@bmts.com, Fedora List <fedora-list@redhat.com>,
jwendel10@comcast.net, zaitcev@redhat.com,
Linux Newbie <linux-newbie@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: RE: Kernel 2.6.10 Can't Open Initial Console on FC3
Date: Mon, 03 Jan 2005 11:09:28 +0800 [thread overview]
Message-ID: <1104721768.32006.180.camel@localhost.localdomain> (raw)
In-Reply-To: <3k77vr$fs05t3@mxip08a.cluster1.charter.net>
On Sat, 2005-01-01 at 10:05 -0600, Joseph D. Wagner wrote:
> They tell me there's a way to make it work without initrd, but it's
> ugly, messy, and not recommended:
>
> http://fedora.redhat.com/docs/udev/
>
> I haven't yet tested to see if it works with initrd and without
> support for hotplug devices, but from the documentation I've read my
> money is on no.
It does work. For quite a while on the PPC tree, we ended up doing some
manual MAKEDEVs to make it work. IIRC, booting with selinux=0 might have
been required as well
(this was in the pre-FC-3 rawhide days)
--
Colin Charles, byte@aeon.com.my
http://www.bytebot.net/
"First they ignore you, then they laugh at you, then they fight you,
then you win." -- Mohandas Gandhi
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-devel-list
next prev parent reply other threads:[~2005-01-03 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-01 16:05 Kernel 2.6.10 Can't Open Initial Console on FC3 Joseph D. Wagner
2005-01-03 3:09 ` Colin Charles [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-31 5:00 Joseph D. Wagner
2005-01-01 7:13 ` Mike Houston
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=1104721768.32006.180.camel@localhost.localdomain \
--to=byte@aeon.com.my \
--cc=fedora-devel-list@redhat.com \
--cc=fedora-list@redhat.com \
--cc=jwendel10@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=mikeserv@bmts.com \
--cc=zaitcev@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox