[Plugin] DVB-Driver

[ich777]

7 hours ago, MatthewH12 said:

EDIT: I just found out I have two cards with two different dates, so I swapped my C2013 card for a C2009 card, and it now shows in the DVB-driver page! 😮

That should not be an issue anyways, from what I see in the syslog everything is loaded fine and should be ready to use.

 

 Feb 16 15:17:31 HomeSRV kernel: saa7164_downloadfirmware() no first image

 

This is the only line that is suspicious to me but the firmware gets loaded correctly afterwards.

 

7 hours ago, MatthewH12 said:

Now to figure out how to pass it through to my plex docker.

I think you should use something in between like TVHeadend, Plex can be really "special" when it comes to DVB cards, but it should be enough if you simply pass through the device /dev/dvb in the template like:

 

[MatthewH12]

I think you should use something in between like TVHeadend, Plex can be really "special" when it comes to DVB cards, but it should be enough if you simply pass through the device /dev/dvb in the template like:

 

Got any tips for setting up tv headend with Plex?


Sent from my iPhone using Tapatalk

[ich777]

39 minutes ago, MatthewH12 said:

Got any tips for setting up tv headend with Plex?

Not really but maybe @alturismo can help with that. I'm not really the Plex guy...

[alturismo]

59 minutes ago, MatthewH12 said:

Got any tips for setting up tv headend with Plex?

21 minutes ago, ich777 said:

Not really but maybe @alturismo can help with that. I'm not really the Plex guy...

 

sure, but may ahead, if your final goal is only Plex you 1st should check what @ich777 pointed at, just add the device like /dev/dvb to Plex and check if the tuner(s) are recognized, if not but they are working in tvheadend then ...

 

you need a proxy between tvheadend and plex, look in CA either for

 

- xteve - more options, insert own EPG, map like you want, remux to standard streams with different types, ...

- tvhproxy - simple, was the 1st before i made my own with xteve, worked nice

- antenna - never tried but i guess more or less same like tvhproxy

- ...

 

there are some solutions therefore out there, take a look what you prefer, in the end we all emulate a hdhr device which plex accepts

[MatthewH12]

23 hours ago, ich777 said:

That should not be an issue anyways, from what I see in the syslog everything is loaded fine and should be ready to use.

 

 Feb 16 15:17:31 HomeSRV kernel: saa7164_downloadfirmware() no first image

 

This is the only line that is suspicious to me but the firmware gets loaded correctly afterwards.

 

I think you should use something in between like TVHeadend, Plex can be really "special" when it comes to DVB cards, but it should be enough if you simply pass through the device /dev/dvb in the template like:

 

Thank you so very much. Once I switched to the main PMS docker build instead of binhex's, the DVB just showed up and I got everything working! Now I just need an antenna and I'm all set. Keep up the awesome work, it's really appreciated!!

Edited February 18, 2022 by MatthewH12

[koyakteruk]

Hi, 
I just start playing with unraid this week, and I am trying to make my tuner mygica T230A to work.
I confirmed that the tuner can work in my windows 10 pc with windows driver.
The tuner is detected in tvheadend but when I tried to scan, it is showing failed status. 
When i run the command dmesg command, I can see some related error with the firmware probably related.
Attach below is the log.

lsusb -v: https://pastebin.com/tmP6jzL9
dmesg: https://pastebin.com/aCrqLVUV

Can someone help me to make this tune to work?
thanks in advance.

 

[  173.872659] si2168 1-0064: Direct firmware load for dvb-demod-si2168-d60-01.fw failed with error -2
[  173.872662] si2168 1-0064: firmware file 'dvb-demod-si2168-d60-01.fw' not found
[  173.876622] si2157 2-0060: found a 'Silicon Labs Si2141-A10'
[  173.876640] si2157 2-0060: Direct firmware load for dvb-tuner-si2141-a10-01.fw failed with error -2
[  173.876641] si2157 2-0060: firmware file 'dvb-tuner-si2141-a10-01.fw' not found
[  173.877234] usb 3-4: DVB: adapter 0 frontend 0 frequency 0 out of range (48000000..870000000)
[  173.879565] si2168 1-0064: Direct firmware load for dvb-demod-si2168-d60-01.fw failed with error -2
[  173.879567] si2168 1-0064: firmware file 'dvb-demod-si2168-d60-01.fw' not found
[  173.883678] si2157 2-0060: found a 'Silicon Labs Si2141-A10'
[  173.883687] si2157 2-0060: Direct firmware load for dvb-tuner-si2141-a10-01.fw failed with error -2
[  173.883689] si2157 2-0060: firmware file 'dvb-tuner-si2141-a10-01.fw' not found

 

[ich777]

27 minutes ago, koyakteruk said:

