From: Tom Popowski <tom@nga.com>
To: linux-kernel@vger.kernel.org
Subject: FA-311 / Natsemi problems with 2.4.1
Date: Fri, 09 Feb 2001 15:16:38 -0800 [thread overview]
Message-ID: <3A847A56.922ED4D@nga.com> (raw)
Please CC me, as I don't follow the list.
Please also forgive me if I'm stepping on toes. I'm in user-space.
I have had similar problems (network server XXXX not responding) with
both a Netgear FA311 (DP83815) and a Macronix (tulip) card when using
Donald Becker's drivers under 2.2.x kernels when connected to a Netgear
FE108 (100BaseTx-HD) hub. Both work correctly when dumbed-down to
10Mb. The fa311 driver from Netgear worked fine at 100Mb with a 2.2
kernel.
Under 2.4.x, fa311 doesn't compile and natsemi.c gives the messages
below. Again, I can (and do) force the card to 10Mb and it works fine
with the natsemi driver.
> I'm having problems with the natsemi drivers on my Netgear FA-311 card.
>
> On one host, I get lots of messages like this:
>
> eth1: Something Wicked happened! 0700.
> eth1: Something Wicked happened! 0740.
> eth1: Something Wicked happened! 0740.
> eth1: Something Wicked happened! 0740.
> eth1: Something Wicked happened! 0740.
> eth1: Something Wicked happened! 0740.
> eth1: Something Wicked happened! 0540.
>
--
Tom Popowski
Software Support
Northwest Geophysical Associates, Inc.
http://www.nga.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-02-09 23:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-09 23:16 Tom Popowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-12 8:52 FA-311 / Natsemi problems with 2.4.1 Jocelyn Mayer
2001-02-06 21:18 Jocelyn Mayer
2001-02-06 23:28 ` Jeff Garzik
2001-02-07 1:45 ` Ben Pharr
2001-02-06 18:28 Jocelyn Mayer
2001-02-06 19:31 ` Manfred Spraul
2001-02-06 2:29 Misc Mail for Erich
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=3A847A56.922ED4D@nga.com \
--to=tom@nga.com \
--cc=linux-kernel@vger.kernel.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