Blindscan on linux with tbs cards

[deeptho]

Just reboot; then run neumoDVB, make a screenshot of the frontend lust; Then report the kernel log messages in /var/log/debug (all since
the last boot) and of /tmp/neumo.log

 

[JDavid22]

Hello again, I am sending information, I think I will reinstall everything again, unless you have a better opinion.

 

[deeptho]

Hello again, I am sending information, I think I will reinstall everything again, unless you have a better opinion.

Why would yoy do that? Nothing good can come result from that

 

[deeptho]

It seems there is a kernel crash because of some missing entry for tbs6522. I have tried to fix it, so please try again.
It should be something like this (from memory).

cd ~/blindscan_kernel/media
git reset --hard
git pull
cd ../media_build
make -j8
#check for error
sudo make install
#then reboot

If the fix works, then the frontendlist will not be empty

 

[JDavid22]

This part has been solved, now I will continue reading how to do the job with NeumoDvb.

I am very grateful to you for all the support.

 

[deeptho]

This part has been solved, now I will continue reading how to do the job with NeumoDvb.

I am very grateful to you for all the support.

First step is to check the satellite list (the default is for western europe; add one or more satellites when needed).
Then add an LNB and try a spectrum scan.

I see that DVB_T/C also appears. For American standards, some code changes would be needed.

 

[JDavid22]

Already something night I have started to test ku 123w and 67w(dvbs2x) and C with 99w, I am reading all the information of the forum and the documentation to refine details and later to ask that there is a lot¡ . My tbs6522 card presents many problems in windows something about i2c that no idea about that but they say it is a bug, I also read something about modifying some file to "correct" i2c_speed ? this problem in other cards, I do not know if it is valid for mine. At the moment it finds the mux quickly, it scans slow, I don't know if here as in windows there is blindscan2 or I am doing wrong the configuration or omitting something...(continue reading..) All north america is using the atsc standard and I think my card is not compatible so I don't know if it is possible to make it work, I have never tried it with crazyscan2 in windows. .by the way I am not in USA, I live in Mexico and I use translator to understand everything you write, I don't use linux either, I had to learn the basics from Debian, Ubuntu and Fedora, here everything was easier to configure and with your help and everyone's help here we are ready to continue learning. Thanks again.

 

[satesco]

Already something night I have started to test ku 123w and 67w(dvbs2x) and C with 99w, I am reading all the information of the forum and the documentation to refine details and later to ask that there is a lot¡ . My tbs6522 card presents many problems in windows something about i2c that no idea about that but they say it is a bug, I also read something about modifying some file to "correct" i2c_speed ? this problem in other cards, I do not know if it is valid for mine. At the moment it finds the mux quickly, it scans slow, I don't know if here as in windows there is blindscan2 or I am doing wrong the configuration or omitting something...(continue reading..) All north america is using the atsc standard and I think my card is not compatible so I don't know if it is possible to make it work, I have never tried it with crazyscan2 in windows. .by the way I am not in USA, I live in Mexico and I use translator to understand everything you write, I don't use linux either, I had to learn the basics from Debian, Ubuntu and Fedora, here everything was easier to configure and with your help and everyone's help here we are ready to continue learning. Thanks again.

The 6522 cards can be used with Crazyyscan2 without a problem. I didn't have to intervene or change files.
Moreover, I scanned cable with one tuner and satellite with another simultaneously.
When I have time, I will check the card with neumoDVB.

 

[deeptho]

Already something night I have started to test ku 123w and 67w(dvbs2x) and C with 99w, I am reading all the information of the forum and the documentation to refine details and later to ask that there is a lot¡ . My tbs6522 card presents many problems in windows something about i2c that no idea about that but they say it is a bug, I also read something about modifying some file to "correct" i2c_speed ? this problem in other cards, I do not know if it is valid for mine. At the moment it finds the mux quickly, it scans slow, I don't know if here as in windows there is blindscan2 or I am doing wrong the configuration or omitting something...(continue reading..) All north

Slow is relative. How long does it take?

neumoDVB uses a high resolution spectrum. Crazyscan uses a low resolution spectrum which is faster and worse quality.

You talk about "i2c" problems, but is there actually any evidence that something goes wrong? If there are problems they should be visible
in the kernel log.

america is using the atsc standard and I think my card is not compatible so I don't know if it is possible to make it work, I have never tried it with crazyscan2 in windows. .by the way I am not in USA, I live in Mexico and I use translator to understand everything you write, I don't use linux either, I had to learn the basics from

Yes, by America I meant the continent. Not sure about which terrestrial standards operate in your country, but my guess would be that it is similar
to the USA.

Debian, Ubuntu and Fedora, here everything was easier to configure and with your help and everyone's help here we are ready to continue learning. Thanks again.

