neumoDVB

[frankviana]

Strange... compiled before and now, appear this:

frank@frank-X99:~/neumodvb/build$ sudo apt install -y libboost-all-dev libgtk-3-0 libgtk-3-dev curl libcurl4-openssl-dev libwxgtk-media3.0-gtk3-dev \
gettext libexif-dev libavcodec-dev libavformat-dev libavutil-dev libswscale-dev python3-jinja2 python3-pip clang-format \
python3-sip-dev libconfig-dev libconfig++-dev libdvbcsa-dev libmpv-dev freeglut3-dev python-wxgtk3.0 python3-wxgtk-media4.0 \
python3-wxgtk-webview4.0 python3-wxgtk4.0 python3-scipy clang lsb-core lsb-release python3-regex fmt fmt-dev
Lendo listas de pacotes... Pronto
Construindo árvore de dependências... Pronto
Lendo informação de estado... Pronto       
E: Impossível encontrar o pacote python-wxgtk3.0
E: Couldn't find any package by glob 'python-wxgtk3.0'
E: Impossível encontrar o pacote fmt
E: Impossível encontrar o pacote fmt-dev

And...

frank@frank-X99:~/neumodvb/build$ sudo cmake ..
-- The CXX compiler identification is Clang 14.0.6
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - failed
-- Check for working CXX compiler: /usr/bin/clang++
-- Check for working CXX compiler: /usr/bin/clang++ - broken
CMake Error at /usr/local/share/cmake-3.20/Modules/CMakeTestCXXCompiler.cmake:59 (message):
  The C++ compiler

    "/usr/bin/clang++"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: /home/frank/neumodvb/build/CMakeFiles/CMakeTmp
    
    Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_16245/fast && /usr/bin/gmake  -f CMakeFiles/cmTC_16245.dir/build.make CMakeFiles/cmTC_16245.dir/build
    gmake[1]: Entrando no diretório '/home/frank/neumodvb/build/CMakeFiles/CMakeTmp'
    Building CXX object CMakeFiles/cmTC_16245.dir/testCXXCompiler.cxx.o
    /usr/bin/clang++    -MD -MT CMakeFiles/cmTC_16245.dir/testCXXCompiler.cxx.o -MF CMakeFiles/cmTC_16245.dir/testCXXCompiler.cxx.o.d -o CMakeFiles/cmTC_16245.dir/testCXXCompiler.cxx.o -c /home/frank/neumodvb/build/CMakeFiles/CMakeTmp/testCXXCompiler.cxx
    Linking CXX executable cmTC_16245
    /usr/local/bin/cmake -E cmake_link_script CMakeFiles/cmTC_16245.dir/link.txt --verbose=1
    /usr/bin/clang++  -Wl,-z,defs -Wl,--no-undefined -fuse-ld=gold  CMakeFiles/cmTC_16245.dir/testCXXCompiler.cxx.o -o cmTC_16245
    /usr/bin/ld.gold: erro: não pôde encontrar -lstdc++
    clang: error: linker command failed with exit code 1 (use -v to see invocation)
    gmake[1]: *** [CMakeFiles/cmTC_16245.dir/build.make:100: cmTC_16245] Erro 1
    gmake[1]: Saindo do diretório '/home/frank/neumodvb/build/CMakeFiles/CMakeTmp'
    gmake: *** [Makefile:127: cmTC_16245/fast] Erro 2
    
    

 

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:11 (project)


-- Configuring incomplete, errors occurred!
See also "/home/frank/neumodvb/build/CMakeFiles/CMakeOutput.log".
See also "/home/frank/neumodvb/build/CMakeFiles/CMakeError.log".

Thx

 

[deeptho]

This is not really a problem with neumoDVB: even the installed compiler does not work...

 

[frankviana]

No way to install?

Do you know something about this packages: python-wxgtk3.0, fmt and fmt-dev?

Thx

 

[deeptho]

No way to install?

Do you know something about this packages: python-wxgtk3.0, fmt and fmt-dev?

Thx

Of course it is possible to install on a recent enough OS. Perhaps you are not using a recent enough OS, or following outdated instructions?

 

[frankviana]

Sorry for delay...

The problem is the old SO




Thx.

 

[frankviana]

Ready for some tests:

 

[frankviana]

This pictures I did before reboot...

After install blindscan (linux_media_blindscan) and reboot, I have only resolution 640x480 (4:3)

I'm using RX5500XT and no way to change to 1080 resolution. The software amdgpu work until Ubuntu 22.04.4

