Difference between revisions of "Kernel"

From GhostBSD Wiki
Jump to: navigation, search
(Modules)
 
(56 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{welcome}}
 
{{welcome}}
{{maintenance}}
 
 
{{Navbar Kernel Competence}}
 
{{Navbar Kernel Competence}}
  
Line 6: Line 5:
  
 
Related to the [[Directory Structure]] we are in the directory ''/boot/kernel''.<br/>
 
Related to the [[Directory Structure]] we are in the directory ''/boot/kernel''.<br/>
On this page we show more kernel modules. Some of it are not installed by default.
+
On this page we show more kernel modules, like driver for wlan, ethernet, bluetooth, sound, file systems... Most of it are not installed by default.<br/>
If you like to start a module at boot time, you have to go to ''/boot/loader.conf'', open it with an editor of your choice. The syntax is always the same:<br/>
+
If you like to start a module at boot time, you have to go to ''/boot/loader.conf'', open it with an editor of your choice. The syntax is in most cases (with few exceptions) the same:<br/>
Take the name of the kernel module, chop of the tailing ''.ko'', also ''/boot/kernel/'' and add the string ''_load="YES"''.<br/>  
+
Take the name of the kernel module, chop of the tailing ''.ko'', also ''/boot/kernel/'' <br/>
For example, to load the module ''/boot/kernel/acpi_ibm.ko'' automatically add this to the ''/boot/loader.conf'':<br/>
+
and add the string ''_load="YES"''.<br/>  
 +
For example, to load the module ''/boot/kernel/acpi_ibm.ko'' <br/> automatically add this to the ''/boot/loader.conf'':<br/>
 
<code>acpi_ibm_load="YES"</code><br/>
 
<code>acpi_ibm_load="YES"</code><br/>
You will get additional information on the linked man pages.<br/> More loadable kernel modules are listed in [https://www.freebsd.org/ports/kld.html FreeBSD Ports: Kld]
+
You will get additional information on the linked man pages.<br/> More loadable kernel modules are listed in [https://www.freebsd.org/ports/kld.html FreeBSD Ports: Kld]<br/>
 +
A lot of additional Information you will find [https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES here]
  
 
==Modules==
 
==Modules==
Line 75: Line 76:
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=aibs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html aibs].ko||ASUSTeK AI Booster ACPI ATK0110 voltage, temperature and fan sensor
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=aibs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html aibs].ko||ASUSTeK AI Booster ACPI ATK0110 voltage, temperature and fan sensor
 
|-
 
|-
|/boot/kernel/alias_cuseeme.ko||
+
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/netinet/html/d5/d2e/alias__cuseeme_8c.html alias_cuseeme].ko||[https://www.leidinger.net/FreeBSD/dox/netinet/html/d5/d2e/alias__cuseeme_8c_source.html FreeBSD kernel IPv4 code]
 
|-
 
|-
|/boot/kernel/alias_dummy.ko||
+
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/netinet/html/d7/d88/alias__dummy_8c.html alias_dummy].ko||FreeBSD kernel IPv4 code
 
|-
 
|-
|/boot/kernel/alias_ftp.ko||
+
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/netinet/html/d0/d0f/alias__ftp_8c_source.html alias_ftp].ko|| Alias_ftp.c performs special processing for FTP sessions under TCP.
 
|-
 
|-
|/boot/kernel/alias_irc.ko||
+
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/netinet/html/d4/dfb/alias__irc_8c_source.html alias_irc].ko||Alias_irc.c intercepts packages contain IRC CTCP commands, and changes DCC commands to export a port on the aliasing host instead    of an aliased host.
 
|-
 
|-
|/boot/kernel/alias_nbt.ko||
+
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/netinet/html/d3/ddc/alias__nbt_8c_source.html alias_nbt].ko||alias_nbt.c performs special processing for NetBios over TCP/IP sessions by UDP.
 
|-
 
|-
|/boot/kernel/alias_pptp.ko||
+
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/netinet/html/d4/db2/alias__pptp_8c_source.html alias_pptp].ko||PPTP_CONTROL_PORT_NUMBER 1723
 
|-
 
|-
|/boot/kernel/alias_skinny.ko||
+
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/netinet/html/d2/dca/alias__skinny_8c_source.html alias_skinny].ko||alias_skinny.c handles the translation for the Cisco Skinny Station protocol.  Skinny typically uses TCP port 2000 to set up calls between a Cisco Call Manager and a Cisco IP phone.  When a phone comes on line,
 
|-
 
|-
|/boot/kernel/alias_smedia.ko||
+
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/netinet/html/d5/da2/alias__smedia_8c_source.html alias_smedia].ko||Alias_smedia.c is meant to contain the aliasing code for streaming media protocols.  It performs special processing for RSTP sessions under TCP.  Specifically, when a SETUP request is sent by a client, or a 200 reply  is sent by a server, it is intercepted and modified.  The address is  changed to the gateway machine and an aliasing port is used.
 
|-
 
|-
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=alpm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html alpm].ko||Acer Aladdin 15x3 Power Management controller driver
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=alpm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html alpm].ko||Acer Aladdin 15x3 Power Management controller driver
Line 95: Line 96:
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=alq&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html alq].ko||The alq facility provides an asynchronous fixed or variable length    recording mechanism, known as Asynchronous Logging Queues.  
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=alq&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html alq].ko||The alq facility provides an asynchronous fixed or variable length    recording mechanism, known as Asynchronous Logging Queues.  
 
|-
 
|-
|/boot/kernel/amd_ecc_inject.ko||
+
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/dev_amd_ecc_inject/html/ amd_ecc_inject].ko||See BKDG for AMD Family 15h Models 00h-0Fh Processors (publication 42301 Rev 3.08 - March 12, 2012):
 
|-
 
|-
|/boot/kernel/amdgpio.ko||
+
|/boot/kernel/[https://reviews.freebsd.org/D16865 amdgpio].ko||This is the driver for ACPI attached GPIO controller in AMD Platforms. This driver is basically a port of "drivers/pinctrl/pinctrl-amd.c" driver in Linux. This patch has the basic functions of GPIO, leaving interrupt related support.
 
|-
 
|-
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=amdpm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html amdpm].ko||This driver provides access to AMD 756/766/768/8111 Power management controllers.  Currently, only the SMBus 1.0 controller function is implemented.  The SMBus 2.0 functionality of the AMD 8111 controller is supported via the [https://www.freebsd.org/cgi/man.cgi?query=amdsmb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html amdsmb(4)] driver.
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=amdpm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html amdpm].ko||This driver provides access to AMD 756/766/768/8111 Power management controllers.  Currently, only the SMBus 1.0 controller function is implemented.  The SMBus 2.0 functionality of the AMD 8111 controller is supported via the [https://www.freebsd.org/cgi/man.cgi?query=amdsmb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html amdsmb(4)] driver.
Line 111: Line 112:
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=amr&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html amr].ko||MegaRAID SCSI/ATA/SATA RAID driver
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=amr&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html amr].ko||MegaRAID SCSI/ATA/SATA RAID driver
 
|-
 
|-
|/boot/kernel/amr_cam.ko||
+
|/boot/kernel/[https://www.leidinger.net/freebsd/dox/dev_amr/html/dc/d57/amr__cam_8c_source.html amr_cam].ko|| MegaRAID SCSI/ATA/SATA RAID driver
 +
 
 
|-
 
|-
|/boot/kernel/amr_linux.ko||
+
|/boot/kernel/[https://www.leidinger.net/freebsd/dox/dev_amr/html/d2/df1/amr__linux_8c.html amr_linux].ko|| MegaRAID SCSI/ATA/SATA RAID driver
 +
 
 
|-
 
|-
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=aout&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html aout].ko||kernel support for executing binary files in legacy a.out format
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=aout&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html aout].ko||kernel support for executing binary files in legacy a.out format
Line 125: Line 128:
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ata&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ata].ko||generic ATA/SATA controller driver
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ata&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ata].ko||generic ATA/SATA controller driver
 
|-
 
|-
|/boot/kernel/ataacard.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES ataacard].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/ataacerlabs.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES ataacerlabs].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/ataamd.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES ataamd].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/ataati.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES ataati].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/atacard.ko||
+
|/boot/kernel/[http://euc.jp/beos/atacard.en.html atacard].ko||ATA PC Card Driver
 
|-
 
|-
|/boot/kernel/atacenatek.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES atacenatek].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/atacypress.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES atacypress].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/atacyrix.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES atacyrix].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/atahighpoint.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES atahighpoint].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/ataintel.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES ataintel].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/ataisa.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES ataisa].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/ataite.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES ataite].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/atajmicron.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES atajmicron].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/atamarvell.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES atamarvell].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/atamicron.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES atamicron].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/atanational.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES atanational].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/atanetcell.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES atanetcell].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/atanvidia.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES atanvidia].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/atapci.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES atapci].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/atapromise.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES atapromise].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/ataserverworks.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES ataserverworks].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/atasiliconimage.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES atasiliconimage].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/atasis.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES atasis].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
|/boot/kernel/atavia.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES atavia].ko||The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
 
|-
 
|-
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ath&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ath_dfs].ko||ath Atheros IEEE 802.11 wireless network driver
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ath&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ath_dfs].ko||ath Atheros IEEE 802.11 wireless network driver
 
|-
 
|-
|/boot/kernel/[ttps://www.freebsd.org/cgi/man.cgi?query=ath_hal&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ath_hal].ko||Atheros Hardware Access Layer (HAL)
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ath_hal&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ath_hal].ko||Atheros Hardware Access Layer (HAL)
 
|-
 
|-
|/boot/kernel/ath_hal_ar5210.ko||
+
|/boot/kernel/ath_hal_ar5210.ko||[https://www.adminbyaccident.com/freebsd/how-to-freebsd/how-to-upgrade-freebsd-from-version-11-2-up-to-12-0/ The file was added as part of updating to 12.0]
 
|-
 
|-
|/boot/kernel/ath_hal_ar5211.ko||
+
|/boot/kernel/ath_hal_ar5211.ko||[https://www.adminbyaccident.com/freebsd/how-to-freebsd/how-to-upgrade-freebsd-from-version-11-2-up-to-12-0/ The file was added as part of updating to 12.0]
 
|-
 
|-
|/boot/kernel/ath_hal_ar5212.ko||
+
|/boot/kernel/ath_hal_ar5212.ko||[https://www.adminbyaccident.com/freebsd/how-to-freebsd/how-to-upgrade-freebsd-from-version-11-2-up-to-12-0/ The file was added as part of updating to 12.0]
 
|-
 
|-
|/boot/kernel/ath_hal_ar5416.ko||
+
|/boot/kernel/ath_hal_ar5416.ko||[https://www.adminbyaccident.com/freebsd/how-to-freebsd/how-to-upgrade-freebsd-from-version-11-2-up-to-12-0/ The file was added as part of updating to 12.0]
 
|-
 
|-
|/boot/kernel/ath_hal_ar9300.ko||
+
|/boot/kernel/ath_hal_ar9300.ko||[https://www.adminbyaccident.com/freebsd/how-to-freebsd/how-to-upgrade-freebsd-from-version-11-2-up-to-12-0/ The file was added as part of updating to 12.0]
 
|-
 
|-
|/boot/kernel/ath_main.ko||
+
|/boot/kernel/ath_main.ko||[https://www.adminbyaccident.com/freebsd/how-to-freebsd/how-to-upgrade-freebsd-from-version-11-2-up-to-12-0/ The file was added as part of updating to 12.0]
 
|-
 
|-
|/boot/kernel/ath_rate.ko||
+
|/boot/kernel/ath_rate.ko||[https://www.adminbyaccident.com/freebsd/how-to-freebsd/how-to-upgrade-freebsd-from-version-11-2-up-to-12-0/ The file was added as part of updating to 12.0]
 
|-
 
|-
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=atp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html atp].ko||ATP  is used for reading and replying to messages contained in QWK mail        packets which are available through public access bulletin boards.
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=atp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html atp].ko||ATP  is used for reading and replying to messages contained in QWK mail        packets which are available through public access bulletin boards.
Line 197: Line 200:
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=bcma&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html bcma].ko|| The bcma driver provides bhnd(4) support for devices using the ARM AMBA  based backplane architecture found in later Broadcom Home Networking Division's network chipsets and embedded systems.
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=bcma&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html bcma].ko|| The bcma driver provides bhnd(4) support for devices using the ARM AMBA  based backplane architecture found in later Broadcom Home Networking Division's network chipsets and embedded systems.
 
|-
 
|-
|/boot/kernel/bcma_bhndb.ko||
+
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/dev_bwn/html/da/df0/if__bwn__pci_8c_source.html bcma_bhndb].ko||Broadcom AMBA Backplane driver [https://www.freebsd.org/cgi/man.cgi?query=bcma&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html]
 
|-
 
|-
|/boot/kernel/beastie_saver.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?splash(4) beastie_saver].ko||splash screen / screen saver interface
 
|-
 
|-
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=bhnd&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html bhnd].ko||Broadcom Home Networking Division interconnect bus
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=bhnd&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html bhnd].ko||Broadcom Home Networking Division interconnect bus
 
|-
 
|-
|/boot/kernel/bhnd_pci.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/bhnd/cores/pci/bhnd_pci.c bhnd_pc]i.ko||Broadcom Common PCI/PCIe Support. This base driver implementation is shared by the bhnd_pcib (root complex) and bhnd_pci_hostb (host bridge) drivers.
 
|-
 
|-
|/boot/kernel/bhnd_pci_hostb.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/tree/master/sys/dev/bhnd/cores/pci bhnd_pci_hostb].ko||Broadcom BHND PCI/PCIe-Gen1 PCI-Host Bridge. This driver handles all interactions with PCI bridge cores operating in endpoint mode. Host-level PCI operations are handled at the bhndb bridge level by the bhndb_pci driver.
 
|-
 
|-
|/boot/kernel/bhnd_pcib.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/bhnd/cores/pci/bhnd_pcib.c bhnd_pcib].ko||Broadcom PCI/PCIe-Gen1 Host-PCI bridge. This driver handles all interactions with PCI bridge cores operating in root complex mode.
 
|-
 
|-
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=bhndb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html bhndb].ko||Broadcom Home Networking Division interconnect bridge driver
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=bhndb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html bhndb].ko||Broadcom Home Networking Division interconnect bridge driver
 
|-
 
|-
|/boot/kernel/bhndb_pci.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/bhnd/bhndb/bhndb_pci.c bhndb_pci].ko||PCI-specific implementation for the BHNDB bridge driver.
 +
Provides support for bridging from a PCI parent bus to a BHND-compatible  bus (e.g. bcma or siba) via a Broadcom PCI core configured in end-point mode.
 +
This driver handles all initial generic host-level PCI interactions with a PCI/PCIe bridge core operating in endpoint mode. Once the bridged bhnd(4) bus has been enumerated, this driver works in tandem with a core-specific bhnd_pci_hostb driver to manage the PCI core.
 
|-
 
|-
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=bktr&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html bktr].ko||Brooktree Bt848/849/878/879 and Pinnacle PCTV video capture driver
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=bktr&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html bktr].ko||Brooktree Bt848/849/878/879 and Pinnacle PCTV video capture driver
 
|-
 
|-
|/boot/kernel/bktr_mem.ko||
+
|/boot/kernel/[https://fossies.org/diffs/motion-release/3.2.12_vs_4.0.1/README.FreeBSD-diff.html bktr_mem].ko|| Motion monitors the video signal from one or more cameras and is able to detect motion.
 
|-
 
|-
|/boot/kernel/blake2.ko||
+
|/boot/kernel/[https://www.freshports.org/sysutils/b2sum blake2].ko||The cryptographic hash function BLAKE2 is an improved version of the SHA-3
 +
finalist BLAKE. Like SHA-3, BLAKE2 offers the highest security, yet is fast as
 +
MD5 on 64-bit platforms and requires at least 33% less RAM than SHA-2 or SHA-3
 +
on low-end systems. The core algorithm of BLAKE2 is derived from ChaCha, a
 +
stream cipher designed by Daniel J. Bernstein that has been proposed as a
 +
standard cipher for TLS.
 
|-
 
|-
|/boot/kernel/blank_saver.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?splash(4) blank_saver].ko||This screen saver simply blanks the screen.
 
|-
 
|-
|/boot/kernel/bridgestp.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?bridge(4) bridgestp].ko||The if_bridge driver creates a logical link between two or more IEEE 802    networks that use the same (or "similar enough") framing format.  For example, it is possible to bridge Ethernet and 802.11 networks together,  but it is not possible to bridge Ethernet and Token Ring together.
 
|-
 
|-
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=bytgpio&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html bytgpio].ko||Intel Bay Trail SoC GPIO controller
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=bytgpio&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html bytgpio].ko||Intel Bay Trail SoC GPIO controller
 
|-
 
|-
|/boot/kernel/callout_test.ko||
+
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/tests/callout_test.h callout_test].ko|| Regularize the Netflix copyright; Copyright (c) 2015 Netflix, Inc.
 
|-
 
|-
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=cam&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html cam].ko||CPU'S AUDIO MIXER for Linux
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=cam&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html cam].ko||CPU'S AUDIO MIXER for Linux
Line 250: Line 260:
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=cc_vegas&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html cc_vegas].ko||Vegas Congestion Control Algorithm
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=cc_vegas&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html cc_vegas].ko||Vegas Congestion Control Algorithm
 
|-
 
|-
|/boot/kernel/ccp.ko||
+
|/boot/kernel/[https://github.com/lattera/freebsd/blob/master/usr.sbin/ppp/ccp.h ccp].ko||[https://reviews.freebsd.org/D12723 experimental driver for AMD Crypto Co-Processor]
 
|-
 
|-
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ccr&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ccr].ko||The ccr driver provides support for the crypto accelerator engine included on PCI Express Ethernet adapters based on the Chelsio Terminator 6    ASIC (T6). The driver accelerates AES-CBC, AES-CCM, AES-CTR, AES-GCM,
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ccr&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ccr].ko||The ccr driver provides support for the crypto accelerator engine included on PCI Express Ethernet adapters based on the Chelsio Terminator 6    ASIC (T6). The driver accelerates AES-CBC, AES-CCM, AES-CTR, AES-GCM,
Line 257: Line 267:
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=cd9660&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html cd9660].ko||The cd9660 driver will permit the FreeBSD kernel to access the cd9660  file system.
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=cd9660&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html cd9660].ko||The cd9660 driver will permit the FreeBSD kernel to access the cd9660  file system.
 
|-
 
|-
|/boot/kernel/cd9660_iconv.ko||
+
|/boot/kernel/[https://github.com/lattera/freebsd/blob/master/sys/fs/cd9660/cd9660_iconv.c cd9660_iconv].ko|| Support for multibyte charsets in LIBICONV.
 
|-
 
|-
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=cfiscsi&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html cfiscsi].ko||The cfiscsi subsystem provides the kernel component of an iSCSI target.  The target is the iSCSI server, providing LUNs backed by local files and  volumes to remote initiators.
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=cfiscsi&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html cfiscsi].ko||The cfiscsi subsystem provides the kernel component of an iSCSI target.  The target is the iSCSI server, providing LUNs backed by local files and  volumes to remote initiators.
Line 293: Line 303:
 
|/boot/kernel/cxgb_t3fw.ko||[https://www.freebsd.org/cgi/man.cgi?query=cxgb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html cxgb] -- Chelsio T3 10 Gigabit Ethernet adapter driver
 
|/boot/kernel/cxgb_t3fw.ko||[https://www.freebsd.org/cgi/man.cgi?query=cxgb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html cxgb] -- Chelsio T3 10 Gigabit Ethernet adapter driver
 
|-
 
|-
|/boot/kernel/cxgbei.ko||
+
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/dev_cxgbe/html/d1/da6/cxgbei_8h.html cxgbei].ko||CXGBEI_CONN_SIGNATURE 0x56788765
 
|-
 
|-
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=cyapa&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html cyapa].ko||Cypress APA trackpad with I2C interface driver
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=cyapa&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html cyapa].ko||Cypress APA trackpad with I2C interface driver
 
|-
 
|-
|/boot/kernel/daemon_saver.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=splash&sektion=4&apropos=0&manpath=FreeBSD+9.0-RELEASE daemon_saver].ko||Animated BSD Daemon screen saver.
 
|-
 
|-
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=dcons&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html dcons].ko||dumb console device driver
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=dcons&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html dcons].ko||dumb console device driver
Line 305: Line 315:
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=dpms&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html dpms].ko||VESA BIOS DPMS driver  
 
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=dpms&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html dpms].ko||VESA BIOS DPMS driver  
 
|-
 
|-
|/boot/kernel/dragon_saver.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=splash&sektion=4&apropos=0&manpath=FreeBSD+9.0-RELEASE dragon_saver].ko||Draws a random dragon curve.
 
|-
 
|-
|/boot/kernel/drm.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=drm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html drm].ko||The Direct Rendering Manager (DRM) is a framework to manage Graphics    Processing Units (GPUs). It is designed to support the needs of complex      graphics devices, usually containing programmable pipelines well suited      to 3D graphics acceleration. Furthermore, it is responsible for memory    management, interrupt handling and DMA to provide a uniform interface    to applications.
 
|-
 
|-
|/boot/kernel/drm2.ko||
+
|/boot/kernel/drm2.ko||Graphics driver; direct rendering manager (DRM) drivers; some interesting [https://www.phoronix.com/scan.php?page=news_item&px=DRM-FreeBSD-Heated additional thoughts]
 
|-
 
|-
|/boot/kernel/ds13rtc.ko||
+
|/boot/kernel/[https://www.leidinger.net/freebsd/dox/dev_iicbus/html/d4/dee/ds13rtc_8c.html ds13rtc].ko||IICBUS device code
 
|-
 
|-
|/boot/kernel/ds1307.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ds1307&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ds1307].ko||The ds1307 serial real-time clock (RTC) is a low-power, full binary-coded  decimal (BCD) clock/calendar plus 56 bytes of NV SRAM.
 +
 
 
|-
 
|-
|/boot/kernel/ds1672.ko||
+
|/boot/kernel/[https://www.leidinger.net/freebsd/dox/dev_iicbus/html/d3/d9b/ds1672_8c_source.html ds1672].ko||Dallas Semiconductor DS1672 RTC sitting on the I2C bus.
 
|-
 
|-
|/boot/kernel/ds3231.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ds3231&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ds3231].ko||The ds3231 is a lowcost, extremely accurate I2C realtime clock (RTC)    with an integrated temperature-compensated crystal oscillator (TCXO) and    crystal.
 
|-
 
|-
|/boot/kernel/dtaudit.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=dtaudit&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html dtaudit].ko||The DTrace dtaudit provider allows users to trace events in the kernel      security auditing subsystem, [https://www.freebsd.org/cgi/man.cgi?query=audit&sektion=4&apropos=0&manpath=FreeBSD+12.1-RELEASE+and+Ports audit(4)].
 
|-
 
|-
|/boot/kernel/dtmalloc.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=malloc&sektion=9 dtmalloc].ko||kernel  memory management routines See also [https://www.patpro.net/blog/index.php/2013/10/21/2538-dtrace-on-freebsd-9-2/]DTrace, also known as Dynamic Tracing, was developed by Sun™ as a tool for locating performance bottlenecks in production and pre-production systems. In addition to diagnosing performance problems, DTrace can be used to help investigate and debug unexpected behavior in both the FreeBSD kernel and in userland programs.[https://www.freebsd.org/doc/handbook/dtrace.html]
 
|-
 
|-
|/boot/kernel/dtnfscl.ko||
+
|/boot/kernel/[https://www.patpro.net/blog/index.php/2013/10/21/2538-dtrace-on-freebsd-9-2/ dtnfscl].ko||Dtrace is enabled by default in the GENERIC kernel, DTrace, also known as Dynamic Tracing, was developed by Sun™ as a tool for locating performance bottlenecks in production and pre-production systems. In addition to diagnosing performance problems, DTrace can be used to help investigate and debug unexpected behavior in both the FreeBSD kernel and in userland programs.[https://www.freebsd.org/doc/handbook/dtrace.html]
 
|-
 
|-
|/boot/kernel/dtrace.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=dtrace&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html dtrace].ko||DTrace is a comprehensive dynamic tracing framework ported from Solaris.
 
|-
 
|-
|/boot/kernel/dtrace_test.ko||
+
|/boot/kernel/[https://www.patpro.net/blog/index.php/2013/10/21/2538-dtrace-on-freebsd-9-2/ dtrace_test].ko||DTrace, also known as Dynamic Tracing, was developed by Sun™ as a tool for locating performance bottlenecks in production and pre-production systems. In addition to diagnosing performance problems, DTrace can be used to help investigate and debug unexpected behavior in both the FreeBSD kernel and in userland programs.[https://www.freebsd.org/doc/handbook/dtrace.html]
 
|-
 
|-
|/boot/kernel/dtraceall.ko||
+
|/boot/kernel/[https://www.patpro.net/blog/index.php/2013/10/21/2538-dtrace-on-freebsd-9-2/ dtraceall].ko||DTrace, also known as Dynamic Tracing, was developed by Sun™ as a tool for locating performance bottlenecks in production and pre-production systems. In addition to diagnosing performance problems, DTrace can be used to help investigate and debug unexpected behavior in both the FreeBSD kernel and in userland programs.[https://www.freebsd.org/doc/handbook/dtrace.html]
 
|-
 
|-
|/boot/kernel/dummynet.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=dummynet&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html dummynet].ko||The dummynet system facility permits the control of traffic going through  the various network interfaces, by applying bandwidth and queue size limitations, implementing different scheduling and queue management policies, and emulating delays and losses.
 
|-
 
|-
|/boot/kernel/efirt.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=efirt&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html efirt].ko||All of the following calls will return ENXIO if UEFI runtime services are  not available.  efirt is currently only available on amd64 and arm64.
 
|-
 
|-
|/boot/kernel/ehci.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ehci&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ehci].ko||The ehci driver provides support for the USB Enhanced Host Controller Interface, which is used by USB 2.0 controllers.
 
|-
 
|-
|/boot/kernel/esp.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=esp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html esp].ko||The esp driver provides support for the AMD Am53C974, the Emulex ESP100,    ESP100A, ESP200 and ESP406, the NCR 53C90, 53C94 and 53C96 as well as the    QLogic FAS100A, FAS216, FAS366 and FAS408 SCSI controller chips found in    a wide variety of systems and peripheral boards.
 
|-
 
|-
|/boot/kernel/evdev.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=evdev&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html evdev].ko||evdev  is  an  Xorg input driver for Linux's generic event devices.  It  therefore supports all input devices that the kernel knows  about,  including most  mice, keyboards, tablets and touchscreens.  evdev is the  default driver on the major Linux distributions.
 
|-
 
|-
|/boot/kernel/exca.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=exca&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html exca].ko||The exca module is used to implement the Intel ExCA interface to PC  Cards.
 
|-
 
|-
|/boot/kernel/ext2fs.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ext2fs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ext2fs].ko||The ext2fs driver will permit the FreeBSD kernel to access ext2 file systems and its derivatives. It currently implements most of the features  required by ext3 and ext4 file systems.  Support for Extended Attributes    in ext4 is experimental.  Journalling and encryption are currently not    supported.
 
|-
 
|-
|/boot/kernel/fade_saver.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=splash&sektion=4&apropos=0&manpath=FreeBSD+9.0-RELEASE fade_saver].ko||The splash pseudo device driver adds support for the splash screen and    screen savers to the kernel.  This driver is required if the splash bitmap image is to be loaded or any screen saver is to be used.
 
|-
 
|-
|/boot/kernel/fasttrap.ko||
+
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/kern/html/da/d46/kern__fork_8c_source.html fasttrap].ko||Tell the DTrace fasttrap provider about the new process so that any tracepoints inherited from the parent can be removed. We have to do this only after p_state is PRS_NORMAL since the fasttrap module will use pfind() later on.
 
|-
 
|-
|/boot/kernel/fbt.ko||
+
|/boot/kernel/[https://www.freebsd.org/doc/handbook/dtrace-enable.html fbt].ko||In FreeBSD 9.2 and 10.0, DTrace support is built into the GENERIC kernel. Users of the AMD64 architecture should also add this line: <code>''options        KDTRACE_FRAME''</code>
 +
This option provides support for FBT. While DTrace will work without this option, there will be limited support for function boundary tracing.
 
|-
 
|-
|/boot/kernel/fdc.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=fdc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html fdc].ko||PC architecture floppy disk controller driver
 
|-
 
|-
|/boot/kernel/fdescfs.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=fdescfs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html fdescfs].ko||The file-descriptor file system, or fdescfs, provides access to the per-process file descriptor namespace in the global file system namespace. The conventional mount point is /dev/fd.
 
|-
 
|-
|/boot/kernel/filemon.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=filemon&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html filemon].ko||The filemon device allows a process to collect file operations data of  its children.
 
|-
 
|-
|/boot/kernel/fire_saver.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=splash&sektion=4&apropos=0&manpath=FreeBSD+9.0-RELEASE fire_saver].ko||The splash pseudo device driver adds support for the splash screen and    screen savers to the kernel.  This driver is required if the splash bitmap image is to be loaded or any screen saver is to be used.
 
|-
 
|-
|/boot/kernel/firewire.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=firewire&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html firewire].ko||IEEE1394 High-performance Serial Bus
 +
 
 
|-
 
|-
|/boot/kernel/firmware.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=firmware&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html firmware].ko||The firmware abstraction provides a convenient interface for loading firmware images into the kernel, and for accessing such images from kernel components.
 
|-
 
|-
|/boot/kernel/fuse.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=fuse&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html fuse].ko|| Fuse  is a  Sinclair  ZX Spectrum emulator. It supports several models (including the 128), with quite faithful emulation of the  display  and    sound.
 
|-
 
