Posts by chewitt

The forum attracts pharma spam, e.g. f00d suppl3ments and annoying a few users with censored words list is considerably less effort for the forum staff than cleaning up the spam that gets posted without it. Sorry

The release images for LE 8.2.x were compiled on Ubuntu 16.04 .. so perhaps use an older VM to build with. We have no real-world interest in maintaining the compilability of older releases on newer platforms.

IMHO docker is the right option for people who want to load up on NAS apps (which appears to be the case sometimes) but for a basic home sharing setup where MariaDB is the only server app required I see no harm having it as a native add-on. The only thing that surprises me is that it's taken so long before someone did the work for the add-on

Provide a Kodi debug log please.

That's a Kodi debug log not the systemd journal log (read post #2) so it doesn't show anything useful. And there's nothing wrong with the certificate on the update server .. but your device has broken NTP so the current datetime is before the validity of the cert starts; hence it throws an error.

I'm not expecting the kernel patch sets to be merged quickly as it touches a bunch of code and everyone's aware that it lays the groundwork for how HDR is handled in other SoC/GPU types .. so there's lots of chefs in the kitchen. LE 10.0 is far enough out that it should be a safe 'yes' and LE 9.0 is a definite 'no' but hopefully one of the interim LE 9.x releases we make between them will add support to the K18 codebase.

Share the systemd journal again (as in post #3) please.

It's technically possible to create two audio paths with some asound.conf magic, but the alsa routing is hardware specific (not generic) and alsa config is one of the Linux "dark arts" so you're unlikely to find a nicely written howto guide for your specific hardware. Should you learn and figure something out on your own you'll also discover that the audio paths through the TV and the AVR result in slightly different timings, and this is something that Kodi cannot adjust for (audio delay can be configured globally not per-output) so there's a high chance you end up with a subtle but annoying reverb effect.

vpeter .. IMHO it would make a good standard add-on for the LE repo.

I'm not aware of anyone anywhere working on updated DVB drivers, and there are numerous other mainline kernel tasks that are more important. So no idea (it's not even worth a blind guess) on when that stuff gets (re)written without the old kernel dependencies.

Clone our git repo, make changes, build an image, test and prove it doesn't cause issues, then submit the required changes with test results to our git repo. There's no objection to netboot improvements, but it's a niche capability and almost nobody uses netboot so equally almost nobody is looking at the piece of our codebase.

What channel does your wifi run on?

If the sole use of the device is an HTPC .. eBay it and get a NUC that costs 1/3rd the price and has better support.

Quote from erbas

these new constructs will work on tuner (dvbs) (S905D)

There is no support for the proprietary DVB drivers used in older 3.14 kernels. They mostly use Amlogic kernel frameworks that don't exist in the mainline kernel, so the drivers need to be adapted.

Solved with a change to the JSON data file that populates the list of available releases .. although this currently means Rockchip release files are not currently listed and must be downloaded manually.

The problem is/was caused by the presence of Rockchip files in the JSON data that the USB/SD Creator (and settings add-on) client read to populate the list of available files. The Rockchip files are using a slightly different file naming convention and this upsets the client. The temporary workaround is to rebuild the JSON file without the Rockchip files - which has been done, and a quick test with the Win/macOS/Linux versions shows the app(s) are working okay again.

I've never seen a Chinese manufacturer spend money on dual IR receivers for an Android box. If there's one thing you can guarantee about them, it's that they're cheap bastards

Let's go back and answer the actual problem:

a) If you're mounting from systemd the Kodi SMB client settings are completely irrelevant because you're not using the Kodi SMB client. Similarly the the LE settings addon SMB config (for the onboard SMB server) is irrelevant because that also has nothing to do with SMB client configuration.

b) When you access the router share from your PC "with no password" the router is still asking for a username/password and your computer is still providing your logon username/password. You don't see a prompt because the router will accept any username/password. That doesn't mean you cannot provide one. If you don't, you're not authenticated, and you won't see share content.

So either configure the systemd mount file options to include a/any username/password, or connect the USB drive directly to the HTPC.