CoreELEC 19.4-Matrix_rc2 Discussion

kszaq · 17 January 2022 18:42

@Djon When it freezes, are you able to collect dmesg ? Does it print something like below over and over again?

[94826.127648@2]- audio_ddr_mngr: frddrs[0] registered by device ff660000.audiobus:tdm@1
[94826.131422@2]- tdm playback mute: 1, lane_cnt = 8
[94826.135310@2]- audio_ddr_mngr: frddrs[0] released by device ff660000.audiobus:tdm@1
[94826.144226@1]- audio_ddr_mngr: frddrs[0] registered by device ff660000.audiobus:tdm@1
[94826.151659@1]- tdm playback mute: 1, lane_cnt = 8
[94826.155317@1]- audio_ddr_mngr: frddrs[0] released by device ff660000.audiobus:tdm@1
[94826.164189@0]- audio_ddr_mngr: frddrs[1] registered by device ff660000.audiobus:i2s2hdmi
[94826.171494@0]- tdm playback mute: 1, lane_cnt = 4
[94826.175629@0]- audio_ddr_mngr: frddrs[1] released by device ff660000.audiobus:i2s2hdmi
[94826.185402@3]- audio_ddr_mngr: frddrs[1] registered by device ff660000.audiobus:i2s2hdmi
[94826.192371@3]- tdm playback mute: 1, lane_cnt = 4
[94826.196458@2]- audio_ddr_mngr: frddrs[1] released by device ff660000.audiobus:i2s2hdmi
[94826.206136@2]- audio_ddr_mngr: frddrs[1] registered by device ff660000.audiobus:i2s2hdmi
[94826.212830@2]- tdm playback mute: 1, lane_cnt = 4
[94826.216835@2]- audio_ddr_mngr: frddrs[1] released by device ff660000.audiobus:i2s2hdmi
[94826.251441@2]- audio_ddr_mngr: frddrs[0] registered by device ff660000.audiobus:tdm@1
[94826.255441@2]- tdm playback mute: 1, lane_cnt = 8
[94826.258692@2]- audio_ddr_mngr: frddrs[0] released by device ff660000.audiobus:tdm@1
[94826.268121@2]- audio_ddr_mngr: frddrs[1] registered by device ff660000.audiobus:i2s2hdmi
[94826.275942@2]- tdm playback mute: 1, lane_cnt = 4
[94826.279031@2]- audio_ddr_mngr: frddrs[1] released by device ff660000.audiobus:i2s2hdmi
[94826.288640@2]- audio_ddr_mngr: frddrs[1] registered by device ff660000.audiobus:spdif@0
[94826.295833@2]- spdif_a keep clk continuous
[94826.299036@2]- audio_ddr_mngr: frddrs[1] released by device ff660000.audiobus:spdif@0
[94826.307686@0]- audio_ddr_mngr: frddrs[1] registered by device ff660000.audiobus:spdif@1
[94826.315898@0]- spdif_b keep clk continuous
[94826.318732@0]- audio_ddr_mngr: frddrs[1] released by device ff660000.audiobus:spdif@1
[94826.336072@3]- audio_dsp: buf=0
[94826.336124@3]- audio_dsp: IEC958_mode_raw=0
[94826.346373@1]- audio_ddr_mngr: frddrs[1] registered by device ff660000.audiobus:i2s2hdmi
[94826.352188@1]- set mclk:11289600, mpll:22579200, get mclk:11289593, mpll:22579186
[94826.356395@1]- asoc aml_dai_set_tdm_fmt, 0x4001, 000000005d527d6e, id(2), clksel(2)
[94826.364205@1]- aml_tdm_set_fmt(), fmt not change
[94826.368632@1]- dump_pcm_setting(000000005d527d6e)
[94826.373271@1]-       pcm_mode(1)
[94826.375982@1]-       sysclk(11289600)
[94826.379222@1]-       sysclk_bclk_ratio(4)
[94826.382779@1]-       bclk(2822400)
[94826.385715@1]-       bclk_lrclk_ratio(64)
[94826.389312@1]-       lrclk(44100)
[94826.392100@1]-       tx_mask(0x3)
[94826.395163@1]-       rx_mask(0x3)
[94826.397867@1]-       slots(2)
[94826.400335@1]-       slot_width(32)
[94826.403405@1]-       lane_mask_in(0x0)
[94826.406693@1]-       lane_mask_out(0xf)
[94826.410072@1]-       lane_oe_mask_in(0x0)
[94826.413632@1]-       lane_oe_mask_out(0x0)
[94826.417264@1]-       lane_lb_mask_in(0x0)
[94826.420795@1]- set mclk:11289600, mpll:22579200, get mclk:11289593, mpll:22579186
[94826.428517@1]- aml_tdm_set_clkdiv, div 4, clksel(2)
[94826.433160@1]- aml_set_bclk_ratio, select I2S mode
[94826.437925@1]- aml_tdm_hw_setting_init(), enable mclk for tdm-2
[94826.443961@1]- aml_tdm_prepare(), reset fddr
[94826.448346@1]- tdm playback mute: 0, lane_cnt = 4
[94826.452961@1]- aml_tdm_prepare(), reset fddr
[94826.457322@1]- tdm playback mute: 0, lane_cnt = 4
[94826.462832@1]- aml_tdm_hw_setting_free(), disable mclk for tdm-2
[94826.467503@1]- tdm playback mute: 1, lane_cnt = 4
[94826.472264@1]- audio_ddr_mngr: frddrs[1] released by device ff660000.audiobus:i2s2hdmi

loznic89 · 17 January 2022 19:10

