Posts by mglae

Quote from diameter

t works only if I setup the Wifi network on the original setup dialog. If I skip it and connect to Wifi afterwards, I get the dependency errors.

A fresh Kodi installation is starting with empty addon repositories. They need to be updated from the net.

After configuring the network with the Installation Wizard a repo update is triggered and the available addons are loaded.

When afterwards changing network configuration the addon repos are not touched. You need to manually force the repo update or wait until it is scheduled automatically.

mattza Google did remove the Chrome 96 deb packages from their server. The LE10 Chrome addon is not installable any more.

MatteN There is no LE10 Generic-Legacy

Splash loading is implemented simple, see here. Look for the file and use ply-image to display it.

Quote from kacharava

So why not to use my (currently) broken LE for testing purposes?

You can add debugging break=load_splash to the APPEND line of syslinux.cfg to start a debug shell after loading the splash. Be warned, this stops the boot process by opening a shell and requires an attached keyboard.

Quote from kacharava

I believe they won't as it is clearly said only 32bit will do.

They do (usually) work.

Quote from kacharava

Where are they located on the HDD after LE is installed?

They are included into the internal initramfs of the kernel and not accessible after system is booted.

Quote from kacharava

No, I don't. Black screen with LibreELEC (official): 11.0.1 at the top left corner.

Then splash is not visible on your system.

With this discussion in mind I noticed that splash is not visible when booting LE11 or LE12 in VMWare Player (just a development setup). LE9.2 or LE10 do show the splash.

A debug shell session show the splash is extracted successfully but not visible until redraw due to scrolling.

Maybe something with framebuffer device changes but it is working on my real HW.

They are included in the LE images and shown by default.

Do you see a splash screen without custom oemsplash .png?

Default splash files are at https://github.com/LibreELEC/Libr…ibreELEC/splash

Which HW do you use?

The colors have to be opaque (alpha channel 100%)

a) New settings are only applied after reboot.

b) /storage partition full?

c) A pastekodi after reboot may show more.

a) The VNSI Addon is using the VDR channel notation like 1_0_1_28AD_431_A401_FFFF0000_0_0_0.png, not the channel name.

b) You have to enable Debug Logging and PVR Component Logging to see the messages.

c) In addition it is (or was - did not test this recently) possible to use Channel Name Logos via the Kodi Core Settings.

a) As you already know the script mentioned in OP can only work on Generic-legacy (X11), not on Generic (GBM). I'm not aware of a GBM tool to be capable switching resolution.

b) Even on Generic-legacy the device name ("HDMI1") may have changed . Type xrandr to check this.

c) /storage/.config/sleep.d has to be used.

You can override guisettings.xml settings from advancedsettings.xml.

Can confirm the issue. Until fixed add systemctl restart samba-config to autostart.sh.

The device names are auto-generated from the chip set by the driver and device card0-HDMI-A-2 (or HDMI2 in X11) is connected.

zelenac There is nothing special in Xorg.0.log. pastekodi should create a ix.io URL too but can fail silently from time to time.

Da Flex HDMI2 seems to be used not DPx. No DiplayPort-to-HDMIadapter involved.

Configuration is stored in /storage/.cache/services/samba.conf and processed with /usr/lib/samba/samba-config

There are several issues with samba server configuration: [1] [2] [3]

Currently they are (only) fixed in LE12 nightly.

Remove any EDID configuration, reboot and create complete logs with:

pastekodi
paste /var/log/Xorg.0.log

Maybe something is visible.

Quote from ToddeSwe

What does it mean anyway? What can't he do?

The error message is irrelevant and printed on not-ARM systems. This is fixed in recent kernels.