y52

I ve understood it already earlier today and changed several settings under the Systemd style. Check the root@espressobin:/etc/systemd/network# cat 10-wan.network [Match] Name=wan [Network] #Bridge=br0 DHCP=ipv4 I believe, that #Bridge=br0 should be disabled, as mentioned earlier. Now the bridge shows root@espressobin:/etc/systemd/network# brctl show bridge name bridge id STP enabled interfaces br0 8000.bab24a6a1ecd no lan0 lan1 I still don't understand the eth0 designation, and I am troubled with the mac address usage. root@espressobin:/etc/systemd/network# ip addr show 2: eth0: link/ether 00:51:82:11:22:00 3: wan@eth0: link/ether 00:51:82:11:22:00 4: lan0@eth0: link/ether 00:51:82:11:22:00 5: lan1@eth0: link/ether 00:51:82:11:22:00 Why are wan, lan0 and lan1 bound to @eth0 and mac addresses are the same for 4 interfaces? What is the eth0 used for ?

I have trouble understanding i-net interfaces on Armbian and the way setting them up. The bridge always includes the wan, while I thought that the latter should not be part of it. Wan should service an external network segment, while the lan i-faces are intended for the lan segment, as their name stand for. root@espressobin:~# brctl show bridge name bridge id STP enabled interfaces br0 8000.bab24a6a1ecd no lan0 lan1 wan Even if I want to remove the wan from the bridge, I am unable doing so. root@espressobin:~# brctl delif br0 wan Gives no changes to the bridge. The following sources show, that the bridge is assembled from lan0, lan1 and wan : https://github.com/armbian/build/tree/master/packages/bsp/mvebu64 while eth0 is a stand alone one. Could the development team clarify each network interface designation ? How could a network be set up? What is the use of MAC addresses, which are built into the u-boot loader? My board lists the following in the boot loader, eth1addr=00:51:82:11:22:01 eth2addr=00:51:82:11:22:02 eth3addr=00:51:82:11:22:03 ethact=neta@30000 ethaddr=00:51:82:11:22:00 while a single ethaddr is assigned to all 4 ports lan0, lan1, eth0 and wan by Armbian (which is strange for me). Some changes were made to the system, which altered the way the interfaces are configured. Thus, I am unable propagating my network settings through the /etc/network/interfaces configuration. ebin-dev commented on 23 Sep 2017 • fix of 'job for raising network interfaces' interrupting the boot sequence: systemd-networkd is configured as a switch (with bridged interfaces) NetworkManager is configured not to manage any interface

