Is “update-initramfs -u” needed after adding or removing a module with “modprobe”?

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











up vote
0
down vote

favorite












Most instructions that I find online about adding or replacing kernel modules in Ubuntu only mention modprobe and rmmod. However, according my experience with e1000e, the modification is reverted after reboot unless I do update-initramfs -u afterwards. The man page of update-initramfs does not mention modules.



So, is it always necessary to run update-initramfs -u after replacing kernel modules if I want to have the modified kernel after reboot?







share|improve this question






















  • Using the /etc/modprobe.d directory is also an option.
    – Raman Sailopal
    Feb 16 at 13:44














up vote
0
down vote

favorite












Most instructions that I find online about adding or replacing kernel modules in Ubuntu only mention modprobe and rmmod. However, according my experience with e1000e, the modification is reverted after reboot unless I do update-initramfs -u afterwards. The man page of update-initramfs does not mention modules.



So, is it always necessary to run update-initramfs -u after replacing kernel modules if I want to have the modified kernel after reboot?







share|improve this question






















  • Using the /etc/modprobe.d directory is also an option.
    – Raman Sailopal
    Feb 16 at 13:44












up vote
0
down vote

favorite









up vote
0
down vote

favorite











Most instructions that I find online about adding or replacing kernel modules in Ubuntu only mention modprobe and rmmod. However, according my experience with e1000e, the modification is reverted after reboot unless I do update-initramfs -u afterwards. The man page of update-initramfs does not mention modules.



So, is it always necessary to run update-initramfs -u after replacing kernel modules if I want to have the modified kernel after reboot?







share|improve this question














Most instructions that I find online about adding or replacing kernel modules in Ubuntu only mention modprobe and rmmod. However, according my experience with e1000e, the modification is reverted after reboot unless I do update-initramfs -u afterwards. The man page of update-initramfs does not mention modules.



So, is it always necessary to run update-initramfs -u after replacing kernel modules if I want to have the modified kernel after reboot?









share|improve this question













share|improve this question




share|improve this question








edited Feb 16 at 14:51

























asked Feb 16 at 13:03









Alexey

3811517




3811517











  • Using the /etc/modprobe.d directory is also an option.
    – Raman Sailopal
    Feb 16 at 13:44
















  • Using the /etc/modprobe.d directory is also an option.
    – Raman Sailopal
    Feb 16 at 13:44















Using the /etc/modprobe.d directory is also an option.
– Raman Sailopal
Feb 16 at 13:44




Using the /etc/modprobe.d directory is also an option.
– Raman Sailopal
Feb 16 at 13:44










1 Answer
1






active

oldest

votes

















up vote
1
down vote













I guess this is about some Linux distribution that is part of the Debian/Ubuntu family, as update-initramfs is part of Debian initramfs-tools.



If the module (and the command to load it) is included in initramfs, then update-initramfs -u is needed: if you don't do it, initramfs will still contain the old state (= old version of the module and the command to load it).



If you are uncertain whether or not the module is included in initramfs, use the lsinitramfs command to view the contents of your initramfs. For example:



$ lsinitramfs /boot/initrd.img-4.9.0-5-amd64 |less


However, running update-initramfs -u should generally never hurt, so if you are uncertain, you can just run it to err on the safe side.






share|improve this answer




















    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%2f424599%2fis-update-initramfs-u-needed-after-adding-or-removing-a-module-with-modprobe%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
    1
    down vote













    I guess this is about some Linux distribution that is part of the Debian/Ubuntu family, as update-initramfs is part of Debian initramfs-tools.



    If the module (and the command to load it) is included in initramfs, then update-initramfs -u is needed: if you don't do it, initramfs will still contain the old state (= old version of the module and the command to load it).



    If you are uncertain whether or not the module is included in initramfs, use the lsinitramfs command to view the contents of your initramfs. For example:



    $ lsinitramfs /boot/initrd.img-4.9.0-5-amd64 |less


    However, running update-initramfs -u should generally never hurt, so if you are uncertain, you can just run it to err on the safe side.






    share|improve this answer
























      up vote
      1
      down vote













      I guess this is about some Linux distribution that is part of the Debian/Ubuntu family, as update-initramfs is part of Debian initramfs-tools.



      If the module (and the command to load it) is included in initramfs, then update-initramfs -u is needed: if you don't do it, initramfs will still contain the old state (= old version of the module and the command to load it).



      If you are uncertain whether or not the module is included in initramfs, use the lsinitramfs command to view the contents of your initramfs. For example:



      $ lsinitramfs /boot/initrd.img-4.9.0-5-amd64 |less


      However, running update-initramfs -u should generally never hurt, so if you are uncertain, you can just run it to err on the safe side.






      share|improve this answer






















        up vote
        1
        down vote










        up vote
        1
        down vote









        I guess this is about some Linux distribution that is part of the Debian/Ubuntu family, as update-initramfs is part of Debian initramfs-tools.



        If the module (and the command to load it) is included in initramfs, then update-initramfs -u is needed: if you don't do it, initramfs will still contain the old state (= old version of the module and the command to load it).



        If you are uncertain whether or not the module is included in initramfs, use the lsinitramfs command to view the contents of your initramfs. For example:



        $ lsinitramfs /boot/initrd.img-4.9.0-5-amd64 |less


        However, running update-initramfs -u should generally never hurt, so if you are uncertain, you can just run it to err on the safe side.






        share|improve this answer












        I guess this is about some Linux distribution that is part of the Debian/Ubuntu family, as update-initramfs is part of Debian initramfs-tools.



        If the module (and the command to load it) is included in initramfs, then update-initramfs -u is needed: if you don't do it, initramfs will still contain the old state (= old version of the module and the command to load it).



        If you are uncertain whether or not the module is included in initramfs, use the lsinitramfs command to view the contents of your initramfs. For example:



        $ lsinitramfs /boot/initrd.img-4.9.0-5-amd64 |less


        However, running update-initramfs -u should generally never hurt, so if you are uncertain, you can just run it to err on the safe side.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 16 at 13:20









        telcoM

        10.7k11132




        10.7k11132






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f424599%2fis-update-initramfs-u-needed-after-adding-or-removing-a-module-with-modprobe%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?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?