It seems to happen that after un-suspending, sometimes the kernel network device driver r8169 have to be removed and applied using modprobe:
I am linking to original thread for details:
viewtopic.php?f=107&t=47744&p=480421#p480421
I am posting into bug section as it seems to be a bug which may be good to be fixed.
MX-18_x64 Continuum
4.15.0-1-amd64 x86_64 + Systemd
XFCE
[BUG] Network device mising after unsuspend, modprobe driver r8169 fix
[BUG] Network device mising after unsuspend, modprobe driver r8169 fix
OS: MXLinux 17, systemd; GPU: AMD Radeon RX 560
Re: [BUG] Network device mising after unsuspend, modprobe driver r8169 fix
Sounds like a job for the config file!
Create a new text file called "config" with these contents:
(Make sure you have a newline in "config after the line with text in it)
and copy it to /etc/pm/config.d:
This already has a entry in the wiki for the same problem with wireless drivers, BTW.
Create a new text file called "config" with these contents:
Code: Select all
SUSPEND_MODULES="r8169"
and copy it to /etc/pm/config.d:
Code: Select all
sudo cp config /etc/pm/config.d
Re: [BUG] Network device mising after unsuspend, modprobe driver r8169 fix
@Stevo thank You for the reply. I think that it NOT worked. The network device not get fixed upon unsuspending.
$ ls -l /etc/pm/config.d/config
$ cat /etc/pm/config.d/config
I tried also without # and that also not worked. I have to run that command (sudo rmmod r8169;sudo modprobe r8169) and enter password always on unsuspending. Or add alias:
echo "alias nup=\"sudo rmmod r8169;sudo modprobe r8169\" >> ~/.bash_aliases
then after reopening terminal session i can use command "nup" (network up) to enable the network. Though better would be is there is automated way and the best if this issue is fixed.
$ ls -l /etc/pm/config.d/config
Code: Select all
-rw-r--r-- 1 root root 27 Jan 22 11:57 /etc/pm/config.d/config
Code: Select all
SUSPEND_MODULES="r8169"
#
echo "alias nup=\"sudo rmmod r8169;sudo modprobe r8169\" >> ~/.bash_aliases
then after reopening terminal session i can use command "nup" (network up) to enable the network. Though better would be is there is automated way and the best if this issue is fixed.
Last edited by postcd on Thu Jan 24, 2019 5:27 am, edited 1 time in total.
OS: MXLinux 17, systemd; GPU: AMD Radeon RX 560
Re: [BUG] Network device mising after unsuspend, modprobe driver r8169 fix
That's weird. With it in my system, I get a notification that the network has been disconnected just as it suspends and the iwlwifi module is disconnected. Do you see that with your manual method?
Also, are you booting as default or with systemd?
Also, are you booting as default or with systemd?
Re: [BUG] Network device mising after unsuspend, modprobe driver r8169 fix
@Stevo
I also see the network disconnection bubble upon suspending and connection one once i do mentioned manual command.
By the way i am using VPN (built in network manager) that gets auto-connected upon Ethernet connection activation.
Yes i am using systemd as noted in first post, because non-systemd caused suspension issues last month..
I also see the network disconnection bubble upon suspending and connection one once i do mentioned manual command.
By the way i am using VPN (built in network manager) that gets auto-connected upon Ethernet connection activation.
Yes i am using systemd as noted in first post, because non-systemd caused suspension issues last month..
OS: MXLinux 17, systemd; GPU: AMD Radeon RX 560
- NevilsStation
- Posts: 304
- Joined: Sun Feb 26, 2017 3:09 pm
Re: [BUG] Network device mising after unsuspend, modprobe driver r8169 fix
Can you explain this further, please?
Because I want to use VPN but don't want to use systemd
Thanks
Suspension issues on this Forum or elsewhere?i am using systemd as noted in first post, because non-systemd caused suspension issues last month..
Because I want to use VPN but don't want to use systemd
Thanks
Custom-built PC w/i7 CPU running MX-16.
Re: [BUG] Network device mising after unsuspend, modprobe driver r8169 fix
NevilsStation: suspension of the system as i linked in my previous post. If you have some offtopic doubts not related to fixing this issue, please kindly PM me.
OS: MXLinux 17, systemd; GPU: AMD Radeon RX 560