After booting, login by SSH, run getedid create, and reboot.
Posts by Da Flex
-
-
Im happy so far with the 8.2.5, but would have been good to know why the 12.0.1 struggles?
with struggle I mean its choppy and jerky playback, sound is fine.
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Rpi5 2 GB version has garbled UI output with this release.
Yep, and it was already fixed in nightly builds:
[RPi5 2GB] Not Rendering LE 12.0.1
With the keyboard I can navigate somewhere, by guessing how the interface will look like. But there was no chance to connect this thing to the network for debugging.How to reproduce
Steps to reproduce the behavior:- Flashing microSD card with Raspberry Pi Imager(on mac) or LibreELEC USB-SD Creator(on Windows).
- Plugging pi 5 to external monitor(with HDMI0), placing microSD card and power cable.
- Waiting to finish resizing a volume with automatic rebooting after 15 secs.
- See not fully rendered screen.
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
chulygun Yes, that's the suggested workflow.
-
It must be an error in the Linux kernel, before LE starts logging.
The kodi.old.log has this part, which isn't at kodi.log:
Code2024-09-14 07:15:26.343 T:975 debug <general>: libva info: VA-API version 1.20.0 2024-09-14 07:15:26.343 T:975 debug <general>: libva info: Trying to open /usr/lib/dri/iHD_drv_video.so 2024-09-14 07:15:26.343 T:975 debug <general>: libva info: Found init function __vaDriverInit_1_20 2024-09-14 07:15:26.343 T:975 error <general>: libva error: /usr/lib/dri/iHD_drv_video.so init failed 2024-09-14 07:15:26.343 T:975 debug <general>: libva info: va_openDriver() returns 1After that the correct driver gets loaded in both logs:
Code2024-09-14 07:15:26.343 T:975 debug <general>: libva info: Trying to open /usr/lib/dri/i965_drv_video.so 2024-09-14 07:15:26.343 T:975 debug <general>: libva info: Found init function __vaDriverInit_1_20 2024-09-14 07:15:26.344 T:975 debug <general>: libva info: va_openDriver() returns 0Maybe it's worth to blacklist the iHD driver.
-
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:
Codecd /storage/.update wget <URL_OF_LE_12.SUB-VERSION.IMG.GZ> reboot -
Use LE 12 nightly instead.
-
I guess the video is encoded wrongly:
Code2024-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.
CodeSep 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. -
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
I guess it's a firmware bug:
Wifi driver unstable, brcmf_sdio_txfail: sdio error · Issue #152 · raspberrypi/Raspberry-Pi-OS-64bitSometimes a crash of Wifi occurr. This problem happens randomly. (I encountered it during the upload from an external drive.) Here the log. [ 3053.918262]…github.com -
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.
