No internet on Debian Testing after resuming from suspend/hibernate

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 running Debian Testing with kernel 4.14 on a Dell Inspiron 5567 and Intel Wireless 3165 (driver iwlwifi).



I'm having a problem with Network Manager: after resuming from suspend/hibernate I can connect to a wireless network but there's no internet. I can connect via Bluetooth tethering (that's actually how I am connected now); upon restart everything works fine. Here's info on dmesg that might be relevant:



[ 127.961205] PM: hibernation exit
[ 128.093977] bluetooth hci0: firmware: direct-loading firmware intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 128.093982] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 128.236229] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[ 128.412174] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[ 128.421404] r8169 0000:02:00.0 enp2s0: link down
[ 128.421484] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[ 128.422207] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 128.541945] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 128.616265] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 132.319776] wlp1s0: authenticate with f4:c6:13:22:a8:e0
[ 132.324793] wlp1s0: send auth to f4:c6:13:22:a8:e0 (try 1/3)
[ 132.330364] wlp1s0: authenticated
[ 132.332430] wlp1s0: associate with f4:c6:13:22:a8:e0 (try 1/3)
[ 132.340239] wlp1s0: RX AssocResp from f4:c6:13:22:a8:e0 (capab=0x411 status=0 aid=5)
[ 132.357641] wlp1s0: associated
[ 132.357695] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 158.140921] wlp1s0: deauthenticating from f4:c6:13:22:a8:e0 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 158.150788] wlp1s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
[ 158.158151] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 158.174255] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 160.106531] wlp1s0: authenticate with f4:c6:13:22:a8:e0
[ 160.114505] wlp1s0: send auth to f4:c6:13:22:a8:e0 (try 1/3)
[ 160.118406] wlp1s0: authenticated
[ 160.120421] wlp1s0: associate with f4:c6:13:22:a8:e0 (try 1/3)
[ 160.128040] wlp1s0: RX AssocResp from f4:c6:13:22:a8:e0 (capab=0x411 status=0 aid=5)
[ 160.132544] wlp1s0: associated
[ 160.132615] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready


I can't help notice two lines:



[ 128.421404] r8169 0000:02:00.0 enp2s0: link down


and



[ 158.150788] wlp1s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)


I googled both of them but nothing relevant to this came up (they are related, apparently, to frequent disconnections from wifi, which is not my case).



I tried the solutions listed here but none of them worked; to wit:



1) restarting network manager via systemctl.



2) Removing and loading iwlmvm, THEN restarting nm via systemctl.



Any ideas? Thanks!



EDIT: I forgot mentioning that I tried replacing nm with wicd but removed the latter because bluetooth was not functioning properly; however I purged nm at some point, so maybe a config file was lost.







share|improve this question


















  • 1




    There are some bugs with that particular wifi. I unfortunately have no solution to share for Linux because in my case I solved it switching for OpenBSD. OpenBSD 6.1 also used to have problems with this particular wifi losing connection once in a while however 6.2 seems to have solved it. At least I will leave here the contribute that wifi chipset can be problematic
    – Rui F Ribeiro
    Jan 12 at 21:18














up vote
0
down vote

favorite












I'm running Debian Testing with kernel 4.14 on a Dell Inspiron 5567 and Intel Wireless 3165 (driver iwlwifi).



