Posts by chewitt

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.

The correct path for the firmware should be /storage/.config/firmware/rtw88/rtw8821c_fw.bin

LE is an OS for HTPC devices. You should run Kodi on Windows, the native OS for the tablet that supports all its hardware.

If you edit source files in the "build.LibreELEC.." folder(s) the next time you respin the build the changes will not be used (as we already built the package and nothing in the package.mk or related folders changed) and if you trigger a change by updating something in package folders and respin the build, we remove the existing unpacked sources in the build folders, then unpack and apply any diff patches, and rebuild the package. If you want to modify a package, you need to provide your changes as a diff patch against the original source that we use. Patches can live in numerous locations, but typically in a "patches" subdir of the package folder.

LibreELEC-AMLGX.arm-9.95.2-box.img.gz <= not boot tested on anything with vendor u-boot, and has a pile of changes inside so YMMV.

There are no file/disk recovery tools in LE, but with most hardware we are booting from USB/SD/HDD storage so the device can be removed from the HTPC and connected to a Desktop distro (Ubuntu, Fedora, etc.) where you can run disk recovery tools. I would advise not using the target disk, to avoid overwriting disk areas you want to recover files from.

RPi4 performance beats RPi3, but starting over with a clean install on RPi3 is the same effort.