From: Studierende der Universitaet des Saarlandes <masp0008@stud.uni-sb.de>
To: "Daniel A. Nobuto" <ramune@bigfoot.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: natsemi.c failure in 2.4.6
Date: Fri, 06 Jul 2001 10:56:24 +0000 [thread overview]
Message-ID: <3B459958.F25665A8@stud.uni-saarland.de> (raw)
> Found that in 2.4.6, Natsetmi card I have doesn't receive
> traffic anymore. It worked in 2.4.5, though.
>
> The natsemi card is forced to 10/half via mii-diag at boot,
> and given a different MAC address (due to some problems I had with
> the original MAC address and netbooting a sparc). Forcing it to
> 100/full didn't work, either.
Could you try what happens without any special options? Default MAC
address, without mii-diag.
> Basic mode control register 0x2100: Auto-negotiation disabled, with
> Speed fixed at 100 mbps, full-duplex.
> [PC Linux 2.4.6] <--> p10/100 hub] <--> [SS4 NetBSD 1.5]
> Speed fixed at 100 mbps, full-duplex.
> I'm advertising 05e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT
> Advertising no additional info pages.
> IEEE 802.3 CSMA/CD protocol.
> Link partner capability is 45e1: Flow-control 100baseTx-FD 100baseTx
> 10baseT-FD. 10baseT. Negotiation completed.
Something is wrong.
Are you sure it's a hub? The link partner ability says FullDuplex
capable, it's either a switch or the negotiation produced wrong results.
The natsemi nic advertises 5e1, but the speed is fixed at 100 mbps.
Probably a forced renegotiation after mii-diag changes is missing, and
the forced settings aren't used properly.
I'll look at it.
--
Manfred
next reply other threads:[~2001-07-06 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 10:56 Studierende der Universitaet des Saarlandes [this message]
2001-07-06 11:40 ` natsemi.c failure in 2.4.6 Daniel A. Nobuto
[not found] ` <3B45F966.351D1C44@colorfullife.com>
[not found] ` <3B463C71.B217B275@colorfullife.com>
2001-07-07 0:48 ` Daniel A. Nobuto
-- strict thread matches above, loose matches on Subject: below --
2001-07-06 10:39 Daniel A. Nobuto
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=3B459958.F25665A8@stud.uni-saarland.de \
--to=masp0008@stud.uni-sb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=ramune@bigfoot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.