svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
vr(4)
To compile this driver into the kernel, place the following lines
in your kernel configuration file: Alternatively, to load the
driver as a module at boot time, place the following line in
if_vr_load="YES" The driver provides support for PCI Ethernet
adapters and embedded controllers based on the VIA Technologies
VT3043 Rhine I, VT86C100A Rhine II, and VT6105/VT6105M Rhine III
Fast Ethernet controller chips. The VIA Rhine chips use bus mas‐
ter DMA and have a descriptor layout designed to resemble that of
the DEC 21x4x chips. The register layout is different however
and the receive filter in the Rhine chips is much simpler and is
programmed through registers rather than by downloading a special
setup frame through the transmit DMA engine. Transmit and re‐
ceive DMA buffers must be longword aligned. The Rhine chips are
meant to be interfaced with external physical layer devices via
an MII bus. They support both 10 and 100Mbps speeds in either
full or half duplex. The driver supports the following media
types: Enable autoselection of the media type and options. The
user can manually override the autoselected mode by adding media
options to the file. Set 10Mbps operation. The option can also
be used to select either or modes. Set 100Mbps (Fast Ethernet)
operation. The option can also be used to select either or
modes. The driver supports the following media options: Force
full duplex operation. Force half duplex operation. Note that
the 100baseTX media type is only available if supported by the
adapter. For more information on configuring this device, see
The driver supports VIA Technologies Rhine I, Rhine II, and Rhine
III based Fast Ethernet adapters including: AOpen/Acer ALN-320 D-
Link DFE520-TX D-Link DFE530-TX Hawking Technologies PN102TX
Soekris Engineering net5501 The following variables are available
as variables: Display lots of useful MAC counters maintained in
the driver. A fatal initialization error has occurred. A fatal
initialization error has occurred. The device has stopped re‐
sponding to the network, or there is a problem with the network
connection (cable). The driver failed to allocate an mbuf for
the receiver ring. The driver failed to allocate an mbuf for the
transmitter ring when allocating a pad buffer or collapsing an
mbuf chain into a cluster. This message applies only to adapters
which support power management. Some operating systems place the
controller in low power mode when shutting down, and some PCI
BIOSes fail to bring the chip out of this state before configur‐
ing it. The controller loses all of its PCI configuration in the
D3 state, so if the BIOS does not set it back to full power mode
in time, it will not be able to configure it correctly. The dri‐
ver tries to detect this condition and bring the adapter back to
the D0 (full power) state, but this may not be enough to return
the driver to a fully operational condition. If you see this
message at boot time and the driver fails to attach the device as
a network interface, you will have to perform second warm boot to
have the device properly configured. Note that this condition
only occurs when warm booting from another operating system. If
you power down your system prior to booting the card should be
configured correctly. The device driver first appeared in The
driver was written by The driver always copies transmit mbuf
chains into longword-aligned buffers prior to transmission in or‐
der to pacify the Rhine chips. If buffers are not aligned cor‐
rectly, the chip will round the supplied buffer address and begin
DMAing from the wrong location. This buffer copying impairs
transmit performance on slower systems but cannot be avoided. On
faster machines (e.g. a Pentium II), the performance impact is
much less noticeable.