klippe

  • Posts

    11
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

klippe's Achievements

  1. I've recently reinstalled Armbian - my previous version faced the eth issue discussed here but after some reboots and network restarts it usually started to work. But then at some point network died completely and I wasn't able to connect to a network at all. So I've installed latest "Armbian 21.05.6 Buster with Linux 5.10.43-meson64". I can see (cd /usr/lib/linux-u-boot[tab]) that it runs "linux-u-boot-odroidhc4-current_21.08.1_arm64" and you know what... the issue is still there. I've just restarted my odroid-hc4 and have no network. Since the u-boot 21.08.1 is newer than aforementioned 2021.07-rc1 it looks that the issue is still not resolved :(.
  2. Ok, so... mindblow. 1. I built image from trunk and booted my hc4 with it. 2. No network. 3. Followed steps from legogris. No network 4. added eth0 to /etc/network/interfaces (auth eth0 and iface eth0 inet dhcp and hotplug) 5. then some reboots dhclient calls, tried disconnecting-connectnig cable (because of hotplug) etc. and... suddenly network started to work. 6. power off, power on and network still works. Cool, right? So then: 1. I tried with stable image 2. booted - network works out of the box No idea what's going on here but hope it'll stay like that. Thanks for the support guys.
  3. I know it may look like that but: 1. I've tried different cables and router ports. Also no other device connected to the router has any network issues. 2. networks works correctly on 4.9 3. the issue only happens on 5.10 and only for the first boot (when the device is powered on). Then after a soft `reboot` network is up and working with no issues.
  4. Here we go: `ip a` 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 valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:1e:06:49:08:b4 brd ff:ff:ff:ff:ff:ff inet6 fe80::e90d:fe83:a2ab:20a6/64 scope link noprefixroute valid_lft forever preferred_lft forever dmesg [ 49.219978] EXT4-fs (mmcblk0p1): resizing filesystem from 450560 to 7712800 blocks [ 55.903177] random: crng init done [ 55.903184] random: 7 urandom warning(s) missed due to ratelimiting [ 60.237243] EXT4-fs (mmcblk0p1): resized to 3145728 blocks [ 70.748887] EXT4-fs (mmcblk0p1): resized to 5767168 blocks [ 78.799163] EXT4-fs (mmcblk0p1): resized filesystem to 7712800 [ 80.669353] meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet] (irq=41) [ 80.683035] meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found [ 80.683050] meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW [ 80.683403] meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rgmii link mode [ 94.359985] meson8b-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 94.360023] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 103.828834] logitech-hidpp-device 0003:046D:2007.0005: HID++ 1.0 device connected. [ 178.512669] meson8b-dwmac ff3f0000.ethernet eth0: Link is Down [ 181.713569] meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet] (irq=41) [ 181.728888] meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found [ 181.728911] meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW [ 181.728928] meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rgmii link mode [ 195.627538] meson8b-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 195.627582] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  5. Yes. I've installed 5.10 again. What I did was: $ ip link set eth0 down; sleep 1; rmmod realtek; sleep 1; modprobe realtek; sleep 1; ip link set eth0 up $ dhclient -r $ dhclient eth0
  6. Have never done it before but I can try. Anything specific that should be included in the config? Guessing amlogic support.
  7. Thanks. However the problem is that after switching to nightly my device no longer boots so I've no way to check network o_O
  8. Thanks. I've tried that but with no effect. Still eth0 not active after that (tried dhclient eth0 to re-fetch ip etc.).
  9. No, it's not the case Thanks but it's not the case. I've tried different cables and ports but the main thing is that all's good with network when I go back to armbian based on 4.9 kernel. Just in that case it doesn't see my HDDs. So kind of stuck here. More in the thread on the Odroid forum: https://forum.odroid.com/viewtopic.php?f=203&t=41456&p=323150
  10. Oops. Sorry, here's the correct link to the armbianmonitor's output: http://ix.io/2Rh8
  11. Hello, I'm facing a weird issue where a network connection doesn't work after my HC4 is started (after a power off), but then after calling a `reboot` network starts to work. I'm running a fresh install of the latest "Armbian Buster mainline kernel 5.10.y". More details in armbianmonitor's output: http://ix.io/2Rh8 http://ix.io/2Req I've tried playing with /etc/network/interfaces by putting stuff like the following there: allow-hotplug eth0 no-auto-down eth0 auto eth0 iface eth0 inet dhcp also tried static ip but nothing works. What exactly is happening? 1. When I power on my HC4 it awaits for network for a longer while (A start job is running for Raise network interfaces) and then finally boots with no network working. 2. ifconfig shows eth0 and lo interfaces. eth0 has no IP set. I cannot connect to the device from outside not reach network from it. 3. then I run `reboot` (need to connect a screen and a keyboard to the device :/) and the device boots quickly with network up and working Any ideas how to resolve that?