[linux-dvb] MT2060 and DibCom3000P on USB stick

Markus Rechberger mrechberger at gmail.com
Wed Mar 22 17:39:43 CET 2006


Interesting that I have the same problem...

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 719000000 0 1 9 3 1 2 0
>>> tune to: 719000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_1_2:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010
dumping lists (0 services)
Done.

but I use an experimental v4l-dvb driver for the em2880..

On 3/22/06, ygosset <ygosset at free.fr> 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.
> "
>
>
> And syslog message when I lauch the scan.
>
> "
> Mar 22 12:47:20 kim kernel: dvb-usb: found a 'LEADTEK - USB2.0 WINFAST DTV
> DONGLE' in cold state, will try to loada firmware
> Mar 22 12:47:20 kim kernel: dvb-usb: downloading firmware from file
> 'dvb-usb-dibusb-6.0.0.8.fw'
> Mar 22 12:47:20 kim kernel: usbcore: registered new driver dvb_usb_dibusb_mc
> Mar 22 12:47:20 kim kernel: usb 4-6: USB disconnect, address 3
> Mar 22 12:47:20 kim kernel: dvb-usb: generic DVB-USB module successfully
> deinitialized and disconnected.
> Mar 22 12:47:22 kim kernel: usb 4-6: new high speed USB device using ehci_hcd
> and address 4
> Mar 22 12:47:22 kim kernel: dvb-usb: found a 'LEADTEK - USB2.0 WINFAST DTV
> DONGLE' in warm state.
> Mar 22 12:47:22 kim kernel: dvb-usb: will pass the complete MPEG2 transport
> stream to the software demuxer.
> Mar 22 12:47:22 kim kernel: DVB: registering new adapter (LEADTEK - USB2.0
> WINFAST DTV DONGLE).
> Mar 22 12:47:22 kim kernel: dib3000: Found a DiBcom 3000P.
> Mar 22 12:47:22 kim kernel: DVB: registering frontend 0 (DiBcom 3000P/M-C
> DVB-T)...
> Mar 22 12:47:22 kim kernel: MT2060: Identified Microtune MT2060 chip
> Mar 22 12:47:22 kim kernel: dvb-usb: schedule remote query interval to 150
> msecs.
> Mar 22 12:47:22 kim kernel: dvb-usb: LEADTEK - USB2.0 WINFAST DTV DONGLE
> successfully initialized and connected.
> Mar 22 12:47:22 kim hal.hotplug[9027]: DEVPATH is not set
> Mar 22 12:48:57 kim kernel:
> Mar 22 12:48:57 kim last message repeated 2 times
> Mar 22 12:48:58 kim kernel: dvb-usb: could not submit URB no. 0 - get them all
> back
> Mar 22 12:50:14 kim kernel: dvb-usb: could not submit URB no. 0 - get them all
> back
> Mar 22 12:50:15 kim kernel:
> Mar 22 12:50:15 kim last message repeated 2 times
> Mar 22 12:50:15 kim kernel: dvb-usb: could not submit URB no. 0 - get them all
> back
> Mar 22 12:51:31 kim kernel: dvb-usb: could not submit URB no. 0 - get them all
> back
> Mar 22 12:51:32 kim kernel:
> Mar 22 12:51:32 kim last message repeated 2 times
> Mar 22 12:51:33 kim kernel: dvb-usb: could not submit URB no. 0 - get them all
> back
> Mar 22 12:52:49 kim kernel: dvb-usb: could not submit URB no. 0 - get them all
> back
> Mar 22 12:52:50 kim kernel:
> Mar 22 12:52:50 kim last message repeated 2 times
> Mar 22 12:52:51 kim kernel: dvb-usb: could not submit URB no. 0 - get them all
> back
> Mar 22 12:54:07 kim kernel: dvb-usb: could not submit URB no. 0 - get them all
> back
> Mar 22 12:54:08 kim kernel:
> Mar 22 12:54:08 kim last message repeated 2 times
> Mar 22 12:54:08 kim kernel: dvb-usb: could not submit URB no. 0 - get them all
> back
> Mar 22 12:55:24 kim kernel: dvb-usb: could not submit URB no. 0 - get them all
> back
> "
>
>
> Some information about my own configuration:
> "[root at kim ~]# lspcidrake
> ..
> usb-uhci        : Intel Corp.|82801DB USB Controller [SERIAL_USB]
> usb-uhci        : Intel Corp.|82801DB USB Controller [SERIAL_USB]
> usb-uhci        : Intel Corp.|82801DB USB Controller [SERIAL_USB]
> ehci-hcd        : Intel Corp.|82801DB USB Enhanced Controller [SERIAL_USB]
> ..
> hub             : Linux 2.6.11-6mdk-i686-up-4GB ehci_hcd|EHCI Host Controller
> [Hub|Unused]
> dvb_usb_dibusb_mc: STAE|MOD3000
> hub             : Linux 2.6.11-6mdk-i686-up-4GB uhci_hcd|UHCI Host Controller
> [Hub|Unused]
> hub             : Linux 2.6.11-6mdk-i686-up-4GB uhci_hcd|UHCI Host Controller
> [Hub|Unused]
> usbhid          : Logitech Inc.|Optical Mouse [Human Interface Devices|Boot
> Interface Subclass|Mouse]
> hub             : Linux 2.6.11-6mdk-i686-up-4GB uhci_hcd|UHCI Host Controller
> [Hub|Unused]
> ..
> [root at kim ~]# uname -a
> Linux kim 2.6.11-6mdk-i686-up-4GB #1 Tue Mar 22 15:51:40 CET 2005 i686
> Intel(R) Pentium(R) M processor 1.50GHz unknown GNU/Linux
> [root at kim ~]# lspci
> 00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller
> (rev 21)
> 00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev
> 21)
> 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
> USB UHCI Controller #1 (rev 03)
> 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
> USB UHCI Controller #2 (rev 03)
> 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
> USB UHCI Controller #3 (rev 03)
> 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI
> Controller (rev 03)
> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83)
> 00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge
> (rev 03)
> 00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev
> 03)
> 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM
> (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller(rev 03)
> 00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97
> Modem Controller (rev 03)
> 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon
> 9600 M10]
> 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
> 02:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG (rev 05)
> 02:05.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ac)
> 02:05.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ac)
> 02:05.2 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev
> 04)
> "
>
> Any Help ?
>
> Yvan.
>
>
>
> Le Vendredi 17 Mars 2006 14:22, ygosset a écrit:
> > Hello.
> >
> > Ok, I will do it ! :)
> > Thanks !!!!
> > I will provide result in two days.(I can't test before).
> >
> > Yes, there is an infrared remote device, but I need a magnifying glass ;).
> >
> > I've another Jpeg at this time:
> > http://img223.imageshack.us/img223/3519/im58bz.jpg
> > (remote controller: http://img114.imageshack.us/img114/2715/im13dd.jpg )
> >
> > Yvan.
> >
> > Le Vendredi 17 Mars 2006 13:57, treza at chez.com a écrit:
> > > As you suggest, you can be the beta-tester !
> > >
> > > To do that :
> > > - Get the latest v4l source tree
> > > - Merge the "MT2060" patches that I submitted today.
> > > - Add to the file "dvb-usb-ids.h" the following lines :
> > >
> > > ------------------------------------------------------------------------
> > > #define USB_VID_LITEON                                      0x04ca
> > >
> > > >>add this>>#define USB_VID_LEADTEK                                 0x0413
> > >
> > > /* Product IDs */
> > > ------------------------------------------------------------------------
> > > #define USB_PID_GRANDTEC_DVBT_USB2_COLD                     0x0bc6
> > > #define USB_PID_GRANDTEC_DVBT_USB2_WARM                     0x0bc7
> > >
> > > >>add this>>#define USB_PID_WINFAST_DTV_DONGLE_COLD                 0x6025
> > > >>add this>>#define USB_PID_WINFAST_DTV_DONGLE_WARM                 0x6026
> > >
> > > #endif
> > > ------------------------------------------------------------------------
> > >
> > > - Add to the file "dibusb-mc.c" the following lines :
> > >
> > > ------------------------------------------------------------------------
> > > /* 08 */        { USB_DEVICE(USB_VID_GRANDTEC,
> > > USB_PID_GRANDTEC_DVBT_USB2_COLD) },
> > > /* 09 */        { USB_DEVICE(USB_VID_GRANDTEC,
> > > USB_PID_GRANDTEC_DVBT_USB2_WARM) },
> > >
> > > >>add this>>/* 10 */        { USB_DEVICE(USB_VID_LEADTEK,
> > >
> > > USB_PID_WINFAST_DTV_DONGLE_COLD) },
> > >
> > > >>add this>>/* 11 */        { USB_DEVICE(USB_VID_LEADTEK,
> > >
> > > USB_PID_WINFAST_DTV_DONGLE_WARM) },
> > >                     { }             /* Terminating entry */
> > >
> > > ------------------------------------------------------------------------
> > >     .num_device_descs = 5,
> > >
> > > >>change to>>       .num_device_descs = 6,
> > >
> > > ------------------------------------------------------------------------
> > >             {   "GRAND - USB2.0 DVB-T adapter",
> > >                     { &dibusb_dib3000mc_table[8], NULL },
> > >                     { &dibusb_dib3000mc_table[9], NULL },
> > >             },
> > >
> > > >>add this>>                {   "LEADTEK - USB2.0 WINFAST DTV DONGLE",
> > > >>add this>>                        { &dibusb_dib3000mc_table[10], NULL },
> > > >>add this>>                        { &dibusb_dib3000mc_table[11], NULL },
> > > >>add this>>                },
> > >
> > >             { NULL },
> > > ------------------------------------------------------------------------
> > >
> > > - Compile, et caetera.
> > >
> > > Then, tell us whether it works or not.
> > >
> > > The normal sequence would be for the LED to go ON for a few
> > > seconds, then OFF, then ON again. If it doesn't blink, maybe
> > > the WARM id is wrong, set it accordingly to what you get
> > > from lsusb while the LED is ON
> > >
> > > Your device seems to have a remote controller ( which won't
> > > work for now).
> > > Can you tell to which components ( references, ... ) the IR
> > > receiver is connected ?
> > >
> > > Regards
> > > O.DANET
> > >
> > >
> > >
> > >
> .....
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb at linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>


--
Markus Rechberger



More information about the linux-dvb mailing list