[linux-dvb] Issue with Dvico Nano USB DVB-T

[Luke]

Hi,

I'm having an issue getting the Dvico Nano2 DVB-T USB stick to work under 
Mythbuntu 7.10 and hoping someone can give me some pointers.

In the dmesg output, I keep getting this:

[  576.541492] dvb-usb: found a 'DViCO FusionHDTV DVB-T NANO2 w/o firmware' in 
warm state.
[  576.725695] dvb-usb: will pass the complete MPEG2 transport streamto the 
software demuxer.
[  576.732111] DVB: registering new adapter (DViCO FusionHDTV DVB-T NANO2 w/o 
firmware)
[  576.827488] DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)...
[  576.827918] xc2028 0-0061: creating new instance
[  576.827926] xc2028 0-0061: type set to XCeive xc2028/xc3028 tuner
[  576.831676] input: IR-receiver inside an USB DVB receiver as 
/devices/pci0000:00/0000:00:11.0/0000:02:02.0/usb1/1-1/input/input8
[  576.856412] dvb-usb: schedule remote query interval to 100 msecs.
[  577.072740] dvb-usb: DViCO FusionHDTV DVB-T NANO2 w/o firmware successfully 
initialized and connected.

I'm a bit concerned about the "w/o firmware" bit above.

I have the following firmware files in /lib/firmware...
xc3028-dvico-au-01.fw
xc3028-v27.fw
dvb-usb-bluebird-01.fw
dvb-usb-bluebird-02.fw
...which I've downloaded based on various posts I've found.

When trying to run a scan I constantly get "tuning failed!!!"...

# scan /usr/share/doc/dvb-utils/examples/scan/dvb-t/au-sydney_north_shore
scanning /usr/share/doc/dvb-utils/examples/scan/dvb-t/au-sydney_north_shore
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 226500000 1 3 9 3 1 1 0
initial transponder 177500000 1 2 9 3 1 2 0
initial transponder 191625000 1 3 9 3 1 1 0
initial transponder 219500000 1 3 9 3 1 1 0
initial transponder 571500000 1 2 9 3 1 2 0
initial transponder 578500000 1 2 9 3 1 2 0
>>> tune to: 
226500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE
WARNING: >>> tuning failed!!!

Any ideas? I'm using kernel version 2.6.27-7-generic. 

One thing to note is that I am running this on a Guest OS under VMware Server 
2 (with the USB passed through) - so that might be the reason its coming up in 
a warm state.

Any help would be much appreciated.

Thanks,

Luke