From: Ben Greear <greearb@candelatech.com>
To: Ganesh Venkatesan <ganesh.venkatesan@gmail.com>
Cc: "netdev@oss.sgi.com" <netdev@oss.sgi.com>
Subject: Re: ethtool -d no longer works for e1000
Date: Wed, 09 Mar 2005 15:09:33 -0800 [thread overview]
Message-ID: <422F822D.9010707@candelatech.com> (raw)
In-Reply-To: <5fc59ff3050309140910f3e492@mail.gmail.com>
Ganesh Venkatesan wrote:
> Ben:
>
> Are you using the e1000 that is included in the 2.6.11 kernel? ethtool
> -d eth? works fine for me. What else is different in your env?
I have patched the e1000 in my 2.6.11 kernel, but I see this -d problem
on other un-patched systems as well, so it can't be (just) my patches
that are the problem.
I also tried this on my x86-64 opteron system, running FC3. I
have not hacked up this kernel or user-space tools at all :)
[root@grok lanforge]# ethtool -i eth3
driver: e1000
version: 5.5.4-k2-NAPI
firmware-version: N/A
bus-info: 0000:02:08.0
[root@grok lanforge]# ethtool -d eth3
Cannot dump registers: Success
[root@grok lanforge]# uname -a
Linux grok 2.6.10-1.766_FC3smp #1 SMP Wed Feb 9 23:17:48 EST 2005 x86_64 x86_64 x86_64 GNU/Linux
I'm using ethtool 1.8 on this system.
What version of ethtool are you using?
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2005-03-09 23:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 21:35 ethtool -d no longer works for e1000 Ben Greear
2005-03-09 22:09 ` Ganesh Venkatesan
2005-03-09 23:09 ` Ben Greear [this message]
2005-03-09 23:13 ` Jon Mason
2005-03-09 23:31 ` Ben Greear
2005-03-09 23:42 ` Ben Greear
2005-03-11 8:54 ` Lennert Buytenhek
2005-03-11 8:55 ` Lennert Buytenhek
2005-03-09 22:59 ` Andre Tomt
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 22:25 cramerj
2005-03-09 23:02 ` Ben Greear
2005-03-10 0:35 cramerj
2005-03-10 0:54 ` Jon Mason
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=422F822D.9010707@candelatech.com \
--to=greearb@candelatech.com \
--cc=ganesh.venkatesan@gmail.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).