Yet another "failure of eth0 after install" questi

[plexustech]

I'm a first-time Gentoo user. I've been running other LINUX flavours for years, but now I've finally seen the light. Well, almost. A client introduced me to Gentoo, and he downloaded the basic system components for me to build a file server/ internet gateway machine. He also gave me what I think is called a "Stage 1" CD (after reading a few posts here) and I built the basic system up to the point where it boots and is ready to go.

<p>Anyway, even though ethernet was working perfectly while the system was being built, alas, it doesn't work now upon booting a stand-alone system. I've RTFM but still can't get it to go. I've removed all the "net.eth0" -type files from /etc/init.d and /etc/conf.d and so on, because even though they were there, they seemed to be broken, as the error messages I'd get upon booting up said that the eth0 device didn't exist. I was hoping to just run <i>net-setup</i> and then <i>rc-update add net.eth0 default</i> but that doesn't do me any good, because as soon as I run <i>net-setup</i>, it skips the configuration bits and immediately exits with the "do the ifconfig thing to see if we got it right" message. Needless to say, when I execute <i>ifconfig</i>, all I see is "lo" and nothing for "eth0". Can anyone advise me on what I need to do to perform a cleanse-the-junk-and-get-eth0-working operation? I've enabled network support in the kernel.
_________________
Idiot Filter: "Ya, we run the C++ operating system on a QNX platform over FDDI twisted pair at 600 MIPS." If they swallow that, hang up.

[barbar]

It seems your nic is not initialized. Did you compile your kernel with the right module ? If you are using genkernel did you emerge hotplug and add it to the rc script ?
what nic do you have ?

[plexustech]

[barbar]

Did you compile the driver into the kernel or as module ? If it is a module you must add it to the /etc/modules.autoload (or modprobe it manually).

What happens when you do ifconfig eth0 up ?

To find out if the NE2000 is the right driver you could boot from the livecd and list the loaded modlules with lsmod.

To me (and many others) it helped to boot with pci=noapic as kernel option (this seems to concern rtl8139).

[Gnufsh]

If you removed /etc/init.d/net.eth0, you're definately going to have some problems. It sounds to me like the kernel wasn't configured with the right driver for your network card. AFAIK, net-setup is not usefull except during install, you just configure /etc/conf.d/net and /etc/init.d/net.eth0 with bring up eth0. You can probably get these files back by re-emerging baselayout. Without those files, once you have the right driver compiled into your kernel, you can just dhcpcd eth0 if you're on a network with dhcp or use ifconfig if you're not.

[plexustech]

Found it: after using the LiveCd as a model and copying the net files, turns out it needed the EEPRO100 driver. However, there are 2 drivers listed to choose from, and one of them doesn't work at all.... so, trial and error. I've now got networking going on the LAN, and have moved on to the next problem of no ppp traffic over dialup, but that's for another thread.
_________________
Idiot Filter: "Ya, we run the C++ operating system on a QNX platform over FDDI twisted pair at 600 MIPS." If they swallow that, hang up.

[james2mart]

well ive got a linksys 10/100 fast ethernet adapter and i just used the tulip driver:

[lucky_strike]

I am having the same type of problem. After the install I can type in /sbin/ifconfig and I get the "eth0" output and the "lo" output. Then I try ping -c 3 www.yahoo.com, after which I get the "command not found" error. Then I type "dhcpcd eth0". This does get it to work but is there a way to have it work on start up w/o having to run "dhcpcd eth0" everytime? Also, on the install hotplug did everything. Maybe I didn't emerge it right. I need some ideas....Thanx.

[Gnufsh]

That is what the /etc/init.d/net.eth0 init script if for. Get /etc/conf.d/net configured and rc-update add net.eth0 default (or boot ot whatever).