78 replies to this topic

[el bandido]

I have drivers installed for Hauppauge 850, 950, and 955.  All three tuners have the same problem. They load as DVB-C. 
I am building the SF8008 now image with these removed from defconfig.
CONFIG_DVB_AU8522=m
CONFIG_DVB_AU8522_DTV=m
CONFIG_DVB_AU8522_V4L=m

[WanWizard]

I think doing an opkg remove of that kernel driver, and an opkg install of the em28xx kernel driver should be sufficient.

 

They are build as a module, so someone or something most have installed the au8522...

[WanWizard]

Found it:

./recipes-openpli/enigma2-dvb-drivers/enigma2-plugin-drivers-atsc-usb-hauppauge-950q.bb:	kernel-module-au8522 \
./recipes-openpli/enigma2-dvb-drivers/enigma2-plugin-drivers-atsc-usb-hauppauge-950q.bb:	kernel-module-au8522-common \
./recipes-openpli/enigma2-dvb-drivers/enigma2-plugin-drivers-atsc-usb-hauppauge-950q.bb:	kernel-module-au8522-dig \

./recipes-openpli/enigma2-dvb-drivers/enigma2-plugin-drivers-atsc-usb-hauppauge.bb:	kernel-module-au8522 \
./recipes-openpli/enigma2-dvb-drivers/enigma2-plugin-drivers-atsc-usb-hauppauge.bb:	kernel-module-au8522-common \
./recipes-openpli/enigma2-dvb-drivers/enigma2-plugin-drivers-atsc-usb-hauppauge.bb:	kernel-module-au8522-decoder \
./recipes-openpli/enigma2-dvb-drivers/enigma2-plugin-drivers-atsc-usb-hauppauge.bb:	kernel-module-au8522-dig \

 

[el bandido]

Same result with the modded build:

sf8008 login: root
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: Si2166D
Has_Outputs: no
Frontend_Device: 1
I2C_Device: 1
NIM Socket 2:
Type: DVB-C
Name: Auvitek AU8522 QAM/8VSB Frontend
Has_Outputs: no
Frontend_Device: 2
I2C_Device: 2
root@sf8008:~#

The defconfig file is attached.

 defconfig.zip   27.73KB   1 downloads
 

[WanWizard]

How can it load that driver if it isn't build?

[el bandido]

This is what the Octagon shows after installing the image without these:
CONFIG_DVB_AU8522=m
CONFIG_DVB_AU8522_DTV=m
CONFIG_DVB_AU8522_V4L=m
 

root@sf8008:~# opkg list-installed | grep em28
kernel-module-em28xx-4.4.35 - 4.4.35-r1
root@sf8008:~# opkg list-installed | grep AU8522
root@sf8008:~#

So what should I do now?
 

[Pr2]

Your second grep is wrong use -i option to ignore case because you type grep AU8522  while it should be grep au8522 in lower case.

So to mitigate this always use -i option so;    grep -i AU8522

[el bandido]

Thanks for the information!

I have not found a solution for the usb tuner problem.
 

[el bandido]

Installed W_scan to prove the ATSC usb tuner is working in the sf8008.
Normal ATSC frequencies for Atlanta, Ga. were found as shown below:


root@sf8008:~# w_scan -fa -A1 -c US
w_scan -fa -A1 -c US
w_scan version 20170107 (compiled for DVB API 5.11)
using settings for UNITED STATES
ATSC
VSB US/CA, DVB-T TW
scan type TERRCABLE_ATSC, channellist 1
output format vdr-2.0
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C <charset> to override
Info: using DVB adapter auto detection.
        /dev/dvb/adapter0/frontend1 -> "Si2166D" doesnt support TERRCABLE_ATSC -> SEARCH NEXT ONE.
        /dev/dvb/adapter0/frontend2 -> TERRCABLE_ATSC "Auvitek AU8522 QAM/8VSB Frontend": good :-)
        /dev/dvb/adapter1/frontend0 -> TERRCABLE_ATSC "Auvitek AU8522 QAM/8VSB Frontend": good :-)
Using TERRCABLE_ATSC frontend (adapter /dev/dvb/adapter0/frontend2)
_ _ Getting frontend capabilities-_ _-_
Using DVB API 5.10
frontend 'Auvitek AU8522 QAM/8VSB Frontend' supports
INVERSION_AUTO
8VSB
QAM_64
QAM_256
FREQ (54.00MHz ... 858.00MHz)

57000: 8VSB(time: 00:00.011)
63000: 8VSB(time: 00:03.035)
69000: 8VSB(time: 00:06.049)
79000: 8VSB(time: 00:09.072)
85000: 8VSB(time: 00:12.098)
177000: 8VSB(time: 00:15.131)
183000: 8VSB(time: 00:18.173)
189000: 8VSB(time: 00:21.192)
195000: 8VSB(time: 00:24.214)         signal ok:        8VSB     f=195000 kHz (0:0:0)
201000: 8VSB(time: 00:24.734)
207000: 8VSB(time: 00:27.759)
213000: 8VSB(time: 00:30.769)
473000: 8VSB(time: 00:33.799)
479000: 8VSB(time: 00:36.804)
485000: 8VSB(time: 00:39.817)         signal ok:        8VSB     f=485000 kHz (0:0:0)
491000: 8VSB(time: 00:40.341)
497000: 8VSB(time: 00:43.376)         signal ok:        8VSB     f=497000 kHz (0:0:0)
503000: 8VSB(time: 00:43.895)         signal ok:        8VSB     f=503000 kHz (0:0:0)
509000: 8VSB(time: 00:44.425)         signal ok:        8VSB     f=509000 kHz (0:0:0)
515000: 8VSB(time: 00:44.981)         signal ok:        8VSB     f=515000 kHz (0:0:0)
521000: 8VSB(time: 00:45.514)         signal ok:        8VSB     f=521000 kHz (0:0:0)
527000: 8VSB(time: 00:46.047)
533000: 8VSB(time: 00:49.048)
539000: 8VSB(time: 00:52.071)         signal ok:        8VSB     f=539000 kHz (0:0:0)
545000: 8VSB(time: 00:52.599)         signal ok:        8VSB     f=545000 kHz (0:0:0)
551000: 8VSB(time: 00:53.389)         signal ok:        8VSB     f=551000 kHz (0:0:0)
557000: 8VSB(time: 00:53.931)
563000: 8VSB(time: 00:56.932)
569000: 8VSB(time: 00:59.952)         signal ok:        8VSB     f=569000 kHz (0:0:0)
575000: 8VSB(time: 01:00.535)
581000: 8VSB(time: 01:03.582)         signal ok:        8VSB     f=581000 kHz (0:0:0)
587000: 8VSB(time: 01:04.118)
593000: 8VSB(time: 01:07.126)
599000: 8VSB(time: 01:10.147)
605000: 8VSB(time: 01:13.174)         signal ok:        8VSB     f=605000 kHz (0:0:0)
611000: 8VSB(time: 01:13.714)
617000: 8VSB(time: 01:16.765)
623000: 8VSB(time: 01:19.788)
629000: 8VSB(time: 01:22.835)
635000: 8VSB(time: 01:25.864)
641000: 8VSB(time: 01:28.892)
647000: 8VSB(time: 01:31.922)
653000: 8VSB(time: 01:34.962)
659000: 8VSB(time: 01:38.014)
665000: 8VSB(time: 01:41.026) ^C
ERROR: interrupted by SIGINT, dumping partial result...
(time: 01:42.176) dumping lists (0 services)
..
Done, scan time: 01:42.176
root@sf8008:~#

 

[el bandido]

Installed W_scan on the PULSe4K. Here are the tuners W_scan found on the PULSe4K:

Info: using DVB adapter auto detection.
        /dev/dvb/adapter0/frontend0 -> "DVB-S2" doesnt support TERRCABLE_ATSC -> SEARCH NEXT ONE.
        /dev/dvb/adapter0/frontend1 -> "DVB-S2" doesnt support TERRCABLE_ATSC -> SEARCH NEXT ONE.
        /dev/dvb/adapter0/frontend2 -> TERRCABLE_ATSC "Auvitek AU8522 QAM/8VSB Frontend": good :-)
Using TERRCABLE_ATSC frontend (adapter /dev/dvb/adapter0/frontend2)

 

 

Here are the tuners W_scan found for the twin DVB-S2 Octagon sf8008:

Info: using DVB adapter auto detection.
        /dev/dvb/adapter0/frontend1 -> "Si2166D" doesnt support TERRCABLE_ATSC -> SEARCH NEXT ONE.
        /dev/dvb/adapter0/frontend2 -> TERRCABLE_ATSC "Auvitek AU8522 QAM/8VSB Frontend": good :-)
        /dev/dvb/adapter1/frontend0 -> TERRCABLE_ATSC "Auvitek AU8522 QAM/8VSB Frontend": good :-)
Using TERRCABLE_ATSC frontend (adapter /dev/dvb/adapter0/frontend2)

Hopefully this can be fixed.

Edited by el bandido, 9 February 2022 - 06:05.

[Dimitrij]

https://forums.openp...dpost&p=1266012

[el bandido]

Thanks for the thread!
The problem now is I have 2 ATSC tuners listed, but no way to switch between the two:

Info: using DVB adapter auto detection.
        /dev/dvb/adapter0/frontend0 -> "Si2166D" doesnt support TERRCABLE_ATSC -> SEARCH NEXT ONE.
        /dev/dvb/adapter0/frontend1 -> "Si2166D" doesnt support TERRCABLE_ATSC -> SEARCH NEXT ONE.
        /dev/dvb/adapter0/frontend2 -> TERRCABLE_ATSC "Auvitek AU8522 QAM/8VSB Frontend": good :-)
        /dev/dvb/adapter1/frontend0 -> TERRCABLE_ATSC "Auvitek AU8522 QAM/8VSB Frontend": good :-)

How do I use /dev/dvb/adapter0/frontend2 and blacklist  /dev/dvb/adapter1/frontend0?
 

[el bandido]

This exact same problem is getting into other receiver models. It would be nice if the problem could be fixed. The new uClan Ustym 4K S2 OTT X and Octagon SX88 V2 have the exact same ATSC tuner problem as the Octagon SF8008. I don't know who writes the closed source coding for these receivers, but maybe someone here does.
 

It seems there is a vtunerc that is in charge of adding usb devices for these receivers. Our Hauppauge atsc device models 850, 950, and 955Q are ATSC and American DVB-C. The vtunerc loads the usb device first correctly as ATSC. But vtunerc comes back again and loads the Hauppauge ATSC as DVB-C. Then when the receiver starts up, the Hauppauge ATSC tuner is locked to European DVB-C.

 

To prove that everything works and that this is the actual problem, DVB-C modulations were removed and replaced with ATSC modulation types in enigma2 /lib/dvb/frontendparms.cpp. An image built this way will allow ATSC channels to be seen if loaded from a good channel list. Any type of ATSC scanning does not work like this because the receiver thinks the scans are supposed to be DVB-C.

To get the ATSC scanning to work, Linux files au8522_dig.c, lgdt3306a.c, lgdt3305.c located at /drivers/media/dvb-frontends/ need to be edited. Changing .delsys = { SYS_ATSC, SYS_DVBC_ANNEX_B } to .delsys = { SYS_ATSC } in these three files makes the three Hauppauge ATSC tuners they are associated with load as ATSC in the receiver. So it appears that ATSC scanning and channel viewing works normally for the three Hauppauge ATSC tuners if you make these changes to the image build.

The vtunerc still loads the Hauppauge ATSC devices twice after making these Linux changes, so you can't just change the Linux files and not mess with the enigma2 frontendparms.cpp. The files that need to be changed to fix this properly seem to be Closed Source, so hopefully someone will see this that has the means to fix it. I got it to work for me. I would like to see it work for everyone else that uses these types of tuners. Thanks.

 

Edited by el bandido, 19 July 2023 - 21:49.

[Dimitrij]

 

The vtunerc loads the usb device first correctly as ATSC. But vtunerc comes back again and loads the Hauppauge ATSC as DVB-C.

How did you know what is this vtunerc?

Commad/log?

Edited by Dimitrij, 20 July 2023 - 05:34.

[el bandido]

I know the vtunerc loads the Hauppauge twice by watching the rs232 output while the receiver is booting.

[Dimitrij]

I know the vtunerc loads the Hauppauge twice by watching the rs232 output while the receiver is booting.

Can you show the output of such a log?

Maybe we can come up with something.

[el bandido]

Log Attached.
Thanks!

Attached Files

•  sf8008.zip   10.36KB   2 downloads

Edited by el bandido, 20 July 2023 - 13:28.

[Dimitrij]

	Строка 368: vtunerc: registered /dev/misc/vtuner1
	Строка 368: vtunerc: registered /dev/misc/vtuner1
	Строка 369: vtunerc: registered /dev/misc/vtuner2
	Строка 369: vtunerc: registered /dev/misc/vtuner2
	Строка 693: vtunerc0: unknown IOCTL 0x3
	Строка 694: vtunerc0: unknown IOCTL 0x4
	Строка 695: vtunerc0: unknown IOCTL 0x6
	Строка 696: vtunerc0: unknown IOCTL 0x5
	Строка 697: vtunerc0: usb frontend initialized as type=0
	Строка 789: hi_dvb_set_source [dmx: 0, tuner: 0, isvtuner: 0]

	Строка 522: DVB: registering new adapter (au0828)
	Строка 523: DVB: registering adapter 1 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)... it ok?????
	Строка 698: DVB: registering adapter 0 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)... it ok????? 

Maybe

ln -s

adapter 0 frontend 0 --> adapter 1 frontend 0

or

adapter 1 frontend 0  --> adapter 0 frontend 0

 

For info https://forums.openp...-on-openpli-82/

 

https://forums.openp...dpost&p=1468723

Edited by Dimitrij, 20 July 2023 - 14:39.

[el bandido]

Thanks very much!

Here are the results:
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: Si2166D
Has_Outputs: no
Frontend_Device: 1
I2C_Device: 1
NIM Socket 2:
Type: DVB-C
Name: Auvitek AU8522 QAM/8VSB Frontend
Has_Outputs: no
Frontend_Device: 2
I2C_Device: 2
root@sf8008:~# ln -s adapter 0 frontend 0 --> adapter 1 frontend 0
ln: 0: File exists
ln: 0: File exists
ln: 0: File exists
ln: 0: File exists
ln: 0: File exists
root@sf8008:~# ln -s adapter 1 frontend 0  --> adapter 0 frontend 0
ln: 0: File exists
ln: 0: File exists
ln: 0: File exists
ln: 0: File exists
ln: 0: File exists
ln: 0: File exists
root@sf8008:~#

So that doesn't seem to help. What next?
 

[Dimitrij]

What version of openpli do you have?

 

It is necessary to choose experimentally the necessary numbers, as here

init 4
mv /dev/dvb/ and etc code...

https://forums.openp...dpost&p=1468723
 

Edited by Dimitrij, 20 July 2023 - 16:49.