9 hours ago, Richard Harnwell said:

Any tips on getting this working with Hauppauge WinTV-NOVA-S2 USB dongle?

 

when i check the Hauppage support site, there is no linux support for USB S2 cards ...

 

https://hauppauge.de/site/support/support_linux.html#tv_tuner

 

from the german page

 

 

only pci devices ...

3 hours ago, alturismo said:

when i check the Hauppage support site, there is no linux support for USB S2 cards ...

 

https://hauppauge.de/site/support/support_linux.html#tv_tuner

 

from the german page

 

 

only pci devices ...

 

Thank you fo that.  That's very confusing/annoying, as I bought it based on the UK page saying it is supported!

 

Is the Ubuntu PPA mentioned some sort of workaround/add-on for Linux support? If so, could I maybe get around it by using an Ubuntu VM and passing the USB through to it?

 

https://www.hauppauge.co.uk/site/products/data_novas2.html

 

Edited February 24, 20251 yr by Richard Harnwell
added an extra thought

23 hours ago, Richard Harnwell said:

WinTV-NOVA-S2

This is really strange, however you can try to use the modprobe command and load the driver manually:

modprobe cx24116

 

However I'm not 100% sure if that will work because if they changed the chipset that obviously wont work, what you can do is issue the command from a Unraid terminal and then post new Diagnostics if it doesn't work.

4 hours ago, ich777 said:

This is really strange, however you can try to use the modprobe command and load the driver manually:

modprobe cx24116

 

However I'm not 100% sure if that will work because if they changed the chipset that obviously wont work, what you can do is issue the command from a Unraid terminal and then post new Diagnostics if it doesn't work.

Thanks. I tried the command. Not sure if you'd expect output from it, but there was none.

 

 

Have attached new diagnostics in case anything has changed.

tower-diagnostics-20250225-0039.zip

5 hours ago, Richard Harnwell said:

Thanks. I tried the command. Not sure if you'd expect output from it, but there was none.

No you don't get any output.

 

The Hauppauge page says also that LibreELEC should work right OOB and since I compile it up to as recommended in their GitHub Repository it should in theory work.

 

I did a bit of research and I found multiple reports that this device is not working on Linux for multiple users.

 

On the LinuxTV Wiki you can see that there are two versions from this Adapter where one is working and the other one not:

There is also a HD version listed and this seems also not to be supported:

 

So it seems there is some misinformation on the Hauppauge page and I even can't find much information about the Vendor/Device IDs.

 

Anyways I am not the biggest fan from USB Tuners however if you really want to use one I would recommend one from Sundtek in combination with TVHeadend:

https://shop.sundtek.com/DVB-S-S2-S2X/

On 2/25/2025 at 6:40 AM, ich777 said:

No you don't get any output.

 

The Hauppauge page says also that LibreELEC should work right OOB and since I compile it up to as recommended in their GitHub Repository it should in theory work.

 

I did a bit of research and I found multiple reports that this device is not working on Linux for multiple users.

 

On the LinuxTV Wiki you can see that there are two versions from this Adapter where one is working and the other one not:

There is also a HD version listed and this seems also not to be supported:

 

So it seems there is some misinformation on the Hauppauge page and I even can't find much information about the Vendor/Device IDs.

 

Anyways I am not the biggest fan from USB Tuners however if you really want to use one I would recommend one from Sundtek in combination with TVHeadend:

https://shop.sundtek.com/DVB-S-S2-S2X/

Thank you, that's a pain. My Unraid runs on a AOOSTAR WTR PRO which unfortunately has no card slots, so has to be USB for my use case. Before I abandon this stick (or resign myself to buiding a standalone Windows box for it) I wonder if it's worth my trying an Ubuntu VM and passing through the USB port to it, given Hauppauge specifically mention getting it working with that distro...

1 hour ago, Richard Harnwell said:

given Hauppauge specifically mention getting it working with that distro...

You can try but it is a huge waste of resources, however I'm really curious if it is really working because the LinuxTV Wiki says no...

On 2/28/2025 at 11:55 AM, ich777 said:

You can try but it is a huge waste of resources, however I'm really curious if it is really working because the LinuxTV Wiki says no...

 

I got it working with a Ubuntu server VM that I passed the USB port/stick to, and following the Hauppauge instructions from  https://www.hauppauge.com/pages/support/support_linux.html , namely:
 

