Posts by chewitt

Soli was the inspiration behind some of the changes in the 6.0.1 image and i'm happy to see someone pick up the baton. These days I simply don't have time to spend hours fiddling with ancient boxes. I also find the difference between an Amlogic S905 or RK3288 box costing $30-40 and ATV1 is too great, and once you hit that mental wall and move on it's hard to retrace your steps.

Pimoroni have shipped a replacement Slice PCB and PSU to my parents who will pass it on when we meet-up in Spain in a couple of weeks. As long as the CM3 card still works I should be back in the Slice business for a public beta of 8.2 in July and release in August.

Meanwhile lrusak is in the process of re-packaging the Slice drivers/firmware into packages we can embed into the Slice image(s). This allows us to drop a bunch of Linux patches and the build-system difference between RPi and Slice is reduced to two words in a config file. This makes it basically impossible for me to miss patches again - future breakage in a release will require deliberate sabotage. He is also creating a python add-on that hooks into Kodi to drive the LED ring. This allows us to drop the Slice Kodi patches and in the long-term we can make the LED patterns for Kodi actions user-configurable.

Kodi has a deep integration and dependency on ffmpeg so basically the answer is no.

Unless you tell us what WLAN chipset is in the box nobody can tell you whether the WLAN device is supported (or not) or what may be required to make it work. Saying "MXQ" box is like saying "I have a blue car" .. it tells us nothing.

First post is updated.

option "CustomEDID" is an nVidia-only configuration parameter so I'm not surprised Intel drivers don't like it, although segfaulting sounds like bad code design for error handling. That's not the issue though. Remove the custom xorg.conf and re-run the getedid script.

If codesnake submits a PR to 8.0 branch with the required changes I'll create an 8.0.2.1 image for Hub and release it; as 8.2.0 will be a while yet and releasing an 8.0.3 image will confuse users of other build projects that won't have something available.

Yup, I deleted the contents there and it will not be reappearing. Slice update/install images are listed under downloads – LibreELEC and/or the USB/SD creator app.

read post #2, we are not vulnerable

The major change between 7.x and 8.x will be things like mesa and the Intel GPU drivers. My gut feel says there's something in the Intel driver that dislikes the BIOS or firmware on your board, because it's honestly not something we've had reported before - at least not noticeably. LE has a large and vocal Intel userbase which isn't complaining. Have you tried a current Milhouse build? - aside from Kodi v18 (which is pre-alpha) this will have newer kernel, drivers, firmwares and mesa.

There is no plan to build any more 8.0.x releases so you'll be waiting for 8.2.0 which I'd guess is sometime we start working on in late July with release in August. I suggest one of you spin up a custom 8.0.2 image with the change.

Nope. It is a pre-compiled module not uncompiled source code, so it is no use at all.

If the system boots up *once* fine as stated in the issue report you can SSH in and run commands before rebooting.

Is this an Intel device or something from another vendor?

Is it running the latest available BIOS/firmware?

btw, the DRI2/3 change will cause graphic mess on-screen but will not cause hard lock-ups in the OS. On second reading of the description it sounds more like a hardware issue.

There is only one VNC add-on in our repo for RPi/RPi2 devices and it uses the dispmanx_vnc code. There are no known issues, so frequent disconnections sounds like a poor network connection. Are you using Ethernet or WLAN?

Sure. Anything that contains a known or undisclosed vulnerability that you expose to the internet can potentially result in a compromised system. LE has a few quirks (mostly read-only etc.) so it's not an ideal target for someone looking to use mass infection to create a botnet from, but that does not ultimately prevent it from being targeted or caught up in things.

wrxtasy  GDPR-1 ^ are we able to manage rtc_pcf8563 module loading from a udev rule, e.g. only load when hardware detected or some other feature present?

systemctl stop kodi.service
mv /storage/.kodi /storage/.kodi-old
tar -xvf backup.tar
systemctl start kodi.service

^ something like that will move the existing Kodi folders out of the way then unpack the backup to recreate folders and test by restarting Kodi. To make and restore backups and test them you'll need 2x-3x the size of the backup as free space on /storage