Posts by chewitt

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

No idea, but since you are clearly playing stolen (torrented) media, support stops here.

I've confirmed via private channels that Gordon is aware that it's dead. I've not received any explanation or confirmation/denial that it will spring back into existence. At least for now I get my wish that people would post here for issues with the LE images ~ I get bored of checking in multiple places.

You're preaching to the converted. The difference between OE and LE is that one-man-project OE enabled Samba 4 without testing first. LE likes to test and so far we noticed some issues with Kodi (which depends on the OS libsmbclient implementation). We are still investigating some changes and dead code clear-up in Kodi, e.g. removing incorrect smb.conf configuration and hacks that date back to Xbox days.

I dropped a note to distrowatch asking them to amend our profile and remove i386. It's still technically possible to create i386 images if you add back support to various build-system packages and compile the image yourself, but it's not something we'll do officially.

Not currently, but it will be possible in the future once the changeable passwords PR has been merged.