Zageron
Members-
Posts
18 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Feature / Changes requests for future Helios64 board or enclosure revisions
Zageron replied to Salamandar's topic in Rockchip
If these two things were added I would definitely get another one would be: - a transceiver / SFP+ port with onboard wiring supporting 10gbe and/or 25gbe. (10gbe ports are too big / expensive / hot for them to work cheaply on a board like this.) - A dedicated lane for the m2 SSD, or replace it with a dedicated 4x nvme slot. The machine works just fine as is otherwise, especially with the new 2.5gbe fixes. (It bodes well for the remainder of the unfixed issued. :)) (Having two would mean I could mirror the enclosure to an offsite location, though that's be pricey for the drives as I loaded mine with 4 10TB reds zzz) -
My plan is as follows: - Insert SD card. - Make a clone / back-up of boot and system using armbian-config whenever I'm about to do something major. (boot and system are both on eMMC) - "unclick" SD card and leave it in the back. - (repeat, until something breaks, and then just insert it and restore using armbian-config if something goes wrong.) I am confused by the eMMC to SD card path though. Here's some context: ❯ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 86.6M 1 loop /snap/core/10578 loop1 7:1 0 178.2M 1 loop /snap/microk8s/1866 loop2 7:2 0 86.6M 1 loop /snap/core/10585 sda 8:0 0 931.5G 0 disk ├─bcache0 253:0 0 9.1T 0 disk /mnt/storage ├─bcache1 253:128 0 9.1T 0 disk ├─bcache2 253:256 0 9.1T 0 disk └─bcache3 253:384 0 9.1T 0 disk sdb 8:16 0 9.1T 0 disk └─bcache0 253:0 0 9.1T 0 disk /mnt/storage sdc 8:32 0 9.1T 0 disk └─bcache1 253:128 0 9.1T 0 disk sdd 8:48 0 9.1T 0 disk └─bcache3 253:384 0 9.1T 0 disk sde 8:64 0 9.1T 0 disk └─bcache2 253:256 0 9.1T 0 disk mmcblk1 179:0 0 14.6G 0 disk └─mmcblk1p1 179:1 0 14.4G 0 part / mmcblk1boot0 179:32 0 4M 1 disk mmcblk1boot1 179:64 0 4M 1 disk mmcblk0 179:96 0 59.5G 0 disk └─mmcblk0p1 179:97 0 59.5G 0 part zram0 251:0 0 1.9G 0 disk [SWAP] zram1 251:1 0 50M 0 disk /var/log ❯ ls -l /sys/block/ total 0 lrwxrwxrwx 1 root root 0 Jan 5 11:46 bcache0 -> ../devices/virtual/block/bcache0 lrwxrwxrwx 1 root root 0 Jan 5 11:46 bcache1 -> ../devices/virtual/block/bcache1 lrwxrwxrwx 1 root root 0 Jan 5 11:46 bcache2 -> ../devices/virtual/block/bcache2 lrwxrwxrwx 1 root root 0 Jan 5 11:46 bcache3 -> ../devices/virtual/block/bcache3 lrwxrwxrwx 1 root root 0 Jan 5 11:46 loop0 -> ../devices/virtual/block/loop0 lrwxrwxrwx 1 root root 0 Jan 5 11:46 loop1 -> ../devices/virtual/block/loop1 lrwxrwxrwx 1 root root 0 Jan 5 11:46 loop2 -> ../devices/virtual/block/loop2 lrwxrwxrwx 1 root root 0 Jan 5 11:46 loop3 -> ../devices/virtual/block/loop3 lrwxrwxrwx 1 root root 0 Jan 5 11:46 loop4 -> ../devices/virtual/block/loop4 lrwxrwxrwx 1 root root 0 Jan 5 11:46 loop5 -> ../devices/virtual/block/loop5 lrwxrwxrwx 1 root root 0 Jan 5 11:46 loop6 -> ../devices/virtual/block/loop6 lrwxrwxrwx 1 root root 0 Jan 5 11:46 loop7 -> ../devices/virtual/block/loop7 lrwxrwxrwx 1 root root 0 Jan 5 19:38 mmcblk0 -> ../devices/platform/fe320000.mmc/mmc_host/mmc0/mmc0:aaaa/block/mmcblk0 lrwxrwxrwx 1 root root 0 Jan 5 11:46 mmcblk1 -> ../devices/platform/fe330000.sdhci/mmc_host/mmc1/mmc1:0001/block/mmcblk1 lrwxrwxrwx 1 root root 0 Jan 5 11:46 mmcblk1boot0 -> ../devices/platform/fe330000.sdhci/mmc_host/mmc1/mmc1:0001/block/mmcblk1/mmcblk1boot0 lrwxrwxrwx 1 root root 0 Jan 5 11:46 mmcblk1boot1 -> ../devices/platform/fe330000.sdhci/mmc_host/mmc1/mmc1:0001/block/mmcblk1/mmcblk1boot1 lrwxrwxrwx 1 root root 0 Jan 5 11:46 sda -> ../devices/platform/f8000000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Jan 5 11:46 sdb -> ../devices/platform/f8000000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 Jan 5 11:46 sdc -> ../devices/platform/f8000000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/ata3/host2/target2:0:0/2:0:0:0/block/sdc lrwxrwxrwx 1 root root 0 Jan 5 11:46 sdd -> ../devices/platform/f8000000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/ata4/host3/target3:0:0/3:0:0:0/block/sdd lrwxrwxrwx 1 root root 0 Jan 5 11:46 sde -> ../devices/platform/f8000000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/ata5/host4/target4:0:0/4:0:0:0/block/sde lrwxrwxrwx 1 root root 0 Jan 5 11:46 zram0 -> ../devices/virtual/block/zram0 lrwxrwxrwx 1 root root 0 Jan 5 11:46 zram1 -> ../devices/virtual/block/zram1 lrwxrwxrwx 1 root root 0 Jan 5 11:46 zram2 -> ../devices/virtual/block/zram2 ❯ sudo cat /etc/fstab # <file system> <mount point> <type> <options> <dump> <pass> tmpfs /tmp tmpfs defaults,nosuid 0 0 UUID=67ef9041-8705-49af-9bff-748ee9580b57 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 UUID=a27e49e9-329b-4bba-a6d3-ec5b23148e6c /mnt/storage btrfs defaults 0 2 - mmcblk0 is the SD card. - mmcblk1 is the eMMC, and is my boot. - What should I be clicking in armbian-config to clone my boot and system to the sd card? - Is there an alternative recommendation for making a backup? Any other recommendations? Thank you very much!
-
fwiw I've stopped using the 2.5gbe interface until this disconnection issue is resolved.
-
No amount of rebooting is resolving this issue for me.
-
After upgrade to Armbian 20.11.3 Buster with Linux 5.9.14-rockchip64 eth1 has vanished. ❯ sudo ip link show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 64:62:66:d0:06:18 brd ff:ff:ff:ff:ff:ff Any ideas? http://ix.io/2I2U
-
Ah, thank you.
-
sudo insmod /lib/modules/5.9.11-rockchip64/kernel/drivers/leds/trigger/ledtrig-netdev.ko sudo systemctl restart helios64-heartbeat-led.service
-
❯ sudo systemctl status helios64-heartbeat-led.service ● helios64-heartbeat-led.service - Enable heartbeat & network activity led on Helios64 Loaded: loaded (/etc/systemd/system/helios64-heartbeat-led.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2020-11-28 23:19:56 PST; 13min ago Process: 1158 ExecStart=/usr/bin/bash -c echo heartbeat | tee /sys/class/leds/helios64\:\:status/trigger (code=exited, status=0/SUCCESS) Process: 1177 ExecStart=/usr/bin/bash -c echo netdev | tee /sys/class/leds/helios64\:blue\:net/trigger (code=exited, status=1/FAILURE) Main PID: 1177 (code=exited, status=1/FAILURE) Nov 28 23:19:56 helios64 systemd[1]: Starting Enable heartbeat & network activity led on Helios64... Nov 28 23:19:56 helios64 bash[1158]: heartbeat Nov 28 23:19:56 helios64 bash[1177]: netdev Nov 28 23:19:56 helios64 bash[1177]: tee: '/sys/class/leds/helios64:blue:net/trigger': Invalid argument Nov 28 23:19:56 helios64 systemd[1]: helios64-heartbeat-led.service: Main process exited, code=exited, status=1/FAILURE Nov 28 23:19:56 helios64 systemd[1]: helios64-heartbeat-led.service: Failed with result 'exit-code'. Nov 28 23:19:56 helios64 systemd[1]: Failed to start Enable heartbeat & network activity led on Helios64.
-
JohnnyMnemonic you can either wait 24 hours now that you have a like, or you can join the irc channel and ask to be activated.
-
http://ix.io/2FHd This is the machine in the broken state. (Requiring reboot)
-
I see! Yes, modifying settings on the windows machine has improved both. However, I am still seeing consistent lock-up / crashing of the interface. Is there anything I can grab for you for details? PS L:\> iperf3.exe -c helios64.local -R -t 700 Connecting to host helios64.local, port 5201 Reverse mode, remote host helios64.local is sending [ 4] local 192.167.0.1 port 4362 connected to 192.167.0.2 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 205 MBytes 1.72 Gbits/sec [ 4] 1.00-2.00 sec 234 MBytes 1.96 Gbits/sec [ 4] 2.00-3.00 sec 233 MBytes 1.95 Gbits/sec [ 4] 3.00-4.00 sec 234 MBytes 1.97 Gbits/sec [ 4] 4.00-5.00 sec 235 MBytes 1.97 Gbits/sec [ 4] 5.00-6.00 sec 235 MBytes 1.97 Gbits/sec [ 4] 6.00-7.00 sec 235 MBytes 1.97 Gbits/sec [ 4] 7.00-8.00 sec 241 MBytes 2.02 Gbits/sec [ 4] 8.00-9.00 sec 243 MBytes 2.04 Gbits/sec [ 4] 9.00-10.00 sec 242 MBytes 2.03 Gbits/sec [ 4] 10.00-11.00 sec 243 MBytes 2.04 Gbits/sec [ 4] 11.00-12.00 sec 238 MBytes 2.00 Gbits/sec [ 4] 12.00-13.00 sec 231 MBytes 1.94 Gbits/sec [ 4] 13.00-14.00 sec 233 MBytes 1.96 Gbits/sec [ 4] 14.00-15.00 sec 232 MBytes 1.95 Gbits/sec [ 4] 15.00-16.00 sec 236 MBytes 1.98 Gbits/sec [ 4] 16.00-17.00 sec 241 MBytes 2.02 Gbits/sec [ 4] 17.00-18.00 sec 238 MBytes 2.00 Gbits/sec [ 4] 18.00-19.00 sec 243 MBytes 2.04 Gbits/sec [ 4] 19.00-20.00 sec 231 MBytes 1.94 Gbits/sec [ 4] 20.00-21.00 sec 233 MBytes 1.95 Gbits/sec [ 4] 21.00-22.00 sec 232 MBytes 1.95 Gbits/sec [ 4] 22.00-23.00 sec 226 MBytes 1.89 Gbits/sec [ 4] 23.00-24.00 sec 238 MBytes 2.00 Gbits/sec [ 4] 24.00-25.00 sec 241 MBytes 2.02 Gbits/sec [ 4] 25.00-26.00 sec 243 MBytes 2.04 Gbits/sec [ 4] 26.00-27.00 sec 236 MBytes 1.98 Gbits/sec [ 4] 27.00-28.00 sec 229 MBytes 1.92 Gbits/sec [ 4] 28.00-29.00 sec 233 MBytes 1.96 Gbits/sec [ 4] 29.00-30.00 sec 234 MBytes 1.96 Gbits/sec [ 4] 30.00-31.00 sec 233 MBytes 1.96 Gbits/sec [ 4] 31.00-32.00 sec 236 MBytes 1.98 Gbits/sec [ 4] 32.00-33.00 sec 238 MBytes 2.00 Gbits/sec [ 4] 33.00-34.00 sec 244 MBytes 2.05 Gbits/sec [ 4] 34.00-35.01 sec 222 MBytes 1.85 Gbits/sec [ 4] 35.01-36.00 sec 0.00 Bytes 0.00 bits/sec [ 4] 36.00-37.00 sec 0.00 Bytes 0.00 bits/sec [ 4] 37.00-38.00 sec 0.00 Bytes 0.00 bits/sec [ 4] 38.00-39.01 sec 0.00 Bytes 0.00 bits/sec [ 4] 39.01-40.01 sec 0.00 Bytes 0.00 bits/sec ... Here's the Helios: Accepted connection from 192.167.0.1, port 4358 [ 5] local 192.167.0.2 port 5201 connected to 192.167.0.1 port 4362 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 207 MBytes 1.74 Gbits/sec 0 422 KBytes [ 5] 1.00-2.00 sec 234 MBytes 1.96 Gbits/sec 0 422 KBytes [ 5] 2.00-3.00 sec 232 MBytes 1.95 Gbits/sec 0 422 KBytes [ 5] 3.00-4.00 sec 235 MBytes 1.97 Gbits/sec 0 422 KBytes [ 5] 4.00-5.00 sec 235 MBytes 1.97 Gbits/sec 0 422 KBytes [ 5] 5.00-6.00 sec 234 MBytes 1.96 Gbits/sec 0 422 KBytes [ 5] 6.00-7.00 sec 235 MBytes 1.97 Gbits/sec 0 422 KBytes [ 5] 7.00-8.00 sec 240 MBytes 2.02 Gbits/sec 0 422 KBytes [ 5] 8.00-9.00 sec 243 MBytes 2.03 Gbits/sec 0 422 KBytes [ 5] 9.00-10.00 sec 243 MBytes 2.04 Gbits/sec 0 422 KBytes [ 5] 10.00-11.00 sec 243 MBytes 2.04 Gbits/sec 0 422 KBytes [ 5] 11.00-12.00 sec 238 MBytes 1.99 Gbits/sec 0 422 KBytes [ 5] 12.00-13.00 sec 233 MBytes 1.95 Gbits/sec 0 422 KBytes [ 5] 13.00-14.00 sec 232 MBytes 1.95 Gbits/sec 0 422 KBytes [ 5] 14.00-15.00 sec 233 MBytes 1.95 Gbits/sec 0 422 KBytes [ 5] 15.00-16.00 sec 236 MBytes 1.98 Gbits/sec 0 422 KBytes [ 5] 16.00-17.00 sec 240 MBytes 2.02 Gbits/sec 0 422 KBytes [ 5] 17.00-18.00 sec 239 MBytes 2.00 Gbits/sec 0 422 KBytes [ 5] 18.00-19.00 sec 243 MBytes 2.04 Gbits/sec 0 422 KBytes [ 5] 19.00-20.00 sec 231 MBytes 1.94 Gbits/sec 0 422 KBytes [ 5] 20.00-21.00 sec 233 MBytes 1.95 Gbits/sec 0 422 KBytes [ 5] 21.00-22.00 sec 232 MBytes 1.94 Gbits/sec 0 422 KBytes [ 5] 22.00-23.00 sec 226 MBytes 1.89 Gbits/sec 0 422 KBytes [ 5] 23.00-24.00 sec 239 MBytes 2.00 Gbits/sec 0 422 KBytes [ 5] 24.00-25.00 sec 240 MBytes 2.02 Gbits/sec 0 422 KBytes [ 5] 25.00-26.00 sec 243 MBytes 2.04 Gbits/sec 0 422 KBytes [ 5] 26.00-27.00 sec 237 MBytes 1.99 Gbits/sec 0 422 KBytes [ 5] 27.00-28.00 sec 230 MBytes 1.92 Gbits/sec 0 422 KBytes [ 5] 28.00-29.00 sec 233 MBytes 1.96 Gbits/sec 0 422 KBytes [ 5] 29.00-30.00 sec 234 MBytes 1.96 Gbits/sec 0 422 KBytes [ 5] 30.00-31.00 sec 233 MBytes 1.96 Gbits/sec 0 422 KBytes [ 5] 31.00-32.00 sec 235 MBytes 1.97 Gbits/sec 0 422 KBytes [ 5] 32.00-33.00 sec 238 MBytes 2.00 Gbits/sec 0 422 KBytes [ 5] 33.00-34.00 sec 244 MBytes 2.05 Gbits/sec 0 422 KBytes client_loop: send disconnect: Broken pipe ❯ ssh helios64.local ssh: connect to host helios64.local port 22: Connection refused ❯ ssh 192.168.1.236 _ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 20.11 Buster with Linux 5.9.10-rockchip64 No end-user support: work in progress System load: 2% Up time: 10:02 Memory usage: 6% of 3.71G IP: 192.168.1.236 192.167.0.2 CPU temp: 48°C Usage of /: 14% of 15G [ General system configuration (beta): armbian-config ] Last login: Thu Nov 26 08:42:37 2020 from 192.167.0.1 ❯ sudo ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.236 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::31d5:231c:fc4f:efc3 prefixlen 64 scopeid 0x20<link> inet6 2001:569:7e49:4101:7221:5284:6898:f078 prefixlen 64 scopeid 0x0<global> ether 64:62:66:d0:06:18 txqueuelen 1000 (Ethernet) RX packets 47851 bytes 6758700 (6.4 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 26542 bytes 20436445 (19.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 27 eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.167.0.2 netmask 255.255.0.0 broadcast 192.167.255.255 inet6 fe80::d8eb:9112:1d81:8ae7 prefixlen 64 scopeid 0x20<link> ether 64:62:66:d0:06:19 txqueuelen 1000 (Ethernet) RX packets 21137514 bytes 29374154279 (27.3 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 11354240 bytes 16174541188 (15.0 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 1 bytes 145 (145.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1 bytes 145 (145.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ~ ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── zageron@helios64 08:50:24 ❯ From here, if I being the adapter down and then back up it hard locks the Helios. So I generally safely sudo reboot at this point.
-
Default Offload Settings with 9000 MTU: PS L:\> iperf3.exe -c helios64.local Connecting to host helios64.local, port 5201 [ 4] local 192.167.0.1 port 59373 connected to 192.167.0.2 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 237 MBytes 1.98 Gbits/sec [ 4] 1.00-2.00 sec 255 MBytes 2.14 Gbits/sec [ 4] 2.00-3.00 sec 248 MBytes 2.08 Gbits/sec [ 4] 3.00-4.00 sec 241 MBytes 2.02 Gbits/sec [ 4] 4.00-5.00 sec 250 MBytes 2.10 Gbits/sec [ 4] 5.00-6.00 sec 244 MBytes 2.05 Gbits/sec [ 4] 6.00-7.00 sec 241 MBytes 2.02 Gbits/sec [ 4] 7.00-8.00 sec 254 MBytes 2.13 Gbits/sec [ 4] 8.00-9.00 sec 240 MBytes 2.01 Gbits/sec [ 4] 9.00-10.00 sec 221 MBytes 1.85 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 2.37 GBytes 2.04 Gbits/sec sender [ 4] 0.00-10.00 sec 2.37 GBytes 2.04 Gbits/sec receiver iperf Done. PS L:\> iperf3.exe -c helios64.local -R Connecting to host helios64.local, port 5201 Reverse mode, remote host helios64.local is sending [ 4] local 192.167.0.1 port 59414 connected to 192.167.0.2 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.01 sec 82.8 MBytes 687 Mbits/sec [ 4] 1.01-2.01 sec 0.00 Bytes 0.00 bits/sec [ 4] 2.01-3.01 sec 0.00 Bytes 0.00 bits/sec [ 4] 3.01-4.01 sec 0.00 Bytes 0.00 bits/sec [ 4] 4.01-5.01 sec 0.00 Bytes 0.00 bits/sec [ 4] 5.01-6.01 sec 0.00 Bytes 0.00 bits/sec [ 4] 6.01-7.02 sec 0.00 Bytes 0.00 bits/sec [ 4] 7.02-8.01 sec 0.00 Bytes 0.00 bits/sec [ 4] 8.01-9.01 sec 0.00 Bytes 0.00 bits/sec iperf3: error - unable to receive control message: Connection reset by peer Crashed the connection. Unable to use connection until rebooting Helios64 unit. TX Offloading disabled 1500 MTU: PS L:\> iperf3.exe -c helios64.local Connecting to host helios64.local, port 5201 [ 4] local 192.167.0.1 port 3691 connected to 192.167.0.2 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 156 MBytes 1.31 Gbits/sec [ 4] 1.00-2.00 sec 163 MBytes 1.37 Gbits/sec [ 4] 2.00-3.00 sec 124 MBytes 1.04 Gbits/sec [ 4] 3.00-4.00 sec 99.9 MBytes 839 Mbits/sec [ 4] 4.00-5.00 sec 157 MBytes 1.31 Gbits/sec [ 4] 5.00-6.01 sec 160 MBytes 1.32 Gbits/sec [ 4] 6.01-7.00 sec 98.4 MBytes 836 Mbits/sec [ 4] 7.00-8.00 sec 112 MBytes 941 Mbits/sec [ 4] 8.00-9.00 sec 176 MBytes 1.48 Gbits/sec [ 4] 9.00-10.00 sec 148 MBytes 1.25 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 1.36 GBytes 1.17 Gbits/sec sender [ 4] 0.00-10.00 sec 1.36 GBytes 1.17 Gbits/sec receiver iperf Done. PS L:\> iperf3.exe -c helios64.local -R Connecting to host helios64.local, port 5201 Reverse mode, remote host helios64.local is sending [ 4] local 192.167.0.1 port 3720 connected to 192.167.0.2 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 211 MBytes 1.77 Gbits/sec [ 4] 1.00-2.00 sec 248 MBytes 2.08 Gbits/sec [ 4] 2.00-3.00 sec 237 MBytes 1.98 Gbits/sec [ 4] 3.00-4.00 sec 211 MBytes 1.77 Gbits/sec [ 4] 4.00-5.00 sec 186 MBytes 1.56 Gbits/sec [ 4] 5.00-6.00 sec 205 MBytes 1.72 Gbits/sec [ 4] 6.00-7.00 sec 218 MBytes 1.83 Gbits/sec [ 4] 7.00-8.00 sec 192 MBytes 1.61 Gbits/sec [ 4] 8.00-9.00 sec 188 MBytes 1.58 Gbits/sec [ 4] 9.00-10.00 sec 220 MBytes 1.85 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 2.07 GBytes 1.78 Gbits/sec 2 sender [ 4] 0.00-10.00 sec 2.07 GBytes 1.77 Gbits/sec receiver Okay I understand a little more now. Receiving on helios is very slow, sending is slightly faster. Note that rx is on. ❯ sudo ethtool -k eth1 | grep rx-checksum rx-checksumming: on (same with windows, IP Offloading is set to rx only)
-
Have you tried checking your router's dhcp for a lease on the helios64? If you have the ethernet plugged in when starting it up, and it makes it through sdcard boot, regardless of your serial console it should get a lease. (Then you can SSH in with the same credentials.) I also had no console output when I first tried to set it up, and ended up using the router to discover what the IP was. Make sure you are using the correct COM address. I had to install the driver, and I was on COM4.