I did lsmod when I was booted to the CD and got e100 which I interpreted to be the driver for Intel [Ethernet Pro 100]. I did lsmod when I was booted to the HD and got e1000. I think this is the problem but what should I do now? I tried using modprobe but I'm not sure what I'm doing. I think we have the files for e100 on the HD.
From that it sounds like you have the correct module loaded, what do
you get when you follow the above suggestions for ifconfig -a or ip (depending on which package you have chosen to emerge) from the hard drive environment? There is something missing between the ifconfig and modprobe processes, but nothing that really screams out. If the module for the correct network card is loaded (the assumption is e100, post up the results you get from lspci so we can see if that is indeed correct) then you may want to check dmesg to see what the problem is. So, boot up, log in as root, then type: modprobe -r e100 modprobe e100 dmesg This should unload the e100 module if it's loaded, then load it, and finally let you view the output from dmesg to see if there were any blaring errors with the module. If there are none, you can then try: dhcpcd eth0 (or) dhclient eth0 Again, depending on what you chose to install. Alternatively at that point you could try: /etc/init.d/net.eth0 start To see if the service starts. But hopefully, long before this point, dmesg has given some extremely helpful and valuable information (such as it's eth1 instead of eth0 and so on). Good luck! -Chad /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
