svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
ste(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_ste_load="YES" The driver provides support for PCI Ethernet
adapters and embedded controllers based on the Sundance Technolo‐
gies ST201 PCI Fast Ethernet controller chip. The Sundance ST201
uses bus master DMA and is designed to be a 3Com Etherlink XL
workalike. It uses the same DMA descriptor structure and is very
similar in operation, however its register layout is different.
The ST201 has a 64-bit multicast hash filter and a single perfect
filter entry for the station address. It supports both 10 and
100Mbps speeds in either full or half duplex using an MII trans‐
ceiver. The driver supports the following media types: Enable
autoselection of the media type and options. The user can manu‐
ally 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 dri‐
ver supports the following media options: Force full duplex oper‐
ation. Force half duplex operation. For more information on
configuring this device, see The driver supports Sundance Tech‐
nologies ST201 based Fast Ethernet adapters and embedded con‐
trollers including: D-Link DFE-530TXS D-Link DFE-550TX D-Link
DFE-580TX The following variables are available as both variables
and tunables: Maximum number of time to delay RX interrupts. The
valid range is 0 to 209712 in units of 1us, the default is 150
(150us). The value 0 effectively disables the RX interrupt mod‐
eration. The resolution of timer is about 3.2us so finer tuning
than 3.2us wouldn't be available. The interface does not need to
be brought down and up again before a change takes effect. A fa‐
tal initialization error has occurred. A fatal initialization
error has occurred. The device has stopped responding to the
network, or there is a problem with the network connection (ca‐
ble). 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 sup‐
port power management. Some operating systems place the con‐
troller in low power mode when shutting down, and some PCI BIOSes
fail to bring the chip out of this state before configuring 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 driver
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 net‐
work interface, you will have to perform a 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