Adding modules to Kernel in LEDE distribution












0














So I'm trying to add one of the staging drivers, I'm trying to load FBTFT in the kernel. I'm using this fork https://github.com/OnionIoT/source



So far things I have done:



make menuconfig



and selected the required options



I also configured the kernel to load the staging drivers



make kernel_menuconfig



Device drivers -> Graphics support -> Frame buffer Devices



<*> Support for frame buffer devices



Device drivers -> Staging drivers



<*> Support for small TFT LCD display modules
<M> FB driver for the ST7735R LCD Controller
<M> Generic FB driver for TFT LCD displays
<M> Module to for adding FBTFT devices


Then I compile



make -j5 V=s



This is the output of the make process output.txt



I flash my device with the bin generated.



sysupgrade -n lede-ramips-mt7688-omega2p-squashfs-sysupgrade.bin



But when is time to use the module, it doesn't work, I've tried all of this:



insmod fb_defio
insmod fb
insmod fbtft

modeprobe fbtft

fbtft_device


and nothing works, I don't think the module is correctly configured, I cannot find it anywhere.
Am I missing something?










share|improve this question















migrated from stackoverflow.com Dec 15 '17 at 6:02


This question came from our site for professional and enthusiast programmers.




















    0














    So I'm trying to add one of the staging drivers, I'm trying to load FBTFT in the kernel. I'm using this fork https://github.com/OnionIoT/source



    So far things I have done:



    make menuconfig



    and selected the required options



    I also configured the kernel to load the staging drivers



    make kernel_menuconfig



    Device drivers -> Graphics support -> Frame buffer Devices



    <*> Support for frame buffer devices



    Device drivers -> Staging drivers



    <*> Support for small TFT LCD display modules
    <M> FB driver for the ST7735R LCD Controller
    <M> Generic FB driver for TFT LCD displays
    <M> Module to for adding FBTFT devices


    Then I compile



    make -j5 V=s



    This is the output of the make process output.txt



    I flash my device with the bin generated.



    sysupgrade -n lede-ramips-mt7688-omega2p-squashfs-sysupgrade.bin



    But when is time to use the module, it doesn't work, I've tried all of this:



    insmod fb_defio
    insmod fb
    insmod fbtft

    modeprobe fbtft

    fbtft_device


    and nothing works, I don't think the module is correctly configured, I cannot find it anywhere.
    Am I missing something?










    share|improve this question















    migrated from stackoverflow.com Dec 15 '17 at 6:02


    This question came from our site for professional and enthusiast programmers.


















      0












      0








      0







      So I'm trying to add one of the staging drivers, I'm trying to load FBTFT in the kernel. I'm using this fork https://github.com/OnionIoT/source



      So far things I have done:



      make menuconfig



      and selected the required options



      I also configured the kernel to load the staging drivers



      make kernel_menuconfig



      Device drivers -> Graphics support -> Frame buffer Devices



      <*> Support for frame buffer devices



      Device drivers -> Staging drivers



      <*> Support for small TFT LCD display modules
      <M> FB driver for the ST7735R LCD Controller
      <M> Generic FB driver for TFT LCD displays
      <M> Module to for adding FBTFT devices


      Then I compile



      make -j5 V=s



      This is the output of the make process output.txt



      I flash my device with the bin generated.



      sysupgrade -n lede-ramips-mt7688-omega2p-squashfs-sysupgrade.bin



      But when is time to use the module, it doesn't work, I've tried all of this:



      insmod fb_defio
      insmod fb
      insmod fbtft

      modeprobe fbtft

      fbtft_device


      and nothing works, I don't think the module is correctly configured, I cannot find it anywhere.
      Am I missing something?










      share|improve this question















      So I'm trying to add one of the staging drivers, I'm trying to load FBTFT in the kernel. I'm using this fork https://github.com/OnionIoT/source



      So far things I have done:



      make menuconfig



      and selected the required options



      I also configured the kernel to load the staging drivers



      make kernel_menuconfig



      Device drivers -> Graphics support -> Frame buffer Devices



      <*> Support for frame buffer devices



      Device drivers -> Staging drivers



      <*> Support for small TFT LCD display modules
      <M> FB driver for the ST7735R LCD Controller
      <M> Generic FB driver for TFT LCD displays
      <M> Module to for adding FBTFT devices


      Then I compile



      make -j5 V=s



      This is the output of the make process output.txt



      I flash my device with the bin generated.



      sysupgrade -n lede-ramips-mt7688-omega2p-squashfs-sysupgrade.bin



      But when is time to use the module, it doesn't work, I've tried all of this:



      insmod fb_defio
      insmod fb
      insmod fbtft

      modeprobe fbtft

      fbtft_device


      and nothing works, I don't think the module is correctly configured, I cannot find it anywhere.
      Am I missing something?







      linux linux-kernel openwrt






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 16 at 22:02









      Rui F Ribeiro

      38.9k1479129




      38.9k1479129










      asked Dec 14 '17 at 13:36









      utiq

      101




      101




      migrated from stackoverflow.com Dec 15 '17 at 6:02


      This question came from our site for professional and enthusiast programmers.






      migrated from stackoverflow.com Dec 15 '17 at 6:02


      This question came from our site for professional and enthusiast programmers.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          In make kernel_menuconfig
          Go to FBTFT driver and press y,
          Right now it is selected for compilation, ('M' symbol in front of FBTFT driver).
          Once you press y, <'M' > will change to < *> which means it will get compiled and included in final image.






          share|improve this answer





















          • Thanks @VivekD, I changed them to <*>, however I can’t still see the module, but I can find at least one driver when I perform a find root@Omega-:/# find . -name fb* ./proc/fb ./sys/bus/spi/drivers/fb_st7735r ./sys/bus/platform/drivers/fb_st7735r And if I do this root@Omega-:~# insmod fbtft_device Failed to find fbtft_device. Maybe it is a built in module ? (fbtft_device = “Module to for adding FBTFT devices” kernel config option)
            – utiq
            Dec 14 '17 at 22:33










          • Hi @utiq, to list down the built-in modules, use lsmod command and try to verify if your module is present in there or not.
            – VivekD
            Dec 15 '17 at 11:14










          • The same, it doesn't show the module when I do lsmod. The module *.ko should be in /proc/modules, right?
            – utiq
            Dec 15 '17 at 16:03













          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',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          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%2f410985%2fadding-modules-to-kernel-in-lede-distribution%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          In make kernel_menuconfig
          Go to FBTFT driver and press y,
          Right now it is selected for compilation, ('M' symbol in front of FBTFT driver).
          Once you press y, <'M' > will change to < *> which means it will get compiled and included in final image.






          share|improve this answer





















          • Thanks @VivekD, I changed them to <*>, however I can’t still see the module, but I can find at least one driver when I perform a find root@Omega-:/# find . -name fb* ./proc/fb ./sys/bus/spi/drivers/fb_st7735r ./sys/bus/platform/drivers/fb_st7735r And if I do this root@Omega-:~# insmod fbtft_device Failed to find fbtft_device. Maybe it is a built in module ? (fbtft_device = “Module to for adding FBTFT devices” kernel config option)
            – utiq
            Dec 14 '17 at 22:33










          • Hi @utiq, to list down the built-in modules, use lsmod command and try to verify if your module is present in there or not.
            – VivekD
            Dec 15 '17 at 11:14










          • The same, it doesn't show the module when I do lsmod. The module *.ko should be in /proc/modules, right?
            – utiq
            Dec 15 '17 at 16:03


















          0














          In make kernel_menuconfig
          Go to FBTFT driver and press y,
          Right now it is selected for compilation, ('M' symbol in front of FBTFT driver).
          Once you press y, <'M' > will change to < *> which means it will get compiled and included in final image.






          share|improve this answer





















          • Thanks @VivekD, I changed them to <*>, however I can’t still see the module, but I can find at least one driver when I perform a find root@Omega-:/# find . -name fb* ./proc/fb ./sys/bus/spi/drivers/fb_st7735r ./sys/bus/platform/drivers/fb_st7735r And if I do this root@Omega-:~# insmod fbtft_device Failed to find fbtft_device. Maybe it is a built in module ? (fbtft_device = “Module to for adding FBTFT devices” kernel config option)
            – utiq
            Dec 14 '17 at 22:33










          • Hi @utiq, to list down the built-in modules, use lsmod command and try to verify if your module is present in there or not.
            – VivekD
            Dec 15 '17 at 11:14










          • The same, it doesn't show the module when I do lsmod. The module *.ko should be in /proc/modules, right?
            – utiq
            Dec 15 '17 at 16:03
















          0












          0








          0






          In make kernel_menuconfig
          Go to FBTFT driver and press y,
          Right now it is selected for compilation, ('M' symbol in front of FBTFT driver).
          Once you press y, <'M' > will change to < *> which means it will get compiled and included in final image.






          share|improve this answer












          In make kernel_menuconfig
          Go to FBTFT driver and press y,
          Right now it is selected for compilation, ('M' symbol in front of FBTFT driver).
          Once you press y, <'M' > will change to < *> which means it will get compiled and included in final image.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Dec 14 '17 at 17:47









          VivekD

          211




          211












          • Thanks @VivekD, I changed them to <*>, however I can’t still see the module, but I can find at least one driver when I perform a find root@Omega-:/# find . -name fb* ./proc/fb ./sys/bus/spi/drivers/fb_st7735r ./sys/bus/platform/drivers/fb_st7735r And if I do this root@Omega-:~# insmod fbtft_device Failed to find fbtft_device. Maybe it is a built in module ? (fbtft_device = “Module to for adding FBTFT devices” kernel config option)
            – utiq
            Dec 14 '17 at 22:33










          • Hi @utiq, to list down the built-in modules, use lsmod command and try to verify if your module is present in there or not.
            – VivekD
            Dec 15 '17 at 11:14










          • The same, it doesn't show the module when I do lsmod. The module *.ko should be in /proc/modules, right?
            – utiq
            Dec 15 '17 at 16:03




















          • Thanks @VivekD, I changed them to <*>, however I can’t still see the module, but I can find at least one driver when I perform a find root@Omega-:/# find . -name fb* ./proc/fb ./sys/bus/spi/drivers/fb_st7735r ./sys/bus/platform/drivers/fb_st7735r And if I do this root@Omega-:~# insmod fbtft_device Failed to find fbtft_device. Maybe it is a built in module ? (fbtft_device = “Module to for adding FBTFT devices” kernel config option)
            – utiq
            Dec 14 '17 at 22:33










          • Hi @utiq, to list down the built-in modules, use lsmod command and try to verify if your module is present in there or not.
            – VivekD
            Dec 15 '17 at 11:14










          • The same, it doesn't show the module when I do lsmod. The module *.ko should be in /proc/modules, right?
            – utiq
            Dec 15 '17 at 16:03


















          Thanks @VivekD, I changed them to <*>, however I can’t still see the module, but I can find at least one driver when I perform a find root@Omega-:/# find . -name fb* ./proc/fb ./sys/bus/spi/drivers/fb_st7735r ./sys/bus/platform/drivers/fb_st7735r And if I do this root@Omega-:~# insmod fbtft_device Failed to find fbtft_device. Maybe it is a built in module ? (fbtft_device = “Module to for adding FBTFT devices” kernel config option)
          – utiq
          Dec 14 '17 at 22:33




          Thanks @VivekD, I changed them to <*>, however I can’t still see the module, but I can find at least one driver when I perform a find root@Omega-:/# find . -name fb* ./proc/fb ./sys/bus/spi/drivers/fb_st7735r ./sys/bus/platform/drivers/fb_st7735r And if I do this root@Omega-:~# insmod fbtft_device Failed to find fbtft_device. Maybe it is a built in module ? (fbtft_device = “Module to for adding FBTFT devices” kernel config option)
          – utiq
          Dec 14 '17 at 22:33












          Hi @utiq, to list down the built-in modules, use lsmod command and try to verify if your module is present in there or not.
          – VivekD
          Dec 15 '17 at 11:14




          Hi @utiq, to list down the built-in modules, use lsmod command and try to verify if your module is present in there or not.
          – VivekD
          Dec 15 '17 at 11:14












          The same, it doesn't show the module when I do lsmod. The module *.ko should be in /proc/modules, right?
          – utiq
          Dec 15 '17 at 16:03






          The same, it doesn't show the module when I do lsmod. The module *.ko should be in /proc/modules, right?
          – utiq
          Dec 15 '17 at 16:03




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f410985%2fadding-modules-to-kernel-in-lede-distribution%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Morgemoulin

          Scott Moir

          Souastre