Rock pi s debian ftdi driver missing

zwei · October 18, 2019, 9:14pm

Thank you a lot.

sudoom · November 19, 2019, 12:08pm

Hello, I use this image and have some trouble with shutdown.
1)install images on 6 pis
2)go to shutdown each pis, each pis have different command
{
sudo shutdown now
sudo shutdown -h now
sudo shutdown -P now
sudo poweroff
sudo halt -p
sudo init 0
}
everything was okay and work/
3) sudo apt update && sudo apt upgrade -y (in each pis)
4) sudo reboot (all pis)
5) do step 2 and pis dont work, ()

piter75 · November 19, 2019, 4:50pm

I have just tried the same procedure on one of my Rock Pi S with shutdown -h now and it: updated, upgraded, rebooted and is still successfully shutting down after the process.

One thing, although it should not matter at all IMHO, is that I used the latest image from this topic: Rock Pi S Armbian Buster minimal (pre-release). It is a bit newer than this one.

sudoom · November 19, 2019, 5:06pm

Thanks, for answer.
I install that image, and in newer version I havent this problem, but I have problem with docker.

piter75 · November 19, 2019, 5:19pm

Oh. I never optimised it for docker

sudoom · November 19, 2019, 5:27pm

but previous version haven’t problem with docker -_-
and I in small confusion, in old version have problem with shutdown, in newer problem with docker
in this point, I think better way is resolve problem with docker/

piter75 · November 19, 2019, 6:01pm

That’s interesting
What problem with docker is it exactly? Can you attach error log?

sudoom · November 19, 2019, 6:19pm

yes, sure/

sudo systemctl status docker.service

docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2019-11-19 21:02:36 +03; 3min 5s ago
Docs: “link”
Process: 1094 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 1094 (code=exited, status=1/FAILURE)

Nov 19 21:02:36 user11 systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
Nov 19 21:02:36 user11 systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Nov 19 21:02:36 user11 systemd[1]: Stopped Docker Application Container Engine.
Nov 19 21:02:36 user11 systemd[1]: docker.service: Start request repeated too quickly.
Nov 19 21:02:36 user11 systemd[1]: docker.service: Failed with result ‘exit-code’.
Nov 19 21:02:36 user11 systemd[1]: Failed to start Docker Application Container Engine.
Nov 19 21:03:03 user11 systemd[1]: docker.service: Start request repeated too quickly.
Nov 19 21:03:03 user11 systemd[1]: docker.service: Failed with result ‘exit-code’.
Nov 19 21:03:03 user11 systemd[1]: Failed to start Docker Application Container Engine.

docker version

Client: Docker Engine - Community
Version: 19.03.5
API version: 1.40
Go version: go1.12.12
Git commit: 633a0ea
Built: Wed Nov 13 07:28:11 2019
OS/Arch: linux/arm64
Experimental: false
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

sudo apt install -f docker-ce

Reading package lists… Done
Building dependency tree
Reading state information… Done
docker-ce is already the newest version (5:19.03.5~3-0~debian-buster).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up docker-ce (5:19.03.5~3-0~debian-buster) …
Job for docker.service failed because the control process exited with error code.
See “systemctl status docker.service” and “journalctl -xe” for details.
invoke-rc.d: initscript docker, action “start” failed.

docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2019-11-19 21:14:38 +03; 47ms ago
Docs: “link”
Process: 1762 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 1762 (code=exited, status=1/FAILURE)

Nov 19 21:14:38 user11 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Nov 19 21:14:38 user11 systemd[1]: docker.service: Failed with result ‘exit-code’.
Nov 19 21:14:38 user11 systemd[1]: Failed to start Docker Application Container Engine.
dpkg: error processing package docker-ce (–configure):
installed docker-ce package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)

journalctl -xe

A stop job for unit docker.socket has finished.
–
– The job identifier is 1077 and the job result is done.
Nov 19 21:14:48 user11 systemd[1]: Stopping Docker Socket for the API.
– Subject: A stop job for unit docker.socket has begun execution
– Defined-By: systemd
– Support: link
–
– A stop job for unit docker.socket has begun execution.
–
– The job identifier is 1077.
Nov 19 21:14:48 user11 systemd[1]: Starting Docker Socket for the API.
– Subject: A start job for unit docker.socket has begun execution
– Defined-By: systemd
– Support: link
–
– A start job for unit docker.socket has begun execution.
–
– The job identifier is 1077.
Nov 19 21:14:48 user11 systemd[1]: Listening on Docker Socket for the API.
– Subject: A start job for unit docker.socket has finished successfully
– Defined-By: systemd
– Support: link
–
– A start job for unit docker.socket has finished successfully.
–
– The job identifier is 1077.
Nov 19 21:14:48 user11 systemd[1]: docker.service: Start request repeated too quickly.
Nov 19 21:14:48 user11 systemd[1]: docker.service: Failed with result ‘exit-code’.
– Subject: Unit failed
– Defined-By: systemd
– Support: link
–
– The unit docker.service has entered the ‘failed’ state with result ‘exit-code’.
Nov 19 21:14:48 user11 systemd[1]: Failed to start Docker Application Container Engine.
– Subject: A start job for unit docker.service has failed
– Defined-By: systemd
– Support: link
–
– A start job for unit docker.service has finished with a failure.
–
– The job identifier is 1016 and the job result is failed.
Nov 19 21:14:48 user11 systemd[1]: docker.socket: Failed with result ‘service-start-limit-hit’.
– Subject: Unit failed
– Defined-By: systemd
– Support: link
–
– The unit docker.socket has entered the ‘failed’ state with result ‘service-start-limit-hit’.
Nov 19 21:15:01 user11 CRON[1955]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 19 21:15:01 user11 CRON[1954]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 19 21:15:01 user11 CRON[1962]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Nov 19 21:15:01 user11 CRON[1965]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
Nov 19 21:15:01 user11 CRON[1955]: pam_unix(cron:session): session closed for user root
Nov 19 21:15:01 user11 CRON[1954]: pam_unix(cron:session): session closed for user root

piter75 · November 19, 2019, 7:02pm

From what I could see on my install netfilter module is missing.
I will take care of it.

sudoom · November 29, 2019, 3:52pm

Hello, today update my pis with this 4 drivers :

linux-buster-root-legacy-rockpi-s
linux-dtb-legacy-rockpis
linux-image-legacy-rockpis
linux-u-boot-rockpi-s-legacy
then unistall and install docker, but have the same problem.

igorp · November 29, 2019, 4:09pm

What exactly have you changed? I assume you reboot before trying again?

sudoom · November 29, 2019, 4:48pm

yes sure, make it for difference pis, 2 pis install like new(new image, update, etc)

igorp · November 29, 2019, 5:06pm

OK, What do you get by executing this script:

wget https://raw.githubusercontent.com/docker/docker/master/contrib/check-config.sh
sudo bash check-config.sh

piter75 · November 29, 2019, 5:09pm

Docker is now broken on Rock Pi S
I will fix it over the weekend.

@igorp Could we re-spin the build of buster image for it then?

igorp · November 29, 2019, 5:19pm

Sure, ping me when its ready. There will be some delay since I am travelling.

If package update is good enough - upload fixed deb packages with version 19.11.4 here:

sudoom · November 29, 2019, 5:31pm

warning: /proc/config.gz does not exist, searching other paths for kernel config …
info: reading kernel config from /boot/config-4.4.198-rockpis …

Generally Necessary:

cgroup hierarchy: properly mounted [/sys/fs/cgroup]
CONFIG_NAMESPACES: missing
CONFIG_NET_NS: missing
CONFIG_PID_NS: missing
CONFIG_IPC_NS: missing
CONFIG_UTS_NS: missing
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_VETH: missing
CONFIG_BRIDGE: missing
CONFIG_BRIDGE_NETFILTER: missing
CONFIG_NF_NAT_IPV4: missing
CONFIG_IP_NF_FILTER: missing
CONFIG_IP_NF_TARGET_MASQUERADE: missing
CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: missing
CONFIG_NETFILTER_XT_MATCH_CONNTRACK: missing
CONFIG_NETFILTER_XT_MATCH_IPVS: missing
CONFIG_IP_NF_NAT: missing
CONFIG_NF_NAT: missing
CONFIG_NF_NAT_NEEDED: missing
CONFIG_POSIX_MQUEUE: enabled
CONFIG_DEVPTS_MULTIPLE_INSTANCES: missing