New Kernel panic log on a quiet system (1000/800): root@espressobin:~# ifconfig root@espressobin:~# [ 145.919967] Bad mode in Synchronous Abort handler detected, code 0x86000018 -- IABT (current EL) [ 145.928804] Internal error: Oops - bad mode: 0 [#1] PREEMPT SMP [ 145.935185] Modules linked in: xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo bridge stp llc ip_tables x_tables [ 145.948080] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.112-mvebu64 #8 [ 145.954821] Hardware name: Marvell Armada 3720 Community Board (DT) [ 145.961208] task: ffffffc0784d0000 ti: ffffffc0784cc000 task.ti: ffffffc0784cc000 [ 145.969220] PC is at rcu_idle_enter+0x0/0x58 [ 145.973801] LR is at cpu_startup_entry+0x10c/0x218 [ 145.978486] pc : [<ffffffc0001058e8>] lr : [<ffffffc0000efb6c>] pstate: 200001c5 [ 145.986398] sp : ffffffc0784cff70 [ 145.989731] x29: ffffffc0784cff70 x28: 0000000000000000 [ 145.995134] x27: 0000000000000000 x26: ffffffc0784cc000 [ 146.000625] x25: ffffffc000db2000 x24: ffffffc000d8c000 [ 146.006114] x23: ffffffc0009fb000 x22: ffffffc0784cff70 [ 146.011603] x21: ffffffc000d88ac0 x20: ffffffc000db2ae8 [ 146.017096] x19: ffffffc000db2000 x18: 0000000000000000 [ 146.022587] x17: 0000007f95539e18 x16: 0000000000000000 [ 146.028079] x15: 0000000000000000 x14: 0000000000000000 [ 146.033571] x13: 0000000000000000 x12: 0000000000000000 [ 146.039060] x11: 00000000afb50401 x10: 00000000000007a0 [ 146.044551] x9 : ffffffc0784cfed0 x8 : 00000000ffff6974 [ 146.050042] x7 : 00000021f981b620 x6 : 0000000000000001 [ 146.055532] x5 : 000000007e246000 x4 : 0000000000000000 [ 146.061024] x3 : 00000000000001c0 x2 : ffffffc000e4e008 [ 146.066513] x1 : 000000007e246000 x0 : 0000000000000000 [ 146.072002] [ 146.073534] Process swapper/1 (pid: 0, stack limit = 0xffffffc0784cc020) [ 146.080461] Stack: (0xffffffc0784cff70 to 0xffffffc0784d0000) [ 146.086398] ff60: ffffffc0784cffd0 ffffffc00008e368 [ 146.094404] ff80: 0000000000000001 0000000000000e12 ffffffc000e406b0 0000000000000000 [ 146.102408] ffa0: 0000000000000000 0000000000000000 0000000000e85000 0000000000e88000 [ 146.110412] ffc0: ffffffc000082810 0000000000000000 0000000000000000 00000000000827fc [ 146.118955] ffe0: 0000000000000000 0000000000000000 5555555555555555 5555555555555555 [ 146.127054] Call trace: [ 146.129493] [<ffffffc0001058e8>] rcu_idle_enter+0x0/0x58 [ 146.134981] [<ffffffc00008e368>] secondary_start_kernel+0x130/0x158 [ 146.141363] [<00000000000827fc>] 0x827fc [ 146.145324] Code: 88017c40 35ffffa1 d5033bbf d65f03c0 (a9bf7bfd) [ 146.151854] ---[ end trace 23c4e4d5739f5e1a ]--- [ 146.156590] Kernel panic - not syncing: Attempted to kill the idle task! [ 146.163448] CPU0: stopping [ 146.163459] CPU: 0 PID: 1 Comm: systemd Tainted: G D 4.4.112-mvebu64 #8 [ 146.163462] Hardware name: Marvell Armada 3720 Community Board (DT) [ 146.163463] Call trace: [ 146.163478] [<ffffffc000089910>] dump_backtrace+0x0/0x108 [ 146.163484] [<ffffffc000089a2c>] show_stack+0x14/0x20 [ 146.163490] [<ffffffc0004eab68>] dump_stack+0x98/0xb8 [ 146.163496] [<ffffffc00008e8a8>] handle_IPI+0x1a8/0x1b8 [ 146.163500] [<ffffffc000082598>] gic_handle_irq+0x78/0x168 [ 146.163504] Exception stack(0xffffffc0784838d0 to 0xffffffc078483a00) [ 146.163508] 38c0: ffffffc078478000 0000008000000000 [ 146.163512] 38e0: ffffffc078483a30 ffffffc0009e8280 0000000060000145 0000000000000000 [ 146.163517] 3900: ffffffc07efc2f00 0000000000004ac7 000000007e236000 0000000000000002 [ 146.163521] 3920: 00000000000100eb 0000000000000000 0000000000000000 ffffffc07efc2fc0 [ 146.163525] 3940: ffffffc078478800 ffffffc078483a70 00000000000007a0 ffffffc0779bdd00 [ 146.163529] 3960: 0000000000000003 00000000000e9a18 0000000000000008 003b9aca00000000 [ 146.163533] 3980: 0000007fa8bd6b28 0000007fa8a8b300 0000000000000061 ffffffc078478000 [ 146.163537] 39a0: ffffffc07efc2f00 0000000000000000 ffffffc0770b0b80 ffffffc0009e496c [ 146.163542] 39c0: 0000000000000000 ffffffc0009e44e4 0000000000000000 0000005588f8c1d0 [ 146.163546] 39e0: ffffffc078483dd0 ffffffc078483a30 ffffffc0000d8188 ffffffc078483a30 [ 146.163551] [<ffffffc000085700>] el1_irq+0x80/0xf8 [ 146.163556] [<ffffffc0000d8188>] finish_task_switch+0x70/0x220 [ 146.163565] [<ffffffc0009e44e4>] __schedule+0x194/0x5d8 [ 146.163569] [<ffffffc0009e496c>] schedule+0x44/0xb8 [ 146.163575] [<ffffffc0009e7600>] schedule_timeout+0x158/0x1a8 [ 146.163578] [<ffffffc0009e6580>] __down+0x60/0x98 [ 146.163585] [<ffffffc0000f1704>] down+0x4c/0x68 [ 146.163590] [<ffffffc0000f62a8>] console_lock+0x18/0x38 [ 146.163598] [<ffffffc000678ab8>] show_cons_active+0x20/0x150 [ 146.163605] [<ffffffc0006bbe80>] dev_attr_show+0x20/0x58 [ 146.163611] [<ffffffc00023d1f4>] sysfs_kf_seq_show+0xb4/0x148 [ 146.163615] [<ffffffc00023bb48>] kernfs_seq_show+0x28/0x30 [ 146.163622] [<ffffffc0001eb22c>] seq_read+0x174/0x420 [ 146.163625] [<ffffffc00023c5bc>] kernfs_fop_read+0x10c/0x198 [ 146.163632] [<ffffffc0001c7208>] __vfs_read+0x18/0x40 [ 146.163637] [<ffffffc0001c7a1c>] vfs_read+0x7c/0x148 [ 146.163641] [<ffffffc0001c8624>] SyS_read+0x44/0xa0 [ 146.163646] [<ffffffc000085e30>] el0_svc_naked+0x24/0x28 [ 146.394930] ---[ end Kernel panic - not syncing: Attempted to kill the idle task!

Yes! It looks true. I've used the saveenv to save my custom variable into the u-boot. The warning has disappeared : flags: ncq led only pmp fbss pio slum part sxs PCIE-0: Link down MMC: sdhci@d0000: 0 SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB Net: eth0: neta@30000 [PRIME] I am looking now setting the network up correctly with 1x wan dhcp and 2x switch i-faces with fixed ips for lan. Has anybody useful configuration or link to setup ? Automated boot from USB is still necessary as well.

Surprisingly, rebooting the system now with the same settings gives a more stable behavior. root@espressobin:~# armbianmonitor -u System diagnosis information will now be uploaded to http://ix.io/OR6 It is quite quiet now: root@espressobin:~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq 20:20:55: 200MHz 0.02 5% 2% 2% 0% 0% 0% 20:21:00: 200MHz 0.02 3% 1% 0% 0% 0% 0% 20:21:06: 0MHz 0.01 1% 1% 0% 0% 0% 0% 20:21:11: 0MHz 0.01 3% 2% 0% 0% 0% 0%

Is the U-Boot log warning meaningful in any way? SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB *** Warning - bad CRC, using default environment Still looking on how to boot in an unattended way from USB.

Do you think, that the hardware is defective? What should I claim to RMA ? I flashed the firmware with the 800_800 image. U-Boot 2017.03-armada-17.10.1-g440395a (Sep 25 2017 - 15:43:51 +0200) Model: Marvell Armada 3720 Community Board ESPRESSOBin CPU @ 800 [MHz] L2 @ 800 [MHz] TClock @ 200 [MHz] DDR @ 800 [MHz] DRAM: 2 GiB The Armbian turns stable. and very quiet. root@espressobin:~# cat /proc/version Linux version 4.4.112-mvebu64 (root@xeon) (gcc version 6.4.1 20171012 (Linaro GCC 6.4-2017.11) ) #8 SMP PREEMPT Wed Jan 24 22:53:43 CET 2018 root@espressobin:~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq 17:27:45: 800MHz 0.12 8% 2% 4% 0% 1% 0% 17:27:50: 0MHz 0.11 1% 1% 0% 0% 0% 0% The scaling works as well: root@espressobin:~# cpufreq-info available frequency steps: 200 MHz, 267 MHz, 400 MHz, 800 MHz I also changed root@espressobin:~# vi /etc/init.d/cpufrequtils ENABLE="true" #GOVERNOR="ondemand" GOVERNOR="conservative" Then I moved back to 1000/800 flash Marvell>> bubt uboot/flash-image-2g-1000_800_boot_sd_and_usb.bin spi usb After booting the Armbian the troubles reappeared back : Welcome to ARMBIAN 5.38 stable Debian GNU/Linux 9 (stretch) 4.4.112-mvebu64 I am accessing the terminal through ssh with the serial cable detached at this stage. sk@espressobin:~$ su - root Password: The login took a minute delay and error mistakes appeared : root@espressobin:~# Message from syslogd@localhost at Feb 24 17:52:59 ... kernel:[ 115.263491] Call trace: Message from syslogd@localhost at Feb 24 17:52:59 ... kernel:[ 115.283741] Call trace: Message from syslogd@localhost at Feb 24 17:53:02 ... kernel:[ 117.609757] Call trace: Message from syslogd@localhost at Feb 24 17:53:02 ... kernel:[ 117.681345] Call trace: The load increased significantly on a quiet system : root@espressobin:~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq 17:55:52: 1000MHz 10.89 52% 47% 4% 0% 0% 0% 17:55:57: 1000MHz 10.90 50% 50% 0% 0% 0% 0% 17:56:02: 1000MHz 10.91 50% 50% 0% 0% 0% 0% 17:56:07: 1000MHz 10.91 50% 50% 0% 0% 0% 0% And finally everything stopped working : Message from syslogd@localhost at Feb 24 18:22:26 ... kernel:[ 1882.169758] Call trace: Message from syslogd@localhost at Feb 24 18:22:26 ... kernel:[ 1882.241982] Call trace: root@espressobin:~# armbianmonitor -m -su: fork: retry: Resource temporarily unavailable -su: fork: retry: Resource temporarily unavailable -su: fork: retry: Resource temporarily unavailable sk@espressobin:~$ su - root -bash: fork: retry: Resource temporarily unavailable Error messages are repetitive every couple of minutes. Message from syslogd@localhost at Feb 24 18:57:06 ... kernel:[ 3961.829759] Call trace: Message from syslogd@localhost at Feb 24 18:57:06 ... kernel:[ 3961.901992] Call trace: Anyway, you can do nothing with the system now. root@espressobin:~# shutdown -r now -su: fork: retry: Resource temporarily unavailable -su: fork: retry: Resource temporarily unavailable What is your expert's advice : is that a faulty hardware, firmware problem or the one of Armbian? Could somebody point me on how to boot from USB automatically , in an unattended way?

