Instal WiFi driver in Ubuntu





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















Today I just got into the world of Ubuntu but I cannot install the drivers for my WiFi dongle which is a Netgear A6210.



I noticed similar questions but I don't know how to proceed so I come here asking for help.



I don't really understand the procedure to follow in this "tutorial": https://github.com/jurobystricky/Netgear-A6210










share|improve this question




















  • 1





    What is the problem to follow the instructions on github? But I am afraid it won't work for modern Ubuntu releases. It is 3 years old.

    – Pilot6
    Feb 9 at 18:26




















0















Today I just got into the world of Ubuntu but I cannot install the drivers for my WiFi dongle which is a Netgear A6210.



I noticed similar questions but I don't know how to proceed so I come here asking for help.



I don't really understand the procedure to follow in this "tutorial": https://github.com/jurobystricky/Netgear-A6210










share|improve this question




















  • 1





    What is the problem to follow the instructions on github? But I am afraid it won't work for modern Ubuntu releases. It is 3 years old.

    – Pilot6
    Feb 9 at 18:26
















0












0








0








Today I just got into the world of Ubuntu but I cannot install the drivers for my WiFi dongle which is a Netgear A6210.



I noticed similar questions but I don't know how to proceed so I come here asking for help.



I don't really understand the procedure to follow in this "tutorial": https://github.com/jurobystricky/Netgear-A6210










share|improve this question
















Today I just got into the world of Ubuntu but I cannot install the drivers for my WiFi dongle which is a Netgear A6210.



I noticed similar questions but I don't know how to proceed so I come here asking for help.



I don't really understand the procedure to follow in this "tutorial": https://github.com/jurobystricky/Netgear-A6210







networking wireless






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 10 at 2:00









GabrielaGarcia

557212




557212










asked Feb 9 at 18:17









valval

1




1








  • 1





    What is the problem to follow the instructions on github? But I am afraid it won't work for modern Ubuntu releases. It is 3 years old.

    – Pilot6
    Feb 9 at 18:26
















  • 1





    What is the problem to follow the instructions on github? But I am afraid it won't work for modern Ubuntu releases. It is 3 years old.

    – Pilot6
    Feb 9 at 18:26










1




1





What is the problem to follow the instructions on github? But I am afraid it won't work for modern Ubuntu releases. It is 3 years old.

– Pilot6
Feb 9 at 18:26







What is the problem to follow the instructions on github? But I am afraid it won't work for modern Ubuntu releases. It is 3 years old.

– Pilot6
Feb 9 at 18:26












1 Answer
1






active

oldest

votes


















0














Unfortunately, you are going to have issues with this one as the code appears to be buggy. Your kernel most likely would have the "CONFIG_FORTIFY_SOURCE" option enabled. To verify this, run this command from a terminal:



cat /boot/config-`uname -r` | grep CONFIG_FORTIFY_SOURCE


Here is the output I got from mine:



CONFIG_FORTIFY_SOURCE=y


If you get the same output as mine, you won't be able to compile it that driver "as it is" due to buggy code:



In function ‘memcpy’,
inlined from ‘rt_ioctl_iwaplist’ at /home/marko/Desktop/Netgear-A6210/os/linux/../../os/linux/sta_ioctl.c:549:2:
./include/linux/string.h:340:4: error: call to ‘__read_overflow2’ declared with attribute error: detected read beyond size of object passed as 2nd parameter
__read_overflow2();


According to a user called genodeftest here:




This issue is a result of the new config option CONFIG_FORTIFY_SOURCE,
which acts like glibc’s FORTIFY_SOURCE in trying to detect some bugs
with memcpy at compile-time. As a very dirty workaround, you could
disable that config option.




and here:




Thanks to CONFIG_FORTIFY_SOURCE, the compiler refused to compile this
buggy code.




To disable that option, it would require you to recompile the kernel and this is not a simple task for novices. I do not advise you to disable that option.



