diff --git a/drivers/intel/ixgbe/ixgbe-5.19.6-zc/COPYING b/drivers/intel/ixgbe/ixgbe-5.19.6-zc/COPYING new file mode 100644 index 0000000000..a953f51e90 --- /dev/null +++ b/drivers/intel/ixgbe/ixgbe-5.19.6-zc/COPYING @@ -0,0 +1,319 @@ +GNU GENERAL PUBLIC LICENSE + +Version 2, June 1991 + +Copyright (C) 1989, 1991 Free Software Foundation, Inc. +51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA + +Everyone is permitted to copy and distribute verbatim copies +of this license document, but changing it is not allowed. + +Preamble + +The licenses for most software are designed to take away your freedom to share +and change it. By contrast, the GNU General Public License is intended to +guarantee your freedom to share and change free software--to make sure the +software is free for all its users. This General Public License applies to most +of the Free Software Foundation's software and to any other program whose +authors commit to using it. (Some other Free Software Foundation software is +covered by the GNU Lesser General Public License instead.) You can apply it to +your programs, too. + +When we speak of free software, we are referring to freedom, not price. Our +General Public Licenses are designed to make sure that you have the freedom to +distribute copies of free software (and charge for this service if you wish), +that you receive source code or can get it if you want it, that you can change +the software or use pieces of it in new free programs; and that you know you can +do these things. + +To protect your rights, we need to make restrictions that forbid anyone to deny +you these rights or to ask you to surrender the rights. These restrictions +translate to certain responsibilities for you if you distribute copies of the +software, or if you modify it. + +For example, if you distribute copies of such a program, whether gratis or for a +fee, you must give the recipients all the rights that you have. You must make +sure that they, too, receive or can get the source code. And you must show them +these terms so they know their rights. + +We protect your rights with two steps: (1) copyright the software, and (2) offer +you this license which gives you legal permission to copy, distribute and/or +modify the software. + +Also, for each author's protection and ours, we want to make certain that +everyone understands that there is no warranty for this free software. If the +software is modified by someone else and passed on, we want its recipients to +know that what they have is not the original, so that any problems introduced by +others will not reflect on the original authors' reputations. + +Finally, any free program is threatened constantly by software patents. We wish +to avoid the danger that redistributors of a free program will individually +obtain patent licenses, in effect making the program proprietary. To prevent +this, we have made it clear that any patent must be licensed for everyone's free +use or not licensed at all. + +The precise terms and conditions for copying, distribution and modification +follow. + +TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + +0. This License applies to any program or other work which contains a notice +placed by the copyright holder saying it may be distributed under the terms of +this General Public License. The "Program", below, refers to any such program +or work, and a "work based on the Program" means either the Program or any +derivative work under copyright law: that is to say, a work containing the +Program or a portion of it, either verbatim or with modifications and/or +translated into another language. (Hereinafter, translation is included without +limitation in the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not covered by +this License; they are outside its scope. The act of running the Program is not +restricted, and the output from the Program is covered only if its contents +constitute a work based on the Program (independent of having been made by +running the Program). Whether that is true depends on what the Program does. + +1. You may copy and distribute verbatim copies of the Program's source code as +you receive it, in any medium, provided that you conspicuously and +appropriately publish on each copy an appropriate copyright notice and +disclaimer of warranty; keep intact all the notices that refer to this License +and to the absence of any warranty; and give any other recipients of the Program +a copy of this License along with the Program. + +You may charge a fee for the physical act of transferring a copy, and you may at +your option offer warranty protection in exchange for a fee. + +2. You may modify your copy or copies of the Program or any portion of it, thus +forming a work based on the Program, and copy and distribute such +modifications or work under the terms of Section 1 above, provided that you +also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices stating that + you changed the files and the date of any change. + b) You must cause any work that you distribute or publish, that in whole or + in part contains or is derived from the Program or any part thereof, to be + licensed as a whole at no charge to all third parties under the terms of + this License. + c) If the modified program normally reads commands interactively when + run, you must cause it, when started running for such interactive use in the + most ordinary way, to print or display an announcement including an + appropriate copyright notice and a notice that there is no warranty (or + else, saying that you provide a warranty) and that users may redistribute + the program under these conditions, and telling the user how to view a copy + of this License. (Exception: if the Program itself is interactive but does + not normally print such an announcement, your work based on the Program is + not required to print an announcement.) + +These requirements apply to the modified work as a whole. If identifiable +sections of that work are not derived from the Program, and can be reasonably +considered independent and separate works in themselves, then this License, +and its terms, do not apply to those sections when you distribute them as +separate works. But when you distribute the same sections as part of a whole +which is a work based on the Program, the distribution of the whole must be on +the terms of this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest your +rights to work written entirely by you; rather, the intent is to exercise the +right to control the distribution of derivative or collective works based on the +Program. + +In addition, mere aggregation of another work not based on the Program with +the Program (or with a work based on the Program) on a volume of a storage or +distribution medium does not bring the other work under the scope of this +License. + +3. You may copy and distribute the Program (or a work based on it, under +Section 2) in object code or executable form under the terms of Sections 1 and 2 +above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable source + code, which must be distributed under the terms of Sections 1 and 2 above + on a medium customarily used for software interchange; or, + b) Accompany it with a written offer, valid for at least three years, to + give any third party, for a charge no more than your cost of physically + performing source distribution, a complete machine-readable copy of the + corresponding source code, to be distributed under the terms of Sections 1 + and 2 above on a medium customarily used for software interchange; or, + c) Accompany it with the information you received as to the offer to + distribute corresponding source code. (This alternative is allowed only for + noncommercial distribution and only if you received the program in object + code or executable form with such an offer, in accord with Subsection b + above.) + +The source code for a work means the preferred form of the work for making +modifications to it. For an executable work, complete source code means all the +source code for all modules it contains, plus any associated interface +definition files, plus the scripts used to control compilation and installation +of the executable. However, as a special exception, the source code distributed +need not include anything that is normally distributed (in either source or +binary form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component itself +accompanies the executable. + +If distribution of executable or object code is made by offering access to copy +from a designated place, then offering equivalent access to copy the source code +from the same place counts as distribution of the source code, even though third +parties are not compelled to copy the source along with the object code. + +4. You may not copy, modify, sublicense, or distribute the Program except as +expressly provided under this License. Any attempt otherwise to copy, modify, +sublicense or distribute the Program is void, and will automatically terminate +your rights under this License. However, parties who have received copies, or +rights, from you under this License will not have their licenses terminated so +long as such parties remain in full compliance. + +5. You are not required to accept this License, since you have not signed it. +However, nothing else grants you permission to modify or distribute the +Program or its derivative works. These actions are prohibited by law if you do +not accept this License. Therefore, by modifying or distributing the Program (or +any work based on the Program), you indicate your acceptance of this License to +do so, and all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + +6. Each time you redistribute the Program (or any work based on the Program), +the recipient automatically receives a license from the original licensor to +copy, distribute or modify the Program subject to these terms and conditions. +You may not impose any further restrictions on the recipients' exercise of the +rights granted herein. You are not responsible for enforcing compliance by third +parties to this License. + +7. If, as a consequence of a court judgment or allegation of patent infringement +or for any other reason (not limited to patent issues), conditions are imposed +on you (whether by court order, agreement or otherwise) that contradict the +conditions of this License, they do not excuse you from the conditions of this +License. If you cannot distribute so as to satisfy simultaneously your +obligations under this License and any other pertinent obligations, then as a +consequence you may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by all those +who receive copies directly or indirectly through you, then the only way you +could satisfy both it and this License would be to refrain entirely from +distribution of the Program. + +If any portion of this section is held invalid or unenforceable under any +particular circumstance, the balance of the section is intended to apply and the +section as a whole is intended to apply in other circumstances. + +It is not the purpose of this section to induce you to infringe any patents or +other property right claims or to contest validity of any such claims; this +section has the sole purpose of protecting the integrity of the free software +distribution system, which is implemented by public license practices. Many +people have made generous contributions to the wide range of software +distributed through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing to +distribute software through any other system and a licensee cannot impose that +choice. + +This section is intended to make thoroughly clear what is believed to be a +consequence of the rest of this License. + +8. If the distribution and/or use of the Program is restricted in certain +countries either by patents or by copyrighted interfaces, the original copyright +holder who places the Program under this License may add an explicit +geographical distribution limitation excluding those countries, so that +distribution is permitted only in or among countries not thus excluded. In such +case, this License incorporates the limitation as if written in the body of this +License. + +9. The Free Software Foundation may publish revised and/or new versions of the +General Public License from time to time. Such new versions will be similar in +spirit to the present version, but may differ in detail to address new problems +or concerns. + +Each version is given a distinguishing version number. If the Program specifies +a version number of this License which applies to it and "any later version", +you have the option of following the terms and conditions either of that version +or of any later version published by the Free Software Foundation. If the +Program does not specify a version number of this License, you may choose any +version ever published by the Free Software Foundation. + +10. If you wish to incorporate parts of the Program into other free programs +whose distribution conditions are different, write to the author to ask for +permission. For software which is copyrighted by the Free Software Foundation, +write to the Free Software Foundation; we sometimes make exceptions for this. +Our decision will be guided by the two goals of preserving the free status of +all derivatives of our free software and of promoting the sharing and reuse of +software generally. + +NO WARRANTY + +11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE +PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED +IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM +"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, +BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A +PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE +PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF +ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + +12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL +ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE +PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, +SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY +TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING +RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF +THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER +PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. + +END OF TERMS AND CONDITIONS + +How to Apply These Terms to Your New Programs + +If you develop a new program, and you want it to be of the greatest possible use +to the public, the best way to achieve this is to make it free software which +everyone can redistribute and change under these terms. + +To do so, attach the following notices to the program. It is safest to attach +them to the start of each source file to most effectively convey the exclusion +of warranty; and each file should have at least the "copyright" line and a +pointer to where the full notice is found. + + one line to give the program's name and an idea of what it does. + Copyright (C) yyyy name of author + + This program is free software; you can redistribute it and/or + modify it under the terms of the GNU General Public License + as published by the Free Software Foundation; either version 2 + of the License, or (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this when it +starts in an interactive mode: + + Gnomovision version 69, Copyright (C) year name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details + type `show w'. This is free software, and you are welcome + to redistribute it under certain conditions; type `show c' + for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may be +called something other than `show w' and `show c' ; they could even be mouse- +clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your school, +if any, to sign a "copyright disclaimer" for the program, if necessary. Here is +a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright + interest in the program `Gnomovision' + (which makes passes at compilers) written + by James Hacker. + + signature of Ty Coon, 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may consider +it more useful to permit linking proprietary applications with the library. If +this is what you want to do, use the GNU Lesser General Public License instead +of this License. diff --git a/drivers/intel/ixgbe/ixgbe-5.19.6-zc/Makefile b/drivers/intel/ixgbe/ixgbe-5.19.6-zc/Makefile new file mode 100644 index 0000000000..3f1969ecf8 --- /dev/null +++ b/drivers/intel/ixgbe/ixgbe-5.19.6-zc/Makefile @@ -0,0 +1,8 @@ +export PF_RING_PATH := $(shell cd ../../../../kernel; pwd) +export C_INCLUDE_PATH := ${PF_RING_PATH}/linux + +all: + cd src; make + +clean: + cd src; make clean diff --git a/drivers/intel/ixgbe/ixgbe-5.19.6-zc/README b/drivers/intel/ixgbe/ixgbe-5.19.6-zc/README new file mode 100644 index 0000000000..b8bd8db6cc --- /dev/null +++ b/drivers/intel/ixgbe/ixgbe-5.19.6-zc/README @@ -0,0 +1,1523 @@ + +ixgbe Linux* Base Driver for Intel(R) Ethernet Network Connections +================================================================== + +November 15, 2021 + +Contents +-------- + +- Overview +- Identifying Your Adapter +- Important Notes +- Building and Installation +- Command Line Parameters +- Additional Features and Configurations +- Known Issues/Troubleshooting +- Support +- License + + +Overview +======== +This driver supports kernel versions 2.6.x and newer. However, some features +may require a newer kernel version. The associated Virtual Function (VF) driver +for this driver is ixgbevf. + +Driver information can be obtained using ethtool, lspci, and ip. Instructions +on updating ethtool can be found in the section Additional Configurations later +in this document. + +This driver is only supported as a loadable module at this time. Intel is not +supplying patches against the kernel source to allow for static linking of the +drivers. + +For questions related to hardware requirements, refer to the documentation +supplied with your Intel adapter. All hardware requirements listed apply to use +with Linux. + +This driver supports XDP (Express Data Path) on kernel 4.14 and later and +AF_XDP zero-copy on kernel 4.18 and later. Note that XDP is blocked for frame +sizes larger than 3KB. + +NOTE: Devices based on the Intel(R) Ethernet Connection X552 and Intel(R) +Ethernet Connection X553 do not support the following features: +* Energy Efficient Ethernet (EEE) +* Intel PROSet for Windows Device Manager +* Intel ANS teams or VLANs (LBFO is supported) +* Fibre Channel over Ethernet (FCoE) +* Data Center Bridging (DCB) +* IPSec Offloading +* MACSec Offloading +In addition, SFP+ devices based on the Intel(R) Ethernet Connection X552 and +Intel(R) Ethernet Connection X553 do not support the following features: +* Speed and duplex auto-negotiation. +* Wake on LAN +* 1000BASE-T SFP Modules + + +Identifying Your Adapter +======================== +The driver is compatible with devices based on the following: + * Intel(R) Ethernet Controller 82598 + * Intel(R) Ethernet Controller 82599 + * Intel(R) Ethernet Controller X520 + * Intel(R) Ethernet Controller X540 + * Intel(R) Ethernet Controller x550 + * Intel(R) Ethernet Controller X552 + * Intel(R) Ethernet Controller X553 + +For information on how to identify your adapter, and for the latest Intel +network drivers, refer to the Intel Support website: +http://www.intel.com/support + + +SFP+ Devices with Pluggable Optics +---------------------------------- + +82599-BASED ADAPTERS +-------------------- + +NOTES: +- If your 82599-based Intel(R) Network Adapter came with Intel optics or is an + Intel(R) Ethernet Server Adapter X520-2, then it only supports Intel optics + and/or the direct attach cables listed below. +- When 82599-based SFP+ devices are connected back to back, they should be + set to the same Speed setting via ethtool. Results may vary if you mix + speed settings. + +Supplier Type Part Numbers +-------- ---- ------------ +SR Modules +Intel DUAL RATE 1G/10G SFP+ SR (bailed) FTLX8571D3BCV-IT +Intel DUAL RATE 1G/10G SFP+ SR (bailed) AFBR-703SDZ-IN2 +Intel DUAL RATE 1G/10G SFP+ SR (bailed) AFBR-703SDDZ-IN1 +LR Modules +Intel DUAL RATE 1G/10G SFP+ LR (bailed) FTLX1471D3BCV-IT +Intel DUAL RATE 1G/10G SFP+ LR (bailed) AFCT-701SDZ-IN2 +Intel DUAL RATE 1G/10G SFP+ LR (bailed) AFCT-701SDDZ-IN1 + +The following is a list of 3rd party SFP+ modules that have received some +testing. Not all modules are applicable to all devices. + +Supplier Type Part Numbers +-------- ---- ------------ +Finisar SFP+ SR bailed, 10g single rate FTLX8571D3BCL +Avago SFP+ SR bailed, 10g single rate AFBR-700SDZ +Finisar SFP+ LR bailed, 10g single rate FTLX1471D3BCL +Finisar DUAL RATE 1G/10G SFP+ SR (No Bail) FTLX8571D3QCV-IT +Avago DUAL RATE 1G/10G SFP+ SR (No Bail) AFBR-703SDZ-IN1 +Finisar DUAL RATE 1G/10G SFP+ LR (No Bail) FTLX1471D3QCV-IT +Avago DUAL RATE 1G/10G SFP+ LR (No Bail) AFCT-701SDZ-IN1 + +Finisar 1000BASE-T SFP FCLF8522P2BTL +Avago 1000BASE-T ABCU-5710RZ +HP 1000BASE-SX SFP 453153-001 + +82599-based adapters support all passive and active limiting direct attach +cables that comply with SFF-8431 v4.1 and SFF-8472 v10.4 specifications. + + +Turning the laser off or on for SFP+ +------------------------------------ +Use "ip link set [down/up] dev " to turn the +laser off and on. + + +82599-based QSFP+ Adapters +-------------------------- + +NOTES: +- If your 82599-based Intel(R) Network Adapter came with Intel optics, it + only supports Intel optics. +- 82599-based QSFP+ adapters only support 4x10 Gbps connections. + 1x40 Gbps connections are not supported. QSFP+ link partners must be + configured for 4x10 Gbps. +- 82599-based QSFP+ adapters do not support automatic link speed detection. + The link speed must be configured to either 10 Gbps or 1 Gbps to match the + link partners speed capabilities. Incorrect speed configurations will result + in failure to link. +- Intel(R) Ethernet Converged Network Adapter X520-Q1 only supports the + optics and direct attach cables listed below. + + +Supplier Type Part Numbers +-------- ---- ------------ +Intel DUAL RATE 1G/10G QSFP+ SRL (bailed) E10GQSFPSR + +82599-based QSFP+ adapters support all passive and active limiting QSFP+ +direct attach cables that comply with SFF-8436 v4.1 specifications. + + +82598-BASED ADAPTERS +-------------------- + +NOTES: +- Intel(r) Ethernet Network Adapters that support removable optical modules + only support their original module type (for example, the Intel(R) 10 Gigabit + SR Dual Port Express Module only supports SR optical modules). If you plug + in a different type of module, the driver will not load. +- Hot Swapping/hot plugging optical modules is not supported. +- Only single speed, 10 gigabit modules are supported. +- LAN on Motherboard (LOMs) may support DA, SR, or LR modules. Other module + types are not supported. Please see your system documentation for details. + + The following is a list of SFP+ modules and direct attach cables that have + received some testing. Not all modules are applicable to all devices. + +Supplier Type Part Numbers +-------- ---- ------------ +Finisar SFP+ SR bailed, 10g single rate FTLX8571D3BCL +Avago SFP+ SR bailed, 10g single rate AFBR-700SDZ +Finisar SFP+ LR bailed, 10g single rate FTLX1471D3BCL + +82598-based adapters support all passive direct attach cables that comply with +SFF-8431 v4.1 and SFF-8472 v10.4 specifications. Active direct attach cables +are not supported. + +Third party optic modules and cables referred to above are listed only for the +purpose of highlighting third party specifications and potential +compatibility, and are not recommendations or endorsements or sponsorship of +any third party's product by Intel. Intel is not endorsing or promoting +products made by any third party and the third party reference is provided +only to share information regarding certain optic modules and cables with the +above specifications. There may be other manufacturers or suppliers, producing +or supplying optic modules and cables with similar or matching descriptions. +Customers must use their own discretion and diligence to purchase optic +modules and cables from any third party of their choice. Customers are solely +responsible for assessing the suitability of the product and/or devices and +for the selection of the vendor for purchasing any product. THE OPTIC MODULES +AND CABLES REFERRED TO ABOVE ARE NOT WARRANTED OR SUPPORTED BY INTEL. INTEL +ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED +WARRANTY, RELATING TO SALE AND/OR USE OF SUCH THIRD PARTY PRODUCTS OR +SELECTION OF VENDOR BY CUSTOMERS. + + +Important Notes +=============== + +Do not unload port driver if VF with active VM is bound to it +------------------------------------------------------------- +Do not unload a port's driver if a Virtual Function (VF) with an active Virtual +Machine (VM) is bound to it. Doing so will cause the port to appear to hang. +Once the VM shuts down, or otherwise releases the VF, the command will complete. + + +Configuring SR-IOV for improved network security +------------------------------------------------ +In a virtualized environment, on Intel(R) Ethernet Network Adapters that +support SR-IOV or Intel(R) Scalable I/O Virtualization (Intel(R) Scalable IOV), +the virtual function (VF) may be subject to malicious behavior. +Software-generated layer two frames, like IEEE 802.3x (link flow control), IEEE +802.1Qbb (priority based flow-control), and others of this type, are not +expected and can throttle traffic between the host and the virtual switch, +reducing performance. To resolve this issue, and to ensure isolation from +unintended traffic streams, configure all SR-IOV or Intel Scalable IOV enabled +ports for VLAN tagging from the administrative interface on the PF. This +configuration allows unexpected, and potentially malicious, frames to be +dropped. + + +Building and Installation +========================= + +To manually build the driver +---------------------------- +1. Move the base driver tar file to the directory of your choice. + For example, use '/home/username/ixgbe' or '/usr/local/src/ixgbe'. + +2. Untar/unzip the archive, where is the version number for the + driver tar file: + + # tar zxf ixgbe-.tar.gz + +3. Change to the driver src directory, where is the version number + for the driver tar: + + # cd ixgbe-/src/ + +4. Compile the driver module: + + # make install + + The binary will be installed as: + /lib/modules//updates/drivers/net/ethernet/intel/ixgbe/ixgbe.ko + + The install location listed above is the default location. This may differ + for various Linux distributions. + +5. Load the module using the modprobe command. + + To check the version of the driver and then load it: + + # modinfo ixgbe + # modprobe ixgbe [parameter=port1_value,port2_value] + + Alternately, make sure that any older ixgbe drivers are removed from the + kernel before loading the new module: + + # rmmod ixgbe; modprobe ixgbe + +6. Assign an IP address to the interface by entering the following, + where is the interface name that was shown in dmesg after modprobe: + + # ip address add / dev + +7. Verify that the interface works. Enter the following, where IP_address + is the IP address for another machine on the same subnet as the interface + that is being tested: + + # ping + +Note: For certain distributions like (but not limited to) Red Hat Enterprise +Linux 7 and Ubuntu, once the driver is installed, you may need to update the +initrd/initramfs file to prevent the OS loading old versions of the ixgbe +driver. + For Red Hat distributions: + # dracut --force + + For Ubuntu: + # update-initramfs -u + + +To build a binary RPM package of this driver +-------------------------------------------- +Note: RPM functionality has only been tested in Red Hat distributions. + +1. Run the following command, where is the version number for the + driver tar file. + + # rpmbuild -tb ixgbe-.tar.gz + + NOTE: For the build to work properly, the currently running kernel MUST + match the version and configuration of the installed kernel sources. If + you have just recompiled the kernel, reboot the system before building. + +2. After building the RPM, the last few lines of the tool output contain the + location of the RPM file that was built. Install the RPM with one of the + following commands, where is the location of the RPM file: + + # rpm -Uvh + or + # dnf/yum localinstall + +NOTES: +- To compile the driver on some kernel/arch combinations, you may need to +install a package with the development version of libelf (e.g. libelf-dev, +libelf-devel, elfutils-libelf-devel). +- When compiling an out-of-tree driver, details will vary by distribution. +However, you will usually need a kernel-devel RPM or some RPM that provides the +kernel headers at a minimum. The RPM kernel-devel will usually fill in the link +at /lib/modules/'uname -r'/build. + + +To build ixgbe driver with DCA +------------------------------ +If your kernel supports DCA, the driver will build by default with DCA enabled. + +Note: DCA is not supported on X550-based adapters. + + + +Command Line Parameters +======================= +If the driver is built as a module, enter optional parameters on the command +line with the following syntax: + +# modprobe ixgbe [