I'm not reacting to length of cable, more to the fact that you changed cables.
Posts by chewitt
-
-
50m cable runs are starting to get long and you're not connecting two powered switches; one end is a lowly Pi board. So what happens if you go back to using the old (shorter) 30m cable?
-
Copy/paste touch /storage/.config/safemode.disable on the command line .. done.
-
If you're seeing the same issue on two different OS images it looks like the device has a failed SDIO wifi module; although the BT section (which is on the same module) looks working which is unusual. I guess if you're only using Ethernet it's not a big deal.
Boot times on mainline are way lower and I find the entire OS to be lighter and more focussed. The only thing that's still "work in progress" for an S905 box is hardware video playback which still needs some rework after recent kernel-side changes. If it works for you, you're welcome to use the nightly images. If not, stick to 3.14 for a while longer. WP2 will be broadly similar, the only exception is that 4K might work as it has 2GB RAM so the currently insane CMA memory allocation needed for that is possible vs. the Hub which is 1GB and needs to wait for some memory use optimisations.
-
Are there any settings I can adjust to fix the built in wifi throughput?
As a rule software cannot fix a hardware problem. Most internal antennae are an afterthought. Connecting a proper external antenna will fix reception issues, but that probably requires a dremel and some handicraft on the NUC case

-
RPi3 remains the benchmark for 3D support. RPi4 has more oompf but a different SoC/drivers and many things with a higher priority for development effort than 3D.
-
It's hacked into meson-gx.dtsi so that all GX devices inherit the same config. See:
HACK: set meson-gx cma pool to 896MB · chewitt/linux@3c771f1 · GitHub
-
I've reported this to connman devs already .. the Jira is Intel staff only and hardly used. The mailing list is the other place to raise issues.
-
Diff
Display More--- a/projects/NXP/devices/iMX6/linux/linux.arm.conf +++ b/projects/NXP/devices/iMX6/linux/linux.arm.conf @@ -861,7 +861,8 @@ CONFIG_IP_PNP_DHCP=y CONFIG_NET_IP_TUNNEL=y # CONFIG_SYN_COOKIES is not set # CONFIG_NET_IPVTI is not set -# CONFIG_NET_FOU is not set +CONFIG_NET_UDP_TUNNEL=y +CONFIG_NET_FOU=m # CONFIG_NET_FOU_IP_TUNNELS is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set^ that probably fixes it
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Code
<source> <name>CinemaM</name> <path pathversion="1">smb://username:[email protected]/VIDEOm/Cinema/</path> <allowsharing>true</allowsharing> </source>Create a user for Kodi, assign rights to the share for that user, and authenticate with that credential, e.g. ^
-
I forgot how full of irrelevant verbose garbage 3.14 kernel logs are

For comparison purposes put LibreELEC-AMLGX.arm-9.80-devel-20200314152345-6c08564-box.img.gz on an SD card, boot and install and then share the logs. You'll need to set dtb=/dtb/meson-gxbb-khadas-play2.dtb in uEnv.ini.
Let's see if we get similar SDIO errors.
-
what is the current state of 3D MVC capability on RPi4B?
Non existent.
-
phil2sat see if this works: meson-gxm-mecool-kiii-pro.dtb.txt (rename to .dtb)
-
Samba (server) in LE settings has nothing to do with the Kodi SMB (client) capabilities. My guess is the Windows box doesn't support SMB2 and needs to have min/max SMB1 set in Kodi service settings. Or you need to check the source configuration in /storage/.kodi/userdata/sources.xml.
-
Track the YouTube plugin thread in the Kodi forums. If there's an issue it's not LE specific.
-
Not possible. Current RPI4 support is deeply written around Leia and future support is written around Matrix.
-
Refusing to support RAID (and disk encryption) is about keeping our distro images small and keeping what our all-volunteer team has to provide user support for simple. RAID is not "risky" but there are 20+ flavours of RAID and based on user requestts there isn't one thing we can add, so we end up being asked for many things and many tools and .. we have always tried to avoid "the death of a thousand cuts" where we keep adding little things that cumulatively lead to LE being yet another bloated general purpose Linux distro instead of the focussed and minimal Kodi client distro that we are (and always have been).
There are many distro choices that support Kodi so there's probably another with package management so you can add the RAID and other thingst you are interested in. You also have the option of taking our codebase and modifying it any way you like. That's the fab thing about open-source.