neumoDVB

[Llew]

Ah.... Das U-Boot. That is a german submarine.
I have used it before on settop boxes and do things like booting different kernels. It required
a serial port connection.

For rpi, there is some info to use an other kernel here:

Raspberry Pi Kernel Compilation - eLinux.org

elinux.org

This would be the first solution.

There also seems to be exist procedure to be able to boot in more
pc like way. Boot a Raspberry Pi 4 using u-boot and Initramfs
It seems like a lot of work, but would be a 2nd solution.
However, tbs5927 is running fine here on linux with kernel 5.17.
You should use the latest blindscan drivers, because they have some fixes for a problem which prevents the upper Ku band being used.

So the third (and best) solution would be to fix the tbs5927 problem.


What happens when you disconnect and then reconnnect
the usb kabel to the RPI? Any kernel messages? They could shed some light on what goes on.

Also: does "lsmod" show that dvb_usb_tbs5927 is loaded?

If not, what happens when you execute "sudo modprobe dvb_usb_tbs5927"? And what messages appear in the kernel logs then?

The 4rd solution is to install a newer clang on the old ubuntu. The procedure is explained on the clang website. It was not too difficult,
but you should uninstall the old clang to avoid possible confusion.

Leaving Ubuntu Mate for now, as I still can't build neumodvb without errors.

I'm back on a previously working Ubuntu 22.04. this worked fine with TBS5927 and a T/T2 stick. It still has the images of the Frontends showing the List -



Disconnecting and reconnecting the 5927 shows it as being found in the kernel log -



No stv091x or stv6120 in lsmod. Modprobing for the card gives a false output -

"FATAL: Module dvb_usb_tbs5927 not found in directory /lib/modules/5.15.0-1022-raspi"

-as the kernel 5.15.0-1022 isn't the presently working kernel (1018). I've tried to purge it, but it still shows as 1022 in the uname command, so that is what you have in modprobe.

I think the best thing I can do for now is to re-install a new Ubuntu 22.04 and get a new kernel into lib/modules.

 

[deeptho]

Leaving Ubuntu Mate for now, as I still can't build neumodvb without errors.

I'm back on a previously working Ubuntu 22.04. this worked fine with TBS5927 and a T/T2 stick. It still has the images of the Frontends showing the List -

View attachment 147363

Disconnecting and reconnecting the 5927 shows it as being found in the kernel log -

View attachment 147362

No stv091x or stv6120 in lsmod. Modprobing for the card gives a false output -

"FATAL: Module dvb_usb_tbs5927 not found in directory /lib/modules/5.15.0-1022-raspi"

-as the kernel 5.15.0-1022 isn't the presently working kernel (1018). I've tried to purge it, but it still shows as 1022 in the uname command, so that is what you have in modprobe.

I think the best thing I can do for now is to re-install a new Ubuntu 22.04 and get a new kernel into lib/modules.

Llew,
that just means that no drivers have been installed. So you need to install the drivers.

 

[Llew]

Llew,
that just means that no drivers have been installed. So you need to install the drivers.

Drivers found for TBS5927 and PCTV dongle.

Spectrum and blindscanning OK apart from an occasional crash at end of scan. Muxes found with no crashing.

Raspberry Pi 4B 8GB and Ubuntu 22.04.

deeptho, where it always crashes is when choosing a channel to view. The errors are shown in the neumologs. Do they give you any clue as to what the problem could be?

 

[deeptho]

Llew,
at least you make some progress. When the program crashes, the interesting information is NEVER
in the log file but appears in the terminal.

Here, K:CN 1 works fine.


Possible problems:
-mpv not properly installed
-directory where video is stored not writeable
-something else...

 

[deeptho]

I have just release neumoDVB version 1.1. The most important changes are described below.

Note that there has been a second major change in how LNBs are defined. In case you haveset DiSEqC configurations
make a note of them before you upgrade.

Also note that there have been some changes to the drivers over the past couple of months. Specifically some important bugs were fixed
for tbs6903x and tbs5927. So make sure to update the drivers and to properly install them.

Main changes

