what is installed to be similar to tcpdump since tcpdump is not installed? the date is off about 11 months in the past which disables net resolution in dd-wrt. Apparently ARP is in play here, as I am seeing lots of this in a tcpdump =ieno1|grep amanda here on this machine but I see no answers: 16:42:20.926695 ARP, Request who-has amanda.coyote.den tell 0.0.0.0, length 46 16:42:20.926695 ARP, Request who-has amanda.coyote.den tell 0.0.0.0, length 46 16:42:20.926695 ARP, Request who-has amanda.coyote.den tell 0.0.0.0, length 46 16:42:20.926695 ARP, Request who-has amanda.coyote.den tell amanda.coyote.den, length 46 16:42:21.470873 ARP, Request who-has amanda.coyote.den tell amanda.coyote.den, length 46 16:42:23.288701 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:24.320147 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:25.344176 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:26.370963 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:27.392224 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:28.416249 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:29.445598 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:30.468289 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:31.488315 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:32.513828 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:33.536356 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 So the protocol is at least transmitting from amanda. This is evidence of dd-wrt ignoring the wrong timestamp because amanda's date is about 11 months out of sync. there is no settime installed so there's no way for be to manually fix that. I got this bit of info by commenting out the "pool" lines forcing chrony to use the "server 192.168.71.3 iburst" in the chrony subdir servers.d/ file. So I wrote another copy of the latest Armbian_26.2.1_Bananapim5_noble_current_6.18.15_xfce_desktop.img to another new 128G card, and fdisk then id's it as having an msdos partition table, skipping 8k and having a 6.4G ext4 as /dev/sdc1 and undefined for the remainder of the card. So I quit fdisk and ran gparted on /dev/sdc/ and selected data recovery. Which warned that it would take a long time, 6.5 hours later its still scanning. blue bar slowly marching back and forth in the progress line at the bottom of the gparted screen. Hopefully recovering enough data to write a valid ext4 partition table & see if /dev/sdc1 is mountable AND bootable. I have since found a cli reboot won't, but a powerdown will if the card was written with a bs=4096. That is where I am with backups of the whole houses still sitting in a /raid6 I can't rebuild w/o net access to install both gfs2 and mdadm from the repo's. So this is a trail report, not a success story. if this fails. I get a 6 pack of 32Giggers which I know WILL work with an msdos table. But that doesn't give the cards adequate room to do housekeeping meaning they will fail in less then a year. Once working I have not had a failure of a 64G card or a 128G card.

@HenricoLegal can you find the wifi chip on your board?

What should the correctly enabled I2C service (for a 40x2 LCD) look like on Bananapim2pro? Should I edit the armbianEnv.txt file and add, for example, the following entry: overlays=i2c0 i2c1? The armbian-config service is a bit confusing, and after editing it, I get this: ........................ verbosity=1 console=both overlay_prefix=meson fdtfile=amlogic/meson-sm1-bananapi-m2-pro.dtb rootdev=UUID=a4fb8074-c453-45da-ab31-4d61dca46cfa rootfstype=ext4 overlays=i2cA i2cB usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u .................. There are other options, but they probably don't apply to bananapim2pro. : sm1-odroid-c4-i2c0 g12b-bananapi-cm4-i2c2 g12a-radxa-zero-i2c-ao....

Hey everyone! I have a TV Box labeled “In Xplus”, running on an Allwinner H313 (most likely a generic/rebranded device). I was able to install Linux on it using Armbian 26.2.0-trunk (Trixie). The system boots normally, but I’m facing network issues: - Wi-Fi is not working (no interface detected) - Ethernet is also not working (only interface is lo) So basically, the system runs fine, but I have no network connectivity at all. My questions: - Is this a current limitation of Armbian support for the H313? - Is there any specific DTB or patch that could fix Wi-Fi/Ethernet? - Is there a more stable Armbian version or another distro with better support? - Has anyone managed to get networking working on this chip? Any help or shared experience would be greatly appreciated. Thanks!

Nicely done. As some additional thoughts: 1. Fragment 0 and 2 of your .dts point to the same spot. They could be combined if you'd like. 2. The util-linux-extra package should be part of the core Ubuntu distribution. An apt install should have been enough, though you may need to enable the universe repository. 3. If you have a /dev/rtc1 device, that suggests that you have an rtc0 as well, and if you disable it, the kernel will natively load and store time to the one you provided. A quick glance at the .dts suggests one at /soc/bus@ff800000/rtc@a8. Adding one final fragment to your overlay like the below might allow you to skip need of hwclock, and both SystemD services for your RTC. See my note about CONFIG_RTC_HCTOSYS_DEVICE and CONFIG_RTC_SYSTOHC_DEVICE above. fragment@3 { target-path = "/soc/bus@ff800000/rtc@a8"; __overlay__ { status = "disabled"; }; }; 4. If you're up for it, submit a PR to create a dtbo for the I2C buses on the M5? Contributions to the project are always welcome.