TCB13

Great, where did you get 4.20 from? Is there a link for it?

@littlema can you try ethtool -K eth0 rx off tx off with the built in network adaptor and see if it helps? Check my answer here to survive reboots https://unix.stackexchange.com/a/495378/23085 .

@Igor just found out the source of my problems. It's the on-board network. I just added a cheap USB 3 to Ethernet adaptor and I'm able to download files without issues at all. Maybe there is some strange bug with the driver for the built in network? However I don't get why it only manifests itself on HTTPS, other protocols such as SSH work just fine. Thank you all. ---------------- Update: I manage to find out that this issues are caused by TCP offloading. Disabling it with `ethtool -K eth0 rx off tx off` fixed the issue, no more errors on downloads.

I did have the same issue with downloads using wget on the device itself. It was fixed by an update 2 days ago (cleaned log bellow) I've no idea about which package update fixed the issue locally. libsystemd0:arm64 (232-25+deb9u7) over (232-25+deb9u6) libnss-myhostname:arm64 (232-25+deb9u7) over (232-25+deb9u6) libpam-systemd:arm64 (232-25+deb9u7) over (232-25+deb9u6) systemd (232-25+deb9u7) over (232-25+deb9u6) udev (232-25+deb9u7) over (232-25+deb9u6) libudev1:arm64 (232-25+deb9u7) over (232-25+deb9u6) systemd-sysv (232-25+deb9u7) over (232-25+deb9u6) php7.3-zip (7.3.1-1+0~20190113101756.25+stretch~1.gbp15aaa9) over (7.3.0-2+0~20181217092659.24+stretch~1.gbp54e52f) php7.3-intl (7.3.1-1+0~20190113101756.25+stretch~1.gbp15aaa9) over (7.3.0-2+0~20181217092659.24+stretch~1.gbp54e52f) php7.3-readline (7.3.1-1+0~20190113101756.25+stretch~1.gbp15aaa9) over (7.3.0-2+0~20181217092659.24+stretch~1.gbp54e52f) php7.3-mysql (7.3.1-1+0~20190113101756.25+stretch~1.gbp15aaa9) over (7.3.0-2+0~20181217092659.24+stretch~1.gbp54e52f) php7.3-xml (7.3.1-1+0~20190113101756.25+stretch~1.gbp15aaa9) over (7.3.0-2+0~20181217092659.24+stretch~1.gbp54e52f) php7.3-opcache (7.3.1-1+0~20190113101756.25+stretch~1.gbp15aaa9) over (7.3.0-2+0~20181217092659.24+stretch~1.gbp54e52f) php7.3-curl (7.3.1-1+0~20190113101756.25+stretch~1.gbp15aaa9) over (7.3.0-2+0~20181217092659.24+stretch~1.gbp54e52f) php7.3-imap (7.3.1-1+0~20190113101756.25+stretch~1.gbp15aaa9) over (7.3.0-2+0~20181217092659.24+stretch~1.gbp54e52f) php7.3-json (7.3.1-1+0~20190113101756.25+stretch~1.gbp15aaa9) over (7.3.0-2+0~20181217092659.24+stretch~1.gbp54e52f) php7.3-mbstring (7.3.1-1+0~20190113101756.25+stretch~1.gbp15aaa9) over (7.3.0-2+0~20181217092659.24+stretch~1.gbp54e52f) php7.3-cli (7.3.1-1+0~20190113101756.25+stretch~1.gbp15aaa9) over (7.3.0-2+0~20181217092659.24+stretch~1.gbp54e52f) libapache2-mod-php7.3 (7.3.1-1+0~20190113101756.25+stretch~1.gbp15aaa9) over (7.3.0-2+0~20181217092659.24+stretch~1.gbp54e52f)] php7.3-common (7.3.1-1+0~20190113101756.25+stretch~1.gbp15aaa9) over (7.3.0-2+0~20181217092659.24+stretch~1.gbp54e52f) linux-dtb-rk3399 (5.70) over (5.65) update-initramfs: Deleting /boot/initrd.img-4.4.162-rk3399 Removing obsolete file uInitrd-4.4.162-rk3399 linux-image-rk3399 (5.70) over (5.65) linux-stretch-root-nanopim4 (5.70) over (5.65) linux-u-boot-nanopim4-default (5.70) over (5.65) php7.3 (7.3.1-1+0~20190113101756.25+stretch~1.gbp15aaa9) over (7.3.0-2+0~20181217092659.24+stretch~1.gbp54e52f)

Thank you for the answer, however if you look closely at my apache config I was trying to get the file from the eMMC card (because I was afraid of those issues you are taking about). I only had the SSL certifications on external media. Also tried with the certificates on the eMMC, same issue. I don't think its an USB3 issue because if I get a 10GB file stored on a USB disk via SCP it works just fine. Another strange thing: if I wget the file on the device itself it works fine, it doesn't stop, so maybe a network issue and the OpenSSL errors aren't that important?

Hello, can you confirm that my Apache/OpenSSL I/O issue might be something you guy already know about? https://forum.armbian.com/topic/7511-nanopi-m4/?do=findComment&comment=69785

Meanwhile the iotop command is also broken: iotop Traceback (most recent call last): File "/usr/sbin/iotop", line 17, in main() File "/usr/lib/python3/dist-packages/iotop/ui.py", line 620, in main main_loop() File "/usr/lib/python3/dist-packages/iotop/ui.py", line 610, in main_loop = lambda: run_iotop(options) File "/usr/lib/python3/dist-packages/iotop/ui.py", line 508, in run_iotop return curses.wrapper(run_iotop_window, options) File "/usr/lib/python3.5/curses/init.py", line 94, in wrapper return func(stdscr, *args, **kwds) File "/usr/lib/python3/dist-packages/iotop/ui.py", line 501, in run_iotop_window ui.run() File "/usr/lib/python3/dist-packages/iotop/ui.py", line 155, in run self.process_list.duration) File "/usr/lib/python3/dist-packages/iotop/ui.py", line 434, in refresh_display lines = self.get_data() File "/usr/lib/python3/dist-packages/iotop/ui.py", line 415, in get_data return list(map(format, processes)) File "/usr/lib/python3/dist-packages/iotop/ui.py", line 388, in format cmdline = p.get_cmdline() File "/usr/lib/python3/dist-packages/iotop/data.py", line 292, in get_cmdline proc_status = parse_proc_pid_status(self.pid) File "/usr/lib/python3/dist-packages/iotop/data.py", line 196, in parse_proc_pid_status key, value = line.split(':\t', 1) ValueError: not enough values to unpack (expected 2, got 1)

