Intel and RaspPi are the only two manufacturers who will get reliable Kodi support in the future.
I look forward to making you eat your hat in the future. Seriously ![]()
Intel and RaspPi are the only two manufacturers who will get reliable Kodi support in the future.
I look forward to making you eat your hat in the future. Seriously ![]()
I wouldn't expect a mainline release for K18 (LE9.0) at this time.
I'm already running an LE image with K18 and a Linux 4.17.3 kernel on S905+ devices but the codebase needs to hit some milestones before we invite public testing and feedback. The core OS is solid but audio/video are still in a proof-of-concept state. LE is orchestrating the current activity on Amlogic mainline audio/video things and one of our extended team also contributes to Armbian; so once things are useable Armbian will see some updates too.
You can install Kodi add-ons that contain binary apps (as network-tools does) but there is no apt-get or equivalent in the OS. So you either add things to extend an existing add-on package (and then submit changes to our git repo.. or not) or you create new ones (and submit them to our git repo.. or not). I think the questions you're asking show you're not familiar with how LE is build/packaged, so before you run away with ideas of reconfiguring LE to be OpenWRT go find the "self-build" instructions in the wiki and compile an image. There are no instructions on how to add more packages to the OS, but there is a ton of "prior art" in our git repo. From past experience; if people have the skills and knowledge to succeed in that kind of task .. that's all they need to get started.
LibreELEC.tv/package.mk at master · LibreELEC/LibreELEC.tv · GitHub
^ that's what it contains. Devs generally have no objections to adding other binaries to the tools package, but it's up to the people that want something added to test and submit the required/desired changes. As a broad rule we'd also want to focus on things that have a use case beyond one person. I think this is the first post to mention RADIUS in the 7+ years I've been hanging around LE/OE etc.
I'll also pass the general comment that if you want a router/firewall distro .. use a router/firewall distro. LE is neither.
Kodi has no limit on the number of sources you can have so you should expect to have more than one folder for music to manage different scraper requirements. In other words; the correct answer is in post #2.
As v8.2.5 is very likely to be the final release of the Krypton builds
No "is very likely" .. it is the final Krypton release.
SSH works fine, but 99% of the filesystem is readonly so you cannot edit things in /etc and if-up.d doesn't exist because we use connmand as the connection manager. You can use "route add" via /storage/.config/autostart.sh which is run at boot time (before networking starts so you need to background and sleep the additions).
No idea about BT modules, but you should consider that C2 is currently stuck on a shitty 3.14 bsp kernel so BT support is well out of date.
Building with only nvidia shaves a few MB off the total image size which is nice, but if you want to keep-up with our main releases I'd aim to make the smallest number of changes as possible. So the rule is: add only what you need and remove nothing if possible. The resulting image doesn't score kudos points for being minimal but it's significantly less effort to sustain over a long period of time.
It's probably unrelated, but it looks like you screwed file permissions as every file has been changed from 644 > 755, and some of those files are scripts that will be copied with current perms intact into the LE image. You need to clone to the git repo to a Linux filesystem like EXT4 to keep the perms intact. I'd hazard a guess that you've cloned to something like NTFS "because working on Windows is easier" .. but it will ultimately cause more problems than it solves. Changing every file also means people have to 'page down' about 500 times to review all your changes .. which means nobody it likely to review them. Commit the changes for each file you touch (usually package.mk's) so that others can follow them.
That script should be burned at the stake for causing support problems and it is banned forever from any official releases. Running from SD card is working.. take the hint.
Check ownership id's and permissions. LE runs as root, but root still needs to have access.
need driver for the usb wifi card Archer t4uhp (chipset rtl8812au (device ID 2357:010f))
ping CGarces is that device ID in the 8812au driver?
what filesystem is on the /var/media/SHARE device?
^ You need to compile your own LE image with that option set to =m and then the module will be present.
systemd starts after the boot config already mounted the second partition on the SD card to /storage and since everything is hard-coded to use /storage/.kodi you cannot then mount another partition to that path. If the other partition is EXT4 you can always switch the boot config to mount the partition with the .kodi folder you want to /storage instead - assuming this is not shared with some other OS as that's generally a bad idea as Kodi settings are OS specific.
What git repo/branch are you actually trying to build ?