Posts by chewitt

In 99/100 cases the failure is due to a lack of clean shutdown in Windows; Linux will not mount the "dirty" NFTS filesystem to prevent corruption. If you run "dmesg | paste" and share the URL we can see the mount failure in the system log and hopefully confirm.

Connman is integral to networking in our OS and something is abnormal for it to generate that many requests. If possible please capture and share a pcap of the box coming on to the network along with the system journal log for that boot.

The "fall creators update" removes support for SMB1 from Win10 so the Windows shares require SMB2/SMB3 connections. You need to use LE 8.1.0 or newer which has changes to support SMB2+ connections. All previous versions of LE only support SMB1.

Backwards seek is/was one of the main unresolved issues for AML users on Krypton and the 3.10 kernel used on WP1 isn't the focus for most of the developers. There are seeking improvements in the Leia codebase but that's still a long way from being stable or something we'll produce alpha releases for, and unfortunately Leia has diverged far enough from Krypton to prevent simple backporting of the changes. TL/DR; it is what it is until Leia comes along.

This is the correct way to put /storage on NFS: Network Boot - NFS - OpenELEC

That will not be the PERFECT solution because all we do is detect it's an old config and rename it out of the way. Samba will then start with our default template and whatever customisations you did before will still be missing. We make no attempt to fix your previous config .. that's your own problem to solve.

Worst that can happen is you miss the 5-second window to type run and then it boots into the graphical installer where to actually screw things up you need to select install to the internal HDD and confirm (twice) that you want to nuke the contents of the disk. Users never cease to redefine our boundaries for the definition of stupid, but assuming you're not it's a safe process.

It's usually a problem with the IPTV source and/or bandwidth. Share a Kodi debug log and we might be able to tell more.

Yes. Create an installer USB and when it first boots (at the bootloader screen) type "run" on the keyboard. The installer self-converts to a LiveUSB using the full size of the drive as persistent storage.

You have mail

PROJECT=Generic ARCH=x86_64 scripts/clean kodi
rm -rf build.LibreELEC-Generic.x86_64-8.2-devel/.ccache

^ run that and re-run the build, see if works?

You have banned add-ons installed. No further support will be provided.

Boot from the installer USB and the syslinux boot prompt type "run" .. and instead of running the installer it will convert itself into a "LiveUSB" with persistent storage. Then configure the laptop boot order to prefer USB .. job done. We do not recommend repartitioning the HDD, although that's mostly selfish and because if/when users screw something up we have no interest in walking them through the process of fixing things.

It uses an Allwinner H3 chipset that we don't currently support. It has a physically different board layout and other different technical features (it is not a clone of the Raspberry Pi despite their claims). It runs an unofficial aka community created version of LibreELEC (or OE) that we have zero knowledge or experience with; but it will be running the ancient (and crap) BSP kernel which is known to have a ton of problems. The best place to ask your question would be the OPi forum or the forum/place you downloaded the image from.

The Generic image should run on those boxes. The one caveat is that some BayTrail/CherryTrail devices require a 32-bit EFI bootloader and since ours is 64-bit the normal installer USB fails to boot. There is an image here Sendspace.com Mobile File that someone created with a different 32-bit bootloader (GRUB probably). If our installer doesn't work, use the alternative one to make the initial install, then update to the latest releases afterwards. The bootloader is only installed once, updates don't change it once installed.

infoalter do you have normal user account in Windows, or a "Microsoft ID" account, e.g. [email protected]?

Quote from 5schatten

But personally I don't see why those two should not be implemented:

That's because your Intel hardware works. Other Intel hardware has issues that were not previously present and that's not acceptable in a beta or final release build. This needs to be tested properly, and when it's ready we'll work it into an appropriate release.

If Samba does not start you have a v3 config file that needs to be removed or updated to the v4 template. Please read the release notes.