WiFi clips out after 4.19.6 kernel
0
WiFi used to work fine on 4.19.1 but after upgrading my kernel it stops working after a while. I've tried a few things that do not work:
sudo service NetworkManager restart
sudo service network-manager restart
sudo service networking restart
None of them do the trick. I do have some logs from the last time it stopped but I can't turn them into an actionable item. Anybody have a tip?
-- Logs begin at Mon 2018-12-03 19:51:48 EST. --
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2483] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2497] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2501] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2506] manager: NetworkManager state is now CONNECTED_LOCAL
Jan 02 21:20:01 envy dhclient[2054]: bound to 192.168.86.41 -- renewal in 33503 seconds.
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2625] manager: NetworkManager state is now CONNECTED_SITE
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2627] policy: set 'owlbear' (wlo1) as default for IPv4 routing and DNS
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2635] device (wlo1): Activation: successful, device activated.
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2647] manager: startup complete
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.3803] manager: NetworkManager state is now CONNECTED_GLOBAL
---> GOES DOWN HERE <-----------
Jan 02 22:10:14 envy NetworkManager[1296]: <warn> [1546485014.2700] sup-iface[0x56522e92b8e0,wlo1]: connection disconnected (reason -3)
Jan 02 22:10:14 envy NetworkManager[1296]: <info> [1546485014.2842] device (wlo1): supplicant interface state: completed -> disabled
Jan 02 22:10:14 envy dhclient[2054]: receive_packet failed on wlo1: Network is down
wireless kernel 18.10
asked Jan 3 at 3:30
vince
135
add a comment |
0
WiFi used to work fine on 4.19.1 but after upgrading my kernel it stops working after a while. I've tried a few things that do not work:
sudo service NetworkManager restart
sudo service network-manager restart
sudo service networking restart
None of them do the trick. I do have some logs from the last time it stopped but I can't turn them into an actionable item. Anybody have a tip?
-- Logs begin at Mon 2018-12-03 19:51:48 EST. --
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2483] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2497] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2501] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2506] manager: NetworkManager state is now CONNECTED_LOCAL
Jan 02 21:20:01 envy dhclient[2054]: bound to 192.168.86.41 -- renewal in 33503 seconds.
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2625] manager: NetworkManager state is now CONNECTED_SITE
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2627] policy: set 'owlbear' (wlo1) as default for IPv4 routing and DNS
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2635] device (wlo1): Activation: successful, device activated.
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2647] manager: startup complete
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.3803] manager: NetworkManager state is now CONNECTED_GLOBAL
---> GOES DOWN HERE <-----------
Jan 02 22:10:14 envy NetworkManager[1296]: <warn> [1546485014.2700] sup-iface[0x56522e92b8e0,wlo1]: connection disconnected (reason -3)
Jan 02 22:10:14 envy NetworkManager[1296]: <info> [1546485014.2842] device (wlo1): supplicant interface state: completed -> disabled
Jan 02 22:10:14 envy dhclient[2054]: receive_packet failed on wlo1: Network is down
wireless kernel 18.10
asked Jan 3 at 3:30
vince
135
I would be more worried about file corruption in the 4.19 kernel
– Jeremy31
Jan 3 at 11:13
same issue in 4.20 kernel, but thanks for the advice.
– vince
Jan 3 at 21:59
Why not use supported kernel versions?
– Jeremy31
Jan 3 at 22:01
Supported kernel versions don't work with my laptop's touchscreen. That issue was fixed in 4.19.5. There were also some reported improvements for AMD GPU's in 4.20 that I wanted to review.
– vince
2 days ago
add a comment |
0
0
0
WiFi used to work fine on 4.19.1 but after upgrading my kernel it stops working after a while. I've tried a few things that do not work:
sudo service NetworkManager restart
sudo service network-manager restart
sudo service networking restart
None of them do the trick. I do have some logs from the last time it stopped but I can't turn them into an actionable item. Anybody have a tip?
-- Logs begin at Mon 2018-12-03 19:51:48 EST. --
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2483] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2497] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2501] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2506] manager: NetworkManager state is now CONNECTED_LOCAL
Jan 02 21:20:01 envy dhclient[2054]: bound to 192.168.86.41 -- renewal in 33503 seconds.
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2625] manager: NetworkManager state is now CONNECTED_SITE
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2627] policy: set 'owlbear' (wlo1) as default for IPv4 routing and DNS
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2635] device (wlo1): Activation: successful, device activated.
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2647] manager: startup complete
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.3803] manager: NetworkManager state is now CONNECTED_GLOBAL
---> GOES DOWN HERE <-----------
Jan 02 22:10:14 envy NetworkManager[1296]: <warn> [1546485014.2700] sup-iface[0x56522e92b8e0,wlo1]: connection disconnected (reason -3)
Jan 02 22:10:14 envy NetworkManager[1296]: <info> [1546485014.2842] device (wlo1): supplicant interface state: completed -> disabled
Jan 02 22:10:14 envy dhclient[2054]: receive_packet failed on wlo1: Network is down
wireless kernel 18.10
asked Jan 3 at 3:30
vince
135
WiFi used to work fine on 4.19.1 but after upgrading my kernel it stops working after a while. I've tried a few things that do not work:
sudo service NetworkManager restart
sudo service network-manager restart
sudo service networking restart
None of them do the trick. I do have some logs from the last time it stopped but I can't turn them into an actionable item. Anybody have a tip?
-- Logs begin at Mon 2018-12-03 19:51:48 EST. --
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2483] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2497] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2501] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2506] manager: NetworkManager state is now CONNECTED_LOCAL
Jan 02 21:20:01 envy dhclient[2054]: bound to 192.168.86.41 -- renewal in 33503 seconds.
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2625] manager: NetworkManager state is now CONNECTED_SITE
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2627] policy: set 'owlbear' (wlo1) as default for IPv4 routing and DNS
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2635] device (wlo1): Activation: successful, device activated.
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.2647] manager: startup complete
Jan 02 21:20:01 envy NetworkManager[1296]: <info> [1546482001.3803] manager: NetworkManager state is now CONNECTED_GLOBAL
---> GOES DOWN HERE <-----------
Jan 02 22:10:14 envy NetworkManager[1296]: <warn> [1546485014.2700] sup-iface[0x56522e92b8e0,wlo1]: connection disconnected (reason -3)
Jan 02 22:10:14 envy NetworkManager[1296]: <info> [1546485014.2842] device (wlo1): supplicant interface state: completed -> disabled
Jan 02 22:10:14 envy dhclient[2054]: receive_packet failed on wlo1: Network is down
wireless kernel 18.10
wireless kernel 18.10
asked Jan 3 at 3:30
vince
135
asked Jan 3 at 3:30
vince
135
asked Jan 3 at 3:30
vince
135
asked Jan 3 at 3:30
vince
135
asked Jan 3 at 3:30
vince
135
135
I would be more worried about file corruption in the 4.19 kernel
– Jeremy31
Jan 3 at 11:13
same issue in 4.20 kernel, but thanks for the advice.
– vince
Jan 3 at 21:59
Why not use supported kernel versions?
– Jeremy31
Jan 3 at 22:01
Supported kernel versions don't work with my laptop's touchscreen. That issue was fixed in 4.19.5. There were also some reported improvements for AMD GPU's in 4.20 that I wanted to review.
– vince
2 days ago
add a comment |
I would be more worried about file corruption in the 4.19 kernel
– Jeremy31
Jan 3 at 11:13
same issue in 4.20 kernel, but thanks for the advice.
– vince
Jan 3 at 21:59
Why not use supported kernel versions?
– Jeremy31
Jan 3 at 22:01
Supported kernel versions don't work with my laptop's touchscreen. That issue was fixed in 4.19.5. There were also some reported improvements for AMD GPU's in 4.20 that I wanted to review.
– vince
2 days ago
I would be more worried about file corruption in the 4.19 kernel
– Jeremy31
Jan 3 at 11:13
I would be more worried about file corruption in the 4.19 kernel
– Jeremy31
Jan 3 at 11:13
same issue in 4.20 kernel, but thanks for the advice.
– vince
Jan 3 at 21:59
same issue in 4.20 kernel, but thanks for the advice.
– vince
Jan 3 at 21:59
Why not use supported kernel versions?
– Jeremy31
Jan 3 at 22:01
Why not use supported kernel versions?
– Jeremy31
Jan 3 at 22:01
Supported kernel versions don't work with my laptop's touchscreen. That issue was fixed in 4.19.5. There were also some reported improvements for AMD GPU's in 4.20 that I wanted to review.
– vince
2 days ago
Supported kernel versions don't work with my laptop's touchscreen. That issue was fixed in 4.19.5. There were also some reported improvements for AMD GPU's in 4.20 that I wanted to review.
– vince
2 days ago
add a comment |
0
active
oldest
votes
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1106460%2fwifi-clips-out-after-4-19-6-kernel%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1106460%2fwifi-clips-out-after-4-19-6-kernel%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
I would be more worried about file corruption in the 4.19 kernel
– Jeremy31
Jan 3 at 11:13
same issue in 4.20 kernel, but thanks for the advice.
– vince
Jan 3 at 21:59
Why not use supported kernel versions?
– Jeremy31
Jan 3 at 22:01
Supported kernel versions don't work with my laptop's touchscreen. That issue was fixed in 4.19.5. There were also some reported improvements for AMD GPU's in 4.20 that I wanted to review.
– vince
2 days ago