Hi Mike! Thanks for your quick reply. On Sat, Dec 10, 2005 at 01:57:46AM +0000, mike choy wrote: > Michael Hanke wrote: > >Hi! > > > >I recently bought a 'dnt Euro Stick' DVB-T USB device. To use it with my > >Debian sarge box (currently kernel 2.6.14-2). > >It should be like a WideView/Yakumo/Hama/Typhoon/Yuan Box > >supported by the kernel -- at least according to this list: > > > >http://www.linuxtv.org/wiki/index.php/DVB_USB > > > >I downloaded a firmware file (dvb-usb-dtt200u-01.fw) from here: > > > >http://www.linuxtv.org/downloads/firmware/ > > > >and put it in /usr/lib/hotplug/firmware and renamed it to > >'dvb-usb-wt220u-01.fw' (because the driver was looking for that > >filename). > > > >When I plug the device it seems that the firmware is loaded properly > >(see output below). But there is one strange message: > > > >dvb-usb: recv bulk message failed: -110 > > > >And now for the problem. When I tried to scan for channels I get this > >error message: > > > >xxx@xxxx:~$ scan de-Leipzig > >scanning de-Leipzig > >using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > >main:1885: FATAL: FE_GET_INFO failed: 22 Invalid argument > > > > > >This is the list of the (relevant) loaded modules: > >Module Size Used by > >dvb_usb_dtt200u 12292 0 > >dvb_usb 20616 1 dvb_usb_dtt200u > >dvb_pll 10884 1 dvb_usb > >dvb_ttusb_budget 32356 0 > >dvb_core 88060 2 dvb_usb,dvb_ttusb_budget > >tda1004x 16260 1 dvb_ttusb_budget > >firmware_class 11840 3 dvb_usb,dvb_ttusb_budget,tda1004x > >ves1820 6788 1 dvb_ttusb_budget > >stv0299 12552 1 dvb_ttusb_budget > >tda8083 6724 1 dvb_ttusb_budget > >cx22700 6788 1 dvb_ttusb_budget > >i2c_core 24792 11 > >dvb_usb,i2c_viapro,mt352,dvb_ttusb_budget,tda1004x,ves1820,stv0299,tda8083,cx22700,radeonfb,i2c_algo_bit > > > > > >Could anybody please give me a pointer where the problem is. The last > >few days spending my time with Google were not really successful. Those > >few people that > >I found that had this Problem (with various devices and kernel versions) > >all surrendered. > > > > > >Thanks in advance. > > > > > >Michael > > > > > > > >-- syslog output --- > > > >Dec 9 20:39:36 localhost kernel: usb 5-6: new high speed USB device > >using ehci_hcd and address 2 > >Dec 9 20:39:38 localhost kernel: dvb-usb: found a 'WideView WT-220U > >PenType Receiver (Typhoon/Freecom)' in cold state, will try to load a > >firmware > >Dec 9 20:39:38 localhost kernel: dvb-usb: downloading firmware from > >file 'dvb-usb-wt220u-01.fw' to the 'Cypress FX2' > >Dec 9 20:39:38 localhost kernel: dvb-usb: WideView WT-220U PenType > >Receiver (Typhoon/Freecom) successfully initialized and connected. > >Dec 9 20:39:38 localhost kernel: usbcore: registered new driver > >dvb_usb_dtt200u > >Dec 9 20:39:38 localhost usb.agent[5038]: dvb-usb-dtt200u: loaded > >successfully > >Dec 9 20:39:38 localhost udev[5136]: creating device node > >'/dev/usbdev5.2' > >Dec 9 20:39:39 localhost kernel: usb 5-6: USB disconnect, address 2 > >Dec 9 20:39:39 localhost kernel: dvb-usb: generic DVB-USB module > >successfully deinitialized and disconnected. > >Dec 9 20:39:40 localhost kernel: usb 5-6: new high speed USB device > >using ehci_hcd and address 3 > >Dec 9 20:39:41 localhost kernel: dvb-usb: found a > >'WideView/Yuan/Yakumo/Hama/Typhoon DVB-T USB2.0 (WT-200U)' in warm > >state. > >Dec 9 20:39:41 localhost kernel: dvb-usb: will use the device's > >hardware PID filter (table count: 15). > >Dec 9 20:39:41 localhost kernel: DVB: registering new adapter > >(WideView/Yuan/Yakumo/Hama/Typhoon DVB-T USB2.0 (WT-200U)). > >Dec 9 20:39:41 localhost kernel: DVB: registering frontend 0 (WideView > >USB DVB-T)... > >Dec 9 20:39:41 localhost kernel: dvb-usb: schedule remote query > >interval to 300 msecs. > >Dec 9 20:39:41 localhost kernel: dvb-usb: > >WideView/Yuan/Yakumo/Hama/Typhoon DVB-T USB2.0 (WT-200U) successfully > >initialized and connected. > >Dec 9 20:39:43 localhost kernel: dvb-usb: recv bulk message failed: > >-110 > >Dec 9 20:39:49 localhost udev[5163]: removing device node > >'/dev/usbdev5.2' > >Dec 9 20:39:49 localhost udev[5175]: configured rule in > >'/etc/udev/rules.d/udev.rules[67]' applied, 'event3' becomes 'input/%k' > >Dec 9 20:39:49 localhost udev[5175]: creating device node > >'/dev/input/event3' > >Dec 9 20:39:49 localhost udev[5165]: configured rule in > >'/etc/udev/rules.d/udev.rules[36]' applied, 'dvb0.dvr0' becomes '%c' > >Dec 9 20:39:49 localhost udev[5165]: creating device node > >'/dev/dvb/adapter0/dvr0' > >Dec 9 20:39:49 localhost udev[5174]: configured rule in > >'/etc/udev/rules.d/udev.rules[36]' applied, 'dvb0.frontend0' becomes > >'%c' > >Dec 9 20:39:49 localhost udev[5174]: creating device node > >'/dev/dvb/adapter0/frontend0' > >Dec 9 20:39:49 localhost udev[5164]: configured rule in > >'/etc/udev/rules.d/udev.rules[36]' applied, 'dvb0.demux0' becomes '%c' > >Dec 9 20:39:49 localhost udev[5164]: creating device node > >'/dev/dvb/adapter0/demux0' > >Dec 9 20:39:49 localhost udev[5166]: configured rule in > >'/etc/udev/rules.d/udev.rules[36]' applied, 'dvb0.net0' becomes '%c' > >Dec 9 20:39:49 localhost udev[5166]: creating device node > >'/dev/dvb/adapter0/net0' > >Dec 9 20:39:49 localhost usb.agent[5248]: dvb-usb-dtt200u: already > >loaded > >Dec 9 20:39:49 localhost udev[5302]: creating device node > >'/dev/usbdev5.3' > > > > > >------------------------------------------------------------------------ > > > >_______________________________________________ > > > >linux-dvb@xxxxxxxxxxx > >http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > micheal > you have loaded the wrong firmware > you need dvb-usb-wt220u-01.fw (do not rename it) also check its md5sum, > like so > >md5sum dvb-usb* > 782c9937b3f42e5248584570857c8b7f dvb-usb-wt220u-01.fw > get driver from here http://www.linuxtv.org/downloads/firmware/ its > right at the bottom of the list Well, what can I say... Now I have the right firmware file and double-checked the md5sum. However, the error remains: ## syslog output ## Dec 10 11:19:25 localhost kernel: usb 5-6: new high speed USB device using ehci_hcd and address 4 Dec 10 11:19:26 localhost kernel: dvb-usb: found a 'WideView WT-220U PenType Receiver (Typhoon/Freecom)' in cold state, will try to load a firmware Dec 10 11:19:26 localhost kernel: dvb-usb: downloading firmware from file 'dvb-usb-wt220u-01.fw' to the 'Cypress FX2' Dec 10 11:19:26 localhost kernel: dvb-usb: WideView WT-220U PenType Receiver (Typhoon/Freecom) successfully initialized and connected. Dec 10 11:19:26 localhost kernel: usbcore: registered new driver dvb_usb_dtt200u Dec 10 11:19:27 localhost usb.agent[5422]: dvb-usb-dtt200u: loaded successfully Dec 10 11:19:27 localhost udev[5520]: creating device node '/dev/usbdev5.4' Dec 10 11:19:28 localhost kernel: usb 5-6: USB disconnect, address 4 Dec 10 11:19:28 localhost kernel: dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. Dec 10 11:19:29 localhost kernel: usb 5-6: new high speed USB device using ehci_hcd and address 5 Dec 10 11:19:29 localhost kernel: dvb-usb: found a 'WideView WT-220U PenType Receiver (Typhoon/Freecom)' in warm state. Dec 10 11:19:29 localhost kernel: dvb-usb: will use the device's hardware PID filter (table count: 15). Dec 10 11:19:29 localhost kernel: DVB: registering new adapter (WideView WT-220U PenType Receiver (Typhoon/Freecom)). Dec 10 11:19:29 localhost kernel: DVB: registering frontend 0 (WideView USB DVB-T)... Dec 10 11:19:29 localhost kernel: dvb-usb: schedule remote query interval to 300 msecs. Dec 10 11:19:29 localhost kernel: dvb-usb: WideView WT-220U PenType Receiver (Typhoon/Freecom) successfully initialized and connected. Dec 10 11:19:32 localhost kernel: dvb-usb: recv bulk message failed: -110 A 'scan de-Leipzig' still gives: scanning de-Leipzig using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' main:1885: FATAL: FE_GET_INFO failed: 22 Invalid argument But this time I discovered an additional error message in the dmesg output when the scan attempt fails: ioctl32(scan:5694): Unknown cmd fd(3) cmd(80a86f3d){00} arg(08050260) on /dev/dvb/adapter0/frontend0 What does that mean? There might be one thing that could be a problem. I'm using an AMD64 kernel but the userspace is all 32bit. This was no problem for any part of the system till now, but I don't now whether it is one for the issue. > Also be aware that this card is very sensitive on its aeriel input under > linux, so if you have amplifier on your aeriel > it will saturate the input, the solution I found was to use a passive Y > spiltter to reduce the gain. Thanks for this information. Cheers, Michael -- GPG key: 1024D/3144BE0F Michael Hanke http://apsy.gse.uni-magdeburg.de/hanke ICQ: 48230050 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://www.linuxtv.org/pipermail/linux-dvb/attachments/20051210/ffe1095c/attachment.pgp
