Help Required Issue with TBS6904SE and Two-Level DiSEqC (1.1 and 1.0) Scanning

[a.golbin]

Hello all,

I have successfully compiled the deeptho/linux_media drivers for the TBS6904SE card on Ubuntu Server 24.04 (kernel 6.8.0-71-generic) with the m88rs6060 demodulator (firmware version 30). All /dev/dvb/adapter[0–19] directories are detected for my 5 number of TBS6904SE cards, and dmesg confirms proper I2C communication and firmware loading. Compilation on Ubuntu 22.04 and 20.04 failed due to kernel incompatibilities.

System setup:

• Server: HP DL580 G9, 2× Intel Xeon E7-8880 v4 @ 2.20 GHz, 32 GB RAM
• LNB: Universal (9750 / 10600 MHz)
• Satellite: Eshail-2 @ 26°E

The problem:
I am unable to scan a known transponder (11045 MHz, SR 27500, H pol, DVB-S2) on Eshail-2 using two-level DiSEqC (1.1 position 2 + 1.0 position 3) via neumo-blindscan, even though this setup works fine on a standalone satellite receiver.


Example command:

neumo-blindscan --adapter 16 --lnb-type 1 --diseqc UC --uncommitted 1 --committed 2 \
--start-freq 10970000 --end-freq 22000000 --step-freq 1000 --pol 3 --delsys DVBS2

I have tried all possible values for --uncommitted and --committed with no success.
dmesg shows DiSEqC commands being sent (e.g., e0 10 39 f2, e0 10 38 fe), but the scan times out with partial lock (reg08=0x47, stat=0x23) and finds no channels.


Limitations observed:

• dvbv5-scan fails (no two-level DiSEqC support).
• neumoDVB GUI installation blocked by dependency issues.
• neumo-blindscan has no direct --freq / --sr option for single-transponder scans.

My questions:

1. Does the TBS6904SE fully support two-level DiSEqC (1.1 + 1.0) with deeptho drivers on kernel 6.8?
2. Are there patches or driver settings to enable single-transponder scanning with neumo-blindscan?
3. Any updated drivers or alternative scanning tools recommended for this setup?

Thanks in advance for any guidance.

 

[deeptho]

Hello all,

I have successfully compiled the deeptho/linux_media drivers for the TBS6904SE card on Ubuntu Server 24.04 (kernel 6.8.0-71-generic) with the m88rs6060 demodulator (firmware version 30). All /dev/dvb/adapter[0–19] directories are detected for my 5 number of TBS6904SE cards, and dmesg confirms proper I2C communication and firmware loading. Compilation on Ubuntu 22.04 and 20.04 failed due to kernel incompatibilities.

System setup:

• Server: HP DL580 G9, 2× Intel Xeon E7-8880 v4 @ 2.20 GHz, 32 GB RAM
• LNB: Universal (9750 / 10600 MHz)
• Satellite: Eshail-2 @ 26°E

The problem:
I am unable to scan a known transponder (11045 MHz, SR 27500, H pol, DVB-S2) on Eshail-2 using two-level DiSEqC (1.1 position 2 + 1.0 position 3) via neumo-blindscan, even though this setup works fine on a standalone satellite receiver.


Example command:

In your example command you forgot to set --rf-in

Also some diseqc swicthes react slowly. So instead of "--diseqc UC" use "--diseqc UCUC"

I have tried all possible values for --uncommitted and --committed with no success.
dmesg shows DiSEqC commands being sent (e.g., e0 10 39 f2, e0 10 38 fe), but the scan times out with partial lock (reg08=0x47, stat=0x23) and finds no channels.


Limitations observed:

• dvbv5-scan fails (no two-level DiSEqC support).
• neumoDVB GUI installation blocked by dependency issues.

There should not be any dependency issues in 24.4. Other people have it working.

• neumo-blindscan has no direct --freq / --sr option for single-transponder scans.

My questions:

1. Does the TBS6904SE fully support two-level DiSEqC (1.1 + 1.0) with deeptho drivers on kernel 6.8?

Yes, but older versions can have bugs. You need to install the latest version to have more bugs fixed.
Especially 6.8 was a really bad kernel itself.

1. Are there patches or driver settings to enable single-transponder scanning with neumo-blindscan?

No. Instead, you can specify start_freq and end_freq close to each other

