Posts by chewitt

It is nnot supported by anything we've ever officially produced and options will be VERY limited. There are some unofficial images that support Meson8 hardware; whether they work on a MXIII clone box is always a dice roll since there are 30+ manufacturers of externally identical boxes with different PCBs and combinations of components inside. You'll have to search the forum for threads and experiment.

LE supports a wide variety of ARM SoC hardware devices. CE supports only Amlogic devices. The CE 9.2 release is probably the best option for the box right now. LE has experimental modern kernel images (see nightly test images) but there is curently no support for the onboard tuner hardware in the upstream kernel. Out of tree tuner and demod drivers exist (in rough format) but the V4L2 demux driver needs to be written from scratch and this is unlikely to be done anytime soon. CE has dropped support for GXBB devices in their K19 images, so the future is not straightforward .. LE is not ready and CE doesn't exist.

It's best to ask for CE help in their forums.

There is no way to "configure" Kodi to hide the OSD popup during transitions. You either need to modify Kodi (at code level) to remove it, or modify the skin so that when it is shown; the skin doesn't actually show anything.

Netboot + Some additional utility scripts that are embedded in test images. Everyone has their own personal workflows so nothing is really standardised at an LE level. If you'd like to understand how it can/should be done, find the Embedded Linux Conference presentations on YouTube from Bayrlibre, Collabora and Pengutronix on building a LAVA lab for KernelCI missions.

The . in /storage/.kodi is not a typo, it's the correct path and the files are there, but WinSCP is hiding folders that start with a period so you need to change the settings.

LE uses /storage/.kodi/addons and /storage/.kodi/userdata/addon_data .. files under /usr are inside the read-only SYSTEM file.

If "used to be fine before" refers to legacy LE/CE images you should probaably stick with them. There is about 1% driver code in-common with the upstream kernel so current LE images with mainline kernels are effectively a complete rewrite. Modern kernels have quite good overall OS support and I can work on creating device-trees and such to enable more boards/boxes to be supported, but the media capabilities are not in good shape. There is no hardware HEVC decoding support, and while the H264 decoder is implemented it needs work, and some major changes in ffmpeg. I don't write code, so I have no ability to fix any of that stuff.

LE has no disk recovery tools .. sorry.

Quote from menkalos

I just followed the instructions to update to the latest version of LibreElec and Kodi.

LibreELEC (Matrix) 10.0 BETA2 – LibreELEC

LibreELEC (Matrix) 10.0 BETA1 – LibreELEC

^ well, the instructions clearly state *** DO NOT UPGRADE! *** so by ignoring them and upgrading you broke your install

I'd suggest you (re)start with a clean install on SD card, then migrate files to the USB drive once working.

The PR is clearly marked as "Draft" status, so it is not merged and not present in nightlies.

Unless you see me comment about making changes to MPEG2, there are no changes to MPEG2.

I find remotes are very much a personal-taste thing. In the UK the "Sky Box" (Satellite) remotes are solid and have all the right buttons.

The obvious solution is to re-encode legacy formats into modern formats so they are playable on the modern device.

Dropbox - LibreELEC.USB-SD.Creator.macOS.dmg - Simplify your life

^ I built this for testing the other week with changes to fix things that don't work. Catalina will whinge about the images not being signed by a trusted Apple developer (as I am not one) but once you allow the .dmg to open and the app to run (Control Panel > Security, etc.) it works. I need someone to fix the JSON parsing code (as I don't have the skills to fix that) and then I'll sign up with Apple to sign the binaries and solve all the security warnings.

[    3.802399] rtw_8821ce 0000:04:00.0: enabling device (0000 -> 0003)
[    3.802438] rtw_8821ce 0000:04:00.0: Direct firmware load for rtw88/rtw8821c_fw.bin failed with error -2
[    3.802442] rtw_8821ce 0000:04:00.0: failed to request firmware
[    3.805443] rtw_8821ce 0000:04:00.0: failed to load firmware
[    3.805447] rtw_8821ce 0000:04:00.0: failed to setup chip efuse info
[    3.805450] rtw_8821ce 0000:04:00.0: failed to setup chip information
[    3.810017] rtw_8821ce: probe of 0000:04:00.0 failed with error -22

No idea

The need for delinterlacing is well understood and it's on the list, but not at the top of the list. Other plumbing needs to be solid (and changes to the V4L2 specs agreed in principle) before we embark on that corner of the jigsaw puzzle.

2021-04-22 08:36:42.422 T:1311    ERROR <general>: CCurlFile::Stat - Failed: SSL peer certificate or SSH remote key was not OK(60) for https://stream.psychedelik.com:8002/
2021-04-22 08:36:42.705 T:1311    ERROR <general>: CCurlFile::FillBuffer - Failed: SSL peer certificate or SSH remote key was not OK(60)
2021-04-22 08:36:42.706 T:1311    ERROR <general>: CCurlFile::Open failed with code 0 for https://stream.psychedelik.com:8002/:
2021-04-22 08:36:42.972 T:1311    ERROR <general>: CCurlFile::FillBuffer - Failed: SSL peer certificate or SSH remote key was not OK(60)
2021-04-22 08:36:42.972 T:1311    ERROR <general>: CCurlFile::Open failed with code 0 for https://stream.psychedelik.com:8002/:                                       
2021-04-22 08:36:42.973 T:1311    ERROR <general>: Open - <https://stream.psychedelik.com:8002/> failed to open
2021-04-22 08:36:42.973 T:1311    ERROR <general>: Init: Error opening file https://stream.psychedelik.com:8002/
2021-04-22 08:36:42.973 T:1311    ERROR <general>: CAudioDecoder: Unable to Init Codec while loading file https://stream.psychedelik.com:8002/

^ those are the only bad things I can see in the log. I can't comment on whether the errors are valid or not, but even if they are, the add-on should handle them gracefully and not crash. I would take it up with the add-on author in the Kodi forums support thread as it's probably not and LE specific issue.

Flirc USB <= then use any IR remote you like. It's not cheap, but it's simple, hassle free, and you can reprogram it any time you like when a newer shinier remote catches your eye.