|-
|/boot/kernel/fusefs.ko||
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=fusefs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html fusefs].ko||The fusefs driver implements a file system that is serviced by a userspace program. There are also some [https://www.freebsd.org/cgi/man.cgi?query=sysctl&sektion=8&apropos=0&manpath=FreeBSD+12.1-RELEASE+and+Ports sysctl(8)] variables available.
 
|-
 
|-
|/boot/kernel/g_audio.ko||
+
|/boot/kernel/g_audio.ko||[https://www.freebsd.org/cgi/man.cgi?query=g&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html g] - Creates a special type of combination often referred to as a group.  This builds a combination by unioning together all the listed objects.
 +
 
 
|-
 
|-
 
|/boot/kernel/g_keyboard.ko||
 
|/boot/kernel/g_keyboard.ko||
Line 375: Line 389:
 
|/boot/kernel/g_mouse.ko||
 
|/boot/kernel/g_mouse.ko||
 
|-
 
|-
|/boot/kernel/geom_bde.ko||
+
|/boot/kernel/geom_bde.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
 
|-
 
|-
|/boot/kernel/geom_cache.ko||
+
|/boot/kernel/geom_cache.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
 
|-
 
|-
|/boot/kernel/geom_ccd.ko||
+
|/boot/kernel/geom_ccd.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
 
|-
 
|-
|/boot/kernel/geom_concat.ko||
+
|/boot/kernel/geom_concat.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
 
|-
 
|-
|/boot/kernel/geom_eli.ko||
+
|/boot/kernel/geom_eli.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
 
|-
 
|-
|/boot/kernel/geom_flashmap.ko||
+
|/boot/kernel/geom_flashmap.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
 
|-
 
|-
|/boot/kernel/geom_gate.ko||
+
|/boot/kernel/geom_gate.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
 
|-
 
|-
|/boot/kernel/geom_journal.ko||
+
|/boot/kernel/geom_journal.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
 
|-
 
|-
|/boot/kernel/geom_label.ko||
+
|/boot/kernel/geom_label.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
 
|-
 
|-
|/boot/kernel/geom_linux_lvm.ko||
+
|/boot/kernel/geom_linux_lvm.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
 
|-
 
|-
|/boot/kernel/geom_md.ko||
+
|/boot/kernel/geom_md.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
 
|-
 
|-
|/boot/kernel/geom_mirror.ko||
+
|/boot/kernel/geom_mirror.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
 
|-
 
|-
|/boot/kernel/geom_mountver.ko||
+
|/boot/kernel/geom_mountver.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
 
|-
 
|-
|/boot/kernel/geom_multipath.ko||
+
|/boot/kernel/geom_multipath.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
 
|-
 
|-
|/boot/kernel/geom_nop.ko||
+
|/boot/kernel/geom_nop.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
|}
+
|-
* /boot/kernel/geom_part_apm.ko
+
|/boot/kernel/geom_part_apm.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/geom_part_bsd.ko
+
|-
* /boot/kernel/geom_part_bsd64.ko
+
|/boot/kernel/geom_part_bsd.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/geom_part_ebr.ko
+
|-
* /boot/kernel/geom_part_gpt.ko
+
|/boot/kernel/geom_part_bsd64.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/geom_part_ldm.ko
+
|-
* /boot/kernel/geom_part_mbr.ko
+
|/boot/kernel/geom_part_ebr.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/geom_part_vtoc8.ko
+
|-
* /boot/kernel/geom_raid.ko
+
|/boot/kernel/geom_part_gpt.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/geom_raid3.ko
+
|-
* /boot/kernel/geom_sched.ko
+
|/boot/kernel/geom_part_ldm.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/geom_shsec.ko
+
|-
* /boot/kernel/geom_stripe.ko
+
|/boot/kernel/geom_part_mbr.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/geom_uzip.ko
+
|-
* /boot/kernel/geom_vinum.ko
+
|/boot/kernel/geom_part_vtoc8.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/geom_virstor.ko
+
|-
* /boot/kernel/geom_zero.ko
+
|/boot/kernel/geom_raid.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/gpiobus.ko
+
|-
* /boot/kernel/gpioiic.ko
+
|/boot/kernel/geom_raid3.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/gpioled.ko
+
|-
* /boot/kernel/gpiospi.ko
+
|/boot/kernel/geom_sched.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/gpioths.ko
+
|-
* /boot/kernel/green_saver.ko
+
|/boot/kernel/geom_shsec.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/gsched_delay.ko
+
|-
* /boot/kernel/gsched_rr.ko
+
|/boot/kernel/geom_stripe.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/h_ertt.ko
+
|-
* /boot/kernel/hifn.ko
+
|/boot/kernel/geom_uzip.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/hpt27xx.ko
+
|-
* /boot/kernel/hptiop.ko
+
|/boot/kernel/geom_vinum.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/hptmv.ko
+
|-
* /boot/kernel/hptnr.ko
+
|/boot/kernel/geom_virstor.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/hptrr.ko
+
|-
* /boot/kernel/hv_netvsc.ko
+
|/boot/kernel/geom_zero.ko||The [https://www.freebsd.org/cgi/man.cgi?query=geom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html geom] utility is used to control various GEOM classes.
* /boot/kernel/hv_storvsc.ko
+
|-
* /boot/kernel/hv_utils.ko
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=gpiobus&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html gpiobus].ko||The gpiobus system provides a simple interface to the GPIO pins that are usually available on embedded architectures and can provide bit banging  style devices to the system.
* /boot/kernel/hv_vmbus.ko
+
|-
* /boot/kernel/hwpmc.ko
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=gpioiic&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html gpioiic].ko||The gpioiic driver provides an IIC bit-banging interface using two GPIO  pins for the SCL and SDA on the gpiobus.  gpioiic implements an open collector kind of output, as recommended by the standard, when driving the
* /boot/kernel/i915kms.ko
+
pins on the gpiobus, i.e, they are never switched to the logical value of  '1', or they are '0' or simply open (Hi-Z/tri-state). So the pullup resistors are required so gpioiic can work.
* /boot/kernel/ibcore.ko
+
|-
* /boot/kernel/icee.ko
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=gpioled&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html gpioled].ko||The gpioled driver provides glue to attach a led(4) compatible device to a GPIO pin.  Each LED in the system has a name which is used to export a  device as /dev/led/_name_. The GPIO pin can then be controlled by writing to this device as described in led(4).
* /boot/kernel/ichsmb.ko
+
|-
* /boot/kernel/ichwd.ko
+
|/boot/kernel/gpiospi.ko||[https://www.leidinger.net/freebsd/dox/dev_gpio/html/d3/d4c/gpiospi_8c_source.html]
* /boot/kernel/ida.ko
+
|-
* /boot/kernel/if_ae.ko
+
|/boot/kernel/gpioths.ko||[https://www.leidinger.net/freebsd/dox/dev_gpio/html/d7/d0d/gpioths_8c.html]
* /boot/kernel/if_age.ko
+
|-
* /boot/kernel/if_alc.ko
+
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?splash(4) green_saver].ko||The splash pseudo device driver adds support for the splash screen and screen savers to the kernel.  This driver is required if the splash bitmap image is to be loaded or any screen saver is to be used.
* /boot/kernel/if_ale.ko
+
|-
* /boot/kernel/if_an.ko
+
|/boot/kernel/gsched_delay.ko||The [https://www.freebsd.org/cgi/man.cgi?query=gsched&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html gsched ]utility (also callable as geom sched ...) changes the scheduling policy of the requests going to a provider.
* /boot/kernel/if_ath.ko
+
* /boot/kernel/if_ath_pci.ko
+
* /boot/kernel/if_aue.ko
+
* /boot/kernel/if_axe.ko
+
* /boot/kernel/if_axge.ko
+
* /boot/kernel/if_bce.ko
+
* /boot/kernel/if_bfe.ko
+
* /boot/kernel/if_bge.ko
+
* /boot/kernel/if_bnxt.ko
+
* /boot/kernel/if_bridge.ko
+
* /boot/kernel/if_bwi.ko
+
* /boot/kernel/if_bwn.ko
+
* /boot/kernel/if_bxe.ko
+
* /boot/kernel/if_cas.ko
+
* /boot/kernel/if_cc.ko
+
* /boot/kernel/if_ccv.ko
+
* /boot/kernel/if_cdce.ko
+
* /boot/kernel/if_cdceem.ko
+
* /boot/kernel/if_cs.ko
+
* /boot/kernel/if_cue.ko
+
* /boot/kernel/if_cxgb.ko
+
* /boot/kernel/if_cxgbe.ko
+
* /boot/kernel/if_cxgbev.ko
+
* /boot/kernel/if_cxl.ko
+
* /boot/kernel/if_cxlv.ko
+
* /boot/kernel/if_dc.ko
+
* /boot/kernel/if_de.ko
+
* /boot/kernel/if_disc.ko
+
* /boot/kernel/if_ed.ko
+
* /boot/kernel/if_edsc.ko
+
* /boot/kernel/if_em.ko
+
* /boot/kernel/if_ena.ko
+
* /boot/kernel/if_enc.ko
+
* /boot/kernel/if_ep.ko
+
* /boot/kernel/if_epair.ko
+
* /boot/kernel/if_et.ko
+
* /boot/kernel/if_fe.ko
+
* /boot/kernel/if_fwe.ko
+
* /boot/kernel/if_fwip.ko
+
* /boot/kernel/if_fxp.ko
+
* /boot/kernel/if_gem.ko
+
* /boot/kernel/if_gif.ko
+
* /boot/kernel/if_gre.ko
+
* /boot/kernel/if_hme.ko
+
* /boot/kernel/if_iavf.ko
+
* /boot/kernel/if_ic.ko
+
* /boot/kernel/if_igb.ko
+
* /boot/kernel/if_ipheth.ko
+
* /boot/kernel/if_ipw.ko
+
* /boot/kernel/if_iwi.ko
+
* /boot/kernel/if_iwm.ko
+
* /boot/kernel/if_iwn.ko
+
* /boot/kernel/if_ix.ko
+
* /boot/kernel/if_ixl.ko
+
* /boot/kernel/if_ixlv.ko
+
* /boot/kernel/if_ixv.ko
+
* /boot/kernel/if_jme.ko
+
* /boot/kernel/if_kue.ko
+
* /boot/kernel/if_lagg.ko
+
* /boot/kernel/if_le.ko
+
* /boot/kernel/if_lge.ko
+
* /boot/kernel/if_lio.ko
+
* /boot/kernel/if_malo.ko
+
* /boot/kernel/if_me.ko
+
* /boot/kernel/if_mos.ko
+
* /boot/kernel/if_msk.ko
+
* /boot/kernel/if_muge.ko
+
* /boot/kernel/if_mwl.ko
+
* /boot/kernel/if_mxge.ko
+
* /boot/kernel/if_my.ko
+
* /boot/kernel/if_ndis.ko
+
* /boot/kernel/if_nfe.ko
+
* /boot/kernel/if_nge.ko
+
* /boot/kernel/if_ntb.ko
+
* /boot/kernel/if_oce.ko
+
* /boot/kernel/if_otus.ko
+
* /boot/kernel/if_pcn.ko
+
* /boot/kernel/if_qlnxe.ko
+
* /boot/kernel/if_qlnxev.ko
+
* /boot/kernel/if_qlxgb.ko
+
* /boot/kernel/if_qlxgbe.ko
+
* /boot/kernel/if_qlxge.ko
+
* /boot/kernel/if_ral.ko
+
* /boot/kernel/if_re.ko
+
* /boot/kernel/if_rl.ko
+
* /boot/kernel/if_rsu.ko
+
* /boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_rtwn_pci&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_rtwn_pci].ko -- Realtek PCI device glue
+
* /boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_rtwn_usb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_rtwn_usb].ko -- Realtek USB device glue
+
* /boot/kernel/if_rue.ko
+
* /boot/kernel/if_rum.ko
+
* /boot/kernel/if_run.ko
+
* /boot/kernel/if_sf.ko
+
* /boot/kernel/if_sge.ko
+
* /boot/kernel/if_sis.ko
+
* /boot/kernel/if_sk.ko
+
* /boot/kernel/if_smsc.ko
+
* /boot/kernel/if_sn.ko
+
* /boot/kernel/if_ste.ko
+
* /boot/kernel/if_stf.ko
+
* /boot/kernel/if_stge.ko
+
* /boot/kernel/if_tap.ko
+
* /boot/kernel/if_ti.ko
+
* /boot/kernel/if_tl.ko
+
* /boot/kernel/if_tun.ko
+
* /boot/kernel/if_tuntap.ko
+
* /boot/kernel/if_tx.ko
+
* /boot/kernel/if_txp.ko
+
* /boot/kernel/if_uath.ko
+
* /boot/kernel/if_udav.ko
+
* /boot/kernel/if_upgt.ko
+
* /boot/kernel/if_ural.ko
+
* /boot/kernel/if_ure.ko
+
* /boot/kernel/if_urndis.ko
+
* /boot/kernel/if_urtw.ko
+
* /boot/kernel/if_vge.ko
+
* /boot/kernel/if_vlan.ko
+
* /boot/kernel/if_vmx.ko
+
* /boot/kernel/if_vr.ko
+
* /boot/kernel/if_vte.ko
+
* /boot/kernel/if_vtnet.ko
+
* /boot/kernel/if_vx.ko
+
* /boot/kernel/if_vxlan.ko
+
* /boot/kernel/if_wb.ko
+
* /boot/kernel/if_wi.ko
+
* /boot/kernel/if_wpi.ko
+
* /boot/kernel/if_xe.ko
+
* /boot/kernel/if_xl.ko
+
* /boot/kernel/if_zyd.ko
+
* /boot/kernel/iflib.ko
+
* /boot/kernel/ig4.ko
+
* /boot/kernel/iic.ko
+
* /boot/kernel/iicbb.ko
+
* /boot/kernel/iicbus.ko
+
* /boot/kernel/iicmux.ko
+
* /boot/kernel/iicsmb.ko
+
* /boot/kernel/iir.ko
+
* /boot/kernel/imcsmb.ko
+
* /boot/kernel/imgact_binmisc.ko
+
* /boot/kernel/intelspi.ko
+
* /boot/kernel/intpm.ko
+
* /boot/kernel/io.ko
+
* /boot/kernel/ioat.ko
+
* /boot/kernel/ip6_mroute.ko
+
* /boot/kernel/ip_mroute.ko
+
* /boot/kernel/ipdivert.ko
+
* /boot/kernel/ipfw.ko
+
* /boot/kernel/ipfw_nat.ko
+
* /boot/kernel/ipfw_nat64.ko
+
* /boot/kernel/ipfw_nptv6.ko
+
* /boot/kernel/ipfw_pmod.ko
+
* /boot/kernel/ipl.ko
+
* /boot/kernel/ipmi.ko
+
* /boot/kernel/ipmi_linux.ko
+
* /boot/kernel/ipoib.ko
+
* /boot/kernel/ips.ko
+
* /boot/kernel/ipsec.ko
+
* /boot/kernel/ipw_bss.ko
+
* /boot/kernel/ipw_ibss.ko
+
* /boot/kernel/ipw_monitor.ko
+
* /boot/kernel/isci.ko
+
* /boot/kernel/iscsi.ko
+
* /boot/kernel/iscsi_initiator.ko
+
* /boot/kernel/iser.ko
+
* /boot/kernel/isl.ko
+
* /boot/kernel/isl12xx.ko
+
* /boot/kernel/ismt.ko
+
* /boot/kernel/isp.ko
+
* /boot/kernel/isp_1040.ko
+
* /boot/kernel/isp_1080.ko
+
* /boot/kernel/isp_2100.ko
+
* /boot/kernel/isp_2200.ko
+
* /boot/kernel/isp_2300.ko
+
* /boot/kernel/isp_2322.ko
+
* /boot/kernel/isp_2400.ko
+
* /boot/kernel/isp_2500.ko
+
* /boot/kernel/isp_12160.ko
+
* /boot/kernel/ispfw.ko
+
* /boot/kernel/iw_cxgbe.ko
+
* /boot/kernel/iwi_bss.ko
+
* /boot/kernel/iwi_ibss.ko
+
* /boot/kernel/iwi_monitor.ko
+
* /boot/kernel/iwm3160fw.ko
+
* /boot/kernel/iwm3168fw.ko
+
* /boot/kernel/iwm7260fw.ko
+
* /boot/kernel/iwm7265Dfw.ko
+
* /boot/kernel/iwm7265fw.ko
+
* /boot/kernel/iwm8000Cfw.ko
+
* /boot/kernel/iwm8265fw.ko
+
* /boot/kernel/iwm9000fw.ko
+
* /boot/kernel/iwm9260fw.ko
+
* /boot/kernel/iwn100fw.ko
+
* /boot/kernel/iwn105fw.ko
+
* /boot/kernel/iwn135fw.ko
+
* /boot/kernel/iwn1000fw.ko
+
* /boot/kernel/iwn2000fw.ko
+
* /boot/kernel/iwn2030fw.ko
+
* /boot/kernel/iwn4965fw.ko
+
* /boot/kernel/iwn5000fw.ko
+
* /boot/kernel/iwn5150fw.ko
+
* /boot/kernel/iwn6000fw.ko
+
* /boot/kernel/iwn6000g2afw.ko
+
* /boot/kernel/iwn6000g2bfw.ko
+
* /boot/kernel/iwn6050fw.ko
+
* /boot/kernel/jedec_dimm.ko
+
* /boot/kernel/joy.ko
+
* /boot/kernel/kbdmux.ko
+
* /boot/kernel/kern_testfrwk.ko
+
* /boot/kernel/kernel
+
* /boot/kernel/kgssapi.ko
+
* /boot/kernel/kgssapi_krb5.ko
+
* /boot/kernel/krpc.ko
+
* /boot/kernel/krping.ko
+
* /boot/kernel/ksyms.ko
+
* /boot/kernel/libalias.ko
+
* /boot/kernel/libiconv.ko
+
* /boot/kernel/libmchain.ko
+
* /boot/kernel/linker.hints
+
* /boot/kernel/linprocfs.ko
+
* /boot/kernel/linsysfs.ko
+
* /boot/kernel/linux.ko
+
* /boot/kernel/linux64.ko
+
* /boot/kernel/linux_common.ko
+
* /boot/kernel/linuxkpi.ko
+
* /boot/kernel/logo_saver.ko
+
* /boot/kernel/lpbb.ko
+
* /boot/kernel/lpt.ko
+
* /boot/kernel/ltc430x.ko
+
* /boot/kernel/mac_biba.ko
+
* /boot/kernel/mac_bsdextended.ko
+
* /boot/kernel/mac_ifoff.ko
+
* /boot/kernel/mac_lomac.ko
+
* /boot/kernel/mac_mls.ko
+
* /boot/kernel/mac_none.ko
+
* /boot/kernel/mac_ntpd.ko
+
* /boot/kernel/mac_partition.ko
+
* /boot/kernel/mac_portacl.ko
+
* /boot/kernel/mac_seeotheruids.ko
+
* /boot/kernel/mac_stub.ko
+
* /boot/kernel/mac_test.ko
+
* /boot/kernel/mach64.ko
+
* /boot/kernel/mdio.ko
+
* /boot/kernel/mem.ko
+
* /boot/kernel/mfi.ko
+
* /boot/kernel/mfi_linux.ko
+
* /boot/kernel/mfip.ko
+
* /boot/kernel/mga.ko
+
* /boot/kernel/miibus.ko
+
* /boot/kernel/mlx.ko
+
* /boot/kernel/mlx4.ko
+
* /boot/kernel/mlx4en.ko
+
* /boot/kernel/mlx4ib.ko
+
* /boot/kernel/mlx5.ko
+
* /boot/kernel/mlx5en.ko
+
* /boot/kernel/mlx5ib.ko
+
* /boot/kernel/mlxfw.ko
+
* /boot/kernel/mly.ko
+
* /boot/kernel/mmc.ko
+
* /boot/kernel/mmcsd.ko
+
* /boot/kernel/mpr.ko
+
* /boot/kernel/mps.ko
+
* /boot/kernel/mpt.ko
+
* /boot/kernel/mqueuefs.ko
+
* /boot/kernel/mrsas.ko
+
* /boot/kernel/mrsas_linux.ko
+
* /boot/kernel/msdosfs.ko
+
* /boot/kernel/msdosfs_iconv.ko
+
* /boot/kernel/mthca.ko
+
* /boot/kernel/mvs.ko
+
* /boot/kernel/mw88W8363fw.ko
+
* /boot/kernel/mx25l.ko
+
* /boot/kernel/mxge_eth_z8e.ko
+
* /boot/kernel/mxge_ethp_z8e.ko
+
* /boot/kernel/mxge_rss_eth_z8e.ko
+
* /boot/kernel/mxge_rss_ethp_z8e.ko
+
* /boot/kernel/nctgpio.ko
+
* /boot/kernel/ndis.ko
+
* /boot/kernel/netgraph.ko
+
* /boot/kernel/nfscl.ko
+
* /boot/kernel/nfscommon.ko
+
* /boot/kernel/nfsd.ko
+
* /boot/kernel/nfslock.ko
+
* /boot/kernel/nfslockd.ko
+
* /boot/kernel/nfsmb.ko
+
* /boot/kernel/nfssvc.ko
+
* /boot/kernel/ng_async.ko
+
* /boot/kernel/ng_atmllc.ko
+
* /boot/kernel/ng_bluetooth.ko
+
* /boot/kernel/ng_bpf.ko
+
* /boot/kernel/ng_bridge.ko
+
* /boot/kernel/ng_bt3c.ko
+
* /boot/kernel/ng_btsocket.ko
+
* /boot/kernel/ng_car.ko
+
* /boot/kernel/ng_ccatm.ko
+
* /boot/kernel/ng_cisco.ko
+
* /boot/kernel/ng_deflate.ko
+
* /boot/kernel/ng_device.ko
+
* /boot/kernel/ng_echo.ko
+
* /boot/kernel/ng_eiface.ko
+
* /boot/kernel/ng_etf.ko
+
* /boot/kernel/ng_ether.ko
+
* /boot/kernel/ng_ether_echo.ko
+
* /boot/kernel/ng_frame_relay.ko
+
* /boot/kernel/ng_gif.ko
+
* /boot/kernel/ng_gif_demux.ko
+
* /boot/kernel/ng_hci.ko
+
* /boot/kernel/ng_hole.ko
+
* /boot/kernel/ng_hub.ko
+
* /boot/kernel/ng_iface.ko
+
* /boot/kernel/ng_ip_input.ko
+
* /boot/kernel/ng_ipfw.ko
+
* /boot/kernel/ng_ksocket.ko
+
* /boot/kernel/ng_l2cap.ko
+
* /boot/kernel/ng_l2tp.ko
+
* /boot/kernel/ng_lmi.ko
+
* /boot/kernel/ng_mppc.ko
+
* /boot/kernel/ng_nat.ko
+
* /boot/kernel/ng_netflow.ko
+
* /boot/kernel/ng_one2many.ko
+
* /boot/kernel/ng_patch.ko
+
* /boot/kernel/ng_pipe.ko
+
* /boot/kernel/ng_ppp.ko
+
* /boot/kernel/ng_pppoe.ko
+
* /boot/kernel/ng_pptpgre.ko
+
* /boot/kernel/ng_pred1.ko
+
* /boot/kernel/ng_rfc1490.ko
+
* /boot/kernel/ng_socket.ko
+
* /boot/kernel/ng_source.ko
+
* /boot/kernel/ng_split.ko
+
* /boot/kernel/ng_sppp.ko
+
* /boot/kernel/ng_sscfu.ko
+
* /boot/kernel/ng_sscop.ko
+
* /boot/kernel/ng_tag.ko
+
* /boot/kernel/ng_tcpmss.ko
+
* /boot/kernel/ng_tee.ko
+
* /boot/kernel/ng_tty.ko
+
* /boot/kernel/ng_ubt.ko
+
* /boot/kernel/ng_UI.ko
+
* /boot/kernel/ng_uni.ko
+
* /boot/kernel/ng_vjc.ko
+
* /boot/kernel/ng_vlan.ko
+
* /boot/kernel/ngatmbase.ko
+
* /boot/kernel/nmdm.ko
+
* /boot/kernel/ntb.ko
+
* /boot/kernel/ntb_hw_amd.ko
+
* /boot/kernel/ntb_hw_intel.ko
+
* /boot/kernel/ntb_hw_plx.ko
+
* /boot/kernel/ntb_transport.ko
+
* /boot/kernel/nullfs.ko
+
* /boot/kernel/nvd.ko
+
* /boot/kernel/nvdimm.ko
+
* /boot/kernel/nvme.ko
+
* /boot/kernel/nvram.ko
+
* /boot/kernel/nxprtc.ko
+
* /boot/kernel/ocs_fc.ko
+
* /boot/kernel/ohci.ko
+
* /boot/kernel/opensolaris.ko
+
* /boot/kernel/otusfw_init.ko
+
* /boot/kernel/otusfw_main.ko
+
* /boot/kernel/ow.ko
+
* /boot/kernel/ow_temp.ko
+
* /boot/kernel/owc.ko
+
* /boot/kernel/padlock.ko
+
* /boot/kernel/padlock_rng.ko
+
* /boot/kernel/pccard.ko
+
* /boot/kernel/pcf.ko
+
* /boot/kernel/pf.ko
+
* /boot/kernel/pflog.ko
+
* /boot/kernel/pfsync.ko
+
* /boot/kernel/plasma_saver.ko
+
* /boot/kernel/plip.ko
+
* /boot/kernel/pmspcv.ko
+
* /boot/kernel/ppbus.ko
+
* /boot/kernel/ppc.ko
+
* /boot/kernel/ppi.ko
+
* /boot/kernel/pps.ko
+
* /boot/kernel/procfs.ko
+
* /boot/kernel/profile.ko
+
* /boot/kernel/proto.ko
+
* /boot/kernel/prototype.ko
+
* /boot/kernel/pseudofs.ko
+
* /boot/kernel/pty.ko
+
* /boot/kernel/puc.ko
+
* /boot/kernel/pwmbus.ko
+
* /boot/kernel/pwmc.ko
+
* /boot/kernel/r128.ko
+
* /boot/kernel/radeonkms.ko
+
* /boot/kernel/radeonkmsfw_ARUBA_me.ko
+
* /boot/kernel/radeonkmsfw_ARUBA_pfp.ko
+
* /boot/kernel/radeonkmsfw_ARUBA_rlc.ko
+
* /boot/kernel/radeonkmsfw_BARTS_mc.ko
+
* /boot/kernel/radeonkmsfw_BARTS_me.ko
+
* /boot/kernel/radeonkmsfw_BARTS_pfp.ko
+
* /boot/kernel/radeonkmsfw_BTC_rlc.ko
+
* /boot/kernel/radeonkmsfw_CAICOS_mc.ko
+
* /boot/kernel/radeonkmsfw_CAICOS_me.ko
+
* /boot/kernel/radeonkmsfw_CAICOS_pfp.ko
+
* /boot/kernel/radeonkmsfw_CAYMAN_mc.ko
+
* /boot/kernel/radeonkmsfw_CAYMAN_me.ko
+
* /boot/kernel/radeonkmsfw_CAYMAN_pfp.ko
+
* /boot/kernel/radeonkmsfw_CAYMAN_rlc.ko
+
* /boot/kernel/radeonkmsfw_CEDAR_me.ko
+
* /boot/kernel/radeonkmsfw_CEDAR_pfp.ko
+
* /boot/kernel/radeonkmsfw_CEDAR_rlc.ko
+
* /boot/kernel/radeonkmsfw_CYPRESS_me.ko
+
* /boot/kernel/radeonkmsfw_CYPRESS_pfp.ko
+
* /boot/kernel/radeonkmsfw_CYPRESS_rlc.ko
+
* /boot/kernel/radeonkmsfw_JUNIPER_me.ko
+
* /boot/kernel/radeonkmsfw_JUNIPER_pfp.ko
+
* /boot/kernel/radeonkmsfw_JUNIPER_rlc.ko
+
* /boot/kernel/radeonkmsfw_PALM_me.ko
+
* /boot/kernel/radeonkmsfw_PALM_pfp.ko
+
* /boot/kernel/radeonkmsfw_PITCAIRN_ce.ko
+
* /boot/kernel/radeonkmsfw_PITCAIRN_mc.ko
+
* /boot/kernel/radeonkmsfw_PITCAIRN_me.ko
+
* /boot/kernel/radeonkmsfw_PITCAIRN_pfp.ko
+
* /boot/kernel/radeonkmsfw_PITCAIRN_rlc.ko
+
* /boot/kernel/radeonkmsfw_R100_cp.ko
+
* /boot/kernel/radeonkmsfw_R200_cp.ko
+
* /boot/kernel/radeonkmsfw_R300_cp.ko
+
* /boot/kernel/radeonkmsfw_R420_cp.ko
+
* /boot/kernel/radeonkmsfw_R520_cp.ko
+
* /boot/kernel/radeonkmsfw_R600_me.ko
+
* /boot/kernel/radeonkmsfw_R600_pfp.ko
+
* /boot/kernel/radeonkmsfw_R600_rlc.ko
+
* /boot/kernel/radeonkmsfw_R700_rlc.ko
+
* /boot/kernel/radeonkmsfw_REDWOOD_me.ko
+
* /boot/kernel/radeonkmsfw_REDWOOD_pfp.ko
+
* /boot/kernel/radeonkmsfw_REDWOOD_rlc.ko
+
* /boot/kernel/radeonkmsfw_RS600_cp.ko
+
* /boot/kernel/radeonkmsfw_RS690_cp.ko
+
* /boot/kernel/radeonkmsfw_RS780_me.ko
+
* /boot/kernel/radeonkmsfw_RS780_pfp.ko
+
* /boot/kernel/radeonkmsfw_RV610_me.ko
+
* /boot/kernel/radeonkmsfw_RV610_pfp.ko
+
* /boot/kernel/radeonkmsfw_RV620_me.ko
+
* /boot/kernel/radeonkmsfw_RV620_pfp.ko
+
* /boot/kernel/radeonkmsfw_RV630_me.ko
+
* /boot/kernel/radeonkmsfw_RV630_pfp.ko
+
* /boot/kernel/radeonkmsfw_RV635_me.ko
+
* /boot/kernel/radeonkmsfw_RV635_pfp.ko
+
* /boot/kernel/radeonkmsfw_RV670_me.ko
+
* /boot/kernel/radeonkmsfw_RV670_pfp.ko
+
* /boot/kernel/radeonkmsfw_RV710_me.ko
+
* /boot/kernel/radeonkmsfw_RV710_pfp.ko
+
* /boot/kernel/radeonkmsfw_RV730_me.ko
+
* /boot/kernel/radeonkmsfw_RV730_pfp.ko
+
* /boot/kernel/radeonkmsfw_RV770_me.ko
+
* /boot/kernel/radeonkmsfw_RV770_pfp.ko
+
* /boot/kernel/radeonkmsfw_SUMO2_me.ko
+
* /boot/kernel/radeonkmsfw_SUMO2_pfp.ko
+
* /boot/kernel/radeonkmsfw_SUMO_me.ko
+
* /boot/kernel/radeonkmsfw_SUMO_pfp.ko
+
* /boot/kernel/radeonkmsfw_SUMO_rlc.ko
+
* /boot/kernel/radeonkmsfw_TAHITI_ce.ko
+
* /boot/kernel/radeonkmsfw_TAHITI_mc.ko
+
* /boot/kernel/radeonkmsfw_TAHITI_me.ko
+
* /boot/kernel/radeonkmsfw_TAHITI_pfp.ko
+
* /boot/kernel/radeonkmsfw_TAHITI_rlc.ko
+
* /boot/kernel/radeonkmsfw_TURKS_mc.ko
+
* /boot/kernel/radeonkmsfw_TURKS_me.ko
+
* /boot/kernel/radeonkmsfw_TURKS_pfp.ko
+
* /boot/kernel/radeonkmsfw_VERDE_ce.ko
+
* /boot/kernel/radeonkmsfw_VERDE_mc.ko
+
* /boot/kernel/radeonkmsfw_VERDE_me.ko
+
* /boot/kernel/radeonkmsfw_VERDE_pfp.ko
+
* /boot/kernel/radeonkmsfw_VERDE_rlc.ko
+
* /boot/kernel/rain_saver.ko
+
* /boot/kernel/random_fortuna.ko
+
* /boot/kernel/random_OTHER.ko
+
* /boot/kernel/rc4.ko
+
* /boot/kernel/rdrand_rng.ko
+
* /boot/kernel/rsu-rtl8712fw.ko
+
* /boot/kernel/rt2561fw.ko
+
* /boot/kernel/rt2561sfw.ko
+
* /boot/kernel/rt2661fw.ko
+
* /boot/kernel/rt2860fw.ko
+
* /boot/kernel/rtc8583.ko
+
* /boot/kernel/rtwn.ko
+
* /boot/kernel/rtwn-rtl8188eefw.ko
+
* /boot/kernel/rtwn-rtl8188eufw.ko
+
* /boot/kernel/rtwn-rtl8192cfwE.ko
+
* /boot/kernel/rtwn-rtl8192cfwE_B.ko
+
* /boot/kernel/rtwn-rtl8192cfwT.ko
+
* /boot/kernel/rtwn-rtl8192cfwU.ko
+
* /boot/kernel/rtwn-rtl8192eufw.ko
+
* /boot/kernel/rtwn-rtl8812aufw.ko
+
* /boot/kernel/rtwn-rtl8821aufw.ko
+
* /boot/kernel/runfw.ko
+
* /boot/kernel/s3.ko
+
* /boot/kernel/s35390a.ko
+
* /boot/kernel/safe.ko
+
* /boot/kernel/savage.ko
+
* /boot/kernel/sbp.ko
+
* /boot/kernel/sbp_targ.ko
+
* /boot/kernel/scc.ko
+
* /boot/kernel/scsi_low.ko
+
* /boot/kernel/sdhci.ko
+
* /boot/kernel/sdhci_acpi.ko
+
* /boot/kernel/sdhci_pci.ko
+
* /boot/kernel/sdt.ko
+
* /boot/kernel/sem.ko
+
* /boot/kernel/send.ko
+
* /boot/kernel/sfxge.ko
+
* /boot/kernel/sgx.ko
+
* /boot/kernel/sgx_linux.ko
+
* /boot/kernel/siba.ko
+
* /boot/kernel/siba_bhndb.ko
+
* /boot/kernel/siftr.ko
+
* /boot/kernel/siis.ko
+
* /boot/kernel/sis.ko
+
* /boot/kernel/smartpqi.ko
+
* /boot/kernel/smb.ko
+
* /boot/kernel/smbfs.ko
+
* /boot/kernel/smbios.ko
+
* /boot/kernel/smbus.ko
+
* /boot/kernel/snake_saver.ko
+
* /boot/kernel/snd_ad1816.ko
+
* /boot/kernel/snd_als4000.ko
+
* /boot/kernel/snd_atiixp.ko
+
* /boot/kernel/snd_cmi.ko
+
* /boot/kernel/snd_cs4281.ko
+
* /boot/kernel/snd_csa.ko
+
* /boot/kernel/snd_driver.ko
+
* /boot/kernel/snd_ds1.ko
+
* /boot/kernel/snd_emu10k1.ko
+
* /boot/kernel/snd_emu10kx.ko
+
* /boot/kernel/snd_envy24.ko
+
* /boot/kernel/snd_envy24ht.ko
+
* /boot/kernel/snd_es137x.ko
+
* /boot/kernel/snd_ess.ko
+
* /boot/kernel/snd_fm801.ko
+
* /boot/kernel/snd_hda.ko
+
* /boot/kernel/snd_hdspe.ko
+
* /boot/kernel/snd_ich.ko
+
* /boot/kernel/snd_maestro.ko
+
* /boot/kernel/snd_maestro3.ko
+
* /boot/kernel/snd_mss.ko
+
* /boot/kernel/snd_neomagic.ko
+
* /boot/kernel/snd_sb8.ko
+
* /boot/kernel/snd_sb16.ko
+
* /boot/kernel/snd_sbc.ko
+
* /boot/kernel/snd_solo.ko
+
* /boot/kernel/snd_spicds.ko
+
* /boot/kernel/snd_t4dwave.ko
+
* /boot/kernel/snd_uaudio.ko
+
* /boot/kernel/snd_via82c686.ko
+
* /boot/kernel/snd_via8233.ko
+
* /boot/kernel/snd_vibes.ko
+
* /boot/kernel/snp.ko
+
* /boot/kernel/sound.ko
+
* /boot/kernel/speaker.ko
+
* /boot/kernel/spibus.ko
+
* /boot/kernel/spigen.ko
+
* /boot/kernel/splash_bmp.ko
+
* /boot/kernel/splash_pcx.ko
+
* /boot/kernel/splash_txt.ko
+
* /boot/kernel/sppp.ko
+
* /boot/kernel/star_saver.ko
+
* /boot/kernel/superio.ko
+
* /boot/kernel/sym.ko
+
* /boot/kernel/systrace.ko
+
* /boot/kernel/systrace_freebsd32.ko
+
* /boot/kernel/systrace_linux.ko
+
* /boot/kernel/systrace_linux32.ko
+
* /boot/kernel/sysvmsg.ko
+
* /boot/kernel/sysvsem.ko
+
* /boot/kernel/sysvshm.ko
+
* /boot/kernel/t4_tom.ko
+
* /boot/kernel/t4fw_cfg.ko
+
* /boot/kernel/t5fw_cfg.ko
+
* /boot/kernel/t6fw_cfg.ko
+
* /boot/kernel/tcpmd5.ko
+
* /boot/kernel/tdfx.ko
+
* /boot/kernel/tmpfs.ko
+
* /boot/kernel/toecore.ko
+
* /boot/kernel/tpm.ko
+
* /boot/kernel/trm.ko
+
* /boot/kernel/twa.ko
+
* /boot/kernel/twe.ko
+
* /boot/kernel/tws.ko
+
* /boot/kernel/u3g.ko
+
* /boot/kernel/uark.ko
+
* /boot/kernel/uart.ko
+
* /boot/kernel/ubsa.ko
+
* /boot/kernel/ubsec.ko
+
* /boot/kernel/ubser.ko
+
* /boot/kernel/ubtbcmfw.ko
+
* /boot/kernel/uchcom.ko
+
* /boot/kernel/ucom.ko
+
* /boot/kernel/ucycom.ko
+
* /boot/kernel/udbp.ko
+
* /boot/kernel/udf.ko
+
* /boot/kernel/udf_iconv.ko
+
* /boot/kernel/udl.ko
+
* /boot/kernel/uep.ko
+
* /boot/kernel/uether.ko
+
* /boot/kernel/ufm.ko
+
* /boot/kernel/ufoma.ko
+
* /boot/kernel/ufs.ko
+
* /boot/kernel/uftdi.ko
+
* /boot/kernel/ugensa.ko
+
* /boot/kernel/ugold.ko
+
* /boot/kernel/uhci.ko
+
* /boot/kernel/uhid.ko
+
* /boot/kernel/uhid_snes.ko
+
* /boot/kernel/uhso.ko
+
* /boot/kernel/uinput.ko
+
* /boot/kernel/uipaq.ko
+
* /boot/kernel/ukbd.ko
+
* /boot/kernel/uled.ko
+
* /boot/kernel/ulpt.ko
+
* /boot/kernel/umass.ko
+
* /boot/kernel/umcs.ko
+
* /boot/kernel/umct.ko
+
* /boot/kernel/umodem.ko
+
* /boot/kernel/umoscom.ko
+
* /boot/kernel/ums.ko
+
* /boot/kernel/unionfs.ko
+
* /boot/kernel/uplcom.ko
+
* /boot/kernel/urio.ko
+
* /boot/kernel/usb.ko
+
* /boot/kernel/usb_quirk.ko
+
* /boot/kernel/usb_template.ko
+
* /boot/kernel/usfs.ko
+
* /boot/kernel/usie.ko
+
* /boot/kernel/uslcom.ko
+
* /boot/kernel/uvisor.ko
+
* /boot/kernel/uvscom.ko
+
* /boot/kernel/vesa.ko
+
* /boot/kernel/via.ko
+
* /boot/kernel/viapm.ko
+
* /boot/kernel/viawd.ko
+
* /boot/kernel/videomode.ko
+
* /boot/kernel/virtio.ko
+
* /boot/kernel/virtio_balloon.ko
+
* /boot/kernel/virtio_blk.ko
+
* /boot/kernel/virtio_console.ko
+
* /boot/kernel/virtio_pci.ko
+
* /boot/kernel/virtio_random.ko
+
* /boot/kernel/virtio_scsi.ko
+
* /boot/kernel/vkbd.ko
+
* /boot/kernel/vmci.ko
+
* /boot/kernel/vmm.ko
+
* /boot/kernel/vpd.ko
+
* /boot/kernel/vpo.ko
+
* /boot/kernel/warp_saver.ko
+
* /boot/kernel/wbwd.ko
+
* /boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wlan&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wlan].ko -- generic 802.11 link-layer support
+
* /boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wlan_acl&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wlan_acl].ko -- MAC-based ACL support for 802.11 devices
+
* /boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wlan_amrr&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wlan_amrr].ko -- AMRR rate adaptation algorithm support for 802.11 devices
+
* /boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wlan_ccmp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wlan_ccmp].ko -- AES-CCMP crypto support for 802.11 devices
+
* /boot/kernel/wlan_rssadapt.ko
+
* /boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wlan_tkip&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wlan_tkip].ko -- TKIP and Michael crypto support for 802.11 devices
+
* /boot/kernel/[ttps://www.freebsd.org/cgi/man.cgi?query=wlan_wep&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wlan_wep].ko  -- WEP crypto support for 802.11 devices
+
* /boot/kernel/[ttps://www.freebsd.org/cgi/man.cgi?query=wlan_xauth&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wlan_xauth].ko -- External authenticator support for 802.11 devices
+
* /boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wmt&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wmt].ko -- MS Windows 7/8/10 - compatible USB HID multi-touch device driver
+
* /boot/kernel/wpifw.ko
+
* /boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wsp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wsp].ko -- Wellspring touchpad driver
+
* /boot/kernel/x86bios.ko
+
* /boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=xhci&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html xhci].ko -- USB eXtensible Host Controller driver
+
* /boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=xz&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html xz].ko - -Compress or decompress .xz and .lzma files
+
* /boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=zfs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html zfs].ko -- configures ZFS file systems
+
* /boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=zlib&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html zlib].ko -- compression/decompression library
+
  
 +
|-
 +
|/boot/kernel/gsched_rr.ko||The [https://www.freebsd.org/cgi/man.cgi?query=gsched&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html gsched ]utility (also callable as geom sched ...) changes the scheduling policy of the requests going to a provider.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=h_ertt&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html h_ertt].ko||The h_ertt Khelp module works within the khelp(9) framework to provide TCP with a per-connection, low noise estimate of the instantaneous RTT.  The implementation attempts to be robust in the face of delayed acknowledgements, TCP Segmentation Offload (TSO), receivers who manipulate TCP timestamps and lack of the TCP timestamp option altogether.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=hifn&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html hifn].ko||The hifn driver supports various cards containing the Hifn 7751, 7951,    7811, 7955, and 7956 chipsets.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=hpt27xx&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html hpt27xx].ko|| The hpt27xx driver provides support for HighPoint's RocketRAID 27xx based    RAID controller.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=hptiop&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html hptiop].ko||The hptiop driver provides support for the HighPoint RocketRAID 3xxx/4xxx    series of SAS and SATA RAID controllers.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=hptmv&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html hptmv].ko||HighPoint RocketRAID 182x device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=hptnr&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html hptnr].ko||HighPoint DC Series Data Center HBA card driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=hptrr&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html hptrr].ko||HighPoint RocketRAID device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=hv_netvsc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html hv_netvsc].ko||The hv_netvsc driver implements the virtual network device for FreeBSD guest partitions running on Hyper-V.  FreeBSD guest partitions running on    Hyper-V do not have direct access to network devices attached to the Hyper-V server.  Although a FreeBSD guest can access network devices using  Hyper-V's full emulation mode, the performance in this mode tends to be  unsatisfactory.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=hv_storvsc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html hv_storvsc].ko||Hyper-V Storage Virtual Service Consumer
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=hv_utils&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html hv_utils].ko||The hv_utils driver provides time keeping, shutdown and heartbeat functionality for FreeBSD guest partitions running on Hyper-V. Hyper-V is a  hypervisor-based virtualization technology from Microsoft. The hv_utils    driver is one of the core drivers required to be present in guest partitions running on Hyper-V.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=hv_vmbus&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html hv_vmbus].ko||The hv_vmbus provides a high performance communication interface between guest and root partitions in Hyper-V.  Hyper-V is a hypervisor-based virtualization technology from Microsoft.  Hyper-V supports isolation in  terms of a partition.  A partition is a logical unit of isolation, supported by the hypervisor, in which operating systems execute.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=hwpmc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html hwpmc].ko||The hwpmc driver virtualizes the hardware performance monitoring facilities in modern CPUs and provides support for using these facilities from  user level processes.
 +
|-
 +
|/boot/kernel/i915kms.ko||Intel i915 KMS driver
 +
|-
 +
|/boot/kernel/ibcore.ko||[https://wiki.freebsd.org/InfiniBand]
 +
|-
 +
|/boot/kernel/icee.ko||[https://www.leidinger.net/FreeBSD/dox/dev_iicbus/html/de/d92/icee_8c.html]
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ichsmb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ichsmb].ko|| The ichsmb driver provides smbus(4) support for the SMBus controller logical device contained in all Intel motherboard chipsets starting from  82801AA (ICH).
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ichwd&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ichwd].ko||The ichwd driver provides watchdog(4) support for the watchdog interrupt timer present on all Intel ICH motherboard chipsets.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ida&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ida].ko||Ida  is a  small  and  fast application for viewing images. Some basic      editing functions are available too.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ae&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ae].ko||Attansic/Atheros L2 FastEthernet controller driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_age&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_age].ko||Attansic/Atheros L1 Gigabit Ethernet driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_alc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_alc].ko||Atheros AR813x/AR815x/AR816x/AR817x Gigabit/Fast Ethernet driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ale&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ale].ko||Atheros AR8121/AR8113/AR8114 Gigabit/Fast Ethernet driver
  
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_an&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_an].ko||Aironet Communications 4500/4800 wireless network adapter driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ath&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ath].ko||Atheros IEEE 802.11 wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ath_pci&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ath_pci].ko||This module provides the PCI/PCIe bus glue needed for the devices supported by the ath(4) and ath_hal(4) drivers.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_aue&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_aue].ko||The aue driver provides support for USB Ethernet adapters based on the    ADMtek AN986 Pegasus chipset.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_axe&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_axe].ko||The axe driver provides support for USB Ethernet adapters based on the      ASIX Electronics AX88172, AX88178, AX88772, AX88772A, AX88772B and    AX88760 USB 2.0 chipsets.
  
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/usb/net/if_axge.c if_axge].ko||ASIX Electronics AX88178A/AX88179 USB 2.0/3.0 gigabit ethernet driver.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_bce&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_bce].ko||QLogic NetXtreme II (BCM5706/5708/5709/5716) PCI/PCIe Gigabit Ethernet adapter driver
  
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_bfe&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_bfe].ko||Broadcom BCM4401 Ethernet Device Driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_bge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_bge].ko||Broadcom BCM57xx/BCM590x Gigabit/Fast Ethernet driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_bnxt&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_bnxt].ko||Broadcom NetXtreme-C/NetXtreme-E Family Ethernet driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_bridge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_bridge].ko||The if_bridge driver creates a logical link between two or more IEEE 802 networks that use the same (or "similar enough") framing format.  For example, it is possible to bridge Ethernet and 802.11 networks together,  but it is not possible to bridge Ethernet and Token Ring together.
  
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_bwi&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_bwi].ko||Broadcom BCM43xx IEEE 802.11b/g wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_bwn&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_bwn].ko||Broadcom BCM43xx SoftMAC IEEE 802.11 wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_bxe&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_bxe].ko||QLogic NetXtreme II Ethernet 10Gb PCIe adapter driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_cas&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_cas].ko||Sun Cassini/Cassini+ and National Semiconductor DP83065 Saturn Gigabit Ethernet driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_cc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_cc].ko||Chelsio T4-, T5-, and T6-based 100Gb, 40Gb, 25Gb, 10Gb, and 1Gb Ethernet adapter driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ccv&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ccv].ko||Chelsio T4-, T5-, and T6-based 100Gb, 40Gb, 25Gb, 10Gb, and 1Gb  Ethernet VF driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_cdce&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_cdce].ko||USB Communication Device Class Ethernet (CDC ECM/NCM) driver
 +
|-
 +
|/boot/kernel/if_cdceem.ko||[https://www.leidinger.net/FreeBSD/dox/dev_usb/html/d5/d48/if__cdceem_8c.html] Universal Serial Bus Communications Class Subclass Specification for Ethernet Emulation Model Devices.
 +
|-
 +
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/dev_cs/html/d8/d8a/if__cs_8c_source.html if_cs].ko||Device driver for Crystal Semiconductor CS8920 based ethernet  adapters. By Maxim Bolotin and Oleg Sharoiko, 27-April-1997
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_cue&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_cue].ko||CATC USB-EL1210A USB Ethernet driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_cxgb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_cxgb].ko||Chelsio T3 10 Gigabit Ethernet adapter driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_cxgbe&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_cxgbe].ko||Chelsio T4-, T5-, and T6-based 100Gb, 40Gb, 25Gb, 10Gb, and 1Gb    Ethernet adapter driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_cxgbev&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_cxgbev].ko||Chelsio T4-, T5-, and T6-based 100Gb, 40Gb, 25Gb, 10Gb, and 1Gb  Ethernet VF driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_cxl&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_cxl].ko||Chelsio T4-, T5-, and T6-based 100Gb, 40Gb, 25Gb, 10Gb, and 1Gb Ethernet adapter driver
  
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_cxlv&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_cxlv].ko||Chelsio T4-, T5-, and T6-based 100Gb, 40Gb, 25Gb, 10Gb, and 1Gb  Ethernet VF driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_dc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_dc].ko||DEC/Intel 21143 and clone 10/100 Ethernet driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_de&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_de].ko||DEC DC21x4x Ethernet device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_disc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_disc].ko||The disc interface is a software discard mechanism which may be used for      performance analysis and/or software testing.  As with other network interfaces, the discard interface must have network addresses assigned for  each address family with which it is to be used.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ed&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ed].ko||NE-2000 and WD-80x3 Ethernet driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_edsc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_edsc].ko||The edsc interface is a software discard mechanism which may be used for performance analysis and software testing. It imitates an Ethernet device, which allows for its use in conjunction with such drivers as  if_bridge(4) and vlan(4).
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_em&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_em].ko||Intel(R) PRO/1000 Gigabit Ethernet adapter driver
 +
|-
 +
|/boot/kernel/[https://github.com/amzn/amzn-drivers/tree/master/kernel/fbsd/ena if_ena].ko||FreeBSD kernel driver for Elastic Network Adapter (ENA) family
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_enc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_enc].ko||The enc interface is a software loopback mechanism that allows hosts or firewalls to filter ipsec(4) traffic using any firewall package that  hooks in via the pfil(9) framework.
 +
|-
 +
|/boot/kernel/if_ep.ko||[https://www.leidinger.net/FreeBSD/dox/dev_ep/html/d4/d2a/if__ep_8c_source.html]
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_epair&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_epair].ko||The epair is a pair of Ethernet-like software interfaces, which are connected back-to-back with a virtual cross-over cable.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_et&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_et].ko||Agere ET1310 10/100/Gigabit Ethernet driver
 +
|-
 +
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/dev_fe/html/d6/dd9/if__fe_8c_source.html#l00118 if_fe].ko||Device driver for Fujitsu MB86960A/MB86965A based Ethernet cards.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_fwe&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_fwe].ko||Ethernet emulation driver for FireWire
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_fwip&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_fwip].ko||IP over FireWire driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_fxp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_fxp].ko||Intel EtherExpress PRO/100 Ethernet device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_gem&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_gem].ko||ERI/GEM/GMAC Ethernet device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_gif&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_gif].ko|| The gif interface is a generic tunnelling device for IPv4 and IPv6.  It  can tunnel IPv[46] traffic over IPv[46].  Therefore, there can be four    possible configurations.  The behavior of gif is mainly based on RFC2893    IPv6-over-IPv4 configured tunnel. On NetBSD, gif can also tunnel ISO traffic over IPv[46] using EON encapsulation.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_gre&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_gre].ko||The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they  are decapsulated and further routed to their final destination.  The    "tunnel" appears to the inner datagrams as one hop.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_hme&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_hme].ko||Sun Microelectronics STP2002-STQ Ethernet interfaces device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_iavf&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_iavf].ko||The iavf driver provides support for the PCI Virtual Functions from the  700 Series of ethernet devices and newer product families. The driver  supports Jumbo Frames, TX/RX checksum offload, TCP segmentation offload  (TSO), Large Receive Offload (LRO), VLAN tag insertion/extraction, VLAN  checksum offload, VLAN TSO, and Receive Side Steering (RSS), all for both  IPv4 and IPv6.
 +
|-
 +
|/boot/kernel/[https://www.leidinger.net/freebsd/dox/dev_iicbus/html/d7/da5/if__ic_8c_source.html#l00097 if_ic].ko||I2C bus IP driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_igb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_igb].ko||The igb driver provides support for PCI Express Gigabit Ethernet adapters  based on the Intel 82575, 82576, 82580, i21x and i35x Ethernet controller  chips.  The driver supports Transmit/Receive checksum offload and Jumbo Frames.  Furthermore it supports TCP segmentation offload (TSO) on all  adapters.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ipheth&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ipheth].ko||The ''ipheth'' driver provides support for network access through Apple  iPhone and iPad devices, often referred to as USB tethering. ''ipheth'' should work with any Apple iPhone or iPad device.  In most cases this must be explicitly enabled on the device first.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ipw&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ipw].ko||The ipw driver provides support for the Intel PRO/Wireless 2100 MiniPCI  network adapter.  ipw supports station, adhoc, and monitor mode operation.  Only one virtual interface may be configured at any time.  For  more information on configuring this device, see ifconfig(8).
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_iwi&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_iwi].ko||The iwi driver provides support for Intel PRO/Wireless 2200BG/2915ABG  MiniPCI and 2225BG PCI network adapters.  iwi supports station, adhoc,  and monitor mode operation.  Only one virtual interface may be configured  at any time.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_iwm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_iwm].ko||Intel IEEE 802.11ac wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_iwn&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_iwn].ko||Intel IEEE 802.11n wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ix&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ix].ko||The ixgbe driver provides support for PCI 10Gb Ethernet adapters based on the Intel 82598EB Intel(R) Network Connections.  The driver supports  Jumbo Frames, MSIX, TSO, and RSS
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ixl&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ixl].ko||Intel Ethernet 700 Series Driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ixlv&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ixlv].ko||Intel XL710 Ethernet 40Gb VF driver
 +
|-
 +
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/dev_ixgbe/html/d6/d89/if__ixv_8c.html if_ixv].ko||ixv_driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_jme&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_jme].ko||The jme device driver provides support for JMicron JMC25x PCI Express Gigabit Ethernet controllers and JMicron JMC26x PCI Express Fast Ethernet  controllers.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_kue&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_kue].ko||The kue driver provides support for USB Ethernet adapters based on the  Kawasaki LSI KL5KLUSB101B chipset.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_lagg&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_lagg].ko||The lagg interface allows aggregation of multiple network interfaces as  one virtual lagg interface for the purpose of providing fault-tolerance  and high-speed links.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_le&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_le].ko||The le driver provides support for Ethernet adapters based on the AMD  Am7990 and Am79C90 (CMOS, pin-compatible) Local Area Network Controller  for Ethernet (LANCE) chips.
  
 +
|-
 +
|boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_lge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_lge].ko||Level 1 LXT1001 NetCellerator PCI Gigabit Ethernet adapter driver
  
 +
|-
 +
|/boot/kernel/if_lio.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_malo&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_malo].ko||Marvell Libertas IEEE 802.11b/g wireless network driver
 +
 +
|-
 +
|/boot/kernel/if_me.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_mos&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_mos].ko||Moschip MCS7730/MCS7830/MCS7832 USB Ethernet driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_msk&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_msk].ko||Marvell/SysKonnect Yukon II Gigabit Ethernet adapter driver
 +
|-
 +
|/boot/kernel/if_muge.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_mwl&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_mwl].ko||Marvell 88W8363 IEEE 802.11n wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_mxge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_mxge].ko||Myricom Myri10GE 10 Gigabit Ethernet adapter driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_my&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_my].ko||Myson Technology Ethernet PCI driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ndis&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ndis].ko||The ndis driver is a wrapper designed to allow binary Windows(R) NDIS miniport network drivers to be used with FreeBSD.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_nfe&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_nfe].ko||NVIDIA nForce MCP Ethernet driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_nge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_nge].ko||The nge driver provides support for various NICs based on the National  Semiconductor DP83820 and DP83821 Gigabit Ethernet controller chips.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ntb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ntb].ko||Virtual Ethernet interface for Non-Transparent Bridges
 +
|-
 +
|/boot/kernel/if_oce.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_otus&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_otus].ko||Atheros AR9170 USB IEEE 802.11a/b/g/n wireless network device
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_pcn&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_pcn].ko||AMD PCnet/PCI Fast Ethernet device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_qlnxe&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_qlnxe].ko||Cavium 25/40/100 Gigabit Ethernet & CNA Adapter Driver
 +
|-
 +
|/boot/kernel/if_qlnxev.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_qlxgb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_qlxgb].ko||QLogic 10 Gigabit Ethernet & CNA Adapter Driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_qlxgbe&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_qlxgbe].ko||QLogic 10 Gigabit Ethernet & CNA Adapter Driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_qlxge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_qlxge].ko||QLogic 8100 Series 10 Gigabit Ethernet Adapter Driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ral&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ral].ko||Ralink Technology IEEE 802.11a/g/n wireless network device
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_re&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_re].ko||RealTek 8139C+/8169/816xS/811xS/8168/810xE/8111 PCI/PCIe Ethernet  adapter driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_rl&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_rl].ko||RealTek 8129/8139 Fast Ethernet device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_rsu&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_rsu].ko||Realtek RTL8188SU/RTL8192SU USB IEEE 802.11b/g/n wireless network  device
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_rtwn_pci&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_rtwn_pci].ko || Realtek PCI device glue
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_rtwn_usb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_rtwn_usb].ko || Realtek USB device glue
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_rue&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_rue].ko||RealTek RTL8150 USB to Fast Ethernet controller driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_rum&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_rum].ko||Ralink Technology USB IEEE 802.11a/b/g wireless network device
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_run&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_run].ko||Ralink Technology USB IEEE 802.11a/g/n wireless network device
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_sf&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_sf].ko||Adaptec AIC-6915 "Starfire" PCI Fast Ethernet adapter driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_sge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_sge].ko||Silicon Integrated Systems SiS190/191 Fast/Gigabit Ethernet driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_sis&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_sis].ko||SiS 900, SiS 7016 and NS DP83815/DP83816 Fast Ethernet device
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_sk&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_sk].ko||SysKonnect SK-984x and SK-982x PCI Gigabit Ethernet adapter driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_smsc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_smsc].ko||USB SMSC LAN9xxx Fast Ethernet driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_sn&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_sn].ko||Ethernet driver for SMC91Cxx based cards
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ste&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ste].ko||Sundance Technologies ST201 Fast Ethernet device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_stf&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_stf].ko|| The stf interface supports "6to4" IPv6 in IPv4 encapsulation.  It can  tunnel IPv6 traffic over IPv4, as specified in RFC3056.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_stge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_stge].ko||Sundance/Tamarack TC9021 Gigabit Ethernet adapter driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_tap&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_tap].ko||The tap interface is a software loopback mechanism that can be loosely    described as the network interface analog of the pty(4), that is, tap  does for network interfaces what the pty(4) driver does for terminals.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ti&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ti].ko||Alteon Networks Tigon I and Tigon II Gigabit Ethernet driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_tl&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_tl].ko||Texas Instruments ThunderLAN Ethernet device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_tun&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_tun].ko||The tun interface is a software loopback mechanism that can be loosely  described as the network interface analog of the pty(4), that is, tun    does for network interfaces what the pty(4) driver does for terminals.
 +
|-
 +
|/boot/kernel/if_tuntap.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_tx&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_tx].ko||SMC 83c17x Fast Ethernet device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_txp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_txp].ko||3Com 3XP Typhoon/Sidewinder (3CR990) Ethernet interface
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_uath&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_uath].ko||Atheros USB IEEE 802.11a/b/g wireless network device
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_udav&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_udav].ko||Davicom DM9601 USB Ethernet driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_upgt&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_upgt].ko||Conexant/Intersil PrismGT SoftMAC USB IEEE 802.11b/g wireless  network device
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ural&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ural].ko||Ralink Technology RT2500USB IEEE 802.11 driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_ure&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_ure].ko||RealTek RTL8152/RTL8153 USB to Ethernet controller driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_urndis&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_urndis].ko||USB Remote NDIS Ethernet device
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_urtw&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_urtw].ko||Realtek RTL8187B/L USB IEEE 802.11b/g wireless network device
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_vge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_vge].ko||VIA Networking Technologies Velocity Gigabit Ethernet adapter
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_vlan&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_vlan].ko||IEEE 802.1Q VLAN network interface
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_vmx&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_vmx].ko||VMware VMXNET3 Virtual Interface Controller device
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_vr&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_vr].ko||VIA Technologies Rhine I/II/III Ethernet device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_vte&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_vte].ko||Vortex86 RDC R6040 Fast Ethernet driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_vtnet&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_vtnet].ko||The vtnet device driver provides support for VirtIO Ethernet devices.
 +
|-
 +
|/boot/kernel/if_vx.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_vxlan&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_vxlan].ko||Virtual eXtensible LAN interface
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_wb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_wb].ko||Winbond W89C840F Fast Ethernet device driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_wi&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_wi].ko||Lucent Hermes, and Intersil PRISM IEEE 802.11 driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_wpi&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_wpi].ko||Intel 3945ABG Wireless LAN IEEE 802.11 driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_xe&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_xe].ko||Xircom PCMCIA Ethernet device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_xl&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_xl].ko||3Com Etherlink XL and Fast Etherlink XL Ethernet device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=if_zyd&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_zyd].ko||ZyDAS ZD1211/ZD1211B USB IEEE 802.11b/g wireless network device
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iflib&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html iflib].ko||iflib is a framework for network interface drivers for FreeBSD.  It is  designed to remove a large amount of the boilerplate that is often needed  for modern network interface devices, allowing driver authors to focus on    the specific code needed for their hardware.  This allows for a shared    set of sysctl(8) names, rather than each driver naming them individually.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ig4&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ig4].ko||The ig4 driver provides access to peripherals attached to an I2C controller.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iic&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html iic].ko||The iic device driver provides generic I/O to any iicbus(4) instance. 
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iicbb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html iicbb].ko|| The iicbb driver provides support to any bit-banging interface for the  iicbus(4) system.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iicbus&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html iicbus].ko|| The iicbus system provides a uniform, modular and architecture-independent system for the implementation of drivers to control various I2C devices and to utilize different I2C controllers.
 +
|-
 +
|/boot/kernel/iicmux.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iicsmb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html iicsmb].ko||The iicsmb driver supports SMB commands over iicbus(4) for the smbus(4)  system.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iir&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html iir].ko||Intel Integrated RAID controller and ICP Vortex driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=imcsmb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html imcsmb].ko||Intel integrated Memory Controller (iMC) SMBus controller  driver
 +
|-
 +
|/boot/kernel/[https://lists.freebsd.org/pipermail/freebsd-arch/2013-May/014361.html imgact_binmisc].ko||imgact_binmisc is an image activator for miscellaneous binary file types that are executed with the help of a user-level interpreter or emulator.
 +
|-
 +
|/boot/kernel/[https://kernelnomicon.org/ intelspi].ko||Driver for SPI support on Minnowboard is intelspi. Hardware supports all four SPI modes and clock frequency configuration but the driver doesn’t (yet). So it’s always mode 0 and frequency is hardcoded to 10MHz. To access it from userland you’d use spigen driver for now.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=intpm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html intpm].ko||Intel PIIX4 Power Management controller driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=io&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html io].ko||Standard I/O Server Interface Functions
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ioat&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ioat].ko||Intel I/O Acceleration Technology
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/netinet6/ip6_mroute.h ip6_mroute].ko||Multicast Routing set/getsockopt commands.
 +
|-
 +
|/boot/kernel/[http://troglobit.github.io/howto/mrouting-in-freebsd/ ip_mroute].ko||Multicast Routing to FreeBSD kernel
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?divert(4) ipdivert].ko||kernel packet diversion mechanism
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ipfw&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ipfw].ko||User interface for firewall, traffic shaper, packet scheduler,  in-kernel NAT
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/doc/handbook/firewalls-ipfw.html ipfw_nat].ko||IPFW is a stateful firewall written for FreeBSD which supports both IPv4 and IPv6. It is comprised of several components: the kernel firewall filter rule processor and its integrated packet accounting facility, the logging facility, NAT, the dummynet(4) traffic shaper, a forward facility, a bridge facility, and an ipstealth facility.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/doc/handbook/firewalls-ipfw.html ipfw_nat64].ko||IPFW is a stateful firewall written for FreeBSD which supports both IPv4 and IPv6. It is comprised of several components: the kernel firewall filter rule processor and its integrated packet accounting facility, the logging facility, NAT, the dummynet(4) traffic shaper, a forward facility, a bridge facility, and an ipstealth facility.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/doc/handbook/firewalls-ipfw.html ipfw_nptv6].ko||IPFW is a stateful firewall written for FreeBSD which supports both IPv4 and IPv6. It is comprised of several components: the kernel firewall filter rule processor and its integrated packet accounting facility, the logging facility, NAT, the dummynet(4) traffic shaper, a forward facility, a bridge facility, and an ipstealth facility.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/doc/handbook/firewalls-ipfw.html ipfw_pmod].ko||IPFW is a stateful firewall written for FreeBSD which supports both IPv4 and IPv6. It is comprised of several components: the kernel firewall filter rule processor and its integrated packet accounting facility, the logging facility, NAT, the dummynet(4) traffic shaper, a forward facility, a bridge facility, and an ipstealth facility.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ipl&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ipl].ko||IP packet log device
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ipmi&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ipmi].ko||OpenIPMI compatible IPMI interface driver. The IPMI (Intelligent Platform Management Interface) is a standard for
 +
monitoring system hardware by permitting generic code to detect and monitor the sensors in a system.  The IPMI standard offers watchdog support,  an FRU database, and other support extensions.  It is currently being  adopted by the makers of many single board and embedded system anufacturers.
 +
 +
|-
 +
|/boot/kernel/[https://www.leidinger.net/freebsd/dox/dev_ipmi/html/d5/da4/ipmi__linux_8c_source.html ipmi_linux].ko||Linux ioctl handler for the ipmi device driver
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/tree/master/sys/ofed/drivers/infiniband/ulp ipoib].ko||Fix some whitespace issues in ipoib.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ips&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ips].ko||IBM/Adaptec ServeRAID controller driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ipsec&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ipsec].ko||The ipsec utility invokes any of several utilities involved in controlling and monitoring the IPsec encryption/authentication system, running  the specified command with the specified arguments and options as if it  had been invoked directly. This largely eliminates possible name collisions with other software, and also permits some centralized services.
 +
|-
 +
|/boot/kernel/ipw_bss.ko||You need to read the LICENSE file in /usr/share/doc/legal/intel,  If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
 +
|-
 +
|/boot/kernel/ipw_ibss.ko||You need to read the LICENSE file in /usr/share/doc/legal/intel,  If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
 +
|-
 +
|/boot/kernel/ipw_monitor.ko||You need to read the LICENSE file in /usr/share/doc/legal/intel,  If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=isci&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html isci].ko||The isci driver provides support for Intel C600 SAS controllers.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iscsi&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html iscsi].ko||The iscsi subsystem provides the kernel component of an iSCSI initiator, responsible for implementing the Full Feature Phase of the iSCSI protocol.  The initiator is the iSCSI client, which connects to an iSCSI target, providing local access to a remote block device.  The userland component is provided by iscsid(8) and both the kernel and userland are configured using iscsictl(8).
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iscsi_initiator&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html iscsi_initiator].ko||This driver, along with its userspace counterpart iscontrol(8), is obsolete.  Users are advised to use iscsi(4) instead.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iser&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html iser].ko||The iser (iSCSI Extensions for RDMA) initiator driver extends the iSCSI  protocol to RDMA. It permits data to be transferred directly into and  out of SCSI buffers without intermediate data copies.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=isl&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html isl].ko||Intersil(TM) I2C ISL29018 sensor driver
 +
 +