• Database format has changed once more, but only regarding LNB definitions. The main change is that there is now on entry per physical LNB in the LNB list, whereas in the past there was a separate entry for each LNB input cable. This means that DiSEqC settings will have to be re-entered. The new format is explained in the documentation and was needed to allow some advanced features to work better.
• New layout of the LNB screen, with exactly one line per physical LNB. To "connect" an LNB to a card double-click on the cell in the connections column and add all tuners to which the LNB is connected. Most DiSEqC settings are associated with such a connection and need to be set on this connection, and no longer on the LNB itself. This allows neumoDVB to compute a single LOF correction value for each LNB instead of separately for each connection. Connections and networks in lnb list also follow a multi-line layout. Individual connections or networks that can not be currently used for some reason are shown as strike-through text.
• Estimate the current satellite position for offset LNBs and display it in the LNB list instead of the USALS pos which is more difficult to interpret for offset LNBs.
• New signal history feature which shows historic SNR for muxes. Use it to inspect signal degradation over time.
• In spectrum and positioner dialog only show muxes for frequencies supported by the LNB. For example, do not show C-band muxes for a Ku-band LNB/
• Ensure immediate consistency of networks, connections and other lnb fields across lnb list and positioner dialog and spectrum dialog. For example, when adding a network to an LNB in the LNB list, the new network can be selected in the spectrum dialog without having to close and reopen it.
• More useful, default sat selection when positioner is currently not pointing to any sat.
• Improved layout of spectrum dialog to also show the date when a spectrum was captured in the spectrum list.
• Identify all LNBs in the system by a small, never changing number, allowing for easier brief identification of cards. E.g. C0 means card 0. C1 card 1.... neumoDVB takes care of this numbering, but the user can change it.
• Blindscan search range is now adapted to symbol rate leading to fewer cases where tuning fails.
• More robust estimation of lof_offsets to handle incorrect data in NIT
• Correctly identify roll-off values below 20%
• Introduce rf_coupler_id: setting this value to a number different than -1 on a connection signifies that that connection shares a cable with any other connection having the same rf_coupler_id. neumoDVB will then ensure that compatible voltage, polarisation, band, and satellites are selected on those connections.
• Do not allow dish motion when tuning services, only when using positioner. This is a choice that will be turned into an option later.
• In positioner and spectrum dialog, allow separate selection of lnb and tuner (lnb_connection)

 

[deeptho]

Here is an example of a new feature in neumoLNB. neumoDVB now remembers the SNR whenever you tune to a mux and
can display a history plot, which also distinghuishes between LNBs and cards. It can be usefd to monitor rain fade, sun outage,
gradual degradations of signals etc.

The example below sows the same mux using 2 different cards and two different LNBs.
When you tune to the same mux for longer periods of time, these longer tunes will be shown as connected lines.

 

[Llew]

@deeptho

v.1.1 problem. Crashes on starting with the main PC Ubuntu 20.2.

v1.0 working OK

Any clues in the terminal?

Neumodvb v1.1 starts OK with RPi, but attempting to add an LNB in the empty column results in it crashing. Terminal in RPi shown.

 

[deeptho]

Llew,
I think you recompilation was not successful and you run a mixture of both versions.
Try

cd neumodvb/build
rm -fr *
cmake ..
makle -=j `nproc`

 

[Llew]

Llew,
I think you recompilation was not successful and you run a mixture of both versions.
Try

cd neumodvb/build
rm -fr *
cmake ..
makle -=j `nproc`

Tried make -j 'nproc' and make -j8 as usual (my nproc is 2). Not helpful. Needless to say, not with the'=' sign (?)

Reinstalled neumodvb with the new changes, now I can't even get into the program. Asks for LD_PRELOAD, so tried LD_PRELOAD=libgomp.so.1 python3 /home/david/Downloads/neumodvb/gui/neumodvb.py. Still can't get in.

I 'll stay with with version 1.0 until I sort this puzzle out.

 

[deeptho]

LLew,
that is a result of an accidental check-in of some debugging code as I am trying to track down some
crashes due to incorrect use of memory. Sorry for that.
Use the following to use the latest code which has this reverted.

git pull
cd build
rm -fr *
cmake ..
make -j `nproc`

Please also read the documentation: you will need to re-enter LNB details

 

[satesco]

