Posts by emveepee

  • NextPVR won't update EPG data

    When I see this "EPG Update complete. [0 inserted, 0 updated, 238 skipped]" it seems that

    1) the source is not very complete, typically PVR will have more than 238 shows but it shows that the guide is being updated.

    2) your XMLTV file is stale. Typically this happens when you point to a local file that you aren't updating correctly. If it is online your source is probably just bad. It could also mean that the guide data matches the m3u file.

    Feel free to post your zipped NextPVR logs on the NextPVR forum and we can have a look.

  • Possible security breach

    Why are you sharing all the documents on the NAS with one username and password if you are so worried about visitors? Limit the source to the media that they can view with the remote.

    With physical access to the LibreElec file system the encryption is useless because you could just install a version of Kodi to log the user name and password, or copy the file and decrypt it elsewhere.

  • [RPi4] TBS 5520SE Drivers for LE11, LE12, LE13

    I used this patch as a model for building for the TBS5530 which works for me with the LE 13 nightly kernel 6.12.5 and I kept the TBS5020se diff in as an aide and it didn't give any errors. For my build I did have to add a line "default m if MEDIA_SUBDRV_AUTOSELECT" to the dvb-usb/Kconfig for the drivers because the default for kernel_make was N not m so the =m was being overwritten by package.mk

  • Building FAILURE: scripts/build llvm:host has failed!

    Even with all LINK and COMPILE runs set to 1, it is slower but eventually there is a task that overpowers the CPU until the out of memory sig 9.

    dmesg shows 14 task for llvm-tblgen on 14 threads the time of the crash. Thinking about that I noticed I didn't have llvm installed, and I seem to be able to build this now. It could just be memory too, since upping my swap space also seems to help. 16G + 2G doesn't work but adding 8G of swap seemed to do it.

  • Can no longer PXE boot LE 13

    I am pretty sure the change has something to do with nfs4. I can't specify disk=NFS4 as a kernel parameter as far as I can tell but I have been able to use /flash/mount-storage-sh to manually mount /storage

    Code
    OVERLAY_DIR=$(cat /sys/class/net/eth0/address | tr -d :)
mount  -t nfs4 172.16.3.4:/mnt/media/storage/$OVERLAY_DIR /storage -o rw,noatime

    It seems like the busybox mount that is used at this early stage before the full mount.nfs etc is available is not good at working with nfs versions

  • Can no longer PXE boot LE 13

    Ok remounting rw does work which allows me to start Kod and I have this log now https://paste.libreelec.tv/clever-wolf.log so maybe related to

    Code
    Dec 17 19:59:29.015980 172.16.3.29 kernel: Kernel command line: root=/dev/ram0 rdinit=/init usbcore.autosuspend=-1 BOOT_IMAGE=/KERNEL ip=dhcp boot=NFS=172.16.3.4:/srv/tftp disk=NFS=172.16.3.4:/mnt/media/storage overlay systemd.debug_shell
Dec 17 19:59:29.015991 172.16.3.29 kernel: Unknown kernel command line parameters "overlay BOOT_IMAGE=/KERNEL boot=NFS=172.16.3.4:/srv/tftp disk=NFS=172.16.3.4:/mnt/media/storage", will be passed to user space.

    I looked for a tmpfiles.d that might be missed but I don't see anything around Dec 6.

  • Can no longer PXE boot LE 13

    Quote from mglae

    Assuming you are using Generic (GBM) this is usually caused by kodi crashing. If ssh is enabled login should still be possible. With adding systemd.debug_shell to the kernel command line a debug shell can be reached at console 3 with Alt-F3 as long kodi is not running.

    If you are using the overlay parameter the message is caused by this mkdir. Please check the access rights of 172.16.3.4:/mnt/media/storage

    Yes it is Generic. If I drop KERNEL/SYSTEM back to the LE 12 or LE `13 before Dec 6th the mkdir works so what access right would have changed?

    Thanks though I now can drop to the shell with ALT-F3 and can see that when it works mount has

    Code
    172.16.3.4:/mnt/media/storage/1002b58608ea on /storage type nfs (rw,noatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.16.3.4,mountvers=3,mountproto=tcp,local_lock=all,addr=172.16.3.4)

    and in the newest version the line is the same but that rw turns to ro but I can see existing files.

  • Can no longer PXE boot LE 13

    I PXE boot one of my machines Radka X4 (Intel n100) and I recently updated it and and it fails to load. Going back in the nigthlies PXI boots appears to have stopped working for me with the Dec 6. I can't see all the FAILED services on boot but it hangs at Reache dtarget kodi.target and freezes Any suggestion how I might diagnose this?

    I did trying renaming my system based storage though and it doesn't recreate it instead I get an error during boot

    writer can't create directory '/storage/the number': Read onlyfile system

    Error in mount_storage: mount command could not mount 172.16.3.4:/mnt/media/storage/same number

  • ITV2 ITV3 & Film4+1 - missing - Astra 28.2E

    On LE 12 I didn't update to v7 yet because I typically wait for the initial release to settle and the Windows part of the update has taken a bit of time to debug. 7.0.1 will be worth it for UK users since it grabs the OpenTV EPG too.

    However scanning files for Linux aren't included and the Linux dtv scanning conf files are crap though so if you need help I can generate them. You can try this one and see how it goes. NextTime post on the NextPVR forum,

    /home/.kodi/addons/service.nextpvr/dtv-scan-tables/dvb-s

    Martin

  • TVHeadEnd - BBC 4 has vanished

    Sorry to perhaps hijack this thread but it could explain the users problem. When I compare the two results from libdvb I only see the video and audio pids change of note. The tsid changes but that is for all frequencies so that probably can be ignored.

    and

  • TVHeadEnd - BBC 4 has vanished

    Thanks. I was wondering if TVHeadend knows not to overwrite the non broadcasting channels during the update, since they still are in the scan they just don't have video and audio PIDs.

    NextPVR users a separate libdvb style conf file for tuning, that is were the replacement needs to take place