Hi, a few days ago I’ve switched from OpenSuSE 13.2 to Tumbleweed.
When i suspend my laptop (close the lid) and resume it afterwards, the ethernet (not WiFi) is unavailable, i.e. it does not reconnect.
I’ve tried restarting Network Manager server, but all it does is add second Network Manager applet in systray.
Google searched suggests editing /etc/pm/config.d/unload_modules and adding SUSPEND_MODULES="$SUSPEND_MODULES [module_name]", but I don’t have “pm” under /etc. I’ve tried creating the missing directories and the unload_modules, add the SUSPEND_MODULES bit, but it didn’t help.
Thank you for the file, unfortunately, when i try to enable the service (with sudo) I get this message “Failed to execute operation: Bad message”.
I don’t see the service Yast service list and my network card still not available after resume.
Starting the service (with sudo) on the other hand, does reload the kernel module and fixes the issue.
Strange, implementing that service works for me without issue. My NIC uses the same driver, although I don’t suffer the resume problem you’ve described.
Thanks for the advice. I’ve created the symbolic link but it didn’t seem to help. Trying to enable the service throws the same error. It does not reload kernel module on resume, but does reload kernel module if I manually start the service as before.
Creating the symbolic link should be all that’s required to have it enabled ie no need to run ‘systemctl enable…’ after that. I can’t replicate the error you’re getting, so hard to advise further…
It is important to note that I’m doing all of this in an openSUSE 13.2 environment, whereas you are doing this with Tumbleweed. I’m not sure how this might impact here, but clearly it is. Hopefully, others can chime in here. You may need to submit a bug report for this. The underlying issue with the r8169 driver (following resume) could also be reported, since we’re effectively only attempting to work around that issue here.
That’s it! The very first “” bracket before “Unit” was missing. It still shows me the errors, but at least my NIC now reconnects on resume. I’m sorry to have taken your time with silly oversight on side and thank you for the info. I have learned something new and got my issue resolved thanks to you.
I started to suspect a syntax error of some kind, but not possible to know without seeing the .service file you created. Anyway, I’m glad you checked and found the missing character, and it is now working to your satisfaction! Yes, it’s all part of the learning.