Add new network device

I'm playing around with Fedora Core 5, and like a twit I installed
without a network device in the system. I install the card after the
fact, then google for a while and get no where. I remember learning how
to do the same thing on debian potato long ago, I guess I need modprobe
and a new file in /etc/sysconfig/network/devices but I'm a little
stuck. Can anyone give me a shove in the right direction?

(E-Mail Removed) wrote:
> I'm playing around with Fedora Core 5, and like a twit I installed
> without a network device in the system. I install the card after the
> fact, then google for a while and get no where. I remember learning how
> to do the same thing on debian potato long ago, I guess I need modprobe
> and a new file in /etc/sysconfig/network/devices but I'm a little
> stuck. Can anyone give me a shove in the right direction?

It should load the driver automatically. Do you see your device in the
list when you do lspci? If so try running kudzu.

Maxim Yegorushkin wrote:
> It should load the driver automatically. Do you see your device in the
> list when you do lspci? If so try running kudzu.

Ah, thanks. lspci shows my card, running kudzu doesn't return anything,
but the database in hwconf does contain information describing the
device. I have eth0 configured to use 'ifup eth0' but doing so fails
with a device not present error. I'm thinking there supposed to be
something in sysconfig/networking/devices but kudzu didn't add anything
there and I can't find any documentation describing what should be
there?

(E-Mail Removed) wrote:
> Maxim Yegorushkin wrote:
> > It should load the driver automatically. Do you see your device in the
> > list when you do lspci? If so try running kudzu.
>
> Ah, thanks. lspci shows my card, running kudzu doesn't return anything,
> but the database in hwconf does contain information describing the
> device. I have eth0 configured to use 'ifup eth0' but doing so fails
> with a device not present error. I'm thinking there supposed to be
> something in sysconfig/networking/devices but kudzu didn't add anything
> there and I can't find any documentation describing what should be
> there?

Sorry, kudzu has nothing to do with it. My mistake.

There either should be a record and an alias in /etc/modprobe.conf or
the device driver should be loaded by HAL subsystem (previous fc
versions used hotplug).

Make sure you have the right driver. Try loading it with modprobe and
then setting it up. If it works add it to modprobe.conf.

http://www.linuxheadquarters.com/how...rkconfig.shtml

Maxim Yegorushkin wrote:
> (E-Mail Removed) wrote:
> > Maxim Yegorushkin wrote:
> > > It should load the driver automatically. Do you see your device in the
> > > list when you do lspci? If so try running kudzu.
> >
> > Ah, thanks. lspci shows my card, running kudzu doesn't return anything,
> > but the database in hwconf does contain information describing the
> > device. I have eth0 configured to use 'ifup eth0' but doing so fails
> > with a device not present error. I'm thinking there supposed to be
> > something in sysconfig/networking/devices but kudzu didn't add anything
> > there and I can't find any documentation describing what should be
> > there?
>
> Sorry, kudzu has nothing to do with it. My mistake.
>
> There either should be a record and an alias in /etc/modprobe.conf or
> the device driver should be loaded by HAL subsystem (previous fc
> versions used hotplug).
>
> Make sure you have the right driver. Try loading it with modprobe and
> then setting it up. If it works add it to modprobe.conf.
>
> http://www.linuxheadquarters.com/how...rkconfig.shtml

Ok I'm still stumped. I added another card figuring I can remove the
2nd when the 1st is working. /etc/modprobe.conf already had

alias eth0 de2048x (or something like that)

And lsmod shows that module in use by '0'. lsmod shows the same for
ne2k-pci, which I added to /etcmodprobe as:

alias eth1 ne2k-pci

Starting and stopping the network compains that the device doesn't seem
to be present for both interfaces. So I started looking through
/lib/modules/fc-whatever/net, I can't find anything that looks like a
network module, no ne2k-pci or any of the modules I remember from way
back like tulip, etc. Just for fun I ran 'insmod x.ko' where x is
random modules and got a bunch of errors that meant nothing to me.

