Have you tested a current LE13 nightly?
Posts by chewitt
-
-
If you want more precise scheduling (after something, but before Kodi starts) you can use a systemd service to run commands. Have a look at the wireguard sample service in /storage/.config/system.d for a rough template.
-
Read: https://wiki.libreelec.tv/development/build-basics and https://wiki.libreelec.tv/development/git-tutorial
Once you create the image with the required changes you just copy the image file to /storage/.update and update, no need to wipe everything and start over.
-
You need to rebuild (or build) an image with that module enabled in config then.
-
just needs dtparam=audio=on in /flash/config.txt as prior Rpi experience taught me, but that solved nothing,
It's not an RPi, so copying the RPi config.txt file (an RPi only thing) does indeed acheive nothing.
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
The fix patch is merged to LE13 and L12 branches so will show up in official nightlies from tomorrow (allegedly).
-
What happens if you install LE 11.0.6 and then manually update to the LE12 nightly?
-
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10199 <= no updates other my nagging, but we'll keep doing that
-
Have you enabled the firewall in LE settings?
-
Code
mount -o remount,rw /flash cp /flash/cmdline.txt /flash/cmdline.original nano /flash/cmdline.txtMake /flash writeable then edit cmdline.txt ^ to use "boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2" and it will read boot instructions from the NVME drive but will then boot the KERNEL and userspace SYSTEM from SD card; which means the partitions on the NVME drive are not actively in use and can be unmounted to run commands against. Remember to copy cmdline.orginal to cmdline.txt before shutting down to remove the SD card else it will attempt to boot from the SD device which is no longer connected.
-
If you're using a Windows PC it may have been converted to Windows line endings. If it happens again the file(s) can be fixed with the "dos2unix" command.
-
The RPi4/5 images in my test share use the default 16K pages. I have no plan to create 4K versions as this is no longer required; the images contain the fix patch for the 16K NTFS issue. NB: LE does not boot to a login console (even if a keyboard is attached) unless you add "textmode" to boot params, but this will disable Kodi start. SSH is disabled by default. You can enable SSH in the first-run wizard and then login remotely.
-
The original scripts make use of the RPi python module which was dropped by LibreELEC, for some reason.
The upstream RPi codebase that we loosely track deprecated the /sysfs approach used in the old Python module in favour of using modern libgpiod and LE(12) simply reflects the same change.
-
not all of my add-ons are compatible and I'd rather roll back.
If there are non-pirate add-ons that are not aarch64 compatible I am genuinely interested to know which ones?
-
Code
umount /dev/nvme0n1p2 parted -s -m /dev/nvme0n1 resizepart 2 100% umount /dev/nvme0n1p2 e2fsck -f /dev/nvme0n1p2 resize2fs /dev/mmcblk1p2 sync shutdownBoot from an SD card or USB then run ^ and it should unmount the second partition, resize it to 100%, and then run a filesystem check. Please also run "cat /flash/fs-resize.log | paste" and share the URL so we can perhaps see why the first-boot resize failed?
NB: I've deleted the second thread as one (here) is enough thanks.
-
Please run "amixer contents | paste" and share the URL - I suspect one of the controls needs switching.
-
LibreELEC images for ARM SoC devices (which typically boot from removable SD card media) have two partitions: a 512MB boot volume and a 32MB persistent storage area that will be resized to 100% of available space on first boot. LibreELEC images for Generic x86_64 devices are exactly the same layout but will run an installer app that allows you to select and install LE to an internal storage device. In both cases it is not possible to install and boot LE from a single partition and the Generic installer targets a whole disk not free space on an existing disk (it will nuke the content of the selected disk).