Nightly builds


#395

Latest nightly working great on my C2. Very impressive that there is one update tar for all supported devices now!


#396

What is the name of image of S905X?


#397

*Generic.img.gz for your box installation
And now only one . tar for update any of box versions


#398

@ozkaradag we confirm this and have a possible fix.


#399

Hi, the above procedure (manual update through custom channel) didn’t work to update from 20190211 (s912 only) to 20190215 (unified s905/s912). I could see the updated version in the json (through web), but the “Available versions” menu in kodi was empty.

Anyway, manual update through downloaded .tar fixed: now my s912 is updated to the last unified night build, and custom channel shows the available version.

Thanks.


#400

Thanks for reporting.
Due to some show stoppers in some of the last nightlies I had to pull and rebuild them.
I assume, the values in the json file sometimes were simply wrong during this time.
It was more important to have issue-free images instead of a functional json file.


#401

WetekPlay2 CoreELEC 9.0 live tv tests.Live TV channel Astra 19.2 travelXP 4K. Test İmaj CoreELEC-Amlogic.arm-9.0-nightly_20190215a


#402

In the final version of CoreELEC 9.0 there is the same error.


#403

Greetings,

Dear friend, the problem is solved.

Thank you so much.

Best regards…


#404

The source of the error was caused by the AVR video output.I changed 1080P24Hz to 1080P and it worked fine.


#405

I can’t install the last builds after 20190206 on my C2. It will install but not loading kodi anymore. I can ssh in and after digging arround I find that symlinks not set correct…

How can I fix this? These symlinks are missing in newer builds after 20190206:

lrwxrwxrwx    1 root     root            18 Feb 16 14:28 libEGL.so -> /var/lib/libEGL.so
lrwxrwxrwx    1 root     root            18 Feb 16 14:28 libEGL.so.1 -> /usr/lib/libEGL.so
lrwxrwxrwx    1 root     root            18 Feb 16 14:28 libEGL.so.1.0.0 -> /usr/lib/libEGL.so
lrwxrwxrwx    1 root     root            24 Feb 16 14:28 libGLESv1_CM.so -> /var/lib/libGLESv1_CM.so
lrwxrwxrwx    1 root     root            24 Feb 16 14:28 libGLESv1_CM.so.1 -> /usr/lib/libGLESv1_CM.so
lrwxrwxrwx    1 root     root            24 Feb 16 14:28 libGLESv1_CM.so.1.0.1 -> /usr/lib/libGLESv1_CM.so
lrwxrwxrwx    1 root     root            21 Feb 16 14:28 libGLESv2.so -> /var/lib/libGLESv2.so
lrwxrwxrwx    1 root     root            21 Feb 16 14:28 libGLESv2.so.2 -> /usr/lib/libGLESv2.so
lrwxrwxrwx    1 root     root            21 Feb 16 14:28 libGLESv2.so.2.0.0 -> /usr/lib/libGLESv2.so
lrwxrwxrwx    1 root     root            21 Feb 16 14:28 libGLESv3.so -> /var/lib/libGLESv3.so
lrwxrwxrwx    1 root     root            21 Feb 16 14:28 libGLESv3.so.3 -> /usr/lib/libGLESv3.so
lrwxrwxrwx    1 root     root            21 Feb 16 14:28 libGLESv3.so.3.0.0 -> /usr/lib/libGLESv3.so

#406

how can i build this for myself?
Getting that erros after unified image patches…

==================================================================
 ERROR: You need to specify a valid device for the Amlogic project
==================================================================

 Valid devices for project: Amlogic
 - Odroid_C2

#407

PROJECT=Amlogic ARCH=arm make release


#408

and this is the error i receive…

jarek@tower:~/CoreElec$ PROJECT=Amlogic ARCH=arm make release
./scripts/image release

 ================================================
 ERROR: You need to specify a valid device for the Amlogic project
 ================================================

 Valid devices for project: Amlogic
 - Odroid_C2
Makefile:9: recipe for target 'release' failed

#409

@pogo1975 you are not using the latest source code :see_no_evil:


#410

@bgx what DTB are you using? This would be the only reason that I can see for your issue

The symlinks are setup depending on which GPU is available on your device and this is read from the dtb


#411

Symlinks look fine. Can you ls -l /var/lib?


#412

@adamg: I don’t use a special dtb just updated all the way with tar and the first installation from month with the c2.img.gz

@Ray: Shure, here’s the output:

CoreELEC:~ # ls -l /var/lib
total 0

drwxr-xr-x 2 root root 60 Jun 22 2018 dbus
lrwxrwxrwx 1 root root 63 Jun 22 2018 docker -> /storage/.kodi/userdata/addon_data/service.system.docker
/docker
drwxr-xr-x 14 root root 4060 Jun 22 2018 firmware
drwx------ 2 root root 40 Jun 22 2018 portables
drwx------ 2 root root 40 Jun 22 2018 private
drwx------ 2 root root 120 Feb 18 07:43 pulse
drwxr-xr-x 2 root root 120 Feb 18 07:43 samba
drwxr-xr-x 3 root root 60 Jun 22 2018 systemd


#413

Well that explains it though. No mali symlinks there. This looks like a dtb issue. Can you just copy the odroidc2.dtb to /flash/dtb.img and reboot


#414

That’s what I also think. Will do so and report back. Thx :slight_smile:

Where to get the c2.dtb ?