Re: nfsroot doesn't work with intel card since

From: Rogier Wolff
Date: Mon Feb 13 2006 - 03:17:52 EST

On Sun, Feb 12, 2006 at 07:52:04PM -0800, H. Peter Anvin wrote:
> Followup to: <20060205215455.7622B1C8E46@xxxxxxxxxxxxxx>
> By author: carlos@xxxxxxxxxxxxxx (Carlos Carvalho)
> In newsgroup:
> >
> > 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 using the 2.6.11 version of
> > the driver (simply replacing the files in the tree). 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.
> >
> Care to try out the klibc tree?
> git://

What doesn't work? We have a bunch of machines that boot diskless.

zebigbos:~> cat /proc/version
Linux version 2.6.15 (erik@zebigbos) (gcc version 3.4.2) #1 SMP Tue Jan 17 11:02:22 CET 2006
zebigbos:~> df /
Filesystem Size Used Avail Use% Mounted on
67G 49G 18G 74% /

As far as I can remember we haven't had any problems in this area for
a long time.

This machine does have a slightly newer ethernet controller:

0000:02:07.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet Controller (rev 03)
0000:02:07.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet Controller (rev 03)


** R.E.Wolff@xxxxxxxxxxxx ** ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at