oxymoron

I managed to switch and try kernel 4.14.15 (via armbian-config > nightlies), 4.15.0-rc9 (via armbian config > switch kernel, after having switched to nightlies), and if I remember correctly also 4.14.0 (installed via apt-get). The process was a bit brittle, I lost USB HDD support in the one or other installation approach (e.g. I think nand-sata-install and kernel switch before apt-get upgrade and the system would not boot from USB anymore, not sure whether this makes sense), anyway it worked out at the end. Indeed I'm using USB receivers - DVBSky 960. As far as I can tell, 4.14.x did not make any difference to 4.13, heavy artefacts quite regularly. But 4.15 looks really good, only a few artefacts very infrequently, which is not perfect but definitely good enough. Thanks a lot for your effort!

This is really weird, after some days it starting stuttering again. And the stuttering stays persistently, for days now. I have no clue why, I haven't been doing anything on that machine - no package upgrades have been performed during that time, the workload on the machine is the same (i.e. same containers running on it), the only thing that happened was that the docker images have been rebuilt, but that can't be related really. Is there anything else I could try?

perfect, thanks a lot Igor!

I changed to performance, stuttering is gone. Which is a real relief, as I would be able to migrate to armbian now. Is this a reasonable long-term solution, not sure about the effects of 'performance'? Btw. I just checked, bananian uses ondemand governor. Presumably not relevant anymore, but this here is on ifconfig root@tv:~# ifconfig ---snip--- eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.28.97 netmask 255.255.255.0 broadcast 192.168.28.255 inet6 fe80::4d:6ff:fe40:90e1 prefixlen 64 scopeid 0x20<link> ether 02:4d:06:40:90:e1 txqueuelen 1000 (Ethernet) RX packets 648141 bytes 43022905 (41.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1217295 bytes 1679524870 (1.5 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 50 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 11040 bytes 21360182 (20.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 11040 bytes 21360182 (20.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

I've installed armbian now and unfortunately TV streaming playback on remote devices stutters. That applies for SD as well as for HDTV, which stutters more. root@bananapi:~# uname -a Linux bananapi 4.13.16-sunxi #20 SMP Fri Nov 24 19:50:07 CET 2017 armv7l GNU/Linux As far as the logging on the bananapi tv server shows (attached/below), there seems not much going on on the CPU side, but obviously on network i/o (varying traffic is owed to switching between SDTV and HTDV).

I'm using the Bananapi as a TV backend server to watch satellite tv. In my case, I'm viewing the tv stream from other devices with Kodi via the VNSI plugin. I'll install the latest armbian now.

Thanks for your reply. This is my current bananian kernel root@tv ~ # uname -a Linux tv.lan 4.4.66-bananian #2 SMP Sat May 6 19:26:50 UTC 2017 armv7l GNU/Linux Please let me know what other information might be helpful. Afterwards I'll setup the server on current armbian to check whether stuttering still occurs. I have to admit that the last time I tried it was maybe half a year ago. root@tv ~ # lsmod Module Size Used by xt_nat 1567 15 xt_tcpudp 2077 29 veth 4218 0 ipt_MASQUERADE 1019 10 nf_nat_masquerade_ipv4 1817 1 ipt_MASQUERADE nf_conntrack_netlink 23591 0 nfnetlink 4905 2 nf_conntrack_netlink iptable_nat 1469 3 nf_conntrack_ipv4 6793 4 nf_defrag_ipv4 1300 1 nf_conntrack_ipv4 nf_nat_ipv4 4480 1 iptable_nat xt_addrtype 2619 2 iptable_filter 1281 1 ip_tables 11125 2 iptable_filter,iptable_nat xt_conntrack 2911 3 x_tables 11316 7 ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,xt_nat,iptable_filter,xt_addrtype nf_nat 11031 3 nf_nat_ipv4,xt_nat,nf_nat_masquerade_ipv4 nf_conntrack 70409 6 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_netlink,nf_conntrack_ipv4 br_netfilter 12383 0 overlay 27626 6 ts2020 5544 2 sun4i_codec 8300 3 snd_soc_core 116192 1 sun4i_codec dvb_usb_dvbsky 7562 14 ftdi_sio 30425 1 snd_pcm_dmaengine 3007 1 snd_soc_core snd_pcm 70170 2 snd_soc_core,snd_pcm_dmaengine m88ds3103 10884 3 dvb_usb_dvbsky snd_timer 18216 1 snd_pcm usbserial 19325 3 ftdi_sio snd 42273 3 snd_soc_core,snd_timer,snd_pcm soundcore 858 1 snd evdev 11204 0 sun4i_ts 3798 0 nvmem_sunxi_sid 2359 0 nvmem_core 7651 1 nvmem_sunxi_sid cpufreq_dt 4010 0 sun4i_ss 15042 0 thermal_sys 51713 2 cpufreq_dt,sun4i_ts uio_pdrv_genirq 2972 0 uio 6976 1 uio_pdrv_genirq root@tv ~ # docker -v Docker version 17.09.1-ce, build 19e2cf6

I'm running a dockerized VDR server on the BPi, still on bananian. Every time I installed armbian, I had to discover that video playback on remote devices started to stutter. Without knowing about the details, my guess is that this is owed to the fact that the mainline kernel build does not feature hw video decoding. (Though I'm not sure whether bananian had it actually.) Unfortunately I cannot use the legacy kernel build, as docker is not supported on that platform. Is there any chance to kind of enable hw video acceleration on the mainline build? I saw some posts here and there in the forum on that topic, but none seemed really having solved it definite or reliably. greets

@tkaiser thank you for bringing light this, that's really interesting insights into USB. I was always wondering what the point of USB would be, if it was not compatible to any OS. I'll check with the vendor support - at least the website claims "USB 3.1 up to 10 Gbit/s - Backwards compatible to USB 3.0/2.0/1.1"

Hi, when I connect my external HDD - an Icy Box IB-RD2253-U31 (http://www.raidsonic.de/products/external_cases/soho_raid/index_en.php?we_objectID=3239) - to my Bananapi M1, running ARMBIAN 5.31 (stable Debian GNU/Linux 8 (jessie) 4.11.6-sunxi) the hard disk is not found. This is regardless of the HDD setup chosen, at least I tried with the two disks inside configured as JBOD as well as RAID1. After connecting the USB HDD, dmesg doesnt show any output, lsblk doesnt show it. Is there anything I can do about it to get it working, is it a firmware issue?