Page 2 of 2

Re: Nanopi M4v2 support request

Posted: Tue Aug 18, 2020 10:32 am
by MichaIng
Hmm probably the proprietary driver blob does not work with the open-source panfrost kernel driver.

Please try to install the Debian mesa driver packages:
apt install --reinstall libgles2 libegl1
Confirm oud it's a downgrade and the libmali package will be removed.

Re: Nanopi M4v2 support request

Posted: Sun Aug 23, 2020 11:22 am
by rothchild
MichaIng wrote: Tue Aug 18, 2020 10:32 am Hmm probably the proprietary driver blob does not work with the open-source panfrost kernel driver.

Please try to install the Debian mesa driver packages:
apt install --reinstall libgles2 libegl1
Confirm oud it's a downgrade and the libmali package will be removed.
Thanks, that does enable Kodi to start at least, although it's smashing the processor even when idling (causing it to overheat in not much time) + there's no sound and no CEC (both of which work on this box with libreelec/armbian)

(also this kodi install doesn't seem quite the same as the on the old raspberry pi (under diet-pi) it didn't by default install the add-on repos for some reason?

Re: Nanopi M4v2 support request

Posted: Sun Aug 23, 2020 12:57 pm
by MichaIng
Yes that is the generic Debian Kodi, now with Debian (Mesa) EGL/GLES drivers, and the respective Xserver version. Sound and CEC support are of course included, so I guess a configuration issue. I didn't use Kodi for a long time, maybe others can help better, but recheck your ALSA/audio settings, check if aplay or any other audio player can play sound successfully.

libreelec is a pure Kodi OS, I'd expect they support most boards better, despite RPi and Odroids where we simply have full support. The RPi foundation+community is quite active in developing and updating their kernel, GPU drivers/firmware and several GPU applications like Kodi and Chromium and others, so there we have no issue. (Plain) Armbian does not have any GPU support, does it? The community creates this media feature script, but that is basically made for Ubuntu, meanwhile quite outdated, so I don't believe its working on a current Armbian Buster image, is it?

So basically it seems that for the ARM proprietary Mali drivers one needs a special kernel build or module at least, the Mali library blob of course, a special Xserver build on that and likely special Kodi build as well. The current Debian Buster open-source Mesa/panfrost drivers do not yet (fully) support RK3399, or the Kodi build does not work well with it. I read that panfrost and current Mesa (available on Debian Bullseye) has very good RK3328 support now, even better then ARM proprietary driver (to be tested), and read as well about Mesa 19 supporting RK3399 quite good already (Buster is on Mesa 18, Bullseye on Mesa 20). This means that Debian Bullseye potentially solves/enabled GPU supported for a bunch of SoCs.

I could create a M4V2 Bullseye image, interested to test it?
We anyway need to start testing Bullseye more broadly then only my VirtualBox instance I run changes through, so proper GPU/Kodi support seems a good reason for "official" testing images.

Re: Nanopi M4v2 support request

Posted: Sun Aug 23, 2020 6:17 pm
by rothchild
Thanks for the update, yes I'd be very happy to help with testing.

Confirmed that the closest I've got to having this run satisfactorily so far has been with Armbian Bullseye.

I think that the issue with sound is tied to it wanting to play through the realtek codec (which I assume is the 3.5mm socket) and I can find no way to switch it to HDMI, it seems like kodi is just not seeing the CEC (I can see that the CECLib is installed, it's just not seeing it for some reason).

Re: Nanopi M4v2 support request

Posted: Sun Sep 13, 2020 9:35 am
by rothchild
Was having all sorts of bother getting it to work nicely with Kodi so I've had a shuffle around and it's been relegated to running Transmission, Couch Potato and PiHole, but it's really unreliable.

Transmission regularly stops working, Ican log in and restart the transmission-daemon service but then quite often the whole lot just drops the ethernet connection and I have to powercycle it to get it back up (as I just get 'no route to host' on ssh and can see via my router control panel that it's not connected).

Any thoughts on how to improve the stability of transmission and the ethernet port on one of these boxes?

Re: Nanopi M4v2 support request

Posted: Sun Sep 13, 2020 1:12 pm
by Joulinar
Hi,

check kernel messaged once the issue happen dmesg -l err,crit,alert,emerg
Plus, having a look to journal about related massages journalctl -n 100 --no-pager
Or dedicated for transmission messages journalctl -u transmission-daemon.service -n 100 --no-pager
Have a look as well to CPU + Mem usage.

Maybe there are some indications why services and connections are failing

Re: Nanopi M4v2 support request

Posted: Sun Sep 13, 2020 5:24 pm
by MichaIng
Please have an eye on memory usage (by Transmission), e.g. via htop. On Debian Stretch there was a bug that made it using more and more memory until OOM killer kicks in. This should have been resolved but he had at least one other report that it still uses too much memory. Since we pull the official Debian build, this is a bid out of our control, but there is at least a way to limit it's memory usage, worst case it needs a restart if it fails with that reached: https://github.com/MichaIng/DietPi/issu ... -502152193

Re: Nanopi M4v2 support request

Posted: Wed Sep 16, 2020 9:50 pm
by rothchild
Thanks both,

Transmisson is at least restartable (incidentally how much memory is too much?), however I now can't start Couchpotato at all

Code: Select all

root@pihole:~# service couchpotato restart
Job for couchpotato.service failed because the control process exited with error code.
See "systemctl status couchpotato.service" and "journalctl -xe" for details.

Code: Select all

root@pihole:~# systemctl status couchpotato.service
● couchpotato.service - LSB: CouchPotato PVR for Usenet and torrents
   Loaded: loaded (/etc/init.d/couchpotato; generated)
   Active: failed (Result: exit-code) since Wed 2020-09-16 20:40:10 BST; 1min 3s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 24198 ExecStart=/etc/init.d/couchpotato start (code=exited, status=2)

Sep 16 20:40:10 pihole systemd[1]: Starting LSB: CouchPotato PVR for Usenet and torrents...
Sep 16 20:40:10 pihole couchpotato[24198]: Starting CouchPotato:start-stop-daemon: matching on world-writable pidfile /var/run/couchpotato/couchpotato.pid is insecure
Sep 16 20:40:10 pihole couchpotato[24198]:  failed!
Sep 16 20:40:10 pihole systemd[1]: couchpotato.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Sep 16 20:40:10 pihole systemd[1]: couchpotato.service: Failed with result 'exit-code'.
Sep 16 20:40:10 pihole systemd[1]: Failed to start LSB: CouchPotato PVR for Usenet and torrents.
And I was just trying to get 'journalctl -xe' but it's severed itself from the network (the router is showing it as disconnected, it's given up on ethernet) so I'll leave this here for now, while I go and manually restart it.

Re: Nanopi M4v2 support request

Posted: Fri Sep 18, 2020 9:29 pm
by MichaIng
Please try:

Code: Select all

rm -R /run/couchpotato
systemctl restart couchpotato