Editing Kernel

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
 
{{welcome}}
 
{{welcome}}
 +
{{maintenance}}
 
{{Navbar Kernel Competence}}
 
{{Navbar Kernel Competence}}
  
Line 6: Line 7:
 
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, like driver for wlan, ethernet, bluetooth, sound, file systems... Most of it are not installed by default.<br/>
 
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 in most cases (with few exceptions) 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 always the same:<br/>
 
Take the name of the kernel module, chop of the tailing ''.ko'', also ''/boot/kernel/'' <br/>
 
Take the name of the kernel module, chop of the tailing ''.ko'', also ''/boot/kernel/'' <br/>
 
and add the string ''_load="YES"''.<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/>
 
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]<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]
−
A lot of additional Information you will find [https://github.com/freebsd/freebsd/blob/master/sys/conf/NOTES here]
+
  
 
==Modules==
 
==Modules==
Line 76: 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/[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_cuseeme.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_dummy.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_ftp.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_irc.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_nbt.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_pptp.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_skinny.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/alias_smedia.ko||
 
|-
 
|-
 
|/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 96: 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/[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/amd_ecc_inject.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/amdgpio.ko||
 
|-
 
|-
 
|/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 112: 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/[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_cam.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/amr_linux.ko||
−
 
+
 
|-
 
|-
 
|/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 128: Line 126:
 
|/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/[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/ataacard.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/ataacerlabs.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/ataamd.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/ataati.ko||
 
|-
 
|-
−
|/boot/kernel/[http://euc.jp/beos/atacard.en.html atacard].ko||ATA PC Card Driver
+
|/boot/kernel/atacard.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/atacenatek.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/atacypress.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/atacyrix.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/atahighpoint.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/ataintel.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/ataisa.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/ataite.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/atajmicron.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/atamarvell.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/atamicron.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/atanational.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/atanetcell.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/atanvidia.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/atapci.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/atapromise.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/ataserverworks.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/atasiliconimage.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/atasis.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/atavia.ko||
 
|-
 
|-
 
|/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
Line 180: Line 178:
 
|/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/[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||[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_ar5210.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_ar5211.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_ar5212.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_ar5416.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_hal_ar9300.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_main.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/ath_rate.ko||
 
|-
 
|-
 
|/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 200: Line 198:
 
|/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/[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/bcma_bhndb.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?splash(4) beastie_saver].ko||splash screen / screen saver interface
+
|/boot/kernel/beastie_saver.ko||
 
|-
 
|-
 
|/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/[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.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_pci_hostb.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/bhnd_pcib.ko||
 
|-
 
|-
 
|/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/[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.
+
|/boot/kernel/bhndb_pci.ko||
−
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/[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/bktr_mem.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freshports.org/sysutils/b2sum blake2].ko||The cryptographic hash function BLAKE2 is an improved version of the SHA-3
+
|/boot/kernel/blake2.ko||
−
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/[https://www.freebsd.org/cgi/man.cgi?splash(4) blank_saver].ko||This screen saver simply blanks the screen.
+
|/boot/kernel/blank_saver.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/bridgestp.ko||
 
|-
 
|-
 
|/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/[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/callout_test.ko||
 
|-
 
|-
 
|/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 260: Line 251:
 
|/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/[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/ccp.ko||
 
|-
 
|-
 
|/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 267: Line 258:
 
|/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/[https://github.com/lattera/freebsd/blob/master/sys/fs/cd9660/cd9660_iconv.c cd9660_iconv].ko|| Support for multibyte charsets in LIBICONV.
+
|/boot/kernel/cd9660_iconv.ko||
 
|-
 
|-
 
|/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 303: Line 294:
 
|/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/[https://www.leidinger.net/FreeBSD/dox/dev_cxgbe/html/d1/da6/cxgbei_8h.html cxgbei].ko||CXGBEI_CONN_SIGNATURE 0x56788765
+
|/boot/kernel/cxgbei.ko||
 
|-
 
|-
 
|/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/[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/daemon_saver.ko||
 
|-
 
|-
 
|/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 315: Line 306:
 
|/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/[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/dragon_saver.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/[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||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/drm2.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.leidinger.net/freebsd/dox/dev_iicbus/html/d4/dee/ds13rtc_8c.html ds13rtc].ko||IICBUS device code
+
|/boot/kernel/ds13rtc.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/[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/[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/ds1672.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/[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.
Line 332: Line 323:
 
|/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/[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/[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/dtmalloc.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/dtnfscl.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/[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/[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/dtrace_test.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/dtraceall.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/[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.
Line 356: Line 347:
 
|/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/[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/[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/fade_saver.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/fasttrap.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>
+
|/boot/kernel/fbt.ko||
−
This option provides support for FBT. While DTrace will work without this option, there will be limited support for function boundary tracing.
+
 
|-
 
|-
 
|/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/[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
Line 369: Line 359:
 
|/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/[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/[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/fire_saver.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/[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
Line 460: Line 450:
 
|/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/[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/gpiospi.ko||[https://www.leidinger.net/freebsd/dox/dev_gpio/html/d3/d4c/gpiospi_8c_source.html]
+
|/boot/kernel/gpiospi.ko||
 
|-
 
|-
−
|/boot/kernel/gpioths.ko||[https://www.leidinger.net/freebsd/dox/dev_gpio/html/d7/d0d/gpioths_8c.html]
+
|/boot/kernel/gpioths.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/green_saver.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/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.
Line 495: Line 485:
 
|/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/[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/i915kms.ko||
 
|-
 
|-
−
|/boot/kernel/ibcore.ko||[https://wiki.freebsd.org/InfiniBand]
+
|/boot/kernel/ibcore.ko||
 
|-
 
|-
−
|/boot/kernel/icee.ko||[https://www.leidinger.net/FreeBSD/dox/dev_iicbus/html/de/d92/icee_8c.html]
+
|/boot/kernel/icee.ko||
 
|-
 
|-
 
|/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=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).
Line 527: Line 517:
  
 
|-
 
|-
−
|/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/if_axge.ko||
 
|-
 
|-
 
|/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_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
Line 555: Line 545:
 
|/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/[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/if_cdceem.ko||
 
|-
 
|-
−
|/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/if_cs.ko||
 
|-
 
|-
 
|/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_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
Line 584: Line 574:
 
|/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://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/if_ena.ko||
 
|-
 
|-
 
|/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/[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/if_ep.ko||
 
|-
 
|-
 
|/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_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.
Line 594: Line 584:
 
|/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.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/if_fe.ko||
 
|-
 
|-
 
|/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_fwe&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html if_fwe].ko||Ethernet emulation driver for FireWire
Line 612: Line 602:
 
|/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.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/if_ic.ko||
 
|-
 
|-
 
|/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_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.
Line 632: Line 622:
 
|/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.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/if_ixv.ko||
 
|-
 
|-
 
|/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_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.
Line 806: Line 796:
 
|/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://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/imgact_binmisc.ko||
 
|-
 
|-
−
|/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/intelspi.ko||
 
|-
 
|-
 
|/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=intpm&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html intpm].ko||Intel PIIX4 Power Management controller driver
Line 816: Line 806:
 
|/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://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/ip6_mroute.ko||
 
|-
 
|-
−
|/boot/kernel/[http://troglobit.github.io/howto/mrouting-in-freebsd/ ip_mroute].ko||Multicast Routing to FreeBSD kernel
+
|/boot/kernel/ip_mroute.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?divert(4) ipdivert].ko||kernel packet diversion mechanism
+
|/boot/kernel/ipdivert.ko||
 
|-
 
|-
 
|/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/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/ipfw_nat.ko||
 
|-
 
|-
−
|/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/ipfw_nat64.ko||
 
|-
 
|-
−
|/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/ipfw_nptv6.ko||
 
|-
 
|-
−
|/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/ipfw_pmod.ko||
 
|-
 
|-
 
|/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=ipl&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ipl].ko||IP packet log device
Line 838: Line 828:
  
 
|-
 
|-
−
|/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/ipmi_linux.ko||
 
|-
 
|-
−
|/boot/kernel/[https://github.com/freebsd/freebsd/tree/master/sys/ofed/drivers/infiniband/ulp ipoib].ko||Fix some whitespace issues in ipoib.
+
|/boot/kernel/ipoib.ko||
 
|-
 
|-
 
|/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=ips&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html ips].ko||IBM/Adaptec ServeRAID controller driver
Line 846: Line 836:
 
|/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/[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_bss.ko||
 
|-
 
|-
−
|/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_ibss.ko||
 
|-
 
|-
−
|/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/ipw_monitor.ko||
 
|-
 
|-
 
|/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=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.
Line 863: Line 853:
  
 
|-
 
|-
−
|/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/isl12xx.ko||
 
|-
 
|-
 
|/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=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
Line 870: Line 860:
  
 
|-
 
|-
−
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_1040].ko||ISP Firmware Modules for FreeBSD
+
|/boot/kernel/isp_1040.ko||
 
|-
 
|-
−
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_1080].ko||ISP Firmware Modules for FreeBSD
+
|/boot/kernel/isp_1080.ko||
 
|-
 
|-
−
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_2100].ko||ISP Firmware Modules for FreeBSD
+
|/boot/kernel/isp_2100.ko||
 
|-
 
|-
−
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_2200].ko||ISP Firmware Modules for FreeBSD
+
|/boot/kernel/isp_2200.ko||
 
|-
 
|-
−
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_2300].ko||ISP Firmware Modules for FreeBSD
+
|/boot/kernel/isp_2300.ko||
 
|-
 
|-
−
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_2322].ko||ISP Firmware Modules for FreeBSD
+
|/boot/kernel/isp_2322.ko||
 
|-
 
|-
−
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_2400].ko||ISP Firmware Modules for FreeBSD
+
|/boot/kernel/isp_2400.ko||
 
|-
 
|-
−
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_2500].ko||ISP Firmware Modules for FreeBSD
+
|/boot/kernel/isp_2500.ko||
 
|-
 
|-
−
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/ispfw/ispfw.c isp_12160].ko||ISP Firmware Modules for FreeBSD
+
|/boot/kernel/isp_12160.ko||
 
|-
 
|-
 
|/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://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/iw_cxgbe.ko||
 
|-
 
|-
−
|/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/iwi_bss.ko||
 
|-
 
|-
−
|/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/iwi_ibss.ko||
 
|-
 
|-
−
|/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/iwi_monitor.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iwm&sektion=4 iwm3160fw].ko||Intel IEEE 802.11ac wireless network driver
+
|/boot/kernel/iwm3160fw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iwm&sektion=4 iwm3168fw].ko||Intel IEEE 802.11ac wireless network driver
+
|/boot/kernel/iwm3168fw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iwm&sektion=4 iwm7260fw].ko||Intel IEEE 802.11ac wireless network driver
+
|/boot/kernel/iwm7260fw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iwm&sektion=4 iwm7265Dfw].ko||Intel IEEE 802.11ac wireless network driver
+
|/boot/kernel/iwm7265Dfw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iwm&sektion=4 iwm7265fw].ko||Intel IEEE 802.11ac wireless network driver
+
|/boot/kernel/iwm7265fw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iwm&sektion=4 iwm8000Cfw].ko||Intel IEEE 802.11ac wireless network driver
+
|/boot/kernel/iwm8000Cfw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?query=iwm&sektion=4 iwm8265fw].ko||Intel IEEE 802.11ac wireless network driver
+
|/boot/kernel/iwm8265fw.ko||
 
|-
 
|-
−
|/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/iwm9000fw.ko||
 
|-
 
|-
−
|/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/iwm9260fw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn100fw].ko||Firmware Module for Intel Wireless driver
+
|/boot/kernel/iwn100fw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn105fw].ko||Firmware Module for Intel Wireless driver
+
|/boot/kernel/iwn105fw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn135fw].ko||Firmware Module for Intel Wireless driver
+
|/boot/kernel/iwn135fw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn1000fw].ko||Firmware Module for Intel Wireless driver
+
|/boot/kernel/iwn1000fw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn2000fw].ko||Firmware Module for Intel Wireless driver
+
|/boot/kernel/iwn2000fw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn2030fw].ko||Firmware Module for Intel Wireless driver
+
|/boot/kernel/iwn2030fw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn4965fw].ko||Firmware Module for Intel Wireless driver
+
|/boot/kernel/iwn4965fw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn5000fw].ko||Firmware Module for Intel Wireless driver
+
|/boot/kernel/iwn5000fw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn5150fw].ko||Firmware Module for Intel Wireless driver
+
|/boot/kernel/iwn5150fw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn6000fw].ko||Firmware Module for Intel Wireless driver
+
|/boot/kernel/iwn6000fw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn6000g2afw].ko||Firmware Module for Intel Wireless driver
+
|/boot/kernel/iwn6000g2afw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn6000g2bfw].ko||Firmware Module for Intel Wireless driver
+
|/boot/kernel/iwn6000g2bfw.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/cgi/man.cgi?iwnfw iwn6050fw].ko||Firmware Module for Intel Wireless driver
+
|/boot/kernel/iwn6050fw.ko||
 
|-
 
|-
 
|/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=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.
Line 953: Line 943:
 
|/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://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/kgssapi.ko||
 
|-
 
|-
−
|/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/kgssapi_krb5.ko||
 
|-
 
|-
−
|/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/krpc.ko||
 
|-
 
|-
−
|/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/krping.ko||
 
|-
 
|-
 
|/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=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.
Line 966: Line 956:
  
 
|-
 
|-
−
|/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/libiconv.ko||
 
|-
 
|-
−
|/boot/kernel/libmchain.ko||Supporting function for the common internet file system CIFS and smbfs
+
|/boot/kernel/libmchain.ko||
 
|-
 
|-
−
|/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,
+
|/boot/kernel/linker.hints||
−
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=linprocfs&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html linprocfs].ko||Linux process file system
Line 985: Line 974:
 
|/boot/kernel/linuxkpi.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/logo_saver.ko||
 
|-
 
|-
 
|/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=lpbb&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html lpbb].ko||parallel port I2C bit-banging interface
Line 991: Line 980:
 
|/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://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/ltc430x.ko||
 
|-
 
|-
 
|/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_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.
Line 1,048: Line 1,037:
 
|-
 
|-
 
|/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=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/[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/mlxfw.ko||
 
|-
 
|-
Line 1,100: Line 1,090:
 
|/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/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/nfscl.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/doc/handbook/network-nfs.html nfscommon].ko||Network File System (NFS)
+
|/boot/kernel/nfscommon.ko||
 
|-
 
|-
 
|/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/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/nfslock.ko||
 
|-
 
|-
−
|/boot/kernel/[https://www.freebsd.org/doc/handbook/network-nfs.html nfslockd].ko||Network File System (NFS)
+
|/boot/kernel/nfslockd.ko||
 
|-
 
|-
 
|/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=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.
Line 1,156: Line 1,146:
 
|/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_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/ng_hci.ko||
 
|-
 
|-
−
|/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/ng_hole.ko||
 
|-
 
|-
−
|/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/ng_hub.ko||
 
|-
 
|-
−
|/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/ng_iface.ko||
 
|-
 
|-
−
|/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/ng_ip_input.ko||
−
 
+
 
|-
 
|-
−
|/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/ng_ipfw.ko||
 
|-
 
|-
−
|/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/ng_ksocket.ko||
 
|-
 
|-
−
|/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/ng_l2cap.ko||
−
 
+
 
|-
 
|-
−
|/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/ng_l2tp.ko||
 
|-
 
|-
−
|/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/ng_lmi.ko||
−
 
+
 
|-
 
|-
−
|/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/ng_mppc.ko||
 
|-
 
|-
−
|/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/ng_nat.ko||
 
|-
 
|-
−
|/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/ng_netflow.ko||
 
|-
 
|-
−
|/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/ng_one2many.ko||
 
|-
 
|-
−
|/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/ng_patch.ko||
 
|-
 
|-
−
|/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
+
|/boot/kernel/ng_pipe.ko||
−
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/ng_ppp.ko||
 
|-
 
|-
−
|/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/ng_pppoe.ko||
 
|-
 
|-
−
|/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/ng_pptpgre.ko||
 
|-
 
|-
−
|/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/ng_pred1.ko||
 
|-
 
|-
−
|/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/ng_rfc1490.ko||
−
 
+
 
|-
 
|-
−
|/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/ng_socket.ko||
 
|-
 
|-
−
|/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/ng_source.ko||
 
|-
 
|-
−
|/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/ng_split.ko||
−
 
+
 
|-
 
|-
−
|/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/ng_sppp.ko||
 
|-
 
|-
−
|/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/ng_sscfu.ko||
 
|-
 
|-
−
|/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/ng_sscop.ko||
 
|-
 
|-
−
|/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/ng_tag.ko||
 
|-
 
|-
−
|/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/ng_tcpmss.ko||
 
|-
 
|-
−
|/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/ng_tee.ko||
 
|-
 
|-
−
|/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/ng_tty.ko||
−
 
+
 
|-
 
|-
−
|/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/ng_ubt.ko||
 
|-
 
|-
−
|/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/ng_UI.ko||
 
|-
 
|-
−
|/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/ng_uni.ko||
 
|-
 
|-
−
|/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/ng_vjc.ko||
 
|-
 
|-
−
|/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/ng_vlan.ko||
 
|-
 
|-
−
|/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/ngatmbase.ko||
 
|-
 
|-
−
|/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/nmdm.ko||
 
|-
 
|-
−
|/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.ko||
 
|-
 
|-
 
|/boot/kernel/ntb_hw_amd.ko||
 
|/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/ntb_hw_intel.ko||
−
 
+
 
|-
 
|-
−
|/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/ntb_hw_plx.ko||
−
 
+
 
|-
 
|-
−
|/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/ntb_transport.ko||
 
|-
 
|-
−
|/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/nullfs.ko||
 
|-
 
|-
−
|/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/nvd.ko||
 
|-
 
|-
−
|/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/nvdimm.ko||
 
|-
 
|-
−
|/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/nvme.ko||
−
 
+
 
|-
 
|-
−
|/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/nvram.ko||
 
|-
 
|-
 
|/boot/kernel/nxprtc.ko||
 
|/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/ocs_fc.ko||
 
|-
 
|-
−
|/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/ohci.ko||
−
 
+
 
|-
 
|-
 
|/boot/kernel/opensolaris.ko||
 
|/boot/kernel/opensolaris.ko||
Line 1,275: Line 1,254:
 
|/boot/kernel/otusfw_main.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/ow.ko||
 
|-
 
|-
−
|/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/ow_temp.ko||
−
 
+
 
|-
 
|-
−
|/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/owc.ko||
 
|-
 
|-
−
|/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.ko||
−
 
+
 
|-
 
|-
 
|/boot/kernel/padlock_rng.ko||
 
|/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/pccard.ko||
−
 
+
 
|-
 
|-
−
|/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/pcf.ko||
 
|-
 
|-
−
|/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/pf.ko||
 
|-
 
|-
−
|/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/pflog.ko||
 
|-
 
|-
−
|/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/pfsync.ko||
 
|-
 
|-
 
|/boot/kernel/plasma_saver.ko||
 
|/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/plip.ko||
 
|-
 
|-
−
|/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/pmspcv.ko||
 
|-
 
|-
−
|/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/ppbus.ko||
 
|-
 
|-
−
|/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/ppc.ko||
 
|-
 
|-
−
|/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
+
|/boot/kernel/ppi.ko||
−
/dev/io interface.
+
 
|-
 
|-
 
|/boot/kernel/pps.ko||
 
|/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/procfs.ko||
 
|-
 
|-
 
|/boot/kernel/profile.ko||
 
|/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/proto.ko||
 
|-
 
|-
 
|/boot/kernel/prototype.ko||
 
|/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/pseudofs.ko||
 
|-
 
|-
−
|/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/pty.ko||
 
|-
 
|-
−
|/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/puc.ko||
 
|-
 
|-
−
|/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/pwmbus.ko||
 
|-
 
|-
−
|/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/pwmc.ko||
 
|-
 
|-
−
|/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/r128.ko||
 
|-
 
|-
−
|/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/radeonkms.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_ARUBA_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_ARUBA_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_ARUBA_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_ARUBA_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_ARUBA_rlc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_ARUBA_rlc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_BARTS_mc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_BARTS_mc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_BARTS_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_BARTS_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_BARTS_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_BARTS_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_BTC_rlc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_BTC_rlc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_CAICOS_mc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_CAICOS_mc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_CAICOS_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_CAICOS_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_CAICOS_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_CAICOS_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_CAYMAN_mc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_CAYMAN_mc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_CAYMAN_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_CAYMAN_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_CAYMAN_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_CAYMAN_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_CAYMAN_rlc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_CAYMAN_rlc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_CEDAR_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_CEDAR_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_CEDAR_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_CEDAR_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_CEDAR_rlc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_CEDAR_rlc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_CYPRESS_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_CYPRESS_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_CYPRESS_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_CYPRESS_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_CYPRESS_rlc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_CYPRESS_rlc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_JUNIPER_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_JUNIPER_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_JUNIPER_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_JUNIPER_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_JUNIPER_rlc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_JUNIPER_rlc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_PALM_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_PALM_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_PALM_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_PALM_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_PITCAIRN_ce.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_PITCAIRN_ce.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_PITCAIRN_mc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_PITCAIRN_mc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_PITCAIRN_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_PITCAIRN_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_PITCAIRN_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_PITCAIRN_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_PITCAIRN_rlc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_PITCAIRN_rlc.ko||
  
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_R100_cp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_R100_cp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_R200_cp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_R200_cp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_R300_cp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_R300_cp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_R420_cp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_R420_cp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_R520_cp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_R520_cp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_R600_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_R600_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_R600_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_R600_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_R600_rlc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_R600_rlc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_R700_rlc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_R700_rlc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_REDWOOD_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_REDWOOD_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_REDWOOD_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_REDWOOD_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_REDWOOD_rlc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_REDWOOD_rlc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RS600_cp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RS600_cp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RS690_cp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RS690_cp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RS780_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RS780_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RS780_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RS780_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV610_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV610_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV610_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV610_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV620_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV620_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV620_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV620_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV630_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV630_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV630_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV630_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV635_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV635_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV635_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV635_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV670_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV670_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV670_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV670_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV710_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV710_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV710_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV710_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV730_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV730_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV730_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV730_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV770_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV770_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_RV770_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_RV770_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_SUMO2_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_SUMO2_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_SUMO2_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_SUMO2_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_SUMO_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_SUMO_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_SUMO_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_SUMO_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_SUMO_rlc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_SUMO_rlc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_TAHITI_ce.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_TAHITI_ce.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_TAHITI_mc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_TAHITI_mc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_TAHITI_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_TAHITI_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_TAHITI_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_TAHITI_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_TAHITI_rlc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_TAHITI_rlc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_TURKS_mc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_TURKS_mc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_TURKS_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_TURKS_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_TURKS_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_TURKS_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_VERDE_ce.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_VERDE_ce.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_VERDE_mc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_VERDE_mc.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_VERDE_me.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_VERDE_me.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_VERDE_pfp.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_VERDE_pfp.ko||
 
|-
 
|-
−
|/boot/kernel/radeonkmsfw_VERDE_rlc.ko||AMD based GPU driver
+
|/boot/kernel/radeonkmsfw_VERDE_rlc.ko||
 
|-
 
|-
−
|/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/rain_saver.ko||
 
|-
 
|-
−
|/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/random_fortuna.ko||
 
|-
 
|-
−
|/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/random_OTHER.ko||
 
|-
 
|-
−
|/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/rc4.ko||
 
|-
 
|-
−
|/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/rdrand_rng.ko||
 
|-
 
|-
−
|/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/rsu-rtl8712fw.ko||
 
|-
 
|-
−
|/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/rt2561fw.ko||
 
|-
 
|-
−
|/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/rt2561sfw.ko||
 
|-
 
|-
−
|/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/rt2661fw.ko||
 
|-
 
|-
−
|/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/rt2860fw.ko||
 
|-
 
|-
−
|/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/rtc8583.ko||
 
|-
 
|-
−
|/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/rtwn.ko||
 
|-
 
|-
−
|/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/rtwn-rtl8188eefw.ko||
 
|-
 
|-
−
|/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/rtwn-rtl8188eufw.ko||
 
|-
 
|-
−
|/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/rtwn-rtl8192cfwE.ko||
 
|-
 
|-
−
|/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/rtwn-rtl8192cfwE_B.ko||
 
|-
 
|-
−
|/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/rtwn-rtl8192cfwT.ko||
 
|-
 
|-
−
|/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/rtwn-rtl8192cfwU.ko||
 
|-
 
|-
−
|/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/rtwn-rtl8192eufw.ko||
 
|-
 
|-
−
|/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/rtwn-rtl8812aufw.ko||
 
|-
 
|-
−
|/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/rtwn-rtl8821aufw.ko||
 
|-
 
|-
−
|/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/runfw.ko||
−
 
+
 
|-
 
|-
−
|/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/s3.ko||
 
|-
 
|-
−
|/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/s35390a.ko||
 
|-
 
|-
−
|/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/safe.ko||
 
|-
 
|-
−
|/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/savage.ko||
 
|-
 
|-
−
|/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/sbp.ko||
 
|-
 
|-
−
|/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/sbp_targ.ko||
 
|-
 
|-
−
|/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/scc.ko||
 
|-
 
|-
−
|/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/scsi_low.ko||
 
|-
 
|-
−
|/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/sdhci.ko||
 
|-
 
|-
−
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/dev/sdhci/sdhci_acpi.c sdhci_acpi].ko||
+
|/boot/kernel/sdhci_acpi.ko||
 
|-
 
|-
 
|/boot/kernel/sdhci_pci.ko||
 
|/boot/kernel/sdhci_pci.ko||
Line 1,565: Line 1,539:
 
|/boot/kernel/sdt.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/sem.ko||
−
 
+
 
|-
 
|-
−
|/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/send.ko||
 
|-
 
|-
−
|/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/sfxge.ko||
 
|-
 
|-
 
|/boot/kernel/sgx.ko||
 
|/boot/kernel/sgx.ko||
Line 1,576: Line 1,549:
 
|/boot/kernel/sgx_linux.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.ko||
 
|-
 
|-
−
|/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/siba_bhndb.ko||
 
|-
 
|-
−
|/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/siftr.ko||
 
|-
 
|-
−
|/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/siis.ko||
 
|-
 
|-
−
|/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/sis.ko||
 
|-
 
|-
−
|/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/smartpqi.ko||
 
|-
 
|-
−
|/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/smb.ko||
 
|-
 
|-
 
|/boot/kernel/smbfs.ko||
 
|/boot/kernel/smbfs.ko||
Line 1,594: Line 1,567:
 
|/boot/kernel/smbios.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/smbus.ko||
 
|-
 
|-
−
|/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/snake_saver.ko||
 
|-
 
|-
 
|/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_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.
Line 1,671: Line 1,644:
 
|/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=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/[ttps://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=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.
Line 1,680: Line 1,653:
 
|/boot/kernel/spibus.ko||
 
|/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/spigen.ko||
 
|-
 
|-
−
|/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/splash_bmp.ko||
 
|-
 
|-
−
|/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/splash_pcx.ko||
 
|-
 
|-
−
|/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/splash_txt.ko||
 
|-
 
|-
−
|/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/sppp.ko||
 
|-
 
|-
−
|/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/star_saver.ko||
 
|-
 
|-
 
|/boot/kernel/superio.ko||
 
|/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/sym.ko||
−
 
+
 
|-
 
|-
−
|/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/systrace.ko||
 
|-
 
|-
−
|/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/systrace_freebsd32.ko||
 
|-
 
|-
−
|/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/systrace_linux.ko||
 
|-
 
|-
−
|/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/systrace_linux32.ko||
 
|-
 
|-
−
|/boot/kernel/[https://man.openbsd.org/options sysvmsg].ko||ncludes support for AT&T System V UNIX style message queues
+
|/boot/kernel/sysvmsg.ko||
 
|-
 
|-
−
|/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/sysvsem.ko||
 
|-
 
|-
−
|/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/sysvshm.ko||
 
|-
 
|-
−
|/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/t4_tom.ko||
 
|-
 
|-
−
|/boot/kernel/t4fw_cfg.ko||[https://github.com/freebsd/freebsd/tree/master/sys/dev/cxgbe/firmware]
+
|/boot/kernel/t4fw_cfg.ko||
 
|-
 
|-
−
|/boot/kernel/t5fw_cfg.ko||[https://github.com/freebsd/freebsd/tree/master/sys/dev/cxgbe/firmware]
+
|/boot/kernel/t5fw_cfg.ko||
 
|-
 
|-
−
|/boot/kernel/t6fw_cfg.ko||[https://github.com/freebsd/freebsd/tree/master/sys/dev/cxgbe/firmware]
+
|/boot/kernel/t6fw_cfg.ko||
 
|-
 
|-
−
|/boot/kernel/tcpmd5.ko||[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218907], [https://github.com/BIRD/bird/pull/2/files]
+
|/boot/kernel/tcpmd5.ko||
 
|-
 
|-
−
|/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/tdfx.ko||
−
 
+
 
|-
 
|-
−
|/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/tmpfs.ko||
 
|-
 
|-
−
|/boot/kernel/[https://github.com/freebsd/freebsd/blob/master/sys/netinet/toecore.h toecore].ko||
+
|/boot/kernel/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/tpm.ko||
 
|-
 
|-
−
|/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/trm.ko||
−
 
+
 
|-
 
|-
−
|/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/twa.ko||
−
 
+
 
|-
 
|-
−
|/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/twe.ko||
 
|-
 
|-
−
|/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/tws.ko||
 
|-
 
|-
−
|/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/u3g.ko||
 
|-
 
|-
−
|/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/uart.ko||
−
 
+
 
|-
 
|-
−
|/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/ubsa.ko||
 
|-
 
|-
−
|/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/ubsec.ko||
−
 
+
 
|-
 
|-
−
|/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/ubser.ko||
 
|-
 
|-
−
|/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/ubtbcmfw.ko||
 
|-
 
|-
−
|/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/uchcom.ko||
 
|-
 
|-
−
|/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/ucom.ko||
 
|-
 
|-
−
|/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/ucycom.ko||
 
|-
 
|-
−
|/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/udbp.ko||
 
|-
 
|-
−
|/boot/kernel/udf.ko||Universal Disk Format
+
|/boot/kernel/udf.ko||
 
|-
 
|-
−
|/boot/kernel/udf_iconv.ko||Universal Disk Format
+
|/boot/kernel/udf_iconv.ko||
 
|-
 
|-
−
|/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/udl.ko||
 
|-
 
|-
−
|/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/uep.ko||
 
|-
 
|-
 
|/boot/kernel/uether.ko||
 
|/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/ufm.ko||
 
|-
 
|-
−
|/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/ufoma.ko||
 
|-
 
|-
 
|/boot/kernel/ufs.ko||
 
|/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/uftdi.ko||
 
|-
 
|-
 
|/boot/kernel/ugensa.ko||
 
|/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/ugold.ko||
 
|-
 
|-
−
|/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/uhci.ko||
 
|-
 
|-
−
|/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.ko||
 
|-
 
|-
 
|/boot/kernel/uhid_snes.ko||
 
|/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/uhso.ko||
 
|-
 
|-
 
|/boot/kernel/uinput.ko||
 
|/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/uipaq.ko||
 
|-
 
|-
−
|/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/ukbd.ko||
−
 
+
 
|-
 
|-
−
|/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/uled.ko||
 
|-
 
|-
−
|/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/ulpt.ko||
 
|-
 
|-
−
|/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/umass.ko||
 
|-
 
|-
−
|/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/umcs.ko||
 
|-
 
|-
−
|/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/umct.ko||
 
|-
 
|-
−
|/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/umodem.ko||
 
|-
 
|-
−
|/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/umoscom.ko||
 
|-
 
|-
−
|/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/ums.ko||
 
|-
 
|-
−
|/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/unionfs.ko||
−
 
+
 
|-
 
|-
−
|/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/uplcom.ko||
−
 
+
 
|-
 
|-
−
|/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/urio.ko||
 
|-
 
|-
−
|/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/usb.ko||
−
 
+
 
|-
 
|-
−
|/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/usb_template.ko||
 
|-
 
|-
−
|/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/usfs.ko||
−
 
+
 
|-
 
|-
 
|/boot/kernel/usie.ko||
 
|/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/uslcom.ko||
 
|-
 
|-
−
|/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/uvisor.ko||
 
|-
 
|-
−
|/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/uvscom.ko||
 
|-
 
|-
−
|/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/vesa.ko||
 
|-
 
|-
 
|/boot/kernel/via.ko||
 
|/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/viapm.ko||
 
|-
 
|-
−
|/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/viawd.ko||
 
|-
 
|-
−
|/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/videomode.ko||
 
|-
 
|-
−
|/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/virtio.ko||
 
|-
 
|-
−
|/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/virtio_balloon.ko||
 
|-
 
|-
−
|/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/virtio_blk.ko||
 
|-
 
|-
−
|/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/virtio_console.ko||
 
|-
 
|-
−
|/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/virtio_pci.ko||
 
|-
 
|-
−
|/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/virtio_random.ko||
 
|-
 
|-
−
|/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/virtio_scsi.ko||
−
 
+
 
|-
 
|-
−
|/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/vkbd.ko||
−
 
+
 
|-
 
|-
−
|/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/vmci.ko||
 
|-
 
|-
−
|/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/vmm.ko||
 
|-
 
|-
 
|/boot/kernel/vpd.ko||
 
|/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/vpo.ko||
 
|-
 
|-
−
|/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/warp_saver.ko||
 
|-
 
|-
−
|/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/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&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html wlan].ko ||generic 802.11 link-layer support
Line 1,897: Line 1,857:
 
|/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/[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/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/[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
Line 1,909: Line 1,869:
 
|/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=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/[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
 
|}
 
|}
  

Please note that all contributions to GhostBSD Wiki are considered to be released under the Creative Commons Attribution (see GhostBSD Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel | Editing help (opens in new window)

Templates used on this page:

Retrieved from "http://wiki.ghostbsd.org/index.php/Kernel"