Nova-T 500 issues - losing one tuner
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
I have a hunch about this problem...
I had this problem (I tink 3 times last weekend) after initially updating my hg tree and recompiling the modules. I then turned on full debugging for the dib0700 module in order to try to see what happens when it goes wrong, but with full debugging on I haven't been able to reproduce the problem. I ran with full debugging on from monday to saturday and *really* tried to make it go away. I tried starting all tuners at once (ie scheduling three programs with the same start time), I tried running long recordings, I tried running plenty of retuning, and I tried doing it "my normal way" of a few recordings a day. Nothing made the tuner die.
So yesterday, I finally gave up in trying to cause the problem. I turned debugging back off, and this morning one of the tuners is dead again (MythTV stopping at "L__" instead of proceeding to "LMS".)
The *ONLY* change I have made is changing the debugging setting.
This, in combination with the fact that some people see it and some don't, leads me to believe that this is timer-induced. Something can't keep up. Adding debugging makes the operations slightly slower (the module needs to do additional IO to speak to syslogd), and this delay seems to be enough to keep it operational.
I don't think this has anything to do with the remote since I have the RC feature disabled (I'm using an M$ MCE remote instead).
I set it up with full debugging (options dvb_usb_0700 debug=15). This will cause a whole bunch of logging in the system logs, but appears to keep the tuner alive. I have now changed the debug setting to 1 (only 'info' type messages) to see if that also keeps the tuner alive.
My system has a 3.3 Ghz Celeron processor. Shaun, Ben, Nicolas -- what kind of systems are you running? If my hunch is correct, I'd expect Shaun and Ben to have faster processors than Nicolas since they are seeing this issue and Nicolas isn't.
// J
Quoted 93 lines · Shaun
Quoted 77 lines · On Friday 01 February 2008 21:43:51 Nicolas Will wrote:
Quoted 30 lines · Ben Firshman
Feb 1 20:52:04 mythtv kernel: [ 11.072000] dvb-usb: found a'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a
firmware Feb 1 20:52:04 mythtv kernel: [ 11.132000] dvb-usb:
downloading firmware from file 'dvb-usb-dib0700-1.10.fw'
...Feb 1 20:52:04 mythtv kernel: [ 11.844000] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. Feb 1 20:52:04 mythtv kernel: [ 11.844000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Feb 1 20:52:04 mythtv kernel: [ 11.844000] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) Feb 1 20:52:04 mythtv kernel: [ 11.956000] DVB: registering frontend 1 (DiBcom 3000MC/P)... ... Feb 1 20:52:04 mythtv kernel: [ 12.500000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Feb 1 20:52:04 mythtv kernel: [ 12.500000] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) Feb 1 20:52:04 mythtv kernel: [ 12.508000] DVB: registering frontend 2 (DiBcom 3000MC/P)... Feb 1 20:52:04 mythtv kernel: [ 13.068000] input: IR-receiver inside an USB DVB receiver as /class/input/input2 Feb 1 20:52:04 mythtv kernel: [ 13.068000] dvb-usb: schedule remote query interval to 150 msecs. Feb 1 20:52:04 mythtv kernel: [ 13.068000] dvb-usb: Hauppauge Nova-T500 Dual DVB-T successfully initialized and connected.
Got the tree from the day of your message, and I'm still having problems. I'm not the only one either:
Quoted 36 lines
http://www.linuxtv.org/pipermail/linux-dvb/2008-January/022629.html
Thanks
Ben
Quoted 29 lines · Nicolas Will
Quoted 4 lines · Ben Firshman
I am using the (almost) latest SVN version of mythtv. I am using the v4l-dvb sources from a couple of days back. I have followed and used the patches that were on (are they in the repos now?):
Quoted 8 lines
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500
After a short while, one of the tuners dies. I get a "(
L__) Partial Lock" message from mythtv. If it's any help, I also get messages like:DVB: frontend 0 frequency limits undefined - fix the driver
In syslog, but that's even when it's working fine.
Weird issue that I never encountered since I started using the card in August...
Get a brand new tree, there have been a lot of changes very recently, merge of old patches and new fixes too.
Make sure that you have the right firmware too.
Then do a cold reboot, going through a power down, then check in the messages that the card was found in a cold state before a firmware upload.
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#Firmware
Nico
Ben,
I'm at loss for an explanation. I'm just not experiencing your problem.
People with a better brain than mine will need to jump in.
Have you tried turning debugging on for the modules, and get a more verbose log from mythbackend ?
Quoted 7 lines
Nico
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvbHi,
I have been experiencing this problem for a few months now. I think it is related to the use of the remote control. I have written a workaround application for Ubuntu Linux that scans for a mt2060 error in the dmesg log. If found it will restart mythtv-backend. This seems to mitigate tha problem.
Quoted 8 lines
I can't wait for this issue to be fixed.
Shaun
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Hi People,
Jonas I like your never give up attitude.
I am running on a 3Ghz P4. At the moment I am running with a very slightly modified driver. I have my remote plugged in and I sometimes get hundreds of messages like the one below:
Jan 23 22:01:00 media-desktop kernel: [ 1062.522880] dib0700: Unknown remote
controller key : 0 20
I have included a line in linux/drivers/media/dvb/dvb-usb/dib0700_devices.c that eats the unknown controller key and prevents the message repeating, as was suggested by Jonas.
Quoted 1 line
From my mythwatcher logs:
[27-1-08 17:02:21] --- Started ---
[27-1-08 19:51:02] --- Started ---
[27-1-08 23:50:20] --- Started ---
[29-1-08 05:41:07] ERROR: Disconnect Detected. [29-1-08 05:41:07] ACTION: Attempting mythtv-backend restart. [29-1-08 19:36:37] ERROR: Disconnect Detected. [29-1-08 19:36:37] ACTION: Attempting mythtv-backend restart. [30-1-08 04:55:17] ERROR: Disconnect Detected. [30-1-08 04:55:17] ACTION: Attempting mythtv-backend restart. [30-1-08 05:00:16] ERROR: Disconnect Detected. [30-1-08 05:00:16] ACTION: Attempting mythtv-backend restart. [1-2-08 06:24:17] ERROR: Disconnect Detected. [1-2-08 06:24:17] ACTION: Attempting mythtv-backend restart. [1-2-08 20:18:48] ERROR: Disconnect Detected. [1-2-08 20:18:48] ACTION: Attempting mythtv-backend restart. [2-2-08 12:24:58] --- Started ---
I have been using the modified driver since [2-2-08 12:24:58]. I have been up for 24 hours with no disconnect. I will let you know how it goes. If I do get a disconnect, I will turn on debugging and see how that goes.
Cheers,
Shaun
Quoted 146 lines · On Sunday 03 February 2008 09:39:01 Jonas Anden wrote:
I have a hunch about this problem...
I had this problem (I tink 3 times last weekend) after initially updating my hg tree and recompiling the modules. I then turned on full debugging for the dib0700 module in order to try to see what happens when it goes wrong, but with full debugging on I haven't been able to reproduce the problem. I ran with full debugging on from monday to saturday and *really* tried to make it go away. I tried starting all tuners at once (ie scheduling three programs with the same start time), I tried running long recordings, I tried running plenty of retuning, and I tried doing it "my normal way" of a few recordings a day. Nothing made the tuner die.
So yesterday, I finally gave up in trying to cause the problem. I turned debugging back off, and this morning one of the tuners is dead again (MythTV stopping at "
L__" instead of proceeding to "LMS".)The *ONLY* change I have made is changing the debugging setting.
This, in combination with the fact that some people see it and some don't, leads me to believe that this is timer-induced. Something can't keep up. Adding debugging makes the operations slightly slower (the module needs to do additional IO to speak to syslogd), and this delay seems to be enough to keep it operational.
I don't think this has anything to do with the remote since I have the RC feature disabled (I'm using an M$ MCE remote instead).
I set it up with full debugging (options
dvb_usb_0700debug=15). This will cause a whole bunch of logging in the system logs, but appears to keep the tuner alive. I have now changed the debug setting to 1 (only 'info' type messages) to see if that also keeps the tuner alive.My system has a 3.3 Ghz Celeron processor. Shaun, Ben, Nicolas -- what kind of systems are you running? If my hunch is correct, I'd expect Shaun and Ben to have faster processors than Nicolas since they are seeing this issue and Nicolas isn't.
// J
Quoted 96 lines · Shaun
Quoted 79 lines · On Friday 01 February 2008 21:43:51 Nicolas Will wrote:
Quoted 30 lines · Ben Firshman
Feb 1 20:52:04 mythtv kernel: [ 11.072000] dvb-usb: found a'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a
firmware Feb 1 20:52:04 mythtv kernel: [ 11.132000] dvb-usb:
downloading firmware from file 'dvb-usb-dib0700-1.10.fw'
...Feb 1 20:52:04 mythtv kernel: [ 11.844000] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. Feb 1 20:52:04 mythtv kernel: [ 11.844000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Feb 1 20:52:04 mythtv kernel: [ 11.844000] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) Feb 1 20:52:04 mythtv kernel: [ 11.956000] DVB: registering frontend 1 (DiBcom 3000MC/P)... ... Feb 1 20:52:04 mythtv kernel: [ 12.500000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Feb 1 20:52:04 mythtv kernel: [ 12.500000] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) Feb 1 20:52:04 mythtv kernel: [ 12.508000] DVB: registering frontend 2 (DiBcom 3000MC/P)... Feb 1 20:52:04 mythtv kernel: [ 13.068000] input: IR-receiver inside an USB DVB receiver as /class/input/input2 Feb 1 20:52:04 mythtv kernel: [ 13.068000] dvb-usb: schedule remote query interval to 150 msecs. Feb 1 20:52:04 mythtv kernel: [ 13.068000] dvb-usb: HauppaugeNova-T 500 Dual DVB-T successfully initialized and connected.
Got the tree from the day of your message, and I'm still having problems. I'm not the only one either:
Quoted 38 lines
http://www.linuxtv.org/pipermail/linux-dvb/2008-January/022629.html
Thanks
Ben
Quoted 31 lines · Nicolas Will
Quoted 6 lines · Ben Firshman
I am using the (almost) latest SVN version of mythtv. I am using the v4l-dvb sources from a couple of days back. I have followed and used the patches that were on (are they in the repos now?):
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500
Quoted 7 lines
After a short while, one of the tuners dies. I get a "(
L__) Partial Lock" message from mythtv. If it's any help, I also get messages like:DVB: frontend 0 frequency limits undefined - fix the driver
In syslog, but that's even when it's working fine.
Weird issue that I never encountered since I started using the card in August...
Get a brand new tree, there have been a lot of changes very recently, merge of old patches and new fixes too.
Make sure that you have the right firmware too.
Then do a cold reboot, going through a power down, then check in the messages that the card was found in a cold state before a firmware upload.
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#Firmwa
reNico
Ben,
I'm at loss for an explanation. I'm just not experiencing your problem.
People with a better brain than mine will need to jump in.
Have you tried turning debugging on for the modules, and get a more verbose log from mythbackend ?
Quoted 7 lines
Nico
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvbHi,
I have been experiencing this problem for a few months now. I think it is related to the use of the remote control. I have written a workaround application for Ubuntu Linux that scans for a mt2060 error in the dmesg log. If found it will restart mythtv-backend. This seems to mitigate tha problem.
Quoted 8 lines
I can't wait for this issue to be fixed.
Shaun
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 4 lines
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 11 lines · Shaun
Hi People,
Jonas I like your never give up attitude.
I am running on a 3Ghz P4. At the moment I am running with a very slightly
modified driver. I have my remote plugged in and I sometimes get hundreds of
messages like the one below:Jan 23 22:01:00 media-desktop kernel: [ 1062.522880] dib0700: Unknown
Quoted 8 lines
remote
controller key : 0 20I have included a line in
linux/drivers/media/dvb/dvb-usb/dib0700_devices.cthat eats the unknown controller key and prevents the message repeating, as
was suggested by Jonas.
There is a patch on the wiki for this, and I'm using it.
Related?
Nico
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Hi,
Quoted 5 lines
Quoted 5 lines
I have included a line in
linux/drivers/media/dvb/dvb-usb/dib0700_devices.cthat eats the unknown controller key and prevents the message repeating, as
was suggested by Jonas.
Yes, the change I was writing about is on the wiki.
Shaun
Quoted 25 lines · On Sunday 03 February 2008 21:38:55 Nicolas Will wrote:
Quoted 11 lines · Shaun
Hi People,
Jonas I like your never give up attitude.
I am running on a 3Ghz P4. At the moment I am running with a very slightly
modified driver. I have my remote plugged in and I sometimes get hundreds of
messages like the one below:Jan 23 22:01:00 media-desktop kernel: [ 1062.522880] dib0700: UnknownQuoted 8 lines
remote
controller key : 0 20I have included a line in
linux/drivers/media/dvb/dvb-usb/dib0700_devices.cthat eats the unknown controller key and prevents the message repeating, as
was suggested by Jonas.There is a patch on the wiki for this, and I'm using it.
Related?
Quoted 7 lines
Nico
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
I'm running a 2.66ghz Pentium D. I don't use the remote. It seems to be pretty sporadic - it's been working for a couple of days now.
Ben
Quoted 166 lines · Jonas Anden
I have a hunch about this problem...
I had this problem (I tink 3 times last weekend) after initially updating my hg tree and recompiling the modules. I then turned on full debugging for the dib0700 module in order to try to see what happens when it goes wrong, but with full debugging on I haven't been able to reproduce the problem. I ran with full debugging on from monday to saturday and *really* tried to make it go away. I tried starting all tuners at once (ie scheduling three programs with the same start time),
I tried running long recordings, I tried running plenty of retuning, and
I tried doing it "my normal way" of a few recordings a day. Nothing made
the tuner die.So yesterday, I finally gave up in trying to cause the problem. I turned
debugging back off, and this morning one of the tuners is dead again (MythTV stopping at "L__" instead of proceeding to "LMS".)The *ONLY* change I have made is changing the debugging setting.
This, in combination with the fact that some people see it and some don't, leads me to believe that this is timer-induced. Something can't keep up. Adding debugging makes the operations slightly slower (the module needs to do additional IO to speak to syslogd), and this delay seems to be enough to keep it operational.
I don't think this has anything to do with the remote since I have the RC feature disabled (I'm using an M$ MCE remote instead).
I set it up with full debugging (options
dvb_usb_0700debug=15). This will cause a whole bunch of logging in the system logs, but appears to keep the tuner alive. I have now changed the debug setting to 1 (only 'info' type messages) to see if that also keeps the tuner alive.My system has a 3.3 Ghz Celeron processor. Shaun, Ben, Nicolas -- what kind of systems are you running? If my hunch is correct, I'd expect Shaun and Ben to have faster processors than Nicolas since they are seeing this issue and Nicolas isn't.
// J
Quoted 111 lines · Shaun
Quoted 92 lines · On Friday 01 February 2008 21:43:51 Nicolas Will wrote:
Quoted 37 lines · Ben Firshman
Feb 1 20:52:04 mythtv kernel: [ 11.072000] dvb-usb: found a'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a
firmware Feb 1 20:52:04 mythtv kernel: [ 11.132000] dvb-usb:
downloading firmware from file 'dvb-usb-dib0700-1.10.fw'
...Feb 1 20:52:04 mythtv kernel: [ 11.844000] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. Feb 1 20:52:04 mythtv kernel: [ 11.844000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Feb 1 20:52:04 mythtv kernel: [ 11.844000] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) Feb 1 20:52:04 mythtv kernel: [ 11.956000] DVB: registering frontend 1 (DiBcom 3000MC/P)... ... Feb 1 20:52:04 mythtv kernel: [ 12.500000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Feb 1 20:52:04 mythtv kernel: [ 12.500000] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T) Feb 1 20:52:04 mythtv kernel: [ 12.508000] DVB: registering frontend 2 (DiBcom 3000MC/P)... Feb 1 20:52:04 mythtv kernel: [ 13.068000] input: IR-receiver inside an USB DVB receiver as /class/input/input2 Feb 1 20:52:04 mythtv kernel: [ 13.068000] dvb-usb: schedule remote query interval to 150 msecs. Feb 1 20:52:04 mythtv kernel: [ 13.068000] dvb-usb: HauppaugeNova-T
500 Dual DVB-T successfully initialized and connected.Got the tree from the day of your message, and I'm still having problems. I'm not the only one either:
Quoted 43 lines
http://www.linuxtv.org/pipermail/linux-dvb/2008-January/022629.html
Thanks
Ben
Quoted 36 lines · Nicolas Will
Quoted 8 lines · Ben Firshman
I am using the (almost) latest SVN version of mythtv. I am using the
v4l-dvb sources from a couple of days back. I have followed and used
the patches that were on (are they in the repos now?):http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500
Quoted 8 lines
After a short while, one of the tuners dies. I get a "(
L__) Partial
Lock" message from mythtv. If it's any help, I also get messages like:DVB: frontend 0 frequency limits undefined - fix the driver
In syslog, but that's even when it's working fine.
Weird issue that I never encountered since I started using the card in
August...Get a brand new tree, there have been a lot of changes very recently,
merge of old patches and new fixes too.Make sure that you have the right firmware too.
Then do a cold reboot, going through a power down, then check in the
messages that the card was found in a cold state before a firmware upload.http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#Firmware
Nico
Ben,
I'm at loss for an explanation. I'm just not experiencing your problem.
People with a better brain than mine will need to jump in.
Have you tried turning debugging on for the modules, and get a more verbose log from mythbackend ?
Quoted 7 lines
Nico
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvbHi,
I have been experiencing this problem for a few months now. I think it is
related to the use of the remote control. I have written a workaround application for Ubuntu Linux that scans for a mt2060 error in the dmesg log.
If found it will restart mythtv-backend. This seems to mitigate tha problem.Quoted 8 lines
I can't wait for this issue to be fixed.
Shaun
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 4 lines
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 5 lines · Jonas Anden
My system has a 3.3 Ghz Celeron processor. Shaun, Ben, Nicolas -- what kind of systems are you running? If my hunch is correct, I'd expect Shaun and Ben to have faster processors than Nicolas since they are seeing this issue and Nicolas isn't.
I have a fast Core 2 Duo, 2.66 GHz, tons of cache, 64-bit OS.
Nico
http://www.youplala.net/linux/home-theater-pc
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
PATCH 1/1 Nova-T 500 issues - losing one tuner
In reply to Jonas AndenHi all,
Quoted 1 line
I have a hunch about this problem...
...
Quoted 4 lines
This, ... leads me to believe that this is timer-induced. Something can't keep up. Adding debugging makes the operations slightly slower (the module needs to do additional IO to speak to syslogd), and this delay seems to be enough to keep it operational.
Attached is an extremely simple patch which seems to resolve the issue for me. Before turning streaming on/off, I have inserted a tiny delay or 10 ms-
Just using 'debug=1' wasn't enough to keep tuner 2 from dying. I set it up yesterday morning with debug=1, and when I got back home in the evening the second tuner was dead again. I then made the attached patch and the system has been stable since then (~24 hrs).
I also made a slight change by removing a "| 0x00" from the code. It performs absolutely nothing (and is probably removed by the compiler in optimization) but confuse when reading the code, imho... Patrick, if you really want it there I can recreate the patch with the or statement back ;)
Feel free to try it out.
// J
linux/drivers/media/dvb/dvb-usb/dib0700_core.c +2 -1
@@ -243,7 +243,7 @@ int dib0700_streaming_ctrl(struct dvb_usu8 b[4 ]; b[0 ] =REQUEST_ENABLE_VIDEO ; - b[1 ] = (onoff <<4 ) |0x00 ;/* this bit gives a kind of command, rather than enabling something or not */ + b[1 ] = (onoff <<4 );/* this bit gives a kind of command, rather than enabling something or not */ b[2 ] = (0x01 <<4 );/* Master mode */ b[3 ] =0x00 ;
@@ -256,6 +256,7 @@ int dib0700_streaming_ctrl(struct dvb_us b[2 ] |= st->channel_state; +msleep (10 );deb_info ("data for streaming: %x %x\n" ,b[1 ],b[2 ]);return dib0700_ctrl_wr (adap->dev, b,4 );
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Hmm... typical, isn't it? Just about ten minutes after I've sent out the patch, the second tuner died again. It appears this is *not* enough to fix the issue. Please discard the previous mail.
// J
Quoted 24 lines · Jonas Anden
Hi all,
Quoted 1 line
I have a hunch about this problem...
...
Quoted 4 lines
This, ... leads me to believe that this is timer-induced. Something can't keep up. Adding debugging makes the operations slightly slower (the module needs to do additional IO to speak to syslogd), and this delay seems to be enough to keep it operational.
Attached is an extremely simple patch which seems to resolve the issue for me. Before turning streaming on/off, I have inserted a tiny delay or 10 ms-
Just using 'debug=1' wasn't enough to keep tuner 2 from dying. I set it up yesterday morning with debug=1, and when I got back home in the evening the second tuner was dead again. I then made the attached patch and the system has been stable since then (~24 hrs).
I also made a slight change by removing a "|
0x00" from the code. It performs absolutely nothing (and is probably removed by the compiler in optimization) but confuse when reading the code, imho... Patrick, if you really want it there I can recreate the patch with the or statement back ;)
Quoted 7 lines
Feel free to try it out.
// J
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb