Posts by chewitt

  • Wyse3040 - no analog sound -

    Quote from lucian

    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>Logging
    2. Restart Kodi
    3. Replicate the problem
    4. 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

  • Radio Plugin: Network Error ??

    Please provide a full debug log.

    How to post a log (wiki)

    1. Enable debugging in Settings>System Settings>Logging
    2. Restart Kodi
    3. Replicate the problem
    4. 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

  • Partitioning issues

    Code
    mount -o remount,rw /flash
cp /flash/cmdline.txt /flash/cmdline.original
nano /flash/cmdline.txt

    Make /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.

  • [RPi5] LE 12.0.0 and NTFS HDD Problem

    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.

  • Partitioning issues

    Code
    umount /dev/nvme0n1p2
parted -s -m /dev/nvme0n1 resizepart 2 100%
umount /dev/nvme0n1p2
e2fsck -f /dev/nvme0n1p2
resize2fs /dev/mmcblk1p2
sync
shutdown

    Boot 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.

  • Partitioning issues

    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).

  • LibreELEC/Kodi add-on for offline file search using 'plocate' as backend

    Compiling the plocate binary from sources and then storing it in a 'bin' directory for use should be simple (including precompiled blobs would be rejected if you ever wanted to include this in the LE binary add-on repo). The sources use the meson build system and important things like specifying a non-standard DB location at compile-time appear to be supported already. If the add-contains compiled binaries I don't think script.plocate.search is correct naming (script.* is really reserved for things that are only scripts; normally Python scripts). Something like tools.plocate would be more appropriate. There is no need to have the binary built separately from the add-on; we only do that for e.g. add-ons like "System Tools" and "Multimedia Tools" where multiple separate binaries are being packaged.

    LE supports udev rules being overlaid from /storage/.config/udev.rules.d at boot time, so the add-on can run a setup (b)ash script that detects presence of a known-name .rules file and create it if missing, but as you noticed there is no "uninstall" function in add-ons so if the add-on is removed the rules file becomes orphaned. You can probably add some udev logic to check for presence of the add-on bin directory first, and if not found skip the rule so orphaned rules files do no harm. It's messy though, so:

    Or you can use a systemd service to run a script that creates or updates the DB before Kodi starts. The negative: using systemd not udev means you lose the ability to trigger an update to the database when a USB drive containing media is connected. The positive: you have simple systemd packaging that aligns with how most binary add-ons are already being started/stopped and packaged for LE use (so lots of prior art in our buildsystem). IMHO most users with portable USB drives full of media will have them connected to their HTPC device before boot so the loss of the connect drive feature isn't such a big deal. NB: plocate also ships with an example systemd service so you can use that with a minor tweak (the buildsystem can patch the sources) to add a kodi.target dependency.

  • tvheadend htsp client missing after upgrade to librelec 12

    Honestly no idea what the issue is, and there is really nothing to configure when DHCP is used (as default) and the design of the OS (everything inside a read-only file) rather prevents users from messing with anything that's important.

    If you have the backup I would soft-reset and then not-restore the backup, but untar the file to somewhere on /storage and then selectively move back the bits of Kodi config and recordings that you need. Kodi is rather simple so a simple "stop > move files around > restart" process is all you need. Move things in small chunks and if the internet dies, you narrowed the problem down.