sudo add-apt-repository ppa:b-rad/kernel+mediatree+hauppauge

sudo apt-get update

sudo apt-get install linux-mediatree

sudo reboot

 

sudo apt-get install linux-firmware-hauppauge

 

I then installed TVHeadEnd, and I have it working and receiving all the channels (haven't figured out how to get them down to just the subset I want easily yet). The video quality is far from perfect though - see screenshots. Behaves as if the signal is poor, when in fact it is perfect on my Sky box. Not had chance to investigate that much yet though.

 

You're right, I would prefer not to have to devote a whole Linux VM to it though. Mind you, could be worse, if that didn't work I would have probably tried it with a Windows VM!

    

Edited March 5, 20251 yr by Richard Harnwell
Added screenshots

Hello, 

i have a problem my DigitalDevices MAX  M2  v1 is not showing up in the Settings of the plugin. I restarted multiple times.

i have no clue where to start

tower-diagnostics-20250424-2039.zip

32 minutes ago, kellekellner said:

i have a problem my DigitalDevices MAX  M2  v1 is not showing up in the Settings of the plugin. I restarted multiple times.

Is this the first time installing the plugin or was it working before?

it was the frist time! And thanks!

2 minutes ago, kellekellner said:

it was the frist time! And thanks!

Please do the following:

1. Open up a Unraid terminal
2. Type in: modprobe ddbridge
3. Type in: ls -l /dev/dvb

If you get a error message about the module not being found in at step 2 thenTy:

1. Type in: depmod -a
2. Type in: modprobe ddbridge
3. Type in: ls -l /dev/dvb

So now there is a solution. I update to unraid 7.1.0 Rc1 an installed the plugin new. Now its working. 

 

Thanks

Just now, ich777 said:

Please do the following:

1. Open up a Unraid terminal
2. Type in: modprobe ddbridge
3. Type in: ls -l /dev/dvb

If you get a error message about the module not being found in at step 2 thenTy:

1. Type in: depmod -a
2. Type in: modprobe ddbridge
3. Type in: ls -l /dev/dvb

 

4 minutes ago, kellekellner said:

So now there is a solution. I update to unraid 7.1.0 Rc1 an installed the plugin new. Now its working. 

Thanks for keeping me up to date, this is really strange, however thank you for keeping me up to date.

 

Would you mind sharing Diagnostics from your system now?

no problem. Thanks for your work!!!

tower-diagnostics-20250424-2139.zip

I’ve just updated to Unraid 7.2.0 (kernel 6.12.54-Unraid) and noticed that the latest DVB Driver bundle on GitHub is still for 6.8.12-Unraid.

I'd like to install the DVB drivers for my old Astrometa DVB-T2 USB stick, but at the moment there’s no matching LibreELEC or TBS build for this new kernel.

Although I read the recompile has been automated, could you please confirm if a 6.12.54-Unraid DVB driver package is planned or already in progress?

Many thanks for maintaining this plugin — it’s hugely appreciated!

1 hour ago, Bob_C said:

I’ve just updated to Unraid 7.2.0 (kernel 6.12.54-Unraid) and noticed that the latest DVB Driver bundle on GitHub is still for 6.8.12-Unraid.

I'd like to install the DVB drivers for my old Astrometa DVB-T2 USB stick, but at the moment there’s no matching LibreELEC or TBS build for this new kernel.

Please upload your Diagnostics, without them I can't say anything.

You are lokking in the wrong spot, the DVB Driver was transfered to the Unraid GitHub Repository.

Are you sure that your Plugin is up to date?

Again, Diagnostics would answer most of the questions and as said I can't help without them.

Hi, Thanks. Sorry about lack of diagnostics. I only installed the DVB plugin the other day for the first time (but didn't get 'round to installing any drivers) and then upgraded to Unraid to 7.2.0. today. I then tried to install the LibreELEC drivers, rebooted and nothing was detected.

root@NAS:~# modinfo cxd2841er | grep filename

filename: /lib/modules/6.12.54-Unraid/kernel/drivers/media/dvb-frontends/cxd2841er.ko.xz

Diagnostics attached.

nas-diagnostics-20251030-2254.zip

7 hours ago, Bob_C said:

I then tried to install the LibreELEC drivers, rebooted and nothing was detected.

From what I see everything is working fine:

Oct 30 14:58:31 NAS kernel: usb 1-3: dvb_usb_v2: found a 'Astrometa DVB-T2' in warm state

Oct 30 14:58:31 NAS kernel: usb 1-12.1: Found UVC 1.00 device KODAK Access Webcam (0c45:6366)

Oct 30 14:58:31 NAS kernel: usbcore: registered new interface driver uvcvideo

Oct 30 14:58:31 NAS kernel: usb 1-3: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer

Oct 30 14:58:31 NAS kernel: dvbdev: DVB: registering new adapter (Astrometa DVB-T2)

Oct 30 14:58:31 NAS kernel: usb 1-3: media controller created

Oct 30 14:58:31 NAS kernel: dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.

Oct 30 14:58:31 NAS kernel: i2c i2c-1: cxd2841er_attach(): attaching CXD2837ER DVB-C/T/T2 frontend

Oct 30 14:58:31 NAS kernel: i2c i2c-1: cxd2841er_attach(): chip ID 0xb1 OK.

Oct 30 14:58:31 NAS kernel: usb 1-3: DVB: registering adapter 0 frontend 0 (Realtek RTL2832 (DVB-T))...

Oct 30 14:58:31 NAS kernel: dvbdev: dvb_create_media_entity: media entity 'Realtek RTL2832 (DVB-T)' registered.

Oct 30 14:58:31 NAS kernel: usb 1-3: DVB: registering adapter 0 frontend 1 (Sony CXD2837ER DVB-T/T2/C demodulator)...

Oct 30 14:58:31 NAS kernel: dvbdev: dvb_create_media_entity: media entity 'Sony CXD2837ER DVB-T/T2/C demodulator' registered.

Oct 30 14:58:31 NAS kernel: r820t 2-003a: creating new instance

Oct 30 14:58:31 NAS kernel: r820t 2-003a: Rafael Micro r820t successfully identified, chip type: R828D

Oct 30 14:58:31 NAS kernel: r820t 2-003a: attaching existing instance

Oct 30 14:58:31 NAS kernel: r820t 2-003a: Rafael Micro r820t successfully identified, chip type: R828D

Oct 30 14:58:31 NAS kernel: rtl2832_sdr rtl2832_sdr.1.auto: Registered as swradio0

Oct 30 14:58:31 NAS kernel: rtl2832_sdr rtl2832_sdr.1.auto: Realtek RTL2832 SDR attached

Oct 30 14:58:31 NAS kernel: rtl2832_sdr rtl2832_sdr.1.auto: SDR API is still slightly experimental and functionality changes may follow

Oct 30 14:58:31 NAS kernel: rc_core: IR keymap rc-astrometa-t2hybrid not found

Oct 30 14:58:31 NAS kernel: Registered IR keymap rc-empty

Oct 30 14:58:31 NAS kernel: rc rc0: Astrometa DVB-T2 as /devices/pci0000:00/0000:00:14.0/usb1/1-3/rc/rc0

Oct 30 14:58:31 NAS kernel: input: Astrometa DVB-T2 as /devices/pci0000:00/0000:00:14.0/usb1/1-3/rc/rc0/input10

Oct 30 14:58:31 NAS kernel: usb 1-3: dvb_usb_v2: schedule remote query interval to 200 msecs

Oct 30 14:58:31 NAS kernel: usb 1-3: dvb_usb_v2: 'Astrometa DVB-T2' successfully initialized and connected

Oct 30 14:58:31 NAS kernel: usbcore: registered new interface driver dvb_usb_rtl28xxu

But can you please explain what you do here:

Oct 30 15:36:25 NAS emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/startScript.sh /tmp/user.scripts/tmpScripts/DVB_Driver_Compile/script

Oct 30 15:36:25 NAS DVB-BUILD: Starting DVB driver build helper…

and here:

Oct 30 15:37:51 NAS emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/startScript.sh /tmp/user.scripts/tmpScripts/DVB_Driver_Compile/script

Oct 30 15:37:51 NAS DVB-BUILD: Building DVB drivers for 6.12.54-Unraid via Docker container…

and finally you DVB device uninitializes:

Oct 30 17:29:26 NAS kernel: r820t 2-003a: destroying instance

Oct 30 17:29:26 NAS kernel: dvb_usb_v2: 'Astrometa DVB-T2:1-3' successfully deinitialized and disconnected

The above could also be related that you are using S3-Sleep and the device doesn't initialize properly again.

Sorry, but please remove everything custom that you are doing here and then try again, if you have no luck please upload new diagnostics.

I also have to say that you have so many custom things for power saving in your go file that I can't tell if this is causing this behavior.

Thanks again for the quick feedback earlier.
After your reply, I worked through a few cleanup and verification steps — here’s what was done and the outcome:

1. Removed all custom build scripts

   • Deleted the old user-script that tried to rebuild DVB drivers in a Docker container.

   • Confirmed I’m running stock LibreELEC DVB driver package from your plugin only.

2. Checked system config (go file, modules, etc.)

   • Commented out aggressive USB/XHCI wake-disable lines to prevent interference.

   • Ensured no custom /etc/modprobe.d/astrometa.conf entries remained.

   • Left autosuspend disabled (good for DVB stability).

3. Blacklisted conflicting SDR module

   • Added /boot/config/modprobe.d/blacklist-rtl2832sdr.conf to stop rtl2832_sdr loading, which was hijacking the stick’s SDR interface.

   • This allowed the proper Sony + SiLabs tuner path to initialise cleanly.

4. Installed Silicon Labs tuner firmware

   • Placed dvb-tuner-si2157-a30-01.fw, dvb-tuner-si2158-a20-01.fw, and dvb-demod-si2168-b40-01.fw in /lib/firmware.

   • Rebooted and verified the Sony CXD2837ER frontend attaches correctly (even if Si2157 doesn’t print verbose logs).

5. Updated to current muxes

   • Removed legacy >700 MHz frequencies.

   • Added valid local muxes (538 / 554 / 562 / 578 / 586 / 602 MHz).

6. Result

   • All muxes lock with Scan Status = OK and show the expected service counts in Tvheadend.

   • DVB-T and DVB-T2 both functioning normally.

   • Streams play perfectly; EPG data populating via OTA grabber.

Everything’s now stable and working 100 %. 👍

16 minutes ago, Bob_C said:

Placed dvb-tuner-si2157-a30-01.fw, dvb-tuner-si2158-a20-01.fw, and dvb-demod-si2168-b40-01.fw in /lib/firmware.

That won't help since this gets deleted every reboot, however these files are shipped with the LibreELEC package.

Again, you don't need to do anything custom when you install the DVB Plugin and the correct package for your Tuner.

1 hour ago, ich777 said:

That won't help since this gets deleted every reboot, however these files are shipped with the LibreELEC package.

Again, you don't need to do anything custom when you install the DVB Plugin and the correct package for your Tuner.

Thanks @ich777 — understood.

The extra firmware copies were only part of the troubleshooting process; they’re indeed cleared on reboot and, as you say, already included in the LibreELEC bundle.

The main issue turned out not to be missing firmware at all but the rtl2832_sdr module loading alongside the proper Sony + SiLabs path on the Astrometa stick.

Once that SDR module was blacklisted and the legacy >700 MHz muxes removed, the tuner initialised cleanly and every current local transmitter mux locked with Scan Status = OK in Tvheadend.

So we’re now 100 % operational using your stock LibreELEC drivers.

Appreciate the confirmation and all your ongoing work on this plugin!

Hey, installing the dvb drivers fresh on 7.2. I get the following error:

Package dvb-driver-2025.03.25.txz installed.
-----ERROR - ERROR - ERROR - ERROR - ERROR - ERROR - ERROR - ERROR - ERROR------
There are no GitHub API calls left for your IP.
The limit will be reset at: 2025-10-31 17:28:02

1 hour ago, knex666 said:

There are no GitHub API calls left for your IP.

There is nothing left to say and you see the issue.

Is something eating up your GitHub API calls in your local network? To install the driver you need at least one API call.

Do you have this monitoring solution in your network is named Pi something?

Hi

I have a TBS tuner that stopped being recognised a while ago and now I'm trying to get it working again. I deleted the plugin and reinstalled but whatever I do it wont recognise the card. Really don't know how to proceed now so any help appreciateds.

Diagnostics attached.

tower-diagnostics-20251109-1631.zip