frank@frank-X99:~$ inxi -G

Graphics:
Device-1: AMD Navi 14 [Radeon RX 5500/5500M / Pro 5500M] driver: N/A
Display: wayland server: X.Org v: 23.2.6 with: Xwayland v: 23.2.6 compositor: gnome-shell
v: 46.0 driver: dri: swrast gpu: N/A resolution: 640x480~59Hz
API: EGL v: 1.5 drivers: kms_swrast,swrast platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.5 vendor: mesa v: 24.0.5-1ubuntu1
renderer: llvmpipe (LLVM 17.0.6 256 bits)

Thx

 

[frankviana]

No way to edit previous post, then...

After rebuild grub using live cd, all OK now.

sudo mount "PARTITION" /mnt
sudo grub-install --root-directory=/mnt /dev/"PARTITION"

Edit: After some reboots, setting BIOS appear 640x480 (480p) using UEFI mode and 1920x1080 (1080p) using Legacy mode.

Thx

 

[deeptho]

No way to edit previous post, then...

After rebuild grub using live cd, all OK now.

sudo mount "PARTITION" /mnt
sudo grub-install --root-directory=/mnt /dev/"PARTITION"

Edit: After some reboots, setting BIOS appear 640x480 (480p) using UEFI mode and 1920x1080 (1080p) using Legacy mode.

Thx

Installing blindscan should not affect your graphics driver. So probably you erased something.

Also, you should not use wayland, because that will cause some other problems.

 

[frankviana]

I did a clean installation and only followed the github steps: first neumodvb and after blindscan, nothing more ...

This wayland configuration is standard ... I didn't install it manually either.

Thx

 

[Llew]

I did a clean installation and only followed the github steps: first neumodvb and after blindscan, nothing more ...

This wayland configuration is standard ... I didn't install it manually either.

Thx

Using Cinnamon in Debian as my desktop, I have the choice when logging in to change from wayland to xorg (preferred for neumodvb).
Clicking on to the cogwheel at bottom right of the login screen allows the change.
Possibly the same with Ubuntu.

 

[RyLe]

Hi

In Fedora 40, moving to kernel 6.4.9-200, there is a new error during compilation:

/home/ryle/blindscan_kernel/media_build/v4l/ccs-core.c:668:21: error: too many arguments to function 'pm_runtime_get_if_active' 668 | pm_status = pm_runtime_get_if_active(&client->dev, true);

It seems that the new kernel version has once again changed the number of parameters of some functions.

 

[deeptho]

Hi

In Fedora 40, moving to kernel 6.4.9-200, there is a new error during compilation:

/home/ryle/blindscan_kernel/media_build/v4l/ccs-core.c:668:21: error: too many arguments to function 'pm_runtime_get_if_active' 668 | pm_status = pm_runtime_get_if_active(&client->dev, true);

It seems that the new kernel version has once again changed the number of parameters of some functions.

RyLe
Unlikely as compiling works for version 6.6.2 on fedora39
Maybe you should upgrade your kernel instead?

 

[RyLe]

Hi

Sorry, I made a typo, it's kernel 6.9.4-200, not 6.4.9-200 like I wrote earlier.

 

[RobVK8FOES]

Greetings, this is my first post on this forum, so thanks for having me!

I recently had some luck in compiling NeumoDVB in DragonOS FocalX R35 (built upon Lubuntu 22.04). There were no errors in the build process.

However, when trying to launch the application, the GUI appears briefly and then crashes with the following error:

username@drgnos-fclx-r35:~/neumodvb/gui$ ./neumodvb.py
loading options from /home/username/neumodvb/config/neumodvb.cfg
loading options from /etc/neumodvb/neumodvb.cfg

(neumodvb.py:56481): Gtk-CRITICAL **: 13:44:26.717: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed

(neumodvb.py:56481): Gtk-WARNING **: 13:44:26.990: Negative content width -6 (allocation 2, extents 4x4) while allocating gadget (node entry, owner GtkEntry)

(neumodvb.py:56481): Gtk-WARNING **: 13:44:26.990: Negative content height -7 (allocation 1, extents 4x4) while allocating gadget (node entry, owner GtkEntry)

(neumodvb.py:56481): Gtk-WARNING **: 13:44:26.990: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node entry, owner GtkEntry)

(neumodvb.py:56481): Gtk-WARNING **: 13:44:26.990: Negative content height -7 (allocation 1, extents 4x4) while allocating gadget (node entry, owner GtkEntry)