I've been able to restore the board through the SATA recovery procedure. My next experience was re-trying the 2G-1200/750, which bricked the board again. I downgraded to the 2G-1000/800 and booted Armbian (several times), but it didn't resulted in a stable system. I was not even able loggin in any single time. I flashed the U-boot with the Espressobin's bootloader again : U-Boot 2017.03-armada-17.06.3-ga33ecb8 (Jul 05 2017 - 14:30:47 +0800) Model: Marvell Armada 3720 Community Board ESPRESSOBin CPU @ 1000 [MHz] L2 @ 800 [MHz] TClock @ 200 [MHz] DDR @ 800 [MHz] DRAM: 2 GiB U-Boot DComphy-0: USB3 5 Gbps Comphy-1: PEX0 2.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-0: Link down MMC: sdhci@d0000: 0 SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB *** Warning - bad CRC, using default environment It shows this bad CRC warning again. The Armbian boots, but halts again even before allowing to log in. The overall experience is just discouraging : there is no any single workable configuration with Armbian for my board. Is there any solution?

I was running the Marvell>> version U-Boot 2017.03-armada-17.10.1-g440395a (Sep 25 2017 - 15:43:51 +0200) aarch64-linux-gnu-gcc (Linaro GCC 6.3-2017.05) 6.3.1 20170404 GNU ld (Linaro_Binutils-2017.05) 2.27.0.20161019 I tried switching to 1200/750 firmware: Marvell>> bubt uboot/flash-image-2g-1200_750_boot_sd_and_usb.bin spi usb Burning U-BOOT image "uboot/flash-image-2g-1200_750_boot_sd_and_usb.bin" from "usb" to "spi" USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 2 USB Device(s) found Image checksum...OK! SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB 24576 bytes written, 795896 bytes skipped in 0.583s, speed 1438635 B/s Done! As the result, my boad is bricked completely and the U-boot stops at : ---------------------------------------------------- SVC_REV:3 Any suggestions on how recover the board now?

I believe you changed this setting before booting the system? Anyway, a 5 days uptime is not a high record for a presumably router application, where high availability is required. How could I boot from USB without manual startup ?

Where is the governor setting set or changed ? This kernel instability was not observed on Yocto and Openwrt distributions provided by Espressobin. Does Armbian build creates one?

