From: Francois Cami <francois.cami@supelec.fr>
To: "Matthew W. Lowe" <swds.mlowe@home.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.3 - Module problems?
Date: Sun, 15 Apr 2001 19:43:11 +0200 [thread overview]
Message-ID: <3AD9DDAF.5E76F797@supelec.fr> (raw)
In-Reply-To: <3ADAC95A.6B35B8DE@home.com>
hi Matthew and everyone
I use a 3COM Etherlink III ISA and a 3C905C PCI in my firewall
box (i440BX mobo). (distro is slackware 7.1, kernels are either
2.2.19 or 2.4.3, modutils 2.3.1 (slackware 7.1 default) ).
The 3C905C was never a problem (and i guess your R8029 isn't either),
however to make the 3C509 ISA work, I had to disable PnP in the
card's firmware, with 3COM tools : see
http://www.3com.com/products/html/prodlist.html?family=570&cat=20&pathtype=download&tab=cat&selcat=Network%20Interface%20Cards%20%26%20Adapters
to download the DOS tools to configure your card without PnP, i.e.
manually
assigning an IRQ and address to it.
You'll have to declare to your BIOS that this particular IRQ is taken
by a non-PNP ISA card too.
Now it works well, whether i use a separate module or build the
module into the kernel.
I hope that helps.
François CAMI (new to the list)
francois.cami@supelec.fr
"Matthew W. Lowe" wrote:
>
> Hey, Thanks for all the help everyone. So far this is my exact
> configuration:
> Two NICs, 3COM Etherlink III ISA, Realtek 8029 PCI (Covered by the
> NE2000 PCI module). Both cards are setup for PnP, the modules have been
> built into the kernel. (It worked in my old version with them build into
> the kernel.)
>
> I have upgraded to the latest modutils, and it appeared to fix the
> problem with the 3COM Etherlink III card.
>
> Alan Cox:
> You mentioned turning PnP off if I was building the modules into the
> kernel? Is there something in the later versions of the kernel that is
> setup like that, or ?? (** didn't quite understand what you meant **)
>
> Thanks,
> Matt
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-04-15 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 10:28 2.4.3 - Module problems? Matthew W. Lowe
2001-04-15 17:43 ` Francois Cami [this message]
2001-04-15 17:53 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2001-04-16 1:25 Matthew W. Lowe
2001-04-15 7:17 ` Jeff Garzik
2001-04-16 1:40 ` Matthew W. Lowe
2001-04-15 12:51 ` Alan Cox
2001-04-16 7:42 ` ecksfantom
2001-04-16 2:43 ` Matthew W. Lowe
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=3AD9DDAF.5E76F797@supelec.fr \
--to=francois.cami@supelec.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=swds.mlowe@home.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox