I can build it, but it won’t run on board, only green light on, and plugin Ethernet cannot see shows in router side.
Rock pi s debian ftdi driver missing
Can you try to connect serial console to it to check what the error is?
Console is on UART0 which is either on 8,10 (v1.1+) or 9,1 (v1.0) depending on the board version.
I will probably upload somewhere precompiled version soon.
nothing readable print out on 115200 bound rate
I was going to mention it - for Rockchip platform 1500000 is default baudrate.
still nothing print out. can you send me a image file and have a try?
Try this image, I have just booted it.
EDIT: One more mention, there is neither WiFi nor Bluetooth in this image.
rockpi login: root
Password:
____ ___ ____ _ __ ____ _ ____
| _ \ / _ \ / ___| |/ / | _ \(_) / ___|
| |_) | | | | | | ' / | |_) | | \___ \
| _ <| |_| | |___| . \ | __/| | ___) |
|_| \_\\___/ \____|_|\_\ |_| |_| |____/
Welcome to Debian Buster with Armbian Linux 4.4.192-rockchip64
System load: 0.13 0.20 0.09 Up time: 2 min
Memory usage: 9 % of 425MB IP:
CPU temp: 34°C
Usage of /: 1% of 58G
root@rockpi:~# uname -a
Linux rockpi 4.4.192-rockchip64 #24 SMP PREEMPT Fri Oct 18 19:42:24 UTC 2019 aarch64 GNU/Linux
1 Like
thanks a lot. one more thing is what’s the password? I tried password, and it is not working
It is Armbian so default root password is: 1234 and you need to change it on first login (you can do it over ssh). At the same time you are forced to create a normal user with your own password.
I wonder what the problem was with the image built by you… Did you build it with Vagrant, Docker or bare metal?
Maybe I forgot to push something to the repo. I will try to build it in pristine environment to check.
I am using ubuntu to build it, I use the mini image from the armbian documents
Ok. Glad that the precompiled image worked 
Thank you a lot.
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, ()
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.
Thanks, for answer.
I install that image, and in newer version I havent this problem, but I have problem with docker.
Oh. I never optimised it for docker 
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/ 
That’s interesting
What problem with docker is it exactly? Can you attach error log?
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
From what I could see on my install netfilter module is missing.
I will take care of it.
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.