I'm having a problem with Network Manager: after resuming from suspend/hibernate I can connect to a wireless network but there's no internet. I can connect via Bluetooth tethering (that's actually how I am connected now); upon restart everything works fine. Here's info on dmesg that might be relevant:



[ 127.961205] PM: hibernation exit
[ 128.093977] bluetooth hci0: firmware: direct-loading firmware intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 128.093982] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 128.236229] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[ 128.412174] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[ 128.421404] r8169 0000:02:00.0 enp2s0: link down
[ 128.421484] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[ 128.422207] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 128.541945] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 128.616265] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 132.319776] wlp1s0: authenticate with f4:c6:13:22:a8:e0
[ 132.324793] wlp1s0: send auth to f4:c6:13:22:a8:e0 (try 1/3)
[ 132.330364] wlp1s0: authenticated
[ 132.332430] wlp1s0: associate with f4:c6:13:22:a8:e0 (try 1/3)
[ 132.340239] wlp1s0: RX AssocResp from f4:c6:13:22:a8:e0 (capab=0x411 status=0 aid=5)
[ 132.357641] wlp1s0: associated
[ 132.357695] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 158.140921] wlp1s0: deauthenticating from f4:c6:13:22:a8:e0 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 158.150788] wlp1s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
[ 158.158151] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 158.174255] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 160.106531] wlp1s0: authenticate with f4:c6:13:22:a8:e0
[ 160.114505] wlp1s0: send auth to f4:c6:13:22:a8:e0 (try 1/3)
[ 160.118406] wlp1s0: authenticated
[ 160.120421] wlp1s0: associate with f4:c6:13:22:a8:e0 (try 1/3)
[ 160.128040] wlp1s0: RX AssocResp from f4:c6:13:22:a8:e0 (capab=0x411 status=0 aid=5)
[ 160.132544] wlp1s0: associated
[ 160.132615] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready


I can't help notice two lines:



[ 128.421404] r8169 0000:02:00.0 enp2s0: link down


and



[ 158.150788] wlp1s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)


I googled both of them but nothing relevant to this came up (they are related, apparently, to frequent disconnections from wifi, which is not my case).



I tried the solutions listed here but none of them worked; to wit:



1) restarting network manager via systemctl.



2) Removing and loading iwlmvm, THEN restarting nm via systemctl.



Any ideas? Thanks!



EDIT: I forgot mentioning that I tried replacing nm with wicd but removed the latter because bluetooth was not functioning properly; however I purged nm at some point, so maybe a config file was lost.







share|improve this question


















  • 1




    There are some bugs with that particular wifi. I unfortunately have no solution to share for Linux because in my case I solved it switching for OpenBSD. OpenBSD 6.1 also used to have problems with this particular wifi losing connection once in a while however 6.2 seems to have solved it. At least I will leave here the contribute that wifi chipset can be problematic
    – Rui F Ribeiro
    Jan 12 at 21:18












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I'm running Debian Testing with kernel 4.14 on a Dell Inspiron 5567 and Intel Wireless 3165 (driver iwlwifi).



I'm having a problem with Network Manager: after resuming from suspend/hibernate I can connect to a wireless network but there's no internet. I can connect via Bluetooth tethering (that's actually how I am connected now); upon restart everything works fine. Here's info on dmesg that might be relevant:



[ 127.961205] PM: hibernation exit
[ 128.093977] bluetooth hci0: firmware: direct-loading firmware intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 128.093982] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 128.236229] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[ 128.412174] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[ 128.421404] r8169 0000:02:00.0 enp2s0: link down
[ 128.421484] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[ 128.422207] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 128.541945] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 128.616265] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 132.319776] wlp1s0: authenticate with f4:c6:13:22:a8:e0
[ 132.324793] wlp1s0: send auth to f4:c6:13:22:a8:e0 (try 1/3)
[ 132.330364] wlp1s0: authenticated
[ 132.332430] wlp1s0: associate with f4:c6:13:22:a8:e0 (try 1/3)
[ 132.340239] wlp1s0: RX AssocResp from f4:c6:13:22:a8:e0 (capab=0x411 status=0 aid=5)
[ 132.357641] wlp1s0: associated
[ 132.357695] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 158.140921] wlp1s0: deauthenticating from f4:c6:13:22:a8:e0 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 158.150788] wlp1s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
[ 158.158151] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 158.174255] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 160.106531] wlp1s0: authenticate with f4:c6:13:22:a8:e0
[ 160.114505] wlp1s0: send auth to f4:c6:13:22:a8:e0 (try 1/3)
[ 160.118406] wlp1s0: authenticated
[ 160.120421] wlp1s0: associate with f4:c6:13:22:a8:e0 (try 1/3)
[ 160.128040] wlp1s0: RX AssocResp from f4:c6:13:22:a8:e0 (capab=0x411 status=0 aid=5)
[ 160.132544] wlp1s0: associated
[ 160.132615] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready


I can't help notice two lines:



[ 128.421404] r8169 0000:02:00.0 enp2s0: link down


and



[ 158.150788] wlp1s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)


I googled both of them but nothing relevant to this came up (they are related, apparently, to frequent disconnections from wifi, which is not my case).



I tried the solutions listed here but none of them worked; to wit:



1) restarting network manager via systemctl.



2) Removing and loading iwlmvm, THEN restarting nm via systemctl.



Any ideas? Thanks!



EDIT: I forgot mentioning that I tried replacing nm with wicd but removed the latter because bluetooth was not functioning properly; however I purged nm at some point, so maybe a config file was lost.







share|improve this question














I'm running Debian Testing with kernel 4.14 on a Dell Inspiron 5567 and Intel Wireless 3165 (driver iwlwifi).



I'm having a problem with Network Manager: after resuming from suspend/hibernate I can connect to a wireless network but there's no internet. I can connect via Bluetooth tethering (that's actually how I am connected now); upon restart everything works fine. Here's info on dmesg that might be relevant:



[ 127.961205] PM: hibernation exit
[ 128.093977] bluetooth hci0: firmware: direct-loading firmware intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 128.093982] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 128.236229] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[ 128.412174] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[ 128.421404] r8169 0000:02:00.0 enp2s0: link down
[ 128.421484] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[ 128.422207] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 128.541945] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 128.616265] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 132.319776] wlp1s0: authenticate with f4:c6:13:22:a8:e0
[ 132.324793] wlp1s0: send auth to f4:c6:13:22:a8:e0 (try 1/3)
[ 132.330364] wlp1s0: authenticated
[ 132.332430] wlp1s0: associate with f4:c6:13:22:a8:e0 (try 1/3)
[ 132.340239] wlp1s0: RX AssocResp from f4:c6:13:22:a8:e0 (capab=0x411 status=0 aid=5)
[ 132.357641] wlp1s0: associated
[ 132.357695] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 158.140921] wlp1s0: deauthenticating from f4:c6:13:22:a8:e0 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 158.150788] wlp1s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
[ 158.158151] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 158.174255] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 160.106531] wlp1s0: authenticate with f4:c6:13:22:a8:e0
[ 160.114505] wlp1s0: send auth to f4:c6:13:22:a8:e0 (try 1/3)
[ 160.118406] wlp1s0: authenticated
[ 160.120421] wlp1s0: associate with f4:c6:13:22:a8:e0 (try 1/3)
[ 160.128040] wlp1s0: RX AssocResp from f4:c6:13:22:a8:e0 (capab=0x411 status=0 aid=5)
[ 160.132544] wlp1s0: associated
[ 160.132615] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready


I can't help notice two lines:



[ 128.421404] r8169 0000:02:00.0 enp2s0: link down


and



[ 158.150788] wlp1s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)


I googled both of them but nothing relevant to this came up (they are related, apparently, to frequent disconnections from wifi, which is not my case).



I tried the solutions listed here but none of them worked; to wit:



1) restarting network manager via systemctl.



2) Removing and loading iwlmvm, THEN restarting nm via systemctl.



Any ideas? Thanks!



EDIT: I forgot mentioning that I tried replacing nm with wicd but removed the latter because bluetooth was not functioning properly; however I purged nm at some point, so maybe a config file was lost.









share|improve this question













share|improve this question




share|improve this question








edited Jan 12 at 23:34

























