white_gecko

Thank you for the porting and the instructions. I'm testing it on an Olimex A20-OLinuXIno-LIME2 (https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2/open-source-hardware) with armibian (jessie). The installation worked. Just a remark, on running `apt-get -y install cgroupfs-mount` it removed the `console-common` package. Is this intended? The `check-config.sh` script has following output: # ./check-config.sh info: reading kernel config from /proc/config.gz ... Generally Necessary: - cgroup hierarchy: properly mounted [/sys/fs/cgroup] - CONFIG_NAMESPACES: enabled - CONFIG_NET_NS: enabled - CONFIG_PID_NS: enabled - CONFIG_IPC_NS: enabled - CONFIG_UTS_NS: enabled - CONFIG_DEVPTS_MULTIPLE_INSTANCES: enabled - CONFIG_CGROUPS: enabled - CONFIG_CGROUP_CPUACCT: enabled - CONFIG_CGROUP_DEVICE: enabled - CONFIG_CGROUP_FREEZER: enabled - CONFIG_CGROUP_SCHED: enabled - CONFIG_CPUSETS: enabled - CONFIG_MEMCG: enabled - CONFIG_KEYS: enabled - CONFIG_MACVLAN: enabled (as module) - CONFIG_VETH: enabled (as module) - CONFIG_BRIDGE: enabled - CONFIG_BRIDGE_NETFILTER: enabled (as module) - CONFIG_NF_NAT_IPV4: enabled (as module) - CONFIG_IP_NF_FILTER: enabled (as module) - CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module) - CONFIG_NF_NAT: enabled (as module) - CONFIG_NF_NAT_NEEDED: enabled - CONFIG_POSIX_MQUEUE: enabled Optional Features: - CONFIG_USER_NS: enabled - CONFIG_SECCOMP: missing - CONFIG_CGROUP_PIDS: missing - CONFIG_MEMCG_KMEM: enabled - CONFIG_MEMCG_SWAP: enabled - CONFIG_MEMCG_SWAP_ENABLED: enabled - CONFIG_BLK_CGROUP: enabled - CONFIG_IOSCHED_CFQ: enabled - CONFIG_BLK_DEV_THROTTLING: enabled - CONFIG_CGROUP_PERF: enabled - CONFIG_CGROUP_HUGETLB: missing - CONFIG_NET_CLS_CGROUP: missing - CONFIG_CGROUP_NET_PRIO: enabled - CONFIG_CFS_BANDWIDTH: enabled - CONFIG_FAIR_GROUP_SCHED: enabled - CONFIG_RT_GROUP_SCHED: enabled - CONFIG_EXT3_FS: missing - CONFIG_EXT3_FS_XATTR: missing - CONFIG_EXT3_FS_POSIX_ACL: missing - CONFIG_EXT3_FS_SECURITY: missing (enable these ext3 configs if you are using ext3 as backing filesystem) - CONFIG_EXT4_FS: enabled - CONFIG_EXT4_FS_POSIX_ACL: enabled - CONFIG_EXT4_FS_SECURITY: enabled - Storage Drivers: - "aufs": - CONFIG_AUFS_FS: missing - "btrfs": - CONFIG_BTRFS_FS: enabled - "devicemapper": - CONFIG_BLK_DEV_DM: enabled (as module) - CONFIG_DM_THIN_PROVISIONING: enabled (as module) - "overlay": - CONFIG_OVERLAY_FS: enabled (as module) - "zfs": - /dev/zfs: missing - zfs command: missing - zpool command: missing But the daemon doesn't start: # service docker status [FAIL] Docker is not running ... failed! # service docker start [ ok ] Starting Docker: docker. # service docker status [FAIL] Docker is not running ... failed! # docker version Client: Version: 1.10.3 API version: 1.22 Go version: go1.4.3 Git commit: 20f81dd Built: Thu Mar 10 22:23:48 2016 OS/Arch: linux/arm Cannot connect to the Docker daemon. Is the docker daemon running on this host? When I start the daemon manually it runs: # docker daemon WARN[0001] devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section. WARN[0002] devmapper: XFS is not supported in your system. Either the kernel doesnt support it or mkfs.xfs is not in your PATH. Defaulting to ext4 filesystem INFO[0002] devmapper: Creating filesystem ext4 on device docker-179:1-387353-base INFO[0224] devmapper: Successfully created filesystem ext4 on device docker-179:1-387353-base INFO[0224] Graph migration to content-addressability took 0.00 seconds INFO[0224] Firewalld running: false INFO[0224] Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address INFO[0225] Loading containers: start. INFO[0225] Loading containers: done. INFO[0225] Daemon has completed initialization INFO[0225] Docker daemon commit=20f81dd execdriver=native-0.2 graphdriver=devicemapper version=1.10.3 INFO[0225] API listen on /var/run/docker.sock … [another terminal] # docker version Client: Version: 1.10.3 API version: 1.22 Go version: go1.4.3 Git commit: 20f81dd Built: Thu Mar 10 22:23:48 2016 OS/Arch: linux/arm Server: Version: 1.10.3 API version: 1.22 Go version: go1.4.3 Git commit: 20f81dd Built: Thu Mar 10 22:23:48 2016 OS/Arch: linux/arm So generally, it works, but the provided init script doesn't work, even outcommenting those lines as @wildcat_paris wrote didn't help: # see also init_is_upstart in /lib/lsb/init-functions (which isn't available in Ubuntu 12.04, or we'd use it) #if [ -x /sbin/initctl ] && /sbin/initctl version 2>/dev/null | grep -q upstart; then # log_failure_msg "$DOCKER_DESC is managed via upstart, try using service $BASE $1" # exit 1 #fi

Still the sound seams to be faster than the video. Is there any way of fixing this? [edit] "--framedrop=yes" is one possibility to keep audio and video in sync, but the of course the video isn't smooth anymore

Thank you for this info. Actually there is no ffmped installed in the default image. But your answer brought me to do more experimenting with the codecs in mpv. Adding the argument "--hwdec=vdpau" did the tric so far. (I thought, it would be selected in some automagic way ;-) ) Actually I have all the permissions, because be default you are root in armbian desktop version.

I'm trying to check if the CedarX is working for me (I'm using the Armbian_4.5_Lime2_Ubuntu_trusty_3.4.109_desktop version). I've added the boot parameters and rebuild the boot.scr, rebooted the board, then I've exported the enironement variables in the terminal: export VDPAU_DRIVER=sunxi; export DISPLAY=:0.0; export VDPAU_OSD=1; export VDPAU_DEINT=1; before I execute "mpv --fs big_buck_bunny_1080p_h264.mov", which should be supported as far as I'm informed. But still the video is not encoded propperly and a bit slow. (My board is an Olimex OLinuXino A20 Lime2) Is it correct to use "mpv"? Am I missing further steps?