All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: David Johnson <dj@david-web.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Can't make XFS work with 2.6.6
Date: Thu, 27 May 2004 13:03:15 -0400	[thread overview]
Message-ID: <200405271303.15932.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <200405271736.08288.dj@david-web.co.uk>

On Thursday, May 27, 2004 12:36 pm, David Johnson wrote:
> XFS is compiled in so it's not a module problem. Google says this error is
> usually caused by passing the wrong root parameter to the kernel, but I'm
> definitely giving the right root device.

Are you sure?  Make sure the device names haven't changed between your 2.4 and 
2.6 kernels.  This can happen if a new driver is compiled in that causes them 
to be reordered, or for other reasons.  XFS has been working fine in 2.6.6 
for me so far...

Jesse

  reply	other threads:[~2004-05-27 17:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 16:36 Can't make XFS work with 2.6.6 David Johnson
2004-05-27 17:03 ` Jesse Barnes [this message]
     [not found] ` <1085676905.5311.33.camel@buffy>
2004-05-27 16:57   ` David Aubin
2004-05-27 17:54   ` David Johnson
2004-05-27 18:00     ` David Aubin
2004-05-27 18:25       ` David Johnson
2004-05-27 19:04         ` David Aubin
2004-05-27 20:55           ` David Johnson
2004-05-27 20:56         ` Christoph Hellwig
2004-05-27 21:08         ` David Aubin
2004-05-27 21:47           ` David Johnson
2004-05-28 12:18             ` Andries Brouwer
2004-05-27 22:08         ` David Aubin
2004-05-27 22:44           ` David Johnson
2004-05-28  7:20           ` Christoph Hellwig
2004-05-28  8:12             ` Måns Rullgård
2004-05-27 20:06 ` Nathan Scott
2004-05-27 20:51 ` Christoph Hellwig
2004-05-27 20:54   ` Christoph Hellwig

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=200405271303.15932.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=dj@david-web.co.uk \
    --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.