asked Jan 12 at 20:46









Óscar Guajardo

164




164







  • 1




    There are some bugs with that particular wifi. I unfortunately have no solution to share for Linux because in my case I solved it switching for OpenBSD. OpenBSD 6.1 also used to have problems with this particular wifi losing connection once in a while however 6.2 seems to have solved it. At least I will leave here the contribute that wifi chipset can be problematic
    – Rui F Ribeiro
    Jan 12 at 21:18












  • 1




    There are some bugs with that particular wifi. I unfortunately have no solution to share for Linux because in my case I solved it switching for OpenBSD. OpenBSD 6.1 also used to have problems with this particular wifi losing connection once in a while however 6.2 seems to have solved it. At least I will leave here the contribute that wifi chipset can be problematic
    – Rui F Ribeiro
    Jan 12 at 21:18







1




1




There are some bugs with that particular wifi. I unfortunately have no solution to share for Linux because in my case I solved it switching for OpenBSD. OpenBSD 6.1 also used to have problems with this particular wifi losing connection once in a while however 6.2 seems to have solved it. At least I will leave here the contribute that wifi chipset can be problematic
– Rui F Ribeiro
Jan 12 at 21:18




There are some bugs with that particular wifi. I unfortunately have no solution to share for Linux because in my case I solved it switching for OpenBSD. OpenBSD 6.1 also used to have problems with this particular wifi losing connection once in a while however 6.2 seems to have solved it. At least I will leave here the contribute that wifi chipset can be problematic
– Rui F Ribeiro
Jan 12 at 21:18










1 Answer
1






active

oldest

votes

















up vote
0
down vote













Have the same problem her on Debian stable with kernel 4.16.0-2-amd64 and Realtek r8169




r8169 0000:02:00.0 enp2s0: link down




You can try to remove and reload the kenel driver before and after suspend.
Create a file
/lib/systemd/system-sleep/reset-network



#!/bin/sh
if [ "$1" == "pre" ]; then
# Do the thing you want before suspend here, e.g.:
rmmod r8169
elif [ "$1" == "post" ]; then
# Do the thing you want after resume here, e.g.:
modprobe r8169
fi


Don't forget to make it executable with
chmod 755 /lib/systemd/system-sleep/reset-network



In some cases the path might be /user/lib/systemd/system-sleep/



You can add other modules too!






share|improve this answer




















  • Thanks! I don't exactly remember how I solved this; maybe I reinstalled. I don't have this issue anymore, it was probably sovled by a kernel upgrade. If anyone else finds your solution useful I'll mark it as the answer. Again, thank you!
    – Óscar Guajardo
    Jul 10 at 21:23










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f416673%2fno-internet-on-debian-testing-after-resuming-from-suspend-hibernate%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













Have the same problem her on Debian stable with kernel 4.16.0-2-amd64 and Realtek r8169




r8169 0000:02:00.0 enp2s0: link down




You can try to remove and reload the kenel driver before and after suspend.
Create a file
/lib/systemd/system-sleep/reset-network



#!/bin/sh
if [ "$1" == "pre" ]; then
# Do the thing you want before suspend here, e.g.:
rmmod r8169
elif [ "$1" == "post" ]; then
# Do the thing you want after resume here, e.g.:
modprobe r8169
fi


Don't forget to make it executable with
chmod 755 /lib/systemd/system-sleep/reset-network



In some cases the path might be /user/lib/systemd/system-sleep/



You can add other modules too!






share|improve this answer




















  • Thanks! I don't exactly remember how I solved this; maybe I reinstalled. I don't have this issue anymore, it was probably sovled by a kernel upgrade. If anyone else finds your solution useful I'll mark it as the answer. Again, thank you!
    – Óscar Guajardo
    Jul 10 at 21:23














up vote
0
down vote













Have the same problem her on Debian stable with kernel 4.16.0-2-amd64 and Realtek r8169




