Nightly builds (NEW)

1 Like

Updated on Coreelec-Amlogic. arm-9.2-nightly_201229, how to enable zram?


Here you can find instruction for autostart.sh

Only one zram disk is created 256M

Try to execute commands one by one and check the output if it has some errors

there are errors, but I can’t provide them right now, sorry.
maybe I’ll do it later…

2020-12-29T21:00:00Z

CoreELEC (official): nightly_20201230 (Amlogic.arm)
CoreELEC:~ # modprobe zram num_devices=4
CoreELEC:~ # echo 256M > /sys/block/zram0/disksize
CoreELEC:~ # echo 256M > /sys/block/zram1/disksize
-sh: can't create /sys/block/zram1/disksize: nonexistent directory
CoreELEC:~ # echo 256M > /sys/block/zram2/disksize
-sh: can't create /sys/block/zram2/disksize: nonexistent directory
CoreELEC:~ # echo 256M > /sys/block/zram3/disksize
-sh: can't create /sys/block/zram3/disksize: nonexistent directory
CoreELEC:~ # mkswap /dev/zram0
Setting up swapspace version 1, size = 268431360 bytes
UUID=289b6fb4-1f9e-4d8f-bb7b-bba337ba0249
CoreELEC:~ # mkswap /dev/zram1
mkswap: can't open '/dev/zram1': No such file or directory
CoreELEC:~ # mkswap /dev/zram2
mkswap: can't open '/dev/zram2': No such file or directory
CoreELEC:~ # mkswap /dev/zram3
mkswap: can't open '/dev/zram3': No such file or directory
CoreELEC:~ # swapon -p 10 /dev/zram0
CoreELEC:~ # swapon -p 10 /dev/zram1
swapon: cannot open /dev/zram1: No such file or directory
CoreELEC:~ # swapon -p 10 /dev/zram2
swapon: cannot open /dev/zram2: No such file or directory
CoreELEC:~ # swapon -p 10 /dev/zram3
swapon: cannot open /dev/zram3: No such file or directory
CoreELEC:~ # swapon -s
Filename				Type		Size	Used	Priority
/dev/zram0                             	partition	262140	0	10

i had an update today which had a freaking long changelog (84 pages or so).
i guess that was an error. can someone provide the corrected changelog?

filkint, I think there is already some ram used and you can use only free ram.

Try to stop kodi first:

free -m
systemctl kodi stop
modprobe zram num_devices=4
echo 256M > /sys/block/zram0/disksize
... and all other commands
free -m

I think nothing was updated from last time. Could be some error with build script.

1 Like
CoreELEC (official): nightly_20210102 (Amlogic.arm)
CoreELEC:~ # htop
CoreELEC:~ # free -m
              total        used        free      shared  buff/cache   available
Mem:            803         170         363          11         269         570
Swap:             0           0           0
CoreELEC:~ # systemctl stop kodi
CoreELEC:~ # free -m
              total        used        free      shared  buff/cache   available
Mem:            803          91         441          11         270         649
Swap:             0           0           0
CoreELEC:~ # modprobe zram num_devices=4
CoreELEC:~ # echo 256M > /sys/block/zram0/disksize
CoreELEC:~ # echo 256M > /sys/block/zram1/disksize
-sh: can't create /sys/block/zram1/disksize: nonexistent directory
CoreELEC:~ # echo 256M > /sys/block/zram2/disksize
-sh: can't create /sys/block/zram2/disksize: nonexistent directory
CoreELEC:~ # echo 256M > /sys/block/zram3/disksize
-sh: can't create /sys/block/zram3/disksize: nonexistent directory
CoreELEC:~ # mkswap /dev/zram0
Setting up swapspace version 1, size = 268431360 bytes
UUID=386e6360-443f-4c0d-a963-811b5fc4618d
CoreELEC:~ # mkswap /dev/zram1
mkswap: can't open '/dev/zram1': No such file or directory
CoreELEC:~ # mkswap /dev/zram2
mkswap: can't open '/dev/zram2': No such file or directory
CoreELEC:~ # mkswap /dev/zram3
mkswap: can't open '/dev/zram3': No such file or directory
CoreELEC:~ # swapon -p 10 /dev/zram0
CoreELEC:~ # swapon -p 10 /dev/zram1
swapon: cannot open /dev/zram1: No such file or directory
CoreELEC:~ # swapon -p 10 /dev/zram2
swapon: cannot open /dev/zram2: No such file or directory
CoreELEC:~ # swapon -p 10 /dev/zram3
swapon: cannot open /dev/zram3: No such file or directory
CoreELEC:~ # free -m
              total        used        free      shared  buff/cache   available
Mem:            803          82         450          11         270         658
Swap:           255           0         255

P.S. Can I add an lz4 compressor?

As you can see you have only 441 MB free ram. And you can create only one 256 MB block for zram. Try higher size or use 2 smaller blocks.

For lz4: before settings size set the algorithm with

echo lz4 > /sys/block/zramX/comp_algorithm

you can check it with

cat /sys/block/zram0/comp_algorithm

and you get result

lzo [lz4] deflate lz4hc 842

LZ4 is enabled only on Amlogic-ng project.

CoreELEC (official): nightly_20210103 (Amlogic.arm)
CoreELEC:~ # modprobe zram num_devices=1
CoreELEC:~ # echo lz4 > /sys/block/zram0/comp_algorithm
-sh: can’t create /sys/block/zram0/comp_algorithm: Permission denied

CoreELEC:~ # cat /sys/block/zram0/comp_algorithm
cat: can’t open ā€˜/sys/block/zram0/comp_algorithm’: No such file or directory

Ah, LZ4 is not enabled on Amlogic project: https://github.com/CoreELEC/CoreELEC/blob/coreelec-9.2/projects/Amlogic/linux/linux.aarch64.conf#L139

It is available only on Amlogic-ng.

CoreELEC:~ # echo lzo > /sys/block/zram0/comp_algorithm
-sh: can’t create /sys/block/zram0/comp_algorithm: Permission denied
CoreELEC:~ # cat /sys/block/zram0/comp_algorithm
cat: can’t open ā€˜/sys/block/zram0/comp_algorithm’: No such file or directory
?

filkint, LZ4 is enabled and works only on Amlogic-ng project. In Amlogic is disabled.

I know that, I don’t know why?

Because no one was using it.

It will be available in next nightly build.

Updated to CoreELEC-Amlogic.arm-9.2-nightly_20210104, hanging on the logo.

Yes, seems CoreELEC-Amlogic.arm-9.2-nightly_20210104 is bad and doesn’t boot :frowning:

Yes, the nightly got removed to prevent update to 20200104.

For those who already updated please download last working nightly:
https://relkai.coreelec.org/archive/CoreELEC-Amlogic.arm-9.2-nightly_20210103.tar

Replace on your CE boot media the files kernel.img with KERNEL and SYSTEM with SYSTEM from the tar located in the subfolder target. Please rename KERNEL to kernel.img again. CE should boot normally again without any loss of data.
The copy of the md5 files is not necessary.