[linux-dvb] freecom USB dvb-t -- new vendor/product ID 14aa:022a

Mikel Martin mikel.martin at gmail.com
Mon Mar 27 22:55:59 CEST 2006


Much better!!


usb 1-2: new high speed USB device using ehci_hcd and address 2
dvb-usb: found a 'WideView WT-220U PenType Receiver (based on ZL353)' in
cold state, will try to load a firmware
dvb-usb: did not find the firmware file. (dvb-usb-wt220u-zl0353-01.fw)
Please see linux/Documentation/dvb/ for more details on firmware-problems.
(-2)
usb 1-2: USB disconnect, address 2
usb 1-2: new high speed USB device using ehci_hcd and address 3
dvb-usb: found a 'WideView WT-220U PenType Receiver (based on ZL353)' in
cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-wt220u-zl0353-01.fw'
usb 1-2: USB disconnect, address 3
dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
usb 1-2: new high speed USB device using ehci_hcd and address 4
dvb-usb: found a 'WideView WT-220U PenType Receiver (based on ZL353)' in
warm state.
dvb-usb: will use the device's hardware PID filter (table count: 15).
DVB: registering new adapter (WideView WT-220U PenType Receiver (based on
ZL353)).
dvb-usb: dvb_dmx_init failed: error -12
dvb-usb: WideView WT-220U PenType Receiver (based on ZL353) error while
loading driver (-12) 

It seems that there's an error there, but now the led has stopped bliking.

If I try to scan for channels:
$dvbscan dvb-t/es-Madrid
scanning dvb-t/es-Madrid
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
main:2228: FATAL: failed to open '/dev/dvb/adapter0/frontend0': 19 No such
device




> -----Mensaje original-----
> De: Patrick Boettcher [mailto:patrick.boettcher at desy.de] 
> Enviado el: lunes, 27 de marzo de 2006 21:52
> Para: Mikel Martin
> CC: linux-dvb at linuxtv.org
> Asunto: RE: [linux-dvb] freecom USB dvb-t -- new 
> vendor/product ID 14aa:022a
> 
> Somehow I the attached firmware was lost. *ahem*
> 
> Try this.
> 
> On Mon, 27 Mar 2006, Mikel Martin wrote:
> 
> > Hi Patrick,
> >
> >  The driver is asking for dvb-usb-wt220u-zl0353-01.fw. 
> Where shuold I 
> > find it?
> >
> >> -----Mensaje original-----
> >> De: Patrick Boettcher [mailto:patrick.boettcher at desy.de]
> >> Enviado el: lunes, 27 de marzo de 2006 20:27
> >> Para: Mikel Martin
> >> CC: linux-dvb at linuxtv.org
> >> Asunto: RE: [linux-dvb] freecom USB dvb-t -- new vendor/product ID 
> >> 14aa:022a
> >>
> >> Hi Mikel,
> >>
> >> Please try the attached firmware and patch (along with 
> latest v4l-dvb 
> >> hg).
> >>
> >> You don't need to load the zl0353-driver, dvb-usb-dtt200u and its 
> >> dependencies is sufficient.
> >>
> >> Please report the result,
> >>
> >> Patrick.
> >>
> >> --
> >>    Mail: patrick.boettcher at desy.de
> >>    WWW:  http://www.wi-bw.tfh-wildau.de/~pboettch/
> >>
> >> On Mon, 27 Mar 2006, Mikel Martin wrote:
> >>
> >>> Hi Patrick,
> >>>
> >>>  Thanks a lot for your interest. I can't do what you ask
> >> yet because I
> >>> don't have the dual boot nor the vmware for linux.
> >>>
> >>>  Playing with the dvb-usb-ids.h to force different 
> firmwares to be 
> >>> downloaded to the stick. I've found the following:
> >>>
> >>>  In windows when I plug the stick it's led blinks for a
> >> while (while
> >>> the Loader is present) and the the led goes on and stops blinking.
> >>> (The Receiver is present now)
> >>>
> >>>  In linux if I force to download the dvb-usb-wt220u-01.fw or 
> >>> dvb-usb-wt220u-02.fw the sticks's led blinks, but if I force to 
> >>> download any other the led doesn't switch on. Perhaps this
> >> information could help.
> >>>
> >>>
> >>>  Apart from this, which is the mecanism used to choose 
> which driver 
> >>> should be used? If both modules are installed, zl10353.ko and the 
> >>> dvb-usb-dtt200u.ko which one would be used?
> >>>
> >>>
> >>> Regards,
> >>>
> >>> Mikel
> >
> 
> Patrick.
> 
> --
>    Mail: patrick.boettcher at desy.de
>    WWW:  http://www.wi-bw.tfh-wildau.de/~pboettch/




More information about the linux-dvb mailing list