From: "Matthew W. Lowe" <swds.mlowe@home.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.3 - Module problems?
Date: Sun, 15 Apr 2001 20:43:24 -0600 [thread overview]
Message-ID: <3ADA5C4C.748D0916@home.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0104160037230.19394-100000@maelstrom.localhost>
I installed that, it fixed my one NIC... The 3COM. Or I assume it did, because
it shows up in ifconfig now, unlike the other one Unfortunately I still can't
ping the local host (destination net unreachable). I think that might just be a
byproduct of my main external card not working. Anyway, I double checked the
settings in both config files for the old kernel and the new one, the realtek
should be covered under the ne2000 pci mod. I built this directly into the
kernel and it still doesn't seem to be working. Anyone have any ideas?
Thanks,
Matt
ecksfantom@home.com wrote:
> I had the same problem when i upgraded to 2.4.2.
> Upgrading to the latest modutils
> (ftp://ftp.kernel.org/pub/linux/utils/modutils/v2.4/modutils-2.4.5.tar.gz)
> should get you going again.
>
> ~Jarrod
>
> On Sun, 15 Apr 2001, 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.
> >
> > Any help would be greatly appriciated.
> >
> > 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/
> >
>
> -
> 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 8:29 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
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 [this message]
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=3ADA5C4C.748D0916@home.com \
--to=swds.mlowe@home.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