Posts by mglae

/etc and /lib are read only in LibreELEC. Configuration is done below /storage/.config.

Can be done like in #2 but dependecies may be missing.

But after downloading the ZIP with wget or manually from the "Code" button on the giitub page it can be installed directly with Kodi's "Install from ZIP" in Settings->Addons. No name or path adjustment required.

Edit: links added.

It should be possible to copy the boot files of hdajackretask from Ubuntu to LE.

Firmware directory is /storage/.config/firmware/ and modprobe directory /storage/.config/modprobe.d/

Guess: because the hang is at the time of network device initialization and there is a history of errors in r8169 driver with ASPM try the pcie_aspm=off kernel parameter in syslinux.cfg

Start with:

Thread

Unable to get external monitor to be the primary monitor

Hi all, I have been trying to get LE working on an old toshiba laptop but I'm having the same issue as in this thread:

Unable to select HDMI-A-1 monitor as output + LibreELEC 11.0.1 tldr; I cannot get the primary output to be the external HDMI monitor. I generally disconnect the laptop display so I don't need a dual screen duplicated setup(if possible), just the HDMI output. I already tried adding the suggested line in from:

RE: Unable to select HDMI-A-1 monitor as output + LibreELEC 11.0.1…

aNewELUser

September 15, 2023 at 3:13 PM

Thread

Using the 2nd Display as the Main Display for Kodi on Your Laptop

Good day to you all,

I'm here to ask if any of you knows how to force Kodi to launch on the 2nd display or how to use the 2nd display as the main display. Currently, I'm using an HP Pavilion G4 with an AMD A6-4400M APU with Radeon™ HD Graphics. I had to boot it off of a USB flash drive since the HDD recently died, but this is just a temporary solution, so please bear with me.

If anyone has experience or knowledge regarding configuring Kodi to use the 2nd display or setting it as the primary…

Revisory

July 18, 2023 at 4:07 PM

Quote from chewitt

I would recommend testing/using LE12 nightlies as those have much newer kernels and mesa code.

Agree. Was the next step on my list.

0ptr You find them here. Kernel is currently 6.5.3.

As side effect you will get Kodi 21alpha. Create a system backup to be able to get back to LE11 again.

No news in journal.

Is there any difference in behavior between cold (power on) and warm boot (reboot)?

Power off via systemd-logind can be configured in /storage/.config/logind.conf.d

journalctl is showing nothing for the failed boots.

You can try LE11 nightly which includes kernel 6.1.45 update.

Should be automatically created by tmpfiles at boot. Please post logs if this occurs again (accessible via samba share without ssh)

mount -o remount,rw /flash
nano /flash/syslinux.cfg

Add the kernel parameter to the APPEND line.

With "early console in setup code" kernel Real Mode initialization has started. But I've no idea what is causing the delay. Later kernel boot is OK.

You may try updating to LE 11 nightly with a more recent kernel.

a) With kernel 6.1.38 the message fail to initialize ptp_kvm is printed at any boot on non-ARM systems. Ignore it.

b) dmesg is not showing the complete boot process, please use journalctl or better pastekodi for most complete logs.

c) My wild guess: kernel load via systinux is very slow or kernel initialization stuck for some time. To see more please do:

mount -o remount,rw /flash
nano /flash/syslinux.cfg

and replace quiet with debug and reboot.

Quote from chewitt

time.microsoft.com

The public Microsoft NTP server is time.windows.com

In LE9 Generic a X11 terminal window can be opened from System Tools Addon. This is still supported with LE11/LE12 Generic-legacy image.

It is not possible with LE11/LE12 Generic image using GBM instead of X11.

IMO you can only change guisettings.xml values from advancedsettings.xml.

The settings.xml file can be replaced with an edited one using a bind mount in autostart.sh.

Connect the old monitor again and run getedid create to save the resolutions.

Wiki: EDID

Quote from wcndave

So I let it do the default action, which I think was run from USB, and it worked, but there was not enough HDD to actually try much.

"Run" mode is the intended one.

Expanding disk is broken for GPT in LE11, see Vmware discussion here. Maybe the work around to increase the disk size of a fresh OVA is working too in Vbox.

Untested manual fix possibility from LE: Boot a fresh OVA into "installer". Press Alt-F3 to get the debug shell. Execute parted /dev/sda and allow to repair the disk. Reboot and choose "run" mode.

Discussion about using installer with OVA - and again Vmware - is here.