09:54 <narmstrong> BrainDamage: this is a question for xdarklight !

15:17 <xdarklight> BrainDamage: from which kernel version did you update and to which version?

15:31 <BrainDamage> xdarklight: 5.8.0 to 5.8.9

15:32 <xdarklight> BrainDamage: hmm, there's not Ethernet related changes in those kernel versions. do you have the kernel log for me when it's *not* working

15:33 <BrainDamage> one moment

15:39 <BrainDamage> xdarklight: https://paste.rs/KZ7

15:52 <xdarklight> BrainDamage: would you be able to re-compile only the .dtb file and do some experiments for me?

15:53 <BrainDamage> sure, but I don't know exactly how

15:54 <xdarklight> BrainDamage: ok, alternative question: do you have a serial console attached to your board and can add some additional commands in u-boot?

15:54 <BrainDamage> yes

15:55 <xdarklight> ah, that's the easier way then. can you please paste the commands you are currently using to boot? then I can tell you where to add my experimental command(s) (which can be easily undone, no devices will be harmed in this process ;) )

16:02 <BrainDamage> xdarklight: https://paste.rs/f0l

16:02 <BrainDamage> yes, it's an ancient version of u-boot

16:02 <BrainDamage> and I know that this line loads the device tree ext4load mmc 0:1 0x21800000 /boot/meson8b-odroidc1.dtb

16:02 <xdarklight> we have nothing better

16:03 <xdarklight> can you please add the following two lines, right before the "bootm" command at the end of the file?

16:03 <xdarklight> fdt set /soc/ethernet@c9410000/mdio/ethernet-phy@0 reset-assert-us <100000>

16:03 <xdarklight> fdt set /soc/ethernet@c9410000/mdio/ethernet-phy@0 reset-deassert-us <300000>

16:03 <BrainDamage> sure

16:04 <xdarklight> I had some users report "issues" with the PHY reset timings. I'm unable to reproduce that problem and not sure what causes this. so my first idea is: we multiply all the delays by 10 compared to what's upstream and see if that works around your issue

16:04 <xdarklight> (next steps would be to either identify the root cause or at least to find "better" timings instead of just multiplying the existing ones by 10)

16:07 <BrainDamage> xdarklight: https://paste.rs/w3P link is still out

16:10 <BrainDamage> boot.ini, to confirm I didn't fail copypasta: https://paste.rs/kEK

16:10 <xdarklight> BrainDamage: "interesting" - nothing seems to have changed. can you please upload your /boot/meson8b-odroidc1.dtb somewhere please?

16:13 <BrainDamage> xdarklight: https://filebin.net/za62s1rfzmg6zgnb/meson8b-odroidc1.dtb?t=7ttuu2c7

16:17 <xdarklight> hmm

16:18 <xdarklight> that one is looking good

16:19 <xdarklight> can you manually run dhcpcd (or any dhcp client which you have installed) to rule out that <some network configuration tool> has unrelated problems?

16:20 <BrainDamage> sure, one moment that I install that on

16:20 <BrainDamage> having a chroot with qemu-guest is a bliss to debug arm boards

16:26 <xdarklight> also let me update my Odroid-C1 to the latest Arch Linux ARM build and boot that kernel (instead of booting linux-next and/or 5.9-rc + patches)

16:27 <BrainDamage> still no luck: https://paste.rs/UYs

16:28 <BrainDamage> fwiw, I've also attempted a manual configuration of the link, but no data gets RX'ed still

16:29 <BrainDamage> this is with manual configuration: https://paste.rs/KeH

16:34 <xdarklight> ok. first observation on my own Odroid-C1+ (after plugging in the Ethernet cable...): with 5.9-rc + patches Ethernet is working fine

16:35 <BrainDamage> mmm, this is a c1, not a c1+

16:35 <xdarklight> I'm updating Arch Linux ARM now so I can test with the same kernel version as you

16:35 <BrainDamage> however, no major changes to ethernet to my knowledge

16:35 <xdarklight> AFAIK there are no Ethernet related changes between C1 and C1+ (only CEC, audio headers and some other small bits)

16:36 <BrainDamage> yup, CEC in C1 requires the RTC bat because of faulty wiring

17:04 <xdarklight> BrainDamage: argh, Arch Linux ARM's default kernel has CONFIG_MMC_MESON_MX_SDHC disabled. I need to update my SD card to make things boot...

17:04 <xdarklight> for now I'll make dinner and come back afterwards

17:05 <xdarklight> also I'm interested why you build your own kernel for Arch Linux ARM instead of using the "default" one

17:08 <BrainDamage> I'm not building my own, I'm using arch arm's vanilla kernel, the odroid official one is ancient

17:08 <BrainDamage> and unfortunately I need some features of more recent kernels

17:09 <BrainDamage> linux-armv7-odroidc1 is in the repos

17:10 <BrainDamage> also, I just realized I forgot to execute sd-fusing after eding the boot, so thhe config didn't apply

17:14 <BrainDamage> buuut, still no network

20:38 <xdarklight> BrainDamage: ah, it's a misunderstanding then. I thought you didn't want to compile the kernel *again* because it takes long

20:39 <xdarklight> BrainDamage: also Ethernet "just works" on my Odroid-C1+ with: Linux alarm 5.8.9-1-ARCH #1 SMP PREEMPT Sat Sep 12 20:20:55 UTC 2020 armv7l GNU/Linux

20:47 <xdarklight> BrainDamage: have you tried connecting your Odroid-C1 to a different switch port or maybe directly to your computer?

21:40 <BrainDamage> xdarklight: yes for the switch port, I've confirmed that the port works by using other machines, moreover, it's two c1s that got the same problem simultaneousl

21:42 <xdarklight> hmm

21:42 <xdarklight> between 5.8.1 and 5.8.9 there's only two stmmac related commits, both are in 5.8.3: https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.8.3

21:43 <xdarklight> both are related to hardware multicast filtering

21:44 <BrainDamage> thanks for all your help so far btw

21:52 <xdarklight> you're welcome

21:52 <xdarklight> I just checked the two stmmac commits

21:52 <xdarklight> one is mis-labeled and only affects Qualcomm platforms

21:52 <xdarklight> that leaves only https://github.com/torvalds/linux/commit/df43dd526e6609769ae513a81443c7aa727c8ca3

21:53 <xdarklight> sorry, wrong link - that's the only only affecting Qualcomm platforms

21:53 <xdarklight> the correct link is https://github.com/torvalds/linux/commit/592d751c1e174df5ff219946908b005eb48934b3

21:54 <BrainDamage> mmm, now I'm wondering something stupid

21:54 <BrainDamage> if it's something else in userspace that's not the network manager that's crippling the ethernet

21:54 <BrainDamage> I'll try to boot to pid1 being bash

21:55 <BrainDamage> then try to manually configure the ethernet card

21:56 <xdarklight> if that's too much effort try including this initramfs: https://filebin.net/4obzlg896t6wfbfj/initramfs.uImage?t=kfogzk8e

21:57 <xdarklight> load it similar to how uImage is loaded (I use 0x22000000 as target address) and then pass it as the middle value to the "bootm" command (currently there's only a dash in your boot.ini)

21:57 <xdarklight> then boot without having a root filesystem specified in the kernel cmdline

22:25 <BrainDamage> using your image the ethernet device isn't found, do have I to load the kernel module manually?

22:25 <BrainDamage> https://paste.rs/PBU

22:27 <BrainDamage> actually, I'm running out of stamina for the day, I'll crash to bed and resume tomorrow evening

22:27 <BrainDamage> thanks again for your help