Posts by Da Flex

Quote from soder10

Rpi5 2 GB version has garbled UI output with this release.

Yep, and it was already fixed in nightly builds:

Thread

[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:

1. Flashing microSD card with Raspberry Pi Imager(on mac) or LibreELEC USB-SD Creator(on Windows).
2. Plugging pi 5 to external monitor(with HDMI0), placing microSD card and power cable.
3. Waiting to finish resizing a volume with automatic rebooting after 15 secs.
4. See not fully rendered screen.

…

stalko

August 28, 2024 at 8:15 PM

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:

2024-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 1

After that the correct driver gets loaded in both logs:

2024-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 0

Maybe it's worth to blacklist the iHD driver.

Quote from marialovesmatcha

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>
reboot

Use LE 12 nightly instead.

Thread

[RPi4] Multiple CEC Adapters with LE 12.0.1

I'm looking for some CEC related help.
Ever since upgrading to 12.0.1, I have two CEC adopters in the Input > Peripherials menu, and they just don't co-oporate. I tried disable on of them in the menu, reboot and both are back active. How can I disable one of them?

silentsound

August 29, 2024 at 4:00 PM

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?

Quote from thestraycat

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.

naderforte No more double posts please.

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:

Wifi driver unstable, brcmf_sdio_txfail: sdio error · Issue #152 · raspberrypi/Raspberry-Pi-OS-64bit

Sometimes 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:

Post

RE: SSD playback issue

Ok, seems to be solved, I don't know how to mark this as such.

Under Settings/Services/Caching, changed to buffer all filesystems, including local. Changed the memory to 1GB and left the other settings alone (system has 16GB of ram)

When starting playback the timeline bar on the bottom of the screen fills up rapidly to about 1/4 of the way or so, I'm assuming it's the cache filling up.

Anyhow, yes, playback is very smooth now. I'm assuming the SSD was reading too fast for correct audio/video sync…

ddw867

August 25, 2024 at 9:46 PM

Quote from picslover

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:

• install LE 12.0.1 Generic
• replicate the issue
• restart until LE boots successfully
• login by SSH
• cd .kodi/temp
• cat kodi.old.log | pastebinit
• post the resulting URL