Posts by chewitt

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.

He also sent the wrong log, i.e. didn't follow the explicit instructions given. Ho hum..

cd /storage
systemctl stop kodi.service
rm -rf .kodi/temp/*
tar -cvf backup.tar .kodi .cache .config
systemctl start kodi.service

That's basically what the backup routine does (except the cleanup of temp, which is just a good idea). Watch the on-screen output for errors, warnings and long time delays where it gets stuck and has to wait for something.

No, it's an archive file (tar on Linux is like zip on Win). Create a new install using the normal install process then restore the backup. The amount of time you spend looking for a one-step "does everything" process/tool is longer than you'll spend doing the two-step restore.

devtmpfs 804.5M 134.0M 670.4M 17% /storage/.config/acestream/dev

^ acestream is a piracy tool. No further support in this forum.