On Sunday, April 22, 2018 at 1:44:18 PM UTC-4, Mike Keehan wrote: > On Sat, 21 Apr 2018 14:20:02 +0200 (CEST) > <argan...@tutanota.com> wrote: > > > >> My issue: > > >> > > >> On qubes version r4.0 after resuming from suspend networking isn't > > >> working. On qubes r3.2 this wasn't an issue. > > >> > > >> > > >> After resuming from suspend to ram, networking on sys-net isn't > > >> working: $ ip addr > > >> 6: ens5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc > > >> fq_codel state DOWN group default qlen 1000 link/ether > > >> 4c:cc:6a:30:f5:90 brd ff:ff:ff:ff:ff:ff > > >> > ...snip... > > > >> --------------------------------------------------------------------------- > > >> After resuming I've tried: > > >> [user@sys-net ~]$ sudo rmmod r8169 > > >> [user@sys-net ~]$ sudo rmmod mii > > >> [user@sys-net ~]$ sudo modprobe mii > > >> [user@sys-net ~]$ sudo modprobe r8169 > > > > > > did you try to `rmmod` *before* suspending ? > > > > Try adding the module names to the sys-net file > /etc/qubes-suspend-module-blacklist, and Qubes should handle them > for you. > > Mike.
I tried that for my ethernet module but it didn't help. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0d7ec88c-d38a-4728-b159-351b3a2a14d2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