Can someone help me to make this tune to work?

What driver package are you using and on what Unraid version are you?

Can you please post your Diagnostics?

[koyakteruk]

11 hours ago, ich777 said:

What driver package are you using and on what Unraid version are you?

Can you please post your Diagnostics?

I am currently on Unraid Version 6.9.2 and using TBS-OpenSource.
Attached is the diagnostics.

tower-diagnostics-20220317-1341.zip

[ich777]

18 minutes ago, koyakteruk said:

TBS-OpenSource

May I ask why you are using the TBS package? This isn‘t a TBS Card…

The TBS package also doesn‘t have the firmware files included, please use the LibreELEC package instead, reboot and post the Diagnostics again after reboot.

[koyakteruk]

50 minutes ago, ich777 said:

May I ask why you are using the TBS package? This isn‘t a TBS Card…

 

The reason is when I change to LibreELEC, the stick is not detected in the page.
Attach is the diagnostics after changing to LibreELEC.

tower-diagnostics-20220317-1427.zip

Edited March 17, 2022 by koyakteruk

[ich777]

34 minutes ago, koyakteruk said:

The reason is when I change to LibreELEC, the stick is not detected in the page.

And with TBs OS it‘s detected?

 

What happens when you do:

ls -la /dev/dvb

from a Unraid terminal?

 

In general I don‘t recommend using USB tuners because they are often really unreliable.

[ich777]

13 hours ago, koyakteruk said:

mygica T230A

Now I remember this device, it is not guaranteed that it works on Linux even if the description says it's supported because newer devices use a slightly different Chipset that is not fully supported.

See this post from another user:

 

[koyakteruk]

29 minutes ago, ich777 said:

Now I remember this device, it is not guaranteed that it works on Linux even if the description says it's supported because newer devices use a slightly different Chipset that is not fully supported.

 

Ahh.. I see.. I guess I will sell this stick and buy new tbs card then.
Thanks for your help @ich777.

[ich777]

3 minutes ago, koyakteruk said:

Ahh.. I see.. I guess I will sell this stick and buy new tbs card then.

Yes, this would be my second recommendation.

I personally use DigitalDevices cards and had not a single issue, TBS Cards are not that expensive with the benefit of having a dual tuner or even more and they are reliable too, my third recommendation would be something like a DVB Sky card that I use in my Test server (if you can find one, they are really hard to get these days).

[koyakteruk]

Hi @ich777,

Just to update on my case, I change back to TBS, then I include the missing .fw into /lib/firmware.
and somehow it work in tvheadend. not sure for how long though.. lol.
I guess this is my workaround until my new tbs card arrived.

[ich777]

17 minutes ago, koyakteruk said:

Just to update on my case, I change back to TBS, then I include the missing .fw into /lib/firmware.
and somehow it work in tvheadend. not sure for how long though.. lol.
I guess this is my workaround until my new tbs card arrived.

I really don't recommend doing it that way because these firmware files are not tested with TBS-OS drivers and can cause actually crashes from what I found from my research, it only is working because TBS also offers a card with a similar tuner but not quite the same.

 

Please be really careful with such things!

[Shockracer]

Hey all, thanks for the plug-in!

 

I picked up a Hauppauge WinTV-quadHD PCI Express TV Tuner Card 1609, it has worked great for 5 to 6 days at a time, it will stop working and I have to restart UnRaid in order for it to start working again for another 5 to 6 days. This has gone on for about 2 months now. Any idea if there is an update coming or if this is a known issue with this card? I like the card as it's a quad tuner and a low profile PCI-E card.

 

Thank 

[ich777]

4 hours ago, Shockracer said:

Any idea if there is an update coming or if this is a known issue with this card?

This is a very strange behavior…

Can you please post your Diagnostigs before and after this happens?

 

How do you use the card on Unraid (TVHeadend - if you ise TVHeadend do you use the container or the plugin, Plex,…)?

[Shockracer]

On 3/18/2022 at 11:49 PM, ich777 said:

This is a very strange behavior…

Can you please post your Diagnostigs before and after this happens?

 

How do you use the card on Unraid (TVHeadend - if you ise TVHeadend do you use the container or the plugin, Plex,…)?

Plex, Live TV and DVR

[ich777]

2 hours ago, Shockracer said:

Plex, Live TV and DVR

I think you only tried to implement ot in Plex or am I wrong?

Can you try if it‘s working in TVHeadend and stays there?

Plex can be a bit special when adding TV cards directly.

 

Your Diagnostics would also be very helpful after the TV card dropped.

[jnk22]

Hi, I am having some problems with my Digital Devices cards since upgrading from 6.9.2 to 6.10-rc3/4.

 

When starting a stream, my logs are getting spammed with this message:

Mar 21 10:31:07 Eutronik kernel: ddbridge 0000:01:00.0: Frontend requested software zigzag, but didn't set the frequency step size

 

I have both DVB-S2 and DVB-C2 cards installed, however last time it was when tuning on a DVB-C2 channel.

Due to the frequent error logging, I have to restart every other day to prevent my log being filled up to 100%.

 

I have waited for the 6.10-rc4 release, but that didn't solve this issue unfortunately 😐

 

---

 

I have done some research regarding this error message, this line has been added at 2022-01-14:

https://github.com/DigitalDevices/dddvb/commit/b6d2a37ac21c6c49830dda085d0176cd9320395f

(file: dvb-core/dvb_frontend.c)

 

Checking your compile script for DD drivers, these seem to be included in your sources - as they are currently in the master branch.

 

Is it possible to manually override the source with an older version of the dddvb drivers? e.g. with 0.9.38pre3 which doesn't have those lines included?

 

There is also a thread in a mailing list:

https://www.spinics.net/lists/kernel/msg3876756.html

There is a line which includes dev_warn_once() instead of dev_warn(), as it is currently being used. I don't know if this would change anything though..

 

dmesg_2022-03-21_10-21.txt lspci-output_2022-03-21_10-21.txt

Edited March 21, 2022 by jnk22
replaced screenshot of dvb-drivers

[ich777]

20 minutes ago, jnk22 said:

Hi, I am having some problems with my Digital Devices cards since upgrading from 6.9.2 to 6.10-rc3/4.

Can you please send me over your Diagnostics too?

 

20 minutes ago, jnk22 said:

I have waited for the 6.10-rc4 release, but that didn't solve this issue unfortunately 😐

That is really unfortunate since I'm running 2x DigitalDevices Cine C/T V6.5 and they are working without a hitch on every Unraid version so far, including the RC versions.

 

21 minutes ago, jnk22 said:

Checking your compile script for DD drivers, these seem to be included in your sources - as they are currently in the master branch.

These are included in the latest build since I build them every time from source when a new Unraid version is released.

 

Please post your Diagnostics so that I can investigate further.

[ich777]

 @jnk22 oh, what I forgot to say is that you always can try the LibreELEC package since this will also work with DigitalDevices cards and is usually a fair bit behind the "proprietary" drivers.

[jnk22]

Thank you for your quick reply!

 

Sure, my diagnostics are attached now

 

Is it normal, that those mentioned lines will not be visible at the diagnostics/log/syslog.txt file?

 

Mar 21 10:59:29 Eutronik kernel: ddbridge 0000:01:00.0: Frontend requested software zigzag, but didn't set the frequency step size
Mar 21 10:59:30 Eutronik kernel: ddbridge 0000:01:00.0: Frontend requested software zigzag, but didn't set the frequency step size
Mar 21 10:59:31 Eutronik kernel: ddbridge 0000:01:00.0: Frontend requested software zigzag, but didn't set the frequency step size
Mar 21 10:59:32 Eutronik kernel: ddbridge 0000:01:00.0: Frontend requested software zigzag, but didn't set the frequency step size
Mar 21 10:59:33 Eutronik kernel: ddbridge 0000:01:00.0: Frontend requested software zigzag, but didn't set the frequency step size
Mar 21 10:59:34 Eutronik kernel: ddbridge 0000:01:00.0: Frontend requested software zigzag, but didn't set the frequency step size
Mar 21 10:59:34 Eutronik kernel: ddbridge 0000:01:00.0: Frontend requested software zigzag, but didn't set the frequency step size
Mar 21 10:59:35 Eutronik kernel: ddbridge 0000:01:00.0: Frontend requested software zigzag, but didn't set the frequency step size
Mar 21 10:59:36 Eutronik kernel: ddbridge 0000:01:00.0: Frontend requested software zigzag, but didn't set the frequency step size
Mar 21 10:59:37 Eutronik kernel: ddbridge 0000:01:00.0: Frontend requested software zigzag, but didn't set the frequency step size

 

This is just a short extract from my current log, in case you are wondering as well why they are not visible in the syslog.txt as well.

eutronik-diagnostics-20220321-1142.zip

Edited March 21, 2022 by jnk22
forgot to upload diagnostics

[ich777]

3 minutes ago, jnk22 said:

Is it normal, that those mentioned lines will not be visible at the diagnostics/log/syslog.txt file?

The lines are in there and listed that they repeated many many many many times...

 

May I ask with what container are you using the cards? TVHeadend or Plex? If TVHeadend the container or the plugin?

 

As said above, no issue here with such messages on my DigitalDevices Cine C/T V6.5, have to look into this, maybe try to select the LibreELEC driver, reboot and see if the same happens.