From: Lazarus Long <lazarus@workspot.net>
To: linux-kernel@vger.kernel.org
Cc: lazarus@workspot.net, becker@webserv.gsfc.nasa.gov
Subject: (BUG) 3c509b and kernel 2.4.x
Date: Tue, 20 Feb 2001 12:13:59 -0800 [thread overview]
Message-ID: <E14VJAd-00007S-00@web1.workspot.net> (raw)
(I searched, but I have not seen this posted to the list before.)
Non-modular support for 3Com EtherLinkIII cards, specifically the ISA
3c509b, worked fine in kernel 2.2.18.
CONFIG_EL3=y
What worked in kernel 2.2.18 does not work in kernel 2.4.1 however.
http://groups.google.com (deja's successor) reveals that multiple
systems are having this problem, but there are no solutions listed
there (at least not among the English posts. I don't speak German,
but apparently many Linux users do.) I've spent quite a number of hours
attempting to resolve the matter, but with no success either.
Search for "Linux 2.4 3c509" shows the follow excerpts among the responses:
> [1.] Upon boot, the 2.4.1 kernel misconfigures one of two 3c509b NICs
> installed in my computer as "BNC" rather than "10baseT".
I get the same here.
> Boot messages for eth0 in kernel 2.2:
> eth0: 3c509 at 0x300 tag 1, 10baseT port, address 00 a0 24 e9 8d a1, IRQ 10.
> and in 2.4:
> eth0: 3c509 at 0x300, BNC port, address 00 a0 24 e9 8d a1, IRQ 10.
>
> i don't know why it says BNC port.. but it isn't right, it should be 10baseT
Again, similar results here. Incorrect port in 2.4.1 but correct in 2.2.18.
> I have three 3com cards( 1 3c590 Vortex, 1 3c900 Cyclone, 1 3c509B) which
> have no trouble with 2.2 kernels. But when I am trying to play with 2.4.0
> kernel, the 3c509 just can not load.
While my other NICs differ, the end result is that the 3c509 does not
work, yet the other NICs do, which is as I have experienced as well.
At the LILO prompt, I pass parameters as follows:
LILO boot: Linux241 ether=10,0x300,eth0 ether=7,0x320,eth1
and the (NE2000 clone) eth0 card works fine, but the 3c509b eth1 card does not.
LILO boot: Linux241 ether=7,0x320,eth0 ether=10,0x300,eth1
is not a solution, and merely causes the ethX values to flip-flop,
with the same failure. (Anticipated, but I'm mentioning it in case it
matters to anyone.)
And of course, I should mention that
LILO boot: Linux2218 ether=10,0x300,eth0 ether=7,0x320,eth1
works just fine, with the NE2000 clone on eth0 *and* the 3c509b on eth1.
(LILO boot: Linux2218 ether=7,0x320,eth0 ether=10,0x300,eth1
functions as expected as well, with the flip-flop and both cards working.)
There are features of kernel 2.4.x that I consider necessary (including,
but not limited to, netfilter) so using kernel 2.2.18 is not an adequate
solution here.
I've tried recompiling the kernel stripped down to bare minimums for
testing, but nothing seems to resolve this. I've also tested the kernel
on both a 486dx33 and a PII400, with the same results. I've also tried
using this as a single NIC in the ether=, for testing, even though
that is not a satisfactory situation here. Again, failure. I've even
physically removed the other NICs from the machine and acheived no success.
I don't see this driver mentioned in MAINTAINERS so I'm filing this
bug report to the list. (I'm uncertain if this is Donald Becker's
"baby" currently or not.) I'm omitting dmesg and .config etc. since
it doesn't seem to be necessary; anyone with a 3c509b will probably get
similar results with a 2.4.x kernel. If needed I can send any specifics
upon request.
Please CC: lazarus@workspot.com in any discussion, as I am not on the list.
--------------------------------------------------------------
Get "Your Linux Desktop on the Net" at http://www.workspot.com
next reply other threads:[~2001-02-20 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 20:13 Lazarus Long [this message]
2001-02-22 22:37 ` (BUG) 3c509b and kernel 2.4.x Petr Baudis
-- strict thread matches above, loose matches on Subject: below --
2001-02-22 20:21 Lazarus Long
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=E14VJAd-00007S-00@web1.workspot.net \
--to=lazarus@workspot.net \
--cc=becker@webserv.gsfc.nasa.gov \
--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