Re: [linux-dvb] Nova-T 500 issues - losing one tuner

2008-03-12 Thread Ben Firshman
When I was having the problem, I was running 2.6.22 (vanilla ubuntu),  
so it doesn't appear to be related to kernel version.

The fix posted a few weeks ago does seem to have stopped it for me. I  
said I lost a tuner recently, but I think that may have just been a  
loss in reception.

Ben

On 11 Mar 2008, at 22:37, Luis Cidoncha wrote:

 On Tue, Mar 11, 2008 at 11:10 PM, Nicolas Will [EMAIL PROTECTED]  
 wrote:

 I'm building a kernel from the 2.6.24.2 virgin source on Ubuntu to  
 do
 some
 testing; I'd like to prove that the problem exists in 2.6.24 proper
 before
 screaming kernel bug. But if 2.6.22 works, a bug is looking more  
 and
 more
 likely.



 I'm having the losing one tuner problem on my Nova T-500 too.

 I'm currently running a vanilla 2.6.23.9, without USB_SUSPEND (the
 support for it is in the kernel, but I have it desactivated)

 Luis.

 ___
 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

2008-03-04 Thread Ben Firshman
I am quite disappointed to report that one of my tuners has just died  
this evening. No error messages to speak of.

Ben

On 26 Feb 2008, at 19:18, Philip Pemberton wrote:

 Patrik Hansson wrote:
 Just wanted to say that I´m experiencing the same.
 Using latest rev (the one with patches merged) + unknown remote key  
 patch.
 Ubuntu 7.10

 Also having a lot of prebuffer timeout 10 times i the middle of  
 shows.

 I think I might have a workaround... On Mythbuntu or one of the many  
 Ubuntu
 variants, this seems to work:

 1)  Run:
   lsmod |grep usbcore

 2)  If step 1 produced any output that started with 'usbcore', then  
 usbcore is
 loaded as a module. Perform step 3a. Otherwise, step 3b.

 3a) Create a text file called /etc/modprobe.d/local-dvb (the name is  
 fairly
 irrelevant). Insert one line of text into it:
   options usbcore autosuspend=-1
 Now go to step 4.

 3b) Your kernel has usbcore built in. That means you have to modify  
 the kernel
 command line...
 Edit /boot/grub/menu.lst (you'll need to sudo to do this).  
 Search for
 this line:
 # defoptions=quiet splash
 Amend it to read:
 # defoptions=quiet splash usbcore.autosuspend=-1
 It's meant to be commented out, so leave the hash at the  
 beginning of the
 line alone... Save and exit, then run ...
 sudo update grub
 Ubuntu will regenerate grub.conf, using the new kernel command  
 line. Off
 to step 4 you go!

 If you're using a non-Debian distro (e.g. Fedora), do the same  
 thing but
 edit the 'kernel' line instead. It might read:
 kernel  /boot/vmlinuz-2.6.24-8-generic root=LABEL=/ ro quiet  
 splash
 Change it to:
 kernel  /boot/vmlinuz-2.6.24-8-generic root=LABEL=/ ro quiet  
 splash
 usbcore.autosuspend=-1

 4)  Reboot your PC.

 This is a bit long-winded, but saves a kernel recompile, and a ton  
 of messing
 around recompiling kernels when Ubuntu do another release.

 I'm working on what I consider to be a better fix, which involves  
 using the
 kernel's Quirks function to disable USB suspend just for the DiBcom
 controllers. That is, the kernel won't try and suspend them at all...

 Thanks,
 -- 
 Phil. |  (\_/)  This is Bunny. Copy and  
 paste Bunny
 [EMAIL PROTECTED]   | (='.'=) into your signature to help  
 him gain
 http://www.philpem.me.uk/ | ()_() world domination.

 ___
 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

2008-02-25 Thread Ben Firshman
Which one disables the remote? I don't use the remote, so I could try  
disabling it and see if I get any problems.

Ben

On 25 Feb 2008, at 19:25, Christophe Boyanique wrote:

 Christophe Boyanique a écrit :
 I would just confirm the symptom that Jonas Anden reported on the
 mailing list a few days ago about the Nova-T 500 loosing one tuner.

 Nothing in the logs or dmesg;
 MythTV stuck on L__

 Host:
 Linux 2.6.22-14-generic
 Intel(R) Pentium(R) 4 CPU 3.00GHz

 v4l from 2008/01/27-16:34

 Just for information: I decided to make this test more than 10 days  
 ago:

 - disable EIT on both tuners in MythTV;
 - disable remote (that I do not use anyway)

 for that I added in a /etc/modprobe.d/local file:
 --- cut ---
 options dvb-usb-dib0700 force_lna_activation=1
 options dvb_usb disable_rc_polling=1
 --- cut ---

 The result is that both tuners are still up and working.

 So it may be either the remote or the EIT which produces the bug I  
 suppose.

 Christophe.

 ___
 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

2008-02-03 Thread Ben Firshman
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

On 3 Feb 2008, at 09:39, 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 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

Re: [linux-dvb] Nova-T 500 issues

2008-02-01 Thread 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.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
 
 
 ___
 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


[linux-dvb] Nova-T 500 issues

2008-01-27 Thread 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

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.

Thanks,

Ben

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb