I guess the old Celeron doesn't provide HDR, right? Otherwise it would be interesting to compare working and non-working logs.
Posts by Da Flex
-
-
I have no idea? How can i tell?
If BIOS/EFI and all Windows drivers are up-to-date, then your firmware, used by LE, is up-to-date, too.
Maybe that step is needed to get reliable results.
-
i rebooted the minipc and it now is able to connect to wirelesss. Don't know why the pc crashed at first try.
I hope your firmware is up-to-date.
-
RPi's have best software support among all LE devices. Just do QC after buying one.
-
I checked the CEC, for some reason there were two CEC add-ons...
That's a known bug. Install latest LE 12 nightly to fix it.
-
is it known, that a fresh installation of LE 12.0.1 along with either TVhead4.2 or 4.3. on Raspi 3 B+ is not really working?
Be more precise.
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 -
We already had it with the 2GB variant (see post #4). The 8GB issue is new here, since they've changed hardware.
-
Last quoted code line seems to say that it's upscaled. Please correct me, if you actually get another resolution.
The log looks fine, just the harmless errors that I see all the time. So I think the TV can't deal with an HDMI param.
Try this (same as before, but without the "M"): "video=HDMI-A-1:1920x1080@60".
Explanation of HDMI params: https://www.kernel.org/doc/html/latest/fb/modedb.html
-
Code
Display More2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 3840x2160 @ 30.000000 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 4096x2160 @ 24.000000 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 4096x2160 @ 23.976025 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 3840x2160 @ 29.970032 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 3840x2160 @ 25.000000 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 3840x2160 @ 24.000000 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 3840x2160 @ 23.976025 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 1920x1080 @ 60.000000 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 1920x1080 @ 59.940063 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 1920x1080i @ 60.000000 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 1920x1080i @ 59.940063 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 1920x1080 @ 50.000000 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 1920x1080i @ 50.000000 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 1920x1080 @ 30.000000 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 1920x1080 @ 29.970032 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 1920x1080 @ 24.000000 Hz 2024-02-27 17:26:06.819 T:815 info <general>: Found resolution 1920x1080 with 1920x1080 @ 23.976025 HzCode2024-02-27 17:26:07.043 T:815 info <general>: GUI format 1920x1080, Display 3840x2160 @ 30.000000 HzSeems like the TV upscales the resolution (try to avoid that in TV settings). Try "video=HDMI-A-1:1920x1080M@30". I guess the TV will double the refresh rate automatically, so you still get 60Hz at the end.
-
@contialdo Congrats! Maybe you got a higher level of electromagnetic interference now. Your surrounding might be the cause.
-
Y, sorry. That's the file I modded: cmdline.txt.
You have to add the param from chewitt at the same line as all other params, only separated by a space sign.
-
There's a timer on my ability to post so rather than respond to folks with quotes I'll have to roll everything up in a single post...
Yeah, cause you're a young lad here.

-
We still don't know your LE hardware. To my knowledge, most desktop PCs don't support CEC.
Please check CEC connectivity from SSH:
PostRE: Rpi4 + Samsung TV - No HDMI-CEC since 11.0.5/6?
If chewitt serious recommendation don‘t ends in a success, you can stop KODI and afterwards check CEC directly.- stop KODI
systemctl stop kodi - scan CEC bus
echo 'scan' | cec-client -s -d 1
HarryHMay 31, 2024 at 2:54 PM - stop KODI
-
When LE is running, witch to TV mode, and then back to AV input.
-
CEC should work. HDMI always has the same wiring, just the cable shielding is better in higher versions.
-
Rule out electromagnetic interference. Take the RPi away from the TV for a test, and use a proper HDMI 2.0 /2.1 cable.
If it doesn't work, install Raspberry Pi OS on another microSD, and give it a shot. That's the gold standard OS for all RPi.
-
RPi3 runs at 32 bit mode, RPi 4 at 64 bit.
It's good to report problems, but we have to be more precise before developers get active.
So if you create a swap file just for testing, we could figure it out, and devs might start working.
-
So it seems like the implementation of the WiFi code on LE12 for the RPI4 has some issues with memory leak/hogging.
I haven't seen such issues at the logs, so I assume LE 12 just uses more RAM. Unfortunately you don't want to fix it by creating a swap file.
