netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: cliff white <cliffw@osdl.org>
To: netdev@oss.sgi.com
Subject: Ethtool doesn't work on Debian unstable?
Date: Thu, 10 Mar 2005 13:54:35 -0800	[thread overview]
Message-ID: <20050310135435.23af10b8@es175> (raw)


This is wierd. I know I am doing something Real Stupid, but i can't figure it out.

Two systems.  2.6.11 kernel on both systems. 
One runs RedHat 9.0, and ethtool Just Works:
 ethtool -g eth0
Ring parameters for eth0:
Pre-set maximums:
RX:             256
RX Mini:        0
RX Jumbo:       0
TX:             256
Current hardware settings:
RX:             64
RX Mini:        0
RX Jumbo:       0
TX:             64
--------------------
The other is Debian unstable, and nothing works:
 ethtool -g eth0
Ring parameters for eth0:
Cannot get device ring settings: Operation not supported
------------------------
If i strace, i see the ioctl failing on the Debian side:
7657  munmap(0xb7fd6000, 75321)         = 0
7657  socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
7657  fstat64(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 5), ...}) = 0
7657  mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7fe8000
7657  write(1, "Ring parameters for eth1:\n", 26) = 26
7657  ioctl(3, SIOCETHTOOL, 0xbffffd30) = -1 EOPNOTSUPP (Operation not supported)
7657  dup(2)                            = 4
------------------------
Can anyone help me here? I'd like to use Debian for this testing, but so far, no love.
cliffw


-- 
"Ive always gone through periods where I bolt upright at four in the morning; 
now at least theres a reason." -Michael Feldman

             reply	other threads:[~2005-03-10 21:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10 21:54 cliff white [this message]
2005-03-10 22:15 ` Ethtool doesn't work on Debian unstable? Andre Tomt
2005-03-10 22:39   ` cliff white

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=20050310135435.23af10b8@es175 \
    --to=cliffw@osdl.org \
    --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).