An update for those interested and a help request for feedback if someone can/knows how to go about the remaining problem(s) or issue(s).
Update
I have managed to archive something rather unthinkable...
For more details on that check here https://github.com/mvp/uhubctl/discussions/563
and then
Here are the loggs
status_before_uhubctl.txtoutput_of_uhubctl.txt
status_after_uhubctl.txt
As you can see my eth1 now has UP status, which means I did not have to physically remove the NIC and reattach it again.
Now for the help part,
Could someone please explain how I can go about and get rid of service fail during the boot see log below or maybe since I'm using systemd-networkd the solution is to put above commands which basically power cycle of the USB port into the bootscript somehow as a service. This approach may not be the best I know but it will solve the "Failed to start systemd-networkd-wait-online.service" once and for all. (or am I far of and totally wrong?)
Please help me out here if you can!
Here is the log
Update
I have managed to archive something rather unthinkable...
For more details on that check here https://github.com/mvp/uhubctl/discussions/563
Code:
sudo apt-get updatesudo apt-get install git -ygit config --global user.name "YourGitHudUserName"git config --global user.email "YourRegisterdEmailAdressOnGitHudAccount"sudo apt-get install libusb-1.0-0-devsudo git clone https://github.com/mvp/uhubctlcd uhubctlsudo makesudo make installCode:
ip a > status_before_uhubctl.txtsudo uhubctl -l 1 -a 0 > output_of_uhubctl.txtip a > status_after_uhubctl.txtHere are the loggs
status_before_uhubctl.txt
Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen> link/ether 2c:cf:67:2f:cf:9a brd ff:ff:ff:ff:ff:ffCode:
Current status for hub 2 [1d6b:0003 Linux 6.6.28+rpt-rpi-2712 xhci-hcd xHCI Host Controller xhci-hcd> Port 1: 0203 power 5gbps U0 enable connect [0bda:8151 Realtek USB 10/100/1G/2.5G LAN 001000001]Sent power off requestNew status for hub 2 [1d6b:0003 Linux 6.6.28+rpt-rpi-2712 xhci-hcd xHCI Host Controller xhci-hcd.0, > Port 1: 0080 offCurrent status for hub 1 [1d6b:0002 Linux 6.6.28+rpt-rpi-2712 xhci-hcd xHCI Host Controller xhci-hcd> Port 1: 0100 power Port 2: 0103 power enable connect [0b05:1a07 ASUSTeK ROG STRIX SCOPE RX TKL WIRELESS DELUXE]Sent power off requestNew status for hub 1 [1d6b:0002 Linux 6.6.28+rpt-rpi-2712 xhci-hcd xHCI Host Controller xhci-hcd.0, > Port 1: 0000 off Port 2: 0000 offstatus_after_uhubctl.txt
Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 2c:cf:67:2f:cf:9a brd ff:ff:ff:ff:ff:ff3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:24:27:88:29:17 brd ff:ff:ff:ff:ff:ff inet 10.0.0.10/24 metric 10 brd 10.0.0.255 scope global eth1 valid_lft forever preferred_lft forever inet6 fd75:a6e1:4b04:360:224:27ff:fe88:2917/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 1758sec preferred_lft 1758sec inet6 fe80::224:27ff:fe88:2917/64 scope link valid_lft forever preferred_lft foreverAs you can see my eth1 now has UP status, which means I did not have to physically remove the NIC and reattach it again.
Now for the help part,
Could someone please explain how I can go about and get rid of service fail during the boot see log below or maybe since I'm using systemd-networkd the solution is to put above commands which basically power cycle of the USB port into the bootscript somehow as a service. This approach may not be the best I know but it will solve the "Failed to start systemd-networkd-wait-online.service" once and for all. (or am I far of and totally wrong?)
Please help me out here if you can!
Here is the log
Code:
systemctl status systemd-networkd-wait-online.service× systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; preset: disabled) Drop-In: /etc/systemd/system/systemd-networkd-wait-online.service.d └─override.conf Active: failed (Result: exit-code) since Tue 2024-04-30 11:14:08 CEST; 24min ago Docs: man:systemd-networkd-wait-online.service(8) Process: 416 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exited, status=1/FAILURE) Main PID: 416 (code=exited, status=1/FAILURE) CPU: 9msApr 30 11:12:07 Pi5 systemd[1]: Starting systemd-networkd-wait-online.service - Wait for Network to be Configured...Apr 30 11:14:08 Pi5 systemd-networkd-wait-online[416]: Timeout occurred while waiting for network connectivity.Apr 30 11:14:08 Pi5 systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILUREApr 30 11:14:08 Pi5 systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.Apr 30 11:14:08 Pi5 systemd[1]: Failed to start systemd-networkd-wait-online.service - Wait for Network to be Configured.Statistics: Posted by Arelius — Tue Apr 30, 2024 9:48 am