I guess even after all these years no ones got around to documenting
simple stuff like how to add a network adapter?

(E-Mail Removed) wrote:
> > Make sure you have the right driver. Try loading it with modprobe and
> > then setting it up. If it works add it to modprobe.conf.

I found modprobe -l gives a nice list of available modules, so I
started at the top and loaded damn near every network module I could.
No idea how to tell if it works, although most of them failed with
"device or resource busy".

At this point I could have reinstalled several times over in the time
I've spent just adding a single adapter, if my frustration is showing
it's because I'm ready to throw this system through a wall.

(E-Mail Removed) wrote:
> (E-Mail Removed) wrote:
> > > Make sure you have the right driver. Try loading it with modprobe and
> > > then setting it up. If it works add it to modprobe.conf.

lspci shows a realtek 8029 adapter, which from I'm reading ne2k-pci
will run fine. The ne2k-pci module is the one it wanted to add itself,
and it appears in lsmod when I reboot. I have:

alias eth1 ne2k-pci

in modprobe.conf, but it says the device doesn't seem to exist when I
try ifup eth1. I have no idea what to do besides start over again with
mor enetwork cards.

(E-Mail Removed) wrote:
> (E-Mail Removed) wrote:
> > (E-Mail Removed) wrote:
> > > > Make sure you have the right driver. Try loading it with modprobe and
> > > > then setting it up. If it works add it to modprobe.conf.
>
> lspci shows a realtek 8029 adapter, which from I'm reading ne2k-pci
> will run fine. The ne2k-pci module is the one it wanted to add itself,
> and it appears in lsmod when I reboot. I have:
>
> alias eth1 ne2k-pci
>
> in modprobe.conf, but it says the device doesn't seem to exist when I
> try ifup eth1. I have no idea what to do besides start over again with
> mor enetwork cards.

What is the output of ifconfig eth1? If it shows something like

[max@localhost ~]$ /sbin/ifconfig eth1
eth1 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:18 Base address:0xcc00

Then you have the right driver. All you have to do is configure TCP/IP
stack. The easiest is to use NetworkManager on fc5.

(E-Mail Removed) wrote:
....
> Ok I'm still stumped. I added another card figuring I can remove the
> 2nd when the 1st is working. /etc/modprobe.conf already had
>
> alias eth0 de2048x (or something like that)
>
> And lsmod shows that module in use by '0'. lsmod shows the same for
> ne2k-pci, which I added to /etcmodprobe as:
>
> alias eth1 ne2k-pci
>
> Starting and stopping the network compains that the device doesn't seem
> to be present for both interfaces. So I started looking through
> /lib/modules/fc-whatever/net, I can't find anything that looks like a
> network module, no ne2k-pci or any of the modules I remember from way

But:
/lib/modules/2.6.16-1.2133_FC5/kernel/drivers/net/ne2k-pci.ko
looks like a network module.

> back like tulip, etc. Just for fun I ran 'insmod x.ko' where x is
> random modules and got a bunch of errors that meant nothing to me.
>
> I guess even after all these years no ones got around to documenting
> simple stuff like how to add a network adapter?

If lsmod shows ne2k-pci try: dmesg | less
and look for line with: ne2k-pci.c:
If after that line you can see eth0: or eth1: with some
informations like IRQ and tests passed and no errors, then driver
is working and maybe you should correct eth number in alias.
Otherwise the driver or the adapter is not usable.

Jarek P.

Jarek Poplawski wrote:
> If lsmod shows ne2k-pci try: dmesg | less
> and look for line with: ne2k-pci.c:

Thanks, that's helpful. It finally caused me to track down my screw
up... in the config I called it ETH0 rather than eth0, that's the whole
problem. Made it lower case and magically everything works. The really
supid part is that I must have typed 'eth0' a million times in my life
and never 'ETH0'. Thanks both of you.