franck102

Hi all, After a restart and after a few days go by my My Orange Pi 4 LTS randomly loses its ability to make outbound network connections. I can ssh into the box, however for some reason the routing tables are empty: > ping 192.168.1.53 ping: connect: Network is unreachable > netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface The box is connected through an ethernet cable, configured to used DHCP, but I see no IPv4 address in the interface configuration: > ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 2a01:cb15:81c2:e500:6cba:b008:2761:e29a prefixlen 64 scopeid 0x0<global> inet6 2a01:cb15:81c2:e500:e971:fd8d:4d26:e65 prefixlen 64 scopeid 0x0<global> inet6 fe80::9935:bbd1:a503:c83a prefixlen 64 scopeid 0x20<link> inet6 2a01:cb15:81c2:e500:681d:5fa0:94fd:9e1a prefixlen 64 scopeid 0x0<global> ether 72:d7:a6:97:4b:cf txqueuelen 1000 (Ethernet) RX packets 195548 bytes 16128189 (16.1 MB) RX errors 0 dropped 13442 overruns 0 frame 0 TX packets 22932 bytes 2779612 (2.7 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 31 I am new to armbian, and not sure where to go to troubleshoot from there. /etc/networks/interfaces is empty, how is eth0 configured? I can resolve the issue by issuing > sudo ip link eth0 down && sudo ip link eth0 up ... and I have added a cron entry doing just that, but obviously I would like to understand where the issue is coming from. Here is some system information: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy Linux orangepi4-lts 5.15.76-rockchip64 #22.08.8 SMP PREEMPT Sun Oct 30 10:57:32 CET 2022 aarch64 aarch64 aarch64 GNU/Linux Thanks! Franck EDIT: here is what I find in journalctl, it looks like the eth0 interface goes down shortly (4mn) after a reboot and never comes back up correctly: Apr 17 06:17:28 orangepi4-lts NetworkManager[1626]: <info> [1681705048.7753] dhcp4 (eth0): state changed new lease, address=192.168.0.102 <normal network manager startup> Apr 17 06:17:28 orangepi4-lts NetworkManager[1626]: <info> [1681705048.8306] device (eth0): Activation: successful, device activated. ... Apr 17 06:17:29 orangepi4-lts nm-dispatcher[2142]: /etc/network/if-up.d/resolved: 12: mystatedir: not found Apr 17 06:17:32 orangepi4-lts kernel: rk_gmac-dwmac fe300000.ethernet eth0: Link is Down Apr 17 06:17:32 orangepi4-lts systemd[1]: systemd-fsckd.service: Deactivated successfully. Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.3960] device (eth0): carrier: link connected Apr 17 06:17:36 orangepi4-lts kernel: rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.3968] device (eth0): ip:dhcp4: restarting Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.4136] dhcp4 (eth0): canceled DHCP transaction Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.4138] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.4139] dhcp4 (eth0): state changed no lease Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.4144] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.4305] dhcp4 (eth0): state changed new lease, address=192.168.0.102 <from this point on, outbound connections are failing, e.g. Apr 17 06:17:38 orangepi4-lts telegraf[1790]: 2023-04-17T04:17:38Z E! [agent] Error writing to outputs.influxdb_v2: failed to send metrics to any configured server(s) > Apr 17 06:17:42 orangepi4-lts systemd[1]: systemd-hostnamed.service: Deactivated successfully. Apr 17 06:17:46 orangepi4-lts systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Apr 17 06:18:28 orangepi4-lts NetworkManager[1626]: <info> [1681705108.9445] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Apr 17 06:18:28 orangepi4-lts NetworkManager[1626]: <info> [1681705108.9446] dhcp4 (eth0): state changed no lease Apr 17 06:18:58 orangepi4-lts systemd-resolved[794]: eth0: Bus client set search domain list to: home Apr 17 06:18:58 orangepi4-lts systemd-resolved[794]: eth0: Bus client set DNS server list to: 192.168.0.254, 2a01:cb15:81c2:e500:7ec1:77ff:fe90:48f0 Apr 17 06:18:58 orangepi4-lts systemd[1]: Starting resolvconf-pull-resolved.service... Apr 17 06:18:58 orangepi4-lts sh[2217]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf Apr 17 06:19:14 orangepi4-lts systemd-resolved[794]: eth0: Bus client set DNS server list to: 2a01:cb15:81c2:e500:7ec1:77ff:fe90:48f0

I am using the officially supported version, Jammy 22.08 CLI, and the board has the 16Gb emmc. The board has 2 USB 2 ports I believe, and only one USB 3 type A port (the other one is type C) I have some serial adapters lying around from Arduino projects, I’ll try to set that up when I find the time. Franck

Hi all, I have a fresh install of Armbian Jammy on an Orange Pi 4 LTS, everything works fine as long as I boot the device with nothing plugged into any of the USB ports. If a USB device is plugged in, the system doesn't boot: nothing comes out on HDMI, and the network doesn't come up. There is steady red light, and a green led flashing in groups of 2. I have the same symptoms in all these configurations: - boot from SD / system on SD - boot from EMMC / system on EMMC - boot from SD / system on USB drive - for all the above a USB keyboard or the USB drive fail the boot if they are plugged in when I power on. I am using the original power supply. If I plug in the keyboard or disk after booting everything works as expected. The last combination (system on USB drive) is what I need to achieve, so I am a bit stuck here. I haven't tried to setup a serial interface, is there any way to see all boot messages from the previous - failed - boot? Thanks! Franck [Edit]: I managed to boot by plugging just the USB drive into one of the 2 USB 2 ports (instead of USB 3). Not sure yet if that is reliable or not (power issue vs. driver issue?)

Hi ChecMate, Just FYI I am seeing the same thing on an Orange Pi 4 LTS that I am setting up, what worked for me was to unplug the keyboard to let the boot start, then plug it in later. I tried 2 keyboards and both USB 2 & 3 ports, and the problem is consistent, if I boot with the kb plugged in the HDMI remains dead. Franck