Blindscan on linux with tbs cards

[deeptho]

So Fedora it is. That link I posted to GitHub give you all the info you need to get up and running.

Yes, and if you have questions or problems, you can ask for help here.

The CLI (command line interface) should pose no threat to anyone. Unlike pre internet days everything is copy/paste into the terminal so you can’t go wrong.

I think modern versions of linux also have an on-screen keyboard. So then you can even perform the installation with only clicking
like in windows. :->

I personally dislike the windows approach: you get an equal amount of problems, and no way to fix them.
On tiop of that you often have to pay for what you get for free on linux. Anyway...

What you’re mainly seeing are examples of users without the prerequisite skills in a Linux environment either going their own way in their choice of Linux flavours and expecting the instructions for another flavour to work off the bat without the necessary adjustments or not following instructions EXACTLY as laid out.

Just follow the instructions EXACTLY as Deeptho has laid out in that GitHub using Fedora and you won’t go wrong.

In most cases in the Linux kernel you’ll find that drivers are already baked in so all you need to ensure is the correct firmware resides in the /lib/firmware so the drivers can locate it and load it at boot time. In your case you’ll be following clearly laid out instructions from the GitHub so that shouldn’t be a consideration for you.

I suggest you get started and if you do come a cropper at any stage you have a very patient developer in the shape of Deeptho to guide you through the process and believe me he is very patient. Not alone will you succeed by the end of the process but you’ll have learnt a bit about Linux environment and wonder why you waited so long.

 

[deeptho]

One newbie question, are the DVB card and its linux drivers installed in the machine before the nuemo app install thereby allowing nuemo to detect it?
In windows I would generally install the DVB card and drivers before apps such as EBSPro and Crazy Scan?

No. software installation can be done with and without the cards. A reboot may be needed after installing the drivers, for reasons not related to neumodvb.

I suppose I should give it a try, all that can be lost is time and hair !

Yes, it could all be lost. Or not.

 

[sat-tv-fan]

Can anyone explain how to install the TBS driver for linux ? I have a 6903 card. I am currently using Mint as I got nowhere with Ubuntu. I tried to install from this page but I never get anywhere errors etc Home · tbsdtv/linux_media Wiki

 

[pk008]

late reply but i guess it will help others in future:

sed -i -r 's/(^CONFIG.*_RC.*=)./\1n/g' v4l/.config
sed -i -r 's/(^CONFIG.*_IR.*=)./\1n/g' v4l/.config

dont run (skip) these commands

 

[deeptho]

I have just updated the drivers and the command line tools for blindscanning.

In the drivers, I have integrated recent updates in the tbs drivers and I have fixed
a bug in those, which makes DVBS2 reception impossible after tuning some GSE muxes.

You can trigger the bug by sanning 11797.5H on 28.2E:-> If you do this, all DVBS2
muxes will not longer produce any output. You can reload the drivers or reboot
to recover.

The lock indicators have been improved to cover very low rollofs and special modulations
like on 11797.5H

The spectral scan algorithm has been updated to that of neuymoDVB.

The command line tools now include a parallel blindscanner:
command like

time ../build/src/stid135-blindscan  -cblindscan -a 0 1 2 3 4 5 6 7 -U0   --rf-in=2

scans 28.2E in 1 minute and 13 seconds and finds 77 muxes on tbs690x, using
all 8 adapters, using the lnb at rf input 2 (3rd connector on the card). It LNB
is selected using input 0 of an uncommitted switch.

The output file is in scan-s2 format.

the GUI program neumoDVB will be updated later

 

[Llew]

I have just updated the drivers and the command line tools for blindscanning.

In the drivers, I have integrated recent updates in the tbs drivers and I have fixed
a bug in those, which makes DVBS2 reception impossible after tuning some GSE muxes.

You can trigger the bug by sanning 11797.5H on 28.2E:-> If you do this, all DVBS2
muxes will not longer produce any output. You can reload the drivers or reboot
to recover.