1. Any updated drivers or alternative scanning tools recommended for this setup?

Thanks in advance for any guidance.

The newest versions (of everything)

 

[a.golbin]

Thanks for your previous guidance.

In your example command you forgot to set --rf-in

Also some diseqc swicthes react slowly. So instead of "--diseqc UC" use "--diseqc UCUC"

I added --rf-in and used --diseqc UCUC as follows:

neumo-blindscan --adapter 0 --rf-in 0 --lnb-type 1 --diseqc UCUC --uncommitted 1 --committed 2 --start-freq 11000000 --end-freq 11100000 --step-freq 1000 --pol H --delsys DVBS2

Yes, but older versions can have bugs. You need to install the latest version to have more bugs fixed.
Especially 6.8 was a really bad kernel itself.

I installed Ubuntu Server 25.04 (6.14.0-27-generic) and ran the above command after installing the neumo driver and neumo-blindscan from the deeptho GitHub repository.

Unfortunately, I still cannot scan any channels.
The dmesg log is attached.

 

[deeptho]

Thanks for your previous guidance.


I added --rf-in and used --diseqc UCUC as follows:

neumo-blindscan --adapter 0 --rf-in 0 --lnb-type 1 --diseqc UCUC --uncommitted 1 --committed 2 --start-freq 11000000 --end-freq 11100000 --step-freq 1000 --pol H --delsys DVBS2

I installed Ubuntu Server 25.04 (6.14.0-27-generic) and ran the above command after installing the neumo driver and neumo-blindscan from the deeptho GitHub repository.

Unfortunately, I still cannot scan any channels.
The dmesg log is attached.

You do not provide enough infotmation: trhe kernel log does not show the driver version, the program log is missing, console output is missing as well.
Step-freq is not needed and is probably much too large.
You should also add --blindscan-method=fft

 

[a.golbin]

The --blindscan-method was set on fft by default.
The problem solved by adding--spectrum-method=fft and select correct command.

Thanks.

 

[deeptho]

The --blindscan-method was set on fft by default.
The problem solved by adding--spectrum-method=fft and select correct command.

Thanks.

good!

 

[a.golbin]

New issue!

If I use scan-s2, w_scan or w_scan_cpp on an adapter before using neumo-tune, then calling neumo-demux on the same adapter causes it to go into D+ state and hang until reboot.

In kern.log I see the following errors repeated infinitely:

2025-09-02T18:03:27.949615+03:30 sahand kernel: m88rs6060_read_status:2897 delsys=6
2025-09-02T18:03:27.954968+03:30 sahand kernel: m88rs6060_get_matype:1553 delsys=DVBS2 matype reg[0xe9]=242 i=1
2025-09-02T18:03:27.954996+03:30 sahand kernel: m88rs6060_read_status:3091 itmp=62 signal=4050 noise=65 cnr=17924
2025-09-02T18:03:27.957761+03:30 sahand kernel: m88rs6060_get_per:2824 pre_bit_count=0/0
2025-09-02T18:03:27.957781+03:30 sahand kernel: m88rs6060_tune:3505 called m88rs6060_read_status r=0 status=0x21f
2025-09-02T18:03:28.165651+03:30 sahand kernel: dvb_frontend: dvb_frontend_thread:840: fe9 calling tune: re_tune=0
2025-09-02T18:03:28.165671+03:30 sahand kernel: m88rs6060_read_status:2897 delsys=6
2025-09-02T18:03:28.171956+03:30 sahand kernel: m88rs6060_get_matype:1553 delsys=DVBS2 matype reg[0xe9]=242 i=1
2025-09-02T18:03:28.174074+03:30 sahand kernel: m88rs6060_read_status:3091 itmp=62 signal=4050 noise=65 cnr=17924
2025-09-02T18:03:28.174094+03:30 sahand kernel: m88rs6060_get_per:2824 pre_bit_count=0/0
2025-09-02T18:03:28.174097+03:30 sahand kernel: m88rs6060_tune:3505 called m88rs6060_read_status r=0 status=0x21f
2025-09-02T18:03:28.381863+03:30 sahand kernel: dvb_frontend: dvb_frontend_thread:840: fe9 calling tune: re_tune=0

I don't have this issue on TBS driver.

Questions:

1. How can I solve this issue?
2. Is there any scan tool fully compatible with the Deeptho driver?