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.
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 onThe linked post (number 9) contains the solution at https://pastebin.com/za8zzjfU
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.
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).
but how can i make changes to /flash/syslinux.cfg
mount -o rw,remount /flashI 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
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
You can bind mount a replacement file
mount -o bind /path/replacement.conf /etc/bluetooth/main.confAs long you are not able to boot from USB you should not delete the LE system on the HDD.
The recommended update path is 8.2.x -> 9.2.6 -> 10.0.1.
After downgrading - which is not supported - kodi is constantly crashing.
Try upgrading again, but hopefully you do have a LE backup around.
Use pastekodi to include kodi logs.
