From: Ingo Molnar <mingo@elte.hu>
To: Mark Knecht <markknecht@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19-rt1 - failed to boot on AMD64
Date: Fri, 1 Dec 2006 09:19:36 +0100 [thread overview]
Message-ID: <20061201081936.GA24896@elte.hu> (raw)
In-Reply-To: <5bdc1c8b0611301504y6d5b957et350bad438c5e636c@mail.gmail.com>
* Mark Knecht <markknecht@gmail.com> wrote:
> OK, so 2.6.19-rt1 starts booting, gets to the point where it see the
> keyboard and mouse, and then apparently starts looking for a remote
> NFS server? I don't remember seeing this on earlier kernels.
if you have a Fedora 5/6-ish setup then you might be better off by
trying my yum rpm kernels, via:
cd /etc/yum.repos.d
wget http://people.redhat.com/~mingo/realtime-preempt/rt.repo
yum install kernel-rt.x86_64
by the looks of it something changed in the .config that prevented your
block device from being detected - and after that the kernel fell back
to other methods of booting.
another thing, is your /etc/fstab using labels, or explicit devices?
IIRC labels are needed i think by the new SATA/PATA code, a'ka:
LABEL=/ / ext3 noatime,nodiratime 1 1
Ingo
prev parent reply other threads:[~2006-12-01 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 23:04 2.6.19-rt1 - failed to boot on AMD64 Mark Knecht
2006-12-01 8:19 ` Ingo Molnar [this message]
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=20061201081936.GA24896@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox