From: Ben Greear <greearb@candelatech.com>
To: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: ethtool -d no longer works for e1000
Date: Wed, 09 Mar 2005 13:35:51 -0800 [thread overview]
Message-ID: <422F6C37.8090202@candelatech.com> (raw)
I tried this with FC2's 2.6.10-1.770_FC2smp kernel and with my own
slightly hacked 2.6.11 kernel. Both give this response:
ethtool -d eth0
Cannot dump registers: Success
I am quite certain this used to work, and used to show me
the PCI bus speed and other nice details...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2005-03-09 21:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 21:35 Ben Greear [this message]
2005-03-09 22:09 ` ethtool -d no longer works for e1000 Ganesh Venkatesan
2005-03-09 23:09 ` Ben Greear
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=422F6C37.8090202@candelatech.com \
--to=greearb@candelatech.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).