If the above steps are successful and the missing interface is showing, then we can confirm that the issue is unsupported SFP+. We will now add a parameter “options ixgbe allow_unsupported_sfp=1” to the ixgbe modue whoes path is : We will now confirm whether this issue is due to the unsupported sfp+. We can easily override the setting by adding a simple parameter to the grub file, which will be explained below.Īs mentioned above some parameters will be added to the grub file. The settings are configured in the EEPROM. Why does this issue happen?ĭue to support issues, Intel is restricting the types of SFPs that can be used on their NICs. If the number of links detected is less than the number of NIC ports detected, then you can be pretty sure that the issue is with the unsupported SFP+. Now, you can check the number of interfaces by running the command “ip a”, and compare the number of links detected with the number of NIC ports detected while running the “lspci” command. While performing the command ” lspci | grep -i net”, you can see the number of NIC ports connected on the motherboard. * How to identify the issue with the Unsupported SFP? How to fix the issue? Let me help you with it. This is because the ixgbe module failed to load because an unsupported SFP+ module type was detected. Sometimes, the interface doesn’t show up. usr/lib/modprobe.d/ is also a thing, there's some noise about it on Red Hat and Debian bug trackers, and the Arch wiki.You might have experienced some troubles in finding the right interface which has the 10G uplink. This scheme is the same as the one employed by udev, systemd andĪ follow-up patch lets files in one directory override files in usr/local/lib/modprobe.d config files during development of lib/modprobe.d config files installed by third-party packages etc/modprobe.d config files manually created by the administrator forĬompatibility with non-standard config files (such as /etc/rc.conf in run/modprobe.d config files generated at runtime, useful e.g. Read config files from the following directories: Modprobe: use more than one config directory Yes, there are directories for software packages and site specific: It seems /lib/modprobe.d is for conf files for the packages we install in the system. Is it all about the the boot stage the conf files are read?įurther reading the linked page, it seems /lib/modprobe.d is for conf files for the packages we install in the system. Ls: cannot access '/run/modprobe.d/': No such file or directory rw-r-r- 1 root root 325 blacklist-ath_pci.conf The /etc/modprobe.d directory isn't available in the initramfs, so the nf isn't created and the rd.driver.blacklist isn't honored.Ĭhanging from /etc/modprobe.d to /lib/modprobe.d/ here restore the module blacklist behavior.Īs an example, this is what I have in a new droplet in Digital Ocean with Ubuntu 17.10: $ ls -l /lib/modprobe.d/ I have only seen this page where somebody had a problem (in Red Hat) and had to move a conf file from /etc to /lib because the former wasn't available in the initramfs: My question is: anybody knows what is the purpose of each of these folders? Modprobe.d - Configuration directory for modprobe My man modprobe.d says the following: NAME
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |