If you have an S905/X/D/W device and a spare SD card balbes150 testing images are available
Posts by chewitt
-
-
If it's not listed here: http://opensource.rock-chips.com/wiki_main_page
It's not supported.
-
The installer for the linuxserver.io repo is in our repo.
-
Install Docker. Use the linuxserver.io container for TVH. Even if you figured out how to download and repackage our TVH add-on we will refuse to support it on another OS.
-
Английский язык пожалуйста
-
As long as the SSD is in a USB caddy it should be seen as removable media that can be imaged.
-
RPi3 can boot from USB after it has been booted from SD card at least once with "program_usb_boot_mode=1" in config.txt to enable the USB boot capability. In the newer 3B+ the capability is enabled by default.
See: How to boot from a USB mass storage device on a Raspberry Pi - Raspberry Pi Documentation
-
Menion Until early Jan when panfrost first started working nobody was really able to do anything practical with a mainline S912 device so the current upstream device trees are known to have fallen behind GXBB/GXL configs. I know he has VIM2(s) and a Vega S95 box, hence:
linux-9999-fix-vega-s95-dts.patch
S905D and S912 are pin compatible so some of the more proven GXL device trees might be a better starting point?
-
Amlogic S905X2/D2/Y2 are the "second gen." devices. At the moment they are Android-only with negligible support in the upstream kernel.
-
@troggy correct, and there are a small number of legitimate add-ons that are only available that way (e.g. the iTV addon for UK). Some of the older 'bad' repo's have public mirrors which makes checking and downloading the add-on zip's without needing the repo a little easier.
-
No idea, Sorry.
-
It's not a topic that gets much airtime within the team. We trust the linuxserver.io folks to provide sensible containers.
-
mywatch Team Kodi regards the use of libhybris as a hack and will not support S912 images that use it. We care that Team Kodi will assist us with support and the Amlogic 3.14 codebase is in minimal maintenance mode. As such we have no plan to release any S912 images until we make the switch to mainline kernels. That work is progressing thanks to the awesome work from the panfrost (open source mali drivers) developers and there are some testing images available from balbes150 for curious users, but there are still some major bugs in panfrost to solve so mainline S912 images are not suitable for serious public testing yet.
As we have no plans for 3.14 based S912 images we stopped building nightlies a while back and I'm not aware of anyone on staff building their own images so the OpenGL debug function error you encountered hasn't been resolved in our codbease. If anyone would like to send a PR with the proper fix (adding support for the missing egl.h functions) we'd be happy to merge it. Otherwise CE have a hack that removes some Kodi code that will allow you to build images.
-
For many (many) reasons that wouldn't be a viable technical direction.
-
RTL8822BU has no in-kernel driver so we aren't going to add it and our distro packaging prevents you from installing it yourself. We are not interested to add ever-more out of tree low-quality realtek drivers to our images. We will sustain the current selection until LE 10.0 then changes we are planning will see only in-kernel drivers supported.
-
I genuinely forget what "echo somevalue > /proc/sys/something" hack is needed to force AP mode. I do remember that it never worked right and in the 3-4 years since I last tested nothing has changed in the Amlogic legacy kernel that would improve it. On that basis your options are limited to using a proper router or getting a USB external wifi stick (which is also a bit of a gamble due to the old kernel involved). If you value an easy life .. use a router.
-
Kodi maintain a list of known/banned add-ons and repos that we reference in our forum rules and users have to acknowledge our forum rules when creating an account.
-
If you updated from one of the initial test versions then passwords might be overwritten (once) as the password changes were added shortly before merging and the first run of the current addon would be treated as a first-run and would create/set passwords. However once you're on the current addon that shouldn't happen again. If it does, there's a bug to be investigated.