From: Andrew Morton <andrewm@uow.edu.au>
To: Juri Haberland <juri@koschikode.com>
Cc: r.verhees@chello.nl, linux-kernel@vger.kernel.org
Subject: Re: 3c900 card and kernel 2.4.3 <
Date: Mon, 14 May 2001 22:55:13 +1000 [thread overview]
Message-ID: <3AFFD5B1.82678220@uow.edu.au> (raw)
In-Reply-To: <20010504203107.DVQ23593.amsmta01-svc@[192.168.2.1]> <20010514111251.32556.qmail@babel.spoiled.org>
Juri Haberland wrote:
>
> r.verhees@chello.nl wrote:
> > Hi there,
> >
> > when i install kernel 2.4.3 or higher on my slackware
> > system the card (3c900) gets detected but doesn't do
> > anything, i also get the line "using NWAY 8" or something
> > like that (had to switch back to 2.4.2 to type e-mail)
> > wondered if anyone else had this problem and if there's
> > some way to solve it?
>
> Hi Ronnie,
>
> did you receive any answer?
>
> Do you use 10Base2 (aka cheaper net)?
> I do and after upgrading to 2.4.3 (I think) I had to force the driver to
> use the BNC connector though the card was configured (via the little config
> program supplied by 3com) to always use the BNC connector...
> This way I lost several hours to figure out why it wasn't working anymore and
> to discover that I have to build it as a module instead of having it compiled
> into the kernel because I couldn't make it work with kernel options - only
> with driver options...
> Any suggestions?
Yes, sorry.
The problem with earlier kernels was that autoselection
would notice the lack of 10baseT link beat and would then
advance on to trying AUI/SQE/10base2/etc. None of these
interfaces allow the driver to know if there's anything
connected and the driver consequently gets stuck on that
interface. The net effect: if you unplug the 10baseT
the driver gets stuck and you have to reboot.
So autoselection was turned off if the NIC was found
to have autonegotiation hardware. If you want to use
the other interfaces, you have to provide an option,
as described in Documentation/networking/vortex.txt.
For non-modular drivers things are less easy. If you
want to force it to use 10baseT (if_port zero) then
it should work OK if you cheat and use mem_start=0x400.
So `ether=0,0,0x400'.
For BNC, it should work just fine with `ether=0,0,1'.
If it doesn't, please shout at me. Compile the
driver with `static int vortex_debug = 7;' at line
183 and send me the boot logs.
Thanks.
-
next prev parent reply other threads:[~2001-05-14 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 20:31 r.verhees
2001-05-14 11:12 ` Juri Haberland
2001-05-14 12:55 ` Andrew Morton [this message]
2001-05-14 14:43 ` Juri Haberland
2001-05-15 21:58 ` 3c900 card and kernel 2.4.3 Juri Haberland
2001-05-15 22:12 ` Juri Haberland
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=3AFFD5B1.82678220@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=juri@koschikode.com \
--cc=linux-kernel@vger.kernel.org \
--cc=r.verhees@chello.nl \
/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
all inboxes | Powered by JetHome®