Optional Features:

CONFIG_USER_NS: missing
CONFIG_SECCOMP: enabled
CONFIG_CGROUP_PIDS: enabled
CONFIG_MEMCG_SWAP: missing
CONFIG_MEMCG_SWAP_ENABLED: missing
CONFIG_MEMCG_KMEM: enabled
CONFIG_BLK_CGROUP: enabled
CONFIG_BLK_DEV_THROTTLING: missing
CONFIG_IOSCHED_CFQ: enabled
CONFIG_CFQ_GROUP_IOSCHED: enabled
CONFIG_CGROUP_PERF: enabled
CONFIG_CGROUP_HUGETLB: missing
CONFIG_NET_CLS_CGROUP: missing
CONFIG_CGROUP_NET_PRIO: missing
CONFIG_CFS_BANDWIDTH: enabled
CONFIG_FAIR_GROUP_SCHED: enabled
CONFIG_RT_GROUP_SCHED: enabled
CONFIG_IP_NF_TARGET_REDIRECT: missing
CONFIG_IP_VS: missing
CONFIG_IP_VS_NFCT: missing
CONFIG_IP_VS_PROTO_TCP: missing
CONFIG_IP_VS_PROTO_UDP: missing
CONFIG_IP_VS_RR: missing
CONFIG_EXT4_FS: enabled
CONFIG_EXT4_FS_POSIX_ACL: enabled
CONFIG_EXT4_FS_SECURITY: enabled
Network Drivers:
- “overlay”:
  - CONFIG_VXLAN: missing
  - CONFIG_BRIDGE_VLAN_FILTERING: missing
    Optional (for encrypted networks):
    - CONFIG_CRYPTO: enabled
    - CONFIG_CRYPTO_AEAD: enabled
    - CONFIG_CRYPTO_GCM: enabled
    - CONFIG_CRYPTO_SEQIV: enabled
    - CONFIG_CRYPTO_GHASH: enabled
    - CONFIG_XFRM: enabled
    - CONFIG_XFRM_USER: missing
    - CONFIG_XFRM_ALGO: enabled
    - CONFIG_INET_ESP: missing
    - CONFIG_INET_XFRM_MODE_TRANSPORT: missing
- “ipvlan”:
  - CONFIG_IPVLAN: missing
- “macvlan”:
  - CONFIG_MACVLAN: missing
  - CONFIG_DUMMY: missing
- “ftp,tftp client in container”:
  - CONFIG_NF_NAT_FTP: missing
  - CONFIG_NF_CONNTRACK_FTP: missing
  - CONFIG_NF_NAT_TFTP: missing
  - CONFIG_NF_CONNTRACK_TFTP: missing
Storage Drivers:
- “aufs”:
  - CONFIG_AUFS_FS: missing
- “btrfs”:
  - CONFIG_BTRFS_FS: missing
  - CONFIG_BTRFS_FS_POSIX_ACL: missing
- “devicemapper”:
  - CONFIG_BLK_DEV_DM: missing
  - CONFIG_DM_THIN_PROVISIONING: missing
- “overlay”:
  - CONFIG_OVERLAY_FS: missing
- “zfs”:
  - /dev/zfs: missing
  - zfs command: missing
  - zpool command: missing

Limits:

/proc/sys/kernel/keys/root_maxkeys: 1000000

piter75 · November 29, 2019, 5:38pm

It should be enough as it is kernel only. I will do that.

@sudoom I will give you a shout when it’s ready.

sudoom · November 29, 2019, 5:54pm

ty, i’l be wait/

igorp · November 30, 2019, 9:04am

Try now.

apt update & apt upgrade

sudoom · November 30, 2019, 11:57am

everything works good, thanks @piter75 and @igorp