Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Troubles regarding TBS6985 CARDS #51

Closed
pbjudby opened this issue Mar 4, 2018 · 13 comments
Closed

Troubles regarding TBS6985 CARDS #51

pbjudby opened this issue Mar 4, 2018 · 13 comments

Comments

@pbjudby
Copy link

pbjudby commented Mar 4, 2018

Hi Tbs.
As I can see you are using TBS tuner card. I have a TBS6985 DVB-S/S2 QUAD tuner - I downloaded and installed the latest drivers from TBS site - No problem - DVB Cards shows in dmesg
After compiling and installing ffdecsawrapper - I got the module dvbloopback men my TBS card is gone.
As long as I install FFdecsawrapper/dvbloopback --> my TBS is missing after reboot and gives this error i dmesg:

[ 4.472541] TurboSight TBS6985 DVB-S2 card port0 MAC=00:22:ab:90:81:a4 [ 4.472545] DVB: registering adapter 0 frontend 0 (TurboSight TBS 6985 DVBS/S2 frontend)... [ 4.472639] DVB: registering new adapter (SAA716x dvb adapter) [ 4.597165] r8169 0000:05:00.0 enp5s0: link down [ 4.597167] r8169 0000:05:00.0 enp5s0: link down [ 4.597201] IPv6: ADDRCONF(NETDEV_UP): enp5s0: link is not ready [ 4.945345] TurboSight TBS 6985 Frontend Attaching... [ 5.026146] TurboSight TBS6985 DVB-S2 card port1 MAC=00:22:ab:90:81:a5 [ 5.026148] DVB: registering adapter 1 frontend 0 (TurboSight TBS 6985 DVBS/S2 frontend)... [ 5.026281] DVB: registering new adapter (SAA716x dvb adapter) [ 5.497338] TurboSight TBS 6985 Frontend Attaching... [ 5.578146] TurboSight TBS6985 DVB-S2 card port2 MAC=00:22:ab:90:81:a6 [ 5.578148] DVB: registering adapter 2 frontend 0 (TurboSight TBS 6985 DVBS/S2 frontend)... [ 5.578289] DVB: registering new adapter (SAA716x dvb adapter) [ 6.049339] TurboSight TBS 6985 Frontend Attaching... [ 6.130140] TurboSight TBS6985 DVB-S2 card port3 MAC=00:22:ab:90:81:a7 [ 6.130143] DVB: registering adapter 3 frontend 0 (TurboSight TBS 6985 DVBS/S2 frontend)... [ 6.925499] r8169 0000:05:00.0 enp5s0: link up [ 6.925512] IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready [ 45.845220] random: nonblocking pool is initialized [ 186.583792] dvbloopback: disagrees about version of symbol dvb_register_adapter [ 186.583798] dvbloopback: Unknown symbol dvb_register_adapter (err -22) [ 186.583817] dvbloopback: disagrees about version of symbol dvb_generic_open [ 186.583820] dvbloopback: Unknown symbol dvb_generic_open (err -22) [ 186.583838] dvbloopback: disagrees about version of symbol dvb_unregister_device [ 186.583841] dvbloopback: Unknown symbol dvb_unregister_device (err -22) [ 186.583857] dvbloopback: disagrees about version of symbol dvb_generic_release [ 186.583859] dvbloopback: Unknown symbol dvb_generic_release (err -22) [ 186.583902] dvbloopback: disagrees about version of symbol dvb_register_device [ 186.583904] dvbloopback: Unknown symbol dvb_register_device (err -22) [ 186.583918] dvbloopback: disagrees about version of symbol dvb_unregister_adapter [ 186.583921] dvbloopback: Unknown symbol dvb_unregister_adapter (err -22)

PS: I have my "Old" Mythtv Backend which just been reinstalled along working with dvbcards and dvbloopback interface. But I cannot make this dvb card work - Since it missing after installing FFdecsawrapper/dvbloopback - and a remove of /lib/modules/$(uname -r)/kernel/drivers/media and then reinstalling the drivers does not do the trick _ Do you have any ideas ?

@bas-t
Copy link
Owner

bas-t commented Mar 4, 2018

If you need the official TBS drivers, you can use another repo I have:
git clone https://github.com/bas-t/tbs-dvbloopback.git

This will build and install the driver and the dvbloopback module in the right way.
You should start with a clean, unmodified kernel plus headers.

@bas-t bas-t closed this as completed Mar 4, 2018
@pbjudby
Copy link
Author

pbjudby commented Mar 5, 2018 via email

@bas-t
Copy link
Owner

bas-t commented Mar 6, 2018

You are welcome.
Mind you, TBS did not update the driver for a long time, so it is compatible up to linux-4.9.x
Cheers!

@pbjudby
Copy link
Author

pbjudby commented Mar 6, 2018 via email

@bas-t
Copy link
Owner

bas-t commented Mar 7, 2018

FYI:
Have a look here:

ljalves/linux_media#165

see the comment from this manio guy, his driver uses the same demod and tuner drivers as yours, so it should be possible to run your driver with even the latest rc kernels.

@pbjudby
Copy link
Author

pbjudby commented Mar 7, 2018 via email

@bas-t
Copy link
Owner

bas-t commented Mar 7, 2018

The init scripts always resided in my wiki, like in the links provided in the README. Almost everyone uses these scripts.

I just noticed that I never updated those links after switching domain names (probably due to the fact that this repo has become obsolete quite some time ago) . I corrected the links just now.

@bas-t
Copy link
Owner

bas-t commented Mar 7, 2018

BTW: this Manio guy contacted me I guess more than a year ago in order to get guidelines too.
I encouraged him to always build the driver you need in-tree, as it is imo the only way to ensure maximum stability. Takes more time though as you are compiling a complete kernel, but obviously, he did anyway.

Now, I had some spare time. And I like to tackle these kind of problems. So I started out with what I have and decided that I'm going to integrate TBS6985 into the kernel. I at first took the tbsdtv repository as a starting point to retrieve the needed out of tree drivers (tas2101 av201x). As you probably know, these demod and tuner drivers are out of tree like saa716x, and I guessed that since Luis Alves had stopped developing drivers, I'd be more up-to-date using the tbsdtv drivers.
Boy, was I wrong!!! You can see why in the commits I made to fix a bunch of compilation errors @ https://github.com/bas-t/dvbloopback/commits/test.

I don't mind fixing a bunch of compiling and other errors, but this was horrendous.

Then I read Manio's comment and switched to the Luis Alves' version of the out of tree drivers. I'm compile testing linux-4.15.7 right now. It appears to do a great job. Next I'll compile test the Debian Stretch stock kernel and if that goes well too, I'll be testing linux-4.16-rc4

If (when) all tests pass, I'll post instructions regarding how to proceed.

Cheers,
Tycho.

@bas-t
Copy link
Owner

bas-t commented Mar 7, 2018

I'm done. Fixing Luis Alves' version of the drivers for in-tree builds was like a walk in the park, compared with the tbsdtv version. And it was fun doing it. Of course I could only compile-test, as I don't have the hardware. So theoretically, you could run any current kernel, starting with linux-4.9.x, with both dvbloopback and TBS6985 drivers built in-tree now. I compile tested this with Debian Stretch stock kernel, longterm support kernels 4.9.x and 4.14.x, stable kernel 4.15.7 and RC kernel 4.16-rc4.

Should you want to test any of this in real life, you first of all need kernel-package and disable the backports repo in your sources.list. You can install kernel-package from buster or sid.

Now you can proceed:

git clone https://github.com/bas-t/dvbloopback.git && cd dvbloopback

git checkout test

./configure (or if you need the headers too: ./configure --headers=yes)

This will build and install a stock kernel (4.9.0-900-amd64 on Stretch). If you run it again, you'll get a 4.9.0-901 version, etc. So it is non-intrusive, you'll keep your current kernel as is.

Should you prefer building a vanilla kernel, do: ./configure --vanilla=4.15.7 --headers=yes (or something like that).

Best of luck,
Tycho.

@pbjudby
Copy link
Author

pbjudby commented Mar 8, 2018 via email

@bas-t
Copy link
Owner

bas-t commented Mar 23, 2018

Did you test this branch?
If you don't want/need it, I'll remove it.

@pbjudby
Copy link
Author

pbjudby commented Mar 26, 2018 via email

@bas-t
Copy link
Owner

bas-t commented Mar 26, 2018

Sorry to hear that, I nevertheless hope that your spine keeps supporting you in a good way.

I'll keep the branch with your driver untill you see a chanche to test it, take your time and recover.

Cheers,
Tycho.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants