[linux-dvb] AverTV A800 trouble

Martin Habbecke M.Habbecke at gmx.de
Wed Jun 28 21:59:47 CEST 2006


Hi,

I own two AverTV A800 USB boxes and unfortunately have some trouble with one 
of them. If I plug in the first one I get:

------------------------------------
Jun 28 21:51:52 shuttle usb 1-1: new high speed USB device using ehci_hcd and 
address 7
Jun 28 21:51:52 shuttle usb 1-1: configuration #1 chosen from 1 choice
Jun 28 21:51:52 shuttle dvb-usb: found a 'AVerMedia AverTV DVB-T USB 2.0 
(A800)' in warm state.
Jun 28 21:51:52 shuttle dvb-usb: will pass the complete MPEG2 transport stream 
to the software demuxer.
Jun 28 21:51:52 shuttle DVB: registering new adapter (AVerMedia AverTV DVB-T 
USB 2.0 (A800)).
Jun 28 21:51:52 shuttle dib3000: Found a DiBcom 3000P.
Jun 28 21:51:52 shuttle DVB: registering frontend 0 (DiBcom 3000P/M-C 
DVB-T)...
Jun 28 21:51:52 shuttle input: IR-receiver inside an USB DVB receiver 
as /class/input/input2
Jun 28 21:51:52 shuttle dvb-usb: schedule remote query interval to 150 msecs.
Jun 28 21:51:52 shuttle dvb-usb: AVerMedia AverTV DVB-T USB 2.0 (A800) 
successfully initialized and connected.
------------------------------------

The device then works perfectly. However, if I plug in the other one, I get:

------------------------------------
Jun 28 21:52:54 shuttle usb 1-1: new high speed USB device using ehci_hcd and 
address 8
Jun 28 21:52:54 shuttle usb 1-1: configuration #1 chosen from 1 choice
Jun 28 21:52:54 shuttle dvb-usb: found a 'AVerMedia AverTV DVB-T USB 2.0 
(A800)' in cold state, will try to load a firmware
Jun 28 21:52:54 shuttle firmware_loading_store: unexpected value (0)
Jun 28 21:52:54 shuttle dvb-usb: downloading firmware from file 
'dvb-usb-avertv-a800-02.fw'
------------------------------------

I have no idea why the first device is in "warm state" and the other in "cold 
state". The only difference between the two devices I have found is their USB 
ID. The working one has 07ca:a801, the non-working one 07ca:a800. Both boxes 
work under Windows, so it doesn't seem to be a hardware problem. Does anyone 
have an idea?

Thanks,
Martin



More information about the linux-dvb mailing list