Rebuilding a kernel module(driver) with debugging












1















I have been trying for the past day to rebuild my iwlwifi modules with debugging enabled. The way to do this is to build with the .config param CONFIG_IWLWIFI_DEBUG=y. If I was building a new kernel this would be easy, but I want to keep using the installed ubuntu kernel. At the moment I don’t care about installing the modules. I just want to see the .ko files build, insmod them, and check for /sys/modules/iwlwifi/parameters/debug which should exist if the modules are built for debugging. What’s the official ubuntu way of doing this?



So far, this is what I’m doing:



My kernel is 4.15.0-43-generic, headers are already installed in /usr/src/linux-headers-4.15.0-43-generic




  1. Installed /usr/src/linux-source-4.15.0 with apt-get and unpacked it to ~/


  2. Set CONFIG_IWLWIFI_DEBUG=y in ~/linux-4.15.0/.config and /usr/src/linux-headers-4.15.0-43-generic/.config because I’m not sure which would be used.


  3. In ~/linux-4.15.0/drivers/net/.../iwlwifi, I run make -C /lib/modules/$(uname -r)/build M=$(pwd) modules


  4. ko modules build, but they aren’t debug-enabled











share|improve this question



























    1















    I have been trying for the past day to rebuild my iwlwifi modules with debugging enabled. The way to do this is to build with the .config param CONFIG_IWLWIFI_DEBUG=y. If I was building a new kernel this would be easy, but I want to keep using the installed ubuntu kernel. At the moment I don’t care about installing the modules. I just want to see the .ko files build, insmod them, and check for /sys/modules/iwlwifi/parameters/debug which should exist if the modules are built for debugging. What’s the official ubuntu way of doing this?



    So far, this is what I’m doing:



    My kernel is 4.15.0-43-generic, headers are already installed in /usr/src/linux-headers-4.15.0-43-generic




    1. Installed /usr/src/linux-source-4.15.0 with apt-get and unpacked it to ~/


    2. Set CONFIG_IWLWIFI_DEBUG=y in ~/linux-4.15.0/.config and /usr/src/linux-headers-4.15.0-43-generic/.config because I’m not sure which would be used.


    3. In ~/linux-4.15.0/drivers/net/.../iwlwifi, I run make -C /lib/modules/$(uname -r)/build M=$(pwd) modules


    4. ko modules build, but they aren’t debug-enabled











    share|improve this question

























      1












      1








      1








      I have been trying for the past day to rebuild my iwlwifi modules with debugging enabled. The way to do this is to build with the .config param CONFIG_IWLWIFI_DEBUG=y. If I was building a new kernel this would be easy, but I want to keep using the installed ubuntu kernel. At the moment I don’t care about installing the modules. I just want to see the .ko files build, insmod them, and check for /sys/modules/iwlwifi/parameters/debug which should exist if the modules are built for debugging. What’s the official ubuntu way of doing this?



      So far, this is what I’m doing:



      My kernel is 4.15.0-43-generic, headers are already installed in /usr/src/linux-headers-4.15.0-43-generic




      1. Installed /usr/src/linux-source-4.15.0 with apt-get and unpacked it to ~/


      2. Set CONFIG_IWLWIFI_DEBUG=y in ~/linux-4.15.0/.config and /usr/src/linux-headers-4.15.0-43-generic/.config because I’m not sure which would be used.


      3. In ~/linux-4.15.0/drivers/net/.../iwlwifi, I run make -C /lib/modules/$(uname -r)/build M=$(pwd) modules


      4. ko modules build, but they aren’t debug-enabled











      share|improve this question














      I have been trying for the past day to rebuild my iwlwifi modules with debugging enabled. The way to do this is to build with the .config param CONFIG_IWLWIFI_DEBUG=y. If I was building a new kernel this would be easy, but I want to keep using the installed ubuntu kernel. At the moment I don’t care about installing the modules. I just want to see the .ko files build, insmod them, and check for /sys/modules/iwlwifi/parameters/debug which should exist if the modules are built for debugging. What’s the official ubuntu way of doing this?



      So far, this is what I’m doing:



      My kernel is 4.15.0-43-generic, headers are already installed in /usr/src/linux-headers-4.15.0-43-generic




      1. Installed /usr/src/linux-source-4.15.0 with apt-get and unpacked it to ~/


      2. Set CONFIG_IWLWIFI_DEBUG=y in ~/linux-4.15.0/.config and /usr/src/linux-headers-4.15.0-43-generic/.config because I’m not sure which would be used.


      3. In ~/linux-4.15.0/drivers/net/.../iwlwifi, I run make -C /lib/modules/$(uname -r)/build M=$(pwd) modules


      4. ko modules build, but they aren’t debug-enabled








      drivers kernel






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 15 at 17:49









      zallikzallik

      62




      62






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Turns out I needed to run make scripts in the headers dir. It exits with failure, but I guess it does whatever it needs to with the build params first.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            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: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            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%2faskubuntu.com%2fquestions%2f1110016%2frebuilding-a-kernel-moduledriver-with-debugging%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














            Turns out I needed to run make scripts in the headers dir. It exits with failure, but I guess it does whatever it needs to with the build params first.






            share|improve this answer




























              0














              Turns out I needed to run make scripts in the headers dir. It exits with failure, but I guess it does whatever it needs to with the build params first.






              share|improve this answer


























                0












                0








                0







                Turns out I needed to run make scripts in the headers dir. It exits with failure, but I guess it does whatever it needs to with the build params first.






                share|improve this answer













                Turns out I needed to run make scripts in the headers dir. It exits with failure, but I guess it does whatever it needs to with the build params first.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 16 at 6:07









                zallikzallik

                62




                62






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • 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%2faskubuntu.com%2fquestions%2f1110016%2frebuilding-a-kernel-moduledriver-with-debugging%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

                    數位音樂下載

                    When can things happen in Etherscan, such as the picture below?

                    格利澤436b