[linux-dvb] MT2060 and DibCom3000P on USB stick

Patrick Boettcher patrick.boettcher at desy.de
Wed Mar 22 19:23:30 CET 2006


On Wed, 22 Mar 2006, ygosset wrote:

> Hello.
>
> I have applied all patch to test MT2060 Tuner on my Usb device from O.Danet
> (treza at chez.com),
> http://www.chez.com/treza/liteon.htm .
>
> Here is my trace:
> "
> cd /tmp/DVB/v4l-dvb/v4l
>
> rmmod dvb-usb-dibusb-mc
> rmmod dvb-usb-dibusb-common
> rmmod dvb-usb
> rmmod dvb_dibusb
> rmmod dib3000mb
> rmmod dib3000mc
> rmmod dib3000-common
> rmmod mt2060
> rmmod dvb-core
> rmmod dvb-pll
> modprobe i2c_core
> modprobe firmware_class
> insmod ./dvb-pll.ko
> insmod ./mt2060.ko
> insmod ./dvb-core.ko
> insmod ./dib3000-common.ko
> insmod ./dib3000mc.ko
> insmod ./dvb-usb.ko
> insmod ./dvb-usb-dibusb-common.ko
> insmod ./dvb-usb-dibusb-mc.ko
>
> "
> [root at kim v4l]# /tmp/DVB/dvb-apps/util/scan/dvbscan -v -n
> -5 /tmp/DVB/dvb-apps/util/scan/dvb-t/fr-Paris
> scanning /tmp/DVB/dvb-apps/util/scan/dvb-t/fr-Paris
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> initial transponder 474000000 0 2 9 3 1 0 0
> initial transponder 498000000 0 2 9 3 1 0 0
> initial transponder 522000000 0 2 9 3 1 0 0
> initial transponder 562000000 0 2 9 3 1 0 0
> initial transponder 586000000 0 3 9 3 1 2 0
>>>> tune to:
> 474000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
>>>> tuning status == 0x02
>>>> tuning status == 0x1e
> WARNING: filter timeout pid 0x0011
> WARNING: filter timeout pid 0x0000
> WARNING: filter timeout pid 0x0010
> WARNING: filter timeout pid 0x0010
>>>> tune to:
> 498000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
>>>> tuning status == 0x03
>>>> tuning status == 0x1f
> WARNING: filter timeout pid 0x0011
> WARNING: filter timeout pid 0x0000
> WARNING: filter timeout pid 0x0010
> WARNING: filter timeout pid 0x0010
>>>> tune to:
> 522000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
>>>> tuning status == 0x02
>>>> tuning status == 0x1f
> WARNING: filter timeout pid 0x0011
> WARNING: filter timeout pid 0x0000
> WARNING: filter timeout pid 0x0010
> WARNING: filter timeout pid 0x0010
>>>> tune to:
> 562000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
>>>> tuning status == 0x02
>>>> tuning status == 0x1f
> WARNING: filter timeout pid 0x0011
> WARNING: filter timeout pid 0x0000
> WARNING: filter timeout pid 0x0010
> WARNING: filter timeout pid 0x0010
>>>> tune to:
> 586000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE
>>>> tuning status == 0x03
>>>> tuning status == 0x1f
> WARNING: filter timeout pid 0x0011
> WARNING: filter timeout pid 0x0000
> WARNING: filter timeout pid 0x0010
> WARNING: filter timeout pid 0x0010
> dumping lists (0 services)
> Done.
> "

So everything is OK for you, except this:

> Mar 22 12:48:58 kim kernel: dvb-usb: could not submit URB no. 0 - get 
> them all back

And additionally, this is very strange. This could mean that your device 
is using another kind of usb-transfer or another USB-Endpoint, which is 
both most unlikely, because you are using the same USB-firmware as all the 
other devices.

Hmm.

After firmware download, how does lsusb -v looks like?

best regards,
Patrick.

--
   Mail: patrick.boettcher at desy.de
   WWW:  http://www.wi-bw.tfh-wildau.de/~pboettch/



More information about the linux-dvb mailing list