Create the USB .. boot from it and unless you hit the keyboard in the first few seconds to start temp/permanent 'live' (run from USB) modes it will start the installer GUI which asks you to pick a storage device (i.e. internal drive) to install to.
Posts by chewitt
-
-
^ according to that it has an RTL8812AU chipset which we have driver for (although devices breed new USB ID's sometimes). There is a caution note that there are multiple revisions in circulation. So it probably works. No guarantee though. And before you ask, no we don't recommend devices. I'm happy to share my personal opinion that all Realtek devices are sh1t though .. due to out-of-kernel unmaintained drivers.
-
Kodi is not designed for (and does not support) cross platform profile moving. You can try literally copy/pasting the userdata folder files over .. but I doubt it will work reliably because there are fundamental differences in file paths and some Kodi settings.
-
*debug* log .. not normal log
-
Moved to the Amlogic community section where hacked-up versions of Kodi are 'supported' by their creators.
-
Reboot after installing. Fixed? .. in which case it's about the environment PATH not being set until reboot.
-
"lspci | paste" would be more useful, assuming it's connected to the PCI bus
-
I don't want to appear rude, but Leia is pre-Alpha code. Bugs are normal. If you don't want bugs .. don't run pre-Alpha buggy code. If you want to participate in bug hunting the development threads in the Kodi forum are the appropriate place to provide feedback.
-
Nope - drivers need to be baked into the LE image. You probably need a development version with newer kernel and firmwares .. and even then you would need to tell us the chipsets in the device to get a factual answer on support. As a rule we support stuff found in HTPC boxes; which is likely a bit different to what's found in a Surface.
-
There is a VPN client add-on in our add-on repo. VNC is not VPN.
-
LE 8.2.1 should be out within 24h
-
I didn't read the other threads etc. because if the people in Kodi forums don't know, the same people in LE forums will not know either. Have you done a proper clean install?
-
You need to disable the on-board wifi via overlay and connect an external USB wifi dongle. The onboard Pi3 wireless has a crap antenna and there is no software fix for that problem.
-
It depends on what updates/patches are applied to Win10 which is why there is no definitive answer. The fact it's on a pi is irrelevant. If the box is up-to-date MS now prevents access to shares with 'guest' rights so you need to enable password protection on the share via LE settings.
-
Code
[ 3.233361] ata2.01: failed to resume link (SControl 0) [ 3.244742] ata2.00: SATA link down (SStatus 4 SControl 0) [ 3.244766] ata2.01: SATA link down (SStatus 0 SControl 0)^ It's not an error that I recognise .. but 9/10 of the "it works in Windows but not in Linux" USB drive issues we see are about cheap SATA bridges with poorly written firmware. It could also be a port issue on the HTPC device - what box is it?
-
Code
17:23:46.186 T:140435866674944 ERROR: CCurlFile::FillBuffer - Failed: HTTP returned error 401 17:23:46.186 T:140435866674944 ERROR: CCurlFile::Open failed with code 401 for http://api.themoviedb.org/3/search/tv?Have you disabled automatic add-on updates in Kodi ? .. ISTR an API key was being abused and was revoked, but an updated version of the add-on was published with a new key to resolve it (or something like that).
-
Kodi still needs a bunch of rework to work with their new stuff, and right now that development has a much lower priority than all the standardised graphics stuff that won't require so much jumping through hoops.
-
Make sure you safe eject from Windows else the NTFS volume is 'dirty' and Linux will refuse to mount it to prevent filesystem damage. If that is not the issue run "dmesg | paste" and share the URL (after a clean boot, with the drive connected) so we can see what the kernel thinks.