From: Steffen Klassert <klassert@mathematik.tu-chemnitz.de>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 3c59x concerns on 2.4->2.6 update?
Date: Sat, 19 Mar 2005 11:22:50 +0100 [thread overview]
Message-ID: <20050319102250.GA11557@bayes.mathematik.tu-chemnitz.de> (raw)
In-Reply-To: <20050318103418.GA14636@merlin.emma.line.org>
In 2.6.11 ethtool data should be available. Please let me know if
you are using 2.6.11 and ethtool does not work with your card.
I have no Tornado card to test but with 3c905/3c905B cards and
options=0x204 configured, mii-diag reports:
Auto-negotiation disabled, with Speed fixed at 100 mbps, full-duplex.
I suppose you talking about 3c905C Tornado cards
(3c900 cards are not of Tornado type).
Steffen
On Fri, Mar 18, 2005 at 11:34:19AM +0100, Matthias Andree wrote:
> Hi,
>
> I've recently upgraded a router which has three 3Com900C Tornado cards
> revisions 74 and 78 from Linux 2.4 to 2.6.
>
> IIRC, Linux 2.4 allowed to report if the link beat was sensed to be 10
> or 100 mbps, Linux 2.6 does not. One of these cards is attached to
> peculiar network gear and needs to be forced to 100baseTx-FD.
> I configured options=0x204 for that interface, which sorta worked;
> vortex-diag and mii-diag still report autonegotiation were enabled.
> Strange.
>
> ethtool (I tried v2 and v3) does not appear to work at all for 3C900C
> cards, "No data available" if run without options.
>
> Any insight into these would be appreciated,
>
> --
> Matthias Andree
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-03-19 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 10:34 Matthias Andree
2005-03-19 10:22 ` Steffen Klassert [this message]
2005-03-19 12:27 ` Matthias Andree
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=20050319102250.GA11557@bayes.mathematik.tu-chemnitz.de \
--to=klassert@mathematik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=matthias.andree@gmx.de \
/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
all inboxes | Powered by JetHome®