Did you stop kodi with systemctl stop kodi before changing the files?
Posts by mglae
-
-
chewitt Great, I'll continue on github.
Johpin Now xorg did start but kodi is in a fail/restart loop. pastekodi is needed - or pastecrash if there is a crash log below /storage/.kodi/temp.
Few notes to improve testing workflow:
- There is no need to install any new image, you can update on reboot with keeping the configuration:
wget -P /storage/.update <url> - For keyboard reboot first switch the console: ctrl-alt-F2 then ctrl-alt-delete.
- While testing it is helpful to disable xorg and kodi restart. Create /storage/.config/system.d/xorg.service.d/norestart.conf and /storage/.config/system.d/kodi.service.d/norestart.conf with:
- There is no need to install any new image, you can update on reboot with keeping the configuration:
-
Likely a mesa issue for "vmware" driver. Generic fails but Generic-legacy is working in VirtualBox.
For Intel HW it is opposite: failure with Generic-legacy but Generic is fine.
-
-
-
-
Xorg is logging to /var/log/Xorg.0.log
Johpin You are using live mode with tmpfs mounted on /storage not allowing persistent configuration. Please switch to run mode at boot.
The reboot is caused by activating LE safe mode after five kodi crashes, but is useless in live configuration.
After switching to run disable safe mode with
-
-
According to the Wiki LE is using libreelec_multi.toml for rc-rc6-mce.
Rename your file and it will be loaded at boot.
-
When testing LE13 Generic-Legacy a few weeks ago Kodi failed to start on Intel HW (while Simple Terminal (st) and Chrome were working).
No issues with AMD and vmware graphics driver.
Expected a magic fix by e.g. Mesa or Kernel bump but seems still to be an issue.
-
on xbmc python version 2.7.0 could not be satisfied
You do need an updated addon with Python3 support.
-
giaguaro Did you disable the on board graphic card in the BIOS after adding the 8600GT?
-
The PR adds kernel nouveau driver via package.mk
-
From llvm.org:
CodeLLVM_PARALLEL_{COMPILE,LINK}_JOBS:STRING Building the llvm toolchain can use a lot of resources, particularly linking. These options, when you use the Ninja generator, allow you to restrict the parallelism. For example, to avoid OOMs or going into swap, permit only one link job per 15GB of RAM available on a 32GB machine, specify -G Ninja -DLLVM_PARALLEL_LINK_JOBS=2. -
heitbaum 20230309 is older than 12.0.1 of 2024-10-17
-
-
Recent RPI5 HW do require a LE12 nightly. The required support is not in 12.0.1
-
It was first included into LE13. Did you force a manual repo update?