Wi-Fi stopped working on Ubuntu 18.10 with Linux 4.18.0-12












1














After Linux upgraded from 4.18.0-11-generic to 4.18.0-12-generic on my Ubuntu 18.10 network connection stopped working and on Wi-Fi settings the message: "No Wi-Fi adapter found" is shown. I can still get the connection working by selecting Linux 4.18.0-11 from the startup menu. I have ASUS Vivobook Flip 15 laptop with no Ethernet adapter available so I must get the connection working either via Wi-Fi or Bluetooth.



Ubuntu 18.04 LTS did not work for my laptop because of Wi-Fi adapter was not recognized, but Ubuntu 18.10 did work before this latest upgrade.



Network controller (apparently):
Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter



Solution: after disabling secure boot via Asus BIOS utility (boot options, scroll down with touchpad to the secure boot option, disable) and rebooting the Wi-Fi adapter started working.



Thanks, @chili555



I noticed this has already been reported as a bug here: RTL8822BE WiFi Disabled in Kernel 4.18.0-12










share|improve this question
























  • When you are booted into the later kernel, does the driver load? lsmod | grep 8822 Are there any clues in the log? dmesg | grep 8822 Welcome to Ask Ubuntu.
    – chili555
    Dec 7 '18 at 15:27










  • lsmod | grep 8822 for 4.18.0-12 was empty, for 4.18.0-11 it was: r8822be 860160 0 mac80211 794624 1 r8822be cfg80211 663552 2 mac80211,r8822be dmesg | grep 8822 for 4.18.0.12 apparently contained only Bluetooth information but for 4.18.0-11: r8822be: module is from the staging directory, the quality is unknown, you have been warned. r8822be 0000:02:00.0: enabling device (0000 -> 0003) r8822be: Using firmware rtlwifi/rtl8822befw.bin r8822be: rtlwifi: wireless switch is on r8822be 0000:02:00.0 wlp2s0: renamed from wlan0 @chili555
    – Eliezer
    Dec 7 '18 at 15:53












  • While booted into -12, load the module and check the log: sudo modprobe r8822be && dmesg | grep 8822 I suspect we'll see an interesting clue.
    – chili555
    Dec 7 '18 at 17:11










  • modprobe: ERROR: could not insert 'r8822be': Operation not permitted
    – Eliezer
    Dec 7 '18 at 17:33










  • You did use sudo, correct? Does the module exist in your -12 version? sudo updatedb && locate r8822be.ko
    – chili555
    Dec 7 '18 at 19:44
















1














After Linux upgraded from 4.18.0-11-generic to 4.18.0-12-generic on my Ubuntu 18.10 network connection stopped working and on Wi-Fi settings the message: "No Wi-Fi adapter found" is shown. I can still get the connection working by selecting Linux 4.18.0-11 from the startup menu. I have ASUS Vivobook Flip 15 laptop with no Ethernet adapter available so I must get the connection working either via Wi-Fi or Bluetooth.



Ubuntu 18.04 LTS did not work for my laptop because of Wi-Fi adapter was not recognized, but Ubuntu 18.10 did work before this latest upgrade.



Network controller (apparently):
Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter



Solution: after disabling secure boot via Asus BIOS utility (boot options, scroll down with touchpad to the secure boot option, disable) and rebooting the Wi-Fi adapter started working.



Thanks, @chili555



I noticed this has already been reported as a bug here: RTL8822BE WiFi Disabled in Kernel 4.18.0-12










share|improve this question
























  • When you are booted into the later kernel, does the driver load? lsmod | grep 8822 Are there any clues in the log? dmesg | grep 8822 Welcome to Ask Ubuntu.
    – chili555
    Dec 7 '18 at 15:27










  • lsmod | grep 8822 for 4.18.0-12 was empty, for 4.18.0-11 it was: r8822be 860160 0 mac80211 794624 1 r8822be cfg80211 663552 2 mac80211,r8822be dmesg | grep 8822 for 4.18.0.12 apparently contained only Bluetooth information but for 4.18.0-11: r8822be: module is from the staging directory, the quality is unknown, you have been warned. r8822be 0000:02:00.0: enabling device (0000 -> 0003) r8822be: Using firmware rtlwifi/rtl8822befw.bin r8822be: rtlwifi: wireless switch is on r8822be 0000:02:00.0 wlp2s0: renamed from wlan0 @chili555
    – Eliezer
    Dec 7 '18 at 15:53












  • While booted into -12, load the module and check the log: sudo modprobe r8822be && dmesg | grep 8822 I suspect we'll see an interesting clue.
    – chili555
    Dec 7 '18 at 17:11










  • modprobe: ERROR: could not insert 'r8822be': Operation not permitted
    – Eliezer
    Dec 7 '18 at 17:33










  • You did use sudo, correct? Does the module exist in your -12 version? sudo updatedb && locate r8822be.ko
    – chili555
    Dec 7 '18 at 19:44














1












1








1







After Linux upgraded from 4.18.0-11-generic to 4.18.0-12-generic on my Ubuntu 18.10 network connection stopped working and on Wi-Fi settings the message: "No Wi-Fi adapter found" is shown. I can still get the connection working by selecting Linux 4.18.0-11 from the startup menu. I have ASUS Vivobook Flip 15 laptop with no Ethernet adapter available so I must get the connection working either via Wi-Fi or Bluetooth.



Ubuntu 18.04 LTS did not work for my laptop because of Wi-Fi adapter was not recognized, but Ubuntu 18.10 did work before this latest upgrade.



Network controller (apparently):
Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter



Solution: after disabling secure boot via Asus BIOS utility (boot options, scroll down with touchpad to the secure boot option, disable) and rebooting the Wi-Fi adapter started working.



Thanks, @chili555



I noticed this has already been reported as a bug here: RTL8822BE WiFi Disabled in Kernel 4.18.0-12










share|improve this question















After Linux upgraded from 4.18.0-11-generic to 4.18.0-12-generic on my Ubuntu 18.10 network connection stopped working and on Wi-Fi settings the message: "No Wi-Fi adapter found" is shown. I can still get the connection working by selecting Linux 4.18.0-11 from the startup menu. I have ASUS Vivobook Flip 15 laptop with no Ethernet adapter available so I must get the connection working either via Wi-Fi or Bluetooth.



Ubuntu 18.04 LTS did not work for my laptop because of Wi-Fi adapter was not recognized, but Ubuntu 18.10 did work before this latest upgrade.



Network controller (apparently):
Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter



Solution: after disabling secure boot via Asus BIOS utility (boot options, scroll down with touchpad to the secure boot option, disable) and rebooting the Wi-Fi adapter started working.



Thanks, @chili555



I noticed this has already been reported as a bug here: RTL8822BE WiFi Disabled in Kernel 4.18.0-12







networking wireless 18.10






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 9 '18 at 8:01







Eliezer

















asked Dec 7 '18 at 15:22









EliezerEliezer

105




105












  • When you are booted into the later kernel, does the driver load? lsmod | grep 8822 Are there any clues in the log? dmesg | grep 8822 Welcome to Ask Ubuntu.
    – chili555
    Dec 7 '18 at 15:27










  • lsmod | grep 8822 for 4.18.0-12 was empty, for 4.18.0-11 it was: r8822be 860160 0 mac80211 794624 1 r8822be cfg80211 663552 2 mac80211,r8822be dmesg | grep 8822 for 4.18.0.12 apparently contained only Bluetooth information but for 4.18.0-11: r8822be: module is from the staging directory, the quality is unknown, you have been warned. r8822be 0000:02:00.0: enabling device (0000 -> 0003) r8822be: Using firmware rtlwifi/rtl8822befw.bin r8822be: rtlwifi: wireless switch is on r8822be 0000:02:00.0 wlp2s0: renamed from wlan0 @chili555
    – Eliezer
    Dec 7 '18 at 15:53












  • While booted into -12, load the module and check the log: sudo modprobe r8822be && dmesg | grep 8822 I suspect we'll see an interesting clue.
    – chili555
    Dec 7 '18 at 17:11










  • modprobe: ERROR: could not insert 'r8822be': Operation not permitted
    – Eliezer
    Dec 7 '18 at 17:33










  • You did use sudo, correct? Does the module exist in your -12 version? sudo updatedb && locate r8822be.ko
    – chili555
    Dec 7 '18 at 19:44


















  • When you are booted into the later kernel, does the driver load? lsmod | grep 8822 Are there any clues in the log? dmesg | grep 8822 Welcome to Ask Ubuntu.
    – chili555
    Dec 7 '18 at 15:27










  • lsmod | grep 8822 for 4.18.0-12 was empty, for 4.18.0-11 it was: r8822be 860160 0 mac80211 794624 1 r8822be cfg80211 663552 2 mac80211,r8822be dmesg | grep 8822 for 4.18.0.12 apparently contained only Bluetooth information but for 4.18.0-11: r8822be: module is from the staging directory, the quality is unknown, you have been warned. r8822be 0000:02:00.0: enabling device (0000 -> 0003) r8822be: Using firmware rtlwifi/rtl8822befw.bin r8822be: rtlwifi: wireless switch is on r8822be 0000:02:00.0 wlp2s0: renamed from wlan0 @chili555
    – Eliezer
    Dec 7 '18 at 15:53












  • While booted into -12, load the module and check the log: sudo modprobe r8822be && dmesg | grep 8822 I suspect we'll see an interesting clue.
    – chili555
    Dec 7 '18 at 17:11










  • modprobe: ERROR: could not insert 'r8822be': Operation not permitted
    – Eliezer
    Dec 7 '18 at 17:33










  • You did use sudo, correct? Does the module exist in your -12 version? sudo updatedb && locate r8822be.ko
    – chili555
    Dec 7 '18 at 19:44
















When you are booted into the later kernel, does the driver load? lsmod | grep 8822 Are there any clues in the log? dmesg | grep 8822 Welcome to Ask Ubuntu.
– chili555
Dec 7 '18 at 15:27




When you are booted into the later kernel, does the driver load? lsmod | grep 8822 Are there any clues in the log? dmesg | grep 8822 Welcome to Ask Ubuntu.
– chili555
Dec 7 '18 at 15:27












lsmod | grep 8822 for 4.18.0-12 was empty, for 4.18.0-11 it was: r8822be 860160 0 mac80211 794624 1 r8822be cfg80211 663552 2 mac80211,r8822be dmesg | grep 8822 for 4.18.0.12 apparently contained only Bluetooth information but for 4.18.0-11: r8822be: module is from the staging directory, the quality is unknown, you have been warned. r8822be 0000:02:00.0: enabling device (0000 -> 0003) r8822be: Using firmware rtlwifi/rtl8822befw.bin r8822be: rtlwifi: wireless switch is on r8822be 0000:02:00.0 wlp2s0: renamed from wlan0 @chili555
– Eliezer
Dec 7 '18 at 15:53






lsmod | grep 8822 for 4.18.0-12 was empty, for 4.18.0-11 it was: r8822be 860160 0 mac80211 794624 1 r8822be cfg80211 663552 2 mac80211,r8822be dmesg | grep 8822 for 4.18.0.12 apparently contained only Bluetooth information but for 4.18.0-11: r8822be: module is from the staging directory, the quality is unknown, you have been warned. r8822be 0000:02:00.0: enabling device (0000 -> 0003) r8822be: Using firmware rtlwifi/rtl8822befw.bin r8822be: rtlwifi: wireless switch is on r8822be 0000:02:00.0 wlp2s0: renamed from wlan0 @chili555
– Eliezer
Dec 7 '18 at 15:53














While booted into -12, load the module and check the log: sudo modprobe r8822be && dmesg | grep 8822 I suspect we'll see an interesting clue.
– chili555
Dec 7 '18 at 17:11




While booted into -12, load the module and check the log: sudo modprobe r8822be && dmesg | grep 8822 I suspect we'll see an interesting clue.
– chili555
Dec 7 '18 at 17:11












modprobe: ERROR: could not insert 'r8822be': Operation not permitted
– Eliezer
Dec 7 '18 at 17:33




modprobe: ERROR: could not insert 'r8822be': Operation not permitted
– Eliezer
Dec 7 '18 at 17:33












You did use sudo, correct? Does the module exist in your -12 version? sudo updatedb && locate r8822be.ko
– chili555
Dec 7 '18 at 19:44




You did use sudo, correct? Does the module exist in your -12 version? sudo updatedb && locate r8822be.ko
– chili555
Dec 7 '18 at 19:44










2 Answers
2






active

oldest

votes


















1














We found, by investigation, that secure boot was turned on in your BIOS but that turning it off restored the wireless.



In the standard Ubuntu installation, all modules are supposed to be signed, therefor satifying secure boot. It appears that r8822be is either not signed or is improperly signed. I suggest that you register and file a bug report: https://bugs.launchpad.net/ubuntu






share|improve this answer





















  • It seemed to be reported already: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806472
    – Eliezer
    Dec 9 '18 at 8:07



















0














I think this may be more complex. I've just updated kernel in 18.04 to 4.18 generic and it's having similar issues (although driver is loaded and ip a shows the interface as down)



Looking at ifquery it seems wlps03 is not registered, despite showing in ip a I'm just going back to older 4.x kernel, but weirdly plugging in ethernet brings up WiFi & ethernet.



This is with an realtek WiFi+gigabit ethernet (shakes fist at realtek).



