Posts by emveepee

    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

    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.

    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.

    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

    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

    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

    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.

    There’s no need to discuss Windows here. This is a forum for a Linux based application. In fact it’s a complete non discussion.

    I was not asking either of you to run Windows my comment is still valid for users with open minds reading this looking for alternatives to non working tuners. Integration does not mean everything in your home must run pure open source Linux and not Windows, macOS or Apple/Android tablets. There are plenty of LE users who to access backends that are running Windows for their shares or severs like Emby, Jellyfin, Plex, PVR (Media Portal, NextPVR) and DLNA as examples and to suggest otherwise is just ridiculous.

    No my Vista is not used for anything but PVR testing but I consider it well protected for Internet issues. I would consider that buying any generic network device for SAT>IP on ebay running god knows what OS version with no updates is potentially more risky.

    For power if you want a 24 hour non-transcoding solution I don't think you can beat a generic arm32/aarch64 device like the RPi but there are limits to a 3A power source needed for USB tuners, hard disks, external 2.5Gb networking etc. With better power supplies I think a NUC or PC running x64 Linux or Windows will have similar power drain but the power management of Windows is going to better. I am a PCIe fan so my server requirements are slightly different and when moving to Linux from Windows 5 years ago I had to give up on letting my system sleep because my internal and external Hauppauge tuners and my USB connections were never correct.

    When you can't get good Linux drivers I stick with my general recommendation for non-haters reading this to try Windows since many people have access at home to a free or nearly-free old PC that support most tuners. You can even install a clean Windows run headless, without a license (many cheap PCs even include a BIOS based license ). I know some people complain about stability but I have a 17 year old headless Vista system that replaced a Linux MythTV setup that still sleeps, responds to WOL and wakes up daily for EPG updates and test recordings 10 and it transcodes better than a current RPi.

    Please no Windows vs Linux discussion needed, my main PVR backend and most test systems I have are Linux based and they are quite reliable too but Linux is just not for everyone. LE clients don't care what the backend runs.

    To be fair I checked the amazon.co.uk 1 star reviews and you shouldn't really be surprised by the lack of Linux support. Even some other variations won't work. Same for their PCTV model. Maybe with Hauppauge web store you can communicate with a real person who can check. I only mentioned Windows since like it or not that is what vendor support and many people here will just tell you to get a SAT>IP box to avoid firmware issues.