So, did anyone notice issues with Apache + SSL? I'm using Armbian Stretch from here https://dl.armbian.com/nanopim4/Debian_stretch_default.7z and apparently when I enable SSL in Apache, large downloads just hang after a while. I can't reproduce this issue with plain HTTP. Example on `wget` (same behaviour on a browser): wget https://xyz---/test.bin --2019-01-13 18:22:22-- https://xyz---/test.bin Resolving xyz--- (xyz---)... 85.241.xxx.xxx Connecting to xyz--- (xyz---)|85.241.xxx.xxx|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 1073741824 (1,0G) [application/octet-stream] Saving to: 'test.bin.2' test.bin.2 39%[==================> ] 403,66M 11,6MB/s eta 54s It was downloading fine until it reached 403,66M, after this point nothing else happened. On the server side I get this: ssl_engine_io.c(2135): [client 85.243.xxx.xxx:59904] OpenSSL: write 16413/16413 bytes to BIO#5588cd8c50 [mem: 5588a87c23] (BIO dump follows) core_filters.c(525): [client 85.243.xxx.xxx:59904] core_output_filter: flushing because of THRESHOLD_MAX_BUFFER core_filters.c(547): (70007)The timeout specified has expired: [client 85.243.xxx.xxx:59904] core_output_filter: writing data to the network ssl_engine_io.c(2144): [client 85.243.xxx.xxx:59904] OpenSSL: I/O error, 16413 bytes expected to write on BIO#5588cd8c50 [mem: 5588a87c23] (70007)The timeout specified has expired: [client 85.243.xxx.xxx:59904] AH01993: SSL output filter write failed. ssl_engine_io.c(2135): [client 95.239.xxx.xxx:9937] OpenSSL: write 45/45 bytes to BIO#55bd9e23e0 [mem: 55bd9ec213] (BIO dump follows) ssl_engine_io.c(2144): [client 95.239.xxx.xxx:9937] OpenSSL: I/O error, 5 bytes expected to read on BIO#55bd9e9d80 [mem: 55bd9ec213] Here is the configuration of the VHosts serving this requests: <VirtualHost *:443> ServerName xyz--- ServerAdmin tcb13--- DocumentRoot /test ErrorLog /test/error.log CustomLog /test/access.log combined SSLEngine on SSLCertificateFile /mnt/SU1/letsencrypt/config/live/xyz---/fullchain.pem SSLCertificateKeyFile /mnt/SU1/letsencrypt/config/live/xyz---/privkey.pem Header always set Strict-Transport-Security "max-age=15768000" LogLevel trace6 </VirtualHost> I'm sure this isn't a network related problem because: Only happens with SSL enabled, on non-ssl vhosts I can download without issues; Other protocols (FTP and SCP) work just fine to download the same test file; No issues while testing the network with iperf3. Some system info: lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.6 (stretch) Release: 9.6 Codename: stretch uname -a Linux testxyz 4.4.162-rk3399 #41 SMP Fri Oct 26 14:03:47 CEST 2018 aarch64 GNU/Linux apache2ctl -V | grep -i "Server version" Server version: Apache/2.4.25 (Debian) root@testxyz:~# dpkg -l |grep apache2 ii apache2 2.4.25-3+deb9u6 arm64 Apache HTTP Server ii apache2-bin 2.4.25-3+deb9u6 arm64 Apache HTTP Server (modules and other binary files) ii apache2-data 2.4.25-3+deb9u6 all Apache HTTP Server (common files) ii apache2-utils 2.4.25-3+deb9u6 arm64 Apache HTTP Server (utility programs for web servers) ii libapache2-mod-php7.3 7.3.0-2+0~20181217092659.24+stretch~1.gbp54e52f arm64 server-side, HTML-embedded scripting language (Apache 2 module) Thank you all.

Hello, I was wondering if it is possible to disable both LEDs on this board or, at least, the green (stat) one. Also I was trying to remove wifi completely and I can do: iwconfig wlan0 txpower off ifconfig wlan0 down systemctl disable wpa_supplicant But not sure if it's possible to remove the driver from the OS and what other unnecessary software I can remove. Thank you in advance.

By using lsmod I found out that usb-storage in this kernel is not loaded as a module, it is builtin. Due to this we need to add the usb-storage quirks into the boot options. I went into /boot/armbianEnv.txt and at the end of "usbstoragequirks=" I added my device by appending ",174c:55aa:u". Then I re-run update-initramfs -u and rebooted. After this, the device not shows as using usb-storage instead of uas: lsusb -t /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M As you can see here, uas is not properly blacklisted for the device: dmesg | grep "usb 5-1" [ 2.308569] usb 5-1: new high-speed USB device number 2 using ehci-platform [ 2.467087] usb 5-1: New USB device found, idVendor=174c, idProduct=55aa [ 2.467106] usb 5-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 2.467117] usb 5-1: Product: ASM1153E [ 2.467127] usb 5-1: Manufacturer: Inateck [ 2.467137] usb 5-1: SerialNumber: 12345678910E [ 2.468297] usb 5-1: UAS is blacklisted for this device, using usb-storage instead So my problem is fixed.

So If I blacklist UAS with "blacklist uas" into /etc/modprobe.d/blacklist-uas.conf I get: lsusb -t /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=, 480M Looking at Class=Mass Storage, Driver=, 480M => seems like the systems doesn't load any other way to deal with the drive. If I just try to disable for specific USB device, like the post said it still loads as uas: echo options usb-storage quirks=174c:55aa:u | tee /etc/modprobe.d/blacklist-uas.conf update-initramfs -u reboot (...) dmesg | grep sda [ 2.488105] sd 0:0:0:0: [sda] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB) [ 2.488584] sd 0:0:0:0: [sda] Write Protect is off [ 2.488592] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 [ 2.489335] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 2.539288] sda: sda1 [ 2.543875] sd 0:0:0:0: [sda] Attached SCSI disk [ 6.898109] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: errors=remount-ro,data=ordered lsusb | grep ASMedia Bus 005 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge lsusb -t /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 480M Any tips here? Thank you.