If any bugs are necessary, I have raised some : I am running a flash-image-2g-1000_800_boot_sd_and_usb.bin The U-Boot 2017.03-armada-17.10.1-g440395a (Sep 25 2017 - 15:43:51 +0200) shows a weird bad CRC (see the above log): SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB *** Warning - bad CRC, using default environment I have finally been able booting with manual U-Boot settings : setenv image_name boot/Image setenv fdt_name boot/dtb/marvell/armada-3720-community.dtb setenv rootdev "/dev/sda1" setenv rootfstype "ext4" setenv verbosity "1" setenv bootusb 'usb reset; ext4load usb 0:1 $kernel_addr $image_name;ext4load usb 0:1 $initrd_addr $initrd_image;ext4load usb 0:1 $fdt_addr $fdt_name;setenv bootargs $console root=$rootdev rw rootwait; booti $kernel_addr - $fdt_addr' run bootusb [ 0.185230] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.195207] futex hash table entries: 512 (order: 4, 65536 bytes) [ 0.202201] xor: measuring software checksum speed [ 0.246557] 8regs : 1919.000 MB/sec [ 0.290588] 8regs_prefetch: 1711.000 MB/sec [ 0.334620] 32regs : 2359.000 MB/sec [ 0.378655] 32regs_prefetch: 1983.000 MB/sec [ 0.383325] xor: using function: 32regs (2359.000 MB/sec) [ 0.388899] pinctrl core: initialized pinctrl subsystem [ 0.395208] NET: Registered protocol family 16 [ 0.411752] cpuidle: using governor ladder [ 0.427920] cpuidle: using governor menu [ 0.432050] vdso: 2 pages (1 code @ ffffffc000db1000, 1 data @ ffffffc000db0000) [ 0.439616] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 0.448354] DMA: preallocated 2048 KiB pool for atomic allocations [ 0.454744] Serial: AMBA PL011 UART driver [ 0.460094] d0012000.serial: ttyMV0 at MMIO 0xd0012000 (irq = 8, base_baud = 0) is a mvebu-uart [ 0.469000] console [ttyMV0] enabled [ 0.469000] console [ttyMV0] enabled [ 0.476342] bootconsole [uart0] disabled [ 0.476342] bootconsole [uart0] disabled ....... [ OK ] Started /etc/rc.local Compatibility. [ OK ] Started LSB: Advanced IEEE 802.11 management daemon. [ OK ] Started LSB: disk temperature monitoring daemon. [ OK ] Started Serial Getty on ttyMV0. [ OK ] Started Getty on tty1. [ OK ] Started Serial Getty on ttyS0. [ OK ] Reached target Login Prompts. [ OK ] Started Authorization Manager. [ OK ] Started LSB: Start NTP daemon. [ OK ] Started LSB: Armbian gathering hardware information. [ OK ] Reached target Multi-User System. [ OK ] Reached target Graphical Interface. Starting Update UTMP about System Runlevel Changes... [ OK ] Started Update UTMP about System Runlevel Changes. Debian GNU/Linux 9 espressobin ttyMV0 espressobin login: Before I was able logging in for the 1st time, the kernel raised an exception : [ 162.674661] Unable to handle kernel NULL pointer dereference at virtual address 000008f9 [ 162.682875] pgd = ffffffc000e88000 [ 162.686472] [000008f9] *pgd=0000000078406003, *pud=0000000078406003, *pmd=0000000078407003, *pte=00e80000d1d00707 [ 162.697016] Internal error: Oops: 96000005 [#1] PREEMPT SMP [ 162.702687] Modules linked in: bridge stp llc ip_tables x_tables [ 162.708996] CPU: 0 PID: 7 Comm: rcu_preempt Not tainted 4.4.112-mvebu64 #8 [ 162.716193] Hardware name: Marvell Armada 3720 Community Board (DT) [ 162.722319] task: ffffffc07847c500 ti: ffffffc0784b8000 task.ti: ffffffc0784b8000 [ 162.730069] PC is at update_blocked_averages+0x84/0x4c0 [ 162.735911] LR is at update_blocked_averages+0x38/0x4c0 [ 162.740961] pc : [<ffffffc0000e2624>] lr : [<ffffffc0000e25d8>] pstate: 200001c5 [ 162.748880] sp : ffffffc0784bbbb0 [ 162.751945] x29: ffffffc0784bbbb0 x28: ffffffc07efc2f00 [ 162.757709] x27: ffffffc07efc2f68 x26: 0000000000000000 [ 162.763202] x25: 0000000000000000 x24: ffffffc07847c970 [ 162.768695] x23: ffffffc0009e496c x22: 0000000000000000 [ 162.774188] x21: ffffffc000db2000 x20: ffffffc07efc2f00 [ 162.779679] x19: 00000000000001c0 x18: ffffffc000e38890 [ 162.785176] x17: 0000000000000001 x16: 0000000000000007 [ 162.790671] x15: 0000000000000000 x14: 0000000000000000 [ 162.796166] x13: 0000000000000000 x12: 0000000000000000 [ 162.801662] x11: 00000000afb50401 x10: afb504000afb5041 [ 162.807156] x9 : ffffffc000a00000 x8 : ffffffc000a00970 [ 162.812651] x7 : ffffffc07efc37a8 x6 : ffffffc077141e58 [ 162.818144] x5 : 000000000000009f x4 : ffffffc077b79c00 [ 162.823639] x3 : 0000000000000000 x2 : 00000025e029edb0 [ 162.829131] x1 : 0000000000000001 x0 : 0000000000000000 [ 162.834623] [ 162.836335] Process rcu_preempt (pid: 7, stack limit = 0xffffffc0784b8020) [ 162.843274] Stack: (0xffffffc0784bbbb0 to 0xffffffc0784bc000) [ 162.848948] bba0: ffffffc0784bbbe0 ffffffc0000e9668 [ 162.857409] bbc0: 00000000ffff7ac7 ffffffc000d8c000 ffffffc0784bbbe0 ffffffc0000e9660 [ 162.865511] bbe0: ffffffc0784bbc80 ffffffc0009e4434 ffffffc07efc2f00 ffffffc000d8c000 [ 162.873615] bc00: ffffffc000db2000 ffffffc07847c500 ffffffc0009e496c ffffffc07847c970 [ 162.881626] bc20: 0000000000000000 0000000000000000 0000000000000001 0000000000000001 [ 162.889909] bc40: ffffffc07efc2f00 ffffffc07efc2f68 ffffffc000a00820 ffffffc07847c500 [ 162.897930] bc60: 000000017efc2f00 00000000ffff79ce 00000001009e496c ffffffc07847c500 [ 162.906124] bc80: ffffffc0784bbcd0 ffffffc0009e496c ffffffc0784b8000 ffffffc0784bbd50 [ 162.914235] bca0: ffffffc000db2000 00000000ffff79ce ffffffc07efbeb80 ffffffc0784bbd80 [ 162.922345] bcc0: 0000000000000003 0000000000000000 ffffffc0784bbcf0 ffffffc0009e75a8 [ 162.930276] bce0: ffffffc07efbeb80 ffffffc0009e75a4 ffffffc0784bbd80 ffffffc000107728 [ 162.938469] bd00: ffffffc000dc8800 ffffffc000dc8b20 ffffffc000db2000 0000000000000001 [ 162.946482] bd20: ffffffc000dc8000 ffffffc000106910 ffffffc07efc3d80 ffffffc000dc8800 [ 162.954673] bd40: ffffffc0784bbd50 0000000000000140 0000000000000000 ffffffc07efbf228 [ 162.962867] bd60: 00000000ffff79ce ffffffc00010ac20 ffffffc07847c500 ffffffff00000000 [ 162.970795] bd80: ffffffc0784bbe20 ffffffc0000d3250 ffffffc07842e080 ffffffc000e44058 [ 162.979076] bda0: ffffffc000c2af10 ffffffc000dc8800 ffffffc0001071c8 0000000000000000 [ 162.987095] bdc0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 162.995109] bde0: ffffffc0784b8000 0000028000000000 00ffffc0784bbe20 ffffffc000000000 [ 163.003392] be00: ffffffc07847c500 ffffffc0000ef6e8 ffffffc000dc8b28 ffffffc000dc8b28 [ 163.011411] be20: 0000000000000000 ffffffc000085dd0 ffffffc0000d3158 ffffffc07842e080 [ 163.019603] be40: 0000000000000000 0000000000000000 0000000000000000 ffffffc0000dc438 [ 163.027622] be60: ffffffc0000d3158 0000000000000000 0000000000000000 ffffffc000dc8800 [ 163.035726] be80: 0000000000000000 0000000000000000 ffffffc0784bbe90 ffffffc0784bbe90 [ 163.043738] bea0: 0000000000000000 ffffffc000000000 ffffffc0784bbeb0 ffffffc0784bbeb0 [ 163.051929] bec0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 163.060032] bee0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 163.068046] bf00: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 163.076326] bf20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 163.084257] bf40: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 163.092181] bf60: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 163.100460] bf80: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 163.108654] bfa0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 163.116757] bfc0: 0000000000000000 0000000000000005 0000000000000000 0000000000000000 [ 163.124861] bfe0: 0000000000000000 0000000000000000 5555555555555555 5555555555555555 [ 163.133049] Call trace: [ 163.135579] [<ffffffc0000e2624>] update_blocked_averages+0x84/0x4c0 [ 163.141621] [<ffffffc0000e9668>] pick_next_task_fair+0x240/0x520 [ 163.148104] [<ffffffc0009e4434>] __schedule+0xe4/0x5d8 [ 163.153323] [<ffffffc0009e496c>] schedule+0x44/0xb8 [ 163.158456] [<ffffffc0009e75a8>] schedule_timeout+0x100/0x1a8 [ 163.164489] [<ffffffc000107728>] rcu_gp_kthread+0x560/0x818 [ 163.170160] [<ffffffc0000d3250>] kthread+0xf8/0x110 [ 163.174933] [<ffffffc000085dd0>] ret_from_fork+0x10/0x40 [ 163.180783] Code: b9411c80 35001900 f9406081 f9408880 (f9447c22) How could a USB boot be automated ? Does this kernel panic come from a 800 Mhz ram setting ?

I've flashed the u-boot with Marvell>> bubt flash-image-2g-1000_800_boot_sd_and_usb.bin spi usb Then I deployed the image to the USB flash, as I have no spare SD card. dd if=Armbian_5.38_Espressobin_Debian_stretch_default_4.4.112.img of=/dev/sdb bs=1M oflag=direct Anyway, I was unable to boot from USB flash, despite that Armbian instructions claim , that "After updating your SPI flash with most recent "sd_and_usb" u-boot, you can boot from USB or SD card the exact same way." ---------------------------------------------------- SVC_REV:3 SVC_REV:3 NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.3(release):devel-17.08.1:627667b NOTICE: BL1: Built : 14:40:36, Oct 4 2NOTICE: BL2: v1.3(release):devel-17.08.1:627667b NOTICE: BL2: Built : 14:40:36, Oct 4 2017 NNOTICE: BL31: v1.3(release):devel-17.08.1:627667b NOTICE: BL31: U-Boot 2017.03-armada-17.10.1-g440395a (Sep 25 2017 - 15:43:51 +0200) Model: Marvell Armada 3720 Community Board ESPRESSOBin CPU @ 1000 [MHz] L2 @ 800 [MHz] TClock @ 200 [MHz] DDR @ 800 [MHz] DRAM: 2 GiB U-Boot DT blob at : 000000007f7182d8 Comphy-0: USB3 5 Gbps Comphy-1: PEX0 2.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-0: Link down MMC: sdhci@d0000: 0 SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB *** Warning - bad CRC, using default environment Net: eth0: neta@30000 [PRIME] Hit any key to stop autoboot: 0 *** ERROR: `serverip' not set *** ERROR: `serverip' not set Bad Linux ARM64 Image magic! Am I wrong somewhere ? How could I boot from a USB flash? I was able to successfully boot from USB both OpenWRT and Yocto from Espressobin site.

and here is my 1st SPi log : root@orangepiplus:~/bin# kermit kermit-usb0.conf Connecting to /dev/ttyUSB0, speed 115200 Escape character: Ctrl-\ (ASCII 28, FS): enabled Type the escape character followed by C to get back, or followed by ? to see other options. ---------------------------------------------------- NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.3(release):armada-17.06.2:a37c108 NOTICE: BL1: Built : 14:31:03, Jul 5 2NOTICE: BL2: v1.3(release):armada-17.06.2:a37c108 NOTICE: BL2: Built : 14:31:04, Jul 5 20NOTICE: BL31: v1.3(release):armada-17.06.2:a37c108 NOTICE: BL31: U-Boot 2017.03-armada-17.06.3-ga33ecb8 (Jul 05 2017 - 14:30:47 +0800) Model: Marvell Armada 3720 Community Board ESPRESSOBin CPU @ 1000 [MHz] L2 @ 800 [MHz] TClock @ 200 [MHz] DDR @ 800 [MHz] DRAM: 2 GiB U-Boot DComphy-0: USB3 5 Gbps Comphy-1: PEX0 2.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-0: Link down MMC: sdhci@d0000: 0 SF: Detected w25q32dw with page size 256 Bytes, erase size 4 KiB, total 4 MiB Net: eth0: neta@30000 [PRIME] Hit any key to stop autoboot: 0 Card did not respond to voltage select! mmc_init: -95, time 41 MMC Device 0 not found no mmc device at slot 0 Card did not respond to voltage select! mmc_init: -95, time 23 ** Bad device mmc 0 ** Card did not respond to voltage select! mmc_init: -95, time 23 ** Bad device mmc 0 ** Bad Linux ARM64 Image magic! Marvell>> I can now experiment with Armbian boot flash. Which file should I choose for now ?

I received my 2G board today, which shows the V5_0_1. The frequency is shown nowhere and the IC markings are unreadable. Where to start with the board setup ?

I shall probably join the testers' efforts as I've ordered a 2GB board for my project. Anyway, it is not delivered yet and I have no clues as for the board version and the memory frequency. The install process will need to be discovered as well, as I understand it is not a simple image flash process. Extending your board bringing up instructions could be helpful.

I looked into Clearfog pro, but I would wish at least 2GB RAM (if not more) to run other applications conveniently. I also looked into Espressobin, ARMADA 8040 Community Board and BeagleBoard-X15 ARM Cortex-A15, which are horribly expensive. Compared to the named above, BPI-R2 offers an interesting alternative, But I do agree with you, that the lack of a stable OS and support from the vendor will diminish all the advantages to nothing.

Given the rotten Vendor's practice, it is probably worth looking for another hardware solution for the router. Is there any other alternative vendor building his board around the MediaTek MT7623N SoC ? Could your prompt any?

Hello, I am quite enthusiastic about the hardware-built features, like network acceleration, QoS and ipsec in this SOC. and I was looking for the siilar hardware at a reasonable price for quite a while. Anyway, I do agree (and my proper past experience also proved it), BPI's reputation could be restrictive for a buying decision. Is there any other alternative vendor building his board around the MediaTek MT7623N SoC ? Will you build an image for that board? Regards, Serge

Hello, MTK have launced a MT7623 based SOC with the interesting BPI-R2 smart router board : http://forum.banana-pi.org/t/banana-pi-bpi-r1-bpi-r2-smart-router-board-comparison-20170612/3390 I am quite enthusiastic about the hardware build features, like network acceleration, QoS and ipsec in this SOC. Will you build an image for thet board? Regards, Serge

I use the dongle root@bananapi:~# lsusb Bus 002 Device 002: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter root@bananapi:~# lsmod Module Size Used by ccm 8074 3 rt2800usb 17554 0 rt2800lib 71732 1 rt2800usb rt2x00usb 8815 1 rt2800usb rt2x00lib 37161 3 rt2x00usb,rt2800lib,rt2800usb mac80211 533155 3 rt2x00lib,rt2x00usb,rt2800lib The problem is that the driver spawns a single wlan : root@bananapi:~# ifconfig wlan0 Link encap:Ethernet HWaddr 00:01:e0:10:30:1d UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:783127 errors:0 dropped:0 overruns:0 frame:0 TX packets:1350158 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:142627539 (136.0 MiB) TX bytes:661366756 (630.7 MiB) How is it possible adding additional interface with "iw" ? Will they be completely independent and functional?

BPI M1 is not equipped with the integrated WiFi. I use an external USB dongle, which loads root@bananapi:~# lsmod Module Size Used by rt2800usb 17554 0 rt2800lib 71732 1 rt2800usb rt2x00usb 8815 1 rt2800usb rt2x00lib 37161 3 rt2x00usb,rt2800lib,rt2800usb mac80211 533155 3 rt2x00lib,rt2x00usb,rt2800lib Would it be possible for it to spin the second wlan ? Are other solutions available, rather than rebuilding the driver?

Hi, Jernej I have two boards : OPI + (H3) and BPI M1 (A20), each running Armbians It is not the p2p (if I understand it correctly), that I want, but rather 2 different wlanX's. I can only connect with the WIFI in certain circumstances, so I need to get the i-net connection with the wlan0 and make it available to the other clients through the hostapd on the wlan1.

How is it possible to add the second wireless interface bound to the same physical WiFi adapter? This question is brought up from the following thread : http://forum.armbian.com/index.php/topic/1346-howto-create-software-wireless-access-point/ This was already discussed. I and Igor disabled second interface in Makefile before building it, because it is confusing for most users (at least from my point of view). Talking how to rebuild driver with this option enabled is off topic... --- I am running Armbian on OPI+ and BPI. How is it possible to add the second wireless interface bound to the same physical WiFi adapter? The goal is to configure the wlan0 in AP mode with hostapd and wlan1 in managed mode with wpa_supplicant, I need to redistribute the WiFi access on a different router.

I am running Armbian on OPI+ and BPI. How is it possible to add the second wireless interface bound to the same physical WiFi adapter? The goal is to configure the wlan0 in AP mode with hostapd and wlan1 in managed mode with wpa_supplicant, I need to redistribute the WiFi access on a different router.