(neumodvb.py:56481): Gtk-WARNING **: 13:44:27.006: Negative content height -7 (allocation 1, extents 4x4) while allocating gadget (node entry, owner GtkEntry)

(neumodvb.py:56481): Gtk-WARNING **: 13:44:27.006: Negative content height -7 (allocation 1, extents 4x4) while allocating gadget (node entry, owner GtkEntry)

(neumodvb.py:56481): Gdk-ERROR **: 13:44:27.033: The program 'neumodvb.py' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
  (Details: serial 836 error_code 10 request_code 152 (GLX) minor_code 26)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)
username@drgnos-fclx-r35:~/neumodvb/gui$

Does anybody know the magic command to rectify this issue? Thanks very much in advance!

 

[deeptho]

Greetings, this is my first post on this forum, so thanks for having me!

I recently had some luck in compiling NeumoDVB in DragonOS FocalX R35 (built upon Lubuntu 22.04). There were no errors in the build process.

However, when trying to launch the application, the GUI appears briefly and then crashes with the following error:

username@drgnos-fclx-r35:~/neumodvb/gui$ ./neumodvb.py
loading options from /home/username/neumodvb/config/neumodvb.cfg
loading options from /etc/neumodvb/neumodvb.cfg

(neumodvb.py:56481): Gtk-CRITICAL **: 13:44:26.717: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed

(neumodvb.py:56481): Gtk-WARNING **: 13:44:26.990: Negative content width -6 (allocation 2, extents 4x4) while allocating gadget (node entry, owner GtkEntry)

(neumodvb.py:56481): Gtk-WARNING **: 13:44:26.990: Negative content height -7 (allocation 1, extents 4x4) while allocating gadget (node entry, owner GtkEntry)

(neumodvb.py:56481): Gtk-WARNING **: 13:44:26.990: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node entry, owner GtkEntry)

(neumodvb.py:56481): Gtk-WARNING **: 13:44:26.990: Negative content height -7 (allocation 1, extents 4x4) while allocating gadget (node entry, owner GtkEntry)

(neumodvb.py:56481): Gtk-WARNING **: 13:44:27.006: Negative content height -7 (allocation 1, extents 4x4) while allocating gadget (node entry, owner GtkEntry)

(neumodvb.py:56481): Gtk-WARNING **: 13:44:27.006: Negative content height -7 (allocation 1, extents 4x4) while allocating gadget (node entry, owner GtkEntry)

(neumodvb.py:56481): Gdk-ERROR **: 13:44:27.033: The program 'neumodvb.py' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
  (Details: serial 836 error_code 10 request_code 152 (GLX) minor_code 26)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)
username@drgnos-fclx-r35:~/neumodvb/gui$

Does anybody know the magic command to rectify this issue? Thanks very much in advance!

If you want help, you will need to provide a log file (/tmp/neumo.log).

Also: This is what is written in the installation instructions:

Ubuntu 22.04.1 LTS​

The latest neumoDVB version may not work anymore because of an outdated libstdc++. You may need to upgrade Ubuntu or install an older version of neumoDVB.

 

[deeptho]

Lately I have been working on improvving the drivers for stid135, mainly to make it easier
to support tbs6916, which has 4 RF inputs, 8 tuners, and 16 demods. This requires solving
all kinds of small problems such as preventing two stid135 chips connected to the same cable
from causing conflicts, such as one selecting a high band and the other a low band. It also required
making small changes to neumoDVB.

The new drivers (not yet released) also solve some other "race" problems which could affect tbs6909x and tbs603x as well. These races can cause some muxes to not be scanned properly
after switching band/pol because demods do not wait for a tuner to be properly configured (
by which I mean: sending diseqc, setting tone...)

Most of the bugs seem to be gone. Today I scanned many satellites without problem,
but I know one more bug is left.

The card runs fast and well. Here is an example of a blindscan of 52E, which takes
about 4 minutes, including getting the spectrum (which is not included in the 3min 24s).
When the card fails to scan muxes, usually there seems to be a good reason for it.



The new drivers also expose all kinds of useful information in /sys. For example, the following
2 commands show the temperature of the two stid135 chips, while in use.

$cat /sys/module/stid135/card0/chip0/temperature
37
$cat /sys/module/stid135/card0/chip1/temperature
36

The value is rather low as the card has a fan (which is also a downside: there is some noise)

And this shows what is happening during a scan: 16 demods are using the same '
input (cable "in0"), which is currently on 18BVolt and no tone

