I've got no idea what the issue is or how to debug SATA initialisation problems, but I'll pass the observation that you're running tests on the drive *after* it is has completed initialisation, and it looks like the initialisation process is where the delay is incurred.
Can you connect the drive to an alternative SATA port? .. any firmware/BIOS updates available for the HTPC?
be adventurous and see what happens?
kostaman Rockchip: use default kernel name by lrusak · Pull Request #2690 · LibreELEC/LibreELEC.tv · GitHub will be the reason. Run the following to tweak boot config:
curl -sL http://milhouse.libreelec.tv/other/rkmigrate.sh -o- | bashThe update function looks for files in the .tar based on the current file naming in /flash so this script renames things to match what the update tar now provides. The decision for a disruptive rename was allowed because at this current pre-alpha release stage user numbers for RK images are small and we'd prefer not to immortalise hacky workarounds in the update function.
The other alternative (for those scared of scripts) is to backup, reinstall with the latest .img and then restore the backup.
So that means there are no discrete GPUs (under $100 at least) that supports 10 bit HEVC in Libreelec? Only option is Gemini/Kaby right now?
Yup. It's a sucky situation and that's one of the reasons we've been working on a next-generation rendering/decoding pipeline that extends Kodi (on Linux) support to a range of other SoC types so people have more hardware options in the future. It's not going to change the discrete GPU situation though. They're somewhat out of fashion these days.
Does this mean we'll also get HEVC 10 bit support on the GT 1030 via ffmpeg 4.0 (NVDEC)?
No, because NVDEC requires EGL streams which Kodi doesn't support.
LE 9.0 still supports nVidia under X11 with the binary blob drivers which provide VDPAU; so everything is 8-bit and no HEVC because nVidia stopped developing VDPAU some time ago. AMD rewrote their formerly VDPAU using drivers to use VAAPI (common with Intel). Kodi v18 is currently broken with VDPAU due to X11 windowing code changes but the main developer that supports X11 has indicated he plans to fix VDPAU support when a replacement test box arrives. Current hardware had some issues and was terminated with a pickaxe. No joke, we have video 
LE 10.0 (Kodi v19 so still a long way off) will drop X11 completely and switch to DRM/GBM and KMS (running on the framebuffer, no X11). This works well with Intel/AMD (which dominate user choices) but currently has zero support for nVidia chips because nVidia is solo-championing their EGL streams alternative to GBM buffer sharing. The two current problems are: a) VDPAU is dead code and right now there's zero appetite from Kodi developers to add another proprietary code path for a closed source driver when *all* other GPU/SoC types we plan to support in the future use GBM/KMS, and b) we had a look at EGL streams recently and it failed to run due to nVidia driver bugs. There is a lot of time to kill before LE 10.0 is a serious proposition and we'll maybe look at EGL streams again, or maybe nVidia comes to their senses and uses the same rendering standard as everyone else?
in the long-term cheap 'Android' boxes/boards will be better all round value for client boxes than x86 kit, except for boxes used as PVR servers, but those don't always need to run Kodi or have the latest GPU in them.
I know that but i have several graphic artifacts at startup and shutdown with LibreELEC 8.2.5 and Raspberry Pi 3 Model B, LibreELEC 7.0 does not start. So i'm trying to build old releases.
RPi 3 hardware was released in Feb 2016 so the OE 6.0 codebase which predates that by a year? is not going to boot even if you do figure out the missing package dependencies. LE 7.0.3 should be fine. NB: Running older software likely introduces more bugs than it might solve, so a current milhouse testing release (newer everything than LE 8.2.5) is probably more productive; and if the issue still exists, report the problem to the milhouse support thread in Kodi forums instead of working backwards with old code.
That's because the download page only advertises things we officially/formally support and the vmware OVA image exists for developer functional testing and making instructional videos to put on YouTube.
Adding a Canadian NTP server just results in you performing time checks against a geographically closer server instead of a randomly assigned NTP server. It makes no difference to the NTP response (all NTP servers provide UTC). To change the timezone offset from UTC; configure the timezone in Kodi Settings > Interface Settings > Regional .. or something like that.
^ the driver is already enabled in our kernel configuration, so assuming it's MT7601U and not MT7610U (which is not supported) it's probably a case of the current driver not knowing about the USB vendor/model ID's of your dongle.
SSH in over Ethernet and run "lsusb" and share the output, then we can suggest some ideas.
Virtual was rolled into Generic starting with 8.2.0 so you can use libreelec-generic.x86_64-8.2.5.ova
OS mounts using systemd have nothing to do with Kodi SMB client configuration in user.conf .. which isn't used at all when accessing the now-local folder at /storage/timecapsule (only when Kodi accesses an SMB share over the network). The same configuration can be done from the GUI btw, if you set max/min to SMB1 and select the "legacy security" option.
I suspect you just forgot to enable the mount before, which has now been done.
You have to reboot the whole OS not just restart Kodi. What does "systemctl status storage-timecapsule.mount" show?
LE uses alsa for Kodi audio by default but there is also basic/limited pulse support to allow for routing audio to a bluetooth speaker which needs pulse. To get pulse effects working you'd have to custom compile the distro image with extra packages and assuming you get past that hurdle you'll need to figure out how to configure effects from the console. The slightly condescending but usually true "rule of thumb" on major changes is "if you have to ask how it's done you don't have the skills to do it" .. so if this is an essential feature you'd probably be better off using Ubuntu as the base OS for your HTPC build as Kodi on Ubuntu uses pulse by default and there are pre-build packages for pulse effects so installing things is simple.
NB: Kodi almost had what you're looking for with ADSP add-ons, but sadly the work on ADSP (which has been ongoing since Kodi v16) has stalled in the last year due to the sole developer not having the time to work on it. Recent core changes broke ADSP code paths and code was recently removed until a future date when things are in a more complete state.
LE installation simply creates two partitions; 512MB and 100% of remaining space. We install the syslinux bootloader with a conf file but we don't actually care which bootloader is used, so if you prefer grub (or grub is the only one that works on your box) go use it. Ubuntu uses grub so that might be a good idea. You simply need to set boot= and disk= in boot params to indicate which partition contains the KERNEL and SYSTEM files, and which one should be used as /storage.
It's also /storage/.config/system.d not /storage/.configfiles/system.d
There is no reason to create a .mount file in /storage/.config/sysctl.d
LibreELEC 6.0.3 is not supported anymore, so you are very much on your own.
LibreELEC 6.0 doesn't exist, we forked and started our releases at 7.0. Anything before then is someone else's problem
