Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Plugin] DVB-Driver

Featured Replies

Sorry just seen your response ich777. Yes this is the thread I thought I was supposed to post in, but still made a mistake.

 

I use your plug in for docker libreelec using TVHeadend. I was just getting confused and I think maybe I did originally post in the right thread. Sorry. I'll try the right thread now.

  • Replies 1.1k
  • Views 176.1k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • @pika & @knex666 & @tknz & @Marolo & @fireplex & @pk1057   Good news for all TBS users!   I just asked Tom to include some necessary Kernel modules to Unraid wh

  • Available versions:   The build process is now automated and should be finished after 1 hour after a new unRAID version is released if everything went well and no compile error occurred.   You can che

  • Thank you!!

Posted Images

In the plugin, when I select "Plex PX Series Tuners (Japan)", the driver "nns779/px4_drv" is installed.
However, the developer of "nns779/px4_drv" has not been online since September 2021.

This driver has several problems.
 - The Linux kernel API has been changed and it does not work after Linux 6.4 series.
 - It has a problem with memory buffer management.

Therefore, Japanese users are using a forked version of px4_drv which fixes the problems.
https://github.com/tsukumijima/px4_drv

 

Could you please add an option to the plugin to install this forked version?
The build process is the same as the original nns779 version.

  • Author
59 minutes ago, cavaministrator said:

Could you please add an option to the plugin to install this forked version?
The build process is the same as the original nns779 version.

Thank you for the heads up!

Yes, please give me a bit and I will look into that and report back.

Are you on Unraid 6.12.10?

 

I just checked and the latest builds are already based on the repository from:

https://github.com/tsukumijima/px4_drv

 

Is it not working or what is the exact issue?

Did you reboot after changing the driver package?

Can you please share your Diagnostics if possible so that I can troubleshoot a bit further?

Is the driver maybe not loaded?

  • Author
Just now, cavaministrator said:

I thought the nns779 version had been adopted from past forum interactions.

Yes, this was the initial repository that I used to build the driver from but I now remember that I had issues building the driver for newer Kernels and also saw that repository and switched the build process over to the new one.

 

Glad to hear that everything is working. :)

  • 3 months later...

Does this work with a mygica a618b? If it does not does anyone know how to get it working?

  • Author
1 hour ago, evilgenius said:

Does this work with a mygica a618b? If it does not does anyone know how to get it working?

Do you have the card already?

If yes please post Diagnostics, HW IDs and the syslog would be interesting.

1 hour ago, ich777 said:

Do you have the card already?

If yes please post Diagnostics, HW IDs and the syslog would be interesting.

Yes I have the card. I can post the info tomorrow if that's ok.

  • Author
1 hour ago, evilgenius said:

Yes I have the card. I can post the info tomorrow if that's ok.

Sorry but I can't find any useful information on that USB Tuner...

It is not recognized, so it is possible it is not working on Linux, if you need a Tuner I would recommend that you stick with something that is known to be working on Linux:

  • TBS Tuners
  • Sundtek
  • DigitalDevices
  • Hauppauge
  • Author
1 hour ago, evilgenius said:

 

I mean it shows up in device list as gtek. So it is seen by unraid yeah?

 

A company that males a webcame with the device name TheBestWebCam will also show up there as TheBestWebCam but it won‘t work unless there is support for it.

 

1 hour ago, evilgenius said:

They do have linux drivers on their website.

If this is a proprietary driver I can‘t support it since I have to compile it for each Kernel version and if they don‘t support the newest Kernel you will be put of luck with the device.

And since they have to provide a dedicated package I think it‘s proprietary because otherwise it would be in the Linux Kernel and the plugin would work with this device.

 

Did you yet try the LibreElec package if it shows up with that?

 

It would be really interesting what hardware that they are using inside the device since then I can do more research.

5 hours ago, ich777 said:

A company that males a webcame with the device name TheBestWebCam will also show up there as TheBestWebCam but it won‘t work unless there is support for it.

 

If this is a proprietary driver I can‘t support it since I have to compile it for each Kernel version and if they don‘t support the newest Kernel you will be put of luck with the device.

And since they have to provide a dedicated package I think it‘s proprietary because otherwise it would be in the Linux Kernel and the plugin would work with this device.

 

Did you yet try the LibreElec package if it shows up with that?

 

It would be really interesting what hardware that they are using inside the device since then I can do more research.

I can take it apart for science lol

  • Author
1 hour ago, evilgenius said:

Here ya go.

MXL692 is part of the LibreELEC Package however I can't tell why it's not recognized, I really don't know what this AS-2056 chip is because the MXL692 is just the demodulator and not the tuner.

 

You could try to do:

modprobe mxl692

 

If the device is not working afterwards it is simply not supported. Sorry...

Yea I think I'll just get another. Sad cause it works great on windows lol. I was looking around linuxtv.org and nothing on that specific one there either.

 

Thanks for your time and help

  • 3 weeks later...

Hi,

 

Wondered if anyone can help?

 

I did have my TBS 6984 quad DVB-S2 card working with this plugin fine a few years ago, recently I have tried installing the card again and using the TBS OpenSource driver option but it looks like there is a problem somewhere, I am seeing:

 

