From: Benjamin LaHaise <bcrl@redhat.com>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: Linux Kernel Maillist <linux-kernel@vger.kernel.org>,
linux-ns83820@kvack.org
Subject: Re: problem w/ auto negotiate & ns83820 & netgear fsm726s switch
Date: Wed, 12 Mar 2003 13:15:31 -0500 [thread overview]
Message-ID: <20030312131531.F16642@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0303120908470.21265@filesrv1.baby-dragons.com>; from babydr@baby-dragons.com on Wed, Mar 12, 2003 at 09:11:02AM -0500
On Wed, Mar 12, 2003 at 09:11:02AM -0500, Mr. James W. Laferriere wrote:
> The switch reports negotiating ...
> Port Name Link On/Off State Rate/Duplex Flow Ctrl
> 26GB Not Defined Up On Forwarding (10 Full) (Disabled)
>
> ns83820 reports , eth0: link now 1000F mbps, full duplex and up.
...
> I am quite aware that this could well be a difficulty in the
> switch still . So I am looking for pointers on where to look ?
> I already tried the netgear suport site ;-} . That is why I am
> running the lastest code for the switch (1.0.4) .
It's entirely possible the card has a different polarity for the phy bits
as compared to the fibre card (Netgear) that the driver is already tested
on. Also, I've only managed to test on a cisco switch -- is there any
other hardware you can test against (ie using the fibre cable for cross
over) to narrow things down? Enabling debug and dumping the status bits
might hint as to what has to be changed. Thankfully Trendnet seems to
have programmed the subsystem id, so I'll be able to include the change
automatically.
-ben
next prev parent reply other threads:[~2003-03-12 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 14:11 problem w/ auto negotiate & ns83820 & netgear fsm726s switch Mr. James W. Laferriere
2003-03-12 18:15 ` Benjamin LaHaise [this message]
2003-03-13 14:34 ` Mr. James W. Laferriere
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=20030312131531.F16642@redhat.com \
--to=bcrl@redhat.com \
--cc=babydr@baby-dragons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ns83820@kvack.org \
/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