Posts by emveepee

Don't make LE visible to your network. This is no different than any Kodi installation if you have access to the filesystem you can access passwords.xml so not LE specific.

TVHeadend and NextPVR can both create a channel from a pipe if you want to test a file as true live TV.

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

As I posted I tried -DLLVM_PARALLEL_LINK_JOBS=1 (in common) and still need `16GB and 8GB swap. Adding -DLLVM_PARALLEL_COMPILE_JOBS=1 didn't making any difference. After adding the swap it worked so I tried the default package it still worked and the memory and swap usage were similar.

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.

I just had the same issue with building llvm on LE 13. When I issue scripts/build llvm directly all 16 threads max out at 100%, all 16GB RAM is used and l swap is 100% and I have to wait for a sig 9 on all threads to use the PC. I will try later the the the link and compile jobs set to 1.

Quote from mglae

To mount a nfs4 server use e.g. disk=NFS=172.16.3.4:/mnt/media/storage,vers=4.2

As a test you may even try with disk=NFS=172.16.3.4:/mnt/media/storage,vers=3 to see if there is any issue in the LE parsing code.

So trying the test it works with vers=4.2 but fails with vers=3 Here is the working log FWIW https://paste.libreelec.tv/flowing-mullet.log

Thanks both of you.

OK, I did try vers=3 from the command line and that failed but I will try the other options

mount -t nfs 172.16.3.4:/mnt/media/storage/$OVERLAY_DIR /storage -o rw,noatime,vers=3

Martin

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

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

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

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.

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

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.

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

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

Thanks for that. I guess there could be a related issue if the audio PIDs increase or in the Swedish case you noted more video PIDs. I'd love to get a full mux from Sweden when the regional news is plays to send to my demodulator.

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.

[BBC FOUR HD]
    SERVICE_ID = 18048
    NETWORK_ID = 9018
    TRANSPORT_ID = 16522
    VIDEO_PID = 6701
    AUDIO_PID = 6702 6706
    PID_0b = 7302
    PID_06 = 6705
    PID_05 = 7108
    FREQUENCY = 634000000
    MODULATION = QAM/256
    BANDWIDTH_HZ = 8000000
    INVERSION = OFF
    CODE_RATE_HP = 2/3
    CODE_RATE_LP = AUTO
    GUARD_INTERVAL = 1/128
    TRANSMISSION_MODE = 32K
    HIERARCHY = NONE
    DELIVERY_SYSTEM = DVBT2
    STREAM_ID = 0

and

[BBC FOUR HD]
    SERVICE_ID = 18048
    NETWORK_ID = 9018
    TRANSPORT_ID = 4170
    PID_0b = 7303 7302
    PID_05 = 7109
    FREQUENCY = 634000000
    MODULATION = QAM/256
    BANDWIDTH_HZ = 8000000
    INVERSION = OFF
    CODE_RATE_HP = 2/3
    CODE_RATE_LP = AUTO
    GUARD_INTERVAL = 1/128
    TRANSMISSION_MODE = 32K
    HIERARCHY = NONE
    DELIVERY_SYSTEM = DVBT2
    STREAM_ID = 0

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

If a user does a a daytime scan, is TVHeadend aware not to change the configuration for the working nighttime values, ie no video PID in the scan? In NextPVR a users would specifically have to remember not to update BBC THREE/FOUR HD.

WSL2 won't give you h/w kernel support or or driver support you can't get in Linux. You can always just install NextPVR on Window if you want an that extra tuner in LE. NextPVR also supports multi-rec so technically you get more than one channel for one tuner as described above.

Because of the Kodi UI you won't really notice that it is another backend. However If you only want one PVR with multiple instance install NextPVR directly LE or just move the LE tuner to Windows. I'd probably wait though since the version 7 of NextPVR is about to be released.