edit: not that important at all…
And you can discuss that elsewhere. I won’t warn you again.
Why not just keep using the 32 G drive,which is snappier/no issues etc..
Map the SSD drive to your network for SMB share
Or use SSD in the other port for playback of your media…
If it ain’t broke/ don’t fix it
Happy Testing
But it’s broken… And I have no interest in using a USB flash drive that overheats and fails after a few months. I have other devices—like the Ugoos AM6B Plus—where the SSD runs normally and at good speeds. And now, on version NG 21.3, the SSD works fine on the Homatics R 4K Plus too; it only fails to work on version NO 22 Beta1. Why even give an answer like that if you don’t have a tip on how to fix it???
When CE crashes and reboots back into CE, you can grab the previous boot’s dmesg to find the reason for the crash
CoreELEC:~ # cat /sys/fs/pstore/dmesg-ramoops-0 | paste
There may be more than one problem causing the reboots, having the crash log would help a lot in explaining the reason for the crash.
Because you posted the 32 gig worked fine/snappier/no issues CeC/Boot.
That’s why.
As soon as it crashes, I’ll send the SSH log right away. Thank you very much.
By the way, I thoroughly tested NG 21.3 with dovi.ko, and everything is working without issues. We can rule out a faulty SSD as the cause of the problems.
Is it better to use Beta or Nightly versions, where a fix might be available?
Always use latest nightly when trying to diagnose a problem.
It looks like an issue with dovi.ko (latest fix fel).
Homatics Box R 4K Plus, CoreELEC 22 Beta1, kernel 5.15.196. I installed 5.15_2.6_dovi_patched_fix_fel.ko. During Dolby Vision P7 FEL playback with TrueHD, the audio started stuttering and the box rebooted. Pstore shows a kernel panic in Commit2DmKs inside dovi_gen_5_15_2026.
Redacted pstore log: https://paste.coreelec.org/ClaraEchoes
I’m currently testing the latest nightly build: Amlogic-no/CE-22/20260730/. If it crashes, I’ll send another crash report.
Random reboots during DV FEL playback is a known issue reported by others in the DV FEL NO thread.
<4>[ 261.611845] stack-protector: Kernel stack is corrupted in: Commit2DmKs+0xd10/0xd14 [dovi_gen_5_15_2026]
<4>[ 261.611917] Unexpected kernel BRK exception at EL1
Does the DV FEL crash happen repeatedly and consistently at the same time point in that video, or is it more random?
This DV FEL issue only affects DV FEL playback. It wouldn’t cause the other random boots during bootup that you described earlier. That more than likely has a different cause.
The crashes during DV FEL 7 are random. However, I’ve just gone about half an hour without a crash or freeze. Could the latest nightly build have fixed it? I don’t want to jump to conclusions, though—it might still crash later.
As you and others have reported, the DV FEL crashes are random. A crash may not happen for a very long time. It’s probably an issue with the dovi module, not any specific nightly. It’s a closed module, hard to debug. Maybe someone in the CE community will figure out a fix.
During boot, dmesg shows:
dovi_gen_5_15_2026: disagrees about version of symbol module_layout
please rebuild ko: dovi_gen_5_15_2026
dovi_gen_5_15_2026: module license 'AML' taints kernel.
dovi_gen_5_15_2026: disagrees about version of symbol __stack_chk_fail
please rebuild ko: dovi_gen_5_15_2026
The module still loads and initializes:
dovi_gen_5_15_2026 585728 0
[dovi_gen_5_15_2026]: *** amlogic_dolby_vision_init dv: s6 ***
[dovi_gen_5_15_2026]: Creating DV mp success
However, the module was apparently built for kernel 5.15.170, while the current nightly uses 5.15.196.
Is this mismatch expected with the currently recommended patched FEL module, or is there a newer dovi.ko compatible with the current 5.15.196 kernel?
Could the module_layout and __stack_chk_fail mismatches cause kernel panics during FEL playback, seeking, or Dolby Vision mode changes?
All that output (including version) is expected and unrelated to the dv fel crashes.
Thank you very much for your help, sir. So, is it better to stay on NG 21.3 until the dovi.ko module is fine-tuned?
Hi everyone.
I’m on Homatics Box R 4k Plus version v14.8.7475 and I’m trying to install/boot into CoreELEC to play some huge (and DV 7.5/6) remuxes I have without stuttering via Plex.
I’ve tried to follow the instructions here: discourse .coreelec .org/t/guide-homatics-box-r-4k-plus-coreelec-installation-configuration-and-modding/28659 without success (it also links to the 20.5 AARCH images instead of ARM).
Next thing I did was to Google and found these two guides: reddit .com/r/Homatics/comments/1qkrd6h/homatics_box_r_4k_plus_coreelec_kodi_setup_problem/
wiki. coreelec .org/coreelec:homatics
On the Reddit one, a user said the main article image was wrong and suggested to use the CoreELEC-Amlogic-ng.arm-21.3-Omega-Generic.img.gz from the Github, I’ve tried it too without success.
My device just don’t boot to CoreELEC. Reset button method doesn’t work, it loads the recovery options only. Also found an APK to boot to CoreELEC directly from ATV, but it just boots up again to ATV.
My pendrive for some reason don’t load on USB3.0 port, only 2.0.
I’ve used Rufus to load the image into it (the one linked above from github), copied the file sc2_s905x4_sei_smb_280.dtb file to COREELEC root and rename it dtb.img
Can someone help me pointing what I’m doing wrong?
Also, I’ve found some info about “dovi.ko”, where can I get it to play the DV files?
Thanks a lot in advance.
Try CE22