Posts by mglae

CvH is referring to 'Temporary failure in name resolution'

Feb 24 17:56:53.914844 LibreELEC systemd[1]: Wait on network was skipped because of a failed condition check (ConditionFileNotEmpty=/storage/.cache/libreelec/network_wait).
Feb 24 17:56:53.914992 LibreELEC systemd[1]: Reached target Network is Online.

Jan 24 22:46:02 LibreELEC systemd[1]: Condition check resulted in Wait on network being skipped.
Jan 24 22:46:02 LibreELEC systemd[1]: Reached target Network is Online.

Wait on Network is disabled resulting in kodi starting without active network connection.

@reboot is not supported in LE, CONFIG_FEATURE_CROND_SPECIAL_TIMES is disabled for busybox crond.

Best practice is to use the Kodi Autoexec Service.

Wrong xml tags order. Use:

<keymap>
<global>      
<mouse>    
<rightclick>Back</rightclick>
</mouse>
</global>
</keymap>

Quote from oJPTo

Do I have to set this for every page not "global" alone?

For all defined in the default file.

Quote from sam-y

How can i check whats used at the moment?

echo $TERM

Quote from sam-y

"st-256color" sounds like 256-color-support?

Yes, but only usable for the st terminal emulator.

Quote from sam-y

How can i install that?

Copy the definitions for your used terminal to /storage/.config/termcap or use a complete one from a common Linux distribution. Then set TERM=xyz ("xyz" is a plyceholder for the terminal definition needed).

For a temporary test just call TERM=xyz mc

LE is only supporting a subset of terminals (linux,screen,xterm,xterm-color,dumb,st-256color). In most cases TERM=xterm is selected.

You can install a custom termcap in /storage/.config/termcap and set TERM.

heitbaum The MPD Client addon of #11 is only available for Leia with Python2.

You can boot the install stick on any UEFI device in UEFI mode or old legacy boot only device into installer and press Alt-F3 to get the debug shell. Use blkid to detect the stick and execute the parted line.

At least with diskpart in Windows it seem not to be possible.

shippy

The images are (intentionally) deleted in the meantime.

To get a current image booting with UEFI firmware in legacy mode change the (protective) MBR flags:

parted -s <disk or image> disk_set pmbr_boot on

Quote from mglae

2. RE: shutdown.sh is executed after network is down

The linked post (number 9) contains the solution at https://pastebin.com/za8zzjfU

1. https://wiki.libreelec.tv/configuration/…own#shutdown.sh but network access will fail.
2. RE: shutdown.sh is executed after network is down

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