The lock indicators have been improved to cover very low rollofs and special modulations
like on 11797.5H

The spectral scan algorithm has been updated to that of neuymoDVB.

The command line tools now include a parallel blindscanner:
command like

time ../build/src/stid135-blindscan  -cblindscan -a 0 1 2 3 4 5 6 7 -U0   --rf-in=2

scans 28.2E in 1 minute and 13 seconds and finds 77 muxes on tbs690x, using
all 8 adapters, using the lnb at rf input 2 (3rd connector on the card). It LNB
is selected using input 0 of an uncommitted switch.

The output file is in scan-s2 format.

the GUI program neumoDVB will be updated later

deeptho,
An executable in src/CMakeLists.txt at Line19 prevented me from building blindscan Only removing it alowed me to complete building neumotune.
I haven't had this error before; it's only since your update that I have come across the problem. Does it concern blindscanning with stid135? I'm not using that in the RPi.

 

[deeptho]

deeptho,
An executable in src/CMakeLists.txt at Line19 prevented me from building blindscan Only removing it alowed me to complete building neumotune.
I haven't had this error before; it's only since your update that I have come across the problem. Does it concern blindscanning with stid135? I'm not using that in the RPi.

As the error message says: it is an internal error in the linker of raspberri pi.

Do the other programs compile ok (use: make -k)?