My suggestion is to keep an eye until someone fixes the error.






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%2f1116971%2finstal-wifi-driver-in-ubuntu%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














    Unfortunately, you are going to have issues with this one as the code appears to be buggy. Your kernel most likely would have the "CONFIG_FORTIFY_SOURCE" option enabled. To verify this, run this command from a terminal:



    cat /boot/config-`uname -r` | grep CONFIG_FORTIFY_SOURCE


    Here is the output I got from mine:



    CONFIG_FORTIFY_SOURCE=y


    If you get the same output as mine, you won't be able to compile it that driver "as it is" due to buggy code:



    In function ‘memcpy’,
    inlined from ‘rt_ioctl_iwaplist’ at /home/marko/Desktop/Netgear-A6210/os/linux/../../os/linux/sta_ioctl.c:549:2:
    ./include/linux/string.h:340:4: error: call to ‘__read_overflow2’ declared with attribute error: detected read beyond size of object passed as 2nd parameter
    __read_overflow2();


    According to a user called genodeftest here:




    This issue is a result of the new config option CONFIG_FORTIFY_SOURCE,
    which acts like glibc’s FORTIFY_SOURCE in trying to detect some bugs
    with memcpy at compile-time. As a very dirty workaround, you could
    disable that config option.




    and here:




    Thanks to CONFIG_FORTIFY_SOURCE, the compiler refused to compile this
    buggy code.




    To disable that option, it would require you to recompile the kernel and this is not a simple task for novices. I do not advise you to disable that option.



    My suggestion is to keep an eye until someone fixes the error.






    share|improve this answer




























      0














      Unfortunately, you are going to have issues with this one as the code appears to be buggy. Your kernel most likely would have the "CONFIG_FORTIFY_SOURCE" option enabled. To verify this, run this command from a terminal:



      cat /boot/config-`uname -r` | grep CONFIG_FORTIFY_SOURCE


      Here is the output I got from mine:



      CONFIG_FORTIFY_SOURCE=y


      If you get the same output as mine, you won't be able to compile it that driver "as it is" due to buggy code:



      In function ‘memcpy’,
      inlined from ‘rt_ioctl_iwaplist’ at /home/marko/Desktop/Netgear-A6210/os/linux/../../os/linux/sta_ioctl.c:549:2:
      ./include/linux/string.h:340:4: error: call to ‘__read_overflow2’ declared with attribute error: detected read beyond size of object passed as 2nd parameter
      __read_overflow2();


      According to a user called genodeftest here:




      This issue is a result of the new config option CONFIG_FORTIFY_SOURCE,
      which acts like glibc’s FORTIFY_SOURCE in trying to detect some bugs
      with memcpy at compile-time. As a very dirty workaround, you could
      disable that config option.




      and here:




      Thanks to CONFIG_FORTIFY_SOURCE, the compiler refused to compile this
      buggy code.




      To disable that option, it would require you to recompile the kernel and this is not a simple task for novices. I do not advise you to disable that option.



      My suggestion is to keep an eye until someone fixes the error.






      share|improve this answer


























        0












        0








        0







        Unfortunately, you are going to have issues with this one as the code appears to be buggy. Your kernel most likely would have the "CONFIG_FORTIFY_SOURCE" option enabled. To verify this, run this command from a terminal:



        cat /boot/config-`uname -r` | grep CONFIG_FORTIFY_SOURCE


        Here is the output I got from mine:



        CONFIG_FORTIFY_SOURCE=y


        If you get the same output as mine, you won't be able to compile it that driver "as it is" due to buggy code:



        In function ‘memcpy’,
        inlined from ‘rt_ioctl_iwaplist’ at /home/marko/Desktop/Netgear-A6210/os/linux/../../os/linux/sta_ioctl.c:549:2:
        ./include/linux/string.h:340:4: error: call to ‘__read_overflow2’ declared with attribute error: detected read beyond size of object passed as 2nd parameter
        __read_overflow2();


        According to a user called genodeftest here:




        This issue is a result of the new config option CONFIG_FORTIFY_SOURCE,
        which acts like glibc’s FORTIFY_SOURCE in trying to detect some bugs
        with memcpy at compile-time. As a very dirty workaround, you could
        disable that config option.




        and here:




        Thanks to CONFIG_FORTIFY_SOURCE, the compiler refused to compile this
        buggy code.




        To disable that option, it would require you to recompile the kernel and this is not a simple task for novices. I do not advise you to disable that option.



        My suggestion is to keep an eye until someone fixes the error.






        share|improve this answer













        Unfortunately, you are going to have issues with this one as the code appears to be buggy. Your kernel most likely would have the "CONFIG_FORTIFY_SOURCE" option enabled. To verify this, run this command from a terminal:



        cat /boot/config-`uname -r` | grep CONFIG_FORTIFY_SOURCE


        Here is the output I got from mine:



        CONFIG_FORTIFY_SOURCE=y


        If you get the same output as mine, you won't be able to compile it that driver "as it is" due to buggy code:



        In function ‘memcpy’,
        inlined from ‘rt_ioctl_iwaplist’ at /home/marko/Desktop/Netgear-A6210/os/linux/../../os/linux/sta_ioctl.c:549:2:
        ./include/linux/string.h:340:4: error: call to ‘__read_overflow2’ declared with attribute error: detected read beyond size of object passed as 2nd parameter
        __read_overflow2();


        According to a user called genodeftest here:




        This issue is a result of the new config option CONFIG_FORTIFY_SOURCE,
        which acts like glibc’s FORTIFY_SOURCE in trying to detect some bugs
        with memcpy at compile-time. As a very dirty workaround, you could
        disable that config option.




        and here:




        Thanks to CONFIG_FORTIFY_SOURCE, the compiler refused to compile this
        buggy code.




        To disable that option, it would require you to recompile the kernel and this is not a simple task for novices. I do not advise you to disable that option.



        My suggestion is to keep an eye until someone fixes the error.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 10 at 3:51









        markomarko

        56717




        56717






























            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%2f1116971%2finstal-wifi-driver-in-ubuntu%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

            Human spaceflight

            Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

            張江高科駅