Posts by mglae

rasser You may have hit the autoconnect bug, see RE: Problem of wifi connection

The Wiki is corrected now.

Unfortunately the sample in the wiki is wrong. shutdown.sh is ever called with one parameter of [halt|poweroff|reboot] and the default condition is never tested.

To have a command executed in any case move it out of the case ... esac statement.

/bin/bash and /bin/sh are both linked to busybox's ash, there is no difference.

Don't change PreferredTechnologies in connman_main.conf and add

SingleConnectedTechnology = true

These addons from kodi repo are outdated.

You can use the Gigathek instead.

There is a bug in10.0 LibreELEC-Settings addon up to 10.0.1 keeping the autoconnect option disabled.

Update to LibreELEC 10.0.2 or use the addon test version from https://github.com/LibreELEC/LibreELEC.tv/issues/4547.

After any update autoconnect has to be enabled once.

Core generation is defined in /usr/lib/sysctl.d/99-coredump.conf. You can temporary disable this setting with

sysctl -w kernel.core_pattern=/dev/null

or override it in file /storage/.config/sysctl.d/99-coredump.conf

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