Device eth0 does not seem to be present

Sometimes, the Linux virtual opportunity under VMware is suddenly unable to access the Internet, and the virtual machines copied from other places will not be able to access the Internet. The specific error is similar to the article title, I found it online and tried it myself. The following methods are available:

 

In fact, there can be a simpler way to solve this problem. If the previous eth0 cannot be used, create an eth1, create it in setup, and then set the IP address and gateway, save and exit. Then, activate the NIC and run the following command:

Ifconfig eth1 up, and then restart the network service: Service Network restart. Now you should be able to ping the Internet. The experiment was successful!

 

 

When the virtual machine uses a template for Linux, the NIC configuration information (mainly Mac) is also copied, but the virtual server will allocate another MAC address, and an error will occur when it is enabled, error message: Device
"Eth0" does not seem to be present, delaying Initialization

Solution:

1. Open ETC/sysconfig/network-scripts/ficfg-eth0, make sure onboot should be yes,

2. Check if the MAC of the ficfg-eth0 matches the MAC of the ifconfig reality and modify the MAC of the ficfg-eth0.

3. Restart the service, including service NetworkManager restart and service network restart.

4. Then the system will automatically identify the NIC information and it will be OK.

System Startup log: bringing up interface eth0: pcnet32 device eth0 does not seem to be present, delaying initialization.

Ifconfig output: No eth0

System-> network configuration: eth0 exists and is inactive. An error occurred while trying to activate: pcnet32 device eth0 does not seem to be present.

There are solutions on the Internet. Http://blog.csdn.net/ccnp_Server/archive/2008/01/24/2063437.aspx

But it is too complicated. I did not try it and did not explain the cause of the problem. Later, I saw a foreigner at communities.vmware.com saying that he said, "What I found was that my modules. dep and modules. alias were empty, which live in/lib/modules/'uname-R '/". This reminds me that when I compile a module in the afternoon, I executed depmod, which will change modules. Dep and modules. Alias. At/lib/modules/'uname-R'/, check that there is only dependency information related to my module. It seems that this is because I executed the depmod command in an incorrect way. (I forgot what happened, as if I was in my working directory depmod.
My. Ko ).

It seems that the dependency information of the system module is lost, and the NIC Driver and other modules cannot be loaded at startup. Therefore, if you want to add your own modules to the system using modprobe, you should import your_module.ko modules to/lib/modules/'uname-R'/and depmod-. Finally, modprob your_module.

Solution: Run depmod under/lib/modules/'uname-R'/to regenerate modules. Dep and modules. Alias, and restart.

After installing Linux 6.0 with Vmware, the following prompt appears when the network cannot connect to the service network restart. Evice eth0 does not seem to be present Use the ifconfig command to view only the Lo status information. Use ifconfig-A as follows: -------------------------------------- Eth4 link encap: Ethernet hwaddr 00: 0C: 29: 75: 9d: A8 Inet ADDR: 192.168.1.20.bcast: 192.168.1.255 mask: 255.255.255.0 Inet6 ADDR: fe80: 20c: 29ff: fe75: 9da8/64 scope: Link Up broadcast running Multicast MTU: 1500 Metric: 1 RX packets: 4377 errors: 2 dropped: 3 overruns: 0 frame: 0 TX packets: 988 errors: 0 dropped: 0 overruns: 0 carrier: 0 Collisions: 0 FIG: 1000 RX Bytes: 451841 (441.2 kib) TX Bytes: 78718 (76.8 kib) Interrupt: 19 base address: 0x2000 Lo link encap: local loopback Inet ADDR: 127.0.0.1 mask: 255.0.0.0 Inet6 ADDR: 1/128 scope: Host Up loopback running MTU: 16436 Metric: 1 RX packets: 246 errors: 0 dropped: 0 overruns: 0 frame: 0 TX packets: 246 errors: 0 dropped: 0 overruns: 0 carrier: 0 Collisions: 0 txqueuelen: 0 RX Bytes: 27552 (26.9 kib) TX Bytes: 27552 (26.9 kib) ------------------------------------------------------ Eth0 changed to eth4, dizzy, thought for a long time, understood, because after I installed Linux, I copied the Linux Virtual Disk four times to meet my multi-system testing. Therefore, the copied NICs are changed to 1-4. I solved it like this, Change the script eth0 to eth4 first. [Root @ Linux ~] # Mv/etc/sysconfig/network-scripts/ifcfg-eth0/etc/sysconfig/network-scripts/ifcfg-eth4 [Root @ Linux ~] # Vi/etc/sysconfig/network-scripts/ifcfg-eth4 Device = "eth4" Hwaddr = "00: 0C: 29: 75: 9d: A8" # (Note: This is the eth4 Mac displayed after changing the MAC of eth0 to ifconfig-) Nm_controlled = "yes" Onboot = "yes" Broadcast = "192.168.1.255" Bootproto = "static" Ipaddr = "192.168.1.dr" Netmask = "255.255.255.0" Network = "192.168.1.0" Gateway = "192.168.1.1" After saving Service Network restart