Linux. vmwrokstation6 Linux lost device pcnet32 device eth0 does not seem to be present

Features:

System Startup log: Bringing up interface eth0: pcnet32 device eth0 does not seepresent, delaying initialization. Ifconfig output: No device interface eth0 is found in the output.

 

 

Cause: Unknown
I suspect that it was caused by modifying the hostname!
General process for modifying the hostname in Linux:
# Hostname newhostname
# Vi/etc/sysconfig/Network
Hostname = newhostname
# Vi/etc/hosts
127.0.0.1 newhostname

I modified it in Gui mode. In the network configuration window, the DNS tab is hostname, and some other operations have been performed since then, when the configuration information is activated, the following error occurs :...... I don't know if there is a scientific basis, but I don't know about Linux!

Then observe and find the most mentioned features, G for a long time, find the only meaningful message:
Modify/etc/modprobe. conf and change alias eth0 vmincs to alias eth0 pcnet32.
Restart the NIC/etc/init. d/network start

I didn't use this method, but thought it was more scientific, so it was printed here.
I tried to solve this problem in a few minutes:
1. Use the conventional method to modify the hostname again, which is invalid after restart;
2. Delete the device driver in Linux and reinstall it (configured through the network configuration GUI). The device driver is not valid after restart;
3. Delete the VM Nic and restart. Shut down the system again, add the VM Nic, and start the system. The system is invalid;
4. Delete the VM Nic, delete the device driver in Linux, restart the system, add the VM Nic, and manually add the device driver in Linux;
5. I added 2nd NICs to the VM host. After the system was started, the fault was solved!

Ifconfig output result:
Eth0 link encap: Ethernet hwaddr 00: 0C: 29: 8e: 1A: 53
Inet ADDR: 192.168.2.138 bcast: 255.255.255.255 mask: 255.255.255.0
Inet6 ADDR: fe80: 20c: 29ff: fe8e: 1a53/64 scope: Link
Up broadcast running Multicast MTU: 1500 Metric: 1
RX packets: 7174 errors: 0 dropped: 0 overruns: 0 frame: 0
TX packets: 85 errors: 0 dropped: 0 overruns: 0 carrier: 0
Collisions: 0 txqueuelen: 0
RX Bytes: 1429456 (1.3 MIB) TX Bytes: 15525 (15.1 kib)

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: 7421 errors: 0 dropped: 0 overruns: 0 frame: 0
TX packets: 7421 errors: 0 dropped: 0 overruns: 0 carrier: 0
Collisions: 0 txqueuelen: 0
RX Bytes: 10162061 (9.6 MIB) TX Bytes: 10162061 (9.6 MIB)

Peth0 link encap: Ethernet hwaddr Fe: FF
Inet6 ADDR: fe80: fcff: FFFF: feff: FFFF/64 scope: Link
Up broadcast running noarp MTU: 1500 Metric: 1
RX packets: 49859 errors: 0 dropped: 0 overruns: 0 frame: 0
TX packets: 4152 errors: 0 dropped: 0 overruns: 0 carrier: 0
Collisions: 0 FIG: 1000
RX Bytes: 18832266 (17.9 MIB) TX Bytes: 591518 (577.6 kib)
Interrupt: 19 base address: 0x2000

Vif0.0 link encap: Ethernet hwaddr Fe: FF
Inet6 ADDR: fe80: fcff: FFFF: feff: FFFF/64 scope: Link
Up broadcast running noarp MTU: 1500 Metric: 1
RX packets: 4109 errors: 0 dropped: 0 overruns: 0 frame: 0
TX packets: 30611 errors: 0 dropped: 0 overruns: 0 carrier: 0
Collisions: 0 txqueuelen: 0
RX Bytes: 583758 (570.0 kib) TX Bytes: 8508834 (8.1 MIB)

Xenbr0 link encap: Ethernet hwaddr Fe: FF
Up broadcast running noarp MTU: 1500 Metric: 1
RX packets: 20729 errors: 0 dropped: 0 overruns: 0 frame: 0
TX packets: 0 errors: 0 dropped: 0 overruns: 0 carrier: 0
Collisions: 0 txqueuelen: 0
RX Bytes: 2981923 (2.8 MIB) TX Bytes: 0 (0.0 B)

Someone said this was a strange wireless network card on the Internet. I also got rid of the configuration file of wireless devices!