Benjamin Gillam schrieb: > I get similar problems on the same card (14aa:0225 - Feb 06 version from > memory?). I cannot tune however, on either frontend. Others have this > card working fine, though. Possibly something to do with our hardware? > [I have no idea at all.] I am using an Athlon XP on a Asus A7V600 > motherboard (in the UK). > > Regards, > > Benjie. > > > d-PUNk wrote: >> Hi! >> >> I am using a Freecom DVB-T usb device which has the usb id 14aa:0225 >> before the driver / firmware is loaded. My system is gentoo linux with >> 2.6.17-gentoo-r8 kernel source. I download the latest snapshot of the >> linux-dvb drivers via mercurial and installed them. I took the firmware >> named dvb-usb-wt220u-fc03.fw. When I modprobe dvb_usb_dtt200u I get: >> >> dvb-usb: found a 'WideView WT-220U PenType Receiver (Typhoon/Freecom)' >> 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 >> (Typhoon/Freecom)). >> DVB: registering frontend 0 (WideView USB DVB-T)... >> input: IR-receiver inside an USB DVB receiver as /class/input/input8 >> dvb-usb: schedule remote query interval to 300 msecs. >> dvb-usb: WideView WT-220U PenType Receiver (Typhoon/Freecom) >> successfully initialized and connected. >> dvb-usb: found a 'WideView WT-220U PenType Receiver (Typhoon/Freecom)' >> 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 >> (Typhoon/Freecom)). >> DVB: registering frontend 1 (WideView USB DVB-T)... >> input: IR-receiver inside an USB DVB receiver as /class/input/input9 >> dvb-usb: schedule remote query interval to 300 msecs. >> dvb-usb: WideView WT-220U PenType Receiver (Typhoon/Freecom) >> successfully initialized and connected. >> usbcore: registered new driver dvb_usb_dtt200u >> dvb-usb: recv bulk message failed: -110 >> >> Now I am quite confused why I find two directories in /dev/dvb named >> adapter0 and adapter1 with >> >> adapter0: >> >> crw-rw---- 1 root video 212, 4 2. Okt 16:50 demux0 >> crw-rw---- 1 root video 212, 5 2. Okt 16:50 dvr0 >> crw-rw---- 1 root video 212, 3 2. Okt 16:50 frontend0 >> crw-rw---- 1 root video 212, 7 2. Okt 16:50 net0 >> >> adapter1 >> >> crw-rw---- 1 root video 212, 68 2. Okt 16:50 demux0 >> crw-rw---- 1 root video 212, 69 2. Okt 16:50 dvr0 >> crw-rw---- 1 root video 212, 67 2. Okt 16:50 frontend0 >> crw-rw---- 1 root video 212, 71 2. Okt 16:50 net0 >> >> >> I can dvbscan on both adapters with correct behaviour (but not at the >> same time) and vlc shows tv when using the generated channels.conf. >> >> I would like to use vdr for recording but this gives me a lot of errors >> (adapter1/demux0: too many open files ... and more). >> >> Can anyone tell me why I got to devices? dmesg looks to me like the >> firmware loads twice. Also two ir-receiver are registered and the >> class/input/inputX increases every time I unload and load the >> dvb_usb_dtt200u. >> I just installed the linuxtv drivers on my notebook which is a Intel Celeron and the original host is an AMD Duron but it's all the same. Two devices. But as I said I am able to tune. May it has anything to do with your signal quality? _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
