Posts by chewitt
-
-
As per our GDPR policy we don't delete accounts and associated posts, but we rename the user to anonymise posts and we remove any personal information (email etc.) from the forum DB. The final act is banning the account to prevent use. I'll do that shortly.
-
As long as you understand there is no hardware decoding and that limits things to 1080p, it'll run fine.
-
I asked for the debug log because it will show what resolutions and refresh rates are being advertised, and then we can either see what the issue is and/or advise how to set things up. There are no config.txt or dtoverlay things for x86_64 hardware, that's a Raspberry Pi only thing. The 4K-HDR wiki article advice still generally applies.
-
If you want more changelog info please go look at the full/original commit log on GitHub. We have no plans to bloat page load times and increase webserver load with more commit data that likely few people read.
-
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 -
See https://wiki.libreelec.tv/development/build-basics
There are no wiki or howto instructions for adding/building third-party network drivers, but there is considerable "prior art" in the buildsystem and existing vendor drivers are found in packages/linux-drivers/* .. it's very much (and intentionally) a fend-for-yourself arrangement. Users with a little initiative and curiosity will normally figure it out.
-
Kodi changed the SMB chunk size defaults in Omega and while these are sensible and reliable defaults for the vast majority of users, a minority might have network setups that require a tweak; hence the controls are in the Kodi GUI.
NB: Unless your network is broken there is no need to fiddle with cache settings. And if the network is broken, the correct solution is to fix the network, not fiddle with caching.
-
I have a hunch that deleting the default route results in ConnMan detecting the deletion and automatically recreating the route as it requires there to be one. So instead of deleting .. what happens if you change the default route to a value that effectively results in no routing? - NB: I would expect Kodi to throw some errors, as these days it expects to be internet connected.
-
Code
2024-09-14 07:53:01.253 T:1134 error <general>: SMBDirectory->GetDirectory: Unable to open directory : 'smb://192.168.98.2/PROVA' unix_err:'d' error : 'Permission denied' 2024-09-14 07:53:01.253 T:1134 error <general>: GetDirectory - Error getting smb://PROVA/PROVA/
Assuming the username/password and SMB protocol versions are correct on the Kodi end, I'd start looking at the samba log on the router for more info. Also note that Kodi changed the default SMB chunk size in latest versions, and this can have odd results; but that normally manifests in failing to play things smoothly, not failing to access shares.
-
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'd enable SSH in LibreELEC and use an SFTP client (WinSCP is my go-to when forced to use Windows) to transfer media files over to the /storage/tvshows and /storage/movies locations that are default mapped as sources in Kodi to get people started.
The /storage filesystem is EXT4 so copying files is (normally) simple in Linux but painful in Windows/macOS as neither support that filesystem type. It's a little slower, but copying over the network ends up being the easy option.
-
can anyone tell me how to import new certificate into my version 11 so I can install add-ons?
This wiki article is describing a different use-case, but the solution is the same:
https://wiki.libreelec.tv/configuration/ssl-tls-certificates
-
How can I get or compile and install this driver?
LE is an embedded style distro so you cannot add drivers ad-hoc like Ubuntu or similar. You need to self-compile an LE image with an additional driver package added to the buildsystem to compile and embed that driver. If that sounds like rocket-science, the other option is begging the creators of community images to include it (as official releases will not, due to the abysmal and unsupportable quality of the driver code).
-
If you have a link to a $free download of something that works in most places can you share? - I'll link it in a wiki page.
-
There's some CLI examples here: https://features.jellyfin.org/posts/2614/hev…aspberry-pi-4-5
-
I've no idea about PINN or what complications it might add. These days I would leave the RPi4 connected to the network and clean install the RPi5 with a current image, then scp the Kodi userdata content you want from old device to new device.
-