[x86-64, LE 12.0.1] wired connection does not wake up after sleep

    Hello.

    I built new PC for Kodi using using N100 (ASUS PRIME N100I-D D4 motherboard). Was bit worried about building my first non-Windows box, but I got pretty much everything working except for wired connection. It works fine after boot but if I put the system to sleep it does not wake up. The LibreELEC settings shows it as 'idle'. Trying to connect it leads to state turning into failure and I get pop-up message that says: Network Error . Input/output error.

    I also cannot send log with no net connection, but here are logs after reboot:

    https://paste.libreelec.tv/trusting-sole.log

    https://paste.libreelec.tv/hip-snipe.log


    This only happens after sleep and rebooting after failure solves the issue. Tried to fiddling with the settings and UEFI, but could not really find anything that could help. Would be great if anybody could help.

    Try the default skin.

    In case it doesn't work, upload kodi.old.log after reboot, and post the resulting URL:

    • cd .kodi/temp
    • cat kodi.old.log | pastebinit
    Quote from Da Flex

    Try the default skin.

    In case it doesn't work, upload kodi.old.log after reboot, and post the resulting URL:

    • cd .kodi/temp
    • cat kodi.old.log | pastebinit

    Thank you for help.


    Switching to default skin did not help.

    Here is the kodi.old.log



    https://paste.libreelec.tv/on-kit.log

    I seem to have solved it.

    Took look at the old.log after posting it. Googled error codes. One of them seemed to be WLAN related. The Asus motherboard does not come with WIFI, but I had an old unused M2 WLAN card. I had it in when installed libreelec, but I don't have antennas for it. It could not (unsuprisingly) find network without the antennas, so I took it out when I was adding SDDs into the case.

    Decided to try putting it back in after I saw the error code, and it seems to have fixed the problem. So not finding that WLAN card caused LAN to also not work.

    Sorry for bothering with such silly error. Appears to work fine now. Did three sleep->wake up cycles and worked fine after each one.


    Thank you for the help!

    Well, that was premature joy.

    The problem came back after first power off and reboot. Now getting the same error again after sleep.

    Have not been able to fix it again. Tried even fresh install on a different SSD and again the same problem. At that point I started to think that maybe the motherboard LAN hardware is faulty, so I downloaded Ubuntu image and installed it. Wired connection works just fine under Ubuntu, including after waking from suspend/sleep.

    Did not know what to try next, so I thought I'll try asking for help from here again.Here is old.log after another failure waking the wired connection after suspend:

    https://paste.libreelec.tv/giving-orca.log

    After coming back from standby, you get exactly two errors:

    Code
    2024-10-01 16:04:24.150 T:1564    error <general>: SETTINGS: dbus_error_handler # DBusError('net.connman.Error.Failed -- Input/output error')
    Code
    2024-10-01 16:04:38.421 T:1193    debug <general>: CServiceAddonManager: stopping service.upnext.
2024-10-01 16:04:38.421 T:1193    debug <general>: CPythonInvoker(9, /storage/.kodi/addons/service.upnext/resources/lib/service_entry.py): trigger Monitor abort request
2024-10-01 16:04:38.421 T:1228    debug <general>: Thread LanguageInvoker 140601852946112 terminating
2024-10-01 16:04:38.421 T:1230    debug <CAddonSettings[[email protected]]>: trying to load setting definitions from old format...
2024-10-01 16:04:38.421 T:1230    debug <general>: [service.upnext] UpNextMonitor -> Service stopped
2024-10-01 16:04:38.421 T:1230    debug <general>: CPythonInvoker(9, /storage/.kodi/addons/service.upnext/resources/lib/service_entry.py): script successfully run
2024-10-01 16:04:38.421 T:1230    debug <general>: onExecutionDone(9, /storage/.kodi/addons/service.upnext/resources/lib/service_entry.py)
2024-10-01 16:04:38.422 T:1230    error <general>: EXCEPTION: No valid addon id could be obtained. None was passed and the script wasn't executed in a normal Kodi manner.

    You can uninstall or deactivate the "Up Next" add-on to rule out the latter error as the cause of the issue.

    I guess the first error is the culprit. I think your network adapter has a standby mode, which isn't fully supported by the Linux kernel. If you want to invest the time, dig deeper, and find network adapter specs, as well as current Linux driver state.

    My suggestion is not to use standby mode at your current hardware. Maybe a screensaver is good enough.