same problem and errors in log. odroid N2 with clean install

vpeter · 17 January 2022 19:13

Then there are 2 different issues. Because Djon wrote in other thread

kszaq · 18 January 2022 16:48

@loznic89 Do you have HDMI multichannel selected as audio output? A workaround that so far worked for me: change output device to “ALSA: Default”.

At the same time, I cannot confirm if “HDMI multi ch” caused the issue as I was not able to reproduce it.

loznic89 · 18 January 2022 20:01

hi kszaq, yes default come “multich” i am trying with alsa default and audio its ok too.

but 1080p content is not played. i am using tvheadend client and kodi library. only working 2160p video content.

http://ix.io/3MHO

boot2k3 · 19 January 2022 10:59

A post was merged into an existing topic: Nightly builds (NEW)

malibu46 · 20 January 2022 09:46

I am very new to CoreElec and have a Beelink King GT with an SD Boot carrying 9.2.8 is there any way i can change this to 19.4 Matrix? Apologies if this is the incorrect thread to use

Garcea · 20 January 2022 10:20

wiki Its better to make a fresh install and redeploy all your addons. You could try to upgrade also directly but could be painful if you have some addons who weren’t ported to pyton3 (perform a full backup of CE and Kodi settings and try to restore them on the new installation of CE-19.rc1).

Motoviper · 20 January 2022 23:24

Currently Running Coreelec 19.4-Matrix_rc1 from SD Card on Tanix Tx3-Mini 2g(905W)

I have tried to upgrade to rc2 and several nightlies using the new kernel 4.9.269 and everytime I get a
“Could not mount LABEL=COREELEC” on boot.

I downgrade back to any old kernel(kernal.img and system files) and it immediately boots perfectly.

vpeter · 21 January 2022 06:57

Can you run this commands in SSH console on rc1 where system boots? It should fix the boot label. After that reboot and then update to rc2.


minix_u22xj_max: # megadl https://mega.nz/file/fEx2nTpa#ar4WSezpJvxQXGy-fwbV8jQ4M5z3M09K-IdFGGVKRos
Downloaded fatlabel_rc2

minix_u22xj_max: # chmod 755 fatlabel_rc2

minix_u22xj_max: # ls -l /dev/disk/by-label/COREELEC
lrwxrwxrwx    1 root     root            15 Jan 21 07:53 /dev/disk/by-label/COREELEC -> ../../mmcblk1p1

minix_u22xj_max: # ./fatlabel_rc2 /dev/disk/by-label/COREELEC COREELEC
minix_u22xj_max: # ./fatlabel_rc2 /dev/disk/by-label/COREELEC
COREELEC

Just to be clear: You only replace kerrnel.img and SYSTEM file and it boots?

Motoviper · 21 January 2022 15:39

Correct.

I ran the commands, rebooted in RC1, updated to RC2 and still will not boot:(exact same error on boot)
"### Starting debugging shell for boot step: mount_flash… type exit to quit ***
***Error in mount_flash: mount_common: Could not mount LABEL=COREELEC ***

I am now back on RC1 (copied kernal.img and system)

Also I have never tried to flash internal and have the internal OS still with the original Tanix TX3 mini image.

vpeter · 21 January 2022 16:03

I don’t understand what is going on here

On RC1 can you dump whole flash partition and upload file flash.gz to somewhere online? This would help very much!

dd if=/dev/disk/by-label/COREELEC | gzip -c >flash.gz

Motoviper · 21 January 2022 20:59

Done:
https://www.dropbox.com/s/pcfdhxs7dvuvfxf/flash.gz?dl=0

vpeter · 22 January 2022 08:41

This flash partition is fine and I can mount it on rc2 on my device.

Could you make one fresh SD card or USB stick with RC2 and see if it boots or not on your device? If it doesn’t then boot with RC1 and update to RC2. When it doesn’t boot you get the message you wrote and then you get into shell. Attach USB keyboard and type dmesg. Make a picture what you get and post it.

oastra · 22 January 2022 10:32

I have an issue with RC2 playing interlace content (1080i) at X2 Boxes
When I play the content and skip forward or back it is a 2 sec fullscreen clear Picture with random colors
I made a clean install on a SD Card and its the same

I test it on 3 X2 Boxes:
Vosen V1 X2
Bqeel y5 X2
H96 Max X2

Whith a X3 (X96 Max+) and a 922X (Orbsmart S86) Box there is no problem

So I have only problems on X2 Boxes with Interlace content on RC2

With RC1 everything is fine

is it possible, there is a problem with the Kernel update on X2 boxes ?

malibu46 · 22 January 2022 11:26

Did you manage to get 19.3 to work on Beelink King GT Pro and does it load from AN SD Card . Is there a straight copy to flash. I am new to this and would welcome some help. Thanks

Motoviper · 22 January 2022 16:53

Fresh install of RC2 on SD Card–Same exact result(no boot) with message. I ran the Dmesg and don’t know how to save the whole long result, but here is the end with the error mount messages. Will this be what you are looking for?

vpeter · 22 January 2022 16:59

Yes, this is perfect!
You boot from USB or SD card? And do you have any other USB sticks attached on booting?
If I’m correct you are using Realtek Wifi stick? Can you try to boot without it?

Motoviper · 22 January 2022 17:44

SD Card. Yes I saw the USB messages and removed it, (it is the Wifi module that initially gets identified as a storage device). Made no difference other than the dmesg messages were gone for the realtek device.

vpeter · 22 January 2022 17:54

Did you tried to boot RC2 from USB stick?

Also which Android version is on device?