svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
jme(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_jme_load="YES" The device driver provides support for JMicron
JMC25x PCI Express Gigabit Ethernet controllers and JMicron
JMC26x PCI Express Fast Ethernet controllers. All LOMs supported
by the driver have TCP/UDP/IP checksum offload for both transmit
and receive, TCP segmentation offload (TSO), hardware VLAN tag
stripping/insertion features, Wake On Lan (WOL) and an interrupt
coalescing/moderation mechanism as well as a 64-bit multicast
hash filter. The JMC25x also supports Jumbo Frames (up to 9216
bytes), which can be configured via the interface MTU setting.
Selecting an MTU larger than 1500 bytes with the utility config‐
ures the adapter to receive and transmit Jumbo Frames. The dri‐
ver 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 Set 10Mbps opera‐
tion. Set 100Mbps (Fast Ethernet) operation. Set 1000baseTX op‐
eration over twisted pair. The driver supports the following me‐
dia options: Force full duplex operation. Force half duplex op‐
eration. For more information on configuring this device, see
The device driver provides support for the following Ethernet
controllers: JMicron JMC250 PCI Express Gigabit Ethernet con‐
troller JMicron JMC251 PCI Express Gigabit Ethernet with Card
Read Host controller JMicron JMC260 PCI Express Fast Ethernet
controller JMicron JMC261 PCI Express Gigabit Ethernet with Card
Read Host controller Tunables can be set at the prompt before
booting the kernel or stored in This tunable disables MSI support
on the Ethernet hardware. The default value is 0. This tunable
disables MSI-X support on the Ethernet hardware. The default
value is 0. The following variables are available as both vari‐
ables and tunables: This variable sets the maximum amount of time
to delay before sending a Tx completion interrupt, in microsec‐
onds. The accepted range is 1 to 65535; the default is 100
(100us). This variable sets the maximum number of outgoing pack‐
ets which may be coalesced together into a single Tx completion
interrupt. The accepted range is 1 to 255; the default is 8.
This variable sets the maximum amount of time to wait for addi‐
tional packets to arrive (for possible packet coalescing) before
firing an Rx completion interrupt, in microseconds. The accepted
range is 1 to 65535; the default is 100 (100us). This variable
sets the maximum number of incoming packets which may be coa‐
lesced into a single Rx completion interrupt. The accepted range
is 1 to 255; the default is 2. This variable sets the maximum
number of events that will be processed in a single batch before
the handler is requeued into a taskqueue. The accepted range is
10 to 255; the default value is 128 events. The interface does
not need to be brought down and up again before a change takes
effect. The driver was written by It first appeared in The dri‐
ver tries to avoid unnecessary station address reprogramming for
controllers that use eFuse to store station address. The number
of times that eFuse can be safely reprogrammed is 16 at most. In
addition, there is no way to restore the factory default station
address once the station address has been reprogrammed via eFuse.
It is highly recommended not to reprogram the station address and
it is the responsibility of the administrator to store the origi‐
nal station address in a safe place when station address is
changed. There are two known 1000baseT link establishment issues
with JMC25x. If the full mask revision number of JMC25x con‐
troller is less than or equal to 4 and the link partner enabled
the IEEE 802.3az Energy Efficient Ethernet feature, the con‐
troller will not be able to establish a 1000baseT link. Also, if
the length of the cable is longer than 120 meters, the controller
can not establish a 1000baseT link. The known workaround for
these issues is to force manual link configuration with 100baseTX
instead of relying on auto-negotiation. The full mask revision
number of controller can be checked with the verbose kernel boot
option. Use the lower nibble of the chip revision number to get
the full mask revision of the controller.