7 replies to this topic

[DrAk3]

Hi all,
i bought another a867 usb tuner because i need 2 dtt tuner into my et9x00, but i can't use them together.. with the first the signal is ok but the screen is always black. if i put the priority to the second i can see the program but can't use the second (same problem... black screen).

this is the dmesg:


AVerMedia A867 driver module V1.0.27 loaded.
dvb-usb: found a 'AVerMedia A867 DVB-T Recevier' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (AVerMedia A867 DVB-T Recevier)
DVB: registering adapter 1 frontend 0 (A867 USB DVB-T)...
dvb-usb: AVerMedia A867 DVB-T Recevier successfully initialized and connected.
dvb-usb: found a 'AVerMedia A867 DVB-T Recevier' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (AVerMedia A867 DVB-T Recevier)
DVB: registering adapter 2 frontend 0 (A867 USB DVB-T)...
dvb-usb: AVerMedia A867 DVB-T Recevier successfully initialized and connected.
usbcore: registered new interface driver dvb-usb-a867
Console: switching to colour dummy device 80x25
DVB: registering adapter 0 frontend 2 (vtuner)...
DVB: registering adapter 0 frontend 3 (vtuner)...

and this is the lsmod:

Module Size Used by
dvb_usb_a867 210137 3
dvb_usb 18026 1 dvb_usb_a867
ipv6 351430 12
dvb 5022440 32
modloader2 32629 1 dvb
modloader 22281 0
tpm 6509 3 dvb,modloader2,modloader


i think that kernel use always the second vtuner because it use the same module. Can i bypass this problem?

regards

D.

[WTE]

Do you watch scrambled channel or FTA?
Maybe your card cannot decode more then 1 channel.

[DrAk3]

With 2 different usb tuners i've no problem. And the problem is the same with fta channel or crypted....

I think tha the same kernel module use always vtuner 2...

D.

[DrAk3]

this is the e2 log while trying to tune a dtt channel:

playing 1:0:19:B0:389:110:EEEE0000:0:0:0:
[eDVBCAService] free slot 0 demux 0 for service 1:0:19:1FA9:32A:110:EEEE0000:0:0:0:
[eDVBCAService] free service 1:0:19:1FA9:32A:110:EEEE0000:0:0:0:
decoder state: play, vpid=-1, apid=-1
DEMUX_STOP - pcr - ok
DEMUX_STOP - video - ok
VIDEO_STOP - ok
AUDIO_STOP - ok
DEMUX_STOP - audio - ok
AUDIO_CONTINUE - ok
cleaning up
TuxTxt cache cleared
start release channel timer

not pauseable.
RemovePopup, id = ZapError
[eDVBLocalTimerHandler] remove channel 0x71eb2278
[eEPGCache] remove channel 0x71eb2278
allocate channel.. 0389:0110

(2)tune
OURSTATE: tuning
allocate Channel: res 0
[eDVBCIInterfaces] addPMTHandler 1:0:19:B0:389:110:EEEE0000:0:0:0:
allocate demux
[SEC] startTuneTimeout 5000
[SEC] setVoltage 0
[SEC] setFrontend 1
setting frontend 2
(2)fe event: status 0, inversion off, m_tuning 1

(2)fe event: status 1f, inversion off, m_tuning 2
OURSTATE: ok
[eDVBLocalTimerHandler] channel 0x71eb2278 running
[eEPGCache] channel 0x71eb2278 running
stop release channel timer
ok ... now we start!!
eventNewProgramInfo 0 0
[EPGC] next update in 2 sec
have 1 video stream(s) (0ab4), and 1 audio stream(s) (0ab7), and the pcr pid is 0ab4, and the text pid is ffffffff
allocate demux
TuxTxt cache cleared
decoder state: play, vpid=2740, apid=2743
DMX_SET_PES_FILTER(0xab4) - pcr - ok
DEMUX_START - pcr - ok
DMX_SET_PES_FILTER(0xab7) - audio - ok
DEMUX_START - audio - ok
AUDIO_SET_BYPASS(0) - ok
AUDIO_PAUSE - ok
AUDIO_PLAY - ok
Video Device: /dev/dvb/adapter0/video0
demux device: /dev/dvb/adapter0/demux0
VIDEO_SET_STREAMTYPE 1 - ok
DMX_SET_PES_FILTER(0xab4) - video - ok
DEMUX_START - video - ok
VIDEO_FREEZE - ok
VIDEO_PLAY - ok
VIDEO_SLOWMOTION(0) - ok
VIDEO_FAST_FORWARD(0) - ok
VIDEO_CONTINUE - ok
AUDIO_CONTINUE - ok
disable teletext subtitles
[eDVBCAService] new service 1:0:19:B0:389:110:EEEE0000:0:0:0:
[eDVBCAService] add demux 0 to slot 0 service 1:0:19:B0:389:110:EEEE0000:0:0:0:
[EPGC] start caching events(1357596821)
[EPGC] abort non avail nownext reading
[EPGC] abort non avail schedule reading
[EPGC] abort non avail schedule other reading
[EPGC] abort non avail netmed schedule reading
[EPGC] abort non avail netmed schedule other reading
[EPGC] abort non avail FreeSat schedule_other reading
[EPGC] abort non avail viasat reading
PATready
DVB service failed to tune - error 2
[eDVBLocalTimerHandler] no transponder tuned... or no TDT/TOT avail .. try to use RTC
[eDVBLocalTimerHandler] getRTC returned time=0. RTC problem?
SCAN: the current channel's ID was not corrected - not adding channel.
ignore sdt update data.... incorrect transponder tuned!!!

