run is persistent and equivalent to an installation. live will boot a not persistent system in RAM.
You can change between run, live and installer any time without losing the persistent data.
run is persistent and equivalent to an installation. live will boot a not persistent system in RAM.
You can change between run, live and installer any time without losing the persistent data.
These DVB driver addons are optional, only one of them is permitted to be enabled. If none is enabled the default DVB drivers of the LibreELEC kernel are used.
It depend on your DVB card if one of the additional driver package is needed.
You can use the LibreELEC driver selection addon to choose the driver package - no need to disable anything manually as I wrote in the old post.
just grab 2 usb sticks. use the custom libreelec installer from their download page and install SMP's image on one. boot with both inserted and install on the other. Easy
More easy: use one stick and type run once on syslinux boot prompt.
[ 1.426428] kernel-overlays-setup: adding overlays from /storage/.cache/kernel-overlays
[ 1.426636] kernel-overlays-setup: processing conf /storage/.cache/kernel-overlays/50-driver.dvb.crazycat.conf
[ 1.436570] kernel-overlays-setup: added modules from /usr/lib/kernel-overlays/driver.dvb.crazycat/lib/modules/5.10.35
[ 1.436601] kernel-overlays-setup: processing conf /storage/.cache/kernel-overlays/50-driver.dvb.digital_devices.conf
[ 1.437979] kernel-overlays-setup: added modules from /usr/lib/kernel-overlays/driver.dvb.digital_devices/lib/modules/5.10.35
[ 1.438018] kernel-overlays-setup: processing conf /storage/.cache/kernel-overlays/50-driver.dvb.dvb-latest.conf
[ 1.447335] kernel-overlays-setup: added modules from /usr/lib/kernel-overlays/driver.dvb.dvb-latest/lib/modules/5.10.35
Disable all three "DVB driver*" addons in kodi settings and test again.
The underlying issue at first boot is already fixed in nightly builds.
The message is not visible any more in nightly builds and 9.95.4.
A crash in backup is fixed, the initial OOM Kodi restart of this thread not.
Fine. Remember to remove the test addon when updating the system.
It is the stale symbolic link /usr/lib/kernel-overlays/*/lib/modules/*/nvidia/nvidia.ko to /var/lib/nvidia.ko at boot time.
In the past this was logged to journal but now it is executed earlier at boot time before systemd is started.
If i install it in /storage/.kodi/addons/ like you described on github, will the newer one be used
Yes. You can see it in Kodi (debug) Log.
ApexDE You can test the updated settings addon from Testing LibreELEC-settings addon · Issue #4547 · LibreELEC/LibreELEC.tv · GitHub.
But IMO there will be no improvement until the OOM issue of the RPI4 kernel is fixed.
Likely DOS line endings. Try dos2unix /storage/.kodi/userdata/keymaps/AVMD0.py
Assuming you are creating a Generic image, these nvidia depmod warnings must be ignored.
Install System Tools addon from LibreELEC repo.
A fix is now included into nightly builds.
The fix is now included into nightly builds.
The delay is 2+2s sec from the script. IMO you can reduce the second sleep, but test it. The sleep command even accepts delays below one second like sleep 0.5.
To disable the additional service of post 24:
Thought you got it in post 41.