You could try using another linker (remove -fuse-ld=gold in CMakeLists.txt(

You could try upgrading or downgrading the compiler, or the "gold" linker
or perhaps change it from clang++ to g++. Not sure if that will work.

In any case the bug is an RPI bug.

 

[Bobben_no]

I have installed the deeptho/linux_media from the github and installed it on ubuntu 22.04.02 (kernel 5.19.0-35). I have used it with other tools that use the DVB api and it works very well for my TBS6903 card. It finds symbol rate and modulation parameters automatically also when using other linux tools that can tune via api. That is really a nice feature. What I do not get to work is my tbs6908 which is also based on stv091x but there are two stv091xon the same PCIe card. I can not see that tbs6903 is supported in compatible cards listed on github but the stv091x tbs5927 is. I assume it is the support for tbs5927 that makes tbs6903 work. I have also a few tbs6908 cards but they are not even recognized in this driver and the system starts to behave strange. When doing lsdvb (and tslsdvb in tsduck) only error message appear but strangely my tbs6504 can still tune to transponders (even though lsdvb does not list the card. Looks like the stv091X based tbs6908 card running with this drivers cause errors in the dvb api or something. Not sure what logs I need to look at and what to searh for in the logs.

 

[deeptho]

I have installed the deeptho/linux_media from the github and installed it on ubuntu 22.04.02 (kernel 5.19.0-35). I have used it with other tools that use the DVB api and it works very well for my TBS6903 card. It finds symbol rate and modulation parameters automatically also when using other linux tools that can tune via api. That is really a nice feature.

Good to hear you had some success.

What I do not get to work is my tbs6908 which is also based on stv091x but there are two stv091xon the same PCIe card. I can not see that tbs6903 is supported in compatible cards listed on github but the stv091x tbs5927 is. I assume it is the support for tbs5927 that makes tbs6903 work. I have also a few tbs6908 cards but

6903 works according to others. I do not have this card myself. There may be minor problems.
The tbs6908 should also work, judging by the code, but: I have no such card and cannot test.

If it does not work, then the answer to "why" should be in the kernel log.

they are not even recognized in this driver and the system starts to behave strange. When doing lsdvb (and tslsdvb in tsduck) only error message appear but

Maybe they need firmware and it has not been installed? Did they work in the tbs drivers?

strangely my tbs6504 can still tune to transponders (even though lsdvb does not list the card. Looks like the stv091X based tbs6908 card running with this drivers cause errors in the dvb api or something. Not sure what logs I need to look at and what to searh for in the logs.

look in the kernel logs if you have them.
If there are none, then make sure rsyslog is installed, that /etc/rsyslog.conf has a line like
kern.debug /var/log/debug
and that rsyslog has been actually (re)started.
The messages will appear in /var/log/debug

Does the 6908 appear in /dev/dvb/adapter? And in the frontendlist of neumodvb?

 

[Bobben_no]

tbs6908 is working just fine when using the tbs drivers. I have re-added firmware in /lib/firmware
by running:

wget http://www.tbsdtv.com/download/document/linux/tbs-tuner-firmwares_v1.0.tar.bz2
sudo tar jxvf tbs-tuner-firmwares_v1.0.tar.bz2 -C /lib/firmware/

The whole ubuntu system has problem as it hangs when running "reboot". Need to force hard reboot by using power button.
With tbs driver system behaves normal.

I have copied some parts of kernel log etc. Not sure what to look so I start with this.

root@tsduck-ThinkStation-P330:~# ls -all /dev/dvb
total 0
drwxr-xr-x  3 root root   60 mars  10 10:07 .
drwxr-xr-x 20 root root 4360 mars  10 10:07 ..
drwxr-xr-x  2 root root  100 mars  10 10:07 adapter0

COMMENT: adapter1,2,3 from tb6908 missing

root@tsduck-ThinkStation-P330:~#  ls -all /dev/dvb/adapter0
total 0
drwxr-xr-x  2 root root     100 mars  10 10:07 .
drwxr-xr-x  3 root root      60 mars  10 10:07 ..
crw-rw----+ 1 root video 212, 0 mars  10 10:07 demux0
crw-rw----+ 1 root video 212, 1 mars  10 10:07 dvr0
crw-rw----+ 1 root video 212, 2 mars  10 10:07 net0

COMMENT: frontend missing for adapter0

grep -i 'stv09' /var/log/debug
2023-03-10T09:53:21.185938+01:00 tsduck-ThinkStation-P330 kernel: [    3.580579] stv0910: found STV0910 id=0x51

COMMENT: With tbs driver it lists four stv0910 from the tbs6908 card

grep -i 'tbs' /var/log/debug
2023-03-10T10:07:14.892934+01:00 tsduck-ThinkStation-P330 kernel: [    3.045490] TBSECP3 driver 0000:02:00.0: enabling device (0000 -> 0002)
2023-03-10T10:07:14.892934+01:00 tsduck-ThinkStation-P330 kernel: [    3.045842] TBSECP3 driver 0000:02:00.0: TurboSight TBS 6908 DVB-S/S2
2023-03-10T10:07:14.892935+01:00 tsduck-ThinkStation-P330 kernel: [    3.066987] dvbdev: DVB: registering new adapter (TBSECP3 DVB Adapter)
2023-03-10T10:07:14.892936+01:00 tsduck-ThinkStation-P330 kernel: [    3.188267] TBSECP3 driver 0000:02:00.0: adap=00000000120255e5 dvb_adap=0000000098913fa0 adap=0 MAC address 00:22:ab:92:95:ec
2023-03-10T10:07:15.010991+01:00 tsduck-ThinkStation-P330 kernel: [    3.288417] tbsecp3_frontend_attach:2444 SET rf_input_nr=0 (null)
2023-03-10T10:07:15.010994+01:00 tsduck-ThinkStation-P330 kernel: [    3.288419] tbsecp3_frontend_attach:2450 Got mac: 0xec9592ab2200
2023-03-10T10:07:15.010995+01:00 tsduck-ThinkStation-P330 kernel: [    3.288421] tbsecp3_frontend_attach:2454 adapter->fe=00000000da883652 dev=000000009e90de6b
2023-03-10T10:07:15.010996+01:00 tsduck-ThinkStation-P330 kernel: [    3.288423] tbsecp3_frontend_attach:2456 dev=000000009e90de6b dev->info=00000000f8662d8b
2023-03-10T10:07:15.011014+01:00 tsduck-ThinkStation-P330 kernel: [    3.288626]  ? tbsecp3_frontend_attach.isra.0.cold+0x377/0xaa6 [tbsecp3]
2023-03-10T10:07:15.011023+01:00 tsduck-ThinkStation-P330 kernel: [    3.288694]  tbsecp3_dvb_init+0x1ff/0x340 [tbsecp3]
2023-03-10T10:07:15.011024+01:00 tsduck-ThinkStation-P330 kernel: [    3.288718]  tbsecp3_probe.cold+0x317/0x484 [tbsecp3]
2023-03-10T10:07:15.011067+01:00 tsduck-ThinkStation-P330 kernel: [    3.288831]  tbsecp3_driver_init+0x23/0x1000 [tbsecp3]


Also found in dmesg:

[    3.288417] tbsecp3_frontend_attach:2444 SET rf_input_nr=0 (null)
[    3.288419] tbsecp3_frontend_attach:2450 Got mac: 0xec9592ab2200
[    3.288421] tbsecp3_frontend_attach:2454 adapter->fe=00000000da883652 dev=000000009e90de6b
[    3.288423] tbsecp3_frontend_attach:2456 dev=000000009e90de6b dev->info=00000000f8662d8b
[    3.288425] BUG: kernel NULL pointer dereference, address: 0000000000000000
[    3.288438] #PF: supervisor read access in kernel mode
[    3.288445] #PF: error_code(0x0000) - not-present page
and
[    3.288616] Call Trace:
[    3.288621]  <TASK>
[    3.288626]  ? tbsecp3_frontend_attach.isra.0.cold+0x377/0xaa6 [tbsecp3]
[    3.288640]  ? klist_class_dev_get+0x12/0x20
[    3.288648]  ? klist_add_tail+0x66/0x80
[    3.288656]  ? device_add+0x15d/0x7c0
[    3.288664]  ? device_create_groups_vargs+0xe6/0x100
[    3.288673]  ? device_create+0x49/0x80
[    3.288681]  ? dvb_register_device+0x467/0x740 [dvb_core]
[    3.288694]  tbsecp3_dvb_init+0x1ff/0x340 [tbsecp3]
[    3.288709]  ? request_threaded_irq+0x116/0x190
[    3.288718]  tbsecp3_probe.cold+0x317/0x484 [tbsecp3]
[    3.288727]  local_pci_probe+0x48/0x90
[    3.288735]  pci_call_probe+0x55/0x180
[    3.288742]  pci_device_probe+0x84/0x120
[    3.288750]  really_probe+0x1e1/0x3c0
[    3.288757]  __driver_probe_device+0x12a/0x1b0
[    3.288765]  driver_probe_device+0x23/0xd0
[    3.288774]  __driver_attach+0xc3/0x260
[    3.288780]  ? __device_attach_driver+0x160/0x160
[    3.288788]  bus_for_each_dev+0x80/0xe0
[    3.288795]  driver_attach+0x1e/0x30
[    3.288802]  bus_add_driver+0x187/0x230
[    3.288810]  driver_register+0x95/0x110
[    3.288817]  ? 0xffffffffc07af000
[    3.288823]  __pci_register_driver+0x68/0x80
[    3.288831]  tbsecp3_driver_init+0x23/0x1000 [tbsecp3]
[    3.288841]  do_one_initcall+0x46/0x220
[    3.288849]  ? kmem_cache_alloc_trace+0x1a6/0x330
[    3.288858]  do_init_module+0x52/0x220
[    3.288865]  load_module+0xb56/0xd40
[    3.288872]  ? kernel_read_file+0x245/0x2a0
[    3.288880]  __do_sys_finit_module+0xcc/0x150
[    3.288888]  ? __do_sys_finit_module+0xcc/0x150
[    3.288897]  __x64_sys_finit_module+0x18/0x30
[    3.288905]  do_syscall_64+0x59/0x90
[    3.288912]  ? do_syscall_64+0x69/0x90
[    3.288919]  ? exit_to_user_mode_prepare+0x3b/0xd0
[    3.288927]  ? syscall_exit_to_user_mode+0x2a/0x50
[    3.288935]  ? do_syscall_64+0x69/0x90
[    3.288941]  ? do_syscall_64+0x69/0x90
[    3.289464]  ? do_syscall_64+0x69/0x90
[    3.289980]  ? irqentry_exit+0x43/0x50
[    3.290478]  ? sysvec_call_function+0x4e/0xb0
[    3.290981]  entry_SYSCALL_64_after_hwframe+0x63/0xcd

 

[deeptho]

So does this problem go away when you remove the 6908 card from the system before booting?

 

[deeptho]

Please try to install the possible fix I have just added:

cd ...../media;
git pull # and check for errors!
cd ../media_build
make -j`nproc` #and check for errors
sudo make install

Of course you will need to reboot, especially after a kernel crash

If you show more kernel logs, then put all of them, starting from where the cards are getting loaded (all of them)

 

[Bobben_no]

So does this problem go away when you remove the 6908 card from the system before booting?

I tested it now and the system reboots without any issues when I remove the 6908 card.

 

[Bobben_no]

Please try to install the possible fix I have just added:

cd ...../media;
git pull # and check for errors!
cd ../media_build
make -j`nproc` #and check for errors
sudo make install

Of course you will need to reboot, especially after a kernel crash

If you show more kernel logs, then put all of them, starting from where the cards are getting loaded (all of them)

I did not see this post when I posted my previous message.
I will try this tomorrow.

 

[Bobben_no]

Please try to install the possible fix I have just added:

cd ...../media;
git pull # and check for errors!
cd ../media_build
make -j`nproc` #and check for errors
sudo make install

Of course you will need to reboot, especially after a kernel crash

If you show more kernel logs, then put all of them, starting from where the cards are getting loaded (all of them)

I got it to work now. I may have missed on the "git checkout master" as TBS media_build will use extra branch but maybe that was not the problem as the tbs6903 was working.
Not sure if your latest changes solved the problem or if me deleting media drivers before reinstalling correctly did solve the problem.
Before installing I run:

rm -rf /lib/modules/`uname -r`/updates/extra/media/
rm -rf /lib/modules/`uname -r`/kernel/drivers/media/

And then did the following :

git clone --depth=1  https://github.com/deeptho/linux_media.git ./media
git checkout master
make dir DIR=../media
make distclean
make -j`nproc`
./install.sh
reboot

I have not tested neumodvb yet but tbs6908 seems to work great now with other tools like tsduck. Symbolrate and modulation parameters gets detected automatically. Great job and thank you very much !

 

[deejaydee]

hello all,
As a happy owner of TBS6903x card for several years, I have installed Neumodvb application which is running well with standard TBS drivers (but of course without blind scan feature). Many thanks Deepthought for this excellent work !
Of course I want to use the blindscan feature, so I managed to install the blindscan drivers. But with no luck so far, after many tries and reinstalls.
I also tested multiple linux kernels. I even tested it on a Fedora 36 distrib. Not better

I currently have a fresh reinstall of ubuntu 22.04 and kernel 5.15.0.67 with all packages and drivers set as per official Deepthought instructions.
Compilation is successful without errors but after installation & reboot, the card loads with multiple i2c errors as well as a reduction of the screen resolution. I've read all previous posts and tried many things, but still no luck so far.

Providing you the dmesg output (starting from driver load, as no specific error before that). Any clue ?

Also, here are my installation commands:
git clone GitHub - tbsdtv/media_build
git clone --depth=1 GitHub - deeptho/linux_media: TBS linux open source drivers ./media
cd media_build
make dir DIR=../media
make allyesconfig
make -j8
sudo make install
sudo reboot

After reboot, cat /sys/module/dvb_core/info/version is well providing "Neumo" version "1.5".

 

[deeptho]

@Bobben_no

That will not work. Please see the documentation in the drivers. You have simply installed some older, non blindscan drivers.

 

[deejaydee]

@Bobben_no

That will not work. Please see the documentation in the drivers. You have simply installed some older, non blindscan drivers.

I am sorry, I just installed once the drivers from a fresh Ubuntu install, following your instructions here: blindscan/INSTALL.md at master · deeptho/blindscan.
Unless instructions in this page are obsolete, I could not have installed older drivers, how could I ?
More help would be greatly appreciated, thank you.

 

[deeptho]

Fedora36 should work just fine. That is what I use.

There seem to be some problems:
TBSECP3 driver 0000:04:00.0: i2c nack (7)

There are some typical ubuntu related problems, which show that you have some mix of drivers.

3.324156] cec: disagrees about version of symbol rc_keyup
[ 3.324159] cec: Unknown symbol rc_keyup (err -22)
[ 3.324175] cec: disagrees about version of symbol rc_register_device
[ 3.324177] cec: Unknown symbol rc_register_device (err -22)
[ 3.324184] cec: disagrees about version of symbol rc_keydown
[ 3.324185] cec: Unknown symbol rc_keydown (err -22)
[ 3.324197] cec: disagrees about version of symbol rc_free_device
[ 3.324198] cec: Unknown symbol rc_free_device (err -22)
[ 3.324330] cec: disagrees about version of symbol rc_allocate_device
[ 3.324331] cec: Unknown symbol rc_allocate_device (err -22)
[ 3.324508] cec: disagrees about version of symbol rc_unregister_device
[ 3.324509] cec: Unknown symbol rc_unregister_device (err -22)

Why don't you simply try the installation procedure in the documentation?
Does it not work for you? What goes wrong?

GitHub - deeptho/linux_media: neumoDVB blindscan drivers media_tree

neumoDVB blindscan drivers media_tree. Contribute to deeptho/linux_media development by creating an account on GitHub.

github.com

 

[deejaydee]

Fedora36 should work just fine. That is what I use.

There seem to be some problems:
TBSECP3 driver 0000:04:00.0: i2c nack (7)

There are some typical ubuntu related problems, which show that you have some mix of drivers.

3.324156] cec: disagrees about version of symbol rc_keyup
[ 3.324159] cec: Unknown symbol rc_keyup (err -22)
[ 3.324175] cec: disagrees about version of symbol rc_register_device
[ 3.324177] cec: Unknown symbol rc_register_device (err -22)
[ 3.324184] cec: disagrees about version of symbol rc_keydown
[ 3.324185] cec: Unknown symbol rc_keydown (err -22)
[ 3.324197] cec: disagrees about version of symbol rc_free_device
[ 3.324198] cec: Unknown symbol rc_free_device (err -22)
[ 3.324330] cec: disagrees about version of symbol rc_allocate_device
[ 3.324331] cec: Unknown symbol rc_allocate_device (err -22)
[ 3.324508] cec: disagrees about version of symbol rc_unregister_device
[ 3.324509] cec: Unknown symbol rc_unregister_device (err -22)

Why don't you simply try the installation procedure in the documentation?
Does it not work for you? What goes wrong?

GitHub - deeptho/linux_media: neumoDVB blindscan drivers media_tree

neumoDVB blindscan drivers media_tree. Contribute to deeptho/linux_media development by creating an account on GitHub.

github.com

This is exactly what I did some days ago. Including with Fedora 36, including with this procedure you just mentioned.
I have just reinstalled my kernel ( sudo apt-get --reinstall install linux-modules-$(uname -r) linux-modules-extra-$(uname -r) && sudo apt install --reinstall linux-headers-$(uname -r) ). After reboot, everything was clean (normal screen resolution and no TBS driver loaded). Then I strictly applied your install procedure. compilation ended without error > reboot, and similar issue after reboot (some other version conflict on some other components this time). See attached dmesg. I don't know what else to try