<br><br>
<div><span class="gmail_quote">On 4/4/06, <b class="gmail_sendername">Michael Krufky</b> <<a href="mailto:mkrufky@linuxtv.org">mkrufky@linuxtv.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">David Shay wrote:<br>> I have a DVICO5 Fusion USB gold box and have gotten it up and running<br>> OK. I am running
2.6.16 and using the drivers provided in the<br>> kernel. Sometimes, however, if I run azap on a channel, it gets<br>> FE_LOCK, all is fine, then I ctrl-C to stop azap. If I run azap<br>> again, I will not get FE_LOCK. If I rmmod dvb_usb_cxusb and then
<br>> modprobe it again, it repairs the symptom. I am not getting any<br>> errors in dmesg.<br>><br>> This has happened on two separate systems, as well. Both gentoo, both<br>> 2.6.16. One's a pentium-4 and the other an epia.
<br>><br>> Any other debugging or other information I can provide?<br>David-<br><br>Thank you for writing about this. I added support for the DViCO<br>Bluebird devices, and I am also experiencing the same issue when using
<br>the driver under 2.6.16 ... The device is able to recover when you<br>remove and re-insert the module, or if you disconnect and reconnect the<br>device, but that isn't practical, considering that you are probably<br>
relying on the box to work in order to record HD programs.<br><br>I have spoken to Patrick about this, and he tells me that the same bug<br>exists in other dvb-usb devices, and also flexcop-usb boxes. I don't<br>have a flexcop-usb device to test with, but I do have some ideas as to
<br>how to prevent this from happening on the FusionHDTV boxes.</blockquote>
<div> </div>
<div>Does this occur on other kernels? Would a temporary kernel down-grade resolve?</div><br> </div>