CoreELEC 19.5-Matrix_rc2 Discussion

This patch itself should be enough to delay the loading of network module so JL2101 can be driven by the generic PHY driver on X3. Remember to set CONFIG_STMMAC_JL2XX1=y in your linux.conf

Why would you use old 9.2 source though? There might be some differences that cause the patch to not work

I also have source of a modified official JL2101 driver that can work on CE’s 4.9 kernel, but that seems to have no performance gain compared to generic driver, so I’m not suggesting to use it

Thank you! Hopefully I will get ethernet working eventually, out of the box or with the patch :slight_smile:

Why 9.2? Simple because I am using shared Kodi DB @MySQL, and I have older devices in the same “mesh” (Odroid C2’s and few Rpi2), which are not supported by ng CE… And honestly, for my needs Leia is sufficient (hopefully all major addons like youtube, scrappers are still working), so I am not in hurry to replace whole infrastructure at this point…

I guess next “big bang” would be with spread of AV1, and it will take years…

Good morning to all.
Sorry for my ignorance, but I’ve been tinkering with my Mekol KI pro box, Amlogic,S905D, with Coreelec installed in the Root.
I want to upgrade it so I can install CoreELEC 19.5-Matrix_rc2 .
I tried everything that says here, but it does not install I get the same image posted by the friend of the forum, ¨¨¨ raw row ¨¨.

I’m looking for the forum, the step by step clean update from scratch, I do not know how to do it. The problem is that I also get the page in English and the translator sometimes goes well and sometimes not.

I tried everything, I put an image where the guide tells you, but I get several zip files and I do not know which one to choose. I put through the Samba application this image ----- [CoreELEC-Amlogic-ng.arm-19.5-Matrix_rc2-Generic.img.gz] -----, reboot and nothing happened.

Then I did the same operation and installed the tar file, through Samba, I put this file ---- [CoreELEC-Amlogic-ng.arm-19.5-Matrix_rc2.tar] ----. Nothing happened either, I got the same as the friend fila cruda.

I think I put the file correctly, I put it in the Update folder. The only thing, I don’t know if I should extract the zip file and put it in the Update folder.

I hope you can help me or guide me the steps to follow, the only more complicated problem is to install from scratch.

Thank you very much for all the work you do.

Read this first por favor, solo comunicaciones en inglés

Hi Reddevil. I assume you are not currently on CE19 - otherwise I’m sure the system would probably update you automatically.
If you are therefore on a previous version (CE18 I’m guessing), I wouldn’t do an update but rather a clean install.
Go to: https://coreelec.org/
Click on 19.5-Matrix_rc2 (Stable)
Click New installation
Click Mecool K1 Pro
Click Download Image

After that, install Rufus on your computer and use it to write the downloaded image to a SD card.
Navigate to the SD card and copy the file "gxl_p230_k1_pro’ from the ‘device_tree’ folder to the SD card root folder and rename it to dtb.img
(if you cannot see the SD card, you might not to first assign a drive letter to it)

Put the SD card in your media player and hopefully it boots up into CE 19.

1 Like

We’re also having display issues with rc2 that rc1 didn’t have, both boxes S905X3 based, 4k content.

X96 Max Plus, HiSense 4k TV - black screen on playing file, tv says no input
X96 Air, TCL 4k TV - Green screen with scrambled artifacts

Both mostly work a second time if you stop the playback and then play the same thing again, it’s a pain though. The below is an example, it worked fine again after stopping and playing again.

Try with nightly 20220910

I have the same problem as vmce. Garbled screen when playing 4k hdr content on my x96max plus (s905x3) and on my Hk1 rbox x4 (s905x4). Tried the latest nightly, but that doesn’t help. Reinstalled 19.3 on the X96, because that version doesn’t have the problem.

1 Like

Hello Zordon.

Thanks. I will try to see if it is updated.
I have coreelec installed in the root of the K1 pro.

Thanks, I’ll try this weekend, with work I don’t have much time. When I try it, I’ll let you know.

Thanks a lot.

I have seen the same garbled screen after the movie finished. Instead of changing the resolution to “standard FullHD” and “Kodi menu” the garbled screen with colors and resolution off appeared. Have paused the 2-hour long movie a few times if that makes a difference.

Try and use the new function limit color depth and set it to 10 or 8bit.

