Profile data is always in a users home folder, which LE simplifies by having a single (root) user, and mapped to the persistent /storage area which is writeable. So each time the system boots the profile data is read, and whatever paths and such are needed for locales are set. There are also helper functions in the OS that know to search the binary addon paths for system.d, profile.d, udev.rules.d content etc.
Posts by chewitt
-
-
Hello. I have a Beelink GT1 Ultimate (gxm_q200) currently running Alexelec(coreelec fork) on SD.
I assume you're asking for help in here because the CE devs have no interest in supporting the piracy-ridden fork that rips off their efforts that you installed on your box. I'm equally disiniterested for a) the same reasons, b) because it's not even a fork of the modern-kernel codebase that LE uses today.
NB: As a random coincidence I created a device-tree for GT1-Ultimate earlier today for one of the Manjaro ARM devs to use, so support for the box should filter through to LE11 nightlies sometime soon.
-
Started working perfectly, thank you so much!! Edit: Also everything I've tested with video playback has been perfect and smooth!!
Nice to hear. Can you please share the URL from "dmesg | paste" so I can check the boot log.
-
My box is some custom model board from Geniatech sold in Portugal as TBee. Using the Nexbox A95X which also has a QCA9377 chip I get Bluetooth disabled by default, by activating the Bluetooth I get the "No Bluetooth adapter found" message again, but the dmesg is different
The Nexbox A95X device-tree doesn't have any references to WiFi or BT devices. WiFi gets found since it's attached to SDIO which is described and acts like a bus with connected devices, but BT is a serial device that needs to be explicitly described with device type or the kernel doesn't know what to probe for.
Please boot https://chewitt.libreelec.tv/testing/LibreE…85.0-box.img.gz - I've added an experimental device-tree for the box that should get BT working.
-
I was looking at picking up a Edal T95M (S905W 1/8g). Does anyone know if it is supported by this build?
`There is no specific device-tree for the box but other S905W devices may work. Don't expect anything greater than 1080p.
-
Hi. I tried the last nightly build on my S905X with a QCA9377 Wireless chip, Wifi is working perfectly but I don't have Bluetooth working. Any idea? Thanks. http://ix.io/41Fx dmesg
The P212 device-tree describes hardware with a Broadcom compatible chip, so the wrong driver is probed. What is the box?
-
Are there plans to make the .tar pack available again for nightly release updates?
There's no need, you can update from .img files too.
-
I'd asking the skin support thread in the Kodi forum. That normally reaches the author or current maintainer. I stopped using other skins ages ago as Estuary is nice/simple/reliable.
-
Systemd mount files are for mounting remote (SMB/NFS) filesystems, not sharing of local filesystems via SMB. To share a locally mounted USB drive you can just enable "auto-share removable media" in LE settings Samba options.
-
From the description of the problem it's not clear what the issue is, so best to share a sample of the file.
-
I moved things into a separate thread to avoid clogging up the main one with box recovery posts.
-
Does DVB-T2/S2 tuner work with this test image or not?
Only if it's a USB tuner with support in the upstream kernel. Everything dependent on ancient vendor kernel drivers is a firm no.
-
Hardware (and/or Windows) supporting DV is not equal to Linux supporting DV. As DV is proprietary closed-source magic there is not really any support for it outside of ARM device vendor kernels that depend upon more closed-source DV blobs to work.
-
..but should be supported in newer kernels, so the nightly will probably work.
-
I'd guess that u-boot has been corrupted or overwritten with an incompatible version. Assuming the eMMC didn't die the easiest way to get things working again would be to use Amlogic burning tool to restore the correct factory image for the box (from XDA forums or similar) so that the box boots (Android). Once it boots again, it's simple to boot an LE image. Alternatively you need to connect a UART cable to the box so we can see the early boot output - but this involves the box being opened and UART cable attaching, which may (or may not) require the UART pins to be soldered to the board first. From the level of technical detail in your posts, I'd suggest the restore-Android approach.
-
You cannot install drivers in LE, they need to be embededded (baked into) the image. You need to us the WiFi chipset and/or make/model of the WiFi card in the box. From there we can investigate.
-
There are multiple issues with the current 'update' functionality, and rearranging of files on the test server is not the most important bit that we need to resolve. Once the other pieces are done, easier updates for nightlies will be possible. There is no timeline - people have lives and families and things will be done as/when developers have time. Until then folks can update manually using .img.gz files (not .tar files) which has been supported since 2015.
-
S905X boxes should work quite well, S905X2 less so (unless hardware decode disabled) .. "but nothing" doesn't really describe a problem that would could respond to
