I tried the new version of the driver last night with some success The driver loads with the following messages in dmesg: Sep 29 08:13:04 kulfi kernel: [ 16.216298] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 2' in cold state, will try to load a firmware Sep 29 08:13:04 kulfi kernel: [ 16.305374] dvb-usb: downloading firmware from file 'dvb-usb-bluebird-01.fw' Sep 29 08:13:04 kulfi kernel: [ 16.367611] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 2' in cold state, will try to load a firmware Sep 29 08:13:04 kulfi kernel: [ 16.369592] dvb-usb: downloading firmware from file 'dvb-usb-bluebird-01.fw' Sep 29 08:13:04 kulfi kernel: [ 16.431272] usbcore: registered new driver dvb_usb_cxusb Sep 29 08:13:04 kulfi kernel: [ 16.564442] usb 7-1: USB disconnect, address 2 Sep 29 08:13:04 kulfi kernel: [ 16.564545] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. Sep 29 08:13:04 kulfi kernel: [ 16.669246] usb 7-2: USB disconnect, address 3 Sep 29 08:13:04 kulfi kernel: [ 16.669343] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. Sep 29 08:13:04 kulfi kernel: [ 18.267412] usb 7-1: new high speed USB device using ehci_hcd and address 4 Sep 29 08:13:04 kulfi kernel: [ 18.384471] usb 7-1: configuration #1 chosen from 1 choice Sep 29 08:13:04 kulfi kernel: [ 18.384779] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 2' in warm state. Sep 29 08:13:04 kulfi kernel: [ 18.384900] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Sep 29 08:13:04 kulfi kernel: [ 18.395525] DVB: registering new adapter (DViCO FusionHDTV DVB-T Dual Digital 2). Sep 29 08:13:04 kulfi kernel: [ 18.731996] DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)... Sep 29 08:13:04 kulfi kernel: [ 18.732535] input: IR-receiver inside an USB DVB receiver as /class/input/input3 Sep 29 08:13:04 kulfi kernel: [ 18.732624] dvb-usb: schedule remote query interval to 150 msecs. Sep 29 08:13:04 kulfi kernel: [ 18.732680] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 2 successfully initialized and connected. Then I ran scan with the example file for my city: root@kulfi:/var/log# scan /usr/share/doc/dvb-utils/examples/scan/dvb-t/au-canberra scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/au-canberra using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 205625000 1 3 3 3 1 1 0 initial transponder 177500000 1 2 0 3 1 2 0 initial transponder 191625000 1 3 0 3 1 1 0 initial transponder 219500000 1 3 1 3 1 1 0 initial transponder 543500000 1 2 0 3 1 2 0 >>> tune to: 205625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: 205625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE (tuning failed) WARNING: >>> tuning failed!!! >>> tune to: 177500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 0x0807 0x0807: pmt_pid 0x0160 Southern Cross Television -- SC10 Canberra (running) 0x0807 0x0827: pmt_pid 0x06ae Southern Cross Television -- SC10 HD (running) Network Name 'Southern Cross Television ' >>> tune to: 191625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: 191625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE (tuning failed) WARNING: >>> tuning failed!!! >>> tune to: 219500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE Network Name 'WIN Digital' 0x327a 0x0001: pmt_pid 0x0020 WIN Digital -- WIN TV Canberra (running) 0x327a 0x000a: pmt_pid 0x00b0 WIN Digital -- WIN TV HD (running) >>> tune to: 543500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 0x0350 0x0350: pmt_pid 0x0400 SBS -- SBS HD (running) 0x0350 0x0351: pmt_pid 0x0401 SBS -- SBS DIGITAL 1 (running) 0x0350 0x0352: pmt_pid 0x0402 SBS -- SBS DIGITAL 2 (running) 0x0350 0x0353: pmt_pid 0x0408 SBS -- SBS EPG (running) 0x0350 0x035e: pmt_pid 0x0403 SBS -- SBS RADIO 1 (running) 0x0350 0x035f: pmt_pid 0x0404 SBS -- SBS RADIO 2 (running) Network Name 'SBS NETWORK' >>> tune to: 571500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: 571500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE (tuning failed) and at that point the machine had locked up hard. I also noticed that on some occasions it would lock up on the first channel it found as well. Mark Michael Krufky <mkrufky@xxxxxxxxxxx> wrote: >Michael Krufky wrote: >> Michael Krufky wrote: >>> I have written to my contact at DViCO with some questions about this >>> device. While we're waiting for his response, please try the >suggestion >>> above. Please keep in mind that you will need to have the bluebird >>> firmware present in order for this test to work. >> >> I've received confirmation from DViCO that the usb components on the >> DViCO FusionHDTV DVB-T Dual Digital 2 are identical to the usb component >> on the DViCO FusionHDTV DVB-T Dual Digital 1. >> >> The attached patch, applied against v4l-dvb master repository, adds >> support for your device. Please test this and let me know how it goes. >> >> ...or you can just clone the tree located at: >> >> http://linuxtv.org/hg/~mkrufky/cxusb > >Oops.... Slight problem in that last patch... I fixed it in the tree, >and the corrected patch is attached. Let me know how it works. > > cxusb.c | 16 +++++++++++----- > dvb-usb-ids.h | 10 ++++++---- > 2 files changed, 17 insertions(+), 9 deletions(-) > > > _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
