Posts by mglae
-
-
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)
-
Code
mount -o remount,rw /flash nano /flash/syslinux.cfgAdd 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:
Codemount -o remount,rw /flash nano /flash/syslinux.cfgand replace quiet with debug and reboot.
-
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
-
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.
-
Will I be able to access the .kodi/userdata on Windows without installing additional software?
No. But is really not needed.
Via ssh do:
Codesystemctl stop kodi # edit/delete anything needed systemctl start kodi -
Hide the static avahi service files by over-mounting the directory:
Codemount -t tmpfs tmpfs /etc/avahi/servicesYou can create a systemd drop in file for the avahi unit and add a ExecStartPre=/usr/bin/mount ... line.
-
a) Add video=LVDS-1:d
b) With DEFAULT run in syslinux.cfg use "run". You can check the kernel parameters with cat /proc/cmdline
-
You have to disable the video output you don't want ( chewitt already mentioned it).
Use ls /sys/class/drm to get the correct LVDS name and use video={lvds name}:d.
Usually it is video=LVDS-1:d or video=eDP-1:d
-
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.
