Posts by kny2tl

    Hello everyone,

    recently I've done clean install of Kodi 10.5 and since then my connection to WiFi is sometimes lost and Kodi won't reconnect (Ethernet is not an option, unfortunately). There was no change at all on router, so I can isolate it to Kodi (and still nothing suspicious in router logs, anyway).


    From GUI, rescan wifi - very limited number of Wifi networks are displayed. After powering down and up, my network is sometimes visible - and if not, power down and up over and over. Once found, I need to enter passphrase, ensure network is set to autoreconnect etc, and then later it disconnects again (of course, once I disable debug). Once connected, time varies before connection is lost: sometimes hours, sometime days. On the same router are connected other Wifi devices that keeps connectivity as they should, so perhaps again router should not be blamed.

    The latest log: http://ix.io/4mAt


    Output of .cache\connman\wifi_dca632234b95_4c756b796e2d636170736d616e_managed_psk\settings


    There's just one wifi that Kodi was ever connected to, so there shouldn't be any kind of "interference" etc. Interesting is Feb 02, while GUI has the right. Apart from that, looks legit to me. Frequency etc is matching router.

    /.cache/connman/settings

    Cheers,

    kny2tl

    No signal is back: using SD card to boot only and rest read/write from USB disc. As the tvheadend backed runs just fine, I wonder if there's other client (frontend) that could use tvheadend backend. I tried to set up IPTV simple client but failed miserably at the first attempt, but I can't blame others than me (as I don't want to use live stream, but TV signal)

    So far booting from SD and USB disk works (assuming I managed to get it work, both SD and USB have the same size so just looking at size of partitions is not useful :). If the SD is to blame, the wear has to be terrible considering my set up was mostly read only, no live tv recording etc.

    thanks anyway, hopefully it'll stay this way!

    Morning, CvH!

    It's very strange indeed; one of the reasons I chose Pi4 + TvHat was fixed hardware, less fiddling with drivers, kernels etc - reading that so many folsk are happy with their solution for dvb-t2.

    Anyway, over Sunday got system updated, have the latest firmware "ad" applied and still getting the same problems. SD came to my mind when reading on of the forums, so will try to get system to other SD and if that would work, I'd have to get some ssd and get boot from SD and system on ssd..

    Re firmware:

    Code
    Pi:/etc/default # rpi-eeprom-update
    BOOTLOADER: up-to-date
    CURRENT: Tue Sep 10 10:41:50 UTC 2019 (1568112110)
     LATEST: Tue Sep 10 10:41:50 UTC 2019 (1568112110)
    VL805: up-to-date
    CURRENT: 000137ab
     LATEST: 000137ab

    But, found "ad" rpi-eeprom/vl805-000137ad.bin at master · raspberrypi/rpi-eeprom · GitHub.

    Not sure why libreelec won't find the newer itself. Perhaps as my libreelec is still 9.2.0?

    nevertheless, downloaded ad version,

    Code
    Pi:~/downloads # rpi-eeprom-update -f ~/downloads/vl805-000137ad.bin
    *** INSTALLING /storage/downloads/vl805-000137ad.bin  ***
    Traceback (most recent call last):
      File "/usr/bin/rpi-eeprom-config", line 113, in <module>
        main()
      File "/usr/bin/rpi-eeprom-config", line 106, in main
        image = BootloaderImage(args.eeprom, args.out)
      File "/usr/bin/rpi-eeprom-config", line 36, in __init__
        (filename, IMAGE_SIZE, len(self._bytes)))
    Exception: /storage/downloads/vl805-000137ad.bin: Expected size 524288 bytes actual size 98904 bytes

    That's where I am now. Later today I'll update libreelec to 9.2.1 in hope that "ad" firmware will be available. I tried to use yesterday 9.2.1 and didn't get tvheadend client working at all. on 9.2.0. it was.

    Thanks, CvH.

    1) Anytime I lose the signal, I check the tvheadend backend from PC and I'm able to get video and audio. Same if I plug antenna to TV directly (though not dvb-t2 signal, that's the reason why I'm trying to use pi + tvhat). So I'm pretty sure it's OK
    2) Doing that pretty much as often as the 1) above; in the past it helped, not today (tried 4x times)

    3) Little puzzled for this one: `temps` = temp folders? I can google and purge for sure. Firmware upgrades - will google if there's anything new.

    In the meantime I had fun with router and firewall, just for case and everything seems ok (as far as my networking skills are ok)

    And again, thans for looking into this.

    All,

    yesterday without any update/config change I got infamous "Tvheadend htsp client no signal" message, system was running for months. Most of this today I spent trying to fix etc, resulting in extremely clean reinstall. After watching for some 40m, it's back, again being just watched, no changes.This time reboot helped, but I need to find what is going on.

    Rapsberry 4, tvhat.

    TVHeadend v9.2.0.120 + tvheadend HTSP client 4.4.18.2, otherwise all default installation, didn't have time to do anything else.

    Signal is recieved via antenna; and whenever I get this error, I was able to connect via http://<>:9981/extjs.html, so I'm very positive that signal recieved via antenna is OK.

    Kodi: http://ix.io/2eLv dmesg: http://ix.io/2eLw

    earlier today I tried fresh install with the latest versions, but the same problem, didn't get the live TV at all, so I'd like to avoid upgrades at any costs.

    Also in the kodi.log you can see

    2020-03-20 14:05:19.824 T:2738025328 ERROR: AddOnLog: Tvheadend HTSP Client: pvr.hts - unable to connect to 192.168.88.250:9982

    2020-03-20 14:05:20.132 T:2566427504 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer

    But I'm not overly concerned about that as workaround is to switch to another channel and back. Eventually I'd like to sort it out, but "No signal" is getting my nightmare