if i lock the vtuner 1 on channel (start recording for example) this is the e2 log for the second vtuner (that in this case works fine):

playing 1:0:19:1FA9:32A:110:EEEE0000:0:0:0:
[eDVBCAService] free slot 0 demux 0 for service 1:0:19:B0:389:110:EEEE0000:0:0:0:
[eDVBCAService] can not send updated demux info
decoder state: play, vpid=-1, apid=-1
DEMUX_STOP - pcr - ok
DEMUX_STOP - video - ok
VIDEO_STOP - ok
AUDIO_STOP - ok
DEMUX_STOP - audio - ok
AUDIO_CONTINUE - ok
cleaning up
TuxTxt cache cleared
not pauseable.
RemovePopup, id = ZapError
allocate channel.. 032a:0110
available channel.. 0389:0110
opening frontend 3
(3)tune
OURSTATE: tuning
allocate Channel: res 0
[eDVBCIInterfaces] addPMTHandler 1:0:19:1FA9:32A:110:EEEE0000:0:0:0:
allocate demux
[SEC] startTuneTimeout 5000
[SEC] setVoltage 0
[SEC] setFrontend 1
setting frontend 3
(3)fe event: status 0, inversion off, m_tuning 1
(3)fe event: status 1f, inversion off, m_tuning 2
OURSTATE: ok
[eDVBLocalTimerHandler] channel 0x71eb05a8 running
[eEPGCache] channel 0x71eb05a8 running
[EPGC] next update in 2 sec
stop release channel timer
ok ... now we start!!
eventNewProgramInfo 0 0
have 1 video stream(s) (0aaa), and 1 audio stream(s) (0aad), and the pcr pid is 0aaa, and the text pid is ffffffff
allocate demux
TuxTxt cache cleared
decoder state: play, vpid=2730, apid=2733
DMX_SET_PES_FILTER(0xaaa) - pcr - ok
DEMUX_START - pcr - ok
DMX_SET_PES_FILTER(0xaad) - audio - ok
DEMUX_START - audio - ok
AUDIO_SET_BYPASS(0) - ok
AUDIO_PAUSE - ok
AUDIO_PLAY - ok
Video Device: /dev/dvb/adapter0/video0
demux device: /dev/dvb/adapter0/demux1
VIDEO_SET_STREAMTYPE 1 - ok
DMX_SET_PES_FILTER(0xaaa) - video - ok
DEMUX_START - video - ok
VIDEO_FREEZE - ok
VIDEO_PLAY - ok
VIDEO_SLOWMOTION(0) - ok
VIDEO_FAST_FORWARD(0) - ok
VIDEO_CONTINUE - ok
AUDIO_CONTINUE - ok
disable teletext subtitles
[eDVBCAService] new service 1:0:19:1FA9:32A:110:EEEE0000:0:0:0:
[eDVBCAService] add demux 1 to slot 0 service 1:0:19:1FA9:32A:110:EEEE0000:0:0:0:
[eDVBLocalTimerHandler] diff is -392
[eDVBLocalTimerHandler] no correction found... store calced correction(392)
[eDVBLocalTimerHandler] not changed
PATready
use pmtpid 00cd for service_id 1fa9
eventNewProgramInfo 0 0
have 1 video stream(s) (0aaa), and 1 audio stream(s) (0aad), and the pcr pid is 0aaa, and the text pid is ffffffff
decoder state: play, vpid=2730, apid=2733
VIDEO_SLOWMOTION(0) - ok
VIDEO_FAST_FORWARD(0) - ok
VIDEO_CONTINUE - ok
AUDIO_CONTINUE - ok
[eDVBCIInterfaces] gotPMT
VIDEO_GET_EVENT - ok
VIDEO_GET_EVENT - ok
VIDEO_GET_EVENT - ok
[EPGC] start caching events(1357597123)
sdt update done!
PATready
RECORD service event 2

[DrAk3]

Finally i found the problem.
Yesterday i bought another a867 usb key and, as u can see reading above, i can't use both in my et9x00.
During many tests i also try to use again the af9035 kernel module with the new a867 and it works! Apparently my 2 a867 keys are identical and not broken (both works fine with che a867 module driver) but the old one doesn't work with af9035 module reporting errors while tuning channel with this errors:

mxl5007t_write_reg: 473: failed!
mxl5007t_init: error -140 on line 696
mxl5007t_write_reg: 473: failed!
mxl5007t_sleep: error -140 on line 714
mxl5007t_write_reg: 473: failed!
mxl5007t_sleep: error -140 on line 716

So i think that there are 2 types of a867 skyit keys and with 1 of them the af9035 module doesn't work.

Just for closing the thread:

- the af9035 module works better than the a867 (cpu time very low and much faster during zapping)
- now i can use a835 and a867 usb key together.

Regards

D.

[Gennar1]

Hi all, the patch in attachment fixes the problem with the af9035 driver and the new revision of the A867 stick (the "DP7" revision).
The fix has been successfully tested by Drake.

Pieterg, can you add this patch to the Xtrend kernels?
Also, the patch tda18218-7mhz-lopass.patch should be deleted, as it was only required by the old out-of-kernel af9035 driver (due to a wrong setting of the IF frequency). The new af9035 kernel driver does not need it anymore.

Regards,
Gennar1

Attached Files

•  mxl5007t-add-no_probe-and-no_reset-parameters.patch.zip   1.25KB   25 downloads

[pieterg]

thanks, I'll commit the patch

[DrAk3]

many many thanks!