Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: Ethernet down after resume. Tumbleweed

Hybrid View

  1. #1

    Question Ethernet down after resume. Tumbleweed

    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.

    Anyone knows how to fix this?

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,071
    Blog Entries
    1

    Default Re: Ethernet down after resume. Tumbleweed

    Some more information is required to help diagnose this. To start with...following a resume, capture the output from
    Code:
    ip link
    Code:
    systemctl status NetworkManager
    Code:
    journalctl -u NetworkManager
    If you don't have internet connectivity on this machine, then you could cupy/paste output to a text file and transfer via memory stick.

  3. #3
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,071
    Blog Entries
    1

    Default Re: Ethernet down after resume. Tumbleweed

    If sleep hooks really do turn out to be needed (for module unloading/reloading), then it needs to be done using systemd methods...

    https://wiki.archlinux.org/index.php..._and_hibernate

  4. #4

    Default Re: Ethernet down after resume. Tumbleweed

    Quote Originally Posted by deano_ferrari View Post
    If sleep hooks really do turn out to be needed (for module unloading/reloading), then it needs to be done using systemd methods...

    https://wiki.archlinux.org/index.php..._and_hibernate
    Thank you for the link. I've verified that running
    Code:
    sudo /usr/sbin/modprobe -r r8169 && sudo /usr/sbin/modprobe r8169
    after resume fixes the issue. Unfortunately, it is not clear to me how to achieve this using service file.

  5. #5
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,071
    Blog Entries
    1

    Default Re: Ethernet down after resume. Tumbleweed

    Quote Originally Posted by RaveNBlack View Post
    Thank you for the link. I've verified that running
    Code:
    sudo /usr/sbin/modprobe -r r8169 && sudo /usr/sbin/modprobe r8169
    after resume fixes the issue. Unfortunately, it is not clear to me how to achieve this using service file.
    Create a service file eg etc/systemd/system/r8169-reload.service

    Code:
    [Unit]
    Description=Reload wireless driver after system resume
    After=suspend.target
    
    [Service]
    Type=oneshot
    ExecStart=/usr/sbin/modprobe -r r8169
    ExecStart=/usr/sbin/modprobe r8169
    
    [Install]
    WantedBy=suspend.target
    Then enable and start the service
    Code:
    systemctl enable r8169-reload.service
    Code:
    systemctl start r8169-reload.service
    Hope that does the trick.

  6. #6

    Default Re: Ethernet down after resume. Tumbleweed

    Quote Originally Posted by deano_ferrari View Post
    Create a service file eg etc/systemd/system/r8169-reload.service

    Code:
    [Unit]
    Description=Reload wireless driver after system resume
    After=suspend.target
    
    [Service]
    Type=oneshot
    ExecStart=/usr/sbin/modprobe -r r8169
    ExecStart=/usr/sbin/modprobe r8169
    
    [Install]
    WantedBy=suspend.target
    Then enable and start the service
    Code:
    systemctl enable r8169-reload.service
    Code:
    systemctl start r8169-reload.service
    Hope that does the trick.
    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.

  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,071
    Blog Entries
    1

    Default Re: Ethernet down after resume. Tumbleweed

    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.

  8. #8
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,071
    Blog Entries
    1

    Default Re: Ethernet down after resume. Tumbleweed

    Try enabling the service manually with
    Code:
    mkdir /etc/systemd/system/suspend.target.wants
    Code:
    ln -s /etc/systemd/system/r8169-reload.service /etc/systemd/system/suspend.target.wants/r8169-reload.service
    Start it with
    Code:
    systemctl start r8169-reload
    and then try suspending/resuming again.
    Last edited by deano_ferrari; 15-Oct-2015 at 01:48.

  9. #9

    Default Re: Ethernet down after resume. Tumbleweed

    Quote Originally Posted by deano_ferrari View Post
    Try enabling the service manually with
    Code:
    mkdir /etc/systemd/system/suspend.target.wants
    Code:
    ln -s /etc/systemd/system/r8169-reload.service /etc/systemd/system/suspend.target.wants/r8169-reload.service
    Start it with
    Code:
    systemctl start r8169-reload
    and then try suspending/resuming again.
    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.

  10. #10
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,071
    Blog Entries
    1

    Default Re: Ethernet down after resume. Tumbleweed

    Quote Originally Posted by RaveNBlack View Post
    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...

    What does the following command report?
    Code:
    systemctl status r8169-reload.service

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •