Posts by chewitt

Requests to modify how the Kodi SSH/FTP client performs/behaves should be done via the Kodi forums. LE simply consumes whatever code the respective Kodi devs publish or bundle with Kodi.

This has a high probability of failure because autostart.sh is executed right at the start of userspace boot before the network stack is up. If you run the script in the background (as you are) you need to add sleep values to allow the network to come up, and you probably need to delay Kodi start to allow for the mount to happen first.

This is why systemd mounts exist. Systemd allows you to apply dependencies, e.g. so the mount "wants" the network target to be up, and "before" the Kodi service is started. Look at the examples in /storage/.config/system.d/

3D support in RPi4B is not broken, it is not implemented (in both LE 9.2.x and LE10 codebases). Last time I asked about future support in the LE10 codebase I was told it's not impossible to support, but there's a long list of much higher-prioority things in the To-Do list. If you need 3D support, it's best to keep an RPi3 around (which does suppport it under LE 9.2.x, but not LE10).

Real-life is rather busy right now .. I'll get around to it eventually

If the local Samba server is enabled (it is by default) LE advertises local SMB shares via ZeroConf (Avahi) so you should be able to "browse" the network for ZeroConf shares to add in Kodi.

I'll add $0.02 to the conversation: If you want any form of response or interest from devs you need to test/use LE10 images. It's not that we don't care about LE 9.2.x, we do, but it's a codebase that is no longer in development so anything you find is not going to be fixed, and LE10 has significant-enough differences in software component versions to make comparisons low-value.

Quote from @fterlife

I am by no means a programmer though so apologies if these are dumb questions.

not. dumb. but. its. complicated.

Quote from PANiCnz

Audio passthrough has stopped working on my x86 install. Was working fine on B3 and I skipped B4. Any chance this is a known issue or do you need logs etc?

Debug Logs.

Quote from @fterlife

Just an idea but would it be possible to send the HDMI signal interlaced to the tv and have the tv perform the deinterlacing? Usually TV's are quite capable deinterlace devices. I only see progressive resolutions in the whitelist. Perhaps interlaced resolutions can be enabled some other way?

Not possible as Kodi has no concept of video pass-through and only outputs progressive.

You can use a current nightly until 9.95.5 is released. There are more BT fixes in the settings add-on.

Quote from Coolzero

I have still this erorr in the log, is there a solution?

Code

2021-06-16 07:27:11.513 T:1207    ERROR <general>: DBus error: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower was not provided by any .service files
2021-06-16 07:27:11.513 T:1207     INFO <general>: LogindUPowerSyscall - UPower not found, battery information will not be available

It's harmless and simply reporting that UPower doesn't exist (which is true on LE, it's used on some generic distros). You can ignore it.

It's best to ask in the PINN forums (or RPi forums) nobody on staff runs NOOBS/PINN so our experience is rather limited.

There was some traffic on the mesa mailing list in the last couple of months about alternative GBM back-ends, which is basically about nVidia partially conceeding they aren't going to win the GBM vs. EGL Streams discussion and tweaking things on their side to reduce the differences, combined with compromise on the mesa side to allow alternatives to current libgbm; which isn't so objectionable now the EGL Streams "GBM" shim makes the differences relatively minor.

This basically allows Tegra DRM drivers to plug into mesa's userspace rendering infra which is well proven and widely supported; the shift from X11 is gathering momentum and Wayland needs mesa. Tegra V4L2 accelerated decoding is then the (non-trivial) missing link. If V4L2 compliant DRM/ffmpeg drivers are written (compliant to kernel V4L2, not some proprietary nVidia-ised interpretation) Kodi should require no changes to support Tegra boards. That's the theory anyway

Last time we looked the Tegra GPU drivers needed X11 to run, which does not align with the V4L2 oriented technical direction LE is persuing for all devices, so there is little interest in trying to support the boards.

Write this file Dropbox - bootsector.img - Simplify your life to the USB using any USB writing tool that you like (on whatever OS you are using). As long as the USB drive is okay it will nuke the partition tables and allow your OS to repartition/reformat the storage again. If it fails to write, the USB drive has a problem and it's time to bin it and get a new one (they don't last forever).

Use dd ?

chmod +x LibreELEC.USB-SD.Creator.Linux-64bit.bin
./LibreELEC.USB-SD.Creator.Linux-64bit.bin

^ first line makes the .bin executable, second line executes the .bin