Ubuntu 16.10 not recognising bnx2 network interfaces











up vote
1
down vote

favorite












I have a ProLiant DL360 g7 server that was running Ubuntu 14.04 LTS. I was trying to update the OpenSSH version, but without wanting, my server got upgraded to Ubuntu 16.10. Since then, I have "lost" my NIC cards as the ifconfig does not show them up.



The first thing that I found in google was that the NIC naming system has changed from eth0 to eno1.



When I do



sudo ifconfig eno1 up


I get the error:



Can't load firmware file “bnx2/bnx2-mips-09-6.2.1a.fw”
SIOCSIFFLAGS: No such file or directory


By doing



dmesg | grep bnx2


it recognises my 4 interfaces mentioning the old ethX naming and in the end:



Can't load firmware file “bnx2/bnx2-mips-09-6.2.1a.fw”


Then



ip link


shows:
my four interfaces with the new naming style: eno1, eno2, enp5s0f0 etc



I have also renamed the main interface in /etc/network/interfaces to correspond to eno1.



If i do



ifconfig eno1


I get what I would expect from ifconfig under normal situation: the right IP assigned in eno1 (i.e. inet, netmask, etc and all counters for packets and errors are 0)



locate bnx2/bnx2-mips-09-6.2.1a.fw


initially returned 1 path: /lib/firmware/bnx2/bnx2-mips-09-6.2.1a.fw. I copied this file, along with other bnx2 files, to:



/lib/firmware/3.2.0-55-generic/bnx2/bnx2-mips-09-6.2.1a.fw


Finally,



uname -r shows:


3.2.0-55-generic
and



cat /etc/lsb-release


mentions;
Ubuntu. 16.10, yakkety



I feel quite lost in what options I have. I believe the updated system is not recognising my NIC cards and I do not know what I should do.



Other people give a solution for Red Hat (bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw") which involves rebuilding the initramfs image in red Hat, but not sure whether this is the direction I should take or how this can be done in Ubuntu. Any help greatly appreciated.










share|improve this question




























    up vote
    1
    down vote

    favorite












    I have a ProLiant DL360 g7 server that was running Ubuntu 14.04 LTS. I was trying to update the OpenSSH version, but without wanting, my server got upgraded to Ubuntu 16.10. Since then, I have "lost" my NIC cards as the ifconfig does not show them up.



    The first thing that I found in google was that the NIC naming system has changed from eth0 to eno1.



    When I do



    sudo ifconfig eno1 up


    I get the error:



    Can't load firmware file “bnx2/bnx2-mips-09-6.2.1a.fw”
    SIOCSIFFLAGS: No such file or directory


    By doing



    dmesg | grep bnx2


    it recognises my 4 interfaces mentioning the old ethX naming and in the end:



    Can't load firmware file “bnx2/bnx2-mips-09-6.2.1a.fw”


    Then



    ip link


    shows:
    my four interfaces with the new naming style: eno1, eno2, enp5s0f0 etc



    I have also renamed the main interface in /etc/network/interfaces to correspond to eno1.



    If i do



    ifconfig eno1


    I get what I would expect from ifconfig under normal situation: the right IP assigned in eno1 (i.e. inet, netmask, etc and all counters for packets and errors are 0)



    locate bnx2/bnx2-mips-09-6.2.1a.fw


    initially returned 1 path: /lib/firmware/bnx2/bnx2-mips-09-6.2.1a.fw. I copied this file, along with other bnx2 files, to:



    /lib/firmware/3.2.0-55-generic/bnx2/bnx2-mips-09-6.2.1a.fw


    Finally,



    uname -r shows:


    3.2.0-55-generic
    and



    cat /etc/lsb-release


    mentions;
    Ubuntu. 16.10, yakkety



    I feel quite lost in what options I have. I believe the updated system is not recognising my NIC cards and I do not know what I should do.



    Other people give a solution for Red Hat (bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw") which involves rebuilding the initramfs image in red Hat, but not sure whether this is the direction I should take or how this can be done in Ubuntu. Any help greatly appreciated.










    share|improve this question


























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I have a ProLiant DL360 g7 server that was running Ubuntu 14.04 LTS. I was trying to update the OpenSSH version, but without wanting, my server got upgraded to Ubuntu 16.10. Since then, I have "lost" my NIC cards as the ifconfig does not show them up.



      The first thing that I found in google was that the NIC naming system has changed from eth0 to eno1.



      When I do



      sudo ifconfig eno1 up


      I get the error:



      Can't load firmware file “bnx2/bnx2-mips-09-6.2.1a.fw”
      SIOCSIFFLAGS: No such file or directory


      By doing



      dmesg | grep bnx2


      it recognises my 4 interfaces mentioning the old ethX naming and in the end:



      Can't load firmware file “bnx2/bnx2-mips-09-6.2.1a.fw”


      Then



      ip link


      shows:
      my four interfaces with the new naming style: eno1, eno2, enp5s0f0 etc



      I have also renamed the main interface in /etc/network/interfaces to correspond to eno1.



      If i do



      ifconfig eno1


      I get what I would expect from ifconfig under normal situation: the right IP assigned in eno1 (i.e. inet, netmask, etc and all counters for packets and errors are 0)



      locate bnx2/bnx2-mips-09-6.2.1a.fw


      initially returned 1 path: /lib/firmware/bnx2/bnx2-mips-09-6.2.1a.fw. I copied this file, along with other bnx2 files, to:



      /lib/firmware/3.2.0-55-generic/bnx2/bnx2-mips-09-6.2.1a.fw


      Finally,



      uname -r shows:


      3.2.0-55-generic
      and



      cat /etc/lsb-release


      mentions;
      Ubuntu. 16.10, yakkety



      I feel quite lost in what options I have. I believe the updated system is not recognising my NIC cards and I do not know what I should do.



      Other people give a solution for Red Hat (bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw") which involves rebuilding the initramfs image in red Hat, but not sure whether this is the direction I should take or how this can be done in Ubuntu. Any help greatly appreciated.










      share|improve this question















      I have a ProLiant DL360 g7 server that was running Ubuntu 14.04 LTS. I was trying to update the OpenSSH version, but without wanting, my server got upgraded to Ubuntu 16.10. Since then, I have "lost" my NIC cards as the ifconfig does not show them up.



      The first thing that I found in google was that the NIC naming system has changed from eth0 to eno1.



      When I do



      sudo ifconfig eno1 up


      I get the error:



      Can't load firmware file “bnx2/bnx2-mips-09-6.2.1a.fw”
      SIOCSIFFLAGS: No such file or directory


      By doing



      dmesg | grep bnx2


      it recognises my 4 interfaces mentioning the old ethX naming and in the end:



      Can't load firmware file “bnx2/bnx2-mips-09-6.2.1a.fw”


      Then



      ip link


      shows:
      my four interfaces with the new naming style: eno1, eno2, enp5s0f0 etc



      I have also renamed the main interface in /etc/network/interfaces to correspond to eno1.



      If i do



      ifconfig eno1


      I get what I would expect from ifconfig under normal situation: the right IP assigned in eno1 (i.e. inet, netmask, etc and all counters for packets and errors are 0)



      locate bnx2/bnx2-mips-09-6.2.1a.fw


      initially returned 1 path: /lib/firmware/bnx2/bnx2-mips-09-6.2.1a.fw. I copied this file, along with other bnx2 files, to:



      /lib/firmware/3.2.0-55-generic/bnx2/bnx2-mips-09-6.2.1a.fw


      Finally,



      uname -r shows:


      3.2.0-55-generic
      and



      cat /etc/lsb-release


      mentions;
      Ubuntu. 16.10, yakkety



      I feel quite lost in what options I have. I believe the updated system is not recognising my NIC cards and I do not know what I should do.



      Other people give a solution for Red Hat (bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw") which involves rebuilding the initramfs image in red Hat, but not sure whether this is the direction I should take or how this can be done in Ubuntu. Any help greatly appreciated.







      ubuntu network-interface firmware






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 13 '17 at 12:36









      Community

      1




      1










      asked Mar 9 '17 at 19:13









      Kostas

      64




      64






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          You're almost there. I had almost the same exact problem, except our server had a directory of /lib/firmware/bnx2x (note the extra "x"). I fixed it by creating
          mkdir /lib/firmware/bnx2 and then from your linked solution downloaded the bnx2-mips-09-6.2.1b.fw file into there and ran update-initramfs -u and rebooted and voila. Note that your error is looking for a filename slightly different, ending in 1a.fw, not 1b.fw.






          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: 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%2f350350%2fubuntu-16-10-not-recognising-bnx2-network-interfaces%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








            up vote
            0
            down vote













            You're almost there. I had almost the same exact problem, except our server had a directory of /lib/firmware/bnx2x (note the extra "x"). I fixed it by creating
            mkdir /lib/firmware/bnx2 and then from your linked solution downloaded the bnx2-mips-09-6.2.1b.fw file into there and ran update-initramfs -u and rebooted and voila. Note that your error is looking for a filename slightly different, ending in 1a.fw, not 1b.fw.






            share|improve this answer

























              up vote
              0
              down vote













              You're almost there. I had almost the same exact problem, except our server had a directory of /lib/firmware/bnx2x (note the extra "x"). I fixed it by creating
              mkdir /lib/firmware/bnx2 and then from your linked solution downloaded the bnx2-mips-09-6.2.1b.fw file into there and ran update-initramfs -u and rebooted and voila. Note that your error is looking for a filename slightly different, ending in 1a.fw, not 1b.fw.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                You're almost there. I had almost the same exact problem, except our server had a directory of /lib/firmware/bnx2x (note the extra "x"). I fixed it by creating
                mkdir /lib/firmware/bnx2 and then from your linked solution downloaded the bnx2-mips-09-6.2.1b.fw file into there and ran update-initramfs -u and rebooted and voila. Note that your error is looking for a filename slightly different, ending in 1a.fw, not 1b.fw.






                share|improve this answer












                You're almost there. I had almost the same exact problem, except our server had a directory of /lib/firmware/bnx2x (note the extra "x"). I fixed it by creating
                mkdir /lib/firmware/bnx2 and then from your linked solution downloaded the bnx2-mips-09-6.2.1b.fw file into there and ran update-initramfs -u and rebooted and voila. Note that your error is looking for a filename slightly different, ending in 1a.fw, not 1b.fw.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Apr 21 '17 at 13:29









                RobbieTheK

                135




                135






























                    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%2f350350%2fubuntu-16-10-not-recognising-bnx2-network-interfaces%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