r8169 0000:02:00.0 enp2s0: link down




You can try to remove and reload the kenel driver before and after suspend.
Create a file
/lib/systemd/system-sleep/reset-network



#!/bin/sh
if [ "$1" == "pre" ]; then
# Do the thing you want before suspend here, e.g.:
rmmod r8169
elif [ "$1" == "post" ]; then
# Do the thing you want after resume here, e.g.:
modprobe r8169
fi


Don't forget to make it executable with
chmod 755 /lib/systemd/system-sleep/reset-network



In some cases the path might be /user/lib/systemd/system-sleep/



You can add other modules too!






share|improve this answer




















  • Thanks! I don't exactly remember how I solved this; maybe I reinstalled. I don't have this issue anymore, it was probably sovled by a kernel upgrade. If anyone else finds your solution useful I'll mark it as the answer. Again, thank you!
    – Óscar Guajardo
    Jul 10 at 21:23












up vote
0
down vote










up vote
0
down vote









Have the same problem her on Debian stable with kernel 4.16.0-2-amd64 and Realtek r8169




r8169 0000:02:00.0 enp2s0: link down




You can try to remove and reload the kenel driver before and after suspend.
Create a file
/lib/systemd/system-sleep/reset-network



#!/bin/sh
if [ "$1" == "pre" ]; then
# Do the thing you want before suspend here, e.g.:
rmmod r8169
elif [ "$1" == "post" ]; then
# Do the thing you want after resume here, e.g.:
modprobe r8169
fi


Don't forget to make it executable with
chmod 755 /lib/systemd/system-sleep/reset-network



In some cases the path might be /user/lib/systemd/system-sleep/



You can add other modules too!






share|improve this answer












Have the same problem her on Debian stable with kernel 4.16.0-2-amd64 and Realtek r8169




r8169 0000:02:00.0 enp2s0: link down




You can try to remove and reload the kenel driver before and after suspend.
Create a file
/lib/systemd/system-sleep/reset-network



#!/bin/sh
if [ "$1" == "pre" ]; then
# Do the thing you want before suspend here, e.g.:
rmmod r8169
elif [ "$1" == "post" ]; then
# Do the thing you want after resume here, e.g.:
modprobe r8169
fi


Don't forget to make it executable with
chmod 755 /lib/systemd/system-sleep/reset-network



In some cases the path might be /user/lib/systemd/system-sleep/



You can add other modules too!







share|improve this answer












share|improve this answer



share|improve this answer










answered Jul 10 at 8:08









RubbelDeCatc

1011




1011











  • Thanks! I don't exactly remember how I solved this; maybe I reinstalled. I don't have this issue anymore, it was probably sovled by a kernel upgrade. If anyone else finds your solution useful I'll mark it as the answer. Again, thank you!
    – Óscar Guajardo
    Jul 10 at 21:23
















  • Thanks! I don't exactly remember how I solved this; maybe I reinstalled. I don't have this issue anymore, it was probably sovled by a kernel upgrade. If anyone else finds your solution useful I'll mark it as the answer. Again, thank you!
    – Óscar Guajardo
    Jul 10 at 21:23















Thanks! I don't exactly remember how I solved this; maybe I reinstalled. I don't have this issue anymore, it was probably sovled by a kernel upgrade. If anyone else finds your solution useful I'll mark it as the answer. Again, thank you!
– Óscar Guajardo
Jul 10 at 21:23




Thanks! I don't exactly remember how I solved this; maybe I reinstalled. I don't have this issue anymore, it was probably sovled by a kernel upgrade. If anyone else finds your solution useful I'll mark it as the answer. Again, thank you!
– Óscar Guajardo
Jul 10 at 21:23












 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f416673%2fno-internet-on-debian-testing-after-resuming-from-suspend-hibernate%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Christian Cage

How to properly install USB display driver for Fresco Logic FL2000DX on Ubuntu?