[linux-dvb] DViCO FusionHDTV DVB-T Dual Digital 4

[Andrew Kennan]

> All I know is that people in Melbourne are having trouble -- I havent heard
> from anybody else in AU.  One of my testers has the Dual Digital 1 card, which
> uses an mt352 demod -- this one is working just fine.  (He has it in the same
> box with the Dual Digital 4)
>   
I'm in Perth, Australia and am also unable to tune using this patch.

I don't know if this is relevant but I noticed the following line in the 
output from dmesg:

[17180450.876000] DVB: Unable to find symbol xc3028_attach()

in amongst the other output:

[17179758.992000] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 
4' in warm state.
[17179758.996000] dvb-usb: will pass the complete MPEG2 transport stream 
to the software demuxer.
[17179759.024000] DVB: registering new adapter (DViCO FusionHDTV DVB-T 
Dual Digital 4).
[17179759.356000] DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)...
[17179759.392000] DVB: Unable to find symbol xc3028_attach()
[17179759.392000] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 4 
successfully initialized and connected.
[17179759.396000] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 
4' in warm state.
[17179759.396000] dvb-usb: will pass the complete MPEG2 transport stream 
to the software demuxer.
[17179759.424000] DVB: registering new adapter (DViCO FusionHDTV DVB-T 
Dual Digital 4).
[17179759.716000] DVB: registering frontend 1 (Zarlink ZL10353 DVB-T)...
[17179759.752000] DVB: Unable to find symbol xc3028_attach()
[17179759.756000] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 4 
successfully initialized and connected.
[17179759.756000] usbcore: registered new driver dvb_usb_cxusb

Regards

Andrew