I have a desktop computer connected to the internet through Ethernet cable (it doesn’t have a wifi chip).
When I wake up the machine after suspending over night, it doesn’t have internet connection, so I have to reboot. I try to do sudo systemctl start NetworkManager but to no avail.
I think this only happens recently, I don’t recall this problem in the past.
Any tips? Are there any modules I should check?
Thanks.
systemctl status "netctl@ethernet\\x2ddhcp.service
× netctl@ethernet\x2ddhcp.service - Networking for netctl profile ethernet-dhcp
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
Active: failed (Result: exit-code) since Mon 2024-07-08 10:03:16 CEST; 22s ago
Invocation: 243064607e764457b7c8fd5ef685df23
Docs: man:netctl.profile(5)
Process: 622974 ExecStart=/usr/lib/netctl/network start ethernet-dhcp (code=exited, status=1/FAILURE)
Main PID: 622974 (code=exited, status=1/FAILURE)
jul 08 10:03:16 eos systemd[1]: Starting Networking for netctl profile ethernet-dhcp...
jul 08 10:03:16 eos network[622974]: Profile 'ethernet-dhcp' does not exist or is not readable
jul 08 10:03:16 eos systemd[1]: netctl@ethernet\x2ddhcp.service: Main process exited, code=exited, status=1/FAILURE
jul 08 10:03:16 eos systemd[1]: netctl@ethernet\x2ddhcp.service: Failed with result 'exit-code'.
jul 08 10:03:17 eos systemd[1]: Failed to start Networking for netctl profile ethernet-dhcp.
and:
journalctl -xeu "netctl@ethernet\\x2ddhcp.service"
~
jul 08 10:03:16 eos systemd[1]: Starting Networking for netctl profile ethernet-dhcp...
░░ Subject: A start job for unit netctl@ethernet\x2ddhcp.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit netctl@ethernet\x2ddhcp.service has begun execution.
░░
░░ The job identifier is 7324.
jul 08 10:03:16 eos network[622974]: Profile 'ethernet-dhcp' does not exist or is not readable
jul 08 10:03:16 eos systemd[1]: netctl@ethernet\x2ddhcp.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit netctl@ethernet\x2ddhcp.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
jul 08 10:03:16 eos systemd[1]: netctl@ethernet\x2ddhcp.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit netctl@ethernet\x2ddhcp.service has entered the 'failed' state with result 'exit-code'.
jul 08 10:03:17 eos systemd[1]: Failed to start Networking for netctl profile ethernet-dhcp.
░░ Subject: A start job for unit netctl@ethernet\x2ddhcp.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit netctl@ethernet\x2ddhcp.service has finished with a failure.
░░
░░ The job identifier is 7324 and the job result is failed.
Here comes one update. I don’t know what changed, but the issue doesn’t seem to happen anymore, at least not today after waking up the machine after being suspended during the weekend. Thanks for your help.
Cheers, Manuel