Posts by chewitt

The system is up for some time before the crash so it's unlikely to be something with the core OS, and more likely to be something that result from use. Hard to say what though, the current logs don't reveal much (Kodi log is not a debug log).

Flirc software needs a "desktop" OS to run the IR receiver setup app; Windows, macOS, or something like RaspiOS. There are some command line binaries/utils too, but last time I tried to run those they didn't work on LE - although I'll admint that was more than a few years ago now so things might have changed. I did try to download them and test before replying, but LE12 (which I'm using) uses aarch64 (64-bit) userspace and the tools are armhf (32-bit) so don't run - I've pinged Jason (who runs flirc) about that.

[   14.878121] ntfs3: sda1: failed to replay log file. Can't mount rw!

In 99/100 cases when a "Windows" flavoured filesystem is being used and either won't mount or goes read-only, chkdsk.exe is the answer.

Hard to comment on what the issue is from that info. I'd suggest approaching it as an upgrade opportunity: start with a new installer USB but interrupt boot and type "run" instead of allowing to default to install (and running the installer). This should give you a working LE install on the USB, from where you can a) prove the current release boots/runs okay on the hardware, b) copy/backup any essential config you want from the original installation, c) figure out what update or reinstall path is appropriate.

The TVH client addon data will be in /storage/.kodi/userdata/addon_data/pvr.hts .. so you will need to enable support for "hidden files and folders" in Kodi GUI settings else the file manager will ignore the .kodi folder (in linux the . prefix denotes a hidden folder).

You should be able to connect a serial UART device to the GPIO header on the board, see https://pinout.xyz/pinout/uart for the pinout.

What distro/version and host hardware are you building on?

You need to repair the NTFS filesystem on a Windows box with chkdsk.exe, and then unmount cleanly and it should work.

The "clean install" advice is all about mitigating add-on update problems that can occur with the Python2 > Python3 change from LE10 and later. If users have a simple setup there's generally no problem with the direct update. However if users have third-party, or not installed from a repo that contains the updated Python3 version of the add-on things can crash, and if that happens it can be challenging for less technical users to self-recover and we're not staffed for the effort. If your update went fine.. "if it works, don't fix it" applies

Quote

Is there any way to get it both (Boblight AND hardware decoding)?

Yes/No. Devices that run GBM/DRMPRIME graphics do not support software grabbers at the current time, and I have low expectation of that changing anytime soon as it will be a non-trivial feature to implement. Ambilight/Boblight setups either need to stick with older images that use legacy display pipelines, or switch to an external HDMI grabber (which being a hardware solution, has no dependency on software).

Quote from der.schultze

Any idea?

Chat with the add-on creators in the Kodinerds forum. It's unlikely to be an LE issue.

https://www.kodinerds.net/thread/71663-r…an-de-webseite/ <= might be worth having a look at this thread (or others in the KN forum).

Configure a timezone in Kodi.

Raspberry Pi has some closed-source broadcom boot firmware which some folk get upset or uptight about, but unlike Rockchip who pay lip-service to upstream support and still have closed-source blobs and NXP who hide their entire ecosystem behind an NDA/paywall they openly provide A1+ support for their boards and the software ecosystem around them (both the open and closed-source bits). Pi devs have also been funding a lot of upstream development for their hardware too; because their own resources are limited and time-to-market counts so major things like mesa have been subcontracted to people with the knowledge and expertise.

NB: LE has fairly terrible software support for all the (now dated) Amlogic boards you mentioned. Rockchip support is reasonable. Allwinner is the best of the three. RPi4 still wins the best supported board medal though.

Quote from andymarc

Can anyone assist?

This is the LE forum. The folks who create CE hang out somewhere else.

Where are the symlinks pointing to?

If the NAS supports WOL and some form of scriptable sleep/shutdown command it might be possible to create a startup script that sends the magic packet to wake the NAS and delay Kodi/Emby start until SMB shares are online, and to then send a shutdown command when the HTPC device is turned off. Neither app supports "If NAS source is online use config A, if NAS source is offline use config B" logic; they both expect a single configuration and for that config to be valid. The systemd suggestion simply allows scheduling logic (and scripts) to be used that ensure sources are available before Kodi or Emby container start. I'm not sure if you'll find any howto or prior art for WOL in the forum; it's not a thing that comes up often and most folks ultimately accept that NAS devices are designed to be used in an always-on state.