No tune
#1
Hi all,
I have problem with tuning. I try two DVB-T tuner (on this device http://dx.com/p/hd16t-android-4-0-google...ler-169876):

- MXL101 (integrated device)
- then I bought USB with AF9015 chipset + TDA 18218

My Kernel wersion is 2.6.34 and is compiled with support for MXL101 and AF9015(TDA18218).

I see frontend0 in /dev/dvb/adapter0 and also in /dev/dvb/adapter1

At web service tvheadend in configurations page I see both tuners.

But both tuners have problem with tune. Always I get this error:
[ ERROR]:dvb: "/dev/dvb/adapterX" tuning to "858,000 kHz" -- Front configuration failed -- Operation not supported on transport endpoint, frequency: 858000000
etc.

Where is the problem, what I must check?

Thanks, MG
Reply
#2
Have you made sure the user running tvheadend has read/write access to the adapter? Usually that means making it part of the "video" group.
Reply
#3
I also try run tvheadend as root...

[[email protected] tvheadend]# dmesg | grep -i dvb
[ 5.618815] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware
[ 5.624133] usb 2-1.4: firmware: requesting dvb-usb-af9015.fw
[ 8.147206] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'
[ 8.253233] dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state.
[ 8.255330] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 8.374279] DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick)
[ 8.450860] DVB: registering adapter 1 frontend 0 (Afatech AF9013 DVB-T)...
[ 8.503768] dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected.

[[email protected] tvheadend]# ls -l /dev/dvb/* -R
/dev/dvb/adapter0:
crw-rw-rw- 1 root video 212, 4 Jan 1 1970 demux0
crw-rw-rw- 1 root video 212, 20 Jan 1 1970 demux1
crw-rw-rw- 1 root video 212, 36 Jan 1 1970 demux2
crw-rw-rw- 1 root video 212, 9 Jan 1 1970 dsc0
crw-rw-rw- 1 root video 212, 5 Jan 1 1970 dvr0
crw-rw-rw- 1 root video 212, 21 Jan 1 1970 dvr1
crw-rw-rw- 1 root video 212, 37 Jan 1 1970 dvr2
crw-rw-rw- 1 root video 212, 3 Jan 1 1970 frontend0
crw-rw-rw- 1 root video 212, 7 Jan 1 1970 net0
crw-rw-rw- 1 root video 212, 23 Jan 1 1970 net1
crw-rw-rw- 1 root video 212, 39 Jan 1 1970 net2

/dev/dvb/adapter1:
crw-rw-rw- 1 root video 212, 68 Jan 1 1970 demux0
crw-rw-rw- 1 root video 212, 69 Jan 1 1970 dvr0
crw-rw-rw- 1 root video 212, 67 Jan 1 1970 frontend0
crw-rw-rw- 1 root video 212, 71 Jan 1 1970 net0

[[email protected] tvheadend]# ./tvheadend -C
Mar 24 21:31:44 [ INFO]:START: initialising
Mar 24 21:31:44 [ INFO]:dvb: Found adapter /dev/dvb/adapter0 (AMLOGIC DVB-T) via PCI
Mar 24 21:31:44 [ INFO]:dvb: Found adapter /dev/dvb/adapter1 (Afatech AF9013 DVB-T) via USB (480 Mbit/s)
Mar 24 21:31:44 [ INFO]:dvb: Adapter /dev/dvb/adapter1 will run in filtered mode
Mar 24 21:31:44 [ INFO]:CSA: Using 32bit parallel descrambling
Mar 24 21:31:44 [ INFO]:epggrab: module eit created
Mar 24 21:31:44 [ INFO]:epggrab: module uk_freesat created
Mar 24 21:31:44 [ INFO]:epggrab: module uk_freeview created
Mar 24 21:31:44 [ INFO]:epggrab: module viasat_baltic created
Mar 24 21:31:44 [ INFO]:epggrab: module pyepg created
Mar 24 21:31:44 [ INFO]:epggrab: module xmltv created
Mar 24 21:31:44 [ INFO]:epgdb: loaded v2
Mar 24 21:31:44 [ INFO]:epgdb: channels 0
Mar 24 21:31:44 [ INFO]:epgdb: brands 0
Mar 24 21:31:44 [ INFO]:epgdb: seasons 0
Mar 24 21:31:44 [ INFO]:epgdb: episodes 0
Mar 24 21:31:44 [ INFO]:epgdb: broadcasts 0
Mar 24 21:31:44 [ INFO]:dvr: Creating new configuration ''
Mar 24 21:31:44 [WARNING]:dvr: Output directory for video recording is not yet configured for DVR configuration "". Defaulting to to "/root". This can be changed from the web user interface.
Mar 24 21:31:44 [ NOTICE]:START: HTS Tvheadend version 3.5.52~g819b8c8 started, running as PID:753 UID:0 GID:0, settings located in '/root/.hts/tvheadend'
Mar 24 21:31:45 [ ERROR]:dvb: "/dev/dvb/adapter1" tuning to "506,000 kHz" -- Front configuration failed -- Operation not supported, frequency: 506000000
Mar 24 21:32:05 [ ERROR]:dvb: "/dev/dvb/adapter1" tuning to "538,000 kHz" -- Front configuration failed -- Operation not supported, frequency: 538000000
^CMar 24 21:32:06 [ INFO]:epgdb: saved
Mar 24 21:32:06 [ INFO]:epgdb: brands 0
Mar 24 21:32:06 [ INFO]:epgdb: seasons 0
Mar 24 21:32:06 [ INFO]:epgdb: episodes 0
Mar 24 21:32:06 [ INFO]:epgdb: broadcasts 0
Mar 24 21:32:06 [ NOTICE]:STOP: Exiting HTS Tvheadend
Reply
#4
You're probably missing firmware or something for the second tuner (adapter1), the other seems to be working fine.
Reply
#5
When tvheadend try tune I found this:

[ 809.550543] af9015: too much data; cmd:41 len:59
[ 847.022245] af9015: too much data; cmd:41 len:59
[ 1027.895749] af9015: too much data; cmd:41 len:59
Reply
#6
Sounds like the driver is broken. I would highly recommend upgrading to a less ancient kernel.
Reply
#7
I compile different version drivers for AF9015 and error "af9015: too much data; cmd:41 len:59" is not displayed. Bud result is the same: "Front configuration failed -- Operation not supported". I also compile w_scan and today I make test with this program (maybe display more specifics informations).

I would like to use newest kernel than 2.6.34, bud I can't find newest for amlogic aml8726-m3 (with Mali-400 display driver).

What DVB API version tvheadend need? My kernel use 5.1.
Reply
#8
w_scan works bud tvheadend no :-( It is possible import data to tvheadend from w_scan?

[[email protected]ldroot tvheadend]# ./w_scan -c CZ
w_scan version 20091230 (compiled for DVB API 5.1)
using settings for CZECH REPUBLIC
DVB aerial
DVB-T Europe
frontend_type DVB-T, channellist 4
output format vdr-1.6
Info: using DVB adapter auto detection.
/dev/dvb/adapter0/frontend0 -> DVB-T "Afatech AF9013 DVB-T": good :-)
Using DVB-T frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_
Using DVB API 5.1
frontend Afatech AF9013 DVB-T supports
INVERSION_AUTO
QAM_AUTO
TRANSMISSION_MODE_AUTO
GUARD_INTERVAL_AUTO
HIERARCHY_AUTO
FEC_AUTO
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Scanning 7MHz frequencies...
177500: (time: 00:00)
184500: (time: 00:03)
191500: (time: 00:06)
198500: (time: 00:08)
205500: (time: 00:11)
212500: (time: 00:13)
219500: (time: 00:16)
226500: (time: 00:19)
Scanning 8MHz frequencies...
474000: (time: 00:21)
482000: (time: 00:24)
490000: (time: 00:26)
498000: (time: 00:29)
506000: (time: 00:31)
514000: (time: 00:34)
522000: (time: 00:36)
530000: (time: 00:39)
538000: (time: 00:41)
546000: (time: 00:44) (time: 00:46) signal ok:
QAM_AUTO f = 546000 kHz I999B8C999D999T999G999Y999
new transponder:
(QAM_64 f = 658000 kHz I999B8C34D0T8G8Y0)
....
....
....
tune to: QAM_AUTO f = 570000 kHz I999B8C999D999T999G999Y999
(time: 04:01) service = CT 1 (Ceska televize)
service = CT 2 (Ceska televize)
service = CT 24 (Ceska televize)
service = CT sport (Ceska televize)
service = CRo RADIOZURNAL (Ceska televize)
service = CRo DVOJKA (Ceska televize)
service = CRo VLTAVA (Ceska televize)
service = CRo RADIO WAVE (Ceska televize)
service = CRo D-DUR (Ceska televize)
service = CRo RADIO JUNIOR (Ceska televize)
service = CRo PLUS (Ceska televize)
service = CRo JAZZ (Ceska televize)
tune to: QAM_64 f = 730000 kHz I999B8C23D0T8G4Y0
etc.
Reply
#9
I can't remember which API it uses. You could try the stable version (3.4) and the master branch (3.9) but I suspect getting a newer kernel is the only solution.
Reply
#10
I searched on internet for newer kernel, but for Meson3 (CPU type) newest kernel is not exist (only for Meson6, but must do a lot of editing and the result will be uncertain). I spent a lot of hours with it, but without result (bud XBMC on this device works fine). Probably I buy Raspberry Pi and it will run only tvheadend for my home network and that's it... Thank you for your support.
Reply



Logout Mark Read Team Forum Stats Members Help
No tune0
This forum uses Lukasz Tkacz MyBB addons.