All my videos are switched to 12 bit, PVR and Movies. Is that right? it seems to play fine. or rather limit it to 10 bit.

issue with CoreELEC (official): 19.5-Matrix_rc2 (Amlogic-ng.arm) on the X96 2GB with /media/COREELEC/device_trees/gxl_p212_2g.dtb copied to dtb.img:

When TV coldstarts the box (= the box is powered from the TV over USB), then we always end up with kernel_hdmimode=576i50hz in resolution.ini

When it is not working (TV coldstarted the CoreELEC box):

CoreELEC:~ # cat /flash/config.ini | grep ^vout
vout='1080p60hz'

cat /sys/class/amhdmitx/amhdmitx0/disp_mode 
VIC:22

CoreELEC:~ # fw_printenv bootargs
bootargs=rootfstype=ramfs init=/init console=ttyS0,115200 no_console_suspend earlyprintk=aml-uart,0xc81004c0 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 androidboot.selinux=permissive logo=osd1,loaded,0x3d800000,576cvbs maxcpus=4 vout=576cvbs,enable hdmimode=1080p60hz cvbsmode=576cvbs hdmitx= cvbsdrv=0 androidboot.firstboot=0 jtag=apao androidboot.hardware=amlogic mac=xxx androidboot.mac=xxx

CoreELEC:~ # dmesg | grep "fb:"| head -n 4
[    0.000000@0]d fb: osd1
[    0.000000@0]d fb: loaded
[    0.000000@0]d fb: 0x3d800000
[    0.000000@0]d fb: 576cvbs

CoreELEC:~ # cat /flash/resolution.ini 
# WARNING DO NOT MODIFY THIS FILE! ALL CHANGES WILL BE LOST!
kernel_hdmimode=576i50hz
frac_rate_policy=0
native_4k_gui=0
hdmitx=,
allfmt_names=2160p60hz 2160p50hz 2160p30hz 2160p25hz 2160p24hz smpte24hz smpte25hz smpte30hz smpte50hz smpte60hz 1080p25hz 1080p30hz 1080p50hz 1080p60hz 1080p24hz 1080p120hz 1080i60hz 1080i50hz 720p60hz 720p50hz 480p60hz 480i60hz 576p50hz 576i50hz 480p60hz_4x3 480i60hz_4x3 576p50hz_4x3 576i50hz_4x3 2160p60hz420 smpte60hz420 2160p50hz420 smpte50hz420 2560x1080p50hz 2560x1080p60hz 640x480p60hz 800x480p60hz 800x600p60hz 852x480p60hz 854x480p60hz 1024x600p60hz 1024x768p60hz 1152x864p75hz 1280x768p60hz 1280x800p60hz 1280x960p60hz 1280x1024p60hz 1360x768p60hz 1366x768p60hz 1400x1050p60hz 1440x900p60hz 1440x2560p60hz 2560x1440p60hz 1600x900p60hz 1600x1200p60hz 1680x1050p60hz 1920x1200p60hz 2048x1080p24hz 2160x1200p90hz 2560x1600p60hz 3440x1440p60hz 2400x1200p90hz 3840x1080p60hz invalid

vs.

when it is working (TV was already on when CoreELEC booted):

CoreELEC:~ # cat /flash/config.ini | grep ^vout
vout='1080p60hz'

CoreELEC:~ # cat /sys/class/amhdmitx/amhdmitx0/disp_mode 
VIC:16

CoreELEC:~ # fw_printenv bootargs
bootargs=rootfstype=ramfs init=/init console=ttyS0,115200 no_console_suspend earlyprintk=aml-uart,0xc81004c0 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 androidboot.selinux=permissive logo=osd1,loaded,0x3d800000,576cvbs maxcpus=4 vout=576cvbs,enable hdmimode=1080p60hz cvbsmode=576cvbs hdmitx= cvbsdrv=0 androidboot.firstboot=0 jtag=apao androidboot.hardware=amlogic mac=xxx androidboot.mac=xxx

CoreELEC:~ # dmesg | grep "fb:"| head -n 4
[    0.000000@0]d fb: osd1
[    0.000000@0]d fb: loaded
[    0.000000@0]d fb: 0x3d800000
[    0.000000@0]d fb: 1080p60hz

