Posts by chewitt

cp /etc/X11/xorg-radeon.conf /storage/.config/xorg.conf
nano /storage/.config/xorg.conf

^ do that to make changes and it will be used on reboot.

One of the design goals for K19 is the removal of all vendor proprietary interfaces. iMX6 is already gone and VDPAU/amcodec can be removed once the K18 release branch is forked. VAAPI gets a pass because it's no longer Intel specific (AMD and Allwinner will use it). One of the related design goals for LE10 is the removal of X11 and it's many dependencies.

The next generation Kodi video pipeline based on DRM/GBM allows us to support 10+ different GPU/SoC types (everything except nVidia) under a single framework and code path. There is nothing to stop someone implementing EGL streams, but it's not going to be popular with the main Kodi architects (given the design goals) and so far nobody is volunteering to do the work.

Unless that situation changes there will be a technical decision to terminate nVidia support after LE 9.0, and we are actively collecting stats on the number of installed devices with nVidia GPU's to quantify the impact of that decision. NB: If LE ends nVidia support you can still install drivers under Ubuntu or some other distro using Wayland or Xorg.

Most box makers don't deviate far from the OEM reference designs so it's 'probably' supportable (the SoC is on the supported list) .. but it all hinges on getting the device tree right.

It's a long way off, but Python 3 is a firm commit for Kodi v19. The switch should be made once the Leia release branch has been forked.

Nothing will be fixed in the 8.2 branch even if you find and prove a problem. Update to the current Alpha release (8.90.003) and retest please.

Unless you manually turn containers off or the system runs out of disk space they will just keep running. If you are using the popular linuxserver.io containers a periodic reboot of the pi will result in updates to the containers being pulled from their repo.

RK3399 is a supportable but current team focus is on board devices not the legion of crappy Android boxes that can be found on gearbest. Use the right device tree and it should work though.

"it depends" on how different the other OS is to the current RK 4.4 kernel. In some cases (same kernel codebase) the device tree might just work and life is simple. In other cases the current device tree probably contains the info you need to reinterpret things to a new one. Android != Linux and kernel version determines whether you're working in ancient greek or modern greek (so to speak).

@mihailescu2m if you push your current code/changes to GitHub it would be interesting to diff your branch against our master branch and see what's required. At some future point maybe you even send us a PR

Yeah, that will be required too

I've recently been looking at brcmfmac sdio firmwares and current code will take firmware *files* that are placed in /storage/.config/firmware and append them to /usr/lib/firmware but it will not take a folder structure, so /storage/.config/firmware/brcm/* will be ignored.

Can you share (pastebin) the .txt file?

You can fake the EDID data from the TV to make the HTPC think it's connected, see Custom EDID [LibreELEC.wiki]

@mihailescu2m that's a great validation of why we've been working on the next-generation Linux video pipeline for Kodi. Have you contacted the HK people to ask for updated mali drivers with the required features? (they won't have them, but can request from ARM).

Update to the current Alpha release and retest.

Did you enable "adjust refresh rate" and whitelist the modes you'll allow it to switch to? .. because if you don't it'll stick at the default 60.00Hz.

Google "libreelec debug log" and you might find something. It's simple and laziness is no excuse.

connmanctl
agent on
scan wifi
services
connect wpa_blahblahblah_psk

connect via ethernet and SSH into the device, then enter the user/pass when prompted

if this works, it's something in our settings addon that's not correctly trapping a response from dbus

if it doesn't work, it's something else .. and I have no idea

wrxtasy Original S905 is what I still use as the family daily driver so I wasn't aware of S905X/D etc. doing HDR > SDR.

It's not normal behaviour and 3B+ is fully supported. Update to the 8.90.003 alpha (which contains newer pi firmware etc.) and if the issue isn't resolved provide a Kodi debug log that demonstrates the problem.