disable kernel module which is compiled in kernel (not loaded)

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
17
down vote

favorite
3












My server has two 1-Gbit and two 10-Gbit onboard network cards.



I need to disable the 1-Gbit network cards completely, so that ifconfig -a does not show them.



The network cards use different kernel modules. The 10-Gbit use ixgbe, and the 1-Gbit use igb.



01:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
Subsystem: Dell Ethernet 10G 4P X520/I350 rNDC
Kernel driver in use: ixgbe

05:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
Subsystem: Dell I350 Gigabit Network Connection
Kernel driver in use: igb


Both ixgbe and igb are compiled statically in the kernel (not as a lodable module). I need to disable the module using the kernel boot parameters



I have tried appending the following to my kernel, but it has no effect:



igb.blacklist=yes
igb.enable=0
igb.disable=yes


the igb network cards are still showing



How can I disable igb completely ?






kernel boot linux-kernel







share|improve this question

























    up vote
    17
    down vote

    favorite
    3












    My server has two 1-Gbit and two 10-Gbit onboard network cards.



    I need to disable the 1-Gbit network cards completely, so that ifconfig -a does not show them.



    The network cards use different kernel modules. The 10-Gbit use ixgbe, and the 1-Gbit use igb.



    01:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
    Subsystem: Dell Ethernet 10G 4P X520/I350 rNDC
    Kernel driver in use: ixgbe

    05:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    Subsystem: Dell I350 Gigabit Network Connection
    Kernel driver in use: igb


    Both ixgbe and igb are compiled statically in the kernel (not as a lodable module). I need to disable the module using the kernel boot parameters



    I have tried appending the following to my kernel, but it has no effect:



    igb.blacklist=yes
    igb.enable=0
    igb.disable=yes


    the igb network cards are still showing



    How can I disable igb completely ?






    kernel boot linux-kernel







    share|improve this question























      up vote
      17
      down vote

      favorite
      3









      up vote
      17
      down vote

      favorite
      3






      3





      My server has two 1-Gbit and two 10-Gbit onboard network cards.



      I need to disable the 1-Gbit network cards completely, so that ifconfig -a does not show them.



      The network cards use different kernel modules. The 10-Gbit use ixgbe, and the 1-Gbit use igb.



      01:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
      Subsystem: Dell Ethernet 10G 4P X520/I350 rNDC
      Kernel driver in use: ixgbe

      05:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
      Subsystem: Dell I350 Gigabit Network Connection
      Kernel driver in use: igb


      Both ixgbe and igb are compiled statically in the kernel (not as a lodable module). I need to disable the module using the kernel boot parameters



      I have tried appending the following to my kernel, but it has no effect:



      igb.blacklist=yes
      igb.enable=0
      igb.disable=yes


      the igb network cards are still showing



      How can I disable igb completely ?






      kernel boot linux-kernel







      share|improve this question













      My server has two 1-Gbit and two 10-Gbit onboard network cards.



      I need to disable the 1-Gbit network cards completely, so that ifconfig -a does not show them.



      The network cards use different kernel modules. The 10-Gbit use ixgbe, and the 1-Gbit use igb.



      01:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
      Subsystem: Dell Ethernet 10G 4P X520/I350 rNDC
      Kernel driver in use: ixgbe

      05:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
      Subsystem: Dell I350 Gigabit Network Connection
      Kernel driver in use: igb


      Both ixgbe and igb are compiled statically in the kernel (not as a lodable module). I need to disable the module using the kernel boot parameters



      I have tried appending the following to my kernel, but it has no effect:



      igb.blacklist=yes
      igb.enable=0
      igb.disable=yes


      the igb network cards are still showing



      How can I disable igb completely ?






      kernel boot linux-kernel




      kernel boot linux-kernel






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 2 days ago









      Martin Vegter

      53031110219




      53031110219




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          26
          down vote



          accepted










          You should be able to blacklist the igb “module”, even when built-in, by blacklisting its initialisation function: add



          initcall_blacklist=igb_init_module


          to your kernel’s boot parameters.



          See How do I disable I2C Designware support when it's not built as a module? for background information. The general recipe here is to look for the module in the kernel source code, and look for functions which have the __init attribute — there should only be one. Blacklist that, and the driver won’t be initialised.






          share|improve this answer


















          • 2




            For those to whom it matters, the initcall_blacklist parameter appeared in Linux 3.16.
            – Ruslan
            yesterday










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f468024%2fdisable-kernel-module-which-is-compiled-in-kernel-not-loaded%23new-answer', 'question_page');

          );

          Post as a guest

















          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          26
          down vote



          accepted










          You should be able to blacklist the igb “module”, even when built-in, by blacklisting its initialisation function: add



          initcall_blacklist=igb_init_module


          to your kernel’s boot parameters.



          See How do I disable I2C Designware support when it's not built as a module? for background information. The general recipe here is to look for the module in the kernel source code, and look for functions which have the __init attribute — there should only be one. Blacklist that, and the driver won’t be initialised.






          share|improve this answer


















          • 2




            For those to whom it matters, the initcall_blacklist parameter appeared in Linux 3.16.
            – Ruslan
            yesterday














          up vote
          26
          down vote



          accepted










          You should be able to blacklist the igb “module”, even when built-in, by blacklisting its initialisation function: add



          initcall_blacklist=igb_init_module


          to your kernel’s boot parameters.



          See How do I disable I2C Designware support when it's not built as a module? for background information. The general recipe here is to look for the module in the kernel source code, and look for functions which have the __init attribute — there should only be one. Blacklist that, and the driver won’t be initialised.






          share|improve this answer


















          • 2




            For those to whom it matters, the initcall_blacklist parameter appeared in Linux 3.16.
            – Ruslan
            yesterday












          up vote
          26
          down vote



          accepted







          up vote
          26
          down vote



          accepted






          You should be able to blacklist the igb “module”, even when built-in, by blacklisting its initialisation function: add



          initcall_blacklist=igb_init_module


          to your kernel’s boot parameters.



          See How do I disable I2C Designware support when it's not built as a module? for background information. The general recipe here is to look for the module in the kernel source code, and look for functions which have the __init attribute — there should only be one. Blacklist that, and the driver won’t be initialised.






          share|improve this answer














          You should be able to blacklist the igb “module”, even when built-in, by blacklisting its initialisation function: add



          initcall_blacklist=igb_init_module


          to your kernel’s boot parameters.



          See How do I disable I2C Designware support when it's not built as a module? for background information. The general recipe here is to look for the module in the kernel source code, and look for functions which have the __init attribute — there should only be one. Blacklist that, and the driver won’t be initialised.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited 2 days ago

























          answered 2 days ago









          Stephen Kitt

          144k22317382




          144k22317382







          • 2




            For those to whom it matters, the initcall_blacklist parameter appeared in Linux 3.16.
            – Ruslan
            yesterday












          • 2




            For those to whom it matters, the initcall_blacklist parameter appeared in Linux 3.16.
            – Ruslan
            yesterday







          2




          2




          For those to whom it matters, the initcall_blacklist parameter appeared in Linux 3.16.
          – Ruslan
          yesterday




          For those to whom it matters, the initcall_blacklist parameter appeared in Linux 3.16.
          – Ruslan
          yesterday

















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f468024%2fdisable-kernel-module-which-is-compiled-in-kernel-not-loaded%23new-answer', 'question_page');

          );

          Post as a guest
































































          Comments

          Post a Comment

          Popular posts from this blog

          What does second last employer means? [closed]

          Image
          Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote -3 down vote favorite Say, for example I have worked in the following companies, Company A => 2010 - 2011 Company B => 2011 - 2012 Company C => 2012 - Till Date Company D => Have offer Now assume Company D is asking to submit documents from my second last employer. So from the list of companies given, which company would be qualified as second last employer? software-industry employer share | improve this question asked Aug 10 '14 at 5:16 Rajaprabhu Aravindasamy 559 1 6 13 closed as off-topic by Jim G., jmort253 ♦ Aug 11 '14 at 1:58 This question appears to be off-topic. The users who voted to close gave this specific reason: "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address...
          Read more

          Installing NextGIS Connect into QGIS 3?

          Image
          Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote 1 down vote favorite Just acquired free version of NEXTGIS and trying to install the plugin for QGIS. It tells me it was not designed for version 3 of QGIS. How do I set up the QGIS-NEXTGIS interface then? qgis qgis-plugins nextgis share | improve this question edited 3 hours ago PolyGeo ♦ 51.9k 17 77 233 asked 4 hours ago IanGS 16 4 New contributor IanGS is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment  |  up vote 1 down vote favorite Just acquired free version of NEXTGIS and trying to install the plugin for QGIS. It tells me it was not designed for version 3 of QGIS. How do I set up the QGIS-NEXTGIS interface then? qgis qgis-plugin...
          Read more

          One-line joke

          A one-liner is a joke that is delivered in a single line. A good one-liner is said to be pithy - concise and meaningful. [1] Comedians and actors use this comedic method as part of their act, e.g. Jimmy Carr, Tommy Cooper, Rodney Dangerfield, Norm Macdonald, Ken Dodd, Stewart Francis, Zach Galifianakis, Mitch Hedberg, Anthony Jeselnik, Milton Jones, Shappi Khorsandi, Jay London, Mark Linn-Baker, Demetri Martin, Groucho Marx, Dan Mintz, Emo Philips, Tim Vine, Steven Wright and Henny Youngman and Arnold Schwarzenegger. [ citation needed ] Many fictional characters are also known to deliver one-liners, including James Bond, who usually includes pithy and laconic quips after disposing of a villain. [ citation needed ] Examples "A baby seal walks into a club." "A dyslexic man walks into a bra." (Anonymous) "There are three types of people, those who can count and those who can't." "Venison's dear, isn't it?" (Jimmy Carr) "An escala...
          Read more