|-
 +
|/boot/kernel/[ttps://www.leidinger.net/FreeBSD/dox/dev_iicbus/html/d9/db5/isl12xx_8c_source.html isl12xx].ko||Driver for ISL12xx family i2c realtime clocks
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ismt&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ismt].ko||Intel SMBus Message Transport (SMBus 2.0) driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=isp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html isp].ko||Qlogic based SPI and FibreChannel SCSI Host Adapters
 +
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_1040].ko||ISP Firmware Modules for FreeBSD
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_1080].ko||ISP Firmware Modules for FreeBSD
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_2100].ko||ISP Firmware Modules for FreeBSD
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_2200].ko||ISP Firmware Modules for FreeBSD
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_2300].ko||ISP Firmware Modules for FreeBSD
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_2322].ko||ISP Firmware Modules for FreeBSD
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_2400].ko||ISP Firmware Modules for FreeBSD
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_2500].ko||ISP Firmware Modules for FreeBSD
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_12160].ko||ISP Firmware Modules for FreeBSD
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ispfw&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ispfw].ko||Firmware for Qlogic based SPI and FibreChannel SCSI Host  Adapters
 +
 +
|-
 +
|/boot/kernel/[https://svnweb.freebsd.org/base?view=revision&revision=256694 iw_cxgbe].ko||iWARP driver for Chelsio T4/T5 chips.  This is a straight port of the iw_cxgb4 found in OFED distributions.
 +
|-
 +
|/boot/kernel/[https://lists.freebsd.org/pipermail/freebsd-stable/2007-October/037799.html iwi_bss].ko||Intel(R) PRO/Wireless 2200BG; You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/. If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
 +
|-
 +
|/boot/kernel/[https://lists.freebsd.org/pipermail/freebsd-ports/2007-March/039137.html iwi_ibss].ko||Add Intel firmwares for Intel PRO/Wireless LAN 2100/2200/2915 cards  in a uuencoded format along with their respective LICENSE files. Add new share/doc/legal directory to BSD.usr.dist mtree file. This  is the place we install LICENSE files for restricted firmwares.
 +
|-
 +
|/boot/kernel/[https://lists.freebsd.org/pipermail/freebsd-ports/2007-March/039137.html iwi_monitor].ko||Add Intel firmwares for Intel PRO/Wireless LAN 2100/2200/2915 cards  in a uuencoded format along with their respective LICENSE files. Add new share/doc/legal directory to BSD.usr.dist mtree file. This  is the place we install LICENSE files for restricted firmwares.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iwm&sektion=4 iwm3160fw].ko||Intel IEEE 802.11ac wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iwm&sektion=4 iwm3168fw].ko||Intel IEEE 802.11ac wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iwm&sektion=4 iwm7260fw].ko||Intel IEEE 802.11ac wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iwm&sektion=4 iwm7265Dfw].ko||Intel IEEE 802.11ac wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iwm&sektion=4 iwm7265fw].ko||Intel IEEE 802.11ac wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iwm&sektion=4 iwm8000Cfw].ko||Intel IEEE 802.11ac wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iwm&sektion=4 iwm8265fw].ko||Intel IEEE 802.11ac wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/dev_iwm/html/da/d35/if__iwm__9000_8c_source.html iwm9000fw].ko||Intel IEEE 802.11ac wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/dev_iwm/html/d0/d9f/if__iwm__9260_8c.html iwm9260fw].ko||Intel IEEE 802.11ac wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn100fw].ko||Firmware Module for Intel Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn105fw].ko||Firmware Module for Intel Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn135fw].ko||Firmware Module for Intel Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn1000fw].ko||Firmware Module for Intel Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn2000fw].ko||Firmware Module for Intel Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn2030fw].ko||Firmware Module for Intel Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn4965fw].ko||Firmware Module for Intel Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn5000fw].ko||Firmware Module for Intel Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn5150fw].ko||Firmware Module for Intel Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn6000fw].ko||Firmware Module for Intel Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn6000g2afw].ko||Firmware Module for Intel Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn6000g2bfw].ko||Firmware Module for Intel Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn6050fw].ko||Firmware Module for Intel Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=jedec_dimm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html jedec_dimm].ko||The jedec_dimm driver reports asset information (Part Number, Serial Number) encoded in the "Serial Presence Detect" (SPD) data on JEDEC DDR3 and DDR4 DIMMs.  It also calculates and reports the memory capacity of the    DIMM, in megabytes.  If the DIMM includes a "Thermal Sensor On DIMM"    (TSOD), the temperature is also reported.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=joy&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html joy].ko||Global array of joystick state information, which  is  updated  by  the  poll_joystick() function.  Only the first num_joysticks elements will  contain meaningful information.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=kbdmux&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html kbdmux].ko||The kbdmux keyboard driver provides support for basic keyboard multiplexing.  It is built around the idea of a "super keyboard".  The kbdmux  driver acts as a master keyboard consuming input from all slave keyboards  attached to it.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=kern_testfrwk&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html kern_testfrwk].ko||A kernel testing framework
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=kernel&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html kernel]||The  Kernel  application is the first application started. It is mandatory in the sense that the minimal system based on Erlang/OTP  consists    of  Kernel  and STDLIB.
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/tree/master/sys/kgssapi kgssapi].ko||Stop using des_cblock for arguments to DES functions.
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/tree/master/sys/kgssapi kgssapi_krb5].ko||Stop using des_cblock for arguments to DES functions.
 +
|-
 +
|/boot/kernel/[https://lists.freebsd.org/pipermail/freebsd-questions/2010-June/217677.html krpc].ko||zfs.ko: depends on krpc - not available or version mismatch
 +
|-
 +
|/boot/kernel/[https://www.phoronix.com/scan.php?page=news_item&px=FreeBSD-11.2-Beta-3-Released krping].ko||support for setting service types for outgoing RDMA connections via the KRPING utility
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ksyms&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ksyms].ko||The /dev/ksyms character device provides a read-only interface to a snapshot of the kernel symbol table.  The in-kernel symbol manager is designed to be able to handle many types of symbols tables, however, only    elf(5) symbol tables are supported by this device. The ELF format image  contains two sections: a symbol table and a corresponding string table.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=libalias&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html libalias].ko||The libalias library is a collection of functions for aliasing and dealiasing of IP packets, intended for masquerading and network address  translation (NAT).
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iconv&sektion=3 libiconv].ko||The iconv_open() function opens a converter from the codeset srcname to  the codeset dstname and returns its descriptor.  The arguments srcname    and dstname accept "" and "char", which refer to the current locale encoding.Supporting function for the common internet file system CIFS and smbfs
 +
|-
 +
|/boot/kernel/libmchain.ko||Supporting function for the common internet file system CIFS and smbfs
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=kldxref&sektion=8&manpath=FreeBSD+5.0-RELEASE linker.hints]||The kldxref utility is used to generate hint files which list modules,
 +
their version numbers, and the files that contain them.  These hints are  used by the kernel loader to determine where to find a particular KLD, Option -f file  Specify a different name for the hint files than linker.hints.    module.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=linprocfs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html linprocfs].ko||Linux process file system
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=linsysfs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html linsysfs].ko||Linux system file system
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=linux&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html linux].ko||Linux ABI support
 +
|-
 +
|/boot/kernel/linux64.ko||
 +
|-
 +
|/boot/kernel/linux_common.ko||
 +
|-
 +
|/boot/kernel/linuxkpi.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?splash(4) logo_saver].ko||Animated graphical FreeBSD logo
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=lpbb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html lpbb].ko||parallel port I2C bit-banging interface
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=lpt&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html lpt].ko||The current lpt driver is the port of the original lpt driver to the  ppbus(4) system.
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES ltc430x].ko||I2C bus multiplexer (mux) devices, LTC4305 and LTC4306 i2c mux chips
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mac_biba&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mac_biba].ko||The mac_biba policy module implements the Biba integrity model, which protects the integrity of system objects and subjects by means of a  strict information flow policy.  In Biba, all system subjects and objects    are assigned integrity labels, made up of hierarchal grades, and non-hi-erarchal components.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mac_bsdextended&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mac_bsdextended].ko||The mac_bsdextended security policy module provides an interface for the  system administrator to impose mandatory rules regarding users and some    system objects.  Rules are uploaded to the module (typically using    ugidfw(8), or some other tool utilizing libugidfw(3)) where they are    stored internally and used to determine whether to allow or deny specific  accesses (see ugidfw(8)).
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mac_ifoff&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mac_ifoff].ko||The mac_ifoff interface silencing module allows administrators to enable    and disable incoming and outgoing data flow on system network interfaces    via the sysctl(8) interface.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mac_lomac&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mac_lomac].ko||The mac_lomac policy module implements the LOMAC integrity model, which    protects the integrity of system objects and subjects by means of an information flow policy coupled with the subject demotion via floating labels.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mac_mls&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mac_mls].ko||Multi-Level Security confidentiality policy
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mac_none&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mac_none].ko||null MAC policy module
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mac_ntpd&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mac_ntpd].ko||policy allowing ntpd to run as non-root user
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mac_partition&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mac_partition].ko||The  ac_partition policy module implements a process partition policy,    which allows administrators to place running processes into "partitions",    based on their numeric process partition (specified in the process's MAC  label).
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mac_portacl&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mac_portacl].ko||network port access control policy
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mac_seeotheruids&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mac_seeotheruids].ko||The mac_seeotheruids policy module, when enabled, denies users to see  processes or sockets owned by other users.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mac_stub&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mac_stub].ko||The mac_stub policy module implements a stub MAC policy that has no effect on access control in the system.  Unlike mac_none(4), each MAC entry  point is defined as a "no-op", so the policy module will be entered for  each event, but no change in system behavior should result.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mac_test&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mac_test].ko||MAC framework testing policy
 +
|-
 +
|/boot/kernel/mach64.ko||..
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mdio&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mdio].ko||IEEE 802.3 Management Data Input/Output interface
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mem&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mem].ko||use modules from "mem"ory & allow consistent syntax for  inits
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mfi&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mfi].ko||This driver is for LSI's next generation PCI Express SAS RAID controllers.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mfi_linux&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mfi_linux].ko||This driver is for LSI's next generation PCI Express SAS RAID controllers. Access to RAID arrays (logical disks) from this driver is provided via /dev/mfid? device nodes. A simple management interface is also    provided on a per-controller basis via the /dev/mfi? device node.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mfip&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mfip].ko||LSI MegaRAID SAS driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mga&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mga].ko||  is an Xorg driver for Matrox video cards. 
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=miibus&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html miibus].ko||The miibus driver provides an interconnection between the Media Access Control (MAC) sublayer, the Physical Layer entities (PHY), Station Management (STA) entities, and the PHY Layer as defined by the IEEE 802.3 Standard.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mlx&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mlx].ko||Mylex DAC-family RAID driver
 +
|-
 +
|/boot/kernel/mlx4.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mlx4en&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mlx4en].ko||Mellanox ConnectX-3 10GbE/40GbE network adapter driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mlx4ib&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mlx4ib].ko||Mellanox ConnectX-3 10GbE/40GbE network adapter driver
 +
 +
|-
 +
|/boot/kernel/mlx5.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mlx5en&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mlx5en].ko||Mellanox ConnectX-4, ConnectX-4 LX and ConnectX-5 based 100Gb, 50Gb, 40Gb, 25Gb and 10Gb Ethernet adapter driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mlx5ib&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mlx5ib].ko||Mellanox ConnectX-4 and ConnectX-4 LX based 100Gb, 50Gb, 40Gb, 25Gb and 10Gb network adapter driver
 +
|-
 +
|/boot/kernel/mlxfw.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mly&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mly].ko||Mylex AcceleRAID/eXtremeRAID family driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mmc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mmc].ko||MultiMediaCard and SD Card bus driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mmcsd&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mmcsd].ko||MMC and SD memory card driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mpr&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mpr].ko||LSI Fusion-MPT 3/3.5 IT/IR 12Gb/s Serial Attached SCSI/SATA/PCIe driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mps&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mps].ko||LSI Fusion-MPT 2 IT/IR 6Gb/s Serial Attached SCSI/SATA driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mpt&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mpt].ko||LSI Fusion-MPT SCSI/Fibre Channel driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mqueuefs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mqueuefs].ko||The mqueuefs module will permit the FreeBSD kernel to support POSIX message queue.  The module contains system calls to manipulate POSIX message  queues.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mrsas&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mrsas].ko||LSI MegaRAID 6Gb/s and 12Gb/s SAS+SATA RAID controller driver
 +
|-
 +
|/boot/kernel/mrsas_linux.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=msdosfs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html msdosfs].ko||The msdosfs driver will permit the FreeBSD kernel to read and write MS-DOS based file systems. The most common usage follows: <code>mount -t msdosfs /dev/ada0sN/mnt</code>
 +
|-
 +
|/boot/kernel/msdosfs_iconv.ko||
 +
|-
 +
|/boot/kernel/mthca.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mvs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mvs].ko||A command line Mediawiki client
 +
|-
 +
|/boot/kernel/mw88W8363fw.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mx25l&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mx25l].ko||The mx25l driver provides support for the family of non-volatile storage  devices known collectively as SpiFlash(tm).  SpiFlash chips typically  have part numbers beginning with EN25, IS25, MX25, S25, SST25, or W25.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mxge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mxge]_eth_z8e.ko||mxge -- Myricom Myri10GE 10 Gigabit Ethernet adapter driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mxge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mxge]_ethp_z8e.ko||mxge -- Myricom Myri10GE 10 Gigabit Ethernet adapter driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mxge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mxge]_rss_eth_z8e.ko||mxge -- Myricom Myri10GE 10 Gigabit Ethernet adapter driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=mxge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html mxge]_rss_ethp_z8e.ko||mxge -- Myricom Myri10GE 10 Gigabit Ethernet adapter driver
 +
|-
 +
|/boot/kernel/nctgpio.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ndis&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ndis].ko||The ndis driver is a wrapper designed to allow binary Windows(R) NDIS    miniport network drivers to be used with FreeBSD.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=netgraph&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html netgraph].ko||These functions facilitate user-mode program participation in the kernel netgraph(4) graph-based networking system, by utilizing the netgraph  socket node type (see ng_socket(4)).
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/doc/handbook/network-nfs.html nfscl].ko||Network File System (NFS)
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/doc/handbook/network-nfs.html nfscommon].ko||Network File System (NFS)
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=nfsd&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html nfsd].ko||The nfsd utility runs on a server machine to service NFS requests from  client machines.  At least one nfsd must be running for a machine to operate as a server.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/doc/handbook/network-nfs.html nfslock].ko||Network File System (NFS)
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/doc/handbook/network-nfs.html nfslockd].ko||Network File System (NFS)
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=nfsmb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html nfsmb].ko||The nfsmb driver provides access to NVIDIA nForce2/3/4 SMBus 2.0 controllers.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=nfssvc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html nfssvc].ko||The nfssvc() system call is used by the NFS daemons to pass information into and out of the kernel and also to enter the kernel as a server daemon.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_async&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_async].ko||The async node type performs conversion between synchronous frames and  asynchronous frames, as defined for the PPP protocol in RFC 1662.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_atmllc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_atmllc].ko||The atmllc node type translates frames in to and out of ATM LLC encapsulation, as specified by RFC 1483.
 +
|-
 +
|/boot/kernel/ng_bluetooth.ko||The ng_bluetooth module is a placeholder for global Bluetooth variables. All Bluetooth variables can be examined and changed via [[sysctl]].
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_bpf&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_bpf].ko||The bpf node type allows Berkeley Packet Filter (see bpf(4)) filters to be applied to data travelling through a Netgraph network. Each node allows an arbitrary number of connections to arbitrarily named hooks.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_bridge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_bridge].ko||The bridge node type performs Ethernet bridging over one or more links.    Each link (represented by a connected hook) is used to transmit and receive raw Ethernet frames.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_bt3c&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_bt3c].ko||Netgraph node type that is also a 3Com Bluetooth PC card
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_btsocket&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_btsocket].ko||Bluetooth sockets layer
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_car&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_car].ko||Committed Access Rate netgraph node type
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_ccatm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_ccatm].ko||The ng_ccatm node implements the API specified by the ATM Forum for access to ATM services (see ATM-Forum document af-saa-0108).
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_cisco&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_cisco].ko||The cisco node type performs encapsulation and de-encapsulation of packets using the Cisco HDLC protocol. This is a fairly simple protocol for  the transmission of packets across high speed synchronous lines.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_deflate&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_deflate].ko||The deflate node type implements the Deflate sub-protocols of the Compression Control Protocol (CCP).
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_device&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_device].ko||A device node is both a netgraph node and a system device interface.    When a device node is created, a new device entry appears which is accessible via the regular file operators such as open(2), close(2), read(2),  write(2), etc.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_echo&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_echo].ko||The echo node type reflects all data and control messages back to the    sender.  This node type is used for testing and debugging.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_eiface&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_eiface].ko||The eiface netgraph node implements the generic Ethernet interface.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_etf&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_etf].ko||The etf node type multiplexes and filters data between hooks on the basis  of the ethertype found in an Ethernet header, presumed to be in the first  14 bytes of the data.  Incoming Ethernet frames are accepted on the    downstream hook and if the ethertype matches a value which the node has  been configured to filter, the packet is forwarded out the hook which was    identified at the time that value was configured.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_ether&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_ether].ko||The ether netgraph node type allows Ethernet interfaces to interact with    the netgraph(4) networking subsystem.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_ether_echo&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_ether_echo].ko||The ether_echo node type reflects all data and control messages back to  the sender.  It assumes (and does not check) that the packet is an ethernet frame, and swaps the source and destination addresses before echoing  it.  This node type is used for testing and debugging.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_frame_relay&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_frame_relay].ko||The frame_relay node type performs encapsulation, de-encapsulation, and    multiplexing of packets using the frame relay protocol.  It supports up  to 1024 DLCI's.  The LMI protocol is handled by a separate node type (see  ng_lmi(4)).
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_gif&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_gif].ko||The ng_gif netgraph node type allows gif(4) interfaces to interact with the netgraph(4) networking subsystem.  Once the ng_gif module is loaded  in the kernel, a node is automatically created for each gif(4) interface  in the system.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_gif_demux&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_gif_demux].ko||The ng_gif_demux netgraph node type demultiplexes the output from ng_gif(4) nodes in the netgraph(4) networking subsystem.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_hci&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_hci].ko||The hci node type is a Netgraph node type that implements Bluetooth Host  Controller Interface (HCI) layer as per chapter H1 of the Bluetooth Specification Book v1.1.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_hole&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_hole].ko||The hole node type silently discards all data and control messages it receives.  This type is used for testing and debugging.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_hub&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_hub].ko||The hub node type provides a simple mechanism for distributing packets over several links.  Packets received on any of the hooks are forwarded  out the other hooks.  Packets are not altered in any way.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_iface&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_iface].ko||An iface node is both a netgraph node and a system networking interface. When an iface node is created, a new interface appears which is accessi ble via ifconfig(8).  Iface node interfaces are named ng0, ng1, etc.    When a node is shutdown, the corresponding interface is removed and the    interface name becomes available for reuse by future iface nodes; new    nodes always take the first unused interface.  The node itself is assigned the same name as its interface, unless the name already exists, in  which case the node remains unnamed.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_ip_input&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_ip_input].ko||The ip_input node type takes all received packets and queues them into the IP in input processing subsystem.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_ipfw&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_ipfw].ko||The ipfw node implements interface between ipfw(4) and netgraph(4) subsystems.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_ksocket&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_ksocket].ko|| A ksocket node is both a netgraph node and a BSD socket.  The ng_ksocket    node type allows one to open a socket inside the kernel and have it appear as a Netgraph node.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_l2cap&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_l2cap].ko||ng_l2cap -- Netgraph node type that implements Bluetooth Logical Link    Control and Adaptation Protocol (L2CAP)
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_l2tp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_l2tp].ko||The l2tp node type implements the encapsulation layer of the L2TP protocol as described in RFC 2661.  This includes adding the L2TP packet  header for outgoing packets and verifying and removing it for incoming packets.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_lmi&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_lmi].ko||The lmi node type performs the frame relay LMI protocol.  It supports the      ITU Annex A, ANSI Annex D, and Group-of-four LMI types.  It also supports    auto-detection of the LMI type.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_mppc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_mppc].ko||The mppc node type implements the Microsoft Point-to-Point Compression    (MPPC) and Microsoft Point-to-Point Encryption (MPPE) sub-protocols of  the PPP protocol. These protocols are often used in conjunction with the  Point-to-Point Tunneling Protocol (PPTP).
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_nat&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_nat].ko||An ng_nat node performs network address translation (NAT) of packets    passing through it.  A nat node uses libalias(3) engine for packet aliasing.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_netflow&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_netflow].ko||The ng_netflow node implements Cisco's NetFlow export protocol on a router running FreeBSD.  The ng_netflow node listens for incoming traffic  and identifies unique flows in it.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_one2many&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_one2many].ko||The one2many provides a simple mechanism for routing packets over several    links in a one-to-many (and in the reverse direction, many-to-one) fashion.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_patch&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_patch].ko||The patch node performs data modification of packets passing through it.    Modifications are restricted to a subset of C language operations on unsigned integers of 8, 16, 32 or 64 bit size.
 +
|-
 +
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/netgraph/html/d2/d0e/ng__pipe_8c_source.html ng_pipe].ko||kernel netgraph code; This node permits simple traffic shaping by emulating bandwidth
 +
and delay, as well as random packet losses.  The node has two hooks, upper and lower. Traffic flowing from upper to lower hook is referenced as downstream, and vice versa. Parameters for  both directions can be set separately, except for delay.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_ppp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_ppp].ko||The ppp node type performs multiplexing for the PPP protocol.  It handles    only packets that contain data, and forwards protocol negotiation and  control packets to a separate controlling entity (e.g., a user-land daemon).
 +
|-
 +
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/netgraph/html/d2/d0e/ng__pipe_8c_source.html ng_pppoe].ko||kernel netgraph code; States for the session state machine. These have no meaning if there is no hook attached yet.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_pptpgre&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_pptpgre].ko||The pptpgre node type performs Generic Routing Encapsulation (GRE) over    IP for the PPTP protocol as specified by RFC 2637.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_pred1&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_pred1].ko||The pred1 node type implements the Predictor-1 sub-protocols of the Compression Control Protocol (CCP).
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_rfc1490&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_rfc1490].ko||The rfc1490 node type performs protocol encapsulation, deencapsulation,  and multiplexing according to RFC 1490 (which has since been updated by      RFC 2427). This particular type of encapsulation is often used on top of  frame relay DLCI channels.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_socket&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_socket].ko||A socket node is both a BSD socket and a netgraph node.  The ng_socket  node type allows user-mode processes to participate in the kernel  netgraph(4) networking subsystem using the BSD socket interface.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_source&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_source].ko||The source node acts as a source of packets according to the parameters  set up using control messages and input packets.  The ng_source node type    is used primarily for testing and benchmarking.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_split&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_split].ko||The split node type is used to split a bidirectional stream of packets into two separate unidirectional streams of packets.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_sppp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_sppp].ko||An sppp node is a netgraph(4) interface to the original sppp(4) network  module for synchronous lines.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_sscfu&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_sscfu].ko||The sscfu netgraph node type implements ITU-T recommendation Q.2130.  This recommendation specifies the Service Specific Coordination Function  at the UNI.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_sscop&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_sscop].ko|| The sscop netgraph node type implements the ITU-T standard Q.2110. This    standard describes the so called Service Specific Connection Oriented  Protocol (SSCOP) that is used to carry signalling messages over the private and public UNIs and the public NNI. 
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_tag&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_tag].ko||The tag node type allows mbuf packet tags (see mbuf_tags(9)) to be examined, stripped or applied to data travelling through a Netgraph network.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_tcpmss&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_tcpmss].ko||The tcpmss node type is designed to alter the Maximum Segment Size option  of TCP packets.  This node accepts an arbitrary number of hooks
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_tee&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_tee].ko||The tee node type has a purpose similar to the tee(1) command.  Tee nodes  are useful for debugging or "snooping" on a connection between two netgraph nodes.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_tty&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_tty].ko||The tty node type is both a netgraph node type and a TTY hook.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_ubt&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_ubt].ko||Netgraph node type that is also a driver for Bluetooth USB devices
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_UI&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_UI].ko||The UI node type has two hooks, upstream and downstream.  Packets received on downstream must have 0x03 (indicating unnumbered information)  as their first byte; if not the packet is dropped.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_uni&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_uni].ko||The uni netgraph node type implements ATM Forum signalling 4.0.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_vjc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_vjc].ko|| The vjc node type performs Van Jacobson compression, which is used over      PPP, SLIP, and other point-to-point IP connections to compress TCP packet    headers.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ng_vlan&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ng_vlan].ko|| The vlan node type multiplexes frames tagged according to the IEEE 802.1Q    standard between different hooks.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ngatmbase&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ngatmbase].ko||netgraph ATM utility module
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=nmdm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html nmdm].ko||The nmdm driver provides two tty(4) devices connected by a virtual "nullmodem" cable.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ntb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ntb].ko||Non-Transparent Bridge subsystem
 +
|-
 +
|/boot/kernel/ntb_hw_amd.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ntb_hw_intel&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ntb_hw_intel].ko||Intel(R) Non-Transparent Bridge driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ntb_hw_plx&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ntb_hw_plx].ko||PLX/Avago/Broadcom Non-Transparent Bridge driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ntb_transport&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ntb_transport].ko||Packet-oriented transport for Non-Transparent Bridges
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=nullfs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html nullfs].ko||The nullfs driver will permit the FreeBSD kernel to mount a loopback file  system sub-tree.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=nvd&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html nvd].ko||The nvd driver exposes NVM Express (NVMe) namespaces as disks to the kernel disk storage API. 
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=nvdimm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html nvdimm].ko||The nvdimm driver provides access to Non-Volatile DIMM (NVDIMM) persistent memory devices, which are ACPI-enumerated under the root NVDIMM device with a _HID of ACPI0012 and in the NFIT table.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=nvme&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html nvme].ko||NVM Express core driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=nvram&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html nvram].ko||The nvram driver provides access to BIOS configuration NVRAM on i386 and      amd64 systems.
 +
|-
 +
|/boot/kernel/nxprtc.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ocs_fc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ocs_fc].ko||Device driver for Emulex Fibre Channel Host Adapters
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ohci&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ohci].ko||The ohci driver provides support for OHCI-type PCI based USB controllers.
 +
 +
|-
 +
|/boot/kernel/opensolaris.ko||
 +
|-
 +
|/boot/kernel/otusfw_init.ko||
 +
|-
 +
|/boot/kernel/otusfw_main.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ow&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ow].ko||OWFS library access commands for Tcl
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ow_temp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ow_temp].ko||The ow_temp module supports many of the 1-Wire temperature sensors.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=owc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html owc].ko||Dallas Semiconductor 1-Wire Controller
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=padlock&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html padlock].ko||driver for the cryptographic functions and RNG in VIA C3, C7  and Eden processors
 +
 +
|-
 +
|/boot/kernel/padlock_rng.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=pccard&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html pccard].ko||The pccard driver implements the PC Card bus.  The pccard driver supports  all PC Card bridges in the system.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=pcf&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html pcf].ko||Philips I2C bus controller
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=pf&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html pf].ko||Packet filtering takes place in the kernel.  A pseudo-device, /dev/pf,  allows userland processes to control the behavior of the packet filter    through an ioctl(2) interface.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=pflog&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html pflog].ko||packet filter logging interface
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=pfsync&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html pfsync].ko||The pfsync interface is a pseudo-device which exposes certain changes to  the state table used by pf(4).
 +
|-
 +
|/boot/kernel/plasma_saver.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=plip&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html plip].ko||printer port Internet Protocol driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=pmspcv&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html pmspcv].ko||PMC-Sierra PM8001/8081/8088/8089/8074/8076/8077 SAS/SATA HBA Controller driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ppbus&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ppbus].ko||Parallel Port Bus system
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ppc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ppc].ko||architecture independent PowerPC platform emulator capable of running most PowerPC operating systems.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ppi&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ppi].ko||The ppi driver provides a convenient means for user applications to manipulate the state of the parallel port, enabling easy low-speed I/O operations without the security problems inherent with the use of the
 +
/dev/io interface.
 +
|-
 +
|/boot/kernel/pps.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=procfs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html procfs].ko||The process file system, or procfs, implements a view of the system process table inside the file system.  It is normally mounted on /proc.
 +
|-
 +
|/boot/kernel/profile.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=proto&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html proto].ko||Rdproto reads and interprets the named proto file relative to the root directory root.
 +
|-
 +
|/boot/kernel/prototype.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=pseudofs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html pseudofs].ko||The pseudofs module offers an abstract API for pseudo-file systems such  as procfs(5) and linprocfs(5).  It takes care of all the hairy bits like    interfacing with the VFS system, enforcing access control, keeping track    of file numbers, and cloning files and directories that are process-specific.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=pty&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html pty].ko|| Pty is a tool to help debug console programs which take the terminal out    of canonical mode, by allowing the program being debugged and the debugger to run on separate terminal devices.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=puc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html puc].ko||PCI "Universal" Communications driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=pwmbus&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html pwmbus].ko||The PWMBUS (Pulse-Width Modulation) interface allows a device driver to register to a global bus so other devices in the kernel can use them in a  generic way.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=pwmc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html pwmc].ko||PWM (Pulse Width Modulation) control device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=r128&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html r128].ko||ATI Rage 128 video driver
 +
|-
 +
|/boot/kernel/[https://wiki.freebsd.org/Graphics radeonkms].ko||AMD based GPUs are also supported using the drm-kmod port or package. There are two separate modules available for AMD devices based on their generation. The modules are named: amdgpu and radeonkms
 +
|-
 +
|/boot/kernel/radeonkmsfw_ARUBA_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_ARUBA_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_ARUBA_rlc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_BARTS_mc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_BARTS_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_BARTS_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_BTC_rlc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_CAICOS_mc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_CAICOS_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_CAICOS_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_CAYMAN_mc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_CAYMAN_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_CAYMAN_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_CAYMAN_rlc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_CEDAR_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_CEDAR_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_CEDAR_rlc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_CYPRESS_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_CYPRESS_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_CYPRESS_rlc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_JUNIPER_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_JUNIPER_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_JUNIPER_rlc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_PALM_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_PALM_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_PITCAIRN_ce.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_PITCAIRN_mc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_PITCAIRN_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_PITCAIRN_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_PITCAIRN_rlc.ko||AMD based GPU driver
 +
 +
|-
 +
|/boot/kernel/radeonkmsfw_R100_cp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_R200_cp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_R300_cp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_R420_cp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_R520_cp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_R600_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_R600_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_R600_rlc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_R700_rlc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_REDWOOD_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_REDWOOD_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_REDWOOD_rlc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RS600_cp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RS690_cp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RS780_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RS780_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV610_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV610_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV620_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV620_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV630_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV630_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV635_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV635_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV670_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV670_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV710_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV710_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV730_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV730_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV770_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_RV770_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_SUMO2_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_SUMO2_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_SUMO_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_SUMO_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_SUMO_rlc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_TAHITI_ce.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_TAHITI_mc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_TAHITI_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_TAHITI_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_TAHITI_rlc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_TURKS_mc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_TURKS_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_TURKS_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_VERDE_ce.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_VERDE_mc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_VERDE_me.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_VERDE_pfp.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/radeonkmsfw_VERDE_rlc.ko||AMD based GPU driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=splash&sektion=4&manpath=FreeBSD+9.1-RELEASE rain_saver].ko||Draws a shower on the screen.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=random&sektion=4 random_fortuna].ko||The random device returns an endless supply of random bytes when read.  It also accepts and reads data as any ordinary file.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=random&sektion=4 random_OTHER].ko||The random device returns an endless supply of random bytes when read.  It also accepts and reads data as any ordinary file.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=rc4&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html rc4].ko||This library implements the Alleged RC4 cipher, which is described for      example in Applied Cryptography. It is believed to be compatible with    RC4[TM], a proprietary cipher of RSA Security Inc.
 +
|-
 +
|/boot/kernel/[https://en.wikipedia.org/wiki/RDRAND rdrand_rng].ko||RDRAND is an instruction for returning random numbers from an Intel on-chip hardware.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=rsu&sektion=4 rsu-rtl8712fw].ko||Realtek RTL8188SU/RTL8192SU USB IEEE 802.11b/g/n wireless network    device
 +
|-
 +
|/boot/kernel/[https://github.com/crystax/android-vendor-freebsd/blob/master/sys/dev/ral/rt2661.c rt2561fw].ko||Ralink Technology RT2561, RT2561S and RT2661 chipset driver
 +
|-
 +
|/boot/kernel/[https://github.com/crystax/android-vendor-freebsd/blob/master/sys/dev/ral/rt2661.c rt2561sfw].ko||Ralink Technology RT2561, RT2561S and RT2661 chipset driver
 +
|-
 +
|/boot/kernel/[https://github.com/crystax/android-vendor-freebsd/blob/master/sys/dev/ral/rt2661.c rt2661fw].ko||Ralink Technology RT2561, RT2561S and RT2661 chipset driver
 +
|-
 +
|/boot/kernel/[https://github.com/crystax/android-vendor-freebsd/blob/master/sys/dev/ral/rt2661.c rt2860fw].ko||Ralink Technology RT2561, RT2561S and RT2661 chipset driver
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/iicbus/rtc8583.c rtc8583].ko||Driver for realtime clock EPSON RTC-8583
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=rtwn&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html rtwn].ko||Realtek IEEE 802.11 wireless network driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=rtwnfw&apropos=0&sektion=4&manpath=FreeBSD+11-current&format=html rtwn-rtl8188eefw].ko||Firmware Module for Realtek Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=rtwnfw&apropos=0&sektion=4&manpath=FreeBSD+11-current&format=html rtwn-rtl8188eufw].ko||Firmware Module for Realtek Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=rtwnfw&apropos=0&sektion=4&manpath=FreeBSD+11-current&format=html rtwn-rtl8192cfwE].ko||Firmware Module for Realtek Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=rtwnfw&apropos=0&sektion=4&manpath=FreeBSD+11-current&format=html rtwn-rtl8192cfwE_B].ko||Firmware Module for Realtek Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=rtwnfw&apropos=0&sektion=4&manpath=FreeBSD+11-current&format=html rtwn-rtl8192cfwT].ko||Firmware Module for Realtek Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=rtwnfw&apropos=0&sektion=4&manpath=FreeBSD+11-current&format=html rtwn-rtl8192cfwU].ko||Firmware Module for Realtek Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=rtwnfw&apropos=0&sektion=4&manpath=FreeBSD+11-current&format=html rtwn-rtl8192eufw].ko||Firmware Module for Realtek Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=rtwnfw&apropos=0&sektion=4&manpath=FreeBSD+11-current&format=html rtwn-rtl8812aufw].ko||Firmware Module for Realtek Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=rtwnfw&apropos=0&sektion=4&manpath=FreeBSD+11-current&format=html rtwn-rtl8821aufw].ko||Firmware Module for Realtek Wireless driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=runfw&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html runfw].ko||This module provides firmware sets for the Ralink RT2700U, RT2800U,    RT3000U and RT3900E chip based USB WiFi adapters. Please read Ralink's    license, src/sys/contrib/dev/run/LICENSE.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=s3&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html s3].ko||S3 video driver
 +
|-
 +
|/boot/kernel/[https://www.leidinger.net/freebsd/dox/dev_iicbus/html/d2/df2/s35390a_8c_source.html s35390a].ko||Driver for Seiko Instruments S-35390A Real-time Clock
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=safe&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html safe].ko||The safe driver supports cards containing SafeNet crypto accelerator  chips.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=savage&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html savage].ko||S3 Savage video driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=sbp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html sbp].ko||Serial Bus Protocol 2 (SBP-2) Mass Storage Devices driver, The sbp driver provides support for SBP-2 devices that attach to the  FireWire (IEEE 1394) port. It should work with SBP-2 devices which the  CAM layer supports, for example, HDDs, CDROM drives and DVD drives.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=sbp_targ&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html sbp_targ].ko||The sbp_targ driver provides support for SBP-2 target mode.  This driver    is supposed to work with cam(4), targ(4) and firewire(4). You also need  to use scsi_target(8), which can be found in      /usr/share/examples/scsi_target, to provide actual devices.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=scc&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html scc].ko||driver for Serial Communications Controllers (SCC) devices
 +
|-
 +
|/boot/kernel/[https://www.leidinger.net/FreeBSD/dox/cam/html/d7/d36/scsi__low_8h.html scsi_low].ko||[https://www.freebsd.org/cgi/man.cgi?query=scsi&apropos=0&sektion=4&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html Common Access Method Storage subsystem]
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=sdhci&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html sdhci].ko||PCI SD Host Controller bridge driver
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/sdhci/sdhci_acpi.c sdhci_acpi].ko||
 +
|-
 +
|/boot/kernel/sdhci_pci.ko||
 +
|-
 +
|/boot/kernel/sdt.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=sem&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html sem].ko||semaphore for executing shell command lines in parallel
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=send&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html send].ko||Send  will cause each of the specified files to be delivered to each of    the destinations in the "To:", "cc:", "Bcc:", "Dcc:", and "Fcc:" fields      of  the message.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=sfxge&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html sfxge].ko||Solarflare 10Gb Ethernet adapter driver
 +
|-
 +
|/boot/kernel/sgx.ko||
 +
|-
 +
|/boot/kernel/sgx_linux.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=siba&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html siba].ko||Sonic Inc. Silicon Backplane driver,  The siba driver provides bhnd(4) support for devices based on the Sonic    Inc. Silicon Backplane, an interblock communications architecture found    in earlier Broadcom Home Networking Division wireless chipsets and embed    ded systems.
 +
|-
 +
|/boot/kernel/siba_bhndb.ko||Sonic Inc. Silicon Backplane driver,  The siba driver provides bhnd(4) support for devices based on the Sonic    Inc. Silicon Backplane, an interblock communications architecture found    in earlier Broadcom Home Networking Division wireless chipsets and embed    ded systems.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=siftr&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html siftr].ko||Statistical Information For TCP Research
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=siis&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html siis].ko||SiliconImage Serial ATA Host Controller driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=sis&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html sis].ko||SiS 900, SiS 7016 and NS DP83815/DP83816 Fast Ethernet device  driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=smartpqi&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html smartpqi].ko||The smartpqi SCSI driver provides support for the new generation of PQI  controllers from Microsemi.  The smartpqi driver is the first SCSI driver    to implement the PQI queuing model.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=smb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html smb].ko|| The smb character device driver provides generic I/O to any smbus(4) instance.  To control SMB devices, use /dev/smb? with the ioctls described    below.  Any of these ioctl commands takes a pointer to struct smbcmd as    its argument.
 +
|-
 +
|/boot/kernel/smbfs.ko||
 +
|-
 +
|/boot/kernel/smbios.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=smbus&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html smbus].ko||System Management Bus
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=splash&sektion=4&manpath=FreeBSD+9.1-RELEASE snake_saver].ko||Draws a snake of string.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_ad1816&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_ad1816].ko||The snd_ad1816 bridge driver allows the generic audio driver sound(4) to    attach to the AD1816 sound card.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_als4000&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_als4000].ko||The snd_als4000 bridge driver allows the generic audio driver sound(4) to  attach to the ALS4000 sound card.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_atiixp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_atiixp].ko||The snd_atiixp bridge driver allows the generic audio driver, sound(4), to attach to ATI IXP audio devices.  This driver supports 16bit playback    and recording, and 32bit native playback and recording.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_cmi&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_cmi].ko||The snd_cmi bridge driver allows the generic audio driver sound(4) to attach to the CMedia CMI8338/CMI8738 audio cards.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_cs4281&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_cs4281].ko||The snd_cs4281 bridge driver allows the generic audio driver sound(4) to    attach to the CS4281 sound card.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_csa&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_csa].ko||The snd_csa bridge driver allows the generic audio driver sound(4) to attach to Crystal Semiconductor CS461x/462x/4280 based sound cards.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/doc/handbook/sound-setup.html snd_driver].ko||This is a metadriver which loads all of the most common sound drivers and can be used to speed up the search for the correct driver. It is also possible to load all sound drivers by adding the metadriver to /boot/loader.conf.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_ds1&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_ds1].ko||The snd_ds1 bridge driver allows the generic audio driver sound(4) to attach to the Yamaha DS-1 sound card.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_emu10k1&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_emu10k1].ko||The snd_emu10k1 bridge driver allows the generic audio driver sound(4) to attach to the SoundBlaster Live! and Audigy audio cards.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_emu10kx&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_emu10kx].ko||The snd_emu10kx bridge driver allows the generic audio driver sound(4) to  attach to Creative sound cards based on the EMU10K1, CA0100, CA0101,  CA0102 and CA0108 DSPs.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_envy24&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_envy24].ko||The snd_envy24 bridge driver allows the generic audio driver sound(4) to  attach to VIA Envy24 (ICE1724 or VT1724 chipset) and compatible audio devices.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_envy24ht&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_envy24ht].ko||The snd_envy24ht bridge driver allows the generic audio driver sound(4)  to attach to VIA Envy24HT (ICE1724 or VT1724 chipset) and compatible audio devices.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_es137x&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_es137x].ko||The snd_es137x bridge driver allows the generic audio driver sound(4) to attach to the Ensoniq 137x audio cards.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_ess&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_ess].ko||The snd_ess bridge driver allows the generic audio driver sound(4) to attach to the ESS ISA sound cards.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_fm801&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_fm801].ko||Forte Media FM801 bridge device driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_hda&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_hda].ko||The High Definition (HD) Audio specification was developed by Intel as the logical successor of the old AC'97 specification and has several advantages, such as higher bandwidth which allows more channels and more detailed formats, support for several logical audio devices, and general  purpose DMA channels.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_hdspe&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_hdspe].ko||The snd_hdspe bridge driver allows the generic audio driver sound(4) to attach to RME HDSPe audio devices.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_ich&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_ich].ko||Intel ICH AC'97 and compatible bridge device driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_maestro&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_maestro].ko||The snd_maestro bridge driver allows the generic audio driver sound(4) to  attach to ESS Maestro based sound chips.  This chipset is very popular in  notebook computers, but it is also very used in a wide selection of cheap  OEM sound cards.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_maestro3&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_maestro3].ko||The snd_maestro3 driver provides support for the ESS Maestro3 and Allegro-1 sound chips under the PCM framework. These chips are mostly found  in laptop computers and feature an AC97 mixer, a multi-channel sample  rate converter that can mix up to four digital audio streams in hardware,  recording support, and external volume control buttons.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_mss&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_mss].ko||Microsoft Sound System ISA PnP/non-PnP bridge device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_neomagic&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_neomagic].ko||The snd_neomagic bridge driver allows the generic audio driver, sound(4),  to attach to the NeoMagic 256AV/ZX audio devices. These chips are mostly  found in laptop computers.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_sb8&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_sb8].ko||snd_sbc, snd_sb16, snd_sb8 -- Creative Sound Blaster ISA and compatible  bridge device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_sb8&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_sb16].ko||snd_sbc, snd_sb16, snd_sb8 -- Creative Sound Blaster ISA and compatible  bridge device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_sb8&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_sbc].ko||snd_sbc, snd_sb16, snd_sb8 -- Creative Sound Blaster ISA and compatible  bridge device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_solo&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_solo].ko||The snd_solo bridge driver allows the generic audio driver sound(4) to  attach to the ESS Solo-1x PCI cards.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_spicds&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_spicds].ko||The snd_spicds I2S codec driver is used by several sound drivers for  soundcards which use the supported codec chips.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_t4dwave&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_t4dwave].ko||Trident 4DWave bridge device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_uaudio&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_uaudio].ko||USB audio and MIDI device driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_via82c686&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_via82c686].ko||The snd_via82c686 bridge driver allows the generic audio driver,  sound(4), to attach audio devices based on the VIA 82C686A chipset.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_via8233&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_via8233].ko||The snd_via8233 bridge driver allows the generic audio driver, sound(4),  to attach to the VIA VT8233 audio devices. These audio chipsets are integrated in the southbridge on many VIA based motherboards.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snd_vibes&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snd_vibes].ko||The snd_vibes bridge driver allows the generic audio driver, sound(4), to attach audio devices based on the S3 SonicVibes chipset.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=snp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html snp].ko||/dev/snp is a snoop device which allows users to attach to any tty and watch activities on it.  The kernel must be compiled with device snp, or  the snp module must be loaded, for these devices to be available.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=sound&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html sound].ko||The sound driver is the main component of the FreeBSD sound system.  It works in conjunction with a bridge device driver on supported devices and  provides PCM audio record and playback once it attaches.  Each bridge device driver supports a specific set of audio chipsets and needs to be enabled together with the sound driver.  PCI and ISA PnP audio devices  identify themselves so users are usually not required to add anything to  /boot/device.hints.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=speaker&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html speaker].ko||The speaker device driver allows applications to control the PC console  speaker on an IBM-PC--compatible machine running FreeBSD.
 +
|-
 +
|/boot/kernel/spibus.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=spigen&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html spigen].ko||The spigen driver provides direct access to a slave device on the SPI    bus.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=splash&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html splash]_bmp.ko||The splash pseudo device driver adds support for the splash screen and  screen savers to the kernel.  This driver is required if the splash bitmap image is to be loaded or any screen saver is to be used.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=splash&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html splash]_pcx.ko||The splash pseudo device driver adds support for the splash screen and    screen savers to the kernel.  This driver is required if the splash bitmap image is to be loaded or any screen saver is to be used.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=splash&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html splash]_txt.ko||The splash pseudo device driver adds support for the splash screen and  screen savers to the kernel.  This driver is required if the splash bitmap image is to be loaded or any screen saver is to be used.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=sppp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html sppp].ko||The sppp network layer implements the state machine and the Link Control  Protocol (LCP) of the point to point protocol (PPP) as described in RFC    1661.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=splash&sektion=4&manpath=FreeBSD+9.1-RELEASE star_saver].ko||Twinkling stars.
 +
|-
 +
|/boot/kernel/superio.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=sym&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html sym].ko||NCR/Symbios/LSI Logic 53C8XX PCI SCSI host adapter driver
 +
 +
|-
 +
|/boot/kernel/[https://en.wikipedia.org/wiki/Systrace systrace].ko||Systrace is a computer security utility which limits an application's access to the system by enforcing access policies for system calls. This can mitigate the effects of buffer overflows and other security vulnerabilities. It was developed by Niels Provos and runs on various Unix-like operating systems.
 +
|-
 +
|/boot/kernel/[https://en.wikipedia.org/wiki/Systrace systrace_freebsd32].ko||Systrace is a computer security utility which limits an application's access to the system by enforcing access policies for system calls. This can mitigate the effects of buffer overflows and other security vulnerabilities. It was developed by Niels Provos and runs on various Unix-like operating systems.
 +
|-
 +
|/boot/kernel/[https://en.wikipedia.org/wiki/Systrace systrace_linux].ko||Systrace is a computer security utility which limits an application's access to the system by enforcing access policies for system calls. This can mitigate the effects of buffer overflows and other security vulnerabilities. It was developed by Niels Provos and runs on various Unix-like operating systems.
 +
|-
 +
|/boot/kernel/[https://en.wikipedia.org/wiki/Systrace systrace_linux32].ko||Systrace is a computer security utility which limits an application's access to the system by enforcing access policies for system calls. This can mitigate the effects of buffer overflows and other security vulnerabilities. It was developed by Niels Provos and runs on various Unix-like operating systems.
 +
|-
 +
|/boot/kernel/[https://man.openbsd.org/options sysvmsg].ko||ncludes support for AT&T System V UNIX style message queues
 +
|-
 +
|/boot/kernel/[https://www.postgresql.org/docs/8.3/kernel-resources.html sysvsem].ko||The options SYSVSHM and SYSVSEM need to be enabled when the kernel is compiled. (They are by default.) The maximum size of shared memory is determined by the option SHMMAXPGS (in pages).
 +
|-
 +
|/boot/kernel/[https://www.postgresql.org/docs/8.3/kernel-resources.html sysvshm].ko||The options SYSVSHM and SYSVSEM need to be enabled when the kernel is compiled. (They are by default.) The maximum size of shared memory is determined by the option SHMMAXPGS (in pages).
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/cxgbe/tom/t4_tom.c t4_tom].ko||[https://github.com/freebsd/freebsd/tree/master/sys/dev/cxgbe/firmware]
 +
|-
 +
|/boot/kernel/t4fw_cfg.ko||[https://github.com/freebsd/freebsd/tree/master/sys/dev/cxgbe/firmware]
 +
|-
 +
|/boot/kernel/t5fw_cfg.ko||[https://github.com/freebsd/freebsd/tree/master/sys/dev/cxgbe/firmware]
 +
|-
 +
|/boot/kernel/t6fw_cfg.ko||[https://github.com/freebsd/freebsd/tree/master/sys/dev/cxgbe/firmware]
 +
|-
 +
|/boot/kernel/tcpmd5.ko||[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218907], [https://github.com/BIRD/bird/pull/2/files]
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=tdfx&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html tdfx].ko||Voodoo Graphics and VoodooII Memory Access GLIDE device driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=tmpfs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html tmpfs].ko||The tmpfs driver implements an in-memory, or tmpfs file system.  The    filesystem stores both file metadata and data in main memory.
 +
|-
 +
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/netinet/toecore.h toecore].ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=tpm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html tpm].ko||The tpm driver provides support for various trusted platform modules  (TPM) that can store cryptographic keys.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=trm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html trm].ko||Tekram TRM-S1040 ASIC based PCI SCSI host adapter driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=twa&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html twa].ko||The twa driver provides support for AMCC's 3ware 9000/9500/9550/9650 series SATA controllers.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=twe&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html twe].ko|| The twe driver provides support for AMCC's 3ware 5000/6000/7000/8000 series PATA/SATA RAID adapters.  These adapters were formerly known as  "3ware Escalade".  These devices support 2, 4, 8, or 12 ATA disk drives and provide RAID0    (striping) and RAID1 (mirroring) functionality.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=tws&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html tws].ko|| The tws driver provides support for LSI's 3ware 9750 SATA+SAS 6Gb/s RAID    controller cards.  These controllers feature the LSISAS2108 6Gb/s SAS RAID-on-Chip (ROC) and    are available in 4- and 8-port configurations, supports RAID levels 0, 1,    5, 6, 10, 50 and single disk, with 96 SATA and/or SAS hard drives and    SSDs.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=u3g&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html u3g].ko||The u3g driver provides support for the multiple USB-to-serial interfaces    exposed by many 3G USB/PCCard modems.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=uart&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html uart].ko||driver for Universal Asynchronous Receiver/Transmitter (UART) devices
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ubsa&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ubsa].ko|| The ubsa driver provides support for the USB-to-RS232 Bridge chip used by  a variety of serial adapters from Belkin and other vendors.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ubsec&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ubsec].ko||Broadcom and BlueSteel uBsec 5x0x crypto accelerator
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ubser&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ubser].ko||USB support for BWCT console serial adapters
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ubtbcmfw&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ubtbcmfw].ko||Firmware driver for Broadcom BCM2033 chip based Bluetooth USB devices
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=uchcom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html uchcom].ko|WinChipHead CH341/CH340 serial adapter driver|
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ucom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ucom].ko||USB tty support
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ucycom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ucycom].ko||device driver for Cypress CY7C63743 and CY7C64013 USB to RS232  bridges
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=udbp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html udbp].ko||USB Double Bulk Pipe driver
 +
|-
 +
|/boot/kernel/udf.ko||Universal Disk Format
 +
|-
 +
|/boot/kernel/udf_iconv.ko||Universal Disk Format
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=udl&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html udl].ko||DisplayLink DL-120 / DL-160 USB display devices
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=uep&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html uep].ko||eGalax touchscreen driver
 +
|-
 +
|/boot/kernel/uether.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ufm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ufm].ko||USB driver for Cypress Semiconductor FM Radio
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ufoma&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ufoma].ko||The ufoma driver provides support for USB mobile phone terminals in the subset of the Mobile Computing Promotion Consortium USB Implementation  Guideline, which is adopted by FOMA, the NTT DoCoMo 3G system, terminal.
 +
|-
 +
|/boot/kernel/ufs.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=uftdi&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html uftdi].ko||USB support for serial adapters based on the FTDI family of USB    serial adapter chips.
 +
|-
 +
|/boot/kernel/ugensa.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ugold&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ugold].ko||TEMPer gold HID thermometer
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=uhci&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html uhci].ko||UHCI USB Host Controller driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=uhid&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html uhid].ko||USB generic HID support
 +
|-
 +
|/boot/kernel/uhid_snes.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=uhso&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html uhso].ko||support for several HSxPA devices from Option N.V.
 +
|-
 +
|/boot/kernel/uinput.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=uipaq&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html uipaq].ko||The uipaq driver provides support for the USB serial emulation provided  by the iPAQ devices.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ukbd&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ukbd].ko||USB keyboard driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=uled&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html uled].ko||USB LED driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ulpt&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ulpt].ko||USB printer support
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=umass&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html umass].ko||The umass driver provides support for Mass Storage devices that attach to  the USB port.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=umcs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html umcs].ko||USB support for serial adapters based on the MCS7820 and MCS7840 chips
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=umct&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html umct].ko||The umct driver provides support for USB to RS-232 converters based on    the Magic Control Technology USB-232 design.  These devices support most    of the standard RS-232 features including baud rates ranging from 300 to    115200 bits per second.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=umodem&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html umodem].ko||USB Communication Device Class serial (CDC ACM) driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=umoscom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html umoscom].ko||USB support for serial adapters based on chips made by MOSCHIP
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=ums&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ums].ko||USB mouse driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=unionfs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html unionfs].ko|| A userspace unionfs implementation
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=uplcom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html uplcom].ko||USB support for Prolific PL-2303/2303X/2303HX serial adapters    driver
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=urio&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html urio].ko||USB driver for the Rio MP3 players
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=usb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html usb].ko||The libusb library contains interfaces for directly managing a usb device.  The current implementation supports v1.0 of the libusb API.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=usb_template&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html usb_template].ko||USB device side templates
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=usfs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html usfs].ko||USB device side support for bulk only transport mass storage
 +
 +
|-
 +
|/boot/kernel/usie.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=uslcom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html uslcom].ko||Silicon Laboratories CP2101/CP2102/CP2103/CP2104/CP2105 based  USB serial adapter
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=uvisor&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html uvisor].ko||USB support for the PalmOS based PDAs
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=uvscom&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html uvscom].ko||USB support for SUNTAC Slipper U VS-10U serial adapters driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=vesa&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html vesa].ko||vesa is an Xorg driver for generic VESA video cards.  It can drive most      VESA-compatible video cards, but only makes use of the  basic  standard      VESA core that is common to these cards. The driver supports depths 8,  15 16 and 24.
 +
|-
 +
|/boot/kernel/via.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=viapm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html viapm].ko||This driver provides access to the VIA chipset Power Management Unit family.  They are VT82C586B, VT82C596A, VT82C596B, VT82C686A and VT8233.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=viawd&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html viawd].ko||The viawd driver provides watchdog(4) support for the watchdog interrupt  timer present on VIA south bridge chipset (VT8251, CX700, VX800, VX855,  VX900).
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/doc/handbook/consoles.html videomode].ko||The FreeBSD console default video mode may be adjusted to 1024x768, 1280x1024, or any other size supported by the graphics chip and monitor.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=virtio&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html virtio].ko||VirtIO is a specification for para-virtualized I/O in a virtual machine  (VM).  Traditionally, the hypervisor emulated real devices such as an  Ethernet interface or disk controller to provide the VM with I/O. This  emulation is often inefficient.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=virtio_balloon&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html virtio_balloon].ko||The virtio_balloon device driver provides support for VirtIO memory balloon devices.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=virtio_blk&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html virtio_blk].ko||VirtIO Block driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=virtio_console&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html virtio_console].ko||VirtIO Console driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=virtio&sektion=4 virtio_pci].ko||VirtIO is a specification for para-virtualized I/O in a virtual machine    (VM).  Traditionally, the hypervisor emulated real devices such as an    Ethernet interface or disk controller to provide the VM with I/O. This  emulation is often inefficient.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=virtio_random&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html virtio_random].ko||The virtio_random device driver provides support for VirtIO entropy devices.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=virtio_scsi&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html virtio_scsi].ko||The virtio_scsi device driver provides support for VirtIO SCSI devices.
 +
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=vkbd&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html vkbd].ko||The vkbd interface is a software loopback mechanism that can be loosely    described as the virtual AT keyboard analog of the pty(4), that is, vkbd    does for virtual AT keyboards what the pty(4) driver does for terminals.
 +
 +
|-
 +
|/boot/kernel/[https://reviews.freebsd.org/D14289 vmci].ko||vmware kernel module, VMCI allows virtual machines to communicate with host kernel modules and ...
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=vmm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html vmm].ko||vmm.ko provides the kernel portion of the bhyve(4) hypervisor.  An Intel CPU with VT-x/EPT or AMD CPU with SVM support is required.  PCI device passthrough to a virtual machine requires hardware with VT-d    support.
 +
|-
 +
|/boot/kernel/vpd.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=vpo&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html vpo].ko||The vpo driver provide access to parallel port Iomega Zip and Jaz drives.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=splash&sektion=4&manpath=FreeBSD+9.1-RELEASE warp_saver].ko||Streaking stars.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wbwd&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wbwd].ko||device driver for Winbond/Nuvoton Super I/O chips watchdog timer
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wlan&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wlan].ko ||generic 802.11 link-layer support
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wlan_acl&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wlan_acl].ko ||MAC-based ACL support for 802.11 devices
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wlan_amrr&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wlan_amrr].ko ||AMRR rate adaptation algorithm support for 802.11 devices
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wlan_ccmp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wlan_ccmp].ko ||AES-CCMP crypto support for 802.11 devices
 +
|-
 +
|/boot/kernel/wlan_rssadapt.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wlan_tkip&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wlan_tkip].ko ||TKIP and Michael crypto support for 802.11 devices
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wlan_wep&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wlan_wep].ko  ||WEP crypto support for 802.11 devices
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wlan_xauth&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wlan_xauth].ko ||External authenticator support for 802.11 devices
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wmt&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wmt].ko ||MS Windows 7/8/10 - compatible USB HID multi-touch device driver
 +
|-
 +
|/boot/kernel/[http://wipfw.sourceforge.net/ wpifw].ko||IPFW is a packet filtering and accounting system which resides in the kernelmode, and has a user-land control utility, ipfw. Together, they allow you to define and query the rules used by the kernel in its routing decisions. WIPFW is a MS Windows operable version of IPFW for FreeBSD OS. You can use the same functionality and configure it as only you work with IPFW.
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=wsp&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wsp].ko ||Wellspring touchpad driver
 +
|-
 +
|/boot/kernel/x86bios.ko||
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=xhci&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html xhci].ko ||USB eXtensible Host Controller driver
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=xz&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html xz].ko ||Compress or decompress .xz and .lzma files
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=zfs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html zfs].ko ||configures ZFS file systems
 +
|-
 +
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=zlib&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html zlib].ko||compression/decompression library
 +
|}
  
  

Latest revision as of 08:47, 10 March 2020

Welcome to Icon Disti GhostBSD.png Kernel.
Kernel Competence
Sysctl Kldstat Third-party Kernel Modules
Kernel Modules FreeBSD Ports: Kld Kenv
Compiling a new GhostBSD kernel
Back to the Icon Disti GhostBSD.pngSystem

Introduction[edit]

Related to the Directory Structure we are in the directory /boot/kernel.
On this page we show more kernel modules, like driver for wlan, ethernet, bluetooth, sound, file systems... Most of it are not installed by default.
If you like to start a module at boot time, you have to go to /boot/loader.conf, open it with an editor of your choice. The syntax is in most cases (with few exceptions) the same:
Take the name of the kernel module, chop of the tailing .ko, also /boot/kernel/
and add the string _load="YES".
For example, to load the module /boot/kernel/acpi_ibm.ko
automatically add this to the /boot/loader.conf:
acpi_ibm_load="YES"
You will get additional information on the linked man pages.
More loadable kernel modules are listed in FreeBSD Ports: Kld
A lot of additional Information you will find here

Modules[edit]

Module Description
/boot/kernel/aac.ko Adaptec AdvancedRAID Controller driver
/boot/kernel/aacraid.ko Adaptec AACRAID Controller driver
/boot/kernel/accf_data.ko buffer incoming connections until data arrives
/boot/kernel/accf_dns.ko buffer incoming DNS requests until the whole first request is present
/boot/kernel/accf_http.ko buffer incoming connections until a certain complete HTTP requests arrive
/boot/kernel/acl_nfs4.ko introduction to the POSIX.1e/NFSv4 ACL security API
/boot/kernel/acl_posix1e.ko introduction to the POSIX.1e/NFSv4 ACL security API
/boot/kernel/acpi_asus.ko Asus Laptop Extras
/boot/kernel/acpi_asus_wmi.ko Asus Laptop WMI Extras
/boot/kernel/acpi_dock.ko Laptop Docking Station device driver
/boot/kernel/acpi_fujitsu.ko Fujitsu Laptop Extras
/boot/kernel/acpi_hp.ko ACPI extras driver for HP laptops
/boot/kernel/acpi_ibm.ko ACPI extras driver for IBM laptops
/boot/kernel/acpi_panasonic.ko ACPI hotkey driver for Panasonic laptops
/boot/kernel/acpi_sony.ko ACPI notebook controller driver for Sony laptops
/boot/kernel/acpi_toshiba.ko Toshiba HCI interface
/boot/kernel/acpi_video.ko ACPI Video Extensions driver
/boot/kernel/acpi_wmi.ko The acpi_wmi driver provides an interface for vendor specific WMI implementations (e.g. HP and Acer laptops).
/boot/kernel/ads111x.ko The ads111x driver provides support for the ADS101x/ADS111x family of analog to digital converter (ADC) devices.
/boot/kernel/aesni.ko Starting with Intel Westmere and AMD Bulldozer, some x86 processors implement a new set of instructions called AESNI.
/boot/kernel/agp.ko The agp driver provides uniform, abstract methods for controlling some devices of Ali, AMD, ATI, Intel, NVIDIA, SiS, VIA
/boot/kernel/aha.ko This driver provides access to the SCSI bus connected to the Adaptec AHA-154x SCSI host adapters.
/boot/kernel/ahc.ko This driver provides access to the SCSI bus(es) connected to the Adaptec AIC77xx and AIC78xx host adapter chips.
/boot/kernel/ahc_isa.ko This driver provides access to the SCSI bus(es) connected to the Adaptec AIC77xx and AIC78xx host adapter chips.
/boot/kernel/ahc_pci.ko This driver provides access to the SCSI bus(es) connected to the Adaptec AIC77xx and AIC78xx host adapter chips.
/boot/kernel/ahci.ko Serial ATA Advanced Host Controller Interface driver
/boot/kernel/ahd.ko This driver provides access to the SCSI bus(es) connected to Adaptec AIC79xx host adapter chips.
/boot/kernel/aibs.ko ASUSTeK AI Booster ACPI ATK0110 voltage, temperature and fan sensor
/boot/kernel/alias_cuseeme.ko FreeBSD kernel IPv4 code
/boot/kernel/alias_dummy.ko FreeBSD kernel IPv4 code
/boot/kernel/alias_ftp.ko Alias_ftp.c performs special processing for FTP sessions under TCP.
/boot/kernel/alias_irc.ko Alias_irc.c intercepts packages contain IRC CTCP commands, and changes DCC commands to export a port on the aliasing host instead of an aliased host.
/boot/kernel/alias_nbt.ko alias_nbt.c performs special processing for NetBios over TCP/IP sessions by UDP.
/boot/kernel/alias_pptp.ko PPTP_CONTROL_PORT_NUMBER 1723
/boot/kernel/alias_skinny.ko alias_skinny.c handles the translation for the Cisco Skinny Station protocol. Skinny typically uses TCP port 2000 to set up calls between a Cisco Call Manager and a Cisco IP phone. When a phone comes on line,
/boot/kernel/alias_smedia.ko Alias_smedia.c is meant to contain the aliasing code for streaming media protocols. It performs special processing for RSTP sessions under TCP. Specifically, when a SETUP request is sent by a client, or a 200 reply is sent by a server, it is intercepted and modified. The address is changed to the gateway machine and an aliasing port is used.
/boot/kernel/alpm.ko Acer Aladdin 15x3 Power Management controller driver
/boot/kernel/alq.ko The alq facility provides an asynchronous fixed or variable length recording mechanism, known as Asynchronous Logging Queues.
/boot/kernel/amd_ecc_inject.ko See BKDG for AMD Family 15h Models 00h-0Fh Processors (publication 42301 Rev 3.08 - March 12, 2012):
/boot/kernel/amdgpio.ko This is the driver for ACPI attached GPIO controller in AMD Platforms. This driver is basically a port of "drivers/pinctrl/pinctrl-amd.c" driver in Linux. This patch has the basic functions of GPIO, leaving interrupt related support.
/boot/kernel/amdpm.ko This driver provides access to AMD 756/766/768/8111 Power management controllers. Currently, only the SMBus 1.0 controller function is implemented. The SMBus 2.0 functionality of the AMD 8111 controller is supported via the amdsmb(4) driver.
/boot/kernel/amdsbwd.ko The amdsbwd driver provides watchdog(4) support for the watchdog timers present on the supported chipsets.
/boot/kernel/amdsmb.ko The amdsmb driver provides access to the AMD-8111 SMBus 2.0 controller.
/boot/kernel/amdsmn.ko The amdsmn driver provides support for resources on the System Management Network bus in AMD Family 17h processors.
/boot/kernel/amdtemp.ko device driver for AMD processor on-die digital thermal sensor
/boot/kernel/amr.ko MegaRAID SCSI/ATA/SATA RAID driver
/boot/kernel/amr_cam.ko MegaRAID SCSI/ATA/SATA RAID driver
/boot/kernel/amr_linux.ko MegaRAID SCSI/ATA/SATA RAID driver
/boot/kernel/aout.ko kernel support for executing binary files in legacy a.out format
/boot/kernel/arcmsr.ko Areca RAID Controller driver
/boot/kernel/asmc.ko device driver for the Apple System Management Controller (SMC)
/boot/kernel/at45d.ko The at45d driver provides support for the family of non-volatile storage devices known collectively as DataFlash(tm). DataFlash chips typically have part numbers beginning with AT45DB.
/boot/kernel/ata.ko generic ATA/SATA controller driver
/boot/kernel/ataacard.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/ataacerlabs.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/ataamd.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/ataati.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/atacard.ko ATA PC Card Driver
/boot/kernel/atacenatek.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/atacypress.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/atacyrix.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/atahighpoint.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/ataintel.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/ataisa.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/ataite.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/atajmicron.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/atamarvell.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/atamicron.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/atanational.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/atanetcell.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/atanvidia.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/atapci.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/atapromise.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/ataserverworks.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/atasiliconimage.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/atasis.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/atavia.ko The 'ATA' driver supports all legacy ATA/ATAPI controllers, including PC Card devices. You only need one "device ata" for it to find all PCI and PC Card ATA/ATAPI devices on modern machines. Alternatively, individual bus and chipset drivers may be chosen by using the 'atacore' driver then selecting the drivers on a per vendor basis. For example to build a system which only supports a VIA chipset, omit 'ata' and include the 'atacore', 'atapci' and 'atavia' drivers.
/boot/kernel/ath_dfs.ko ath Atheros IEEE 802.11 wireless network driver
/boot/kernel/ath_hal.ko Atheros Hardware Access Layer (HAL)
/boot/kernel/ath_hal_ar5210.ko The file was added as part of updating to 12.0
/boot/kernel/ath_hal_ar5211.ko The file was added as part of updating to 12.0
/boot/kernel/ath_hal_ar5212.ko The file was added as part of updating to 12.0
/boot/kernel/ath_hal_ar5416.ko The file was added as part of updating to 12.0
/boot/kernel/ath_hal_ar9300.ko The file was added as part of updating to 12.0
/boot/kernel/ath_main.ko The file was added as part of updating to 12.0
/boot/kernel/ath_rate.ko The file was added as part of updating to 12.0
/boot/kernel/atp.ko ATP is used for reading and replying to messages contained in QWK mail packets which are available through public access bulletin boards.
/boot/kernel/autofs.ko The autofs driver is the kernel component of the automounter infrastructure. Its job is to pass mount requests to the automountd(8) daemon, and pause the processes trying to access the automounted filesystem until the mount is completed.
/boot/kernel/bcma.ko The bcma driver provides bhnd(4) support for devices using the ARM AMBA based backplane architecture found in later Broadcom Home Networking Division's network chipsets and embedded systems.
/boot/kernel/bcma_bhndb.ko Broadcom AMBA Backplane driver [1]
/boot/kernel/beastie_saver.ko splash screen / screen saver interface
/boot/kernel/bhnd.ko Broadcom Home Networking Division interconnect bus
/boot/kernel/bhnd_pci.ko Broadcom Common PCI/PCIe Support. This base driver implementation is shared by the bhnd_pcib (root complex) and bhnd_pci_hostb (host bridge) drivers.
/boot/kernel/bhnd_pci_hostb.ko Broadcom BHND PCI/PCIe-Gen1 PCI-Host Bridge. This driver handles all interactions with PCI bridge cores operating in endpoint mode. Host-level PCI operations are handled at the bhndb bridge level by the bhndb_pci driver.
/boot/kernel/bhnd_pcib.ko Broadcom PCI/PCIe-Gen1 Host-PCI bridge. This driver handles all interactions with PCI bridge cores operating in root complex mode.
/boot/kernel/bhndb.ko Broadcom Home Networking Division interconnect bridge driver
/boot/kernel/bhndb_pci.ko PCI-specific implementation for the BHNDB bridge driver.

