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 kodiDo 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:dThen 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:DThen 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.
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.
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).
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
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 GBSo "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 stableIs this on your original problematic pi, or the borrowed pi?
Can you ssh in on 10.0.3 and capture debug logs?
I can try to boot it up with Ubuntu if you like.
Ah - the link was labelled "Ubuntu pastebin" which I assumed you had named as a failed dmesg from an Ubuntu log.
But I see now that was just a default label as the paste site was hosted by Ubuntu. Don't worry about the Ubuntu boot.
A swap test will be more useful.
that exists log is here: Ubuntu Pastebin
More words would be useful. Can you confirm that you installed Ubuntu on your pi that has problems with libreelec,
and it produces that error in dmesg?
To rule out any impact from connected devices, can you boot the pi with as little as possible connected (no usb devices, no hat, no hdmi).
Just Pi, power and ethernet (so you can ssh in and get dmesg log). Does the dmesg have that error in? If so I'd say it's a hardware problem with that pi.
Doing a swap test (with a different pi4) could also confirm this.
Leave config.txt unchanged.
Try adding to cmdline.txt (end of existing line)
video=HDMI-A-1:1920x1080@60D(assuming your display supports 1080p60).
Make sure you use the first hdmi port (closest to power socket).
Would the output from dmesg show any instance of an under voltage condition.
Ideally it should. But the log shows:
Feb 02 15:29:50 LibreELEC kernel: Firmware transaction timeoutwhich means firmware isn't responding to requests (it has likely crashed).
And as the firmware checks for under-voltage, it may be impossible to get that information into kernel log.
Can you post output of "vcgencmd log msg" (e.g. piped through paste if that working).
Can you confirm you have no custom settings (like overclock) in config.txt?
If you have access to another pi4, then trying it with your sdcard, power supply etc may be useful.
I'd also be interested if RPiOS works correctly? It could be a hardware issue, but I'd expect that to affect other distributions.
Are you connected to the denon amp through HDMI?
The source (Pi) will read the EDID from the sink (display or AVR) and that will include audio capabilities.
A faulty HDMI cable may make it impossible to read the edid.
ssh in and run:
edid-decode /sys/devices/platform/gpu/drm/card?/card?-HDMI-A-1/edidand you should find an "Audio Data Block" describing the capabilities.