Device eth0 does not seem to be present, delaying initialization.
by Nomad of Norad from LinuxQuestions.org on (#5B9N9)
Okay, I have a really old, netpliance sort of distro that was installed onto a really old machine, built on a really old version of CentOS, and recently it became necessary to migrate the hard drive out to a newer and better machine. It's been like pulling teeth obtaining a machine I could get this to work in, but I'm most of the way to getting it up and running again. My problem is, on the newest machine, when I boot the thing, I'm getting the following error:
Tulip device eth0 does not seem to be present, delaying initialization.
....and ethernet is not working. The big problem is, this box is one of those configure-and-command-it-from-the-built-in-web-interface things, so with the ethernet part of it not working... that kinda puts a damper on using the thing.
Several of the general-Linux-help pages I've come across telling me what to do when I get an error like this tell me to go to go remove /etc/udev/rules.d/70-persistent-net.rules and then reboot, and it will then recreate that with the correct ethernet device inserted. Trouble is, when I invoke RM /etc/udev/rules.d/70-persistent-net.rules it tells me that this directory or file does not exist.
Some have suggested the kernel doesn't recognize or support the particular make of ethernet port on the machine, but I'm guessing its also possible its simply tripping over some internal setting that's not letting it "see" that the ethernet port is different from what it had on the previous machine. In any event, the current machine is an HP Compaq 8200 Elite CMT, which appears to date from about when Windows 7 came out, and I'm trying to use CentOS 4.9 on it.
(I need to do a complete backup of its info, from its internal functions for that, and then update this thing through at least two major-update versions of the netpliance system, but I ran into a severe ram shortfall in the original machine, and it seems pretty likely this was preventing the backup from even starting, hence the drive migration.)
When I invoke ifconfig -a I see only bond0 as my ethernet, with HWaddr 00:00:00:00:00:00
Anyway, I'm at a loss as to what to do.
Tulip device eth0 does not seem to be present, delaying initialization.
....and ethernet is not working. The big problem is, this box is one of those configure-and-command-it-from-the-built-in-web-interface things, so with the ethernet part of it not working... that kinda puts a damper on using the thing.
Several of the general-Linux-help pages I've come across telling me what to do when I get an error like this tell me to go to go remove /etc/udev/rules.d/70-persistent-net.rules and then reboot, and it will then recreate that with the correct ethernet device inserted. Trouble is, when I invoke RM /etc/udev/rules.d/70-persistent-net.rules it tells me that this directory or file does not exist.
Some have suggested the kernel doesn't recognize or support the particular make of ethernet port on the machine, but I'm guessing its also possible its simply tripping over some internal setting that's not letting it "see" that the ethernet port is different from what it had on the previous machine. In any event, the current machine is an HP Compaq 8200 Elite CMT, which appears to date from about when Windows 7 came out, and I'm trying to use CentOS 4.9 on it.
(I need to do a complete backup of its info, from its internal functions for that, and then update this thing through at least two major-update versions of the netpliance system, but I ran into a severe ram shortfall in the original machine, and it seems pretty likely this was preventing the backup from even starting, hence the drive migration.)
When I invoke ifconfig -a I see only bond0 as my ethernet, with HWaddr 00:00:00:00:00:00
Anyway, I'm at a loss as to what to do.