Posts by chewitt

Just plug it in

I'm wondering if this is why AirPlay isn't working in master (at least for me) ?

On what hardware? .. we need a volunteer to test a connman change that should resolve these issues. As none of the staff experience the problem we've not been able to test it.

Sure, if you can find a reliable source for the drivers and create a build-system package then compile them into an image.

Quote from Wizzi07

I’m currently running kzaqs 8.2.1.1 on S912 device.. could somebody please tell me what’s the benefits and drawbacks of upgrading to this build?

"if it works, don't fix it"

At a Kodi level there isn't a significant difference between the two distro's so it's an unusual report. I'd be interested to hear what happens if you 'update' to progressively older LE releases which have 17.5, 17.4, 17.3 code. OE 8.0.4 has Kodi 17.3.

NB: How it behaves on Krypton is now irrelevant for debug/fixing purposes because there will be no more Krypton releases and there are lots of changes to PVR in the Leia codebase. If you find/test an Leia image and it's still an issue, report it to Kodi developers via Kodi forums and it will be investigated.

Windows 7 might require max client protocol in Kodi forcing to SMB2, and authenticated access to the shares. Worst case you can force Kodi to SMB1 but that should really be avoided.

It is not possible to install drivers, they must be compiled into the OS image.

nb: This is an English language forum.

Linux does not create /dev/sda0 nodes; numbering starts at /dev/sda1 and a default install of LE will either use UUID's or boot=/dev/sda1 and system=/dev/sda2. Check the bootloader configuration for a typo.

At the current time THERE ARE NO BUILDS FOR ALLWINNER DEVICES released by the LibreELEC team. Please save your breath and our time by not creating "is <device> supported?" posts, because whatever the device is, it's not supported. Elsewhere on the internet there are some LE builds circulating. These appear to be based on old kernels, old drivers, old hacks for Kodi, and we don't know what else. They are nothing to do with us and we have no knowledge about who is creating them or why anything does or doesn't work in them.

The current Allwinner development effort in our GitHub repo centres on modern kernels and uboot, and will ultimately use V4L2/mem2mem decoding with GBM/DRM rendering in Kodi. Some of this work depends on future V4L2 kernel changes not scheduled to be finalised until Q2-2018-ish timeframe, and at the time of making this sticky post an interim video driver is only partially written. TL;DR: If you clone the allwinner development branch in our github repo at the moment you will not get a working image to play with. The core OS probably boots but Kodi will not run. Again, save your breath and our time and please wait patiently until there are official announcements and alpha/nightly type releases have started.

Thanks

UPDATE: 23/7/2018 ref. to: Delivery of Allwinner VPU driver main goals - Bootlin's blog

As part of their work on the DRM driver the bootlin team have shared an LE image. At the current time their codebase is a little behind our master branch and further behind current Kodi master branch. The majority of their code has been actively developed in collaboration with our developers working on other SoC platforms, but we need to adapt their concepts in a couple of areas so approaches remain unified over multiple SoC/GPU types. We are also waiting on mali GBM libraries to be released for the H6 chip, and we haven't spent much time on distro packaging. Most SoCs have a long list of minor hardware support niggles when bumping to mainline kernels (device trees, drivers, etc.) and despite a sizeable and active user community we expect Allwinner hardware to be no exception. So we are still some way from releasing public images, and we are only just starting to think about specific device support. As a broad sweeping rule LE strongly favours 'boards' over 'boxes' as they tend to be better made and better supported devices, so that's where our focus will start and likely remain.

From that description nobody understands what you did, what's installed, what LE is installed on, etc. - and nobody can help you.

run the same build command again .. you get a new image with the changes

Incomplete "work in progress" at the moment.

If it works, it works, and does no harm.

echo "(sleep 10 && /bin/bash /path/to/acrecalbox.sh)&" > /storage/.config/autostart.sh

^ something like that should work, depending on what acrecalbox.sh contains?

The allwinner development branch in our git repo is (or will) use DRM/V4L2 for video output. The V4L2 driver is still being written. It will not currently result in a working image. Lakka has quite different (more simple) video requirements.

NB: There are some other H3 sources out there which use an older collection of OE era hacks to create a "working" image, but these are based on an outdated approach and are nothing to do with us.

Use an SFTP client and transfer things to /storage/.kodi/addons and /storage/.kodi/userdata

Download the zip to the Pi device and unpack to /storage/.kodi/addons then run SQL commands to 'enable' the addon. IMHO it would be a lot easier to install the Windows version of Kodi on the Notebook and use that until a new TV is sourced.