AMD Lance NIC Driver issues on Minix

Today, we found a strange problem on Minix on VMware. After using a static IP address, the external network cannot ping Minix. Minix must ping the external network before pinging it. The same problem also occurs on Google groups:

I have Minix3 on a VMWare virtual machine... If I try to ping the box itself (192.168.1.134), I don't get a reply unless I first ping the box back from the minix machine. I am running in bridged mode and I can get to the internet fine from the minix machine, but other machines cannot communicate with the minix machine unless the minix machine first communicates with the caller. has anyone had similar issues? It is driving me crazy.

Because most people install and run Minix on VMware, the NIC Driver of VMware on Minix is particularly important, at least more important than other Nic drivers. The problem encountered here is caused by the AMD Lance NIC of VMware on Minix. The lance driver must be loaded in the first 16 MB of memory, if you load the NIC after the system starts, the lance will be loaded to 16 MB, causing the driver to not work. When we see this, we will immediately think that if we load the driver beforehand (within 16 MB), we will avoid the above problems, such as before loading the file system? Well, this is a rogue method, but it is not the best.

The solution on Minix 3.1.5 is to run the following command to restart the lance DRIVER:

# service refresh lance

In Minix 3.1.3, it is unfortunate that the NIC Driver (lance) will not work completely, but it is not difficult for many hackers who use Minix to follow the comp. OS. this Fix on minix for Minix 3.1.3a, VMware, and Networking can solve this problem on Minix 3.1.3.