The first test was with the new neumodvb version after I switched to Ubuntu 22.04. After checking and updating some dependencies for the application, the installation went well. So I could start neumoDVB without any problems. Only the new format, I had to be careful because I was used to the old version, where first I/we chose the card and then the lnb; now it's the other way around. So I decided on the lnb but with minor difficulties primarily due to saving the configuration (it's more a matter of the new configuration mode, and of course, of habit).
I found the first bug at 16.0E, low symbol rate muxes(radio programs). When switching to another mux,neumodvb crashed. I repeated the scan, and it hit again. So I made a video of how it happened. Maybe it will help Deeptho to fix this bug.
I did this test with the 6903x card, which, as we know, is very well supported by Deeptho. Maybe this bug is from a low symbol rate or perhaps a wrong setting(?).
libcuda seems to be missing since every time, "cannot load libcuda.so.1" appears after stopping neumodvb. I thought about installing it, but I'm afraid it might ruin the resolution(?).
(I don't know if it matters, but after the upgrade to Ubuntu 22.04, I kept the same 5.13.0.39-generic kernel as Ubuntu 20.04)

 

[Llew]

I can't choose a current or usals position in the LNB list - it doesn't open for me to add anything. Perhaps I've missed something in the documents?


Woken up. Missed Networks

 

[Llew]

Blindscan was going well, then crashed neumodvb. Tried to start the program but it has lost neumodvb.py.

Reinstalled and rebuilt, but gives no neumodvb.py error.

 

[Llew]

Blindscan was going well, then crashed neumodvb. Tried to start the program but it has lost neumodvb.py.

Reinstalled and rebuilt, but gives no neumodvb.py error.

View attachment 147691View attachment 147692

My error. missed Cmake before make -j8. when reinstalling.

As before, blindscan crashes the program half way through. Got a screenshot before it could crash.

 

[satesco]

Hi, Llew,

The setup on the new version is indeed a bit more complicated. I'd say it's a bit cluttered, but only because Deeptho has thought of giving us more possibilities to use his application, especially for those who want to use their reception system more complex.
I tried to configure it for a fixed antenna, and here is what I did (see below).
I hope I haven't strayed from the guidelines in the documentation Deeptho was talking about.

 

[Llew]

Hi, Llew,

The setup on the new version is indeed a bit more complicated. I'd say it's a bit cluttered, but only because Deeptho has thought of giving us more possibilities to use his application, especially for those who want to use their reception system more complex.
I tried to configure it for a fixed antenna, and here is what I did (see below).
I hope I haven't strayed from the guidelines in the documentation Deeptho was talking about.

Yes. it took me a while to get the document information into my thick head. Still more to understand.

Building the fields with the new Networks / Connections into the List is a nice addition.

I hadn't noticed the SDT channel naming before in the Service Information box. Maybe that's new too?

 

[satesco]

I am waiting for Deeptho to respond to issues raised by us. I'm trying to get familiar with the new version of neumoDVB.

 

[deeptho]

The first test was with the new neumodvb version after I switched to Ubuntu 22.04. After checking and updating some dependencies for the application, the installation went well. So I could start neumoDVB without any problems. Only the new format, I had to be careful because I was used to the old version, where first I/we chose the card and then the lnb; now it's the other way around. So I decided on the lnb but with minor difficulties primarily due to saving the configuration (it's more a matter of the new configuration mode, and of course, of habit).
I found the first bug at 16.0E, low symbol rate muxes(radio programs). When switching to another mux,neumodvb crashed. I repeated the scan, and it hit again. So I made a video of how it happened. Maybe it will help Deeptho to fix this bug.

I cannot receive that frequency on which it crashes here.
I will need to test on your computer

Yesterday I fixed some bug that can create some crashes, but it has not yet been put on github.

I did this test with the 6903x card, which, as we know, is very well supported by Deeptho. Maybe this bug is from a low symbol rate or perhaps a wrong setting(?).
libcuda seems to be missing since every time, "cannot load libcuda.so.1" appears after stopping neumodvb. I thought about installing it, but I'm afraid it might ruin the resolution(?).

Don't worry about libcuda. That is unfortunately some warning message encoded in some external library. Just ignore it. It is not a problem.

(I don't know if it matters, but after the upgrade to Ubuntu 22.04, I kept the same 5.13.0.39-generic kernel as Ubuntu 20.04)

Yes, at the moment media_build does not support the 6.1 kernels, but if a kernel works, there is no need to change it.

 

[deeptho]

My error. missed Cmake before make -j8. when reinstalling.

As before, blindscan crashes the program half way through. Got a screenshot before it could crash.

View attachment 147694View attachment 147695

The error message is a new one for me. A bit strange, because 28.2E is one I test regularly. The crash might be related to the bug I fixed yesterday or perhaps not (error message is different). I will upload that code todat.

It might help to get a copy of your databases, mainly the files in ~/neumo/db/chdb.mdb to see if there is something in there that can reproduce the problem.

If you can manage, you could also try and run neumodvb under gdb and then capture a backtrace. It is explained somewhere in the documentation.
Or you can provide me temporary access on your compyter with a teamviewer session or something similar.

 

[deeptho]

Llew,
I just scanned 28.2E with 6909x (not 6903x because that is currently not in my computer). No problems. All works fine.
Could be the patch I made yesterday which is a case of memory corruption. For me that lead to crashes (but not always!) withoyt any
error message, but I found the cause (related to the new list of services that is now shown).

I will release it within the next hour. A simple test is to see if the new code fixes your problem (probably not).