mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Carlos Carvalho <carlos@fisica.ufpr.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nfsroot doesn't work with intel card since 2.6.12.2/2.6.11
Date: Sun, 05 Feb 2006 21:19:30 -0500	[thread overview]
Message-ID: <1139192370.7870.8.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20060205215455.7622B1C8E46@fisica.ufpr.br>

On Sun, 2006-02-05 at 19:54 -0200, Carlos Carvalho wrote:
> We have several machines with Intel Corp. 82544EI Gigabit Ethernet
> Controller (Copper) (rev 02), as reported by lspci. They don't manage
> to mount the rootfs via nfs anymore. I've tried several combinations
> and the last one that works is 2.6.12.2 using the 2.6.11 version of
> the driver (simply replacing the files in the tree). 2.6.12.2 with its
> own driver doesn't work.
> 
> There seems to be a pattern: at each version the machine has more
> difficulty mounting the rootfs. Other machines using other ethercards
> but with the same server and filesystem work normally.
> 
> This is a showstopper for us since we cannot upgrade the kernel.
> 
> The same problem happens with 2.4, and the last combination that
> manages to boot is 2.4.32-pre1 with the 2.4.30 driver.
> 
> Any hints?

Not easy, given that you've told us nothing about your actual setup.
However at a quick guess: have you tried the 'tcp' mount option?

Cheers,
  Trond


  reply	other threads:[~2006-02-06  2:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-05 21:54 Carlos Carvalho
2006-02-06  2:19 ` Trond Myklebust [this message]
2006-02-13  3:52 ` H. Peter Anvin
2006-02-13  8:19   ` Rogier Wolff
2006-02-06  8:42 Knut Petersen
2006-02-06 14:39 ` Carlos Carvalho
2006-02-06 15:49   ` Knut Petersen
2006-02-06 20:40     ` Carlos Carvalho

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=1139192370.7870.8.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=carlos@fisica.ufpr.br \
    --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

all inboxes | Powered by JetHome®