Based on (limited) information provided I'm guessing your display or HDMI cable is faulty and isn't providing an EDID.
This thread may be helpful:
Posts by popcornmix
-
-
Is there a way to adjust overscan ie. border in the vido output? and the resolution.
The ui works, but the text is a little hard to read.See: https://kodi.wiki/view/Settings/…deo_calibration
Your resolution is fixed when using composite.
The default Estuary skin is optimised for 1080p (you can use it at lower resolutions but you may find the text is small).
You should investigate switching to skin that better supports low resolution screens.
There was a SD/CRT skin
I found, but it may not have been updated beyond Matrix.
But there are many skins. You may find something that works better.
-
First, remove any changes to config.txt and cmdline.txt (note: a # character is not a valid comment character in cmdline.txt).
Run "getedid create". It captures your current edid (which is a broken, zero length one) and modifies http://config.txt/cmdline.txt to use it.
It appears here (with zero length): /storage/.config/firmware/edid/edid-HDMI-A-1.bin
What you can do is replace that file with a valid edid (it won't exactly match your display capabilities, but it may be usable).
Here is a possible edid
Download that and copy it to /storage/.config/firmware/edid/edid-HDMI-A-1.bin
Run "create-edid-cpio" to update the fake edid used to this one.
Now reboot. Do you get video? Can you choose audio output?
-
from cmdline.txt and rebooting and getting a new log file?
If I remove that I don't get a picture anymore, but I can still log in via ssh and get the log file
You can, but I believe the kernel will just choose a default hdmi mode (I have a feeling it was 1024x768 which isn't that widely supported) if hotplug detect is working. If hotplug detect is not working I think you will get no resolutions.
Do you have another TV you can connect to? If that works it rules out the hdmi cable. If it doesn't then the cable is the problem and needs replacing.
If the other TV works and has similar capabilities then you could try capturing its edid and using it with the original TV.
-
Remove
Codehdmi_group=1 hdmi_mode=5from config.txt (they apply to a deprecated driver we don't use).
Remove hdmi_drive=2 from cmdline.txt (they only make sense in config.txt and if you moved them there, they would have no effect as they apply to a deprecated driver we don't use)
This is the key bit from log:
Code2023-07-12 08:05:03.831 T:770 INFO <general>: Found resolution 1280x720 with 1280x720 @ 60.000000 HzThere should be many modes found, and is more confirmation that there is no usable edid.
To be sure, run:
Codefind /sys -name edid -exec wc -c {} \;You should see something line:
Code256 /sys/devices/platform/gpu/drm/card0/card0-HDMI-A-1/edid 0 /sys/devices/platform/gpu/drm/card0/card0-HDMI-A-2/edid 0 /sys/devices/platform/gpu/drm/card0/card0-Writeback-1/edidThe actual hdmi display you are using should start with a non-zero number (typically 256 for a TV style display with audio).
If all the numbers shown are 0, we can't read the edid.
-
That log doesn't have debug enabled.
The link I gave shows a pastekodi command that reports a lot more info than the kodi.log.
There is no cmdline option to hardcode audio. We need to confirm what the issue is.
I'm suspecting it's not possible to read the edid, which suggests either the hotplug detect (pin 19)
or SCL/SDA (pins 15/16) are not functional.
-
The fact it doesn't just work out of the box for you (like it does for almost everyone else) suggests you have a problem with detecting the display. This is probably a faulty hdmi cable (although it could be a faulty display).
Try switching hdmi cable, or connecting to a different hdmi input (of there is more than one).
Post a log file which may have more clues.
-
I tried forcing 720p using config.txt and hdmi_mode=4
I also tried hdmi_safe=1
config.txt settings apply to the old, deprecated firmware display driver.
cmdline.txt is the standard linux way of configuring display modes. e.g. see here.
Something like:
Codevideo=HDMI-A-1:1280x720@60DAdded to cmdline.txt (on end of same line).
-
Did you find and read this?
-
However, I noticed that when viewing such files, the screen goes blue (no signal) for a second and then returns to the connection with the pi, where the file starts flawlessly. This does not happen with H264 encoded files, so I find it a bit strange. Obviously I have never had this issue before, since the pi 3b cannot play H265 content. Any explanation to this?
Does this occur if you disable hw decoding in settings/video?
-
Is the Pi3 running the same version of LE as the Pi4?
It is more likely a change in behaviour due to different versions.
All the "hdmi_" settings you've mentioned apply to the deprecated firmware display driver.
LE10/11/12 use the kms driver (kernel side) rather than fkms (firmware side) used by LE9.
The kms driver does rely on a fully working hdmi cable (i.e. reporting hotplug and edid correctly).
The fkms driver was more likely to somewhat work with a faulty cable.
As a simple test, connect the Pi4 to the display without an sdcard inserted.
It should show a diagnostic screen, that includes info about hotplug (HPD) and edid.
What does it show?
-
Are you stopping the video when navigating with kodi?
Do you have "adjust display refresh rate to match video" set to on start/stop?
-
Ok... But the guide(https://wiki.libreelec.tv/support/update) says it should be a .tar file to update. The only one i found is a .gz one.
That will work fine.
-
No. There's currently no 3d support.
-
2. My understanding is that RBP3 doesn't use standard (hardware) video acceleration, and will run worse on newer versions, so the best version to use is 9.2 since that was built pre-4 and has all the specialized video accelerations tricks for RBP built in.
HW acceleration works fine on Pi2/Pi3 for h264, mpeg4, mpeg2 (with licence), VC1 (with licence) with latest kodi.
The only loss compared to 9.2 is hevc decode. That had a heavily software accelerated decoder which used bits of
arm simd, 3d shaders and VPU vector operations. Unfortunately that just wasn't possible to support when moving to
standard linux api (v4l2 and drm).
I'd recommend using the latest LE image, and avoid hevc encodes.
If you need to play hevc, then stick with 9.2.
-
Try with video=HDMI-A-1:1920x1080@60D
-
Okay - those logs look identical so the firmware is loading the device tree overlay (called HAT) correctly.
Looking through the kernel log. This is the bad one:
CodeFeb 17 04:10:58.938161 LibreELEC kernel: wm8804 1-003b: Failed to read device ID: -121 Feb 17 04:10:58.938688 LibreELEC kernel: wm8804: probe of 1-003b failed with error -121and this is the good one:
CodeFeb 17 04:10:58.605877 LibreELEC kernel: wm8804 1-003b: revision EThis feels like a hardware issue. You might want to try reaseating the HAT to make sure it's secure,
and perhaps check the soldering looks consistent along the 40 pin header.
-
<<Do you have "adjust display refresh rate to match video" enabled.>>
It was set off, I changed it to always but it didn't seem to make a difference.
I then thought what happens if I set the display rate to 25fps and its almost perfect. I reset the refresh rate to 30 and rebooted but still jerky. Blundering about the wiki I manage to track down the entry for this and it says always isn't recommended - which of the two remaining is the best choice?
On Start/Stop is usually recommended.
