Jump to content

ABF023

Members
  • Posts

    22
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. I understand your decision, thank you for your continuous support🌻🌻
  2. hi ManoftheSea~ Except add the "v5 emmc" and "v7 emmc" configurations to it, How to use UEFI booting? I would like to refer to your usage Thank you.
  3. hi ManoftheSea~🥺
  4. Probably understood~ Thank you for all your help and replies, look forward to the new version to solve these problems, thank you again ~~
  5. hi~ManoftheSea: here's another problem.When I full-upgrade, the network does not start automatically, I need to execute: root@espressobin:~# ifconfig eth0 up root@espressobin:~# dhclient wan /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf root@espressobin:~# After execution, I can get the LAN IP, but I can't resolve the domain name, and then I add dns to /etc/resolv.conf to resolve the domain name normally When I restart, I need to repeat the operation again, how can I get it up and running automatically?
  6. This can be executed, but there is no information output..Only one ‘disabled’ output root@espressobin:~# cat /proc/device-tree/soc/internal-regs@d0000000/sdhci@d8000/status disabled root@espressobin:~#
  7. Yes, it's in there,thanks root@espressobin:/boot/dtb/marvell# ls armada-3720-db.dtb armada-8040-mcbin-singleshot.dtb armada-3720-espressobin.dtb armada-8040-puzzle-m801.dtb armada-3720-espressobin-emmc.dtb armada-8080-db.dtb armada-3720-espressobin-ultra.dtb cn9130-crb-A.dtb armada-3720-espressobin-v7.dtb cn9130-crb-B.dtb armada-3720-espressobin-v7-emmc.dtb cn9130-db-B.dtb armada-3720-turris-mox.dtb cn9130-db.dtb armada-3720-uDPU.dtb cn9131-db-B.dtb armada-7040-db.dtb cn9131-db.dtb armada-8040-clearfog-gt-8k.dtb cn9132-db-B.dtb armada-8040-db.dtb cn9132-db.dtb armada-8040-mcbin.dtb
  8. OK, yes. After adding scriptaddr, it starts normally
  9. root@espressobin:~# cat /boot/armbianEnv.txt board_version=v7 verbosity=1 rootdev=UUID=ea6c33de-9fb0-4d48-afc8-639a9682ec9a rootfstype=ext4 fdtfile=marvell/armada-3720-espressobin-v7-emmc.dtb
  10. root@espressobin:~# cat /proc/device-tree/soc/internal-regs@d0000000/sdhci@d8000 cat: /proc/device-tree/soc/internal-regs@d0000000/sdhci@d8000: Is a directory root@espressobin:~# cd /proc/device-tree/soc/internal-regs@d0000000/sdhci@d8000 root@espressobin:/proc/device-tree/soc/internal-regs@d0000000/sdhci@d8000# ls '#address-cells' interrupts mmc-ddr-1_8v pinctrl-names bus-width marvell,pad-type mmc-hs400-1_8v reg clock-names marvell,xenon-emmc name '#size-cells' clocks marvell,xenon-tun-count non-removable status compatible mmccard@0 pinctrl-0
  11. 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.213V 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 list sdhci@d0000: 0 sdhci@d8000: 1 => mmc dev 0 MMC: no card present => mmc dev 1 switch to partitions #0, OK mmc1(part 0) is current device => mmcinfo Device: sdhci@d8000 Manufacturer ID: 15 OEM: 0 Name: 4FTE4R Bus Speed: 52000000 Mode: MMC High Speed (52MHz) Rd Block Len: 512 MMC version 5.1 High Capacity: Yes Capacity: 3.6 GiB Bus Width: 8-bit Erase Group Size: 512 KiB HC WP Group Size: 8 MiB User Capacity: 3.6 GiB WRREL Boot Capacity: 4 MiB ENH RPMB Capacity: 512 KiB ENH Boot area 0 is not write protected Boot area 1 is not write protected When I enter armbian, mmc cannot be detected........Several versions have the same problem, 22.11, 22.08, 22.05 root@espressobin:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 1 28.7G 0 disk └─sda1 8:1 1 28.4G 0 part / mtdblock0 31:0 0 3.9M 0 disk mtdblock1 31:1 0 64K 0 disk zram0 254:0 0 993.7M 0 disk [SWAP] zram1 254:1 0 50M 0 disk /var/log zram2 254:2 0 993.7M 0 disk /tmp root@espressobin:~# dmesg|grep -i mmc [ 1.393013] mmc0: SDHCI controller on d00d0000.sdhci [d00d0000.sdhci] using ADMA
  12. Starting resolvconf-pull-resolved.service... [ OK ] Finished resolvconf-pull-resolved.service. Starting resolvconf-pull-resolved.service... [ OK ] Finished resolvconf-pull-resolved.service. Starting resolvconf-pull-resolved.service... [ OK ] Finished resolvconf-pull-resolved.service. Starting resolvconf-pull-resolved.service... [ OK ] Finished resolvconf-pull-resolved.service. [ ***] A start job is running for Wait for… to be Configured (57s / no limit) I stay here for a long time every time I start... Does anyone know why? Then an error message appears: [ OK ] Finished resolvconf-pull-resolved.service. Starting resolvconf-pull-resolved.service... [ OK ] Finished resolvconf-pull-resolved.service. [FAILED] Failed to start Wait for Network to be Configured. See 'systemctl status systemd-networkd-wait-online.service' for details. [ OK ] Reached target Network is Online. Starting LSB: Advanced IEEE 802.11 management daemon... Starting /etc/rc.local Compatibility... [ OK ] Started LSB: Advanced IEEE 802.11 management daemon. [ OK ] Started /etc/rc.local Compatibility. Then when I follow the error prompt, the following message appears: root@espressobin:~# systemctl status systemd-networkd-wait-online.service ● systemd-networkd-wait-online.service - Wait for Network to be Configured Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; > Active: failed (Result: exit-code) since Thu 2022-11-10 12:34:58 UTC; 5min> Docs: man:systemd-networkd-wait-online.service(8) Process: 667 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exit> Main PID: 667 (code=exited, status=1/FAILURE) CPU: 153ms Nov 10 12:34:58 espressobin systemd-networkd-wait-online[667]: Event loop faile> Nov 10 12:34:58 espressobin systemd[1]: systemd-networkd-wait-online.service: M> Nov 10 12:34:58 espressobin systemd[1]: systemd-networkd-wait-online.service: F> Nov 10 12:34:58 espressobin systemd[1]: Failed to start Wait for Network to be > Warning: journal has been rotated since unit was started, output may be incompl
  13. Thank you very much. The printenv information is as follows:
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines