@sam_nazarko Is this problem still on focus? The workaround is annoying on my network because of high load.
There are more DVB dongles to be supported in a future update, yes
1 Like
It certainly took a little longer than expected, but I’ve now added most DVB drivers from 4.x kernels to the Vero 4K kernel.
Most dongles should now work out of the box, although you may need to download and copy some firmware files. If this is the case, please let me know what files are needed and I’ll have them included in a future update of OSMC.
Thanks for your patience, and looking forward to your feedback. It looks like we will also be releasing our own DVB-T2 dongle soon enough which will work across all OSMC supported devices and stay supported in the long term.
Sam
1 Like
Thanks. I’ll definitely look at this tonight. As Debian stretch will be published in a couple of days, is there a plan to bump OSMC linux version for Vero 4k to 4.9 as in upstream?
Hi – there are no plans to do this at this time.
Sam
Still no success in enabling the device in 3.14.29-19-osmc. Every thing seems to be okay according to the logs and it recognize the chip currectly as Afatech AF9033, but the dongle lamp is still off and new errors in tvheadend on scanning muxes.
lsusb output:
Bus 001 Device 003: ID 048d:9006 Integrated Technology Express, Inc. IT9135 BDA Afatech DVB-T HDTV Dongle
Tvheadend mux scanning log:
2017-06-08 04:43:09.124 mpegts: 602MHz in IRIB - tuning on Afatech AF9033 (DVB-T) : DVB-T #0
2017-06-08 04:43:09.124 linuxdvb: Afatech AF9033 (DVB-T) : DVB-T #0 - DTV_CLEAR failed [e=Inappropriate ioctl for device]
dmesg log:
[ 6.255070] WARNING: You are using an experimental version of the media stack.
As the driver is backported to an older kernel, it doesn't offer
enough quality for its usage in production.
Use it with care.
Latest git patches (needed if you report a bug to linux-media@vger.kernel.org):
a83dbc951051ded0ec728f65cc918b7320600b55 Remove unused stv6120 headers.
[ 6.329089] dvb_usb_af9035 1-2:1.0: prechip_version=83 chip_version=02 chip_type=9135
[ 6.339563] usb 1-2: dvb_usb_v2: found a 'ITE 9135(9006) Generic' in cold state
[ 6.358323] usb 1-2: dvb_usb_v2: downloading firmware from file 'dvb-usb-it9135-02.fw'
[ 6.455377] dvb_usb_af9035 1-2:1.0: firmware version=3.40.1.0
[ 6.455402] usb 1-2: dvb_usb_v2: found a 'ITE 9135(9006) Generic' in warm state
[ 6.455410] dvb_usb_af9035 1-2:1.0: [0] overriding tuner from 00 to 60
[ 6.455999] usb 1-2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 6.456067] dvbdev: DVB: registering new adapter (ITE 9135(9006) Generic)
[ 6.456075] usb 1-2: media controller created
[ 6.457011] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[ 6.519295] af9033 1-001c: firmware version: LINK 3.40.1.0 - OFDM 3.40.1.0
[ 6.519308] af9033 1-001c: Afatech AF9033 successfully attached
[ 6.519337] usb 1-2: DVB: registering adapter 0 frontend 0 (Afatech AF9033 (DVB-T))...
[ 6.519360] dvbdev: dvb_create_media_entity: media entity 'Afatech AF9033 (DVB-T)' registered.
[ 6.542518] it913x it9133bx-tuner.1.auto: ITE IT913X BX successfully attached
[ 6.553868] rc rc1: ITE 9135(9006) Generic as /devices/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-2/rc/rc1
[ 6.587453] Registered IR keymap rc-it913x-v1
[ 6.587629] input: ITE 9135(9006) Generic as /devices/c9000000.dwc3/xhci-hcd.0.auto/usb1/1-2/rc/rc1/input6
[ 6.587768] usb 1-2: dvb_usb_v2: 'ITE 9135(9006) Generic' successfully initialized and connected
[ 6.587826] usbcore: registered new interface driver dvb_usb_af9035
I am suspected to the old version of Tvheadend. How can I get sure about that?
I even tried to install tvheadend 4,3 armhf from upstream, but it could not be installed due to low version of libdbus-1-3 in jessie.
If that’s the case, then dvbscan/wscan/scan should work however. So best to get a channel mapping outside of TVH (stop it first as it grabs adapters) and then proceed.
It’s good to see your tuner is being detected and firmware is being loaded.
Sam
I tried scan/dvbscan/dvbsnoop on both rbp an vero with no success. The only working suit on rbp was w-scan . Here is the logs from w-scan on rbp and vero:
Vero 4k:
w_scan version 20130331 (compiled for DVB API 5.4)
using settings for IRAN, ISLAMIC REPUBLIC OF
scan type TERRESTRIAL, channellist 4
output format czap/tzap/szap/xine
output charset 'UTF-8'
Info: using DVB adapter auto detection.
/dev/dvb/adapter0/frontend0 -> "Afatech AF9033 (DVB-T)" doesnt support TERRESTRIAL -> SEARCH NEXT ONE.
main:3228: FATAL: ***** NO USEABLE TERRESTRIAL CARD FOUND. *****
Please check wether dvb driver is loaded and
verify that no dvb application (i.e. vdr) is running.
RaspberryPi 2:
w_scan version 20130331 (compiled for DVB API 5.4)
using settings for IRAN, ISLAMIC REPUBLIC OF
scan type TERRESTRIAL, channellist 4
output format czap/tzap/szap/xine
output charset 'UTF-8'
Info: using DVB adapter auto detection.
/dev/dvb/adapter0/frontend0 -> TERRESTRIAL "Afatech AF9033 (DVB-T)": good :-)
Using TERRESTRIAL frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_
Using DVB API 5.a
frontend 'Afatech AF9033 (DVB-T)' supports
INVERSION_AUTO
QAM_AUTO
TRANSMISSION_MODE_AUTO
GUARD_INTERVAL_AUTO
HIERARCHY_AUTO
FEC_AUTO
FREQ (174.00MHz ... 862.00MHz)
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
As you see, the frontend doesnt support TERRESTRIAL in Vero 4k, but in RaspberryPi 2.
You need to stop tvheadend before running w-scan or it wont pick up adapter.
Run
sudo service tvheadend stop
And try again
Of course tvheadend is stopped in both cases.
Is the firmware correct?
Same antenna for both Pi2 and Vero 4K?
Yes. Compared firmwares by md5sum. Everything is same.
same problem here:
w_scan version 20130331 (compiled for DVB API 5.4)
using settings for ESTONIA
Country identifier EE not defined. Using defaults.
scan type TERRESTRIAL, channellist 4
output format czap/tzap/szap/xine
WARNING: could not guess your codepage. Falling back to ‘UTF-8’
output charset ‘UTF-8’, use -C to override
Info: using DVB adapter auto detection.
/dev/dvb/adapter0/frontend0 -> “Afatech AF9033 (DVB-T)” doesnt support T ERRESTRIAL -> SEARCH NEXT ONE.
main:3228: FATAL: ***** NO USEABLE TERRESTRIAL CARD FOUND. *****
tvheadend system log:
2017-06-12 11:24:51.002 linuxdvb: Afatech AF9033 (DVB-T) : DVB-T #0 - DTV_CLEAR failed [e=Inappropriate ioctl for device]
2017-06-12 11:24:51.002 mpegts: 626MHz in levira - tuning on Afatech AF9033 (DVB-T) : DVB-T #0
2017-06-12 11:24:51.002 linuxdvb: Afatech AF9033 (DVB-T) : DVB-T #0 - DTV_CLEAR failed [e=Inappropriate ioctl for device]
2017-06-12 11:24:51.003 mpegts: 722MHz in levira - tuning on Afatech AF9033 (DVB-T) : DVB-T #0
2017-06-12 11:24:51.003 linuxdvb: Afatech AF9033 (DVB-T) : DVB-T #0 - DTV_CLEAR failed [e=Inappropriate ioctl for device]
2017-06-12 11:24:51.003 mpegts: 490MHz in levira - tuning on Afatech AF9033 (DVB-T) : DVB-T #0
2017-06-12 11:24:51.003 linuxdvb: Afatech AF9033 (DVB-T) : DVB-T #0 - DTV_CLEAR failed [e=Inappropriate ioctl for device]
provide URL of dmesg paste-log and also the link to the firmware you used.
tvheadend output when i try create new network
settings: Unable to create dir “/home/osmc/.hts/tvheadend/input/dvb/networks/7b9bd5dd65769a6f284146e17adb28a9”: Permission denied
log:https://paste.osmc.tv/gipivocodi.vbs
firmware Index of /linux/v4l-dvb/firmware/Si2168/Si2168-B40
How do you come to that firmware link? Shouldn’t it be this?
http://palosaari.fi/linux/v4l-dvb/firmware/af9035/
The firmware is included in dvb-firmware-osmc package.
sorry this is my second dvb adapter which do no working too and yes firmware is from that site:http://palosaari.fi/linux/v4l-dvb/firmware/af9035/ and with old vero1 this dvb adpter working but with vero4 not working .I have 3 different dvb adapters and None does not work,i have copied from old vero1 firmware no benefit
We are still improving the support for DVB adapters on Vero 4K. For now
I’d recommend still using it on the Vero 1 until we fix this in the (likely) very
near future.
Sam
1 Like