106 replies to this topic

[ColinB]

Thanks. Actually if I insert the Usb dongle my box doesn't recognize the interface.. No dvb-t/t2 adapter recognized (if I insert my old RTL2832U adapter everything is ok)..
The firmware you posted is for DVB-t2? Basically what I should do? Copy firmware? And for kernel .ko? and anything more?

Thanks again

 

It wont. You will need a kernel 4.10+

 

Then you have to install the drivers manualy.

 

Then you will need to swp front ends if you want T2. The script is in this thread.

 

Nothing has changed except the kernel. So all driver are in this post.

 

Once setup it is a good enough backup tuner for T2.

[orator89]

 

Thanks. Actually if I insert the Usb dongle my box doesn't recognize the interface.. No dvb-t/t2 adapter recognized (if I insert my old RTL2832U adapter everything is ok)..
The firmware you posted is for DVB-t2? Basically what I should do? Copy firmware? And for kernel .ko? and anything more?

Thanks again

 

It wont. You will need a kernel 4.10+

 

Then you have to install the drivers manualy.

 

Then you will need to swp front ends if you want T2. The script is in this thread.

 

Nothing has changed except the kernel. So all driver are in this post.

 

Once setup it is a good enough backup tuner for T2.

 

 

 

Thanks for the reply, Colin

SO basically if I want for thi moment only make working only the DVB-T part and not DVB-t2, i can't with kernel 3.6.0? I understood correctly? I need kernel 4.10+ also for the only dvb-t part? Thanks

[giorgijag]

I bought astrometa DVB-T2 usb tuner. On windows 10 everything working perfect.

I want to use in Ubuntu, but seems there is some problem, but don't know what:

Please help me figure out what is the problem.

W_scan :

~$ w_scan -ft -c GE
w_scan -ft -c GE
w_scan version 20170107 (compiled for DVB API 5.10)
using settings for GEORGIA
Country identifier GE not defined. Using defaults.
scan type TERRESTRIAL, channellist 4
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.
main:4007: FATAL: ***** NO USEABLE TERRESTRIAL CARD FOUND. *****
Please check wether dvb driver is loaded and
verify that no dvb application (i.e. vdr) is running.

$ lsmod | grep dvb

dvb_usb_rtl28xxu 40960 1
dvb_usb_v2 40960 1 dvb_usb_rtl28xxu
dvb_core 126976 2 dvb_usb_v2,rtl2832
rc_core 36864 5 lirc_dev,ir_lirc_codec,dvb_usb_v2,dvb_usb_rtl28xxu

$ lsusb

Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
**Bus 003 Device 007: ID 15f4:0131 HanfTek** << this device
Bus 003 Device 004: ID 1c4f:0003 SiGma Micro HID controller
Bus 003 Device 003: ID 0bda:818b Realtek Semiconductor Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

sudo dmesg -t | grep dvb

[sudo] password for ggg:
usb 3-1: Product: dvbt2
usb 3-1: Manufacturer: astrometadvbt2
usb 3-1: dvb_usb_v2: found a 'Astrometa DVB-T2' in warm state
usb 3-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
dvbdev: DVB: registering new adapter (Astrometa DVB-T2)
lirc lirc0: lirc_dev: driver ir-lirc-codec (dvb_usb_rtl28xxu) registered at minor = 0
usb 3-1: dvb_usb_v2: schedule remote query interval to 200 msecs
usb 3-1: dvb_usb_v2: 'Astrometa DVB-T2' successfully initialized and connected
usbcore: registered new interface driver dvb_usb_rtl28xxu
dvb_usb_v2: 'Astrometa DVB-T2:3-1' successfully deinitialized and disconnected
usb 3-1: Product: dvbt2
usb 3-1: Manufacturer: astrometadvbt2
usb 3-1: dvb_usb_v2: found a 'Astrometa DVB-T2' in warm state
dvb_usb_rtl28xxu: probe of 3-1:1.0 failed with error -110
usb 3-1: Product: dvbt2
usb 3-1: Manufacturer: astrometadvbt2
usb 3-1: dvb_usb_v2: found a 'Astrometa DVB-T2' in warm state
usb 3-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
dvbdev: DVB: registering new adapter (Astrometa DVB-T2)
lirc lirc0: lirc_dev: driver ir-lirc-codec (dvb_usb_rtl28xxu) registered at minor = 0
usb 3-1: dvb_usb_v2: schedule remote query interval to 200 msecs
usb 3-1: dvb_usb_v2: 'Astrometa DVB-T2' successfully initialized and connected
dvb_usb_v2: 'Astrometa DVB-T2:3-1' successfully deinitialized and disconnected
usb 3-7: Product: dvbt2
usb 3-7: Manufacturer: astrometadvbt2
usb 3-7: dvb_usb_v2: found a 'Astrometa DVB-T2' in warm state
usb 3-7: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
dvbdev: DVB: registering new adapter (Astrometa DVB-T2)
lirc lirc0: lirc_dev: driver ir-lirc-codec (dvb_usb_rtl28xxu) registered at minor = 0
usb 3-7: dvb_usb_v2: schedule remote query interval to 200 msecs
usb 3-7: dvb_usb_v2: 'Astrometa DVB-T2' successfully initialized and connected

dvb-fe-tool -a 0 -f 0

Device Realtek RTL2832 (DVB-T) (/dev/dvb/adapter0/frontend0) capabilities:
CAN_FEC_1_2
CAN_FEC_2_3
CAN_FEC_3_4
CAN_FEC_5_6
CAN_FEC_7_8
CAN_FEC_AUTO
CAN_GUARD_INTERVAL_AUTO
CAN_HIERARCHY_AUTO
CAN_INVERSION_AUTO
CAN_MUTE_TS
CAN_QAM_16
CAN_QAM_64
CAN_QAM_AUTO
CAN_QPSK
CAN_RECOVER
CAN_TRANSMISSION_MODE_AUTO
DVB API Version 5.10, Current v5 delivery system: DVBT
Supported delivery system:
[DVBT]

dvb-fe-tool -a 0 -f 1

WARNING device dvb0.frontend1 not found

[orator89]

Ehi, someone has the Astrometa 2018 version with CXD2837 demodulator instead of Panasonic MN88473? I have kernel 4.4.35 (Openpli 8.2, decoder uclan 4k pro) and found  driver kernel cxd2841.ko for this device but it's not recognized as DVB-T2/, with command:

 

ls -la /dev/dvb/adapter*/*

there's only adapter 1 frontend 0 for DVB-T part (and it doesn't find channels... I live in Italy where DVB-T is still working in use)
Someone has updated drivers or firmwares/modules to get it working?

Edited by orator89, 26 July 2022 - 19:04.

[WanWizard]

Same issue as with the RTL2832? That fix isn't in the release image.

[orator89]

Same issue as with the RTL2832? That fix isn't in the release image.

 

No different issue... This issue is in all the images and is not related to "IOCTL" errors
This time is problem with the slave demodulators of the tuner, that are not recognized by driver because the drivers need update... I started also a topic

[WanWizard]

Ok.