Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Hi People, I am writing to inform you of a simple tool I have written to help with this tuner issue. The tool I have made will monitor dmesg output and reset the MythTV Backend if it detects a mt2060 errors. It is not a fix, but a workaround. I have written it for Ubuntu/Debian based systems. I have included the GPL source, feel free to modify as needed. I have it installed on a friend and my Ubuntu based boxes for the last few months and all seems OK. To help with debugging issues, a log is written to: /var/log/mythwatch.log Example output: [24-2-08 19:51:34] --- Started Ver: 0.2.3 --- [27-2-08 07:33:52] ERROR: Disconnect Detected. [27-2-08 07:33:52] ACTION: Attempting mythtv-backend restart. [28-2-08 05:47:20] ERROR: Disconnect Detected. [28-2-08 05:47:20] ACTION: Attempting mythtv-backend restart. [28-2-08 16:51:28] ERROR: Disconnect Detected. [28-2-08 16:51:28] ACTION: Attempting mythtv-backend restart. Note: It is not perfect in that sometimes I loose a tuner without a mt2060 error (very seldom). I am working on the idea of scanning for PAT errors in the MythTV backend log. There seems to be a connection with loosing a tuner and PAT errors. Download URL: http://www.bluboy.f2s.com/develop/MythWatch.tar.gz The tool allows you to record your shows at almost 100% reliability, but with the chance that a reset could lose a few seconds of a recording. This will happen if a reset happends while a show is being recorded. Cheers Shaun PS: For each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-T not recognized (under XP) after trying to have it working under mandriva
Hi, The firmware should be loaded each time the PC is cold booted. Try turning off the machine (power down) for a minute or so and then start it up again. This works for the Nova 500 DVB-T card. Cheers Shaun On Wednesday 13 February 2008 17:33:14 paul fredéric wrote: Hello, After trying to have it working under Mandriva 2008, it is not anymore recognized (a in XP). So I guess i have erased some data for identification. Is there any way to restore the identification data (firmware ?) on a DVB-T ? All the best ___ __ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] uk-Sudbury dvb-t tuning data file question.
Hi Steve, I found that the best method is to use mythtv to tune, no special files required. Just use mythtv-setup and it should work. Id did for me and I am in Kent using a Nova 500 DVB-T. Cheers Shaun On Tuesday 05 February 2008 10:36:17 [EMAIL PROTECTED] wrote: Hello, Apologies if this is the wrong list to ask. Perhaps you could answer a few questions for me? Sudbury, in England, is one of the sites with two DVB-T transmitters, Sudbury and SudburyB, main transmitter Tacolneston. On my Mythtv box I have found /usr/share/doc/dvb-utils/examples/scan/dvb-t/uk-SudburyB but there is no file for Sudbury. Now according to the www.ukfree.tv site Sudbury has six muxes, SudburyB has only one for ITV. I suspect I am missing something here, why is there only one frequency file for Sudbury and why is called SudburyB? Should there be two files, as for Dover for example, uk-Sudbury with six muxes and uk_SudburyB with one? I assume MythTv does not use these files during tuning? Regards, Steve Goodey ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Hi, 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. Yes, the change I was writing about is on the wiki. Shaun On Sunday 03 February 2008 21:38:55 Nicolas Will wrote: On Sun, 2008-02-03 at 11:37 +, Shaun wrote: 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. There is a patch on the wiki for this, and I'm using it. Related? Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
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. 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 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_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 On Sat, 2008-02-02 at 10:20 +, Shaun wrote: On Friday 01 February 2008 21:43:51 Nicolas Will wrote: On Fri, 2008-02-01 at 21:07 +, Ben Firshman wrote: 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.50] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Feb 1 20:52:04 mythtv kernel: [ 12.50] 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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
On Friday 01 February 2008 21:43:51 Nicolas Will wrote: On Fri, 2008-02-01 at 21:07 +, Ben Firshman wrote: 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.50] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Feb 1 20:52:04 mythtv kernel: [ 12.50] 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-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: http://www.linuxtv.org/pipermail/linux-dvb/2008-January/022629.html Thanks Ben Nicolas Will wrote: On Sun, 2008-01-27 at 14:30 +, Ben Firshman wrote: 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 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 ? Nico ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Hi, 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. I can't wait for this issue to be fixed. Shaun ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
