To restrict your output to the relevant information you could try something like …
journalctl -t systemd-sleep
to see when you last suspended and resumed and then limit your journalctl information to shortly before suspend and after resume; e. g. journalctl --since "2020-07-06 22:45:00" --until "2020-07-08 22:00:00"
Do not post this information here directly; instead read about how to “Pastebin” this information in the above link.
Nothing, really long to read. (Tl dr) Anyway, after returning from sleep, does it happen every time that there is no ethernet connection, or just randomly?
after one restart with normal wired network connection, every time unit is put into suspend and subsequently restarted the wired Ethernet does not connect
the “nmcli” command returns that the wired connection is “getting IP configuration”
I just wanted to see what ethernet adapter it is? So that is the only section needed.
Edit: You could create a service file like this for suspend & resume. Your adapter’s designation is different than “enp6s0” you will need to substitute you own adapter’s ID into the service file.
You have a few choices. You could try the r8169. It works for some. Not for others. You could also try the r8168-dkms or you could try creating the suspend resume service as outlined in the link i posted.
I do have a “test/standby” installation of EndeavourOS that is updated close to the same frequency as my “main” installation – it does NOT exhibit the same loss of ethernet network connectivity after a sleep/suspend action.
I am quite puzzled by what may have been either a package introduction/change/elimination, or whether a different setting has been introduced.