From: Zwane Mwaikambo <zwane@linuxpower.ca>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: jgarzik@pobox.com, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][2.5][RFT] 3c509.c extra ethtool features
Date: Mon, 7 Oct 2002 08:41:25 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0210070836580.24365-100000@montezuma.mastecende.com> (raw)
In-Reply-To: <200210071040.MAA18108@harpo.it.uu.se>
On Mon, 7 Oct 2002, Mikael Pettersson wrote:
> 3c509-TPO, ca 1994 vintage, ethtool eth0 output:
>
> Settings for eth0:
> Supported ports: [ TP AUI ]
> Supported link modes: 10baseT/Half 10baseT/Full
> Supports auto-negotiation: No
> Advertised link modes: Not reported
> Advertised auto-negotiation: No
> Speed: 10Mb/s
> Duplex: Half
> Port: Twisted Pair
> PHYAD: 0
> Transceiver: internal
> Auto-negotiation: off
> Current message level: 0x00000002 (2)
> Link detected: yes
Cool.
> So far so good (except it reports AUI although it has none).
Hmm, that info is from the card registers, perhaps your board just doesn't
have the interface wired?
> Unfortunately, this simple query killed the link, and I had to
> down/up eth0 to get it back.
Could be a missing EL3WINDOW change somewhere, i don't write to any
registers in the query path. I'll check that out.
> Next I tried ethtool -s to change some settings (port, speed,
> full duplex) and all returned errors. I kind of expected that.
> Next I tried to rlogin to this box from another: complete kernel hang :-(
Could be one of the -EINVALs i think i need more sanity checks in there.
> I may be able to test some more later this week, on a slightly newer
> 3c509(B?) TP/AUI combo NIC.
Thanks,
Zwane
--
function.linuxpower.ca
next prev parent reply other threads:[~2002-10-07 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 10:40 [PATCH][2.5][RFT] 3c509.c extra ethtool features Mikael Pettersson
2002-10-07 12:41 ` Zwane Mwaikambo [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-06 21:00 Zwane Mwaikambo
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=Pine.LNX.4.44.0210070836580.24365-100000@montezuma.mastecende.com \
--to=zwane@linuxpower.ca \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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).