How are you connecting to the share?
Does it fail/error immediately or after 30+ seconds?
Posts by chewitt
-
-
Code
2024-10-24 19:43:34.317 T:1734 debug <general>: [WHITELIST] whitelisted modes: 4096x2160 @ 60.000000 Hz 4096x2160 @ 24.000000 Hz 4096x2160 @ 23.976025 Hz 3840x2160 @ 60.000000 Hz 3840x2160 @ 24.000000 Hz 3840x2160 @ 23.976025 Hz 1920x1080 @ 60.000000 Hz 1920x1080 @ 24.000000 Hz 1920x1080 @ 23.976025 Hz^ Just don't expect 25fps material to play correctly with those defined. I suggest you go read the config recommendations.
-
Code
2024-10-24 19:41:31.786 T:1871 info <general>: ffmpeg[0x20ca0230]: Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuv420p(tv), 3840x2160 [SAR 1:1 DAR 16:9], 7392 kb/s, 25 fps, 25 tbr, 90k tbn (default) ... 2024-10-24 19:41:31.786 T:1871 debug <general>: [WHITELIST] Matched an exact resolution with double the refresh rate 4096x2160 @ 50.000000 Hz (20)You are forcing 3840x2160 to be scaled to 4096x2160 which is a CPU intensive task that will suck on most hardware. Please follow the config. recommendations in https://wiki.libreelec.tv/configuration/4k-hdr and with a full whitelist configured to omit the 4096 resolutions and with normal handling for 4K@25Hz, it'll probably work.
-
Kodi 21 has optimisations to GUI rendering that make things more efficient. Kodi 22 will have more again.The developer doing the work deliberately uses an Odroid C2 board as the baseline OpenGLES 2.0 device; not because it's Amlogic, but because it's a good example of an older device with limited capabilities.
-
How exactly do add the file?
Enable SSH and login to the device over the network and use "nano" to create/edit text configuration files. You cannot read the EXT4 filesystem used for /storage on a Windows machine.
-
Code
video=HDMI-A-1:1920x1080M@60Try adding that ^ to boot params in cmdline.txt
-
Your device is ARMv8, but LE11 uses 64-bit kernel + 32-bit (arm) userspace while LE12 switched to 64-bit kernel + 64-bit (aarch64) userspace. Python3 add-ons like Netflix/Disney/Max are not affected, but most of these depend upon inputstream.adaptive which is a compiled binary add-on. This will need to updated to an aarch64 compatible version before it will work. The updates to binary add-ons should happen automatically once you've booted into LE12, but if not you can manually force-refresh the repo, or worst case uninstall them (keeping preferences) then clear /storage/.kodi/addons/packages, and reinstall them from the LE add-on repo.
-
popcornmix is there any way to force 1080p composite output using kernel DRM?
-
Any ideas?
You create a systemd "mount" file (used for mounting remote storage) not a "service" file, so looks like classic "PEBKAC"
-
Sorry for the time-wasting.
No worries. I'm glad it was good guess
-
This add-on might be of interest: https://github.com/matthane/script.audiooffsetmanager
-
The main user-experience issue is that Linux has no "fsck.ntfs" equivalent to the "fsck.ext4" tool, so when errors occur the OS has no way to self-recover and continue. Similar issues occur with EXT4 filesystems, but we check the filesystem before mounting during boot and fsck if necessary, which clears dirty flags in most scenarios and allows a dirty drive to be mounted read-write.
The workaround might be to self-compile an LE image that disables the in-kernel NTFS3 driver and revert to NTFS-3G, which should give the same experience as older releases. We aren't interested to do that in official releases because we are keen to keep moving forwards and continue supporting in-kernel driver development. The number of user issues here is overall quite low - despite the impacts users often being rather vocal.
-
You need to set SMB min/max to v1 as the default connection is v2. If you configure SMB min v1 and max v3 it continues to connect at v2 which is not supported.
-
unless I'm missing something glaringly obvious
The most likely explanation is a difference in the performance of the SD cards. I'm using an NVME drive on the RPi5 and it's 25-30 seconds from typing "reboot" to looking at an updated Kodi home screen.
-
In recent releases LE changed from using the long-proven but rather slow "NTFS-3G" drivers which run under FUSE/userspace (hence the slowness) to newer and much faster (but less proven) in-kernel drivers. Hence there are some scenarios with "old releases didn't flag problems, newer ones do" as the drivers being used are completely different. The in-kernel ones are maturing without any major issues, but some users see problems with the filesystem of removable USB devices being marked dirty. There are no "fsck" drivers for NTFS filesystems so "fixing" that generally needs the drive to be reconnected to Windows. One of the major differences between Windows and Linux is that Windows will keep trying at all costs to mount a broken filesystem and make it accessible to the user, wheras Linux bails at the first sign of an issue and either refuses to mount the filesystem, or will force read-only mounting to prevent further damage.
-
I didn't read the log file any further than the banned add-ons. It's probably a self-inflicted problem:
Official:Forum rules/Banned add-ons - Official Kodi Wiki
No support in this forum (as per forum rules you clearly didn't read).
-
The main issue though is at 4K in RGB the display loses sync constantly
That sounds like a textbook case of not using 4K60 "certified" cables. Resulting in insufficient bandwidth and sync problems.
-
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
