M-VIA 1.0 supports the following network interface cards (NICs):
If you do not have one of the NICs listed above, you can use the the M-VIA loopback device within a single node.
This release of M-VIA was tested with kernel versions 2.2.5 and 2.2.12. A 2.2.12 or newer kernel is recommended.
The standard network card driver must either be compiled as a module (in which case M-VIA will replace it) or not compiled at all.
SMP support is turned on by default in 2.2 kernels. SMP support somewhat degrades network performance (a couple of microseconds) so you may want to turn if off. Do this by setting "Symmetric multi-processing support" to "n" under the "Processor type and features" configuration section when configuring your kernel.
gunzip -c mvia-X.XX.tar.gz | tar xvf - cd mvia-X.XX
This file is self-documenting. Normally the only variables you will need to set are the kernel version number and whether to compile for a SMP or single-processor machine.
Modules are placed by default in /lib/modules/<kernel-version-number>/net. Note that by default modules for all supported devices are installed. The modules are:
depmod -a <kernel-version-number>
This ensures the kernel module loader knows about the dependencies among the new modules.
/deventries for M-VIA devices.
M-VIA associates network devices with entries in /dev. By default, these are via_lo (via loopback), via_eth0, via_eth1, etc.:
/etc/conf.modulesto enable automatic loading of the M-VIA loopback module:
alias char-major-60 via_lo
If you changed the
MVIA_CHAR_MAJOR option in
the 60 in the above line with the appropriate major device number.
/etc/conf.modulesin the following format:
alias <dev> <via_module>
where dev is the name of the Linux device, e.g.
eth0, and via_module
The M-VIA device modules are backward compatible with the corresponding
Linux modules, however, they can not be loaded simultaneously. Remove
or comment out any entries in
conf.modules which share the same suffix
as an M-VIA device module, e.g. the M-VIA
via_tulip and standard
tulip module may not be loaded simultaneously.
The method used to configure network interfaces is Linux distribution
specific. On a Red Hat system create the appropriate
/etc/vip_hostsand edit for your network.
If you want to load the kernel modules manually, then ignore steps 7
through 9, above. If you wish to load modules using
should be aware of the following dependencies:
Thus, to use just the M-VIA loopback device you would run, from the modules directory:
insmod via_ka.o insmod via_lo.o
To use the M-VIA eepro100 driver you would run, from the modules directory:
insmod via_ka.o insmod via_ering.o insmod via_eepro100.o
If you use
modprobe to load modules, then these dependencies are