Posts by natumbri

dhanar10 - this may sound obvious, but do you have the rx and tx around the right way (ie crossed over)?

Have not managed to find a usb-serial yet, but I think I have a spare arduino in a box somewhere - I'll use that if I find it.

In the meantime, I can confirm the following builds an image that boots (from fresh install and from update):

git checkout master
git pull
git revert 4c80f82f21028b08b6a2d10201eb111baae48909
PROJECT=Allwinner ARCH=arm DEVICE=H3 UBOOT_SYSTEM=nanopi-m1 make image

Maybe dejan_ and dhanar10 the issue is the same one you are experiencing - the nanopi M1 is similar to the orange pi boards you have.

I thought someone might ask for that Sadly, I'm not sure if I have a serial-USB around here anywhere. I'll investigate.

Hi,

I have a nanopi M1. LibreELEC has been working well up until recently, but recent nightly builds do not boot. Neither after an update, nor from a fresh install.

I think I have tracked the problem down to the update to u-boot: update to v2020.01 (commit u-boot: update to v2020.01 · LibreELEC/LibreELEC.tv@4c80f82 · GitHub). A build from u-boot: use upstream patches for Orange Pi 3 (the commit prior to the u-boot 2020.01 commit) builds and boots just fine - as far as I can tell, this is the last one that boots.

Thoughts, anyone?

For 512mb devices, consider building from master with zram enabled. With the switch to linux 5, zram is better than it used to be. Not sure how much better, or if it fixes anything, but worth a try perhaps?

see here for tiny bit more discussion

and here for suggestions regarding what to change

ambidex the --hostID setting is for setting ... the hostID of the machine running the snapclient. At the moment, there is no setting for the hostname or IP address of the machine running the snapserver.

There are a number of cases where being able to set a hostname or IP address for the snapserver would be useful (eg. where machines are on different subnets).

I've created a pull request to add such a setting: Addon - Snapclient - Add snapserver hostname/IP setting by natumbri · Pull Request #3875 · LibreELEC/LibreELEC.tv · GitHub

Cheers,

Nik.

Quote from milhouse

natumbri your config diff is incomplete, you'll need a few more: http://ix.io/1wyu

Nah, I don't think so. The only changes that you have and I don't, that actually do anything, are:

+CONFIG_CRYPTO_LZO=m
+CONFIG_LZO_COMPRESS=m

With the default LZO-RLE, I don't think those are required? ([v3,0/7] lib/lzo: performance improvements - Patchwork) My kernel seems to be working just fine without them, in any event. The zram swap is reported as available (and is used from time to time), and the compression algorithm is reported as lzo-rle.

But... I could be wrong: is there any way to check if it is *actually* working, or if it just *looks* like it is working?

Also, maybe the switch to LZO-RLE (with the associated reduced processing overhead) is a reason to reconsider for LE? Processing overhead seems to be the main (*only* - but for that, why wouldn't you turn it on?) argument against implementing zram on LE. And that is much less of a problem with LZO-RLE.

Or not. As has been mentioned, people who really want can always build it for themselves.

Cheers,

Nik

Easy enough to try. I use it on a 512MB H3 NanoPi M1. Not sure if it makes any difference, one way or the other.

diff --git a/projects/Allwinner/linux/linux.arm.conf b/projects/Allwinner/linux/linux.arm.conf

index 5ca704dc7c..19c3913ec4 100644
--- a/projects/Allwinner/linux/linux.arm.conf
+++ b/projects/Allwinner/linux/linux.arm.conf
@@ -777,6 +777,9 @@ CONFIG_CMA_AREAS=7
 # CONFIG_ZPOOL is not set
 # CONFIG_ZBUD is not set
 # CONFIG_ZSMALLOC is not set
+CONFIG_ZSMALLOC=m
+CONFIG_ZRAM=m
+CONFIG_PGTABLE_MAPPING=y
 CONFIG_GENERIC_EARLY_IOREMAP=y
 # CONFIG_IDLE_PAGE_TRACKING is not set
 CONFIG_FRAME_VECTOR=y

/storage/.config/autostart.sh

#!/bin/bash

( 
modprobe zram 

swapoff -a

totalmem=`free | grep -e "^Mem:" | awk '{print $2}'`
mem=$(( $totalmem * 512))

echo $mem > /sys/block/zram0/disksize
mkswap /dev/zram0
swapon -p 100 /dev/zram0
) &

Quote from jernej

natumbri please test this image first: libreelec-h3.arm-9.1-devel-20190605004918-cdc4ec0-nanopi_m1.img.gz

If it is good, I'll ask to include this board in nightlies.

Thanks - I've done a basic test, and the image seems to work at least as well as the early build.

Cheers, and thanks again for all your work on this!!

Nik

Quote from jernej

natumbri please test this image first: libreelec-h3.arm-9.1-devel-20190605004918-cdc4ec0-nanopi_m1.img.gz

If it is good, I'll ask to include this board in nightlies.

Thanks! I will test and rreport back.

Cheers

Nik

Quote from jernej

Yes, but note that only version with 1 GiB of RAM will be supported. If you have 512 MiB version you can still use same image, but I don't accept bug reports which occurs due to memory consumption. Which version do you have?

Hi - just wondering if you've been able to add the nano pi M1 build, at this stage? I haven't been able to find it.

Thanks again for all your efforts!

Nik

Quote from jernej

Yes, but note that only version with 1 GiB of RAM will be supported. If you have 512 MiB version you can still use same image, but I don't accept bug reports which occurs due to memory consumption. Which version do you have?

Thanks! I thought you might say that - you have been very clear about 512MiB devices, and I can certainly understand your reasoning!

I have a 512MiB device. I'm currently using a build from the previous thread. I haven't run into any low memory issues, but I'm a pretty light user.

Thanks again

Nik

Thanks for all the work on this!

Any chance of adding a build for the NanoPi M1?

Cheers

Nik