Posts by chewitt

    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.

    linux.arm.conf#l1373

    ^ 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.

    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.

    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.

    I would advise against nvidia purchases. Long-term LE/Kodi support for nVidia GPU's is questionable due to nVidia (again) choosing to set their own 'standard' instead of following the one used by literally everyone else. I'll be writing a blog post about them soon.

    UsePrivilegeSeparation=yes makes sense in a conventional distro where you have multiple users and it is desirable to limit the code that runs with root privileges. In LE everything already runs as root, so setting it achieves nothing.

    If you want to experiment you set additional boot time args in /storage/.cache/services/sshd.conf, e.g. include an option to use an alternate config file /etc/sshd_config .. from fuzzy memory it's "-F /path/to/file" ??