[Top] [All Lists]

RE: ethtool -d no longer works for e1000

To: "Ben Greear" <greearb@xxxxxxxxxxxxxxx>, "Jon Mason" <jdmason@xxxxxxxxxx>
Subject: RE: ethtool -d no longer works for e1000
From: "cramerj" <cramerj@xxxxxxxxx>
Date: Wed, 9 Mar 2005 16:35:47 -0800
Cc: "Ganesh Venkatesan" <ganesh.venkatesan@xxxxxxxxx>, <netdev@xxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
Thread-index: AcUlAbLuSvfhASemSfikF1cIghcqcwABfYLg
Thread-topic: ethtool -d no longer works for e1000
Ah!  Yes, if you're running ethtool 1.8, then this was an issue (or
rather, an annoyance) in e1000.c where we would default to mac_type =
e1000_undefined for any newer hardware.  Continuous updates to this file
for every piece of hardware we released got old pretty quick.  We've
since changed the default mac_type to e1000_82543, which has a basic set
of registers that haven't changed with each hardware release.  And
although the e1000_82546 mac_type exists, it isn't yet being assigned to
the 82546GB hardware (again, see e1000.c), thus the error.

Long story short, an updated ethtool should do the trick.


> -----Original Message-----
> From: netdev-bounce@xxxxxxxxxxx [mailto:netdev-bounce@xxxxxxxxxxx] On
> Behalf Of Ben Greear
> Sent: Wednesday, March 09, 2005 3:42 PM
> To: Jon Mason
> Cc: Ganesh Venkatesan; netdev@xxxxxxxxxxx
> Subject: Re: ethtool -d no longer works for e1000
> Ben Greear wrote:
> > Jon Mason wrote:
> >
> >> I don't see this problem at all on my 2.6.11-rc4-mm1 kernel
> >> proc).
> >
> >
> > I think I see the problem.  ethtool -d eth0 works for me,
> > but ethtool -d eth1 does not, even with both are e1000
> > NICs.  It appears it cannot handle reading the second NIC for
> > some reason?
> Errr, my bad.  The problem is more that the dual-port pro/1000 NICs
> don't seem to work, but the built-in e1000s do.
> The chipset that does not work correctly is: 82546GB
> The NICs with chipset: 82541EI seem to work just fine.
> Ben
> --
> Ben Greear <greearb@xxxxxxxxxxxxxxx>
> Candela Technologies Inc

<Prev in Thread] Current Thread [Next in Thread>