The cmdline.txt from RPi4 has the default settings, so in theory you don't need extra options on RPi5, except SSH.
Please install the LE image again on microSD. This time use Balena Etcher. It does verification after writing.
Posts by Da Flex
-
-
Do you use the HDMI-0 port of RPi5? That's the one near to the USB-C port.
-
It's a pretty new device, so it's not unexpected.
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 -
- Login by SSH, and open the file cmdline.txt. It works similar to config.txt.
- Append vc4.force_hotplug=1 to the end of the line.
- Store that file, and reboot.
-
I beliefe there is a "sync to display" option somewhere (video settings or gear icon on playback bar). Can you try that?
-
Zewkin On which build the issue started to happen? It could help to narrow it down.
-
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 -
-
LibreELEC-RPi2.arm-12.0-nightly-20240205-690684c.img.gz
Partially fixed. I have access but very very slow and it freezes for 5-10 seconds. If I start a YT video from a playlist file, audio starts for 4 seconds, freeze for 20 seconds, still the playlist entries screen visible, than the video starts running with audio.
Please update your server to NFS4. That fixed problems for some users.
BTW: I have also some audio stutter every 5 minutes for 2 seconds length, which component debug log file I should switch on?
New thread please. Post a link at log level 1 (pastekodi result on SSH).
-
We need a log from our own log server. No more HasteBin logs.
-
however, when compared to Raspberry Pi1 , the RF reader gives still rather high reading...
What does that mean?
-
PD: I can't test if HDR is working I have an old monitor here
HDR can't work on Generic Legacy, because Xorg doesn't support it. No need for a test.
-
That wasn't a question, just a point for better stability on NFS4.
-
either way my NUC works fine so its deffo a RPi issue
No, read this thread. Switching to NFS4 makes a difference:
-
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 -
Yes my server uses NFS4 as NUC running LE also used v4 and worked fine.
Code2024-01-31 17:55:50.414 T:1039 debug <general>: NFS: Context for 192.168.1.200/mnt/user/Stuff not open - get a new context. 2024-01-31 17:55:50.414 T:1039 debug <general>: NFS: version: 3Seems like you're wrong.
-
Thx. There are a couple of cache settings for network access. I think it's worth to play with them (see post #8).
-
- activate log level 1 by creating an advancedsettings.xml file
- reboot
- when the error appears, upload the log (by GUI, or by pastekodi command on SSH), and post the resulting URL