Let me know how it goes...

 

[JDavid22]

I don't know if I put more order in the LNB and Mux configurations, Neumodvb scans and finds Mux's but not services makes it better but the problem persists, I don't know if update that was done in linux_media for tbs6522 is relevant...I will do more tests from scratch and later I will send some screenshots as well as the respective logs maybe I will find something that will help.
The times I mean that sometimes it does it fast especially in C band but in ku band it always stops and takes a long time to advance or does not advance and I have to start again. I hope I can explain myself. Good afternoon!

 

[deeptho]

I don't know if I put more order in the LNB and Mux configurations, Neumodvb scans and finds Mux's but not services makes it better but the problem persists, I don't know if update that was done in linux_media for tbs6522 is relevant...I will do more tests from scratch and later I will send some screenshots as well as the respective logs maybe I will find something that will help.

It is not clear what problem you have. Services will be scanned if there are services on the mux. Otherwise not.

The times I mean that sometimes it does it fast especially in C band but in ku band it always stops and takes a long time to advance or does not advance and I have to start again. I hope I can explain myself. Good afternoon!

That could be a bug, but you will have to explain better.

 

[JDavid22]

Here is some information about the tbs6522 card, hopefully the performance of the tbs can be improved....

 

[deeptho]

I assume you mean that almost nothing is locked? Or do you mean the time it takes?

The log files show many i2c errors which explains why little is tuned.

It could be a bug (I have not tested much with si2183 cards) or a hardware problem.

If it is a bug, I suspect it is due to "parallel" scanning and perhaps the driver not being well protected to multiple
simultaneous accesses. Last time I tested the si2183 driver there was no parallel blindscan yet.

What happens if you do NOT use blindscan all, but click each peak one by one and press the tune button and then wait until
the scan ends (give it 30-40 seconds each time)

Do you then get more muxes? And can you also provide log files for that experiment.

It will help me to find out if there is a problem with the drivers.

 

[JDavid22]

It takes longer than normal...in ebs pro it finds almost most of the tps and channels in a test I did in the same satellite 117w it finished in 3min with 52 tps found 195 channels in total, in neumodvb it did not find valid mux most of them in red color, it only found like 5 mux's and like 5 services in total. I will do the test you ask me and upload more information. Thank you.

 

[JDavid22]

I am sending more information, I hope it can help.

When I scan mux by mux in C band it works fine, but in Ku band, the problem persists.

Thank you.

 

[deeptho]

I did some experiments with my tbs6504 and found that the chip itself wronly reports the nature of the streams. The driver seems to do the right thing, but the result is wrong. neumoDVB changed over the years and did not care about the stream type in the past but now it does. Workarounds are possible to solve this problem, but the first thing to know is if GSE and GCE streams are actually supported by the si21832 based cards.

So I tried crazyscan and ebspro under windows but neither of them seems to work with the card: the spectrum is completely constant, tuning does not work. ebspro freezes. This is not the most recent version, but also a not very old version of streamreader.

Any suggestions on how to solve this (I will update the software of course).

Or on what happens on non-transport streams (GSE, GS) under windiws with tbs6504 or tbs6522 on GSE and GCS transponders such as 52E 11245V. And what does it do with DVB multistreams such as those on 5.0W. In all cases: does it lock? What is reported about the details of the stream?

Regarding the i2c problems: these seem to happen under very specific circumstances also on my card. I will need to investigate further.

The workaround is now in the latest drivers. So canning will work again, but GSE and GCS streams will not be locked or wrongly reported as
transport strewams. Note that this will be 2x slower than on tbs6903x and 8x slower than on tbs6909x. It will also be slower than crazyscan, because more information is extracted from the stream and each locked dvb mux then can take 30-60 seconds. Nothing can be done about
that, except scanning multiple muxes in parallel if the hardware supports it

 

[Llew]

what does it do with DVB multistreams such as those on 5.0W.

IThe TBS 6522 doesn't lock on this example multistream TP for me. Fine on a regular transponder with an equivalent signal strength.

 

[satesco]

@Llew, I will check the 6522 cards on the MIS at 5.0W, but until then, I will say that the last time I checked it at this position, the card worked fine with Crazyscan, and I could use it for Italian and French TV programs.

 

[Llew]

@Llew, I will check the 6522 cards on the MIS at 5.0W, but until then, I will say that the last time I checked it at this position, the card worked fine with Crazyscan, and I could use it for Italian and French TV programs.

OK now, wrong PLS code

Just need now to sort out the TBS6522 problem in neumodvb.

 

[deeptho]

I expected DVB multistreams to work. So that is confirmed. The remaining quesion is about GCS and GSE multistreams (like on 52.0E)