Would it be possible to build ffmpeg with libx264 and libx265 support or are they still too slow?
The ffmpegx add-on provides an ffmpeg binary wth h264 support (not sure about h265). Hardware encoding is still some way off as the kernel is still missing a defined uAPI for V4L2 encoding so there's a choreographed dance between kernel, specs, and userspace apps like gstreamer and ffmpeg to pull off.
dmesg showed that the firmware overlay was processed, but the iwlwifi driver was not added.
The RPi5 image doesn't contain iwlwifi drivers or firmware.
This image (LE13) has the driver enabled: https://chewitt.libreelec.tv/testing/LibreE…-12.90.1.img.gz
I'd like to know the specific firmware files required for that card, as the iwlwifi folder in upstream linux-firmware contains a ton of files and I only want to pick the subset needed. Please experiment and report back.
Google how to use fdtput and disable the SDIO node for the WiFi device in device-tree. Or blacklist the kernel driver. Or use rfkill.
Have a look here: https://github.com/jefflessard/tm…eedback/devices
If you know the VFD config that worked on CE there should be a matching dtso file. Amlogic u-boot doesn't support overlays so you cannot load/use the dtso overlays directly, but you should be able to look at the content there and see how I've implemented the same changes in board dts files in my kernel branch.
The device-tree content for tm16xx has changed format a bit due to kernel maintainer feedback so the dts files in my 6.17 repo will work with the driver in LE13/master but not the driver in the LE12.2 image.
Some platforms, e.g. SNES, have about 10x possible emulators so the workflow is oriented towards opening the game ROM/file and then selecting the emulator you want to run it with, not running an emulator and then selecting a game.
Please stop creating new threads with the same question!
LE does not have package management. It does have Docker. Docker runs containers, which provide apps to the OS. You can install containers that provide the apps you are looking for. NB: VLC server is not compatible with V4L2/GBM graphics.
Now I am going to try CEC over HDMI
HDMI-CEC is rarely supported on x86_64 hardware so this likely won't work.
There are changes to iptables/nftables in recent kernels and I probably need to spend more time on the issue; which won't happen that quickly as I'm travelling for most of the next week.
The trac ticket is referring to https://code.ffmpeg.org/FFmpeg/FFmpeg/…ac5c69aa1cffffb and a few follow-up commits. This was merged for ffmpeg 8.0 so it will not be in current LE images which use 7.1; we are waiting on an update of v4l2_request support patches for ffmpeg 8.0 to be completed, and then we will bump to 8.0. I am hoping to see patches submitted this week, but the contributor responsible has a history of optimism on dates, so no promises 
You can install the Docker add-on and then pull an Icecast2 container, e.g. https://hub.docker.com/r/pltnk/icecast2 - we have no idea how it is configured or whether the end-result is useable. The main idea behind Docker support is that users can install and support whatever they like (emphasis on the user supporting themselves).
NB: The Virtual OVA exists for internal test and devevlopment and we expect audio and video rendered in the ESXi browser client or vmware fusion/workstation/player. Users are welcome to experiment with other use-cases, but those are also self-supported.
is there any way to tell what was applied?
If the system boots /etc/os-release will tell you what is running. If the system does not boot you can compare the md5 hashes of the KERNEL and SYSTEM files in the boot partition with hashes of files in the released Generic and Generic-Legacy images to see which ones match.
The common mistake with recursive copying is some form of cp -R /oldstorage/.kodi /newstorage/.kodi which results in the old Kodi userdata files being copied to /storage/.kodi/.kodi and since that's the wrong location you still see a clean install on restart.
It also sounds like the clone worked (it booted) so the missing step was editing syslinux.cfg in the boot partition to change default boot mode from 'run' to 'boot'
Hi chewitt Can you please share how to clear / erase the spi flash?
If asked, we would have advised to use the backup and restore functions in the LE settings add-on.
The file plays software decoded on an RPi5, albeit with an abysmal frame-rate (but frames are rendered). Have you done previous tests on the same 1080p display device? - forcing Kodi to downscale 4K prores to 1080p probably doesn't help the cause.
Probably impossible for the thread starter, and needs further explanations.
Most device-tree files are visibly littered with 'status' describing whether something should be 'enabled' or 'disabled' so as long as you have half a clue about includes/dtsi it's 'not rocket science' to disable something in a specific board dts that was enabled in the inherited board family or SoC dtsi.
The WiFi module is part of the RK3566 SoC, so not removable
That is incorrect. The WiFi module is a separate chip (Cypress CYW43455 according to schematics on the Pine64 website) connected to SDIO (WiFi) and serial UART (BT) lines of the SoC but not functionally part of the SoC itself. The module it always is a separate chip package soldered to the main PCB.
It would be easier to disable the SDIO/BT module through device-tree changes (disable the sdio node, disable the BT node) than to physically modify the board by unsoldering chips, although that could also be done if you have the tools/skills.
Mainline u-boot overwrites the 'memory' node in device-tree with what it detected, so 1MB is corrected to 2MB, whereas Amlogic u-boot uses the value described in device-tree, hence all the 1g/2/3g dtb variants you find in vendor kernel sources.
