|
Hi, I am a newbie to TV on linux. I appologise in advance for this rather long mailing. Has anyone suceeded with Avermedia DBV-T USB 2.0 on linux? I have just bought this device, encouraged by the statement on the box "Linux compatible, go to our web site for instructions". I found that these so called instructions merely say "go to http://www.wi-bw.tfh-wildau.de/~pboettch/home/index.php?site=dvb-usb-howto " which, although giving good general instruction, is not specific for the device. I am using Fedora Core 3 with upgraded kernel 2.6.15.4. This kernel has all the modules needed for the device according to the LinuxTV DVB-USB Wiki. I installed the firmware. On booting this kernel with the device plugged into the usb hub the device LED comes on and the relevant part of dmesg is:- ======================================================== usb 3-4.2: new high speed USB device using ehci_hcd and address 5 DEV: registering device: ID = '3-4.2' PM: Adding info for usb:3-4.2 bus usb: add device 3-4.2 bound device '3-4.2' to driver 'usb' DEV: registering device: ID = '3-4.2:1.0' PM: Adding info for usb:3-4.2:1.0 bus usb: add device 3-4.2:1.0 usb: Matched Device 3-4.2:1.0 with Driver dvb_usb_a800 dvb-usb: found a 'AVerMedia AverTV DVB-T USB 2.0 (A800)' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (AVerMedia AverTV DVB-T USB 2.0 (A800)). CLASS: registering class device: ID = 'dvb0.demux0' class_hotplug - name = dvb0.demux0 class_device_create_hotplug called for dvb0.demux0 CLASS: registering class device: ID = 'dvb0.dvr0' class_hotplug - name = dvb0.dvr0 class_device_create_hotplug called for dvb0.dvr0 CLASS: registering class device: ID = 'dvb0.net0' class_hotplug - name = dvb0.net0 class_device_create_hotplug called for dvb0.net0 DEV: registering device: ID = 'i2c-1' PM: Adding info for No Bus:i2c-1 CLASS: registering class device: ID = 'i2c-1' class_hotplug - name = i2c-1 dib3000: Found a DiBcom 3000P. DVB: registering frontend 0 (DiBcom 3000P/M-C DVB-T)... CLASS: registering class device: ID = 'dvb0.frontend0' class_hotplug - name = dvb0.frontend0 class_device_create_hotplug called for dvb0.frontend0 input: device IR-receiver inside an USB DVB receiver is statically allocated, will n ot register Please convert to input_allocate_device() or contact dtor_core@xxxxxxxxxxxxx dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: AVerMedia AverTV DVB-T USB 2.0 (A800) successfully initialized and connected. bound device '3-4.2:1.0' to driver 'dvb_usb_a800' usb: Bound Device 3-4.2:1.0 to Driver dvb_usb_a800 CLASS: registering class device: ID = 'usbdev3.5' class_hotplug - name = usbdev3.5 class_device_create_hotplug called for usbdev3.5 =================================================== This looks promising and as stated /dev/dvb0.demux0, dvb0.frontend0, dvb0.dvr0, dvb0.net0 are set up. At this point I tried to use the dvb-apps scan util but :- ======================================================= # ./dvbscan dvb-t/uk-Bilsdale scanning dvb-t/uk-Bilsdale using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' main:2232: FATAL: failed to open '/dev/dvb/adapter0/frontend0': 2 No such file or directory ======================================================= These /dev/adapterx/ dev files are what dvb-apps expects. Why were they not formed by the dvb_usb_a800 driver but the /dev/dvb0.xxx0 instead? Do you know of any app-software which deals these /dev/dvb0.xxx0 files? I tried ln -s /dev/dvb0.frontend0 /dev/dvb/adapter0/frontend0 ln -s /dev/dvb0.demux0 /dev/dvb/adapter0/demux0 and now:- ======================================================= ./dvbscan dvb-t/uk-Bilsdale scanning dvb-t/uk-Bilsdale using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 474000000 0 2 1 3 0 0 0 >>> tune to: 474000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMI SSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x0000 WARNING: filter timeout pid 0x0010 dumping lists (0 services) Done. ======================================================== Does this tell me anything useful? I then tried altering dvb-apps/utils/scan/scan.c to replacing the adapterx/xxxx calls with dvb0.xxx0 calls but same result. I also tried using dvb-apps's MAKEDEV.sh to create the /dev/adapterx files but to no avail. I don't know where to go from here. Any (relevant) suggestions would be gratefully received. -- Best wishes, Howard (A.H.Gilbert, Thornaby-on-Tees.) |
_______________________________________________ linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
