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











up vote
0
down vote

favorite












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 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 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 at 17:11










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










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















up vote
0
down vote

favorite












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 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 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 at 17:11










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










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













up vote
0
down vote

favorite









up vote
0
down vote

favorite











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 at 8:01

























asked Dec 7 at 15:22









Eliezer

34




34












  • 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 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 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 at 17:11










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










  • You did use sudo, correct? Does the module exist in your -12 version? sudo updatedb && locate r8822be.ko
    – chili555
    Dec 7 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 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 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 at 17:11










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










  • You did use sudo, correct? Does the module exist in your -12 version? sudo updatedb && locate r8822be.ko
    – chili555
    Dec 7 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 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 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 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 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 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 at 17:11












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




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












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




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










1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










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 at 8:07











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

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote



accepted










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 at 8:07















up vote
1
down vote



accepted










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 at 8:07













up vote
1
down vote



accepted







up vote
1
down vote



accepted






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 at 20:54









chili555

38k55177




38k55177












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


















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
















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




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


















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.





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%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

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