How to block drivers built-into Kernel, i.e. drivers who are not a module

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











up vote
6
down vote

favorite












I configured and compiled Linux kernel with nouveau driver built-into kernel, i.e. with <*> as opposed to <M> when doing make menuconfig inside Linux kernel source directory.



Now, I intend to use another driver rather than nouveau. If nouveau was a module, I would add a line like blacklist nouveau inside /etc/modprobe.d/blacklist.conf



What should I do now.







share|improve this question
























    up vote
    6
    down vote

    favorite












    I configured and compiled Linux kernel with nouveau driver built-into kernel, i.e. with <*> as opposed to <M> when doing make menuconfig inside Linux kernel source directory.



    Now, I intend to use another driver rather than nouveau. If nouveau was a module, I would add a line like blacklist nouveau inside /etc/modprobe.d/blacklist.conf



    What should I do now.







    share|improve this question






















      up vote
      6
      down vote

      favorite









      up vote
      6
      down vote

      favorite











      I configured and compiled Linux kernel with nouveau driver built-into kernel, i.e. with <*> as opposed to <M> when doing make menuconfig inside Linux kernel source directory.



      Now, I intend to use another driver rather than nouveau. If nouveau was a module, I would add a line like blacklist nouveau inside /etc/modprobe.d/blacklist.conf



      What should I do now.







      share|improve this question












      I configured and compiled Linux kernel with nouveau driver built-into kernel, i.e. with <*> as opposed to <M> when doing make menuconfig inside Linux kernel source directory.



      Now, I intend to use another driver rather than nouveau. If nouveau was a module, I would add a line like blacklist nouveau inside /etc/modprobe.d/blacklist.conf



      What should I do now.









      share|improve this question











      share|improve this question




      share|improve this question










      asked Apr 14 '16 at 9:17









      user3405291

      723315




      723315




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          5
          down vote



          accepted










          You can also temporarily blacklist them on the grub command line (linux line) when you boot with the syntax



          module_to_blacklist.blacklist=yes


          OR



          modprobe.blacklist=module_to_blacklist


          You need to modify the grub,cfg to make the changes permanent.



          Mind you, this solution will not work for few modules






          share|improve this answer




















          • Which modules does it not work for, for example? What is the reason? E.g. in particular does not seem to work for i8042.
            – Ciro Santilli 新疆改造中心 六四事件 法轮功
            Dec 30 '17 at 22:57










          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%2f276392%2fhow-to-block-drivers-built-into-kernel-i-e-drivers-who-are-not-a-module%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
          5
          down vote



          accepted










          You can also temporarily blacklist them on the grub command line (linux line) when you boot with the syntax



          module_to_blacklist.blacklist=yes


          OR



          modprobe.blacklist=module_to_blacklist


          You need to modify the grub,cfg to make the changes permanent.



          Mind you, this solution will not work for few modules






          share|improve this answer




















          • Which modules does it not work for, for example? What is the reason? E.g. in particular does not seem to work for i8042.
            – Ciro Santilli 新疆改造中心 六四事件 法轮功
            Dec 30 '17 at 22:57














          up vote
          5
          down vote



          accepted










          You can also temporarily blacklist them on the grub command line (linux line) when you boot with the syntax



          module_to_blacklist.blacklist=yes


          OR



          modprobe.blacklist=module_to_blacklist


          You need to modify the grub,cfg to make the changes permanent.



          Mind you, this solution will not work for few modules






          share|improve this answer




















          • Which modules does it not work for, for example? What is the reason? E.g. in particular does not seem to work for i8042.
            – Ciro Santilli 新疆改造中心 六四事件 法轮功
            Dec 30 '17 at 22:57












          up vote
          5
          down vote



          accepted







          up vote
          5
          down vote



          accepted






          You can also temporarily blacklist them on the grub command line (linux line) when you boot with the syntax



          module_to_blacklist.blacklist=yes


          OR



          modprobe.blacklist=module_to_blacklist


          You need to modify the grub,cfg to make the changes permanent.



          Mind you, this solution will not work for few modules






          share|improve this answer












          You can also temporarily blacklist them on the grub command line (linux line) when you boot with the syntax



          module_to_blacklist.blacklist=yes


          OR



          modprobe.blacklist=module_to_blacklist


          You need to modify the grub,cfg to make the changes permanent.



          Mind you, this solution will not work for few modules







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Apr 14 '16 at 9:20









          SHW

          7,67133370




          7,67133370











          • Which modules does it not work for, for example? What is the reason? E.g. in particular does not seem to work for i8042.
            – Ciro Santilli 新疆改造中心 六四事件 法轮功
            Dec 30 '17 at 22:57
















          • Which modules does it not work for, for example? What is the reason? E.g. in particular does not seem to work for i8042.
            – Ciro Santilli 新疆改造中心 六四事件 法轮功
            Dec 30 '17 at 22:57















          Which modules does it not work for, for example? What is the reason? E.g. in particular does not seem to work for i8042.
          – Ciro Santilli 新疆改造中心 六四事件 法轮功
          Dec 30 '17 at 22:57




          Which modules does it not work for, for example? What is the reason? E.g. in particular does not seem to work for i8042.
          – Ciro Santilli 新疆改造中心 六四事件 法轮功
          Dec 30 '17 at 22:57

















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f276392%2fhow-to-block-drivers-built-into-kernel-i-e-drivers-who-are-not-a-module%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Bahrain

          Postfix configuration issue with fips on centos 7; mailgun relay