Posts by chewitt

Five options:

a) Copy the file old release file (.img.gz, .img, or .tar) to the Update SMB share on the box and reboot

b) Use an SFTP client to copy it to /storage/.update, then reboot

c) SSH in, change directory (cd) to /storage/.update and then wget the file, then reboot

d) Use the manual update function to change to an older release series and select an older version, then reboot.

e) Create new install media using the older .img.gz file and clean-install using that.

Unless you did 'E' once you're on the old release, do a hard reset in LE settings to remove all traces of newer versions.

All of the above are documented in the wiki .. and I'm done with the spoon feeding.

Kodi determines audio/video capabilities based on EDID content on the HDMI connection so if the EDID output is bad or broken it will cause features to be not-detected. It's unusual for a modern TV to have bad EDID data, but it does happen.

I'd suggest experimenting with other HDMI cables and different ports on the TV, as different ports often have different capabilities and sometimes you need to enable e.g. "Deep Colour" modes in port settings to have HDR or 4K60 support (there are no standard terms; vendors make up different names).

Kodi dropped support for "amcodec" decoding several years ago and that makes it impossible to use the Amlogic legacy kernels. AMLGX (LE12) is using a modern Linux 6.7 kernel; support is a little experimental in places and things are not perfect, but it's usable and avoids the need to purchase a new box for some users.

The box will work, but it needs a device-tree file that describes S/PDIF hardware. I'll have a look at that..

Yes, but what kind of file? .. media file, update file, backup file? - they are all different and have different workflows.

NB: If you are still trying to downgrade the easiest option will be to go into LE settings > Updates. Change from auto to manual update mode. Select the LE major version to use. Select the specific release listed. Hit enter to start the update. Once you updated (to the older release) go into settings and do a hard reset of settings; this resets Kodi to a fresh install state do you clear all config and add-on related things from the previous (newer) version.

Quote from petediscrete

You do know the mods will shut down that discussion very quickly.

If the development conversation here ends up discussing both distros it's really not an issue for anyone. That said, if you want to ask detailed Q's about CE internals it's probably the wrong forum to use because that's not our expertise.

Quote from retropie boy

Would i rename each TV episode like this for example (S2.E1 Diamonds 'n dust)

No, they would be like "The A-Team s02e01.mp4" .. the filename must contain the show, series number and episode number. Any other info like "- Diamonds 'n dust" is ignored by online scrapers. You can use e.g. s01e01 or S01E01, the casing doesn't matter.

NB: The Kodi wiki is quite clear on this stuff, and you either follow the naming conventions needed or have issues with scraping things to the library. It is technically possible to tweak the regex's used by the scrapers to suit custom schemes, but if you have to ask how that's done you have no business trying to use that feature!

I'm not 100% sure of all points, but udevil knows they are USB drives and this inherently means they are removable block storage devices unlike e.g. SATA drives which are treated as non-removable, and it mounts them to a known "auto-mount removable block storage" location. Those differences are all documented/registered in the udev database which is queried by apps; and those apps may choose to show different icons or handle them differently based on different properties, e.g. bus type, mount location. I don't use UPnP so can't say what Kodi does with removable vs. internal drives, but there's probably info in the Kodi wiki or you might need to ask Q's in the Kodi forum.

To prevent auto-mounting you'll need to clone the default rules file to /storage/.config/udev.rules.d/95-udevil-mount.rules and then modify it to create exceptions for specific drives using UUIDs/LABELS or such. You can then create alternative mounts e.g. using a systemd service that runs ExecStart commands to mount things as you need them.

LE can/will shut itself down gracefully on most x86_64 hardware. The exceptions will be things with broken BIOS/firmware but IMHO those should be quite rare these days. You can schedule shutdown with cron or a systemd timer, and if the BIOS has an RTC/wake capability it can also be (re)woken on schedule too; or you need to look at sending WOL magic packets to the NIC from something else in the network (assuming the NICs support WOL, which these days most do).

Kodi has "profile" support, but I understand it to be more about how to manage different sources/libraries for different users than security lockdown capabilities, and it's one of the more unloved areas of the Kodi codebase so you should expect inconsistencies and quirks on implementation. It might help, or it might not (not something I use so can't really speak from experience).

The last Q was "how do I connect over SSH" .. which we answered. So what are you trying to do now?

Kernel performance (perf) sampling has nothing to do with this, and MCP7A is the ION chip type (not an audio chip).

Please install the multimedia tools add-on which includes "alsamixer" and check the HDMI card output is not muted or at zero. This is not the same as the volume control and mute function in the Kodi GUI.

Lots of Android boxes have S/PDIF output but I'm told the real Amlogic p212 reference board does not have that; and the upstream p212 device-tree file that you're using correctly describes the reference board. Maintainers are not keen on me adding S/PDIF to the reference board or creating a pseudo "p212-spdif" board, so the workaround will be to upstream a real p212 box which is verifiable and has S/PDIF outputs. The OSMC Vero4 might suit that purpose.

NB: Using old driver code is basically impossible as there's practically zero code in-common between the legacy vendor kernel and the modern/upstream kernel codebase.

Quote from CommodoreCrunch

The download links for Pi 4 and 5 give a 404 because the URL still says "arm" instead of "aarch64"

Oops .. should be fixed in https://github.com/LibreELEC/website/pull/19

Quote from jim_p

As it seems, it still has the same issue with wifi that le 11 had, because iwd and connman could not work well together

If this is about your ageing Amlogic box? the primary issue is the unmaintained Realtek vendor drivers it requires that are not fully conformant to modern kernel wireless frameworks, so no point/need to start threads on them. If you're lucky I might be able to persuade the person working on upstream support for RTL8192DU to look at RTL8189ES/FS in the mid-term future.

LibreComputer's owner said "Green, not tint, is usually HDCP or HPD issues with the TV. What make and model?"

Quote from PANiCnz

Unfortunately, the range of devices supported by the Skip 1s is a big lack luster.

You know it's a programmable universal remote, right?

Quote from bpr323

should I change the docker volume setup

Yes.

Quote from bpr323

Does this mean the "whole system" is loaded to, and runs from RAM after boot?

If the device has 1GB+ RAM, yes.

OpenVPN is present in the OS and a new VPN connection can be created by calling it (at the right time in the boot sequence) with a command that specifies the relevant .conf file to use; and assuming that conf file correctly references the certs that are required (either external files or more likely they are embedded in the conf itself). The /storage/.config/system.d/wireguard.conf.sample shows how to run a wireguard connect command at the right time in the boot sequence. All you need to do is rename and mod the file slightly to run an OpenVPN command instead. NB: The sooner you learn a little about how OpenVPN connections are started and stopped, the sooner you stop needing GUI add-ons that are rarely available/updated and only complicate a simple process.