Looks like this is some bug related to the UAS module of the kernel. The answer here by Cinos Modnar seems to be a nice workaround: https://unix.stackexchange.com/questions/239782/connection-problem-with-usb3-external-storage-on-linux-uas-driver-problem however looks like the device is not blacklisted. I also tried to blacklist uas, but after this the disk isn't mounted.

Hello, I'm running rsync to backup a VPS to an USB hard drive on the neo2 and sometimes rsync just stops with "read error from input device (I/O error)". I believe this issue happens when rsync is causing high load in the USB disk, writing or removing a large number of files or trying to write a big file. Notes: The hard drive is on a self powered enclosure - so power failure is not really an option here I also have Apache and mariadb storing data on the USB disk and I never had this kind of I/O errors with it OS: Debian GNU/Linux 9.4 (stretch) Drive is ext4 Whenever rysnc stops I get this under /var/log/messages: sd 0:0:0:0: [sda] tag#1 data cmplt err -32 uas-tag 2 inflight: sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 38 80 0a 68 00 00 a0 00 sd 0:0:0:0: [sda] tag#0 data cmplt err -32 uas-tag 1 inflight: CMD sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 57 50 28 78 00 03 00 00 sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 38 80 0a 68 00 00 a0 00 sd 0:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD sd 0:0:0:0: [sda] tag#2 CDB: opcode=0x2a 2a 00 19 47 7f 20 00 00 90 00 sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 57 50 28 78 00 03 00 00 scsi host0: uas_eh_device_reset_handler start usb 5-1: reset high-speed USB device number 2 using ehci-platform scsi host0: uas_eh_device_reset_handler success sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 sd 0:0:0:0: [sda] tag#0 Sense Key : 0x2 [current] sd 0:0:0:0: [sda] tag#0 ASC=0x3a ASCQ=0x0 sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 57 50 28 78 00 03 00 00 sd 0:0:0:0: [sda] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 sd 0:0:0:0: [sda] tag#1 Sense Key : 0x2 [current] sd 0:0:0:0: [sda] tag#1 ASC=0x3a ASCQ=0x0 sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x2a 2a 00 19 47 7f 20 00 00 90 00 EXT4-fs warning (device sda1): ext4_end_bio:323: I/O error 10 writing to inode 13001563 (offset 0 size 73728 starting block 53014518) My fstab: LABEL=USBHD /mnt/storage ext4 defaults,nofail 0 0 Why does it happen? Thank you. PS: can someone move this to the Technical support section? Posted on the wrong place!

@Igor thanks for the feedback and your hard work. Indeed it is working fine now! Although this is an experimental build I've been running it flawless for a few months now. Thank you all for your great work.

Thanks for the feedback!

Hello, I've been running the Ubuntu experimental version in my NanoPi NEO2 for months now without any issues, it has been running just fine. However today I tried to run apt-get update and got: N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'http://beta.armbian.com xenial InRelease' doesn't support architecture 'arm64' N: Skipping acquire of configured file 'utils/binary-arm64/Packages' as repository 'http://beta.armbian.com xenial InRelease' doesn't support architecture 'arm64' N: Skipping acquire of configured file 'xenial-desktop/binary-arm64/Packages' as repository 'http://beta.armbian.com xenial InRelease' doesn't support architecture 'arm64' This wasn't showing up before, does this actually means I don't get updates anymore? Why? What's changed / how should I fix this? Board: NanoPi NEO2 Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial Thank you.

Hello, first of all many thanks to all the community that keeps this project alive. I recently bought a NanoPi NEO2 board and of course decided to drop the OS provided by Friendlyarm and give a try to Armbian's Ubuntu build for this board. Everything seems to work just fine, however I'm unable to get a reading on the CPU Frequency. I tried multiple tools and commands but somehow all end up with something like "cpuinfo_cur_freq: No such file or directory. For instance, here is the output of armbianmonitor: armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU/usr/bin/armbianmonitor: line 264: /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq: No such file or directory Any tips on how to fix this / get the reading? Thank you!