MINIX supports several Ethernet chips for networking over LAN, ADSL, and cable. These include Intel Pro/100, RealTek 8029 and 8139, AMD LANCE, and several 3Com chips. During setup you will be asked which Ethernet chip you have, if any.
You can determine what network adaptors your computer has by looking at your system's documentation.
Alternatively, from MINIX you can run netconf to see what network cards are recognized.
If you are using Windows, another way is to go to the Device Manager as follows:
Windows XP: Start > Control Panel > System > Hardware > Device Manager Windows Vista: Start > type device > The Device Manager shows up
System requires double clicking; the rest are single. Expand the + next to “Network adapters” to see what you have. Write it down. If you do not have a supported chip, you can still run MINIX, but without Ethernet.
If you are running Linux, you can run the following command to find out which Ethernet card you have.
lspci | grep Ether
You can use the…
netconf
…tool to select your network chip and configure your IP address automatically using DHCP, or manually by providing the address, netmask, gateway, and other information. That tool is limited to one network card only. More advanced settings have to be done by hand. To do that, edit “/etc/inet.conf”. Usually, the format is:
eth0 fxp 0 { default; };
where fxp is the name of the ethernet driver you want to start (it is the name of the process inet looks for, to talk to, for ethernet). Take a look at “/usr/etc/rc” how ethernet drivers are started. Currently, the choices are:
lance rtl8139 rtl8169 fxp e1000 dpeth dp8390 orinoco atl2 dec21140A
For details on inet.conf, please see the inet.conf manpage.
You will now be asked which (if any) of the available Ethernet drivers you want installed. An asterisk (*) will appear next to the closest match for your hardware. Please choose the numerical option (e.g., 1) that corresponds to your driver. The setup script will then save the corresponding driver keyword (e.g., fxp) and some options in the system file /etc/inet.conf.
If you are running MINIX 3 in a Virtual Machine and your Ethernet chip isn't detected, see the following table to determine which selection to make:
| Virtual Machine | NIC Selection |
|---|---|
| KVM | 9. Realtek 8139 based card (also emulated by KVM) |
| QEMU | 2. Realtek 8029 based card (also emulated by Qemu) |
| Bochs | 3. NE2000, 3com 503 or WD based card (also emulated by Bochs) |
| VMWare | 8. AMD LANCE (also emulated by VMWare and VirtualBox) |
| VirtualBox | 8. AMD LANCE (also emulated by VMWare and VirtualBox) |
| VirtualPC | 5. DEC Tulip 21140A in VirtualPC |
The following table tells you shows all the NIC options, as well as the driver name that corresponds to each option.
| NIC Selection | Corresponding Driver Name |
|---|---|
| 0. No Ethernet card (no networking) | (n/a) |
| 1. 3Com 501 or 3Com 509 based card | dpeth |
| 2. Realtek 8029 based card (also emulated by Qemu) | dp8390 |
| 3. NE2000, 3com 503 or WD based card (also emulated by Bochs) | dp8390 |
| 4. Attansic/Atheros L2 FastEthernet | atl2 |
| 5. DEC Tulip 21140A in VirtualPC | dec21140A |
| 6. Intel PRO/1000 Gigabit | e1000 |
| 7. Intel Pro/100 | fxp |
| 8. AMD LANCE (also emulated by VMWare and VirtualBox) | lance |
| 9. Realtek 8139 based card (also emulated by KVM) | rtl8139 |
| 10. Realtek 8169 based card | rtl8169 |
| 11. Different Ethernet card (no networking) | (n/a) |
After changing network settings, you'll need to reboot for them to take effect.