I’m sorry, I didn’t mean to make it difficult.
I’ll try it in about 3 hours.
It began to reboot cyclically after coreelec was loaded. I even showed the main menu once, but went into a reboot. I wrote everything over to the flash drive, the memory partitioning (initial separation) is successful, then cyclic reboots until the Kodi menu appears.
Additionally: I noticed that a picture with artifacts began to appear before coreelec loaded for a fraction of a second (nothing dangerous, it also appears on the neighboring console with s905w2. And everything works fine there). I’m just writing a difference that I noticed. I’ll attach a similar image below, but it’s unlikely to be related to reboots, just for understanding the picture.
AI suggests that this may be related to:
reserved-memory {
In the 2GB version (dts files. are posted above):
linux,ion-dev {
compatible = "shared-dma-pool";
reusable;
size = <0x0 0x5c00000>;
alignment = <0x0 0x400000>;
phandle = <0x4b>;
};
And in the 1Gb version:
linux,ion-dev {
compatible = "shared-dma-pool";
reusable;
size = <0x0 0x0>;
alignment = <0x0 0x400000>;
phandle = <0x4b>;
};
But I haven’t looked at the dtb yet…
Don’t copy paste AI discussion but only final result when you succeed.
Don’t you think we already know things like this?
We need a dmesg to be able to finally implement it.
I’m sorry, I’m just using all the available tools to solve the problem and sharing my thoughts with you…
Changing the dtb to this parameter did not help…
Please tell me how else I can do this. Coreelec is rebooting cyclically, and I can’t connect via ssh…
By UART, read forum.
We do not have such 1gb device so we can not test it by ourself.
Unfortunately, I’m not technically savvy enough for UART.
Okay, I’ll try to work with what I have, and maybe I’ll get something working.
In any case, thank you, Portisch and vpeter, for your help, and for Coreelec in general.
Make two CE USB Sticks. On the first CE USB Stick put the DTB that works to boot Kodi. On the Second CE USB Stick put the experimental DTB with changes for video playback.
Plug in the experimental CE USB Stick and boot. As soon CE crashes/reboots, QUICKLY switch USB sticks. When the stable CE USB Stick boots get this log
CoreELEC:~ # cat /sys/fs/pstore/dmesg-ramoops-0 | paste
That is the dmesg log from the previous boot that is held in RAM after a system crash/reboot. Don’t unplug power, or RAM and log is cleared.
Is it possible to install it in the internal memory if it’s already installed in the internal memory?
So, first I’ll run it from a flash drive with a non-working dtb, and then, after rebooting, I’ll quickly remove the flash drive so that it can boot from the internal memory. Then, I’ll run the following command:
cat /sys/fs/pstore/dmesg-ramoops-0 | paste
Okay, I’ll try it tomorrow.
If you already have CE on the eMMC, and USB booting still has priority over eMMC boot, then I guess that’s fine. Try it.
It probably worked.
Linux version 5.15.153
You always need to be on latest nightly for such support!
It looks like the latest version of coreelec, obtained from here:
I’ve downloaded it again, installed it on a clean flash drive, and added the latest dtb:
https://paste.coreelec.org/EnglandKamal
But it doesn’t seem to have made any difference…
Install the latest nightly from here
I tried it, but there were no changes.
It was the same cyclic reboot…
Soft rendering of videos (using the CPU) works well.
I haven’t been able to launch hard rendering yet. However, I have achieved that when I launch TV/video, the system doesn’t freeze completely, but tries to launch it, even though it used to freeze…
I’ll leave the last workers (soft render) here for now.
work6.dtb.img (70.6 KB)
work1.6.dtb.img (70.6 KB)
As you never enabled tmate as requested and we don’t have such device we will never be able to finish such implementation.