Posts by chewitt

No debug log demonstrating issues = no problem to investigate.

You can post logs and dig into things all you like but this is a driver issue that needs to be fixed by nvidia. Let me know when you get a support ticket, because then (and only then) I can enquire with their support team.

You have pirate add-ons/repo's installed. No support is provided to users of that crap.

Nope, and I would discourage anything from being created because users get very OCD about "performance" numbers and raw metrics on CPU etc. are misleading on the overall performance and experience of a device.

Faster I/O on the card will always help the overall LE/Kodi experience, but the "slow" I/O on the card is still many times faster than your ISP connection so buffering issues are about ISP/latencies not hardware. The read-ahead setting in the buffer can be increased, but cache tweaking only ever solves local network performance issues, i.e. bursty wifi and drop-outs, not "my internet connection isn't fast enough" type issues. As a broad rule unless your internal network is crap (in which case the solution is fixing your network) cache tweaks should not be needed.

There is nothing we can do to make it appear. Our end is good, and we have no idea which mirror you're talking to.

I've seen a couple of reports (on other builds, it's nothing Slice specific) where people aren't seeing 8.0.0 in the lists of available manual updates. This can only be an issue with mirror servers as the JSON file queried by the settings add-on is 100% correct on our servers.

There have been similar reports from internal testing but it's not been something we've been able to pin down.

100% not supported, thankfully..

An occasional spring clean is never a bad idea.

If you boot noobs lite you can just install LE from the menu - it will install 8.0.0 since an hour ago.

If you want to add LE to an existing noobs install the files required are here:

LibreELEC-RPi.arm-8.0.0-noobs.tar (RPi)
LibreELEC-RPi2.arm-8.0.0-noobs.tar (RPi2)

add "debugging" to cmdline.txt and you will see on-screen output from journald that is normally hidden; it might give you a clue

Chromium doesn't exist for RPi hardware (it needs Xorg) but you can install the YouTube add-on from the Kodi repo.

It would be a good idea for someone to run the nvidia bug reporting shell script that's included in the Linux driver package against an affected system and submit the bug report to them - don't ever assume someone else has reported the issue and it's known/being worked on. Once you get a support ticket, share here or PM to me and I can run enquiries with their driver team.

run "lspci | paste" and share the URL it generates so we can see what chipset is on the board; then we can figure out what might be needed

It's not possible. You can try asking the Estuary v2 skin developers for an enhancement via Kodi forums.

systemctl stop kodi.service
mv /storage/.kodi /storage/.kodi-old
systemctl start kodi.service

will give you a clean Kodi instance without reinstalling. It's easy to stop/start Kodi to move working bits of the old configuration to the new one.

dmnc If you're using an Intel GPU device you will need to enable DRI3 via xorg.conf to avoid the graphical issues. It's not possible for us to set that by default as it screws things up for too many people (not a large audience, but a lot more than a handful).