Hauppauge WinTV-NOVA-S2 tuner not recognised

  • I have been running NextPVR for many years on Windows but almost a year ago changed to running on LibreElec. It been working well with my SAT>IP and Hauppauge DVB-T2 tuners but never been able to get my Hauppauge WinTV-NOVA-S2 tuner recognised. Six months ago Hauppauge were not that helpful saying some new driver had recently been created so it should work. However I just emailed support again and this time the reply included a separate link for the WinTV-NOVA-S2 tuner!

    https://hauppauge.s3.us-east-1.amazonaws.com/linux/dvb-demod-m88ds3103c.fw

    I followed the LibreElec wiki instructions to add firmware and created directory:-

    /storage/.config/firmware and copied the file to the directory and rebooted but the NOVA-S2 is still not recognised!

    Is there something else I should be doing? I am running the latest LibreElec.

    Chris

  • Is there something else I should be doing?

    Sharing a log file?

    NB: These days we are not too enthusiastic about adding patches that we can't drop in the future with a kernel bump, so if there are things in Issues/Forum threads that work (meaning, they need to be tested and confirmed first) someone needs to submit them to the linux-media mailing list. As long as there are signs that patch(es) will be merged upstream we will be happy to pick/backport the changes until some future kernel bump drops them. Firmware is more easily handled as we mostly have our own collection(s) and can add things to our own repo.

    Also note that I'm unable to test any form of DVB hardware (as no DVB-T/DVB-S feeds) so I depend on being told what's needed.

  • Any h/w issues would be in the kernel logs. If it is an issue with NextPVR server it would be in the NextPVR server logs.

    Also is it all frequencies, just DVB-S frequencies (patch #2) or certain frequencies? It could even be the dtv-scanning-tables.

    Martin

  • There is no indication anywhere I can see that the tuner is recognised!

    You didn't bother to look in the log then?

    Looks detected to me /shrug

  • The kernel logs didn't identify that it found anything on this device

    Code
    Oct 03 19:38:38 LibreELEC kernel: usb 1-2: new high-speed USB device number 2 using xhci_hcd

    I would expect to see kernel: usb 1-2: New USB device found, idVendor=2013, idProduct=-4062, bcdDevice=##

    Do you see anything with find /dev/dvb

    If yes the do the journalctl | paste again.

    Note the NextPVR server does the /dev/dvb scan on startup and if it is slow to be detected you would need to rescan to find the device. There are also scripts on the NextPVR forum showing how to have the server startup delayed.

    Since the device is new to the kernel I don't know how Hauppauge can say LE should have the drivers.

    Martin

  • 2013:0462

    The last contribution to linux-media from the Hauppague maintainer was adding some 461 variants. The '0462' PID variant doesn't exist in the Linux 6.17.y kernel and I don't see any patches on kernel mailing lists.

    Hauppague might be under the no-longer-true assumption that LE packages downstream driver collections. That turned out to be a pain in the rear to maintain as we were regularly being held back waiting for sources to be kernel bumped, so we dropped them and we now only support upstream drivers. I'll be happy to pick patches that add drivers that are being upstreamed (patches might need a few more iterations but they are visible on lists etc.) but we aren't adding patches with no plan.