Minix Neo U22-XJ boots into a white noise screen with later nightly builds

Help & Support Installation & Booting
21

Try latest nightly with new dtb g12b_s922x_minix_u22xj_rev_a.dtb.

22

@mr-b please check, if there are same errors of es8316 3-0010 than in your log from yesterday.

24

Ah Ok I thought someone wanted me to try a different DTB.
Yes I posted the log yesterday https://paste.coreelec.org/BanquetOrthodox and saw lots of those lines:

========== journalctl -a -b -0 ==========
Jun 24 10:26:05.418338 CoreELEC kernel: es8316 3-0010: ASoC: error at soc_component_read_no_lock on es8316.3-0010: -6
Jun 24 10:26:05.420243 CoreELEC kernel: es8316 3-0010: ASoC: error at soc_component_read_no_lock on es8316.3-0010: -6
Jun 24 10:26:05.420825 CoreELEC kernel: es8316 3-0010: ASoC: error at soc_component_read_no_lock on es8316.3-0010: -6
Jun 24 10:26:05.421241 CoreELEC kernel: es8316 3-0010: ASoC: error at soc_component_read_no_lock on es8316.3-0010: -6
Jun 24 10:26:05.421656 CoreELEC kernel: es8316 3-0010: ASoC: error at soc_component_read_no_lock on es8316.3-0010: -6
Jun 24 10:26:05.422146 CoreELEC kernel: es8316 3-0010: ASoC: error at soc_component_read_no_lock on es8316.3-0010: -6
Jun 24 10:26:05.422664 CoreELEC kernel: es8316 3-0010: ASoC: error at soc_component_read_no_lock on es8316.3-0010: -6
Jun 24 10:26:05.423079 CoreELEC kernel: es8316 3-0010: ASoC: error at soc_component_read_no_lock on es8316.3-0010: -6
Jun 24 10:26:05.423472 CoreELEC kernel: es8316 3-0010: ASoC: error at soc_component_read_no_lock on es8316.3-0010: -6
Jun 24 10:26:05.423855 CoreELEC kernel: es8316 3-0010: ASoC: error at soc_component_read_no_lock on es8316.3-0010: -6
Jun 24 10:26:05.424959 CoreELEC kernel: es8316 3-0010: ASoC: error at soc_component_read_no_lock on es8316.3-0010: -6
Jun 24 10:26:05.425489 CoreELEC kernel: es8316 3-0010: ASoC: error at soc_component_read_no_lock on es8316.3-0010: -6
Jun 24 10:26:05.425885 CoreELEC kernel: es8316 3-0010: ASoC: error at soc_component_read_no_lock on es8316.3-0010: -6
Jun 24 10:26:05.426264 CoreELEC kernel: es8316 3-0010: ASoC: error at soc_component_read_no_lock on es8316.3-0010: -6

I also saw “Jun 24 10:26:14.192143 CoreELEC kernel: [drm] am_meson_drm_fb_pan_display, skip set_par’s pan display” several times.

25

And latest nightly with new DTB still has es8316 error lines?

Is it really so hard to test before making post?

2 Likes
26

Why you wrote about what we know about old log?

  1. You must install new nightly update and be sure that is used new non max dtb.
  2. And only after you must upload new log.
1 Like
28

You’re making it difficult to help you, everything’s is an argument.

A NEW Minix u22xj REV A dtb (NON-MAX) was added to the June 25th nightly. That’s what you were asked to try.

2 Likes
30

Tx for the clarification.

The new rev A dtb boots fine!

https://paste.coreelec.org/QuotedHunting

Running on Minix U22-XJ with CoreELEC (official): 22.0-Piers_nightly_20250625, kernel: Linux ARM 64-bit version 5.15.153

No error lines like the below visible:
CoreELEC kernel: es8316 3-0010: ASoC: error at soc_component_read_no_lock on es8316.3-0010

In case it’s relevant,
CoreELEC kernel: [drm] am_meson_drm_fb_pan_display, skip set_par’s pan display
appears twice. That line was not present in 21.2.

Good to have confirmation that the wiki instructions that I was following for the U22-XJ model were correct.

I can’t tell from https://archive.coreelec.org/Amlogic-no/CE-22/20250625/changelog-20250625.html who added the rev A dtb to enable this so I can only say tx to whomever concerned!
Happy to supply more logs if req’d, as long as it boots.

31

Have you 1 second noise or not in first part of booting CE?

32

Yes I see a variable half-hearted attempt at a white noise screen after the Minix splash screen and before the CE ‘eclipse’ logo.

The other thing that might be relevant is that when CE boot fails and it boots into Minix Android, after booting back into CE the screen was partly green on media playback. I didn’t notice as I’m colour-blind but the fix was to boot back into Android and disable Dolby Vision as per Minix U22-XJ (Max) - #87 by manggudgee. It’s a bit of a pain. Presumably it must be a Minix default boot setting and one that CE can’t disable.

After boot it also says:
“Android Dolby Vision kernel module is not compatible
No Dolby Vision media playback possible!
Please upgrade Android firmware of your device to minimum Linux kernel version ‘5.15.137’.
Dolby Vision media will be displayed in HDR instead [of?] Dolby Vision until the firmware fulfill (sic) the minimum requirements.”

NEO U22-XJ Official Firmware Releases | MINIX Forum doesn’t list firmware versions in the above format so I’ve just ignored it.

33

Follow these instructions.

1 Like
34

Tx the DV warning message has gone. ChatGPT guided me on how to use File Manager to move the dovi.ko file from a share subfolder into /storage.

35

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.