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.
Posts by Da Flex
-
-
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.
-
It's scary that a read-only access damages files. I assume a lot of buffering is going on in the background, because audio is large, and has a lossless codec.
- format your USB drive as EXT4
if it doesn't work, create a swap file (I suggest to create it at the same USB drive, swap file size: twice RPi RAM size)
-
Which audio format / codec do you play? I don't see it in the link.
-
Funny issue, I never heard about that. Like a broken vinyl record.
Playback is a read-only process, so LE can't be the cause. I think your USB drive has reached end-of-life.
-
-
Do you get the same error without the USB drives?
CodeOct 05 21:01:59.657874 LibreELEC kernel: musb-hdrc musb-hdrc.6.auto: VBUS_ERROR in a_idle (80, <SessEnd), retry #0, port1 00000104 -
I wonder if I should simply install again LE11, which was working fine.
Yes please. If it's not working with the old setup anymore, then I bet on the HDMI cables (see above).
-
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 -
Thank you. Same issue, I used the latest “daily”. I presume that is correct (and my 2gb is now working)?
We mark our builds as "stable" or "nightly". You need latest "nightly" for RPi5 2GB:
-
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 -
I would first try exFAT, and if it doesn't work reliable, get a Synology NAS to share the HDD.
-
The preferred file system for your HDD is EXT4 on LE / Linux. Unfortunately Windows can't read it.
So if you also need Windows access, format the HDD as exFAT.
Try one of those file systems, and hopefully the HDD will be detected every time.
-
Maybe wrong EDID. Try getedid create on SSH, and reboot.
-
LE has problems with HDD and SSD:
CodeSep 30 16:09:05.135462 LibreELEC udevil[1139]: mount: /var/media/sda1-ata-WDC_WD10EZEX-00B: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error. ... Sep 30 16:09:06.094721 LibreELEC udevil[1140]: mount: /var/media/Új kötet: wrong fs type, bad option, bad superblock on /dev/nvme0n1p5, missing codepage or helper program, or other error. Sep 30 16:09:06.094721 LibreELEC udevil[1140]: dmesg(1) may have more information after failed mount system call. Sep 30 16:09:06.094982 LibreELEC kernel: ntfs3: nvme0n1p5: volume is dirty and "force" flag is not set! Sep 30 16:09:06.112361 LibreELEC udevil[1138]: mount: /var/media/nvme0n1p3-nvme-Patriot_M.2_P30: wrong fs type, bad option, bad superblock on /dev/nvme0n1p3, missing codepage or helper program, or other error. ... Sep 30 16:09:09.768228 LibreELEC kernel: iwd[681]: segfault at d ip 00000000004a4977 sp 00007ffdb7c30828 error 4 in iwd[400000+12d000] likely on CPU 10 (core 5, socket 0)Make sure your firmware is up-to-date. Since you also have Windows installed, it should be easy to update all drivers.
-
After coming back from standby, you get exactly two errors:
Code2024-10-01 16:04:24.150 T:1564 error <general>: SETTINGS: dbus_error_handler # DBusError('net.connman.Error.Failed -- Input/output error')Code2024-10-01 16:04:38.421 T:1193 debug <general>: CServiceAddonManager: stopping service.upnext. 2024-10-01 16:04:38.421 T:1193 debug <general>: CPythonInvoker(9, /storage/.kodi/addons/service.upnext/resources/lib/service_entry.py): trigger Monitor abort request 2024-10-01 16:04:38.421 T:1228 debug <general>: Thread LanguageInvoker 140601852946112 terminating 2024-10-01 16:04:38.421 T:1230 debug <CAddonSettings[[email protected]]>: trying to load setting definitions from old format... 2024-10-01 16:04:38.421 T:1230 debug <general>: [service.upnext] UpNextMonitor -> Service stopped 2024-10-01 16:04:38.421 T:1230 debug <general>: CPythonInvoker(9, /storage/.kodi/addons/service.upnext/resources/lib/service_entry.py): script successfully run 2024-10-01 16:04:38.421 T:1230 debug <general>: onExecutionDone(9, /storage/.kodi/addons/service.upnext/resources/lib/service_entry.py) 2024-10-01 16:04:38.422 T:1230 error <general>: EXCEPTION: No valid addon id could be obtained. None was passed and the script wasn't executed in a normal Kodi manner.You can uninstall or deactivate the "Up Next" add-on to rule out the latter error as the cause of the issue.
I guess the first error is the culprit. I think your network adapter has a standby mode, which isn't fully supported by the Linux kernel. If you want to invest the time, dig deeper, and find network adapter specs, as well as current Linux driver state.
My suggestion is not to use standby mode at your current hardware. Maybe a screensaver is good enough.
-
Maybe not enough RAM for current setup. Try a swap file:
