Posts by popcornmix

Post current contents of /flash/config.txt and /flash/cmdline.txt

The obvious error in your log is:

апр 11 19:28:42 server kernel: [drm:vc4_bo_create] *ERROR* Failed to allocate from CMA

and the related:

апр 11 19:28:36 LibreELEC kernel: cma: Failed to reserve 256 MiB
апр 11 19:28:36 LibreELEC kernel: Kernel command line: coherent_pool=1M 8250.nr_uarts=0 cma=64M cma=256M video=HDMI-A-1:1360x768M@60 smsc95xx.macaddr=E4:5F:01:81:78:7D vc_mem.mem_base=0xec00000 vc_mem.mem_size=0x10000000  boot=UUID=0607-1118 disk=UUID=dcad1c13-ae95-4d08-935d-befe971ffab6 quiet root=/dev/ram0 rdinit=/init usbcore.autosuspend=-1

Now, kodi 18 was awkward on Pi4, as gpu_mem is used for 3d textures, and cma is used for hevc decode,
and it's a bit of a juggling act to get both memory pools to be happy. In your case it's not happy.

Kodi 19 uses kms, and 3d textures move from gpu_mem top cma, which makes like much better.
Leave gpu_mem as a default, then you can give a decent chunk (e.g. 512M) to cma and everything is happy.

You can continue juggling with gpu_mem and cma settings on kodi 18, and you may get a satisfactory balance.

But moving to Kodi 19 is likely to just avoid this issue completely.

Have you enabled "Adjust display refresh rate" in settings/videos?

Not having that enabled is the main reason for judder.

I also run with all TV motion smoothing settings off and everything is perfectly smooth.

The cmdline.txt settings for video are just standard linux, not pi specific. See here:

modedb default video mode support — The Linux Kernel documentation

or

Kernel mode setting - ArchWiki

Quote from pitri

I am starting to think it can be caused by some physical default on the board and I don't like the idea as they are out of stock evrywhere at that moment

If you plug in to display and power on a Pi4 with no sdcard inserted you should see a diagnostic display. Does that work?

That will help confirm if there is a physical defect.

LE 9 is very old, and won't get any any fixes. Try updating to Matrix.

Does unplugging/replugging hdmi cable fix the blank screen?

Normally GUI only appearing in a quarter of display is some mixup in guisettings.xml.

Can you try (ssh in):

systemctl stop kodi
mv /storage/.kodi /storage/.kodi_back
systemctl start kodi

Do you now have kodi working with full screen 4k display?

If it doesn't help you can move the .kodi directory back.

LE 10 / Kodi Matrix has moved from firmware display driver (fkms - controlled with config.txt) to a standard kernel display driver (kms controlled with cmdline.txt).

I think what you are asking to do is to have both hdmi ports connected, but be able to switch which one is disabled.

Have a look here.

I think if you add to cmdline.txt (end of existing line):

video=HDMI-A-1:D video=HDMI-A-2:d

Then the first hdmi port will be enabled, and the second will be disabled. If instead you do:

video=HDMI-A-1:d video=HDMI-A-2:D

Then the first hdmi port will be disabled, and the second will be enabled.

Note that CEC only works (with LE) on the first hdmi port, so if you use that with one display, then make sure it is first.

Quote from twilightened

I did try this. However, after experiencing performance problems, especially on live streams, i had to delete the edid file. So i think it is safe to say that it affects some other aspects of the system that i do not know of.

It's extremely unlikely that using the edid file is the cause of live streaming issues.

Quote from nikstra

As I mentioned in the first post, RPiOS boots fine. I'll install Kodi on it and we'll see what happens.

What info and/or logs should I provide other than kodi.log?

I don't think logs will show this. The display gets into a bad state with a valid hdmi signal (that it is happy with after switching inputs).

Learning what conditions cause the bad state is the useful information we want.

LE includes disable_fw_kms_setup=1 in config.txt - might be worth adding that to RPiOS.

Also make sure RPiOS runs in the same hdmi resolution as you get with LE (I think 1080p60).

You can choose that with the display configuration app.

If you have a spare sdcard then installing RPiOS would be interesting.

My guess would be that if RPiOS boots with a working display then kodi will work okay when launched.

But RPiOS may have the same issue when booting (and probably will be fixed with the addition of the hdmi_group/hdmi_mode lines).

At the moment any information is useful.

Your splitter is the problem (it is masking the audio capabilities).

But you should be able to workaround it.

Capture the correct edid (when it is just connected to the AVR) with getedid.

You should then be able to plug in the projector and still have LE see the good edid in the future.

(The captured edid will survive reboots).

Quote from nikstra

ILooking at the output of edidparser http://ix.io/4ki4 it seems like 1080p@60 should work

HDMI:EDID found CEA format: code 16, 1920x1080p @ 60Hz (native)

I think the linked thread suggests some monitors don't like the switch from the firmware driving a mode (e.g. 1080p60) to the kernel driving the *same* mode - even though the monitor is happy with how each mode is driven separately.

The workaround is to make the firmware choose a different mode for the first stage of booting, which seems to allow the kernel to drive the original mode (e.g. 1080p60) happily.

You should find kodi is still using the preferred mode (1080p60). If it's not I suspect you can switch to it in settings.

Perhaps try the suggestion here: RE: LE 10.0.1 / Rpi4 / No picture after update from LE 10.0.0

Quote from @fterlife

I tried many things but I can't get any debug info for some reason even via SSH.

Could you connect through ssh? What commands did you try running and how did they fail?

So everything works now? Do you still have the "firmware transaction" error in dmesg log on either original or borrowed board?

I've read you post several times but I'm still confused what does and doesn't work.

I could borrow a Pi 4B 4GB, it is around the same age.
Same SD-Card, connected by HDMI to be HP Screen:
LibreElec runs on my  Pi 4B 8 GBLibreElec runs on the Pi 4B 4 GB

So "my Pi 4B 8 GB" is the Pi you have been testing throughout this thread. Which I thought hung on splash screen.

Are you stating LibreElec runs (i.e. works normally) on this Pi?

Is everything the same in the tests of the two pi (as well as sdcard, the power supply, cables, display, peripherals)?

It sounds like you changed hdmi resolution (looks like to 1280x720 sbs @ 50Hz). Note that sbs is a 3d mode and probably shouldn't be used as default.

TV is showing Kodi  even after booting it again and again, so it is stable

Is this on your original problematic pi, or the borrowed pi?