Posts by chewitt

I replied here: https://github.com/dave-p/TVHadmi…ment-2357927072

Do cold boot not warm boot?

ifconfig bond0 192.168.1.1 netmask 255.255.255.0 up
ip link set eth0 master bond0
ip link set eth1 master bond0

Something like that ^ might work? .. I've no ideas how ConnMan will react to a bonded interface, or whether it will be persistent, or whether it kicks you from SSH at the same time (likely). LE will support the "iproute2" command-set (see https://www.kernel.org/doc/Documentat…ing/bonding.txt) but we're not really designed for fancy network configurations. Our goal is less about having the fastest connection (although that's nice) but to ensure it's "fast enough" to play what you need without issues.

If there were general issues with SD card boot on RPi5 boards we'd be flooded with reports, and we're not, so it's likely to be something local. I'd start with updating to the latest board firmware, and experimenting with another SD card.

READ: https://wiki.libreelec.tv/hardware/amlogic (then use the correct image; hint, it's not the WP2 image).

mount -o remount,rw /flash
fdtput -t i /flash/rk3288-tinker-s.dtb i2c@ff140000 status okay

It's probably easier to use "fdtput" to make the modification. I think that's ^ correct.

Completed.

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.

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.

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.

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.