rnsi

Hi ManoftheSea, First, thanks for your work on this. But I don't think I understand your comments. You then go on to mention: So which is it? systemd-networkd or not? The image I downloaded has NetworkManager active by default. I assume the ports are flagged as unmanaged so the user can ENABLE only the services needed, rather than try to hunt down and DISABLE the unneeded services. It would have saved a bit of time if that were documented somewhere. But it doesn't matter now. The system is working and seems stable so far.

Update: I changed /boot/armbianEnv.txt, set board_version to v7. Now I also have "led2" in /sys/class/leds. Still missing "led3" though.

I got the EspressoBin v7 running with Armbian_23.5.1_Espressobin_jammy_current_5.15.113_minimal. Trying to control the LEDs, but they are not where I would expect them: # ls -al /sys/class/leds/ total 0 drwxr-xr-x 2 root root 0 Dec 31 1969 . drwxr-xr-x 57 root root 0 Dec 31 1969 .. lrwxrwxrwx 1 root root 0 Dec 31 1969 mmc0:: -> ../../devices/platform/soc/soc:internal-regs@d0000000/ d00d0000.sdhci/leds/mmc0:: Only one LED is listed. Where are the others? How can I enable them?

I believe I solved it. No need to add anything to /etc/network/interfaces Instead, edit /etc/NetworkManager/conf.d/10-ignore-interfaces.conf. This file instructs NetworkManager to ignore all of the ethernet ports. Remove those entries. /etc/NetworkManager/conf.d/10-ignore-interfaces.conf: [keyfile] unmanaged-devices=interface-name:br* I don't know what br* is, so I left it in there. Reboot and the network connects with DHCP as it should. Update /etc/network/interfaces if you need static addresses.

systemd-networkd is masked, and nmcli & networkctl shows everything as unmanaged. It seems like networking is disabled in this image. When I unmasked and enabled systemd-networkd, it didn't complete boot.

Create a script with the following: ip link set lan0 up dhclient then create a service file: /etc/systemd/system/lan0.service [Unit] Description=Start lan0 [Service] ExecStart=/usr/bin/bash /path/to/script.sh [Install] WantedBy=multi-user.target then "systemctl daemon-reload" and "systemctl enable lan0". reboot While this will auto start lan0, it does not fix the issue of why doesn't the lan auto start out of the box. It also doesn't reconnect if the network drops. It seems that Armbian on EspressoBin doesn't expect to use the network. I might try GTI's filesystem next to see if I have better results. Though I doubt I'll ever see updates from them.

I've "solved" this problem by adding a systemd service to start lan0, but this is clearly not an ideal solution. Still looking for the right fix. I've tried with jammy and jammy minimal, and bookworm and bookworm minimal with the same results. Also, it seems that dhclient is not installed in either bookworm image. Are these images expecting no network connections?

I've got Jammy Minimal running on my EspressoBin v7 from Armbian_23.5.1_Espressobin_jammy_current_5.15.113_minimal. All seems to be working except the NICs do not auto-start with the system. Only lo starts. I have to "ip link set lan0 up" and "dhclient" each time it reboots. My /etc/network/interfaces: source /etc/network/interfaces.d/* # Network is managed by Network manager auto lo iface lo inet loopback auto lan0 allow-hotplug lan0 iface lan0 inet dhcp The NetworkManager.service is running. How do I make lan0 auto start? Thanks

Hello- Just got my EspressoBin v7, trying to boot to SD using Armbian 23.02 Bullseye. Followed instructions at https://www.armbian.com/espressobin/. Board is 2GB, so I used flash-image-DDR4-2g_2cs_6-1200_750.bin. U-Boot showed CPU runs at 1200, and I confirmed "C120" on the chip. Interrupt boot process bubt flash-image-DDR4-2g_2cs_6-1200_750.bin spi usb env default -a saveenv Flashed Armbian_23.02.2_Espressobin_bullseye_current_5.15.93_minimal.img to a new SanDisk SD card with belenaEtcher and dd. Board doesn't boot, I get "Wrong image format for "source" command" then it tries to boot other devices. I've tried a second new SD card and both minimal and not minimal filesystems with the same result. Any suggestions or advice is greatly appreciated. My U-Boot output: TIM-1.0 mv_ddr-devel-g251bc63 DDR4 16b 2GB 2CS WTMI-devel-18.12.1-1d97715 WTMI: system early-init SVC REV: 5, CPU VDD voltage: 1.225V Setting clocks: CPU 1200 MHz, DDR 750 MHz CZ.NIC's Armada 3720 Secure Firmware 0b68a33-dirty (May 16 2022 17:51:06) Running on ESPRESSObin NOTICE: Booting Trusted Firmware NOTICE: BL1: v2.6(release):a921da5e NOTICE: BL1: Built : 17:55:48, May 16 2022 NOTICE: BL1: Booting BL2 NOTICE: BL2: v2.6(release):a921da5e NOTICE: BL2: Built : 17:55:48, May 16 2022 NOTICE: BL1: Booting BL31 NOTICE: BL31: v2.6(release):a921da5e NOTICE: BL31: Built : 17:55:48, May 16 2022 U-Boot 2022.04-armbian (May 16 2022 - 17:50:52 +0000) DRAM: 2 GiB Core: 38 devices, 20 uclasses, devicetree: fit WDT: Not starting watchdog@8300 Comphy chip #0: Comphy-0: USB3_HOST0 5 Gbps Comphy-1: PEX0 5 Gbps Comphy-2: SATA0 6 Gbps SATA link 0 timeout. AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode flags: ncq led only pmp fbss pio slum part sxs PCIe: Link down MMC: sdhci@d0000: 0, sdhci@d8000: 1 Loading Environment from SPIFlash... SF: Detected mx25u3235f with page size 256 Bytes, erase size 4 KiB, total 4 MiB OK Model: Globalscale Marvell ESPRESSOBin Board Net: eth0: ethernet@30000 Hit any key to stop autoboot: 0 MMC Device 1 not found no mmc device at slot 1 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr load - load binary file from a filesystem Usage: load <interface> [<dev[:part]> [<addr> [<filename> [bytes [pos]]]]] - Load binary file 'filename' from partition 'part' on device type 'interface' instance 'dev' to address 'addr' in memory. 'bytes' gives the size to load in bytes. If 'bytes' is 0 or omitted, the file is read until the end. 'pos' gives the file byte position to start reading from. If 'pos' is 0 or omitted, the file is read from the start. ## Executing script at 06000000 Wrong image format for "source" command SCRIPT FAILED: continuing... libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk sdhci@d0000.blk... Found 2 disks No EFI system partition ERROR: invalid device tree starting USB... Bus usb@58000: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 Bus usb@5e000: USB EHCI 1.00 scanning bus usb@58000 for devices... 1 USB Device(s) found scanning bus usb@5e000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: unknown device scanning bus for devices... Device 0: unknown device (NULL udevice *): mvneta_setup_txqs: can't create txq=0 BOOTP broadcast 1 timeout: packet not sent BOOTP broadcast 2 timeout: packet not sent BOOTP broadcast 3 timeout: packet not sent My printenv: => printenv boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr} boot_efi_binary=load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootaa64.efi; if fdt addr ${fdt_addr_r}; then bootefi ${kei boot_efi_bootmgr=if fdt addr ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr;fi boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_syslinux_conf} boot_net_usb_start=usb start boot_pci_enum=pci enum boot_prefixes=/ /boot/ boot_script_dhcp=boot.scr.uimg boot_scripts=boot.scr.uimg boot.scr boot_syslinux_conf=extlinux/extlinux.conf boot_targets=mmc1 mmc0 usb0 scsi0 pxe dhcp bootcmd=run distro_bootcmd bootcmd_dhcp=devtype=dhcp; run boot_net_usb_start; run boot_pci_enum; if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi;se; bootcmd_mmc0=devnum=0; run mmc_boot bootcmd_mmc1=devnum=1; run mmc_boot bootcmd_pxe=run boot_net_usb_start; run boot_pci_enum; dhcp; if pxe get; then pxe boot; fi bootcmd_scsi0=devnum=0; run scsi_boot bootcmd_usb0=devnum=0; run usb_boot bootfstype=ext4 criptaddr=0x6d00000 distro_bootcmd=scsi_need_init=; setenv nvme_need_init; for target in ${boot_targets}; do run bootcmd_${target}; done efi_dtb_prefixes=/ /dtb/ /dtb/current/ eth1addr=00:51:82:11:22:01 eth2addr=00:51:82:11:22:02 eth3addr=00:51:82:11:22:03 ethact=ethernet@30000 ethaddr=00:51:82:11:22:00 fdt_addr=0x6f00000 fdt_addr_r=0x6f00000 fdtcontroladdr=7fadcf40 fdtfile=marvell/armada-3720-espressobin-v7.dtb kernel_addr=0x7000000 kernel_addr_r=0x7000000 load_efi_dtb=load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefix}${efi_fdtfile} mmc_boot=if mmc dev ${devnum}; then devtype=mmc; run scan_dev_for_boot_part; fi nvme_boot=run boot_pci_enum; run nvme_init; if nvme dev ${devnum}; then devtype=nvme; run scan_dev_for_boot_part; fi nvme_init=if ${nvme_need_init}; then setenv nvme_need_init false; nvme scan; fi pxefile_addr_r=0x6e00000 ramdisk_addr_r=0xa000000 sata_boot=if sata dev ${devnum}; then devtype=sata; run scan_dev_for_boot_part; fi scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run sca; scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devpt scan_dev_for_efi=setenv efi_fdtfile ${fdtfile}; for prefix in ${efi_dtb_prefixes}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefixe scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${boot_syslinux_conf}; then echo Found ${prefix}${boot_syslinuxi scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Be scsi_boot=run boot_pci_enum; run scsi_init; if scsi dev ${devnum}; then devtype=scsi; run scan_dev_for_boot_part; fi scsi_init=if ${scsi_need_init}; then scsi_need_init=false; scsi scan; fi stderr=serial@12000 stdin=serial@12000 stdout=serial@12000 usb_boot=usb start; if usb dev ${devnum}; then devtype=usb; run scan_dev_for_boot_part; fi ver=U-Boot 2022.04-armbian (May 16 2022 - 17:50:52 +0000) Environment size: 4408/65532 bytes