Posts by chewitt

Flirc + "any IR remote you want to use" is always a winning combination.

cp /storage/.config/samba.conf.sample /storage/.config/samba.conf

^ edit the list of shares and reboot to effect the change

That's for Amlogic legacy kernels which we no longer develop. I'm talking about the mainline kernel codebase.

It would be best to post the Q in the Kodi forums where the scraper developers hang out.

Quote from mattlach

I've also never quite understood the difficulty in adding NVDec, considering Kodi uses FFMPEG for playback, and FFMPEG supports NVDec. But that may be a question for another thread...

In the last 2.5 years Team Kodi has been slowly and successfully driving the Linux codebase towards common standards (GBM/V4L2) and away from vendor-proprietary interfaces (VDPAU, Amcodec, iMX6, OMXplayer, etc.) so there is low interest in adding another nvidia vendor proprietary interface (NVDEC) to Kodi. It's probably not hard to do, but someone has to do it, and even if it's done it's unlikely to be accepted into the codebase.

Amlogic should auto-detect HDMI vs CVBS output and configure itself as required. I've never tested it (as I have nothing that takes composite input) but the DRM driver supports it.

The arm32 container probably works (we use 32-bit userspace on RPi4)

I've no idea what a "regular" RPi is but if you add facts like model number to the question; the Zero thru 3B+ models do not support 4K and the 4B does support it. And "no log = no problem" .. because we suck at blind guessing what user issues are.

Most of the team still regard x86_64 as the "true" Kodi experience and is still the best for GUI (due to raw CPU performance) and will be the first to properly crack HDR support. That said, ARM devices are now approx 85% of our userbase (75% is RPi of some kind) and whlie ARM means there is usually some kind of compomise somewhere, they're increasingly capable devices.

All I can say is .. it works for me

LE is inentionally a "client" OS with some super-limited server capabilities and docker support targets running basic apps that complement our client fucntions. If you want a server device, you're running the wrong distro.

Despite being a total pariah when it comes to following open-source standards the nVidia folks deserve credit for supporting cards with updated LTS drivers for huge time periods, but even they have limits. I forget what specific X11 version caused the break, but I think it was around LE 9.0 when nVidia stopped updating the 304.xx drivers and we switched to 340.xx. GitHub will have a record of the change.

Linux network development - Patchwork

^ shows that that patches I flagged were accepted, meaning they are queued for Linux 5.9, and there are no new patches which means the chipset is still not supported in the kernel. Your next move is to wait patiently.

You can use WinSCP to transfer files over the network to the booted device. It's slower than a local copy to USB, but can run in the background.

Go read post #2 again, then if that does not match your experience, post again with some evidence of a problem. LE is not Retrpie so comparisons with an entirely different distro are not particularly relevant. Yes they are both Linux OS, but Ferrari and Nissan are both cars, if you get the point.

LE will mount the HDD device to a consistent path based on the disk label (if it has one) or the UUID (if it doesn't).

LE embeds multiple nVidia (vendor) drivers to support different generations of GPUs, but the 304.xx series is the last one to support 7-series cards and this no longer supports the ABI version we need to support current Xorg with other GPUs (Intel, AMD, etc.) so it was dropped and the oldest driver we include now is the 340.xx series which stops at the 8-series cards. As 7-series cards are now 15+ years old we're comfortable with that - never in our history have we ever pitched ourselves as something to use with old or recycled hardware, and our focus is on current and bleeding edge HTPC kit. In the future we might drop nVidia drivers completely and default to nouveau, but nouveau hasn't been tested (by nouveau developers) on cards that old for a long time either so I wouldn't guarantee it works. Time for a GPU upgrade, or swap to a Raspberry Pi 4 which will probably be cheaper and will out-perform anything that shipped with a GeForce 7-series card.

Install the system-tools add-on from our repo and configure "hdparm" over SSH to configure a spin-down time. There should be lots of how-to guides on hdparm if you Google for them.