Wireless QCA9377 not working at 16.04

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








up vote
0
down vote

favorite












I'm not able to see my wifi device on my Lenovo Y520 notebook running Kubuntu 16.04 LTS. Even though it's not running, command ip link show shows that I have only lo, enp4s0, and wlp3s0. I tried to do sudo ifup wlp3s0 but it says "Unknown interface wlp3s0"



But, I've confirmed that the device works fine on PuppyLinux based on Xenial, which is funny. In Puppy, the device name is wlan0.



I did some comparison on the following command modinfo ath10k_pci on both OSes and the diff is only:



ichsan@future:~$ diff /tmp/ubuntu /tmp/puppy 
1c1
< filename: /lib/modules/4.10.0-28-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
---
> filename: /lib/modules/4.9.58/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
24d23
< srcversion: 50E531406EF702B9976A8A9
32a32,33
> alias: of:N*T*Cqcom,ipq4019-wifiC*
> alias: of:N*T*Cqcom,ipq4019-wifi
35c36
< vermagic: 4.10.0-28-generic SMP mod_unload
---
> vermagic: 4.9.58 SMP preempt mod_unload modversions


This is my wireless card details retrieved from my Ubuntu https://paste.ubuntu.com/p/mpDvkd4WZc/



This one is from my Puppy https://paste.ubuntu.com/p/ZFpm8NW5Hm/










share|improve this question























  • Are there any differences between /etc/modprobe.d/ directories of the 2 OS's?
    – Jeremy31
    Feb 17 at 12:40










  • You want me to compare filenames inside recursively? Or want me to compare the file size as well?
    – sancho21
    Feb 17 at 23:04










  • Just compare the contents of the files in that location, I suspect you might see blacklist ideapad_laptop on Puppy Linux
    – Jeremy31
    Feb 17 at 23:19










  • Checked on Puppy, it's not blacklisted
    – sancho21
    Feb 17 at 23:51














up vote
0
down vote

favorite












I'm not able to see my wifi device on my Lenovo Y520 notebook running Kubuntu 16.04 LTS. Even though it's not running, command ip link show shows that I have only lo, enp4s0, and wlp3s0. I tried to do sudo ifup wlp3s0 but it says "Unknown interface wlp3s0"



But, I've confirmed that the device works fine on PuppyLinux based on Xenial, which is funny. In Puppy, the device name is wlan0.



I did some comparison on the following command modinfo ath10k_pci on both OSes and the diff is only:



ichsan@future:~$ diff /tmp/ubuntu /tmp/puppy 
1c1
< filename: /lib/modules/4.10.0-28-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
---
> filename: /lib/modules/4.9.58/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
24d23
< srcversion: 50E531406EF702B9976A8A9
32a32,33
> alias: of:N*T*Cqcom,ipq4019-wifiC*
> alias: of:N*T*Cqcom,ipq4019-wifi
35c36
< vermagic: 4.10.0-28-generic SMP mod_unload
---
> vermagic: 4.9.58 SMP preempt mod_unload modversions


This is my wireless card details retrieved from my Ubuntu https://paste.ubuntu.com/p/mpDvkd4WZc/



This one is from my Puppy https://paste.ubuntu.com/p/ZFpm8NW5Hm/










share|improve this question























  • Are there any differences between /etc/modprobe.d/ directories of the 2 OS's?
    – Jeremy31
    Feb 17 at 12:40










  • You want me to compare filenames inside recursively? Or want me to compare the file size as well?
    – sancho21
    Feb 17 at 23:04










  • Just compare the contents of the files in that location, I suspect you might see blacklist ideapad_laptop on Puppy Linux
    – Jeremy31
    Feb 17 at 23:19










  • Checked on Puppy, it's not blacklisted
    – sancho21
    Feb 17 at 23:51












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I'm not able to see my wifi device on my Lenovo Y520 notebook running Kubuntu 16.04 LTS. Even though it's not running, command ip link show shows that I have only lo, enp4s0, and wlp3s0. I tried to do sudo ifup wlp3s0 but it says "Unknown interface wlp3s0"



But, I've confirmed that the device works fine on PuppyLinux based on Xenial, which is funny. In Puppy, the device name is wlan0.



I did some comparison on the following command modinfo ath10k_pci on both OSes and the diff is only:



ichsan@future:~$ diff /tmp/ubuntu /tmp/puppy 
1c1
< filename: /lib/modules/4.10.0-28-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
---
> filename: /lib/modules/4.9.58/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
24d23
< srcversion: 50E531406EF702B9976A8A9
32a32,33
> alias: of:N*T*Cqcom,ipq4019-wifiC*
> alias: of:N*T*Cqcom,ipq4019-wifi
35c36
< vermagic: 4.10.0-28-generic SMP mod_unload
---
> vermagic: 4.9.58 SMP preempt mod_unload modversions


This is my wireless card details retrieved from my Ubuntu https://paste.ubuntu.com/p/mpDvkd4WZc/



