Hello again,
I have finally found some time to use a proper SD card to rebuild the image - this time based on the official released v131 codebase - and try again:
Oh, I see. Sorry, I should have done "bash -x /DietPi/dietpi/func/dietpi-set_hardware serialconsole enable" (which indeed works fine).
Fourdee wrote:Not sure what these are, try running the following to get more information:
Code: Select all
root@DietPi:~# systemctl status hwservice.service -l
● hwservice.service - hwservice
Loaded: loaded (/lib/systemd/system/hwservice.service; enabled)
Active: failed (Result: exit-code) since Thu 2016-09-22 15:25:44 BST; 5h 15min ago
Process: 591 ExecStart=/etc/init.d/hwservice start (code=exited, status=127)
Main PID: 591 (code=exited, status=127)
Sep 22 15:25:44 DietPi systemd[1]: Starting hwservice...
Sep 22 15:25:44 DietPi hwservice[591]: /etc/init.d/hwservice: line 16: /usr/sbin/hwservice: No such file or directory
Sep 22 15:25:44 DietPi systemd[1]: hwservice.service: main process exited, code=exited, status=127/n/a
Sep 22 15:25:44 DietPi systemd[1]: Failed to start hwservice.
Sep 22 15:25:44 DietPi systemd[1]: Unit hwservice.service entered failed state.
Code: Select all
root@DietPi:~# systemctl status hwservice_monitor.service -l
● hwservice_monitor.service - hwservice_monitor
Loaded: loaded (/lib/systemd/system/hwservice_monitor.service; enabled)
Active: failed (Result: exit-code) since Thu 2016-09-22 15:25:44 BST; 5h 17min ago
Process: 584 ExecStart=/etc/init.d/hwservice_monitor start (code=exited, status=127)
Main PID: 584 (code=exited, status=127)
Sep 22 15:25:44 DietPi hwservice_monitor[584]: /etc/init.d/hwservice_monitor: line 16: /usr/sbin/hwservice_monitor: No such file or directory
Sep 22 15:25:44 DietPi systemd[1]: hwservice_monitor.service: main process exited, code=exited, status=127/n/a
Sep 22 15:25:44 DietPi systemd[1]: Failed to start hwservice_monitor.
Sep 22 15:25:44 DietPi systemd[1]: Unit hwservice_monitor.service entered failed state.
Code: Select all
root@DietPi:~# systemctl status lcd4linux.service -l
● lcd4linux.service - daemon for driving LCD based displays
Loaded: loaded (/lib/systemd/system/lcd4linux.service; enabled)
Active: failed (Result: exit-code) since Thu 2016-09-22 15:25:44 BST; 5h 17min ago
Process: 524 ExecStart=/usr/sbin/lcd4linux $ARGS (code=exited, status=127)
Sep 22 15:25:44 DietPi lcd4linux[524]: /usr/sbin/lcd4linux: error while loading shared libraries: libX11.so.6: cannot open shared object file: No such file or directory
Sep 22 15:25:44 DietPi systemd[1]: lcd4linux.service: control process exited, code=exited status=127
Sep 22 15:25:44 DietPi systemd[1]: Failed to start daemon for driving LCD based displays.
Sep 22 15:25:44 DietPi systemd[1]: Unit lcd4linux.service entered failed state.
For the first two, it is very interesting that /usr/sbin/hwservice does indeed exist, but on the NanoPi3 is a dangling relative link:
Code: Select all
root@DietPi:~# ls -l /usr/sbin/hwservice
lrwxrwxrwx 1 root root 6 Jun 29 12:53 /usr/sbin/hwservice -> bin/ls
and of course, /usr/sbin/bin/ls does not exist. But I have no clue why "hwservice" should even link to "/bin/ls"...!?
Regarding the second one, it first looked like at least Debian packages libx11-6, libgd-3, libmysqlclient18 and libpython2.7.so.1.0 (including their dependencies) are missing, as the lcd4linux binary
on my NanoPi3 was dynamically linked against those libraries. But even installing all library dependencies did not help - now lcd4linux failed differently:
Code: Select all
root@DietPi:~# systemctl status -l lcd4linux.service
● lcd4linux.service - daemon for driving LCD based displays
Loaded: loaded (/lib/systemd/system/lcd4linux.service; enabled)
Active: failed (Result: resources) since Thu 2016-09-22 21:14:16 BST; 3s ago
Process: 2149 ExecStart=/usr/sbin/lcd4linux $ARGS (code=exited, status=0/SUCCESS)
Sep 22 21:14:16 DietPi LCD4Linux[2151]: LCD2USB: could not find a LCD2USB USB LCD
Sep 22 21:14:16 DietPi LCD4Linux[2151]: Error initializing driver LCD2USB: Exit!
Sep 22 21:14:16 DietPi systemd[1]: PID file /var/run/lcd4linux.pid not readable (yet?) after start.
Sep 22 21:14:16 DietPi systemd[1]: lcd4linux.service never wrote its PID file. Failing.
Sep 22 21:14:16 DietPi systemd[1]: Failed to start daemon for driving LCD based displays.
Sep 22 21:14:16 DietPi systemd[1]: Unit lcd4linux.service entered failed state.
I then noticed that "my" lcd4linux binary was not from Debian, but seemingly from FriendlyARM, as the Debian package "lcd4linux" was not even installed. I then did an "apt-get install lcd4linux", which indeed finally made the errors go away, and the lcd4linux service is now running, but still has suspicious output:
Code: Select all
root@DietPi:~# systemctl status -l lcd4linux.service
● lcd4linux.service - daemon for driving LCD based displays
Loaded: loaded (/lib/systemd/system/lcd4linux.service; enabled)
Active: active (running) since Thu 2016-09-22 21:24:59 BST; 54s ago
Process: 2620 ExecStart=/usr/sbin/lcd4linux $ARGS (code=exited, status=0/SUCCESS)
Main PID: 2622 (lcd4linux)
CGroup: /system.slice/lcd4linux.service
└─2622 /usr/sbin/lcd4linux
Sep 22 21:24:59 DietPi systemd[1]: lcd4linux.service: Supervising process 2622 which is not our child. We'll most likely not notice when it exits.
Sep 22 21:24:59 DietPi systemd[1]: Started daemon for driving LCD based displays.
Sep 22 21:24:59 DietPi LCD4Linux[2622]: widget 'Rain': class 'icon' not supported
Any ideas?
Fourdee wrote:awl29 wrote:The serial console device is called /dev/ttySAC0 on this device, not ttySAC2
Aha! Lets see if this has any effect on the serial console. Please try running:
Code: Select all
systemctl enable serial-getty@ttySAC0.service
reboot
ps aux > /root/attach_enabled.txt
Then same again with disable:
Code: Select all
systemctl disable serial-getty@ttySAC0.service
reboot
ps aux > /root/attach_disabled.txt
Results attached - the ZIP contains both the enabled and the disabled case.
Fourdee wrote:awl29 wrote:As you seem to have access to a NanoPi2, can you please check whether the same issues also exist there (which, IMO, is quite likely)?
Doubtful, we use ARMbian to build that image. But i'll make a note to check it either way.
I think you mixed up NanoPi2 (i.e. NanoPi-M2/NanoPC-T2 - for which no Armbian exists) with NanoPi NEO or NanoPi-M1 (for which indeed Armbian images are available). But in case you have indeed created the NanoPi2 image from an Armbian build for the Samsung/Nexell S5P4418 SoC, it would also be possible to use this exact build for NanoPi3 - except both the initramfs and the kernels on the /boot partition, which must be specific to S5P6818.
Additional news:
Even though I think the above issues should probably be fixed before the NanoPi3 image becomes official, I have nevertheless uploaded my new v131 master branch image for NanoPi3 to your dropbox. What do you think?
Thanks again, sorry for all those new (but truly minor!) issues & best regards,
awl