I think we are better of trying to pin the problem down to a point where we can switch it on/off with a change of kernel or dvb code, may I humbly suggest.
Verify if the current tree is stable on 2.6.22.
Verify if it breaks with a newer kernel, then check for changes in the changelog regarding usb.
Collecting debug info about the disconnects is probably very good, let´s hope someone takes pity on us.
I had problems until my recent config, at the same moment it was stable I stopped tinkering and haven´t dared to upgrade anything since.
My bet is that the dibcom stuff does something ugly and that there is changes in the kernel usb code (or even config) that makes the problem reappear.
/Henrik
On Thu, Mar 27, 2008 at 9:05 AM, Nicolas Will <nico@xxxxxxxxxxxx> wrote:
Adding the following lines in your /etc/modprobe.d/options would be a
On Wed, 2008-03-26 at 21:17 +0000, Nicolas Will wrote:
> Well, fine.
>
> What we need here is a developer.
>
> What a developer needs is info, without it, he will not be able to
> help.
>
> I've posted logs, now your turn.
>
good start:
Then post the lines of /var/log/syslog and /var/log/messages around the
options dvb-usb-dib0700 debug=1
options mt2060 debug=1
options dibx000_common debug=1
options dvb_core debug=1
options dvb_core dvbdev_debug=1
options dvb_core frontend_debug=1
options dvb_usb debug=1
options dib3000mc debug=1
disconnect event.
Better post them somewhere on a web page or a pastebin.
Nico
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
_______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