root@Tower:~# dmesg|grep -i dvb
[    0.000000] Command line: BOOT_IMAGE=/bzimage initrd=/bzroot saa716x_tbs-dvb.int_type=1
[    0.058421] Kernel command line: BOOT_IMAGE=/bzimage initrd=/bzroot saa716x_tbs-dvb.int_type=1
[   25.266293] dvbdev: DVB: registering new adapter (SAA716x dvb adapter)
[   28.491089] DVB: Unable to find symbol isl6422_attach()
[   28.491666] SAA716x Budget 0000:03:00.0: DVB: registering adapter 0 frontend 0 (TurboSight TBS 6984 DVB-S/S2)...
[   28.491905] dvbdev: DVB: registering new adapter (SAA716x dvb adapter)
[   28.494167] DVB: Unable to find symbol isl6422_attach()
[   28.494722] SAA716x Budget 0000:03:00.0: DVB: registering adapter 1 frontend 0 (TurboSight TBS 6984 DVB-S/S2)...
[   28.494937] dvbdev: DVB: registering new adapter (SAA716x dvb adapter)
[   28.497367] DVB: Unable to find symbol isl6422_attach()
[   28.497925] SAA716x Budget 0000:03:00.0: DVB: registering adapter 2 frontend 0 (TurboSight TBS 6984 DVB-S/S2)...
[   28.498173] dvbdev: DVB: registering new adapter (SAA716x dvb adapter)
[   28.500750] DVB: Unable to find symbol isl6422_attach()
[   28.501310] SAA716x Budget 0000:03:00.0: DVB: registering adapter 3 frontend 0 (TurboSight TBS 6984 DVB-S/S2)...
[   90.605334] SAA716x Budget 0000:03:00.0: DVB: adapter 3 frontend 0 frequency 0 out of range (950000..2150000)
[   90.686522] SAA716x Budget 0000:03:00.0: DVB: adapter 2 frontend 0 frequency 0 out of range (950000..2150000)
[   92.171488] SAA716x Budget 0000:03:00.0: DVB: adapter 1 frontend 0 frequency 0 out of range (950000..2150000)
[   92.238677] SAA716x Budget 0000:03:00.0: DVB: adapter 0 frontend 0 frequency 0 out of range (950000..2150000)

 

Note the isl6422_attach issue.

 

I have measured the voltage out of my DVB-S2 card for the LNBs and it should be between 13 and 18 V DC but I get nothing. A quick google on ISL6422 shows it's responsible to providing power to LNBs so I am guessing this is the issue.

 

Note the card appears under /dev/dvb fine and configures in tvheadend container but a scan finds nothing and reports faint or no signal.

 

Any idea's please? (I tried libreelec driver and that doesn't find the card at all).

 

Thanks 🙂

  • Author
25 minutes ago, fireplex said:

Any idea's please? (I tried libreelec driver and that doesn't find the card at all).

Diagnostics please? :)

  • Author
1 minute ago, fireplex said:

Apologies, probably shouldn't have used the grep as I see other errors now which may mean my card doesn't have that chip...

From what I can see in your Diagnostics everything should work fine.

 

Is this a new instance from TVHeadend or is that the old existing one?

 

Please make sure the tuners is enabled and properly assigned to a network:

grafik.thumb.png.f98b4790997b6ddf6ecde9106d27c386.png

 

This message is usually a indication that something is not configured properly in TVHeadend.

Thanks for checking, it could be the card has a HW fault as I haven't used it for some time - I will see if I can find a Windows PC to try it in.

 

Yes, this is a fresh install of TVHeadend with a new appdata.

 

image.thumb.png.7ab1302cdb41e940f86c4d6b3bb4985c.png

 

image.thumb.png.37438d1c69a122840eb0824028a9a361.png

  • Author
1 hour ago, fireplex said:

it could be the card has a HW fault as I haven't used it for some time

I don't think so.

 

1 hour ago, fireplex said:

Yes, this is a fresh install of TVHeadend with a new appdata.

There is maybe a simple configuration step in TVHeadend missing, if you search for out of range here in this thread you'll see a few posts which the most of where misconfigured TVHeadend instances.
Maybe something at the network is wrong, however it seems the card is working properly.

A friend of mine is using a dual tuner DVB-S card from TBS which is working fine.

Just as an update I tried my Plex docker which did tune before, and that's also no longer finding any channels.

 

I'll see if I can try Windows tomorrow.

Tried a Windows box but it couldn't even find the card, so that was a non starter.

 

I've tried everything I can think of in tvheadend, I had previous notes on how to configure it and they didn't work either.

 

Is there anyway I can get dvbscan / dvb-apps installed on unRAID so I could try those at the CLI ?

  • Author
1 hour ago, fireplex said:

Is there anyway I can get dvbscan / dvb-apps installed on unRAID so I could try those at the CLI ?

Nope not easily.

 

1 hour ago, fireplex said:

I've tried everything I can think of in tvheadend, I had previous notes on how to configure it and they didn't work either.

Are you willing to upgrade to Unraid 7 and try it there (I run it on my main server and it is working perfectly fine. :)

I could try and upgrade to 7, are you thinking a newer kernel (presumably) may help?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.