> -----Original Message----- > From: fedora-list-bounces@xxxxxxxxxx > [mailto:fedora-list-bounces@xxxxxxxxxx] On Behalf Of Betti > Ann & Preston Smith > Sent: Tuesday, May 25, 2004 10:18 AM > To: duncanbrown@xxxxxxxxxxxxxxxxx; For users of Fedora Core releases > Subject: Re: FC2 - No eth0 > > Further to previous discussions on this, I received the > message "module ne could not be found" while trying to > activate the eth0 device. > > How do i install module ne and where do i find it? This is > another part of the learning curve .... I am sure it has > something to do with rpm but I do not know what > > Preston > > > At 12:17 PM 5/24/04, you wrote: > > >Betti Ann & Preston Smith said: > > > > > During boot and when I try to manually install the card I get "ne > > > device eth0 does not seem to be present" > > > > > > Where do I go from here? > > > >lspci output > >contents of any /etc/sysconfig/network-scripts/ifcfg-eth* > file contents > >of /etc/modprobe.conf > > > >did i forget anything, guys? > > --- > Betti Ann & Preston Smith, Head of St Margaret's Bay, NS, > prsmith@xxxxxxxxxxxxxxx > 1962 MGA 1600 MK II, 1980 MGB Limited Edition > 2002 Damon Challenger 335 Motor Home on 2001 Ford V-10 20,500 > lb chassis > > > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list > Generally, there is a alias in your /etc/modprobe.conf (or modules.conf on prior releases) that points eth0 to the kernel module (driver) for your specific network card. Here is example: alias eth0 e100 This is for an Intel based card. /dev/eth0 is using the e100 kernel module.
