Hi,
>>Do you have a mt2060 ?
>
>
> To be honest I am not sure. I have an AverTV A800 which certainly
> depends on DiB3000MC. Furthermore with the new driver the module for
> mt2060 is also automatically loaded when I plug in the usb-device.
> The command lsmod of the dvb-modules gives:
Do you see "MT2060: successfully identified" in the kernel log ?
Klaus Frahm wrote:
On 31 Jul, Sergei Haller wrote:
I am pretty certain that have had exactly the same problem as me, only I
classified it that one needs to get a 2nd lock immediately after the
first one to start the video flux. I am using VLC and either I had to
push the stop/play buttons or as another work to use "tzap -x
<Channel-name>" directly followed VLC. I believe this should also work
with VDR (if you retry the old driver). The workaround with tzap is (or
was) important when I wanted to program to record something.
See my first answer in this thread for more details and links to other
posts in the mailing list about this issue.
As with you, the new driver solves this locking problem.
That's strange : on my side, I have no such locking problem with old
driver :
FE: DiBcom 3000P/M-C DVB-T (DVBT)
status CV | signal 0000 | snr 0001 | ber 001fffff | unc 0000ffff |
status CV | signal 0000 | snr 0001 | ber 001fffff | unc 0000ffff |
status CV | signal 0000 | snr 0001 | ber 001fffff | unc 0000ffff |
status CV | signal 0000 | snr 0001 | ber 001fffff | unc 0000ffff |
status CV | signal 0000 | snr 0001 | ber 001fffff | unc 0000ffff |
status CV | signal 0000 | snr 0001 | ber 001fffff | unc 0000ffff |
<-- channel switch
status SCVYL | signal 7b22 | snr 000d | ber 00001050 | unc 00000000 |
FE_HAS_LOCK
status SCVYL | signal 7b3d | snr 0000 | ber 00000690 | unc 00000000 |
FE_HAS_LOCK
status SCVYL | signal 7b5b | snr 0000 | ber 00000720 | unc 00000000 |
FE_HAS_LOCK
Matthieu
_______________________________________________
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
