Posts by mglae

After pulseaudio support you have to use ALSA: or PULSE: prefix, e.g ALSA:plughw:2,0.

The plugin crash if not using a prefix is likely be fixed in the near future.

Weird behavior but cannot be fixed.

Technically: xbmcgui.Dialog.browse() is returning default path on cancel.

Debug logs?

Please, this thread is about getedid failing!

Up to (and including) their 10th generation Comet Lake processors Intel only have HDMI 1.4 interfaces implemented. For HDMI 2.0 output the LSPCon Display Port to HDMI converter are used and required. As consequence the limited native HDMI interface is not used at all in most cases.

Quote from HorzaSe

Is there any way to Log what differences GetEdId causes in the output?

As good start always use the pastekodi script and post the URL (enabling Kodi debug logging can likely be omitted here).

Quote from bg.lebowski

but how can i make changes to /flash/syslinux.cfg

mount -o rw,remount /flash

Quote from bg.lebowski

I only got the error message when it try to boot LE from a SATA boot device. I never get the the error when I try to boot LE from a USB boot device

Quote from mglae

If for OP it disappears by not using latest DVB drivers and for you by not using the SATA interface it is likely something different.

Exactly what I tried to say?!

BUG: soft lockup - CPU#0 stuck for ... is a watchdog message whenever a kernel thread is not releasing the CPU for a long time.

If for OP it disappears by not using latest DVB drivers and for you by not using the SATA interface it is likely something different.

Kernel log buffer size can be increased by adding e.g. log_buf_len=2M to the APPEND line in /flash/syslinux.cfg. To increase Systemd journal size enable persistent logs in LE Settings Addon.

There is a bug in LibreELEC Settings Addon disabling AutoConnect when changing default settings. See e.g. libreleec 9.97.1/10.0 matrix Networking not connecting automatically

You can bind mount a replacement file

mount -o bind /path/replacement.conf /etc/bluetooth/main.conf

GDPR-7 TL;DR

OK, Chrome* devices are that different, ignore my sentence.

As long you are not able to boot from USB you should not delete the LE system on the HDD.

The recommended update path is 8.2.x -> 9.2.6 -> 10.0.1.

For Chromebox see https://forum.kodi.tv/showthread.php?tid=194362

After downgrading - which is not supported - kodi is constantly crashing.

Try upgrading again, but hopefully you do have a LE backup around.

Use pastekodi to include kodi logs.

This can be a limitation of busybox unzip.

Try 7za after installing System Tools Addon.

You can work around general audio delays via advancedsettings.xml:

<advancedsettings>
  <video>
    <latency>
      <delay>+150</delay>
    </latency>
  </video>
</advancedsettings>

Restart kodi using command systemctl restart kodi

========== /storage/.config ==========
total 92
drwxr-xr-x    2 1000     1000          4096 Dec 18 18:49 aacs
-rwxrwxrwx    1 1000     1000             3 Dec 22 17:39 boot.status
-rwxrwxrwx    1 1000     1000           284 Jul 22  2019 hosts.conf
[...]

NFS file system on /storage is mounted for user 1000:1000 but root:root (or 0:0) is required.

Check your NFS server configuration.

Create a log via LibreELEC-Settings Addon after trying to log on via ssh -v [email protected].

Or get terminal access by adding textmode to your kernel command line and use journalctl -u sshd to check the server and pastekodi to create a log.