Provides support for bridging from a PCI parent bus to a BHND-compatible bus (e.g. bcma or siba) via a Broadcom PCI core configured in end-point mode. This driver handles all initial generic host-level PCI interactions with a PCI/PCIe bridge core operating in endpoint mode. Once the bridged bhnd(4) bus has been enumerated, this driver works in tandem with a core-specific bhnd_pci_hostb driver to manage the PCI core.

/boot/kernel/bktr.ko Brooktree Bt848/849/878/879 and Pinnacle PCTV video capture driver
/boot/kernel/bktr_mem.ko Motion monitors the video signal from one or more cameras and is able to detect motion.
/boot/kernel/blake2.ko The cryptographic hash function BLAKE2 is an improved version of the SHA-3

finalist BLAKE. Like SHA-3, BLAKE2 offers the highest security, yet is fast as MD5 on 64-bit platforms and requires at least 33% less RAM than SHA-2 or SHA-3 on low-end systems. The core algorithm of BLAKE2 is derived from ChaCha, a stream cipher designed by Daniel J. Bernstein that has been proposed as a standard cipher for TLS.

/boot/kernel/blank_saver.ko This screen saver simply blanks the screen.
/boot/kernel/bridgestp.ko The if_bridge driver creates a logical link between two or more IEEE 802 networks that use the same (or "similar enough") framing format. For example, it is possible to bridge Ethernet and 802.11 networks together, but it is not possible to bridge Ethernet and Token Ring together.
/boot/kernel/bytgpio.ko Intel Bay Trail SoC GPIO controller
/boot/kernel/callout_test.ko Regularize the Netflix copyright; Copyright (c) 2015 Netflix, Inc.
/boot/kernel/cam.ko CPU'S AUDIO MIXER for Linux
/boot/kernel/cardbus.ko The cardbus driver implements the CardBus bus. The cardbus driver supports all cardbus bridges in the system.
/boot/kernel/carp.ko The CARP allows multiple hosts on the same local network to share a set of IPv4 and/or IPv6 addresses. Its primary purpose is to ensure that these addresses are always available.
/boot/kernel/cbb.ko The pccbb driver implements the Yenta specification for CardBus bridges.
/boot/kernel/cc_cdg.ko CAIA-Delay Gradient (CDG) is a hybrid congestion control algorithm which reacts to both packet loss and inferred queuing delay.
/boot/kernel/cc_chd.ko CHD Congestion Control Algorithm
/boot/kernel/cc_cubic.ko The CUBIC congestion control algorithm was designed to provide increased throughput in fast and long-distance networks.
/boot/kernel/cc_dctcp.ko The DCTCP (data center TCP) congestion control algorithm aims to maximise throughput and minimise latency in data center networks by utilising the proportion of Explicit Congestion Notification (ECN) marks received from capable hardware as a congestion signal.
/boot/kernel/cc_hd.ko The HD congestion control algorithm is an implementation of the Hamilton Institute's delay-based congestion control which aims to keep network queuing delays below a particular threshold (queue_threshold).
/boot/kernel/cc_htcp.ko The H-TCP congestion control algorithm was designed to provide increased throughput in fast and longdistance networks. It attempts to maintain fairness when competing with legacy NewReno TCP in lower speed scenarios where NewReno is able to operate adequately.
/boot/kernel/cc_vegas.ko Vegas Congestion Control Algorithm
/boot/kernel/ccp.ko experimental driver for AMD Crypto Co-Processor
/boot/kernel/ccr.ko The ccr driver provides support for the crypto accelerator engine included on PCI Express Ethernet adapters based on the Chelsio Terminator 6 ASIC (T6). The driver accelerates AES-CBC, AES-CCM, AES-CTR, AES-GCM,

AES-XTS, SHA1, SHA2-224, SHA2-256, SHA2-384, SHA2-512, SHA1-HMAC, SHA2-224-HMAC, SHA2-256-HMAC, SHA2-384-HMAC, and SHA2-512-HMAC operations for crypto(4) and ipsec(4). The driver also supports chaining one of AES-CBC, AES-CTR, or AES-XTS with SHA1-HMAC, SHA2-224-HMAC, SHA2-256-HMAC, SHA2-384-HMAC, or SHA2-512-HMAC for encrypt-then-authenticate operations.

/boot/kernel/cd9660.ko The cd9660 driver will permit the FreeBSD kernel to access the cd9660 file system.
/boot/kernel/cd9660_iconv.ko Support for multibyte charsets in LIBICONV.
/boot/kernel/cfiscsi.ko The cfiscsi subsystem provides the kernel component of an iSCSI target. The target is the iSCSI server, providing LUNs backed by local files and volumes to remote initiators.
/boot/kernel/cfumass.ko The cfumass driver provides device side support for emulating an USB mass storage device compliant with the USB Mass Storage Class Bulk-Only (BBB) Transport specification, implemented as a ctl(4) frontend driver.
/boot/kernel/chromebook_platform.ko support driver for hardware on various Chromebook models
/boot/kernel/chvgpio.ko chvgpio supports the GPIO controller that can be found in Intel's Cherry View SoC family.
/boot/kernel/ciss.ko Common Interface for SCSI-3 Support driver
/boot/kernel/cloudabi.ko CloudABI support
/boot/kernel/cloudabi32.ko CloudABI support
/boot/kernel/cloudabi64.ko CloudABI support
/boot/kernel/cmx.ko The cmx driver provides support for the PCCARD based Omnikey CardMan 4040 smartcard reader. The driver provides a character device special file based Chip/Smart Card Interface Devices (CCID) interface. The driver implements what the vendor calls the Synchronous API onto the smartcard reader device.
/boot/kernel/coretemp.ko device driver for Intel Core on-die digital thermal sensor
/boot/kernel/cpuctl.ko The special device /dev/cpuctl presents interface to the system CPU. It provides functionality to retrieve CPUID information, read/write machine specific registers (MSR) and perform CPU firmware updates.
/boot/kernel/cpufreq.ko CPU frequency control framework
/boot/kernel/crypto.ko The OpenSSL crypto library implements a wide range of cryptographic algorithms used in various Internet standards. The services provided by this library are used by the OpenSSL implementations of SSL, TLS and S/MIME, and they have also been used to implement SSH, OpenPGP, and other cryptographic standards.
/boot/kernel/cryptodev.ko user-mode access to hardware-accelerated cryptography
/boot/kernel/ctl.ko CAM Target Layer
/boot/kernel/cuse.ko Userland character device library
/boot/kernel/cxgb_t3fw.ko cxgb -- Chelsio T3 10 Gigabit Ethernet adapter driver
/boot/kernel/cxgbei.ko CXGBEI_CONN_SIGNATURE 0x56788765
/boot/kernel/cyapa.ko Cypress APA trackpad with I2C interface driver
/boot/kernel/daemon_saver.ko Animated BSD Daemon screen saver.
/boot/kernel/dcons.ko dumb console device driver
/boot/kernel/dcons_crom.ko Configuration ROM stub for dcons(4)
/boot/kernel/dpms.ko VESA BIOS DPMS driver
/boot/kernel/dragon_saver.ko Draws a random dragon curve.
/boot/kernel/drm.ko The Direct Rendering Manager (DRM) is a framework to manage Graphics Processing Units (GPUs). It is designed to support the needs of complex graphics devices, usually containing programmable pipelines well suited to 3D graphics acceleration. Furthermore, it is responsible for memory management, interrupt handling and DMA to provide a uniform interface to applications.
/boot/kernel/drm2.ko Graphics driver; direct rendering manager (DRM) drivers; some interesting additional thoughts
/boot/kernel/ds13rtc.ko IICBUS device code
/boot/kernel/ds1307.ko The ds1307 serial real-time clock (RTC) is a low-power, full binary-coded decimal (BCD) clock/calendar plus 56 bytes of NV SRAM.
/boot/kernel/ds1672.ko Dallas Semiconductor DS1672 RTC sitting on the I2C bus.
/boot/kernel/ds3231.ko The ds3231 is a lowcost, extremely accurate I2C realtime clock (RTC) with an integrated temperature-compensated crystal oscillator (TCXO) and crystal.
/boot/kernel/dtaudit.ko The DTrace dtaudit provider allows users to trace events in the kernel security auditing subsystem, audit(4).
/boot/kernel/dtmalloc.ko kernel memory management routines See also [2]DTrace, also known as Dynamic Tracing, was developed by Sun™ as a tool for locating performance bottlenecks in production and pre-production systems. In addition to diagnosing performance problems, DTrace can be used to help investigate and debug unexpected behavior in both the FreeBSD kernel and in userland programs.[3]
/boot/kernel/dtnfscl.ko Dtrace is enabled by default in the GENERIC kernel, DTrace, also known as Dynamic Tracing, was developed by Sun™ as a tool for locating performance bottlenecks in production and pre-production systems. In addition to diagnosing performance problems, DTrace can be used to help investigate and debug unexpected behavior in both the FreeBSD kernel and in userland programs.[4]
/boot/kernel/dtrace.ko DTrace is a comprehensive dynamic tracing framework ported from Solaris.
/boot/kernel/dtrace_test.ko DTrace, also known as Dynamic Tracing, was developed by Sun™ as a tool for locating performance bottlenecks in production and pre-production systems. In addition to diagnosing performance problems, DTrace can be used to help investigate and debug unexpected behavior in both the FreeBSD kernel and in userland programs.[5]
/boot/kernel/dtraceall.ko DTrace, also known as Dynamic Tracing, was developed by Sun™ as a tool for locating performance bottlenecks in production and pre-production systems. In addition to diagnosing performance problems, DTrace can be used to help investigate and debug unexpected behavior in both the FreeBSD kernel and in userland programs.[6]
/boot/kernel/dummynet.ko The dummynet system facility permits the control of traffic going through the various network interfaces, by applying bandwidth and queue size limitations, implementing different scheduling and queue management policies, and emulating delays and losses.
/boot/kernel/efirt.ko All of the following calls will return ENXIO if UEFI runtime services are not available. efirt is currently only available on amd64 and arm64.
/boot/kernel/ehci.ko The ehci driver provides support for the USB Enhanced Host Controller Interface, which is used by USB 2.0 controllers.
/boot/kernel/esp.ko The esp driver provides support for the AMD Am53C974, the Emulex ESP100, ESP100A, ESP200 and ESP406, the NCR 53C90, 53C94 and 53C96 as well as the QLogic FAS100A, FAS216, FAS366 and FAS408 SCSI controller chips found in a wide variety of systems and peripheral boards.
/boot/kernel/evdev.ko evdev is an Xorg input driver for Linux's generic event devices. It therefore supports all input devices that the kernel knows about, including most mice, keyboards, tablets and touchscreens. evdev is the default driver on the major Linux distributions.
/boot/kernel/exca.ko The exca module is used to implement the Intel ExCA interface to PC Cards.
/boot/kernel/ext2fs.ko The ext2fs driver will permit the FreeBSD kernel to access ext2 file systems and its derivatives. It currently implements most of the features required by ext3 and ext4 file systems. Support for Extended Attributes in ext4 is experimental. Journalling and encryption are currently not supported.
/boot/kernel/fade_saver.ko The splash pseudo device driver adds support for the splash screen and screen savers to the kernel. This driver is required if the splash bitmap image is to be loaded or any screen saver is to be used.
/boot/kernel/fasttrap.ko Tell the DTrace fasttrap provider about the new process so that any tracepoints inherited from the parent can be removed. We have to do this only after p_state is PRS_NORMAL since the fasttrap module will use pfind() later on.
/boot/kernel/fbt.ko In FreeBSD 9.2 and 10.0, DTrace support is built into the GENERIC kernel. Users of the AMD64 architecture should also add this line: options KDTRACE_FRAME

This option provides support for FBT. While DTrace will work without this option, there will be limited support for function boundary tracing.

/boot/kernel/fdc.ko PC architecture floppy disk controller driver
/boot/kernel/fdescfs.ko The file-descriptor file system, or fdescfs, provides access to the per-process file descriptor namespace in the global file system namespace. The conventional mount point is /dev/fd.
/boot/kernel/filemon.ko The filemon device allows a process to collect file operations data of its children.
/boot/kernel/fire_saver.ko The splash pseudo device driver adds support for the splash screen and screen savers to the kernel. This driver is required if the splash bitmap image is to be loaded or any screen saver is to be used.
/boot/kernel/firewire.ko IEEE1394 High-performance Serial Bus
/boot/kernel/firmware.ko The firmware abstraction provides a convenient interface for loading firmware images into the kernel, and for accessing such images from kernel components.
/boot/kernel/fuse.ko Fuse is a Sinclair ZX Spectrum emulator. It supports several models (including the 128), with quite faithful emulation of the display and sound.
/boot/kernel/fusefs.ko The fusefs driver implements a file system that is serviced by a userspace program. There are also some sysctl(8) variables available.
/boot/kernel/g_audio.ko g - Creates a special type of combination often referred to as a group. This builds a combination by unioning together all the listed objects.
/boot/kernel/g_keyboard.ko
/boot/kernel/g_modem.ko
/boot/kernel/g_mouse.ko
/boot/kernel/geom_bde.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_cache.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_ccd.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_concat.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_eli.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_flashmap.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_gate.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_journal.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_label.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_linux_lvm.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_md.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_mirror.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_mountver.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_multipath.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_nop.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_part_apm.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_part_bsd.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_part_bsd64.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_part_ebr.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_part_gpt.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_part_ldm.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_part_mbr.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_part_vtoc8.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_raid.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_raid3.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_sched.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_shsec.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_stripe.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_uzip.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_vinum.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_virstor.ko The geom utility is used to control various GEOM classes.
/boot/kernel/geom_zero.ko The geom utility is used to control various GEOM classes.
/boot/kernel/gpiobus.ko The gpiobus system provides a simple interface to the GPIO pins that are usually available on embedded architectures and can provide bit banging style devices to the system.
/boot/kernel/gpioiic.ko The gpioiic driver provides an IIC bit-banging interface using two GPIO pins for the SCL and SDA on the gpiobus. gpioiic implements an open collector kind of output, as recommended by the standard, when driving the

pins on the gpiobus, i.e, they are never switched to the logical value of '1', or they are '0' or simply open (Hi-Z/tri-state). So the pullup resistors are required so gpioiic can work.

/boot/kernel/gpioled.ko The gpioled driver provides glue to attach a led(4) compatible device to a GPIO pin. Each LED in the system has a name which is used to export a device as /dev/led/_name_. The GPIO pin can then be controlled by writing to this device as described in led(4).
/boot/kernel/gpiospi.ko [7]
/boot/kernel/gpioths.ko [8]
/boot/kernel/green_saver.ko The splash pseudo device driver adds support for the splash screen and screen savers to the kernel. This driver is required if the splash bitmap image is to be loaded or any screen saver is to be used.
/boot/kernel/gsched_delay.ko The gsched utility (also callable as geom sched ...) changes the scheduling policy of the requests going to a provider.
/boot/kernel/gsched_rr.ko The gsched utility (also callable as geom sched ...) changes the scheduling policy of the requests going to a provider.
/boot/kernel/h_ertt.ko The h_ertt Khelp module works within the khelp(9) framework to provide TCP with a per-connection, low noise estimate of the instantaneous RTT. The implementation attempts to be robust in the face of delayed acknowledgements, TCP Segmentation Offload (TSO), receivers who manipulate TCP timestamps and lack of the TCP timestamp option altogether.
/boot/kernel/hifn.ko The hifn driver supports various cards containing the Hifn 7751, 7951, 7811, 7955, and 7956 chipsets.
/boot/kernel/hpt27xx.ko The hpt27xx driver provides support for HighPoint's RocketRAID 27xx based RAID controller.
/boot/kernel/hptiop.ko The hptiop driver provides support for the HighPoint RocketRAID 3xxx/4xxx series of SAS and SATA RAID controllers.
/boot/kernel/hptmv.ko HighPoint RocketRAID 182x device driver
/boot/kernel/hptnr.ko HighPoint DC Series Data Center HBA card driver
/boot/kernel/hptrr.ko HighPoint RocketRAID device driver
/boot/kernel/hv_netvsc.ko The hv_netvsc driver implements the virtual network device for FreeBSD guest partitions running on Hyper-V. FreeBSD guest partitions running on Hyper-V do not have direct access to network devices attached to the Hyper-V server. Although a FreeBSD guest can access network devices using Hyper-V's full emulation mode, the performance in this mode tends to be unsatisfactory.
/boot/kernel/hv_storvsc.ko Hyper-V Storage Virtual Service Consumer
/boot/kernel/hv_utils.ko The hv_utils driver provides time keeping, shutdown and heartbeat functionality for FreeBSD guest partitions running on Hyper-V. Hyper-V is a hypervisor-based virtualization technology from Microsoft. The hv_utils driver is one of the core drivers required to be present in guest partitions running on Hyper-V.
/boot/kernel/hv_vmbus.ko The hv_vmbus provides a high performance communication interface between guest and root partitions in Hyper-V. Hyper-V is a hypervisor-based virtualization technology from Microsoft. Hyper-V supports isolation in terms of a partition. A partition is a logical unit of isolation, supported by the hypervisor, in which operating systems execute.
/boot/kernel/hwpmc.ko The hwpmc driver virtualizes the hardware performance monitoring facilities in modern CPUs and provides support for using these facilities from user level processes.
/boot/kernel/i915kms.ko Intel i915 KMS driver
/boot/kernel/ibcore.ko [9]
/boot/kernel/icee.ko [10]
/boot/kernel/ichsmb.ko The ichsmb driver provides smbus(4) support for the SMBus controller logical device contained in all Intel motherboard chipsets starting from 82801AA (ICH).
/boot/kernel/ichwd.ko The ichwd driver provides watchdog(4) support for the watchdog interrupt timer present on all Intel ICH motherboard chipsets.
/boot/kernel/ida.ko Ida is a small and fast application for viewing images. Some basic editing functions are available too.
/boot/kernel/if_ae.ko Attansic/Atheros L2 FastEthernet controller driver
/boot/kernel/if_age.ko Attansic/Atheros L1 Gigabit Ethernet driver
/boot/kernel/if_alc.ko Atheros AR813x/AR815x/AR816x/AR817x Gigabit/Fast Ethernet driver
/boot/kernel/if_ale.ko Atheros AR8121/AR8113/AR8114 Gigabit/Fast Ethernet driver
/boot/kernel/if_an.ko Aironet Communications 4500/4800 wireless network adapter driver
/boot/kernel/if_ath.ko Atheros IEEE 802.11 wireless network driver
/boot/kernel/if_ath_pci.ko This module provides the PCI/PCIe bus glue needed for the devices supported by the ath(4) and ath_hal(4) drivers.
/boot/kernel/if_aue.ko The aue driver provides support for USB Ethernet adapters based on the ADMtek AN986 Pegasus chipset.
/boot/kernel/if_axe.ko The axe driver provides support for USB Ethernet adapters based on the ASIX Electronics AX88172, AX88178, AX88772, AX88772A, AX88772B and AX88760 USB 2.0 chipsets.
/boot/kernel/if_axge.ko ASIX Electronics AX88178A/AX88179 USB 2.0/3.0 gigabit ethernet driver.
/boot/kernel/if_bce.ko QLogic NetXtreme II (BCM5706/5708/5709/5716) PCI/PCIe Gigabit Ethernet adapter driver
/boot/kernel/if_bfe.ko Broadcom BCM4401 Ethernet Device Driver
/boot/kernel/if_bge.ko Broadcom BCM57xx/BCM590x Gigabit/Fast Ethernet driver
/boot/kernel/if_bnxt.ko Broadcom NetXtreme-C/NetXtreme-E Family Ethernet driver
/boot/kernel/if_bridge.ko The if_bridge driver creates a logical link between two or more IEEE 802 networks that use the same (or "similar enough") framing format. For example, it is possible to bridge Ethernet and 802.11 networks together, but it is not possible to bridge Ethernet and Token Ring together.
/boot/kernel/if_bwi.ko Broadcom BCM43xx IEEE 802.11b/g wireless network driver
/boot/kernel/if_bwn.ko Broadcom BCM43xx SoftMAC IEEE 802.11 wireless network driver
/boot/kernel/if_bxe.ko QLogic NetXtreme II Ethernet 10Gb PCIe adapter driver
/boot/kernel/if_cas.ko Sun Cassini/Cassini+ and National Semiconductor DP83065 Saturn Gigabit Ethernet driver
/boot/kernel/if_cc.ko Chelsio T4-, T5-, and T6-based 100Gb, 40Gb, 25Gb, 10Gb, and 1Gb Ethernet adapter driver
/boot/kernel/if_ccv.ko Chelsio T4-, T5-, and T6-based 100Gb, 40Gb, 25Gb, 10Gb, and 1Gb Ethernet VF driver
/boot/kernel/if_cdce.ko USB Communication Device Class Ethernet (CDC ECM/NCM) driver
/boot/kernel/if_cdceem.ko [11] Universal Serial Bus Communications Class Subclass Specification for Ethernet Emulation Model Devices.
/boot/kernel/if_cs.ko Device driver for Crystal Semiconductor CS8920 based ethernet adapters. By Maxim Bolotin and Oleg Sharoiko, 27-April-1997
/boot/kernel/if_cue.ko CATC USB-EL1210A USB Ethernet driver
/boot/kernel/if_cxgb.ko Chelsio T3 10 Gigabit Ethernet adapter driver
/boot/kernel/if_cxgbe.ko Chelsio T4-, T5-, and T6-based 100Gb, 40Gb, 25Gb, 10Gb, and 1Gb Ethernet adapter driver
/boot/kernel/if_cxgbev.ko Chelsio T4-, T5-, and T6-based 100Gb, 40Gb, 25Gb, 10Gb, and 1Gb Ethernet VF driver
/boot/kernel/if_cxl.ko Chelsio T4-, T5-, and T6-based 100Gb, 40Gb, 25Gb, 10Gb, and 1Gb Ethernet adapter driver
/boot/kernel/if_cxlv.ko Chelsio T4-, T5-, and T6-based 100Gb, 40Gb, 25Gb, 10Gb, and 1Gb Ethernet VF driver
/boot/kernel/if_dc.ko DEC/Intel 21143 and clone 10/100 Ethernet driver
/boot/kernel/if_de.ko DEC DC21x4x Ethernet device driver
/boot/kernel/if_disc.ko The disc interface is a software discard mechanism which may be used for performance analysis and/or software testing. As with other network interfaces, the discard interface must have network addresses assigned for each address family with which it is to be used.
/boot/kernel/if_ed.ko NE-2000 and WD-80x3 Ethernet driver
/boot/kernel/if_edsc.ko The edsc interface is a software discard mechanism which may be used for performance analysis and software testing. It imitates an Ethernet device, which allows for its use in conjunction with such drivers as if_bridge(4) and vlan(4).
/boot/kernel/if_em.ko Intel(R) PRO/1000 Gigabit Ethernet adapter driver
/boot/kernel/if_ena.ko FreeBSD kernel driver for Elastic Network Adapter (ENA) family
/boot/kernel/if_enc.ko The enc interface is a software loopback mechanism that allows hosts or firewalls to filter ipsec(4) traffic using any firewall package that hooks in via the pfil(9) framework.
/boot/kernel/if_ep.ko [12]
/boot/kernel/if_epair.ko The epair is a pair of Ethernet-like software interfaces, which are connected back-to-back with a virtual cross-over cable.
/boot/kernel/if_et.ko Agere ET1310 10/100/Gigabit Ethernet driver
/boot/kernel/if_fe.ko Device driver for Fujitsu MB86960A/MB86965A based Ethernet cards.
/boot/kernel/if_fwe.ko Ethernet emulation driver for FireWire
/boot/kernel/if_fwip.ko IP over FireWire driver
/boot/kernel/if_fxp.ko Intel EtherExpress PRO/100 Ethernet device driver
/boot/kernel/if_gem.ko ERI/GEM/GMAC Ethernet device driver
/boot/kernel/if_gif.ko The gif interface is a generic tunnelling device for IPv4 and IPv6. It can tunnel IPv[46] traffic over IPv[46]. Therefore, there can be four possible configurations. The behavior of gif is mainly based on RFC2893 IPv6-over-IPv4 configured tunnel. On NetBSD, gif can also tunnel ISO traffic over IPv[46] using EON encapsulation.
/boot/kernel/if_gre.ko The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they are decapsulated and further routed to their final destination. The "tunnel" appears to the inner datagrams as one hop.
/boot/kernel/if_hme.ko Sun Microelectronics STP2002-STQ Ethernet interfaces device driver
/boot/kernel/if_iavf.ko The iavf driver provides support for the PCI Virtual Functions from the 700 Series of ethernet devices and newer product families. The driver supports Jumbo Frames, TX/RX checksum offload, TCP segmentation offload (TSO), Large Receive Offload (LRO), VLAN tag insertion/extraction, VLAN checksum offload, VLAN TSO, and Receive Side Steering (RSS), all for both IPv4 and IPv6.
/boot/kernel/if_ic.ko I2C bus IP driver
/boot/kernel/if_igb.ko The igb driver provides support for PCI Express Gigabit Ethernet adapters based on the Intel 82575, 82576, 82580, i21x and i35x Ethernet controller chips. The driver supports Transmit/Receive checksum offload and Jumbo Frames. Furthermore it supports TCP segmentation offload (TSO) on all adapters.
/boot/kernel/if_ipheth.ko The ipheth driver provides support for network access through Apple iPhone and iPad devices, often referred to as USB tethering. ipheth should work with any Apple iPhone or iPad device. In most cases this must be explicitly enabled on the device first.
/boot/kernel/if_ipw.ko The ipw driver provides support for the Intel PRO/Wireless 2100 MiniPCI network adapter. ipw supports station, adhoc, and monitor mode operation. Only one virtual interface may be configured at any time. For more information on configuring this device, see ifconfig(8).
/boot/kernel/if_iwi.ko The iwi driver provides support for Intel PRO/Wireless 2200BG/2915ABG MiniPCI and 2225BG PCI network adapters. iwi supports station, adhoc, and monitor mode operation. Only one virtual interface may be configured at any time.
/boot/kernel/if_iwm.ko Intel IEEE 802.11ac wireless network driver
/boot/kernel/if_iwn.ko Intel IEEE 802.11n wireless network driver
/boot/kernel/if_ix.ko The ixgbe driver provides support for PCI 10Gb Ethernet adapters based on the Intel 82598EB Intel(R) Network Connections. The driver supports Jumbo Frames, MSIX, TSO, and RSS
/boot/kernel/if_ixl.ko Intel Ethernet 700 Series Driver
/boot/kernel/if_ixlv.ko Intel XL710 Ethernet 40Gb VF driver
/boot/kernel/if_ixv.ko ixv_driver
/boot/kernel/if_jme.ko The jme device driver provides support for JMicron JMC25x PCI Express Gigabit Ethernet controllers and JMicron JMC26x PCI Express Fast Ethernet controllers.
/boot/kernel/if_kue.ko The kue driver provides support for USB Ethernet adapters based on the Kawasaki LSI KL5KLUSB101B chipset.
/boot/kernel/if_lagg.ko The lagg interface allows aggregation of multiple network interfaces as one virtual lagg interface for the purpose of providing fault-tolerance and high-speed links.
/boot/kernel/if_le.ko The le driver provides support for Ethernet adapters based on the AMD Am7990 and Am79C90 (CMOS, pin-compatible) Local Area Network Controller for Ethernet (LANCE) chips.
boot/kernel/if_lge.ko Level 1 LXT1001 NetCellerator PCI Gigabit Ethernet adapter driver
/boot/kernel/if_lio.ko
/boot/kernel/if_malo.ko Marvell Libertas IEEE 802.11b/g wireless network driver
/boot/kernel/if_me.ko
/boot/kernel/if_mos.ko Moschip MCS7730/MCS7830/MCS7832 USB Ethernet driver
/boot/kernel/if_msk.ko Marvell/SysKonnect Yukon II Gigabit Ethernet adapter driver
/boot/kernel/if_muge.ko
/boot/kernel/if_mwl.ko Marvell 88W8363 IEEE 802.11n wireless network driver
/boot/kernel/if_mxge.ko Myricom Myri10GE 10 Gigabit Ethernet adapter driver
/boot/kernel/if_my.ko Myson Technology Ethernet PCI driver
/boot/kernel/if_ndis.ko The ndis driver is a wrapper designed to allow binary Windows(R) NDIS miniport network drivers to be used with FreeBSD.
/boot/kernel/if_nfe.ko NVIDIA nForce MCP Ethernet driver
/boot/kernel/if_nge.ko The nge driver provides support for various NICs based on the National Semiconductor DP83820 and DP83821 Gigabit Ethernet controller chips.
/boot/kernel/if_ntb.ko Virtual Ethernet interface for Non-Transparent Bridges
/boot/kernel/if_oce.ko
/boot/kernel/if_otus.ko Atheros AR9170 USB IEEE 802.11a/b/g/n wireless network device
/boot/kernel/if_pcn.ko AMD PCnet/PCI Fast Ethernet device driver
/boot/kernel/if_qlnxe.ko Cavium 25/40/100 Gigabit Ethernet & CNA Adapter Driver
/boot/kernel/if_qlnxev.ko
/boot/kernel/if_qlxgb.ko QLogic 10 Gigabit Ethernet & CNA Adapter Driver
/boot/kernel/if_qlxgbe.ko QLogic 10 Gigabit Ethernet & CNA Adapter Driver
/boot/kernel/if_qlxge.ko QLogic 8100 Series 10 Gigabit Ethernet Adapter Driver
/boot/kernel/if_ral.ko Ralink Technology IEEE 802.11a/g/n wireless network device
/boot/kernel/if_re.ko RealTek 8139C+/8169/816xS/811xS/8168/810xE/8111 PCI/PCIe Ethernet adapter driver
/boot/kernel/if_rl.ko RealTek 8129/8139 Fast Ethernet device driver
/boot/kernel/if_rsu.ko Realtek RTL8188SU/RTL8192SU USB IEEE 802.11b/g/n wireless network device
/boot/kernel/if_rtwn_pci.ko Realtek PCI device glue
/boot/kernel/if_rtwn_usb.ko Realtek USB device glue
/boot/kernel/if_rue.ko RealTek RTL8150 USB to Fast Ethernet controller driver
/boot/kernel/if_rum.ko Ralink Technology USB IEEE 802.11a/b/g wireless network device
/boot/kernel/if_run.ko Ralink Technology USB IEEE 802.11a/g/n wireless network device
/boot/kernel/if_sf.ko Adaptec AIC-6915 "Starfire" PCI Fast Ethernet adapter driver
/boot/kernel/if_sge.ko Silicon Integrated Systems SiS190/191 Fast/Gigabit Ethernet driver
/boot/kernel/if_sis.ko SiS 900, SiS 7016 and NS DP83815/DP83816 Fast Ethernet device
/boot/kernel/if_sk.ko SysKonnect SK-984x and SK-982x PCI Gigabit Ethernet adapter driver
/boot/kernel/if_smsc.ko USB SMSC LAN9xxx Fast Ethernet driver
/boot/kernel/if_sn.ko Ethernet driver for SMC91Cxx based cards
/boot/kernel/if_ste.ko Sundance Technologies ST201 Fast Ethernet device driver
/boot/kernel/if_stf.ko The stf interface supports "6to4" IPv6 in IPv4 encapsulation. It can tunnel IPv6 traffic over IPv4, as specified in RFC3056.
/boot/kernel/if_stge.ko Sundance/Tamarack TC9021 Gigabit Ethernet adapter driver
/boot/kernel/if_tap.ko The tap interface is a software loopback mechanism that can be loosely described as the network interface analog of the pty(4), that is, tap does for network interfaces what the pty(4) driver does for terminals.
/boot/kernel/if_ti.ko Alteon Networks Tigon I and Tigon II Gigabit Ethernet driver
/boot/kernel/if_tl.ko Texas Instruments ThunderLAN Ethernet device driver
/boot/kernel/if_tun.ko The tun interface is a software loopback mechanism that can be loosely described as the network interface analog of the pty(4), that is, tun does for network interfaces what the pty(4) driver does for terminals.
/boot/kernel/if_tuntap.ko
/boot/kernel/if_tx.ko SMC 83c17x Fast Ethernet device driver
/boot/kernel/if_txp.ko 3Com 3XP Typhoon/Sidewinder (3CR990) Ethernet interface
/boot/kernel/if_uath.ko Atheros USB IEEE 802.11a/b/g wireless network device
/boot/kernel/if_udav.ko Davicom DM9601 USB Ethernet driver
/boot/kernel/if_upgt.ko Conexant/Intersil PrismGT SoftMAC USB IEEE 802.11b/g wireless network device
/boot/kernel/if_ural.ko Ralink Technology RT2500USB IEEE 802.11 driver
/boot/kernel/if_ure.ko RealTek RTL8152/RTL8153 USB to Ethernet controller driver
/boot/kernel/if_urndis.ko USB Remote NDIS Ethernet device
/boot/kernel/if_urtw.ko Realtek RTL8187B/L USB IEEE 802.11b/g wireless network device
/boot/kernel/if_vge.ko VIA Networking Technologies Velocity Gigabit Ethernet adapter
/boot/kernel/if_vlan.ko IEEE 802.1Q VLAN network interface
/boot/kernel/if_vmx.ko VMware VMXNET3 Virtual Interface Controller device
/boot/kernel/if_vr.ko VIA Technologies Rhine I/II/III Ethernet device driver
/boot/kernel/if_vte.ko Vortex86 RDC R6040 Fast Ethernet driver
/boot/kernel/if_vtnet.ko The vtnet device driver provides support for VirtIO Ethernet devices.
/boot/kernel/if_vx.ko
/boot/kernel/if_vxlan.ko Virtual eXtensible LAN interface
/boot/kernel/if_wb.ko Winbond W89C840F Fast Ethernet device driver
/boot/kernel/if_wi.ko Lucent Hermes, and Intersil PRISM IEEE 802.11 driver
/boot/kernel/if_wpi.ko Intel 3945ABG Wireless LAN IEEE 802.11 driver
/boot/kernel/if_xe.ko Xircom PCMCIA Ethernet device driver
/boot/kernel/if_xl.ko 3Com Etherlink XL and Fast Etherlink XL Ethernet device driver
/boot/kernel/if_zyd.ko ZyDAS ZD1211/ZD1211B USB IEEE 802.11b/g wireless network device
/boot/kernel/iflib.ko iflib is a framework for network interface drivers for FreeBSD. It is designed to remove a large amount of the boilerplate that is often needed for modern network interface devices, allowing driver authors to focus on the specific code needed for their hardware. This allows for a shared set of sysctl(8) names, rather than each driver naming them individually.
/boot/kernel/ig4.ko The ig4 driver provides access to peripherals attached to an I2C controller.
/boot/kernel/iic.ko The iic device driver provides generic I/O to any iicbus(4) instance.
/boot/kernel/iicbb.ko The iicbb driver provides support to any bit-banging interface for the iicbus(4) system.
/boot/kernel/iicbus.ko The iicbus system provides a uniform, modular and architecture-independent system for the implementation of drivers to control various I2C devices and to utilize different I2C controllers.
/boot/kernel/iicmux.ko
/boot/kernel/iicsmb.ko The iicsmb driver supports SMB commands over iicbus(4) for the smbus(4) system.
/boot/kernel/iir.ko Intel Integrated RAID controller and ICP Vortex driver
/boot/kernel/imcsmb.ko Intel integrated Memory Controller (iMC) SMBus controller driver
/boot/kernel/imgact_binmisc.ko imgact_binmisc is an image activator for miscellaneous binary file types that are executed with the help of a user-level interpreter or emulator.
/boot/kernel/intelspi.ko Driver for SPI support on Minnowboard is intelspi. Hardware supports all four SPI modes and clock frequency configuration but the driver doesn’t (yet). So it’s always mode 0 and frequency is hardcoded to 10MHz. To access it from userland you’d use spigen driver for now.
/boot/kernel/intpm.ko Intel PIIX4 Power Management controller driver
/boot/kernel/io.ko Standard I/O Server Interface Functions
/boot/kernel/ioat.ko Intel I/O Acceleration Technology
/boot/kernel/ip6_mroute.ko Multicast Routing set/getsockopt commands.
/boot/kernel/ip_mroute.ko Multicast Routing to FreeBSD kernel
/boot/kernel/ipdivert.ko kernel packet diversion mechanism
/boot/kernel/ipfw.ko User interface for firewall, traffic shaper, packet scheduler, in-kernel NAT
/boot/kernel/ipfw_nat.ko IPFW is a stateful firewall written for FreeBSD which supports both IPv4 and IPv6. It is comprised of several components: the kernel firewall filter rule processor and its integrated packet accounting facility, the logging facility, NAT, the dummynet(4) traffic shaper, a forward facility, a bridge facility, and an ipstealth facility.
/boot/kernel/ipfw_nat64.ko IPFW is a stateful firewall written for FreeBSD which supports both IPv4 and IPv6. It is comprised of several components: the kernel firewall filter rule processor and its integrated packet accounting facility, the logging facility, NAT, the dummynet(4) traffic shaper, a forward facility, a bridge facility, and an ipstealth facility.
/boot/kernel/ipfw_nptv6.ko IPFW is a stateful firewall written for FreeBSD which supports both IPv4 and IPv6. It is comprised of several components: the kernel firewall filter rule processor and its integrated packet accounting facility, the logging facility, NAT, the dummynet(4) traffic shaper, a forward facility, a bridge facility, and an ipstealth facility.
/boot/kernel/ipfw_pmod.ko IPFW is a stateful firewall written for FreeBSD which supports both IPv4 and IPv6. It is comprised of several components: the kernel firewall filter rule processor and its integrated packet accounting facility, the logging facility, NAT, the dummynet(4) traffic shaper, a forward facility, a bridge facility, and an ipstealth facility.
/boot/kernel/ipl.ko IP packet log device
/boot/kernel/ipmi.ko OpenIPMI compatible IPMI interface driver. The IPMI (Intelligent Platform Management Interface) is a standard for

