Posts by chewitt

Some of the Q's have complicated answers. Ping us in Slack (as you have access) and we'll help get things up and running.

I pinned the thread so more people find it. Please focus on the mainline investigations

Sadly "user reports bad behaviour from Amlogic legacy kernel sources" is not surprising or something anyone will investigate. We have abandoned that kernel (which is full of bad, period) in favour of the upstream/mainline kernel which is maintainable, although that work is still ongoing and current test images you can find on Index of / are not fully featured. It's a bit of a "rock and a hard place" situation, sorry.

OE used a 230MB boot partition and the image LE currently ships is a little larger (we have used 512MB for the boot partition since 2016) so you either need to use some kind of bootable USB/CD with tools to shrink and move the storage partition so the boot partition can be expanded, or you take the easier and much faster option; create the installer USB and boot from it, and then create a new LE install. The image you posted shows 256MB of data on /storage so you didn't do much yet .. it will be easiest to clean install and start over.

SSH to LibreELEC (we ceased being OpenELEC in March 2016) and run the command then reboot.

You can download images built from the LE master branch from Index of / but the development focus in master is about moving from MMAL to GBM/V4L2 which is still general work in progress. You'll probably find the images are overall less usable than current 9.2 images.

Allwinner devices are supported under the LE master branch not the 9.2 branch. I don't want to appear rude, but if things don't build under 9.2 we're not interested in investigating.

Sounds like something broken on the Kodi (or mirrror) side. Nothing you can do locally. If it's still and issue (hasn't resolved itself) you need to flag it in the Kodi forums and include the full debug log - not just snippets.

If you see the same problem on multiple OS it's likely to be a hardware problem, either something physical in your setup or a faulty board (rare but not unheard of). HDMI should be connected to the port nearest the USB C power connector .. and you need to share a Kodi debug log.

RPi4 supports H264 in hardware to 1080p (same capability as the RPi3) and above that will be software decoded though this is way beyond the CPU capabilities of the hardware. H265 is supported in hardware to 4K (new capability for RPi4). Some people see the lack of 4K support for H264 on the RPi4 as an issue, but as no broadcast formats use that combination (only test files and deliberately encoded media) it's not a real-world problem.

Most of the whiny threads about RPi4 video issues in the LE forum are caused by people not understanding how to use the whitelist and/or forcing deinterlaced media (which needs 50/59.94 modes) to run at 25/29.97 refresh rates, often at 4K resolution, which is never going to be good. I've never been a big Pi user as I always had other toys around, but I've been using RPi4 as the daily driver for a while now and I don't see any major issues. I don't care about 3D support and other niche things RPi3 excells at though. Firmware updates continue to address minor nits in RPi4 behaviour (e.g. heat) but software support has generally come a long way in the 6-months since launch. HDR and higher-bitrate audio support are still missing but they don't exist on older hardware either and neither are simple additions. There are other higher-priority items for the RPi Foundation to work but they are being worked on in the background.

Hard to tell as the software support link on the page fails and the more detailed product specific pages are blank on details. I'd guess the device-tree overlays (or revised device-tree files) are required to make these devices work on the mainline kernel; which not a huge thing to do but something that would need to be done - and Radxa are the people to do it, not us.

Nope, it still has a completely unsupported SoC.

It already works .. so what more answer do you need?

"it's similar" or "it's a cut down version of" means "it's different" and thus images are not likely to work without explicit changes for that chipset, and now that we dropped support for the Rockchip 4.4 kernel and moved Rockchip support to mainline Linux 5.4/5.5 kernels device tree files for the 4.4 kernel are even less likely to get an output/result than before.

Kodi debug log output (full log) will tell us more technical detail about your setup and media than your text description.

echo "options cfg80211 ieee80211_regdom=AU” > /storage/.config/modprobe.d/cfg80211.conf

^ I'm 99% sure this will fix things assuming you're using the onboard pi wireless. If the regulatory domain is not set, it defaults to 00 which is a global safe default that will be missing a variety of channels and other radio properties depending on where in the world you are.

Kodi only references the EDID data necessary for audio/video config once at startup, so if the HDMI monitor isn't on/connected before Kodi starts it sees nothing after you turn it on. You can dump the edid data to a local .bin file and then configure xorg.conf to always use the .bin file. This makes the nvidia driver (and Xorg) behave as if it's connected to the monitor, even when it isn't connected. This behaviour has been the same since early OE days so you probably did this once on the OE install and then forgot about it. See Custom EDID [LibreELEC.wiki]