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

          Long meetings (6-7 hours a day): Being “babysat” by supervisor

          Image
          Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote 31 down vote favorite 4 I hold a PhD in mechanical engineering with a 7 year background in self-guided, self-paced research including 2 years as a graduate level course instructor and a subject matter expert for various engineering projects in a university setting in the United States. For the last 10-11 months, I am working in a research industry in France where my task is to debug C++ spaghetti code written over a period of several years by my current supervisor. It is a team of 2: just I and my supervisor. Diurnally, I am posed with a "bug of the day" to get out of this C++ code. My supervisor generally gives me about 15-30 minutes to solve it and then accosts me about whether or not the task is completed and then rinses and repeats this until the end of the day. Off-late, my supervisor has been holding 6-7 hour long "meetin
          Read more

          Is the Concept of Multiple Fantasy Races Scientifically Flawed? [closed]

          Image
          Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite Many fantasy worlds have multiple humanoid species (elves, orcs, humans, etc) living in the same world, in addition to that, they often have the ability to interbreed. And I can't help but question their believability... fantasy-races reproduction interspecies-relations share | improve this question edited Aug 9 at 14:46 Michael Kjörling ♦ 21.1k 10 85 161 asked Aug 9 at 13:13 Chlodio 118 6 closed as unclear what you're asking by MichaelK, Gryphon, John, Vincent, Frostfyre Aug 9 at 15:25 Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question. 3 Stack Exchange exist to
          Read more

          Confectionery

          Image
          Prepared foods made with a lot of sugar or other cabohydrates "Sweetmeat" redirects here. For the racehorse, see Sweetmeat (horse). Not to be confused with Sweetbread. This Kransekake is a traditional Scandinavian baker's confection. Confectionery is the art of making confections , which are food items that are rich in sugar and carbohydrates. Exact definitions are difficult. [1] In general, though, confectionery is divided into two broad and somewhat overlapping categories, bakers' confections and sugar confections. [2] Bakers' confectionery, also called flour confections , includes principally sweet pastries, cakes, and similar baked goods. Sugar confectionery includes candies ( sweets in British English), candied nuts, chocolates, chewing gum, bubble gum, pastillage, and other confections that are made primarily of sugar. In some cases, chocolate confections (confections made of chocolate) are treated as a separate category, as are sugar-free versions of
          Read more