Current LE12 or L13 nightlies will solve the issue (100% this is the newer chip needing newer mesa). LE 12.0.2 will be along soon-ish to roll up this issue.
Posts by chewitt
-
-
"This only works for Home Assistant OS, running on Raspberry Pi. Not for Home Assistant Container."
^ simply means you cannot run the Pironman add-on container inside the HAOS container; because the Dockerfile for the add-on assumes a desktop OS is present, and the HAOS container is (like most containers) a stripped-down/minimal OS environment.
Adapting one of the existing Pi case GPIO fan-poking add-ons is probably the easiest option.
-
sparkplug have you added dtparam=pciex1 to /flash/config.txt?
-
I'm moderately confident the answer will be "the Linux drivers only support up to 384Khz" but please restart Kodi in debug mode, run "pastekodi" and share the URL so we can see audio properties and (hopefully) identify the kernel drivers being used.
-
LE runs Kodi without a desktop environment so the plumbing for e.g. Xorg/X11 graphics or Wayland are not needed and absent (minimalist distro and all that). The OutFox instructions look written for RaspiOS (Debian) which is more conventional and I don't see anything obvious in Google searching.
You probably need to reach out to someone on their forum or Discord chat. In short, you need to run OutFox under GLES on an OS with no desktop environment. This is sometimes described as "running on the framebuffer" although that's not technically correct these days - but might help people understand.
Docker won't help because the container cannot directly access graphics hardware to render anything.
-
-
USB SSD drive mounted for extra storage or NVME device attached to the PCIe connector you want to boot from?
-
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 -
Is the wifi chip supported at all?
The upstream device-trees for Amlogic reference boards describe a Broadcom WiFi module and your box probably has something else inside. QCA9377 would be my guess for an S912 box, but others are possible.
The "box" image here: https://chewitt.libreelec.tv/testing/ includes a patch that removes the Broadcom specifics to allow other WiFi modules to probe and work. If that's the case, please report back and share the log URL from "dmesg | paste" - You can wget the image to /storage/.update and reboot to udpate.
If that image doesn't work you'll need to share a log from the original Android kernel or other working Linux distro or share photo's of the board so we can understand what chip/module is inside.
For context, here's the patch (sent to kernel mailing lists this morning by random coincidence): https://patchwork.kernel.org/project/linux-…[email protected]/
-
The HomeAssistant "add-on" seems to be running things in a Docker container, see https://github.com/sunfounder/hom…man5/Dockerfile - which might be a simple (albeit heavy) way to run things. The Dockerfile needs minor tweaks to replace variables with content to be used on LE.
From a quick glance at https://github.com/sunfounder/pironman5 it's probably not that hard to make a simple Python script to poke the GPIO bits required to change fan speeds. Elsewhere in this forum you'll find an add-on for the Argon40 case which also comes with a fan and will be doing essentially the same things, though possibly with different GPIO pins being toggled.
Sunfounder seem to be maintaining the integrations for other OS, so might be worth asking them to look at LE too.
-
Was this a clean install? Because based on the amount of installed addons, I wouldn't guess that.
Due to those add-ons being installed, support ends here too.
-
We have been using the same syslinux bootloader for aeons (unless EFI booting, but that's similar) so the drive should be movable between devices. You might need to reset the audio config afterwards as device names might/will change, but that's probably all.
-
No issues connecting to the repo from here (and the repo is not mirrored)
-
The Nexbox A95 device-tree file in the upstream kernel defines no SDIO WiFi module, which normally means the module will not be probed and detected. It's possible the module is connected via USB instead; it's nnot unheard of but unusual in Amlogic boxes of that era. Ampak modules are normally using Broadcom chipsets, but which one? Logs from the Android/vendor kernel are needed else there are more questions than answers.
-
Some discussion/info on USB WiFi devices supported upstream: https://github.com/morrownr/USB-WiFi
RPi boards are best with cases that provide passive cooling, then there's no fan noise. The Flirc cases are great. No preferences on fans .. they're all much the same and what's available locally for you will be different for me and others.
-
I notice, with the latest bump of Kodi in both the nightlies and chewitt's experimental builds, the GUI no longer renders on my Odroid C2
I've pushed an update to the images in my share with that patch added.
-
This is a forum for solving LibreELEC issues, not reviving dead Android boxes. You're better off asking in an Android focussed forum that might have an archive of Android ROM(s) .. this is not one.
-
It's on by default and accessible with libreelec/libreelec credentials. You can change that in the LE settings add-on. If you want to fiddle with deeper samba features you can rename /storage/.config/samba.conf.sample to samba.conf, make edits, then reboot and your conf will be used instead of the embedded one.