This one is from my Puppy https://paste.ubuntu.com/p/ZFpm8NW5Hm/










share|improve this question















I'm not able to see my wifi device on my Lenovo Y520 notebook running Kubuntu 16.04 LTS. Even though it's not running, command ip link show shows that I have only lo, enp4s0, and wlp3s0. I tried to do sudo ifup wlp3s0 but it says "Unknown interface wlp3s0"



But, I've confirmed that the device works fine on PuppyLinux based on Xenial, which is funny. In Puppy, the device name is wlan0.



I did some comparison on the following command modinfo ath10k_pci on both OSes and the diff is only:



ichsan@future:~$ diff /tmp/ubuntu /tmp/puppy 
1c1
< filename: /lib/modules/4.10.0-28-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
---
> filename: /lib/modules/4.9.58/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
24d23
< srcversion: 50E531406EF702B9976A8A9
32a32,33
> alias: of:N*T*Cqcom,ipq4019-wifiC*
> alias: of:N*T*Cqcom,ipq4019-wifi
35c36
< vermagic: 4.10.0-28-generic SMP mod_unload
---
> vermagic: 4.9.58 SMP preempt mod_unload modversions


This is my wireless card details retrieved from my Ubuntu https://paste.ubuntu.com/p/mpDvkd4WZc/



This one is from my Puppy https://paste.ubuntu.com/p/ZFpm8NW5Hm/







16.04 wireless atheros






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 17 at 12:44

























asked Feb 17 at 0:28









sancho21

1013




1013











  • Are there any differences between /etc/modprobe.d/ directories of the 2 OS's?
    – Jeremy31
    Feb 17 at 12:40










  • You want me to compare filenames inside recursively? Or want me to compare the file size as well?
    – sancho21
    Feb 17 at 23:04










  • Just compare the contents of the files in that location, I suspect you might see blacklist ideapad_laptop on Puppy Linux
    – Jeremy31
    Feb 17 at 23:19










  • Checked on Puppy, it's not blacklisted
    – sancho21
    Feb 17 at 23:51
















  • Are there any differences between /etc/modprobe.d/ directories of the 2 OS's?
    – Jeremy31
    Feb 17 at 12:40










  • You want me to compare filenames inside recursively? Or want me to compare the file size as well?
    – sancho21
    Feb 17 at 23:04










  • Just compare the contents of the files in that location, I suspect you might see blacklist ideapad_laptop on Puppy Linux
    – Jeremy31
    Feb 17 at 23:19










  • Checked on Puppy, it's not blacklisted
    – sancho21
    Feb 17 at 23:51















Are there any differences between /etc/modprobe.d/ directories of the 2 OS's?
– Jeremy31
Feb 17 at 12:40




Are there any differences between /etc/modprobe.d/ directories of the 2 OS's?
– Jeremy31
Feb 17 at 12:40












You want me to compare filenames inside recursively? Or want me to compare the file size as well?
– sancho21
Feb 17 at 23:04




You want me to compare filenames inside recursively? Or want me to compare the file size as well?
– sancho21
Feb 17 at 23:04












Just compare the contents of the files in that location, I suspect you might see blacklist ideapad_laptop on Puppy Linux
– Jeremy31
Feb 17 at 23:19




Just compare the contents of the files in that location, I suspect you might see blacklist ideapad_laptop on Puppy Linux
– Jeremy31
Feb 17 at 23:19












Checked on Puppy, it's not blacklisted
– sancho21
Feb 17 at 23:51




Checked on Puppy, it's not blacklisted
– sancho21
Feb 17 at 23:51










1 Answer
1






active

oldest

votes

















up vote
0
down vote













Suddenly it works. It seems that we just need to upgrade all packages with apt then restart. The device name will remain the same (not changed to wlan0)






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',
    convertImagesToLinks: true,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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%2faskubuntu.com%2fquestions%2f1006930%2fwireless-qca9377-not-working-at-16-04%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
    0
    down vote













    Suddenly it works. It seems that we just need to upgrade all packages with apt then restart. The device name will remain the same (not changed to wlan0)






    share|improve this answer
























      up vote
      0
      down vote













      Suddenly it works. It seems that we just need to upgrade all packages with apt then restart. The device name will remain the same (not changed to wlan0)






      share|improve this answer






















        up vote
        0
        down vote










        up vote
        0
        down vote









        Suddenly it works. It seems that we just need to upgrade all packages with apt then restart. The device name will remain the same (not changed to wlan0)






        share|improve this answer












        Suddenly it works. It seems that we just need to upgrade all packages with apt then restart. The device name will remain the same (not changed to wlan0)







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 18 at 0:46









        sancho21

        1013




        1013



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1006930%2fwireless-qca9377-not-working-at-16-04%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            pylint3 and pip3 broken

            Missing snmpget and snmpwalk

            How to enroll fingerprints to Ubuntu 17.10 with VFS491