Hi,
Klaus Frahm wrote:
On 31 Jul, matthieu castet wrote:
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 ?
No, neither in dmesg nor in /var/log/messages. In dmesg I see after
initializing the device:
usb 5-8: new high speed USB device using ehci_hcd and address 5
usb 5-8: configuration #1 chosen from 1 choice
dibx000_common: module license 'unspecified' taints kernel.
dvb-usb: found a 'AVerMedia AverTV DVB-T USB 2.0 (A800)' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (AVerMedia AverTV DVB-T USB 2.0 (A800)).
DVB: registering frontend 0 (DiBcom 3000MC/P)...
input: IR-receiver inside an USB DVB receiver as /class/input/input3
dvb-usb: schedule remote query interval to 150 msecs.
dvb-usb: AVerMedia AverTV DVB-T USB 2.0 (A800) successfully initialized and connected.
usbcore: registered new driver dvb_usb_a800
Thanks, that could explain the differences.
I don't see your device on
http://linuxtv.org/wiki/index.php/DVB_USB#DiBcom_USB2.0_DVB-T_devices_.28based_on_the_DiB3000M-C.2FP.29
, may be you should add it.
Matthieu
PS : I won't be available for 2 weeks.
_______________________________________________
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
