[linux-dvb] DVICO NANO Australia

[Collier Family]

Thanks for the fast response - yes it does work in windows.


----- Original Message ----- 
From: "Michael Krufky" <mkrufky at linuxtv.org>
To: "Collier Family" <judithc at bigpond.net.au>
Cc: <linux-dvb at linuxtv.org>
Sent: Thursday, November 08, 2007 2:58 PM
Subject: Re: [linux-dvb] DVICO NANO Australia


> Michael Krufky wrote:
>> Collier Family wrote:
>>> I have a  DVICO NANO but I am having the same troubles others had in 
>>> June. It appears it is not being recognised as being cold.
>>>
>>> I have followed the instructions at 
>>> http://fremnet.net/article/228/dvico-fusionhdtv-dual-digital-4-under-linux 
>>> and all went well except the frontend not set. dmesg follows
>>>
>>> usb 5-8: new high speed USB device using ehci_hcd and address 9
>>> usb 5-8: configuration #1 chosen from 1 choice
>>> dvb-usb: found a 'DViCO FusionHDTV DVB-T NANO2' in warm state.
>>> dvb-usb: bulk message failed: -22 (2/0)
>>> dvb-usb: will pass the complete MPEG2 transport stream to the software 
>>> demuxer.
>>> DVB: registering new adapter (DViCO FusionHDTV DVB-T NANO2)
>>> dvb-usb: bulk message failed: -110 (1/0)
>>> dvb-usb: bulk message failed: -110 (3/0)
>>> dvb-usb: bulk message failed: -110 (3/0)
>>> dvb-usb: bulk message failed: -110 (5/0)
>>> dvb-usb: no frontend was attached by 'DViCO FusionHDTV DVB-T NANO2'
>>> dvb-usb: DViCO FusionHDTV DVB-T NANO2 successfully initialized and 
>>> connected.
>>>
>>> Is there any other information that may help I am running vanilla 
>>> 2.6.23.1 kernel on Scientific linux 5.0
>>>
>>> Thanks a lot for the work so far.
>>
>> The DVB-T NANO2 does not require the bluebird firmware -- the fx2 boots 
>> it from the eeprom.  So, the device does not have a "cold" state.  The 
>> only firmware that you need for it is the xc3028 firmware that was used 
>> in Markus' xc3028 kernel driver.
>>
>> However, there is alternate firmware required for the xc3028 for use in 
>> Australia.  I assume that you already have that.
>
> Sorry, I forgot to add the "helpful advice" ;-)
>
> ...It looks like the driver is having trouble accessing the zl10353.  Can 
> you check to make sure the device works in windows?
>
> -Mike