NIC prob 4 Linux Stoogie!

[HeavyG]

They should create a new category for me. How come when I type modprobe I get 'lo' instead of 'eth0'. It shows my card in the "device manager" and says it is configured.
I turned off the BIOS PnP and re-installed but still the same problem. I have a Realtek 8029 card that needs the ne2k-pci module, which is listed under lsmod.

Upon booting, it cant initialize the NIC, that part fails. Everything I've done in Linux up to now fails. I'm getting wearyyyyyyyyyyyyyyyyy........... :o

[CRT_Monkey]

I've got the same card and never had a problem with it. What distro are ya runnin?

If your runnin mandrake (not sure if this is mandrake specific) make sure you have a DHCP daemon running and a program called "pump" installed. That's what I do and it works no prob.

Believe me, it aint the NIC. It has somethin to do with your system configuration. The RealTek card is well supported in Linux, that's a fact.

[HeavyG]

I'm sure it's not the card either. The problem happens under either LM 7.1 or 7.2.
I tried doing 'ifup eth0' and it says
'determining IP info for eth0 via dhcpcd....failed'

I'm not sure how to get the NIC working correctly. When i type modprobe, the first line listed says 'lo' instead of 'eth0' and lists IP and mask info. Any idea what 'lo' means?

Also, when I type 'modprobe eth0' I get the message '/etc/modules.conf is more recent than /lib/modules/2.2.17-21.mdk/modules.dep'
I have no clue what that means. I honestly dont see how Linux will become an everyday OS for the masses.

[Lorithar]

*umms*

modprobe is the command to get your kernel to load a module with its dependent children (other modules)

lsmod lists the modules that have been loaded.

ifconfig -a lists all your interfaces.
by default lo should be up and running before anything else. lo is your loopback interface.

Pump is the utility that RH installs use to get DHCP info from the DHCP server on the network.

IF the module shows under lsmod, then eth0 should be up. if lo is the only interface you can see under ifconfig -a then the problem is likely that your kernel startup is NOT starting the loopback on initialization. This would indicate to me that the system was installed as a desktop standalone, OR the kernel was rebuilt without networking options, incorrect networking options or suchlike.

please try to cut and paste the output from ifconfig -a, lsmod, netstat -rn and the contents of /proc/pci and /proc/devices (you will need to cat the /proc files to a text file as they are realtime filesystems and will not exist if you dual boot)

ifconfig -a >[filename] will put the output in the [filename] which can be read later and pasted into the browser (even if you have to copy it to a floppy and sneakernet it to the box yer posting from it will help enormously)