Is there any way to capture a manual log? Or does the fact that no log is created mean that LE doesn't even manage to start...
kodi.old.log shows a successful boot sequence, so it's not helpful. Maybe a broken hardware part, which can't be initialized at boot sometimes. Hardware boot sequences are complex, so random results are possible.
You can search for dead hardware parts after successful boot (internal WiFi, Bluetooth etc.). I don't think it's an LE problem.
imforumman Our nightly builds run pretty stable. You can go back to 12.0.1, if needed. No ETA for 12.0.2. From SSH:
cd /storage/.update
wget <URL_OF_LE_12.SUB-VERSION.IMG.GZ>
rebootUse LE 12 nightly instead.
I guess the video is encoded wrongly:
2024-09-13 22:22:02.161 T:1038 error <general>: CDVDVideoCodecDRMPRIME::FilterOpen - avfilter_graph_config: Invalid argument (-22)Disable DRM Prime, or encode the video correctly.
Do you use Settings->Services->Caching or advancedsettings.xml?
So is it safe to say, For Dolby Vision support (on a DoVi supported Amlogic platform) CoreElec is my best bet for the foreseeable future?
Yes, because LE uses mainline Linux.
Check your HDD for errors.
Sep 12 18:54:49.042450 LibreELEC udevil[883]: udevil: error 105: mkdir '/media/Új kötet' failed
Sep 12 18:54:49.057068 LibreELEC udevil[872]: Mounted /dev/nvme0n1p1 at /media/nvme0n1p1-nvme-Patriot_M.2_P30
Sep 12 18:54:49.081919 LibreELEC kernel: ntfs3: nvme0n1p5: It is recommened to use chkdsk.
Sep 12 18:54:49.081963 LibreELEC kernel: ntfs3: nvme0n1p3: It is recommened to use chkdsk.
Sep 12 18:54:49.081992 LibreELEC kernel: ntfs3: nvme0n1p3: volume is dirty and "force" flag is not set!
Sep 12 18:54:49.082020 LibreELEC kernel: ntfs3: nvme0n1p5: volume is dirty and "force" flag is not set!
Sep 12 18:54:49.082102 LibreELEC udevil[1105]: mount: /var/media/Új kötet: wrong fs type, bad option, bad superblock on /dev/nvme0n1p5, missing codepage or helper program, or other error.I guess it's a firmware bug:
Play with cache settings:
I am not sure the cable version, the TV is old so I assume it HDMI v1.4, Any way to verify the version of a cable?
Check online order histories and invoices.
Background: Fixed sampling rate means reduced data rate over HDMI. If your cable is HDMI 1.4, then you don't get the shielding of HDMI 2.0 / 2.1, which can result in data loss (A/V loss).
It could also be the specs of your TV. If it has HD Ready (720p) resolution, and can only play 44.1kHz audio, then everything works as expected. In that case you don't need an HDMI 2.0 / 2.1 (4K) cable.
picslover Which HDMI standard have your HDMI cables? We suggest HDMI 2.0 or 2.1.
Workflow for kodi.old.log:
I think you're right, and the boot error isn't in the log. I thought I could find something in the log, but I guess what I found is not the real problem.
So when LE boots, then the log with the boot error is at kodi.old.log. Post that one.
I think it's a RAM / cache size error, maybe triggered by large Google Drive cache:
2024-09-08 12:15:40.746 T:998 debug <general>: CGLContextEGL::SwapBuffers: sync check blocking
2024-09-08 12:15:40.758 T:998 debug <general>: CGLContextEGL::SwapBuffers: sync sleep: 11686<cache>
<buffermode>2</buffermode>
<freememorycachepercent>5</freememorycachepercent>
<memorysize>99145600</memorysize>
<readfactor>30.0</readfactor>
</cache>Dolby Vision (DV) needs a payed license per device. Devices with Linux support and DV license are super rare. That's why we don't support DV, and don't have a roadmap for it.
Pro tip: Search for "Dolby Vision" (magnifier icon) at the LE main page. This question was answered several times.
No.
Add the code at the end of the last (run section) APPEND line, right behind "quiet", only separated by a space sign.
Multiple APPEND lines are not allowed inside of one section.