monitoring system hardware by permitting generic code to detect and monitor the sensors in a system. The IPMI standard offers watchdog support, an FRU database, and other support extensions. It is currently being adopted by the makers of many single board and embedded system anufacturers.

/boot/kernel/ipmi_linux.ko Linux ioctl handler for the ipmi device driver
/boot/kernel/ipoib.ko Fix some whitespace issues in ipoib.
/boot/kernel/ips.ko IBM/Adaptec ServeRAID controller driver
/boot/kernel/ipsec.ko The ipsec utility invokes any of several utilities involved in controlling and monitoring the IPsec encryption/authentication system, running the specified command with the specified arguments and options as if it had been invoked directly. This largely eliminates possible name collisions with other software, and also permits some centralized services.
/boot/kernel/ipw_bss.ko You need to read the LICENSE file in /usr/share/doc/legal/intel, If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
/boot/kernel/ipw_ibss.ko You need to read the LICENSE file in /usr/share/doc/legal/intel, If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
/boot/kernel/ipw_monitor.ko You need to read the LICENSE file in /usr/share/doc/legal/intel, If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
/boot/kernel/isci.ko The isci driver provides support for Intel C600 SAS controllers.
/boot/kernel/iscsi.ko The iscsi subsystem provides the kernel component of an iSCSI initiator, responsible for implementing the Full Feature Phase of the iSCSI protocol. The initiator is the iSCSI client, which connects to an iSCSI target, providing local access to a remote block device. The userland component is provided by iscsid(8) and both the kernel and userland are configured using iscsictl(8).
/boot/kernel/iscsi_initiator.ko This driver, along with its userspace counterpart iscontrol(8), is obsolete. Users are advised to use iscsi(4) instead.
/boot/kernel/iser.ko The iser (iSCSI Extensions for RDMA) initiator driver extends the iSCSI protocol to RDMA. It permits data to be transferred directly into and out of SCSI buffers without intermediate data copies.
/boot/kernel/isl.ko Intersil(TM) I2C ISL29018 sensor driver
/boot/kernel/[ttps://www.leidinger.net/FreeBSD/dox/dev_iicbus/html/d9/db5/isl12xx_8c_source.html isl12xx].ko Driver for ISL12xx family i2c realtime clocks
/boot/kernel/ismt.ko Intel SMBus Message Transport (SMBus 2.0) driver
/boot/kernel/isp.ko Qlogic based SPI and FibreChannel SCSI Host Adapters
/boot/kernel/isp_1040.ko ISP Firmware Modules for FreeBSD
/boot/kernel/isp_1080.ko ISP Firmware Modules for FreeBSD
/boot/kernel/isp_2100.ko ISP Firmware Modules for FreeBSD
/boot/kernel/isp_2200.ko ISP Firmware Modules for FreeBSD
/boot/kernel/isp_2300.ko ISP Firmware Modules for FreeBSD
/boot/kernel/isp_2322.ko ISP Firmware Modules for FreeBSD
/boot/kernel/isp_2400.ko ISP Firmware Modules for FreeBSD
/boot/kernel/isp_2500.ko ISP Firmware Modules for FreeBSD
/boot/kernel/isp_12160.ko ISP Firmware Modules for FreeBSD
/boot/kernel/ispfw.ko Firmware for Qlogic based SPI and FibreChannel SCSI Host Adapters
/boot/kernel/iw_cxgbe.ko iWARP driver for Chelsio T4/T5 chips. This is a straight port of the iw_cxgb4 found in OFED distributions.
/boot/kernel/iwi_bss.ko Intel(R) PRO/Wireless 2200BG; You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/. If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
/boot/kernel/iwi_ibss.ko Add Intel firmwares for Intel PRO/Wireless LAN 2100/2200/2915 cards in a uuencoded format along with their respective LICENSE files. Add new share/doc/legal directory to BSD.usr.dist mtree file. This is the place we install LICENSE files for restricted firmwares.
/boot/kernel/iwi_monitor.ko Add Intel firmwares for Intel PRO/Wireless LAN 2100/2200/2915 cards in a uuencoded format along with their respective LICENSE files. Add new share/doc/legal directory to BSD.usr.dist mtree file. This is the place we install LICENSE files for restricted firmwares.
/boot/kernel/iwm3160fw.ko Intel IEEE 802.11ac wireless network driver
/boot/kernel/iwm3168fw.ko Intel IEEE 802.11ac wireless network driver
/boot/kernel/iwm7260fw.ko Intel IEEE 802.11ac wireless network driver
/boot/kernel/iwm7265Dfw.ko Intel IEEE 802.11ac wireless network driver
/boot/kernel/iwm7265fw.ko Intel IEEE 802.11ac wireless network driver
/boot/kernel/iwm8000Cfw.ko Intel IEEE 802.11ac wireless network driver
/boot/kernel/iwm8265fw.ko Intel IEEE 802.11ac wireless network driver
/boot/kernel/iwm9000fw.ko Intel IEEE 802.11ac wireless network driver
/boot/kernel/iwm9260fw.ko Intel IEEE 802.11ac wireless network driver
/boot/kernel/iwn100fw.ko Firmware Module for Intel Wireless driver
/boot/kernel/iwn105fw.ko Firmware Module for Intel Wireless driver
/boot/kernel/iwn135fw.ko Firmware Module for Intel Wireless driver
/boot/kernel/iwn1000fw.ko Firmware Module for Intel Wireless driver
/boot/kernel/iwn2000fw.ko Firmware Module for Intel Wireless driver
/boot/kernel/iwn2030fw.ko Firmware Module for Intel Wireless driver
/boot/kernel/iwn4965fw.ko Firmware Module for Intel Wireless driver
/boot/kernel/iwn5000fw.ko Firmware Module for Intel Wireless driver
/boot/kernel/iwn5150fw.ko Firmware Module for Intel Wireless driver
/boot/kernel/iwn6000fw.ko Firmware Module for Intel Wireless driver
/boot/kernel/iwn6000g2afw.ko Firmware Module for Intel Wireless driver
/boot/kernel/iwn6000g2bfw.ko Firmware Module for Intel Wireless driver
/boot/kernel/iwn6050fw.ko Firmware Module for Intel Wireless driver
/boot/kernel/jedec_dimm.ko The jedec_dimm driver reports asset information (Part Number, Serial Number) encoded in the "Serial Presence Detect" (SPD) data on JEDEC DDR3 and DDR4 DIMMs. It also calculates and reports the memory capacity of the DIMM, in megabytes. If the DIMM includes a "Thermal Sensor On DIMM" (TSOD), the temperature is also reported.
/boot/kernel/joy.ko Global array of joystick state information, which is updated by the poll_joystick() function. Only the first num_joysticks elements will contain meaningful information.
/boot/kernel/kbdmux.ko The kbdmux keyboard driver provides support for basic keyboard multiplexing. It is built around the idea of a "super keyboard". The kbdmux driver acts as a master keyboard consuming input from all slave keyboards attached to it.
/boot/kernel/kern_testfrwk.ko A kernel testing framework
/boot/kernel/kernel The Kernel application is the first application started. It is mandatory in the sense that the minimal system based on Erlang/OTP consists of Kernel and STDLIB.
/boot/kernel/kgssapi.ko Stop using des_cblock for arguments to DES functions.
/boot/kernel/kgssapi_krb5.ko Stop using des_cblock for arguments to DES functions.
/boot/kernel/krpc.ko zfs.ko: depends on krpc - not available or version mismatch
/boot/kernel/krping.ko support for setting service types for outgoing RDMA connections via the KRPING utility
/boot/kernel/ksyms.ko The /dev/ksyms character device provides a read-only interface to a snapshot of the kernel symbol table. The in-kernel symbol manager is designed to be able to handle many types of symbols tables, however, only elf(5) symbol tables are supported by this device. The ELF format image contains two sections: a symbol table and a corresponding string table.
/boot/kernel/libalias.ko The libalias library is a collection of functions for aliasing and dealiasing of IP packets, intended for masquerading and network address translation (NAT).
/boot/kernel/libiconv.ko The iconv_open() function opens a converter from the codeset srcname to the codeset dstname and returns its descriptor. The arguments srcname and dstname accept "" and "char", which refer to the current locale encoding.Supporting function for the common internet file system CIFS and smbfs
/boot/kernel/libmchain.ko Supporting function for the common internet file system CIFS and smbfs
/boot/kernel/linker.hints The kldxref utility is used to generate hint files which list modules,

their version numbers, and the files that contain them. These hints are used by the kernel loader to determine where to find a particular KLD, Option -f file Specify a different name for the hint files than linker.hints. module.

/boot/kernel/linprocfs.ko Linux process file system
/boot/kernel/linsysfs.ko Linux system file system
/boot/kernel/linux.ko Linux ABI support
/boot/kernel/linux64.ko
/boot/kernel/linux_common.ko
/boot/kernel/linuxkpi.ko
/boot/kernel/logo_saver.ko Animated graphical FreeBSD logo
/boot/kernel/lpbb.ko parallel port I2C bit-banging interface
/boot/kernel/lpt.ko The current lpt driver is the port of the original lpt driver to the ppbus(4) system.
/boot/kernel/ltc430x.ko I2C bus multiplexer (mux) devices, LTC4305 and LTC4306 i2c mux chips
/boot/kernel/mac_biba.ko The mac_biba policy module implements the Biba integrity model, which protects the integrity of system objects and subjects by means of a strict information flow policy. In Biba, all system subjects and objects are assigned integrity labels, made up of hierarchal grades, and non-hi-erarchal components.
/boot/kernel/mac_bsdextended.ko The mac_bsdextended security policy module provides an interface for the system administrator to impose mandatory rules regarding users and some system objects. Rules are uploaded to the module (typically using ugidfw(8), or some other tool utilizing libugidfw(3)) where they are stored internally and used to determine whether to allow or deny specific accesses (see ugidfw(8)).
/boot/kernel/mac_ifoff.ko The mac_ifoff interface silencing module allows administrators to enable and disable incoming and outgoing data flow on system network interfaces via the sysctl(8) interface.
/boot/kernel/mac_lomac.ko The mac_lomac policy module implements the LOMAC integrity model, which protects the integrity of system objects and subjects by means of an information flow policy coupled with the subject demotion via floating labels.
/boot/kernel/mac_mls.ko Multi-Level Security confidentiality policy
/boot/kernel/mac_none.ko null MAC policy module
/boot/kernel/mac_ntpd.ko policy allowing ntpd to run as non-root user
/boot/kernel/mac_partition.ko The ac_partition policy module implements a process partition policy, which allows administrators to place running processes into "partitions", based on their numeric process partition (specified in the process's MAC label).
/boot/kernel/mac_portacl.ko network port access control policy
/boot/kernel/mac_seeotheruids.ko The mac_seeotheruids policy module, when enabled, denies users to see processes or sockets owned by other users.
/boot/kernel/mac_stub.ko The mac_stub policy module implements a stub MAC policy that has no effect on access control in the system. Unlike mac_none(4), each MAC entry point is defined as a "no-op", so the policy module will be entered for each event, but no change in system behavior should result.
/boot/kernel/mac_test.ko MAC framework testing policy
/boot/kernel/mach64.ko ..
/boot/kernel/mdio.ko IEEE 802.3 Management Data Input/Output interface
/boot/kernel/mem.ko use modules from "mem"ory & allow consistent syntax for inits
/boot/kernel/mfi.ko This driver is for LSI's next generation PCI Express SAS RAID controllers.
/boot/kernel/mfi_linux.ko This driver is for LSI's next generation PCI Express SAS RAID controllers. Access to RAID arrays (logical disks) from this driver is provided via /dev/mfid? device nodes. A simple management interface is also provided on a per-controller basis via the /dev/mfi? device node.
/boot/kernel/mfip.ko LSI MegaRAID SAS driver
/boot/kernel/mga.ko is an Xorg driver for Matrox video cards.
/boot/kernel/miibus.ko The miibus driver provides an interconnection between the Media Access Control (MAC) sublayer, the Physical Layer entities (PHY), Station Management (STA) entities, and the PHY Layer as defined by the IEEE 802.3 Standard.
/boot/kernel/mlx.ko Mylex DAC-family RAID driver
/boot/kernel/mlx4.ko
/boot/kernel/mlx4en.ko Mellanox ConnectX-3 10GbE/40GbE network adapter driver
/boot/kernel/mlx4ib.ko Mellanox ConnectX-3 10GbE/40GbE network adapter driver
/boot/kernel/mlx5.ko
/boot/kernel/mlx5en.ko Mellanox ConnectX-4, ConnectX-4 LX and ConnectX-5 based 100Gb, 50Gb, 40Gb, 25Gb and 10Gb Ethernet adapter driver
/boot/kernel/mlx5ib.ko Mellanox ConnectX-4 and ConnectX-4 LX based 100Gb, 50Gb, 40Gb, 25Gb and 10Gb network adapter driver
/boot/kernel/mlxfw.ko
/boot/kernel/mly.ko Mylex AcceleRAID/eXtremeRAID family driver
/boot/kernel/mmc.ko MultiMediaCard and SD Card bus driver
/boot/kernel/mmcsd.ko MMC and SD memory card driver
/boot/kernel/mpr.ko LSI Fusion-MPT 3/3.5 IT/IR 12Gb/s Serial Attached SCSI/SATA/PCIe driver
/boot/kernel/mps.ko LSI Fusion-MPT 2 IT/IR 6Gb/s Serial Attached SCSI/SATA driver
/boot/kernel/mpt.ko LSI Fusion-MPT SCSI/Fibre Channel driver
/boot/kernel/mqueuefs.ko The mqueuefs module will permit the FreeBSD kernel to support POSIX message queue. The module contains system calls to manipulate POSIX message queues.
/boot/kernel/mrsas.ko LSI MegaRAID 6Gb/s and 12Gb/s SAS+SATA RAID controller driver
/boot/kernel/mrsas_linux.ko
/boot/kernel/msdosfs.ko The msdosfs driver will permit the FreeBSD kernel to read and write MS-DOS based file systems. The most common usage follows: mount -t msdosfs /dev/ada0sN/mnt
/boot/kernel/msdosfs_iconv.ko
/boot/kernel/mthca.ko
/boot/kernel/mvs.ko A command line Mediawiki client
/boot/kernel/mw88W8363fw.ko
/boot/kernel/mx25l.ko The mx25l driver provides support for the family of non-volatile storage devices known collectively as SpiFlash(tm). SpiFlash chips typically have part numbers beginning with EN25, IS25, MX25, S25, SST25, or W25.
/boot/kernel/mxge_eth_z8e.ko mxge -- Myricom Myri10GE 10 Gigabit Ethernet adapter driver
/boot/kernel/mxge_ethp_z8e.ko mxge -- Myricom Myri10GE 10 Gigabit Ethernet adapter driver
/boot/kernel/mxge_rss_eth_z8e.ko mxge -- Myricom Myri10GE 10 Gigabit Ethernet adapter driver
/boot/kernel/mxge_rss_ethp_z8e.ko mxge -- Myricom Myri10GE 10 Gigabit Ethernet adapter driver
/boot/kernel/nctgpio.ko
/boot/kernel/ndis.ko The ndis driver is a wrapper designed to allow binary Windows(R) NDIS miniport network drivers to be used with FreeBSD.
/boot/kernel/netgraph.ko These functions facilitate user-mode program participation in the kernel netgraph(4) graph-based networking system, by utilizing the netgraph socket node type (see ng_socket(4)).
/boot/kernel/nfscl.ko Network File System (NFS)
/boot/kernel/nfscommon.ko Network File System (NFS)
/boot/kernel/nfsd.ko The nfsd utility runs on a server machine to service NFS requests from client machines. At least one nfsd must be running for a machine to operate as a server.
/boot/kernel/nfslock.ko Network File System (NFS)
/boot/kernel/nfslockd.ko Network File System (NFS)
/boot/kernel/nfsmb.ko The nfsmb driver provides access to NVIDIA nForce2/3/4 SMBus 2.0 controllers.
/boot/kernel/nfssvc.ko The nfssvc() system call is used by the NFS daemons to pass information into and out of the kernel and also to enter the kernel as a server daemon.
/boot/kernel/ng_async.ko The async node type performs conversion between synchronous frames and asynchronous frames, as defined for the PPP protocol in RFC 1662.
/boot/kernel/ng_atmllc.ko The atmllc node type translates frames in to and out of ATM LLC encapsulation, as specified by RFC 1483.
/boot/kernel/ng_bluetooth.ko The ng_bluetooth module is a placeholder for global Bluetooth variables. All Bluetooth variables can be examined and changed via sysctl.
/boot/kernel/ng_bpf.ko The bpf node type allows Berkeley Packet Filter (see bpf(4)) filters to be applied to data travelling through a Netgraph network. Each node allows an arbitrary number of connections to arbitrarily named hooks.
/boot/kernel/ng_bridge.ko The bridge node type performs Ethernet bridging over one or more links. Each link (represented by a connected hook) is used to transmit and receive raw Ethernet frames.
/boot/kernel/ng_bt3c.ko Netgraph node type that is also a 3Com Bluetooth PC card
/boot/kernel/ng_btsocket.ko Bluetooth sockets layer
/boot/kernel/ng_car.ko Committed Access Rate netgraph node type
/boot/kernel/ng_ccatm.ko The ng_ccatm node implements the API specified by the ATM Forum for access to ATM services (see ATM-Forum document af-saa-0108).
/boot/kernel/ng_cisco.ko The cisco node type performs encapsulation and de-encapsulation of packets using the Cisco HDLC protocol. This is a fairly simple protocol for the transmission of packets across high speed synchronous lines.
/boot/kernel/ng_deflate.ko The deflate node type implements the Deflate sub-protocols of the Compression Control Protocol (CCP).
/boot/kernel/ng_device.ko A device node is both a netgraph node and a system device interface. When a device node is created, a new device entry appears which is accessible via the regular file operators such as open(2), close(2), read(2), write(2), etc.
/boot/kernel/ng_echo.ko The echo node type reflects all data and control messages back to the sender. This node type is used for testing and debugging.
/boot/kernel/ng_eiface.ko The eiface netgraph node implements the generic Ethernet interface.
/boot/kernel/ng_etf.ko The etf node type multiplexes and filters data between hooks on the basis of the ethertype found in an Ethernet header, presumed to be in the first 14 bytes of the data. Incoming Ethernet frames are accepted on the downstream hook and if the ethertype matches a value which the node has been configured to filter, the packet is forwarded out the hook which was identified at the time that value was configured.
/boot/kernel/ng_ether.ko The ether netgraph node type allows Ethernet interfaces to interact with the netgraph(4) networking subsystem.
/boot/kernel/ng_ether_echo.ko The ether_echo node type reflects all data and control messages back to the sender. It assumes (and does not check) that the packet is an ethernet frame, and swaps the source and destination addresses before echoing it. This node type is used for testing and debugging.
/boot/kernel/ng_frame_relay.ko The frame_relay node type performs encapsulation, de-encapsulation, and multiplexing of packets using the frame relay protocol. It supports up to 1024 DLCI's. The LMI protocol is handled by a separate node type (see ng_lmi(4)).
/boot/kernel/ng_gif.ko The ng_gif netgraph node type allows gif(4) interfaces to interact with the netgraph(4) networking subsystem. Once the ng_gif module is loaded in the kernel, a node is automatically created for each gif(4) interface in the system.
/boot/kernel/ng_gif_demux.ko The ng_gif_demux netgraph node type demultiplexes the output from ng_gif(4) nodes in the netgraph(4) networking subsystem.
/boot/kernel/ng_hci.ko The hci node type is a Netgraph node type that implements Bluetooth Host Controller Interface (HCI) layer as per chapter H1 of the Bluetooth Specification Book v1.1.
/boot/kernel/ng_hole.ko The hole node type silently discards all data and control messages it receives. This type is used for testing and debugging.
/boot/kernel/ng_hub.ko The hub node type provides a simple mechanism for distributing packets over several links. Packets received on any of the hooks are forwarded out the other hooks. Packets are not altered in any way.
/boot/kernel/ng_iface.ko An iface node is both a netgraph node and a system networking interface. When an iface node is created, a new interface appears which is accessi ble via ifconfig(8). Iface node interfaces are named ng0, ng1, etc. When a node is shutdown, the corresponding interface is removed and the interface name becomes available for reuse by future iface nodes; new nodes always take the first unused interface. The node itself is assigned the same name as its interface, unless the name already exists, in which case the node remains unnamed.
/boot/kernel/ng_ip_input.ko The ip_input node type takes all received packets and queues them into the IP in input processing subsystem.
/boot/kernel/ng_ipfw.ko The ipfw node implements interface between ipfw(4) and netgraph(4) subsystems.
/boot/kernel/ng_ksocket.ko A ksocket node is both a netgraph node and a BSD socket. The ng_ksocket node type allows one to open a socket inside the kernel and have it appear as a Netgraph node.
/boot/kernel/ng_l2cap.ko ng_l2cap -- Netgraph node type that implements Bluetooth Logical Link Control and Adaptation Protocol (L2CAP)
/boot/kernel/ng_l2tp.ko The l2tp node type implements the encapsulation layer of the L2TP protocol as described in RFC 2661. This includes adding the L2TP packet header for outgoing packets and verifying and removing it for incoming packets.
/boot/kernel/ng_lmi.ko The lmi node type performs the frame relay LMI protocol. It supports the ITU Annex A, ANSI Annex D, and Group-of-four LMI types. It also supports auto-detection of the LMI type.
/boot/kernel/ng_mppc.ko The mppc node type implements the Microsoft Point-to-Point Compression (MPPC) and Microsoft Point-to-Point Encryption (MPPE) sub-protocols of the PPP protocol. These protocols are often used in conjunction with the Point-to-Point Tunneling Protocol (PPTP).
/boot/kernel/ng_nat.ko An ng_nat node performs network address translation (NAT) of packets passing through it. A nat node uses libalias(3) engine for packet aliasing.
/boot/kernel/ng_netflow.ko The ng_netflow node implements Cisco's NetFlow export protocol on a router running FreeBSD. The ng_netflow node listens for incoming traffic and identifies unique flows in it.
/boot/kernel/ng_one2many.ko The one2many provides a simple mechanism for routing packets over several links in a one-to-many (and in the reverse direction, many-to-one) fashion.
/boot/kernel/ng_patch.ko The patch node performs data modification of packets passing through it. Modifications are restricted to a subset of C language operations on unsigned integers of 8, 16, 32 or 64 bit size.
/boot/kernel/ng_pipe.ko kernel netgraph code; This node permits simple traffic shaping by emulating bandwidth

and delay, as well as random packet losses. The node has two hooks, upper and lower. Traffic flowing from upper to lower hook is referenced as downstream, and vice versa. Parameters for both directions can be set separately, except for delay.

/boot/kernel/ng_ppp.ko The ppp node type performs multiplexing for the PPP protocol. It handles only packets that contain data, and forwards protocol negotiation and control packets to a separate controlling entity (e.g., a user-land daemon).
/boot/kernel/ng_pppoe.ko kernel netgraph code; States for the session state machine. These have no meaning if there is no hook attached yet.
/boot/kernel/ng_pptpgre.ko The pptpgre node type performs Generic Routing Encapsulation (GRE) over IP for the PPTP protocol as specified by RFC 2637.
/boot/kernel/ng_pred1.ko The pred1 node type implements the Predictor-1 sub-protocols of the Compression Control Protocol (CCP).
/boot/kernel/ng_rfc1490.ko The rfc1490 node type performs protocol encapsulation, deencapsulation, and multiplexing according to RFC 1490 (which has since been updated by RFC 2427). This particular type of encapsulation is often used on top of frame relay DLCI channels.
/boot/kernel/ng_socket.ko A socket node is both a BSD socket and a netgraph node. The ng_socket node type allows user-mode processes to participate in the kernel netgraph(4) networking subsystem using the BSD socket interface.
/boot/kernel/ng_source.ko The source node acts as a source of packets according to the parameters set up using control messages and input packets. The ng_source node type is used primarily for testing and benchmarking.
/boot/kernel/ng_split.ko The split node type is used to split a bidirectional stream of packets into two separate unidirectional streams of packets.
/boot/kernel/ng_sppp.ko An sppp node is a netgraph(4) interface to the original sppp(4) network module for synchronous lines.
/boot/kernel/ng_sscfu.ko The sscfu netgraph node type implements ITU-T recommendation Q.2130. This recommendation specifies the Service Specific Coordination Function at the UNI.
/boot/kernel/ng_sscop.ko The sscop netgraph node type implements the ITU-T standard Q.2110. This standard describes the so called Service Specific Connection Oriented Protocol (SSCOP) that is used to carry signalling messages over the private and public UNIs and the public NNI.
/boot/kernel/ng_tag.ko The tag node type allows mbuf packet tags (see mbuf_tags(9)) to be examined, stripped or applied to data travelling through a Netgraph network.
/boot/kernel/ng_tcpmss.ko The tcpmss node type is designed to alter the Maximum Segment Size option of TCP packets. This node accepts an arbitrary number of hooks
/boot/kernel/ng_tee.ko The tee node type has a purpose similar to the tee(1) command. Tee nodes are useful for debugging or "snooping" on a connection between two netgraph nodes.
/boot/kernel/ng_tty.ko The tty node type is both a netgraph node type and a TTY hook.
/boot/kernel/ng_ubt.ko Netgraph node type that is also a driver for Bluetooth USB devices
/boot/kernel/ng_UI.ko The UI node type has two hooks, upstream and downstream. Packets received on downstream must have 0x03 (indicating unnumbered information) as their first byte; if not the packet is dropped.
/boot/kernel/ng_uni.ko The uni netgraph node type implements ATM Forum signalling 4.0.
/boot/kernel/ng_vjc.ko The vjc node type performs Van Jacobson compression, which is used over PPP, SLIP, and other point-to-point IP connections to compress TCP packet headers.
/boot/kernel/ng_vlan.ko The vlan node type multiplexes frames tagged according to the IEEE 802.1Q standard between different hooks.
/boot/kernel/ngatmbase.ko netgraph ATM utility module
/boot/kernel/nmdm.ko The nmdm driver provides two tty(4) devices connected by a virtual "nullmodem" cable.
/boot/kernel/ntb.ko Non-Transparent Bridge subsystem
/boot/kernel/ntb_hw_amd.ko
/boot/kernel/ntb_hw_intel.ko Intel(R) Non-Transparent Bridge driver
/boot/kernel/ntb_hw_plx.ko PLX/Avago/Broadcom Non-Transparent Bridge driver
/boot/kernel/ntb_transport.ko Packet-oriented transport for Non-Transparent Bridges
/boot/kernel/nullfs.ko The nullfs driver will permit the FreeBSD kernel to mount a loopback file system sub-tree.
/boot/kernel/nvd.ko The nvd driver exposes NVM Express (NVMe) namespaces as disks to the kernel disk storage API.
/boot/kernel/nvdimm.ko The nvdimm driver provides access to Non-Volatile DIMM (NVDIMM) persistent memory devices, which are ACPI-enumerated under the root NVDIMM device with a _HID of ACPI0012 and in the NFIT table.
/boot/kernel/nvme.ko NVM Express core driver
/boot/kernel/nvram.ko The nvram driver provides access to BIOS configuration NVRAM on i386 and amd64 systems.
/boot/kernel/nxprtc.ko
/boot/kernel/ocs_fc.ko Device driver for Emulex Fibre Channel Host Adapters
/boot/kernel/ohci.ko The ohci driver provides support for OHCI-type PCI based USB controllers.
/boot/kernel/opensolaris.ko
/boot/kernel/otusfw_init.ko
/boot/kernel/otusfw_main.ko
/boot/kernel/ow.ko OWFS library access commands for Tcl
/boot/kernel/ow_temp.ko The ow_temp module supports many of the 1-Wire temperature sensors.
/boot/kernel/owc.ko Dallas Semiconductor 1-Wire Controller
/boot/kernel/padlock.ko driver for the cryptographic functions and RNG in VIA C3, C7 and Eden processors
/boot/kernel/padlock_rng.ko
/boot/kernel/pccard.ko The pccard driver implements the PC Card bus. The pccard driver supports all PC Card bridges in the system.
/boot/kernel/pcf.ko Philips I2C bus controller
/boot/kernel/pf.ko Packet filtering takes place in the kernel. A pseudo-device, /dev/pf, allows userland processes to control the behavior of the packet filter through an ioctl(2) interface.
/boot/kernel/pflog.ko packet filter logging interface
/boot/kernel/pfsync.ko The pfsync interface is a pseudo-device which exposes certain changes to the state table used by pf(4).
/boot/kernel/plasma_saver.ko
/boot/kernel/plip.ko printer port Internet Protocol driver
/boot/kernel/pmspcv.ko PMC-Sierra PM8001/8081/8088/8089/8074/8076/8077 SAS/SATA HBA Controller driver
/boot/kernel/ppbus.ko Parallel Port Bus system
/boot/kernel/ppc.ko architecture independent PowerPC platform emulator capable of running most PowerPC operating systems.
/boot/kernel/ppi.ko The ppi driver provides a convenient means for user applications to manipulate the state of the parallel port, enabling easy low-speed I/O operations without the security problems inherent with the use of the

/dev/io interface.

/boot/kernel/pps.ko
/boot/kernel/procfs.ko The process file system, or procfs, implements a view of the system process table inside the file system. It is normally mounted on /proc.
/boot/kernel/profile.ko
/boot/kernel/proto.ko Rdproto reads and interprets the named proto file relative to the root directory root.
/boot/kernel/prototype.ko
/boot/kernel/pseudofs.ko The pseudofs module offers an abstract API for pseudo-file systems such as procfs(5) and linprocfs(5). It takes care of all the hairy bits like interfacing with the VFS system, enforcing access control, keeping track of file numbers, and cloning files and directories that are process-specific.
/boot/kernel/pty.ko Pty is a tool to help debug console programs which take the terminal out of canonical mode, by allowing the program being debugged and the debugger to run on separate terminal devices.
/boot/kernel/puc.ko PCI "Universal" Communications driver
/boot/kernel/pwmbus.ko The PWMBUS (Pulse-Width Modulation) interface allows a device driver to register to a global bus so other devices in the kernel can use them in a generic way.
/boot/kernel/pwmc.ko PWM (Pulse Width Modulation) control device driver
/boot/kernel/r128.ko ATI Rage 128 video driver
/boot/kernel/radeonkms.ko AMD based GPUs are also supported using the drm-kmod port or package. There are two separate modules available for AMD devices based on their generation. The modules are named: amdgpu and radeonkms
/boot/kernel/radeonkmsfw_ARUBA_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_ARUBA_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_ARUBA_rlc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_BARTS_mc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_BARTS_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_BARTS_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_BTC_rlc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_CAICOS_mc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_CAICOS_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_CAICOS_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_CAYMAN_mc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_CAYMAN_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_CAYMAN_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_CAYMAN_rlc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_CEDAR_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_CEDAR_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_CEDAR_rlc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_CYPRESS_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_CYPRESS_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_CYPRESS_rlc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_JUNIPER_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_JUNIPER_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_JUNIPER_rlc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_PALM_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_PALM_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_PITCAIRN_ce.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_PITCAIRN_mc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_PITCAIRN_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_PITCAIRN_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_PITCAIRN_rlc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_R100_cp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_R200_cp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_R300_cp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_R420_cp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_R520_cp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_R600_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_R600_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_R600_rlc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_R700_rlc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_REDWOOD_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_REDWOOD_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_REDWOOD_rlc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RS600_cp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RS690_cp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RS780_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RS780_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV610_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV610_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV620_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV620_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV630_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV630_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV635_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV635_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV670_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV670_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV710_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV710_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV730_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV730_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV770_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_RV770_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_SUMO2_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_SUMO2_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_SUMO_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_SUMO_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_SUMO_rlc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_TAHITI_ce.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_TAHITI_mc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_TAHITI_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_TAHITI_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_TAHITI_rlc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_TURKS_mc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_TURKS_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_TURKS_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_VERDE_ce.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_VERDE_mc.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_VERDE_me.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_VERDE_pfp.ko AMD based GPU driver
/boot/kernel/radeonkmsfw_VERDE_rlc.ko AMD based GPU driver
/boot/kernel/rain_saver.ko Draws a shower on the screen.
/boot/kernel/random_fortuna.ko The random device returns an endless supply of random bytes when read. It also accepts and reads data as any ordinary file.
/boot/kernel/random_OTHER.ko The random device returns an endless supply of random bytes when read. It also accepts and reads data as any ordinary file.
/boot/kernel/rc4.ko This library implements the Alleged RC4 cipher, which is described for example in Applied Cryptography. It is believed to be compatible with RC4[TM], a proprietary cipher of RSA Security Inc.
/boot/kernel/rdrand_rng.ko RDRAND is an instruction for returning random numbers from an Intel on-chip hardware.
/boot/kernel/rsu-rtl8712fw.ko Realtek RTL8188SU/RTL8192SU USB IEEE 802.11b/g/n wireless network device
/boot/kernel/rt2561fw.ko Ralink Technology RT2561, RT2561S and RT2661 chipset driver
/boot/kernel/rt2561sfw.ko Ralink Technology RT2561, RT2561S and RT2661 chipset driver
/boot/kernel/rt2661fw.ko Ralink Technology RT2561, RT2561S and RT2661 chipset driver
/boot/kernel/rt2860fw.ko Ralink Technology RT2561, RT2561S and RT2661 chipset driver
/boot/kernel/rtc8583.ko Driver for realtime clock EPSON RTC-8583
/boot/kernel/rtwn.ko Realtek IEEE 802.11 wireless network driver
/boot/kernel/rtwn-rtl8188eefw.ko Firmware Module for Realtek Wireless driver
/boot/kernel/rtwn-rtl8188eufw.ko Firmware Module for Realtek Wireless driver
/boot/kernel/rtwn-rtl8192cfwE.ko Firmware Module for Realtek Wireless driver
/boot/kernel/rtwn-rtl8192cfwE_B.ko Firmware Module for Realtek Wireless driver
/boot/kernel/rtwn-rtl8192cfwT.ko Firmware Module for Realtek Wireless driver
/boot/kernel/rtwn-rtl8192cfwU.ko Firmware Module for Realtek Wireless driver
/boot/kernel/rtwn-rtl8192eufw.ko Firmware Module for Realtek Wireless driver
/boot/kernel/rtwn-rtl8812aufw.ko Firmware Module for Realtek Wireless driver
/boot/kernel/rtwn-rtl8821aufw.ko Firmware Module for Realtek Wireless driver
/boot/kernel/runfw.ko This module provides firmware sets for the Ralink RT2700U, RT2800U, RT3000U and RT3900E chip based USB WiFi adapters. Please read Ralink's license, src/sys/contrib/dev/run/LICENSE.
/boot/kernel/s3.ko S3 video driver
/boot/kernel/s35390a.ko Driver for Seiko Instruments S-35390A Real-time Clock
/boot/kernel/safe.ko The safe driver supports cards containing SafeNet crypto accelerator chips.
/boot/kernel/savage.ko S3 Savage video driver
/boot/kernel/sbp.ko Serial Bus Protocol 2 (SBP-2) Mass Storage Devices driver, The sbp driver provides support for SBP-2 devices that attach to the FireWire (IEEE 1394) port. It should work with SBP-2 devices which the CAM layer supports, for example, HDDs, CDROM drives and DVD drives.
/boot/kernel/sbp_targ.ko The sbp_targ driver provides support for SBP-2 target mode. This driver is supposed to work with cam(4), targ(4) and firewire(4). You also need to use scsi_target(8), which can be found in /usr/share/examples/scsi_target, to provide actual devices.
/boot/kernel/scc.ko driver for Serial Communications Controllers (SCC) devices
/boot/kernel/scsi_low.ko Common Access Method Storage subsystem
/boot/kernel/sdhci.ko PCI SD Host Controller bridge driver
/boot/kernel/sdhci_acpi.ko
/boot/kernel/sdhci_pci.ko
/boot/kernel/sdt.ko
/boot/kernel/sem.ko semaphore for executing shell command lines in parallel
/boot/kernel/send.ko Send will cause each of the specified files to be delivered to each of the destinations in the "To:", "cc:", "Bcc:", "Dcc:", and "Fcc:" fields of the message.
/boot/kernel/sfxge.ko Solarflare 10Gb Ethernet adapter driver
/boot/kernel/sgx.ko
/boot/kernel/sgx_linux.ko
/boot/kernel/siba.ko Sonic Inc. Silicon Backplane driver, The siba driver provides bhnd(4) support for devices based on the Sonic Inc. Silicon Backplane, an interblock communications architecture found in earlier Broadcom Home Networking Division wireless chipsets and embed ded systems.
/boot/kernel/siba_bhndb.ko Sonic Inc. Silicon Backplane driver, The siba driver provides bhnd(4) support for devices based on the Sonic Inc. Silicon Backplane, an interblock communications architecture found in earlier Broadcom Home Networking Division wireless chipsets and embed ded systems.
/boot/kernel/siftr.ko Statistical Information For TCP Research
/boot/kernel/siis.ko SiliconImage Serial ATA Host Controller driver
/boot/kernel/sis.ko SiS 900, SiS 7016 and NS DP83815/DP83816 Fast Ethernet device driver
/boot/kernel/smartpqi.ko The smartpqi SCSI driver provides support for the new generation of PQI controllers from Microsemi. The smartpqi driver is the first SCSI driver to implement the PQI queuing model.
/boot/kernel/smb.ko The smb character device driver provides generic I/O to any smbus(4) instance. To control SMB devices, use /dev/smb? with the ioctls described below. Any of these ioctl commands takes a pointer to struct smbcmd as its argument.
/boot/kernel/smbfs.ko
/boot/kernel/smbios.ko
/boot/kernel/smbus.ko System Management Bus
/boot/kernel/snake_saver.ko Draws a snake of string.
/boot/kernel/snd_ad1816.ko The snd_ad1816 bridge driver allows the generic audio driver sound(4) to attach to the AD1816 sound card.
/boot/kernel/snd_als4000.ko The snd_als4000 bridge driver allows the generic audio driver sound(4) to attach to the ALS4000 sound card.
/boot/kernel/snd_atiixp.ko The snd_atiixp bridge driver allows the generic audio driver, sound(4), to attach to ATI IXP audio devices. This driver supports 16bit playback and recording, and 32bit native playback and recording.
/boot/kernel/snd_cmi.ko The snd_cmi bridge driver allows the generic audio driver sound(4) to attach to the CMedia CMI8338/CMI8738 audio cards.
/boot/kernel/snd_cs4281.ko The snd_cs4281 bridge driver allows the generic audio driver sound(4) to attach to the CS4281 sound card.
/boot/kernel/snd_csa.ko The snd_csa bridge driver allows the generic audio driver sound(4) to attach to Crystal Semiconductor CS461x/462x/4280 based sound cards.
/boot/kernel/snd_driver.ko This is a metadriver which loads all of the most common sound drivers and can be used to speed up the search for the correct driver. It is also possible to load all sound drivers by adding the metadriver to /boot/loader.conf.
/boot/kernel/snd_ds1.ko The snd_ds1 bridge driver allows the generic audio driver sound(4) to attach to the Yamaha DS-1 sound card.
/boot/kernel/snd_emu10k1.ko The snd_emu10k1 bridge driver allows the generic audio driver sound(4) to attach to the SoundBlaster Live! and Audigy audio cards.
/boot/kernel/snd_emu10kx.ko The snd_emu10kx bridge driver allows the generic audio driver sound(4) to attach to Creative sound cards based on the EMU10K1, CA0100, CA0101, CA0102 and CA0108 DSPs.
/boot/kernel/snd_envy24.ko The snd_envy24 bridge driver allows the generic audio driver sound(4) to attach to VIA Envy24 (ICE1724 or VT1724 chipset) and compatible audio devices.
/boot/kernel/snd_envy24ht.ko The snd_envy24ht bridge driver allows the generic audio driver sound(4) to attach to VIA Envy24HT (ICE1724 or VT1724 chipset) and compatible audio devices.
/boot/kernel/snd_es137x.ko The snd_es137x bridge driver allows the generic audio driver sound(4) to attach to the Ensoniq 137x audio cards.
/boot/kernel/snd_ess.ko The snd_ess bridge driver allows the generic audio driver sound(4) to attach to the ESS ISA sound cards.
/boot/kernel/snd_fm801.ko Forte Media FM801 bridge device driver
/boot/kernel/snd_hda.ko The High Definition (HD) Audio specification was developed by Intel as the logical successor of the old AC'97 specification and has several advantages, such as higher bandwidth which allows more channels and more detailed formats, support for several logical audio devices, and general purpose DMA channels.
/boot/kernel/snd_hdspe.ko The snd_hdspe bridge driver allows the generic audio driver sound(4) to attach to RME HDSPe audio devices.
/boot/kernel/snd_ich.ko Intel ICH AC'97 and compatible bridge device driver
/boot/kernel/snd_maestro.ko The snd_maestro bridge driver allows the generic audio driver sound(4) to attach to ESS Maestro based sound chips. This chipset is very popular in notebook computers, but it is also very used in a wide selection of cheap OEM sound cards.
/boot/kernel/snd_maestro3.ko The snd_maestro3 driver provides support for the ESS Maestro3 and Allegro-1 sound chips under the PCM framework. These chips are mostly found in laptop computers and feature an AC97 mixer, a multi-channel sample rate converter that can mix up to four digital audio streams in hardware, recording support, and external volume control buttons.
/boot/kernel/snd_mss.ko Microsoft Sound System ISA PnP/non-PnP bridge device driver
/boot/kernel/snd_neomagic.ko The snd_neomagic bridge driver allows the generic audio driver, sound(4), to attach to the NeoMagic 256AV/ZX audio devices. These chips are mostly found in laptop computers.
/boot/kernel/snd_sb8.ko snd_sbc, snd_sb16, snd_sb8 -- Creative Sound Blaster ISA and compatible bridge device driver
/boot/kernel/snd_sb16.ko snd_sbc, snd_sb16, snd_sb8 -- Creative Sound Blaster ISA and compatible bridge device driver
/boot/kernel/snd_sbc.ko snd_sbc, snd_sb16, snd_sb8 -- Creative Sound Blaster ISA and compatible bridge device driver
/boot/kernel/snd_solo.ko The snd_solo bridge driver allows the generic audio driver sound(4) to attach to the ESS Solo-1x PCI cards.
/boot/kernel/snd_spicds.ko The snd_spicds I2S codec driver is used by several sound drivers for soundcards which use the supported codec chips.
/boot/kernel/snd_t4dwave.ko Trident 4DWave bridge device driver
/boot/kernel/snd_uaudio.ko USB audio and MIDI device driver
/boot/kernel/snd_via82c686.ko The snd_via82c686 bridge driver allows the generic audio driver, sound(4), to attach audio devices based on the VIA 82C686A chipset.
/boot/kernel/snd_via8233.ko The snd_via8233 bridge driver allows the generic audio driver, sound(4), to attach to the VIA VT8233 audio devices. These audio chipsets are integrated in the southbridge on many VIA based motherboards.
/boot/kernel/snd_vibes.ko The snd_vibes bridge driver allows the generic audio driver, sound(4), to attach audio devices based on the S3 SonicVibes chipset.
/boot/kernel/snp.ko /dev/snp is a snoop device which allows users to attach to any tty and watch activities on it. The kernel must be compiled with device snp, or the snp module must be loaded, for these devices to be available.
/boot/kernel/sound.ko The sound driver is the main component of the FreeBSD sound system. It works in conjunction with a bridge device driver on supported devices and provides PCM audio record and playback once it attaches. Each bridge device driver supports a specific set of audio chipsets and needs to be enabled together with the sound driver. PCI and ISA PnP audio devices identify themselves so users are usually not required to add anything to /boot/device.hints.
/boot/kernel/speaker.ko The speaker device driver allows applications to control the PC console speaker on an IBM-PC--compatible machine running FreeBSD.
/boot/kernel/spibus.ko
/boot/kernel/spigen.ko The spigen driver provides direct access to a slave device on the SPI bus.
/boot/kernel/splash_bmp.ko The splash pseudo device driver adds support for the splash screen and screen savers to the kernel. This driver is required if the splash bitmap image is to be loaded or any screen saver is to be used.
/boot/kernel/splash_pcx.ko The splash pseudo device driver adds support for the splash screen and screen savers to the kernel. This driver is required if the splash bitmap image is to be loaded or any screen saver is to be used.
/boot/kernel/splash_txt.ko The splash pseudo device driver adds support for the splash screen and screen savers to the kernel. This driver is required if the splash bitmap image is to be loaded or any screen saver is to be used.
/boot/kernel/sppp.ko The sppp network layer implements the state machine and the Link Control Protocol (LCP) of the point to point protocol (PPP) as described in RFC 1661.
/boot/kernel/star_saver.ko Twinkling stars.
/boot/kernel/superio.ko
/boot/kernel/sym.ko NCR/Symbios/LSI Logic 53C8XX PCI SCSI host adapter driver
/boot/kernel/systrace.ko Systrace is a computer security utility which limits an application's access to the system by enforcing access policies for system calls. This can mitigate the effects of buffer overflows and other security vulnerabilities. It was developed by Niels Provos and runs on various Unix-like operating systems.
/boot/kernel/systrace_freebsd32.ko Systrace is a computer security utility which limits an application's access to the system by enforcing access policies for system calls. This can mitigate the effects of buffer overflows and other security vulnerabilities. It was developed by Niels Provos and runs on various Unix-like operating systems.
/boot/kernel/systrace_linux.ko Systrace is a computer security utility which limits an application's access to the system by enforcing access policies for system calls. This can mitigate the effects of buffer overflows and other security vulnerabilities. It was developed by Niels Provos and runs on various Unix-like operating systems.
/boot/kernel/systrace_linux32.ko Systrace is a computer security utility which limits an application's access to the system by enforcing access policies for system calls. This can mitigate the effects of buffer overflows and other security vulnerabilities. It was developed by Niels Provos and runs on various Unix-like operating systems.
/boot/kernel/sysvmsg.ko ncludes support for AT&T System V UNIX style message queues
/boot/kernel/sysvsem.ko The options SYSVSHM and SYSVSEM need to be enabled when the kernel is compiled. (They are by default.) The maximum size of shared memory is determined by the option SHMMAXPGS (in pages).
/boot/kernel/sysvshm.ko The options SYSVSHM and SYSVSEM need to be enabled when the kernel is compiled. (They are by default.) The maximum size of shared memory is determined by the option SHMMAXPGS (in pages).
/boot/kernel/t4_tom.ko [13]
/boot/kernel/t4fw_cfg.ko [14]
/boot/kernel/t5fw_cfg.ko [15]
/boot/kernel/t6fw_cfg.ko [16]
/boot/kernel/tcpmd5.ko [17], [18]
/boot/kernel/tdfx.ko Voodoo Graphics and VoodooII Memory Access GLIDE device driver
/boot/kernel/tmpfs.ko The tmpfs driver implements an in-memory, or tmpfs file system. The filesystem stores both file metadata and data in main memory.
/boot/kernel/toecore.ko
/boot/kernel/tpm.ko The tpm driver provides support for various trusted platform modules (TPM) that can store cryptographic keys.
/boot/kernel/trm.ko Tekram TRM-S1040 ASIC based PCI SCSI host adapter driver
/boot/kernel/twa.ko The twa driver provides support for AMCC's 3ware 9000/9500/9550/9650 series SATA controllers.
/boot/kernel/twe.ko The twe driver provides support for AMCC's 3ware 5000/6000/7000/8000 series PATA/SATA RAID adapters. These adapters were formerly known as "3ware Escalade". These devices support 2, 4, 8, or 12 ATA disk drives and provide RAID0 (striping) and RAID1 (mirroring) functionality.
/boot/kernel/tws.ko The tws driver provides support for LSI's 3ware 9750 SATA+SAS 6Gb/s RAID controller cards. These controllers feature the LSISAS2108 6Gb/s SAS RAID-on-Chip (ROC) and are available in 4- and 8-port configurations, supports RAID levels 0, 1, 5, 6, 10, 50 and single disk, with 96 SATA and/or SAS hard drives and SSDs.
/boot/kernel/u3g.ko The u3g driver provides support for the multiple USB-to-serial interfaces exposed by many 3G USB/PCCard modems.
/boot/kernel/uart.ko driver for Universal Asynchronous Receiver/Transmitter (UART) devices
/boot/kernel/ubsa.ko The ubsa driver provides support for the USB-to-RS232 Bridge chip used by a variety of serial adapters from Belkin and other vendors.
/boot/kernel/ubsec.ko Broadcom and BlueSteel uBsec 5x0x crypto accelerator
/boot/kernel/ubser.ko USB support for BWCT console serial adapters
/boot/kernel/ubtbcmfw.ko Firmware driver for Broadcom BCM2033 chip based Bluetooth USB devices
WinChipHead CH341/CH340 serial adapter driver|
/boot/kernel/ucom.ko USB tty support
/boot/kernel/ucycom.ko device driver for Cypress CY7C63743 and CY7C64013 USB to RS232 bridges
/boot/kernel/udbp.ko USB Double Bulk Pipe driver
/boot/kernel/udf.ko Universal Disk Format
/boot/kernel/udf_iconv.ko Universal Disk Format
/boot/kernel/udl.ko DisplayLink DL-120 / DL-160 USB display devices
/boot/kernel/uep.ko eGalax touchscreen driver
/boot/kernel/uether.ko
/boot/kernel/ufm.ko USB driver for Cypress Semiconductor FM Radio
/boot/kernel/ufoma.ko The ufoma driver provides support for USB mobile phone terminals in the subset of the Mobile Computing Promotion Consortium USB Implementation Guideline, which is adopted by FOMA, the NTT DoCoMo 3G system, terminal.
/boot/kernel/ufs.ko
/boot/kernel/uftdi.ko USB support for serial adapters based on the FTDI family of USB serial adapter chips.
/boot/kernel/ugensa.ko
/boot/kernel/ugold.ko TEMPer gold HID thermometer
/boot/kernel/uhci.ko UHCI USB Host Controller driver
/boot/kernel/uhid.ko USB generic HID support
/boot/kernel/uhid_snes.ko
/boot/kernel/uhso.ko support for several HSxPA devices from Option N.V.
/boot/kernel/uinput.ko
/boot/kernel/uipaq.ko The uipaq driver provides support for the USB serial emulation provided by the iPAQ devices.
/boot/kernel/ukbd.ko USB keyboard driver
/boot/kernel/uled.ko USB LED driver
/boot/kernel/ulpt.ko USB printer support
/boot/kernel/umass.ko The umass driver provides support for Mass Storage devices that attach to the USB port.
/boot/kernel/umcs.ko USB support for serial adapters based on the MCS7820 and MCS7840 chips
/boot/kernel/umct.ko The umct driver provides support for USB to RS-232 converters based on the Magic Control Technology USB-232 design. These devices support most of the standard RS-232 features including baud rates ranging from 300 to 115200 bits per second.
/boot/kernel/umodem.ko USB Communication Device Class serial (CDC ACM) driver
/boot/kernel/umoscom.ko USB support for serial adapters based on chips made by MOSCHIP
/boot/kernel/ums.ko USB mouse driver
/boot/kernel/unionfs.ko A userspace unionfs implementation
/boot/kernel/uplcom.ko USB support for Prolific PL-2303/2303X/2303HX serial adapters driver
/boot/kernel/urio.ko USB driver for the Rio MP3 players
/boot/kernel/usb.ko The libusb library contains interfaces for directly managing a usb device. The current implementation supports v1.0 of the libusb API.
/boot/kernel/usb_template.ko USB device side templates
/boot/kernel/usfs.ko USB device side support for bulk only transport mass storage
/boot/kernel/usie.ko
/boot/kernel/uslcom.ko Silicon Laboratories CP2101/CP2102/CP2103/CP2104/CP2105 based USB serial adapter
/boot/kernel/uvisor.ko USB support for the PalmOS based PDAs
/boot/kernel/uvscom.ko USB support for SUNTAC Slipper U VS-10U serial adapters driver
/boot/kernel/vesa.ko vesa is an Xorg driver for generic VESA video cards. It can drive most VESA-compatible video cards, but only makes use of the basic standard VESA core that is common to these cards. The driver supports depths 8, 15 16 and 24.
/boot/kernel/via.ko
/boot/kernel/viapm.ko This driver provides access to the VIA chipset Power Management Unit family. They are VT82C586B, VT82C596A, VT82C596B, VT82C686A and VT8233.
/boot/kernel/viawd.ko The viawd driver provides watchdog(4) support for the watchdog interrupt timer present on VIA south bridge chipset (VT8251, CX700, VX800, VX855, VX900).
/boot/kernel/videomode.ko The FreeBSD console default video mode may be adjusted to 1024x768, 1280x1024, or any other size supported by the graphics chip and monitor.
/boot/kernel/virtio.ko VirtIO is a specification for para-virtualized I/O in a virtual machine (VM). Traditionally, the hypervisor emulated real devices such as an Ethernet interface or disk controller to provide the VM with I/O. This emulation is often inefficient.
/boot/kernel/virtio_balloon.ko The virtio_balloon device driver provides support for VirtIO memory balloon devices.
/boot/kernel/virtio_blk.ko VirtIO Block driver
/boot/kernel/virtio_console.ko VirtIO Console driver
/boot/kernel/virtio_pci.ko VirtIO is a specification for para-virtualized I/O in a virtual machine (VM). Traditionally, the hypervisor emulated real devices such as an Ethernet interface or disk controller to provide the VM with I/O. This emulation is often inefficient.
/boot/kernel/virtio_random.ko The virtio_random device driver provides support for VirtIO entropy devices.
/boot/kernel/virtio_scsi.ko The virtio_scsi device driver provides support for VirtIO SCSI devices.
/boot/kernel/vkbd.ko The vkbd interface is a software loopback mechanism that can be loosely described as the virtual AT keyboard analog of the pty(4), that is, vkbd does for virtual AT keyboards what the pty(4) driver does for terminals.
/boot/kernel/vmci.ko vmware kernel module, VMCI allows virtual machines to communicate with host kernel modules and ...
/boot/kernel/vmm.ko vmm.ko provides the kernel portion of the bhyve(4) hypervisor. An Intel CPU with VT-x/EPT or AMD CPU with SVM support is required. PCI device passthrough to a virtual machine requires hardware with VT-d support.
/boot/kernel/vpd.ko
/boot/kernel/vpo.ko The vpo driver provide access to parallel port Iomega Zip and Jaz drives.
/boot/kernel/warp_saver.ko Streaking stars.
/boot/kernel/wbwd.ko device driver for Winbond/Nuvoton Super I/O chips watchdog timer
/boot/kernel/wlan.ko generic 802.11 link-layer support
/boot/kernel/wlan_acl.ko MAC-based ACL support for 802.11 devices
/boot/kernel/wlan_amrr.ko AMRR rate adaptation algorithm support for 802.11 devices
/boot/kernel/wlan_ccmp.ko AES-CCMP crypto support for 802.11 devices
/boot/kernel/wlan_rssadapt.ko
/boot/kernel/wlan_tkip.ko TKIP and Michael crypto support for 802.11 devices
/boot/kernel/wlan_wep.ko WEP crypto support for 802.11 devices
/boot/kernel/wlan_xauth.ko External authenticator support for 802.11 devices
/boot/kernel/wmt.ko MS Windows 7/8/10 - compatible USB HID multi-touch device driver
/boot/kernel/wpifw.ko IPFW is a packet filtering and accounting system which resides in the kernelmode, and has a user-land control utility, ipfw. Together, they allow you to define and query the rules used by the kernel in its routing decisions. WIPFW is a MS Windows operable version of IPFW for FreeBSD OS. You can use the same functionality and configure it as only you work with IPFW.
/boot/kernel/wsp.ko Wellspring touchpad driver
/boot/kernel/x86bios.ko
/boot/kernel/xhci.ko USB eXtensible Host Controller driver
/boot/kernel/xz.ko Compress or decompress .xz and .lzma files
/boot/kernel/zfs.ko configures ZFS file systems
/boot/kernel/zlib.ko compression/decompression library


Back to Icon Disti GhostBSD.png/boot/