$cat /sys/module/stid135/card0/state
card_no = 0 dev =00000000c01c2d8f
use_count = 2
chips: 00000000408871bf 000000006af36aca
rf_in[0]: use_count=16 owner=13559 controller=0 voltage=18V tone=off
rf_in[1]: use_count=0 owner=-1 controller=-1 voltage=off tone=off
rf_in[2]: use_count=0 owner=-1 controller=-1 voltage=off tone=off
rf_in[3]: use_count=0 owner=-1 controller=-1 voltage=off tone=off

And using a script, we can inspect the registers of the chips fo debugging. In this
case, the first demod on the second chip has set a 22kHz tone on the cable

stidmap.py|grep REG_RC8CODEW_DVBSX_DISEQC_DISTXCFG
0.0: REG_RC8CODEW_DVBSX_DISEQC_DISTXCFG(2)                        = 0x00000002
0.0: REG_RC8CODEW_DVBSX_DISEQC_DISTXCFG(3)                        = 0x00000002
0.0: REG_RC8CODEW_DVBSX_DISEQC_DISTXCFG(4)                        = 0x00000002
0.0: REG_RC8CODEW_DVBSX_DISEQC_DISTXCFG(1)                        = 0x00000000
0.1: REG_RC8CODEW_DVBSX_DISEQC_DISTXCFG(2)                        = 0x00000002
0.1: REG_RC8CODEW_DVBSX_DISEQC_DISTXCFG(3)                        = 0x00000002
0.1: REG_RC8CODEW_DVBSX_DISEQC_DISTXCFG(4)                        = 0x00000002
0.1: REG_RC8CODEW_DVBSX_DISEQC_DISTXCFG(1)                        = 0x00000002

What the script does is read a binary file /sys/module/stid135/card0/chip0/registers/stid135
and then interpret the registers. It is also possible to write to them, but that is for hackers...

All of the above also works on tbs6909x and tbs6903x.

During the testing, the power supply of my PC died. I also discovered, using an oscillosope,
that some of my diseqc switches behaved very badly and caused voltage drops of several volts for
many milliseconds. This could also be related to my power supply.

I also found out that the drivers by TBS program the chip to output 21KHz instead of 22kHz and this caused diseqc switching to fail from time to time on some switches. I still need to check if this problem is also present on tbs6909X. That requires me to swap cards and there is some work involved.

 

[deeptho]

I have just released neumoDVB-1.7.
To use this, you should also install the latest neumoDVB drivers

Changes in version neumodvb-1.7​

• Support cards with multiple stid135 chips such as tbs6916.
• Improved handling of races when tuning multiple muxes on the same tuner in parallel. This can lead to some threads tuning before diseqc programming is finished, resulting in failed tunes. A typical effect is some muxes failing to scan.
• Bug: When clicking on mux, incorrect question to save network.
• Bug: incorrect format string in OSD.
• Remove unneeded or incorrect assertions.
• Experimental change: when positioner dialog is blind tuning, allow services to reuse adapter.
• Bug: DVBC and DVBT scan not starting.
• Make lnb connection list display more robust against errors in database.
• Create scripts for easier creation of .deb and .rpm packages.
• Bug: Incorrect priority handling when selecting LNBs and other resources.
• Bug: ac3 flag overwritten in pmt parsing (Anixe HD on 19.2E), resulting in no playback
• Bug: incorrect usage of future resulting in incorrect mux count during scanning.
• Bug: positioner_dialog considers some valid NITs invalid.
• Increased font size of the services list on the positioner dialog screen.
• Improved installation instructions for Ubuntu
• Frontend list now also shows config_id.
• Bug: scanning code ignores some valid information provided by driver.

 

[RyLe]

Hi

Thank you for this update, the blindscan driver now builds nicely on an up to date Fedora40 with the latest kernel (6.9.9-200.fc40.x86_64).

I saw that the media_build repository became media_build_old and that there is a newer repository: neumo_media_build.

In the build instructions of neumo_media_build there's a tiny error:
cd media_build must be changed to neumo_media_build

 

[deeptho]

Hi

Thank you for this update, the blindscan driver now builds nicely on an up to date Fedora40 with the latest kernel (6.9.9-200.fc40.x86_64).

I saw that the media_build repository became media_build_old and that there is a newer repository: neumo_media_build.

In the build instructions of neumo_media_build there's a tiny error:
cd media_build must be changed to neumo_media_build

Thanks. I will update that. The reason for a new repo is that it was easier to start from the tbs version