On 28 Jun, Martin Habbecke wrote: > 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? > I have an AverTV A800 USB box which does only connect in the cold state (with an unpatched driver). I have mentioned this a few days ago in this post: http://www.linuxtv.org/pipermail/linux-dvb/2006-June/011072.html There are two ways to get around, one is to reinitialize all USB-devices by a hotplug script (after each plugging of the device) and the other one is to patch the driver, to force a reconnect (see my other post for details). It may be possible that there are different versions of the AVerTV A800 out there, and I believe my USB box has the same USB ID than your non-working one (07ca:a800). So in my case I am using a patched driver (it is a very simple patch in which only a variable is set to true to enforce an additional reconnect which makes the difference between cold and warm state). I was hoping the maintainers could either integrate this patch officially or clarify that it is not good for all versions the device. In your case, I do not know if this patch may affect your working USB device, since this one does not need an additional reconnect but maybe a second reconnect is not a problem (????) or one could make a more complicated patch taking into account the exact USB ID ? I myself have no real expertise on this and apart of the simple reconnect-issue I have no idea how the driver works in detail. You can try my patch and if it does not work for your first USB-device you can use the manual restart of the hotplug scripts (the command: "/etc/hotplug/usb.rc restart" ). This is not a satisfying solution but it should also work. Greetings, Klaus. _______________________________________________ linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
