public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
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 03:17:45 -0400	[thread overview]
Message-ID: <3AD94B19.C73357A1@mandrakesoft.com> (raw)
In-Reply-To: <3ADA49F0.A412EAA@home.com>

"Matthew W. Lowe" wrote:
> I just tried to upgrade from whatever kernel comes with redhat to 2.4.3.
> The build, install and such was smooth. When I got to starting up,
> everything appeared to work, until it got to my NIC cards. Neither of
> them loaded properly. I've built in the EXACT same module for the NICs
> as I did the previous kernel. They were the NE2000 PCI module and the
> 3C59X module. The two NICs I have are: Realtek 8029 PCI, 3COM Etherlink
> III ISA. Both are PNP, the etherlink is NOT the one with the b extention
> at the end.

Maybe this is a typo or maybe not -- "3c509" is for Etherlink III ISA,
"3c59x" is for recent 3com PCI/EISA busmastering 10/100 NICs.

-- 
Jeff Garzik       | "Give a man a fish, and he eats for a day. Teach a
Building 1024     |  man to fish, and a US Navy submarine will make sure
MandrakeSoft      |  he's never hungry again." -- Chris Neufeld

  reply	other threads:[~2001-04-15  7:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-16  1:25 2.4.3 - Module problems? Matthew W. Lowe
2001-04-15  7:17 ` Jeff Garzik [this message]
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
2001-04-18 23:49     ` How to tune TCP for heavily loaded sendmail box Andrew Chan
2001-04-19  7:07       ` Matti Aarnio
  -- strict thread matches above, loose matches on Subject: below --
2001-04-16 10:28 2.4.3 - Module problems? Matthew W. Lowe
2001-04-15 17:43 ` Francois Cami
2001-04-15 17:53   ` Jeff Garzik

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=3AD94B19.C73357A1@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --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