I also checked lsmod, WiFi driver is loaded...






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%2f1099200%2fwi-fi-stopped-working-on-ubuntu-18-10-with-linux-4-18-0-12%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    We found, by investigation, that secure boot was turned on in your BIOS but that turning it off restored the wireless.



    In the standard Ubuntu installation, all modules are supposed to be signed, therefor satifying secure boot. It appears that r8822be is either not signed or is improperly signed. I suggest that you register and file a bug report: https://bugs.launchpad.net/ubuntu






    share|improve this answer





















    • It seemed to be reported already: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806472
      – Eliezer
      Dec 9 '18 at 8:07
















    1














    We found, by investigation, that secure boot was turned on in your BIOS but that turning it off restored the wireless.



    In the standard Ubuntu installation, all modules are supposed to be signed, therefor satifying secure boot. It appears that r8822be is either not signed or is improperly signed. I suggest that you register and file a bug report: https://bugs.launchpad.net/ubuntu






    share|improve this answer





















    • It seemed to be reported already: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806472
      – Eliezer
      Dec 9 '18 at 8:07














    1












    1








    1






    We found, by investigation, that secure boot was turned on in your BIOS but that turning it off restored the wireless.



    In the standard Ubuntu installation, all modules are supposed to be signed, therefor satifying secure boot. It appears that r8822be is either not signed or is improperly signed. I suggest that you register and file a bug report: https://bugs.launchpad.net/ubuntu






    share|improve this answer












    We found, by investigation, that secure boot was turned on in your BIOS but that turning it off restored the wireless.



    In the standard Ubuntu installation, all modules are supposed to be signed, therefor satifying secure boot. It appears that r8822be is either not signed or is improperly signed. I suggest that you register and file a bug report: https://bugs.launchpad.net/ubuntu







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Dec 8 '18 at 20:54









    chili555chili555

    38.2k55177




    38.2k55177












    • It seemed to be reported already: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806472
      – Eliezer
      Dec 9 '18 at 8:07


















    • It seemed to be reported already: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806472
      – Eliezer
      Dec 9 '18 at 8:07
















    It seemed to be reported already: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806472
    – Eliezer
    Dec 9 '18 at 8:07




    It seemed to be reported already: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806472
    – Eliezer
    Dec 9 '18 at 8:07













    0














    I think this may be more complex. I've just updated kernel in 18.04 to 4.18 generic and it's having similar issues (although driver is loaded and ip a shows the interface as down)



    Looking at ifquery it seems wlps03 is not registered, despite showing in ip a I'm just going back to older 4.x kernel, but weirdly plugging in ethernet brings up WiFi & ethernet.



    This is with an realtek WiFi+gigabit ethernet (shakes fist at realtek).



    I also checked lsmod, WiFi driver is loaded...






    share|improve this answer


























      0














      I think this may be more complex. I've just updated kernel in 18.04 to 4.18 generic and it's having similar issues (although driver is loaded and ip a shows the interface as down)



      Looking at ifquery it seems wlps03 is not registered, despite showing in ip a I'm just going back to older 4.x kernel, but weirdly plugging in ethernet brings up WiFi & ethernet.



      This is with an realtek WiFi+gigabit ethernet (shakes fist at realtek).



      I also checked lsmod, WiFi driver is loaded...






      share|improve this answer
























        0












        0








        0






        I think this may be more complex. I've just updated kernel in 18.04 to 4.18 generic and it's having similar issues (although driver is loaded and ip a shows the interface as down)



        Looking at ifquery it seems wlps03 is not registered, despite showing in ip a I'm just going back to older 4.x kernel, but weirdly plugging in ethernet brings up WiFi & ethernet.



        This is with an realtek WiFi+gigabit ethernet (shakes fist at realtek).



        I also checked lsmod, WiFi driver is loaded...






        share|improve this answer












        I think this may be more complex. I've just updated kernel in 18.04 to 4.18 generic and it's having similar issues (although driver is loaded and ip a shows the interface as down)



        Looking at ifquery it seems wlps03 is not registered, despite showing in ip a I'm just going back to older 4.x kernel, but weirdly plugging in ethernet brings up WiFi & ethernet.



        This is with an realtek WiFi+gigabit ethernet (shakes fist at realtek).



        I also checked lsmod, WiFi driver is loaded...







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 30 '18 at 13:23









        MrMeseesMrMesees

        1188




        1188






























            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%2f1099200%2fwi-fi-stopped-working-on-ubuntu-18-10-with-linux-4-18-0-12%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

            How to change which sound is reproduced for terminal bell?

            Can I use Tabulator js library in my java Spring + Thymeleaf project?

            Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents