"Interface eth0 doesn't exist. [ WARN ]" on boot-up
Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Looks indeed like a missing driver. You could try the 'forced' (nvidia) driver.
If you use the 2.6.16.27 kernel that goes with LFS 6.2, you can find it here:
Device Drivers -> Network device support -> Ethernet (10 or 100Mbit) -> EISA, VLB, PCI and on board controllers -> Reverse Engineered nForce Ethernet support (EXPERIMENTAL)
If you use a newer kernel it could be named differently, this is from a 2.6.20.4 kernel:
Device Drivers -> Network device support -> Ethernet (10 or 100Mbit) -> EISA, VLB, PCI and on board controllers -> nForce Ethernet support (NEW).
I had issues on Slackware 12 I could not get arround by configuring inet1.conf , modules.conf, loading drivers manually. eth0 was known as eth1 and eth0 did not exist.
Configuring the udev rule as stated here did the trick:
I have only one ethernet controller, and it is an Intel 8255xER/82551IT Fast Ethernet Controller, which to the best of my knowledge uses the eepro100 kernel driver.
Code:
# lsmod
Module Size Used by
af_packet 17160 0
evdev 9472 0
eepro100 28944 0
mii 5504 1 eepro100
I've tried setting up both static and DHCP (preferred) configurations for the eth0 interface. With the static setup, the interface is brought up, however I am unable to ping anything on my local network. The DHCP fails to even come up.
Thanks for the suggestions, however I still cannot my system's ethernet to work. Is there perhaps another file that I need to examine (that I have not already listed in my first post)? I want to set up my udev rules' file such that I do not have to hard-code the MAC address. I need to be able to use my distro on a multitude of systems, not just the one I am currently using as a test-bed.
To conclude, I tried both of your suggestions, and still no joy.
Btw, could it a be a kernel configuration issue? I have these options configured as follows:
I resolved the issue I was having with my system. Apparently the eepro100 is the correct driver to use for my network card when using an earlier kernel (2.4.27), however it is not the appropriate driver when running 2.6.17.13. For the later kernel I had to use the e100 driver.
This revelation came about when I tested my system with Knoppix, thus gleaning from the modules it loaded, as to which was the correct net driver for my system.
Anyhow, all is well now. Thank you everyone for your help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.