[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: 7.1 networking problem
- From: ABrady <kcsmart kc rr com>
- To: redhat-list redhat com
- Subject: Re: 7.1 networking problem
- Date: Fri, 11 May 2001 11:05:35 -0500
On Fri, 11 May 2001 10:42:36 -0500 "Ian Truelsen" <linux35 hotmail com>
spake unto us:
> Alright. Here is my problem.
>
> I was running 7.0 on my little server, a 400MHz Intel Celeron, 128M RAM,
> 8
> Gig HD, Asus F2B MB, 3Com 905C NIC and D-Link DE528 NIC. All was well.
> Then
> I decided that I wanted the better USB support, etc. from the 2.4.x
> kernel.
> I thought the easiest way would be to download 7.1 and upgrade.
>
> I first tried it out on my workstation, a 1.1 GHz AMD Thunderbird,
> 512Meg
> RAM, 30Gig HD, generic MB with VIA KT133 chipset and RealTek 8139 NIC.
> Worked like a charm.
>
> On my server, the installation program didn't see my NICs. So I added
> the
> following lines to my modules.conf file:
> alias eth0 3c90x (for the 3Com)
> alias eth1 ne2k-pci (for the D-link)
> Then I ran depmod -a. No errors there. So I added the information for
> the
> adapters in the network configuration tool and rebooted. The 3Com, eth0,
> is
> supposed to activate at boot, but its initialization failed. When I
> tried to
> activate rp-pppoe over eth1, it did nothing.
>
> I thought they might have died somehow, so I tried reinstalling 7.0 and
> the
> installation system picked them up and set them up. Everything worked as
> well as it always did.
>
> Then I thought that it might have been the upgrade thing, so I backedup
> and
> tried a clean install of 7.1. Same problem. Same lack of solution.
>
> I have tried everything that my newbie brain and the various online
> resources could conceive of, and now I am hoping that some of you might
> be
> able to help me. I must say that I am very frustrated at the moment.
> Very.
>
> Thank you for listening and any advise would be most welcome.
The advice I was given, and the advice that worked goes like this:
Shut down and remove both cards.
Boot and let kudzu remove anything it sees.
Shut down and add in whatever card you want as eth0.
Boot and let kudzu set it up.
Shut down and add in the eth1 card.
Boot and let kudzu set it up.
Don't understand why that was required. Everything I've used since I added
my first Linksys _NON-ne2000_ board has been found on install or upgrade.
Not until 7.1 or wolverine did I get this problem. But, that method
certainly worked fine here.
--
Weird enough for government work.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]