46 replies to this topic

[frankviana]

Hi. I don't know why the Octagon sf8008 install both ISDB-T/DVB-T usb adapters as DVB-S2x, while Edision osmini4k show correctly (DVB-T). OpenPli and OpenATV.

 

osmini4k:

 

 Osmini4k.jpg   75.04KB   1 downloads

 

 Osmini4k.info.jpg   108.02KB   1 downloads

 

 

sf8008

 

 sf8008.jpg   79.61KB   1 downloads

 

 sf8008.info.jpg   117.63KB   1 downloads

 

 

Thx

Edited by frankviana, 14 August 2021 - 14:54.

[frankviana]

Adapter 0 (S2166D - S2x)

root@sf8008:
dvbsnoop -s feinfo -pd 9 -frontend /dev/dvb/adapter0/frontend0


dvbsnoop V1.4.56 -- https://github.com/OpenVisionE2/dvbsnoop
   DEMUX : /dev/dvb/adapter0/demux0
   DVR   : /dev/dvb/adapter0/dvr0
   FRONTEND: /dev/dvb/adapter0/frontend0

---------------------------------------------------------
FrontEnd Info...
---------------------------------------------------------

Device: /dev/dvb/adapter0/frontend0

Basic capabilities:
    Name: "Si2166D"
    Frontend-type:       QPSK (DVB-S)
    Frequency (min):     950.000 MHz
    Frequency (max):     2150.000 MHz
    Frequency stepsiz:   0.125 MHz
    Frequency tolerance: 0.000 MHz
    Symbol rate (min):     0.100000 MSym/s
    Symbol rate (max):     80.000000 MSym/s
    Symbol rate tolerance: 500 ppm
    Notifier delay: 0 ms
    Frontend capabilities:
        auto inversion
        FEC 1/2
        FEC 2/3
        FEC 3/4
        FEC 4/5
        FEC 5/6
        FEC 6/7
        FEC 7/8
        FEC 8/9
        FEC AUTO
        QPSK
        auto guard interval
        auto hierarchy
        FE_CAN_2G_MODULATION
        FE_CAN_RECOVER

Current parameters:
    Frequency:  0.000 MHz
    Inversion:  OFF
    Symbol rate:  0.000000 MSym/s
    FEC:  FEC AUTO

Adapter 1 ((MyGica s270) Siano Rio)

root@sf8008:
dvbsnoop -s feinfo -pd 9 -frontend /dev/dvb/adapter1/frontend0

dvbsnoop V1.4.56 -- https://github.com/OpenVisionE2/dvbsnoop
   DEMUX : /dev/dvb/adapter0/demux0
   DVR   : /dev/dvb/adapter0/dvr0
   FRONTEND: /dev/dvb/adapter1/frontend0

---------------------------------------------------------
FrontEnd Info...
---------------------------------------------------------

Device: /dev/dvb/adapter1/frontend0

Basic capabilities:
    Name: "Siano Mobile Digital MDTV Receiver"
    Frontend-type:       OFDM (DVB-T)
    Frequency (min):     44250.000 kHz
    Frequency (max):     867250.000 kHz
    Frequency stepsiz:   250.000 kHz
    Frequency tolerance: 0.000 kHz
    Symbol rate (min):     0.000000 MSym/s
    Symbol rate (max):     0.000000 MSym/s
    Symbol rate tolerance: 0 ppm
    Notifier delay: 0 ms
    Frontend capabilities:
        auto inversion
        FEC 1/2
        FEC 2/3
        FEC 3/4
        FEC 5/6
        FEC 7/8
        FEC AUTO
        QPSK
        QAM 16
        QAM 64
        QAM AUTO
        auto transmission mode
        auto guard interval
        auto hierarchy
        FE_CAN_RECOVER

Current parameters:
    Frequency:  0.000 kHz
    Inversion:  OFF
    Bandwidth:  AUTO
    Stream code rate (hi prio):  FEC AUTO
    Stream code rate (lo prio):  FEC AUTO
    Modulation:  QAM AUTO
    Transmission mode:  auto
    Guard interval:  auto
    Hierarchy:  auto

Adapter 2 (Prolink PixelView PlayTV USB SBTVD (Full Seg)

root@sf8008:
dvbsnoop -s feinfo -pd 9 -frontend /dev/dvb/adapter2/frontend0

dvbsnoop V1.4.56 -- https://github.com/OpenVisionE2/dvbsnoop
   DEMUX : /dev/dvb/adapter0/demux0
   DVR   : /dev/dvb/adapter0/dvr0
   FRONTEND: /dev/dvb/adapter2/frontend0

---------------------------------------------------------
FrontEnd Info...
---------------------------------------------------------

Device: /dev/dvb/adapter2/frontend0

Basic capabilities:
    Name: "DiBcom 8000 ISDB-T"
    Frontend-type:       OFDM (DVB-T)
    Frequency (min):     45000.000 kHz
    Frequency (max):     860000.000 kHz
    Frequency stepsiz:   62.500 kHz
    Frequency tolerance: 0.000 kHz
    Symbol rate (min):     0.000000 MSym/s
    Symbol rate (max):     0.000000 MSym/s
    Symbol rate tolerance: 0 ppm
    Notifier delay: 0 ms
    Frontend capabilities:
        auto inversion
        FEC 1/2
        FEC 2/3
        FEC 3/4
        FEC 5/6
        FEC 7/8
        FEC AUTO
        QPSK
        QAM 16
        QAM 64
        QAM AUTO
        auto transmission mode
        auto guard interval
        auto hierarchy
        FE_CAN_RECOVER

Current parameters:
    Frequency:  0.000 kHz
    Inversion:  OFF
    Bandwidth:  6 MHz
    Stream code rate (hi prio):  FEC AUTO
    Stream code rate (lo prio):  FEC AUTO
    Modulation:  QAM AUTO
    Transmission mode:  auto
    Guard interval:  auto
    Hierarchy:  auto

root@sf8008:

[Dimitrij]

please answer

cat /proc/bus/nim_sockets

 

[frankviana]

root@sf8008:
cat /proc/bus/nim_sockets


NIM Socket 0:
Type: DVB-S2X
Name: Si2166D
Has_Outputs: no
Frontend_Device: 0
I2C_Device: 0
NIM Socket 1:
Type: DVB-S2X
Name: Siano Mobile Digital MDTV Receiver
Has_Outputs: no
Frontend_Device: 1
I2C_Device: 1
NIM Socket 2:
Type: DVB-S2X
Name: DiBcom 8000 ISDB-T
Has_Outputs: no
Frontend_Device: 2
I2C_Device: 2
root@sf8008:

[Dimitrij]

I do not know why it is so. It looks like incorrect drivers.

[frankviana]

Strange.. same DEMUX and DVR for 3 adapters.

[frankviana]

I do not know why it is so. It looks like incorrect drivers.

Maybe report to Octagon?

[ultra_signal]

 

the same is happening with uclan

 

openpli 8.0-release ustym4kpro

 

ustym4kpro login: root

root@ustym4kpro:~#

root@ustym4kpro:~# cat /proc/bus/nim_sockets

NIM Socket 0:

Type: DVB-S2X

Name: Si2166D

Has_Outputs: no

Frontend_Device: 0

I2C_Device: 0

NIM Socket 1:

Type: DVB-S2X

Name: Si2166D

Has_Outputs: no

Frontend_Device: 1

I2C_Device: 1

NIM Socket 2:

Type: DVB-S2X

Name: Siano Mobile Digital MDTV Receiver

Has_Outputs: no

Frontend_Device: 2

I2C_Device: 2

root@ustym4kpro:~#

[WanWizard]

What is the output on the Edision?

[ultra_signal]

What is the output on the Edision?

 

Edition is correct. Working perfectly.

 

openpli 8.0-release osninopro

 

osninopro login: root

root@osninopro:~# cat /proc/bus/nim_sockets

NIM Socket 0:

        Type: DVB-S2X

        Name: DVB-S2X (External)

        I2C_Device: 1

        Has_Outputs: no

        Frontend_Device: 0

NIM Socket 1:

        Type: DVB-T2

        Name: DVB-T2/C (External)

        I2C_Device: 255

        Has_Outputs: no

        Frontend_Device: 1

        Mode 0: DVB-T

        Mode 1: DVB-C

NIM Socket 2:

        Type: DVB-T

        Name: MDTV Receiver

        I2C_Device: 255

        Has_Outputs: no

        Frontend_Device: 2

root@osninopro:~#

[frankviana]

What is the output on the Edision?

root@osmini4k:cat /proc/bus/nim_sockets

NIM Socket 0:
        Type: DVB-S2X
        Name: Availink AVL6261
        Frontend_Device: 0
        I2C_Device: 2
        Has_Outputs: no
NIM Socket 1:
        Type: DVB-T
        Name: MDTV Receiver
        Frontend_Device: 1
        I2C_Device: 255
        Has_Outputs: no
NIM Socket 2:
        Type: DVB-T
        Name: STK807X
        Frontend_Device: 2
        I2C_Device: 255
        Has_Outputs: no
root@osmini4k:
-------------------- < Script > ----------------------------
df -m > /tmp/meminfo.dcc; echo ">>> DONE <<<";

>>> DONE <<<
root@osmini4k:

Edited by frankviana, 14 August 2021 - 16:40.

[frankviana]

 

What is the output on the Edision?

root@osmini4k:cat /proc/bus/nim_sockets

NIM Socket 0:
        Type: DVB-S2X
        Name: Availink AVL6261
        Frontend_Device: 0
        I2C_Device: 2
        Has_Outputs: no
NIM Socket 1:
        Type: DVB-T
        Name: MDTV Receiver
        Frontend_Device: 1
        I2C_Device: 255
        Has_Outputs: no
NIM Socket 2:
        Type: DVB-T
        Name: STK807X
        Frontend_Device: 2
        I2C_Device: 255
        Has_Outputs: no
root@osmini4k:
-------------------- < Script > ----------------------------
df -m > /tmp/meminfo.dcc; echo ">>> DONE <<<";

>>> DONE <<<
root@osmini4k:

The same 3 adapters

[WanWizard]

I wonder why is the names are different on both boxes, given they are the same device?

 

Can you post the output of "lsmod" from both boxes? I wonder if there is a driver difference, related to the difference in kernel versions (edision is much newer).

[frankviana]

I wonder why is the names are different on both boxes, given they are the same device?

 

Can you post the output of "lsmod" from both boxes? I wonder if there is a driver difference, related to the difference in kernel versions (edision is much newer).

Yes.. very stange different names.

 

I see this same name DiBcom 8000 ISDB-T from my Ubuntu.

[frankviana]

osmini4k:

root@osmini4k:lsmod

Module                  Size  Used by
dib8000                57344  1
smsdvb                 20480  2
dvb_usb_dib0700       106496  2
dib0070                20480  2 dvb_usb_dib0700
dib7000m               24576  1 dvb_usb_dib0700
dib0090                32768  1 dvb_usb_dib0700
smsusb                 16384  0
dvb_usb                24576  1 dvb_usb_dib0700
smsmdtv                40960  2 smsdvb,smsusb
dib3000mc              20480  1 dvb_usb_dib0700
dibx000_common         16384  3 dib7000m,dib8000,dib3000mc
si2183                643072  0
brcmstb_osmini4k     5017600  8
avl6261                98304  1 brcmstb_osmini4k
avl6862               360448  1 brcmstb_osmini4k
ci                     28672  1 brcmstb_osmini4k
root@osmini4k:

sf8008

root@sf8008:lsmod

Module                  Size  Used by
dib8000                46991  1
dvb_usb_dib0700        95820  1
dib9000                27670  1 dvb_usb_dib0700
dib0070                 7723  2 dvb_usb_dib0700
dib7000m               14050  1 dvb_usb_dib0700
dib0090                24464  1 dvb_usb_dib0700
dib3000mc              10636  1 dvb_usb_dib0700
dibx000_common          6631  5 dib8000,dib9000,dvb_usb_dib0700,dib3000mc,dib7000m
smsdvb                 12313  1
smsusb                 10203  0
smsmdtv                42332  2 smsdvb,smsusb
xfs                   832715  0
libcrc32c               1127  1 xfs
tntfs                 561895  0
hisi_encoder            4121  0
hisi_keys               2792  0
hisi_sci                9592  0
hisi_ir                 4294  0
libahci_platform        6390  0
libahci                23341  1 libahci_platform
hi_pmoc                73918  1
hi_vi                  71057  0
hi_sci                 56990  1 hisi_sci
hi_aenc                 7367  0
hi_venc               229263  1
hi_advca              228114  1
hi_png                 24106  0
hi_jpge                22436  0
hi_jpeg                16843  0
hi_dbe                  5734  0
mali                  284125  0
hi_fb                 197817  3
hi_dvb                928477  10
vtunerc                25550  5 hi_dvb
oled                    6203  2 hi_dvb
hi_keyled              79819  3 oled,hisi_keys,hi_dvb
hi_tuner             
 517464  0
hi_mce                  4402  0
hi_pvr                  4284  0
hi_sync                66760  1
hi_aiao               381932  4
hi_adsp               220281  0
hi_vdec              1251988  1
hi_vpss               400316  0
hi_vfmw              1827881  0
hi_adec                 9236  0
hi_demux              417073  2 hi_dvb
hi_otp                 24944  2 hi_pmoc
hi_tde                112944  0
hi_i2c                 19734  2 hi_tuner,hi_dvb
hi_gpio_i2c            14794  3 hi_tuner,hi_i2c,hi_dvb
hi_gpio                18564  1 hi_dvb
hi_vou               1245286  2
hi_hdmicec              5071  2 hi_dvb
hi_hdmi               900300  3 hi_hdmicec,hi_dvb
hi_cipher             264125  0
hi_pq                1656354  3 hi_vou,hi_vpss
hi_pdm                 25264  0
hi_common              94145  39 mali,hi_fb,hi_pq,hi_vi,hi_cipher,hi_keyled,hi_advca,hi_demux,hi_tuner,hi_i2c,hi_dvb,hi_mce,hi_pdm,hi_otp,hi_png,hi_pvr,hi_sci,hi_tde,hi_vou,hi_adec,hi_adsp,hi_aenc,hi_aiao,hi_hdmi,hi_gpio,hi_jpeg,hi_jpge,hi_pmoc,hi_sync,hi_vdec,hi_venc,hi_vfmw,hi_vpss,hisi_ir,hi_gpio_i2c
hi_mmz                 45984  22 hi_fb,hi_pq,hi_vi,hi_cipher,hi_common,hi_demux,hi_dvb,hi_png,hi_tde,hi_vou,hi_adec,hi_adsp,hi_aenc,hi_aiao,hi_jpeg,hi_jpge,hi_sync,hi_vdec,hi_venc,hi_vfmw,hi_vpss
hi_media                8732  24 hi_common,hi_mmz,hi_png,hi_tde,hi_jpeg,hi_jpge
root@sf8008:
clear

root@sf8008:

 

[frankviana]

 

I wonder why is the names are different on both boxes, given they are the same device?

 

Can you post the output of "lsmod" from both boxes? I wonder if there is a driver difference, related to the difference in kernel versions (edision is much newer).

Yes.. very stange different names.

 

I see this same name DiBcom 8000 ISDB-T from my Ubuntu.

 

Vuzero4k and vuzero appear same Edision

 

All 3 Broadcom and same name STK807X for Pixelview

[frankviana]

I also don't know why only the OE-Alliance has no problems with tuning after lock ISDB-T/DVB-T signal for IDSB-T frequencies. OpenPli/SatdreamGR find the signal, but appear tuner unavailable (gray channels).

 

Posted here, 2 years ago:

 

https://forums.openp...ndpost&p=999913

[WanWizard]

https://cateee.net/l...SB_DIB0700.html

 

In all cases it is a kernel supported driver. Initially I tought it could be a difference in kernel version, but the vuzero runs an old 3.x kernel, so if that works fine, it can't be it.

 

Firmware correctly installed on the sf8008?

[frankviana]

https://cateee.net/l...SB_DIB0700.html

 

In all cases it is a kernel supported driver. Initially I tought it could be a difference in kernel version, but the vuzero runs an old 3.x kernel, so if that works fine, it can't be it.

 

Firmware correctly installed on the sf8008?

yes.. same firmware section downoads (dib0700 and siano)

[WanWizard]

Which driver do you install on OE-A to make it work?