if you want dhcp on wan, change /etc/systemd/network/11-wan.network and activate DHCP=ipv4 by removing the # at beginning of line and disable the static config below
this is maybe caused by some sdcards and new bootchain (Opensource ATF)
i guess you see something like this on loading uboot:
CPU: MediaTek MT7622
Model: mt7622-bpi-r64
DRAM: 1 GiB
WDT: Started with servicing (60s timeout)
MMC: mmc@11230000: 0, mmc@11240000: 1
In: serial@11002000
Out: serial@11002000
Err: serial@11002000
Net:
Warning: ethernet@1b100000 (eth0) using random MAC address - 12:60:ce:66:26:91
eth0: ethernet@1b100000
Hit any key to stop autoboot: 0
unable to read ssr
unable to read ssr
unable to select a mode
mmc_init: -524, time 600
Boot from eMMC
it is discussed here with mtk (together with a dram init issue in bl2 too causing reboot issues due to low voltage)
have you (maybe similar) errors after loading uboot (before the menu) like i’ve posted?
i suggest to use another sdcard (vendor), made good experiences with sandisk.
one other problem can be that an old gpt partition table exists (backup at the end of sdcard), but the you get an error/warning on starting uboot that main gpt does not match backup one…here you can dd the last sector of sdcard with if=/dev/zero. another way is to fix gpt with pc, but gparted overwrites the bootsector on fixing backup-gpt, so you need to reflash the first ~2MB of image to sdcard again
Mhm,gparted breaks bootsector in my case while repairing backup gpt…strage that restoring it does not work in your case…maybe block was to large…i had used the bpi-r64_sdmmc.img from my atf-repo (which contains bootheaders including uboot/fip)
Who can help me with a very simple question?
I bought the BPI-R64 (old version) but I can’t find a description of the power supply anywhere. I would very much like to know where the PLUS pole is. Is it on the inside or is it on the outside of the jack plug?