CoreELEC:~ # cat /flash/resolution.ini 
# WARNING DO NOT MODIFY THIS FILE! ALL CHANGES WILL BE LOST!
kernel_hdmimode=1080p60hz
frac_rate_policy=0
native_4k_gui=0
hdmitx=,
allfmt_names=2160p60hz 2160p50hz 2160p30hz 2160p25hz 2160p24hz smpte24hz smpte25hz smpte30hz smpte50hz smpte60hz 1080p25hz 1080p30hz 1080p50hz 1080p60hz 1080p24hz 1080p120hz 1080i60hz 1080i50hz 720p60hz 720p50hz 480p60hz 480i60hz 576p50hz 576i50hz 480p60hz_4x3 480i60hz_4x3 576p50hz_4x3 576i50hz_4x3 2160p60hz420 smpte60hz420 2160p50hz420 smpte50hz420 2560x1080p50hz 2560x1080p60hz 640x480p60hz 800x480p60hz 800x600p60hz 852x480p60hz 854x480p60hz 1024x600p60hz 1024x768p60hz 1152x864p75hz 1280x768p60hz 1280x800p60hz 1280x960p60hz 1280x1024p60hz 1360x768p60hz 1366x768p60hz 1400x1050p60hz 1440x900p60hz 1440x2560p60hz 2560x1440p60hz 1600x900p60hz 1600x1200p60hz 1680x1050p60hz 1920x1200p60hz 2048x1080p24hz 2160x1200p90hz 2560x1600p60hz 3440x1440p60hz 2400x1200p90hz 3840x1080p60hz invalid

This seems to suggest that even before the kernel starts to do anything, the firmware somehow sets the resolution to 576cvbs when things go wrong.
Why? Is CoreELEC somehow defaulting to 576cvbs whereas we would want it to default to 1080p60hz? What is generating resolution.ini and how can it be made to default to kernel_hdmimode=1080p60hz instead of 576i50hz?

NOTE: In the old LibreELEC with kernel 3.x (where it is working well), I had no custom resolution configured in config.ini but boot.ini conatined this block:

setenv bootrootfs "BOOT_IMAGE=kernel.img boot=UUID=0405-0637 disk=UUID=077f0773-4d14-47dd-9c5c-d73a1134aa1c"
setenv condev "ttyS0,115200"
setenv hdmimode "1080p60hz"
setenv hdmioutput   "1"
setenv vpu          "1"
setenv libreelec "quiet"
setenv hdmi_cec "1"
setenv uenv_addr 0x13000000

fatload mmc 0:1 ${loadaddr} kernel.img
fatload mmc 0:1 ${dtb_mem_addr} dtb.img

if fatload mmc 0:1 ${uenv_addr} config.ini; then env import -t ${uenv_addr} $filesize; fi

setenv libretech "no_console_suspend logo=osd1,loaded,0x3f800000,${hdmimode} vout=${hdmimode},enable hdmimode=${hdmimode} cvbsmode=nocvbs consoleblank=0"
if test "${hdmi_cec}" = "1"; then setenv cec "hdmitx=cec17"; fi
setenv bootargs "console=${condev} ${bootrootfs} ${libretech} ${cec} ${libreelec}"

So would we need vout=576cvbs hdmimode=1080p60hz,enable cvbsmode=nocvbs to make it work? How to achieve that?

I have the growing suspicion that config.ini is entirely ignored.

For comparison, LibreELEC-AMLGX.arm-11.0-nightly-20220918-bb49fdc-box.img.gz does not have this issue.

Compare to LE is useless as it’s complete different system.

Solution: boot CE device once with TV powered before CE device so it can read the EDID of the TV.
Than use suspend, not power off.
Always ensure TV is powered before CE device as otherwise how the CE device should know what resolutions it will support? Some TV report EDID also when powered off, some not.

You can try to dump your disp_cap so the CE device use this dumped data on boot. Please use forum search to get more information about it.

1 Like

I need a solution that allows me to have the TV switch on the CoreELEC device, because I power my CoreELEC device from the USB port of the TV. This way I conserve power with minimal hassle, but it means that the TV and the CoreELEC device get powered on approximately at the same time.

So I am looking for a way to change the default from SD to FullHD.

Compare to LE is useless as it’s complete different system.

I just mentioned it to clarify that the hardware is capable of it.

And the solution was given to you, have you tried it?