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

2008-03-15 Thread Ivor Hewitt
Patrik Hansson wrote:
 I tried changing to 2.6.22-19 on my ubuntu 7.10 with autosuspend=-1
 but i still lost one tuner.

 Have reverted back to 2.6.22-14-generic now and have disabled the
 remote-pulling...and i just lost a tuner, restarting my cardclient and
 mythbackend got it back.

 Did you have remote-pulling disabled in -19 ?

   
Still ticking along nicely here.

I have options:
options dvb-usb-dib0700 force_lna_activation=1
options dvb-usb disable_rc_polling=1
(since I have no remote)

Is the ubuntu kernel completely generic?

I still see an mt2060 write failed error every now and then (four in the 
past 24 hours), but that doesn't appear to break anything. Do you have 
complete tuner loss as soon as you get a write error?

Ivor.

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


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

2008-03-14 Thread Ivor Hewitt
Still no failures here on 2.6.22.19, had one or two mt2060 I2C write failed 
messages but that didn't stop anything working. Running mythtv with multi-rec.
I've attached the list of usb and i2c named files that changed between 
2.6.22.19 and linux-2.6.23.12. I'll browse through and if I have time I'll 
apply a few of the diffs and see if I can create a breakage.

Cheers,
Ivor
+++ ../linux-2.6.23.12/./arch/cris/arch-v32/drivers/i2c.c   2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./arch/powerpc/platforms/powermac/low_i2c.c  
2007-12-18 21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/i2c/i2c-core.c 2007-12-18 21:55:57.0 
+
+++ ../linux-2.6.23.12/./drivers/i2c/busses/i2c-i801.c  2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/i2c/busses/i2c-piix4.c 2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/i2c/busses/i2c-gpio.c  2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/i2c/busses/i2c-savage4.c   2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/i2c/busses/i2c-mv64xxx.c   2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/i2c/busses/i2c-nforce2.c   2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/i2c/busses/i2c-mpc.c   2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/i2c/busses/i2c-pxa.c   2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/i2c/busses/i2c-acorn.c 2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/i2c/busses/i2c-viapro.c2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/i2c/busses/i2c-powermac.c  2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/i2c/busses/i2c-sis5595.c   2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/i2c/busses/i2c-iop3xx.c2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/i2c/busses/i2c-s3c2410.c   2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/i2c/i2c-dev.c  2007-12-18 21:55:57.0 
+
+++ ../linux-2.6.23.12/./drivers/sbus/char/bbc_i2c.c2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/media/dvb/dvb-usb/dvb-usb-i2c.c
2007-12-18 21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/media/video/cx88/cx88-vp3054-i2c.c 
2007-12-18 21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/media/video/cx88/cx88-vp3054-i2c.h 
2007-12-18 21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/media/video/cx88/cx88-i2c.c2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/media/video/ivtv/ivtv-i2c.c2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/media/video/ir-kbd-i2c.c   2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./include/linux/i2c.h2007-12-18 21:55:57.0 
+
+++ ../linux-2.6.23.12/./include/linux/i2c-id.h 2007-12-18 21:55:57.0 
+
+++ ../linux-2.6.23.12/./sound/usb/usx2y/usbusx2yaudio.c2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./sound/usb/usbmixer.c   2007-12-18 21:55:57.0 
+
+++ ../linux-2.6.23.12/./sound/usb/usbquirks.h  2007-12-18 21:55:57.0 
+
+++ ../linux-2.6.23.12/./sound/usb/usbaudio.c   2007-12-18 21:55:57.0 
+
+++ ../linux-2.6.23.12/./drivers/hid/usbhid/usbkbd.c2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/net/usb/usbnet.c   2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/net/usb/usbnet.h   2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/net/irda/irda-usb.c2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/net/wireless/zd1211rw/zd_usb.c 2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/net/wireless/zd1211rw/zd_usb.h 2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/usb/atm/usbatm.c   2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/usb/mon/usb_mon.h  2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/usb/core/usb.c 2007-12-18 21:55:57.0 
+
+++ ../linux-2.6.23.12/./drivers/usb/core/usb.h 2007-12-18 21:55:57.0 
+
+++ ../linux-2.6.23.12/./drivers/usb/misc/legousbtower.c2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/usb/misc/ldusb.c   2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/usb/misc/usbtest.c 2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/usb/misc/usblcd.c  2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/usb/misc/sisusbvga/sisusb_con.c
2007-12-18 21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/usb/misc/sisusbvga/sisusb.c2007-12-18 
21:55:57.0 +
+++ ../linux-2.6.23.12/./drivers/usb/misc/sisusbvga/sisusb_init.h   
2007-12-18 21:55:57.0 

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

2008-03-13 Thread Ivor Hewitt
On Tue, Mar 11, 2008 at 04:55:24PM +0100, Patrik Hansson wrote:
 Have you applied any patches to the v4l-dvb source before compiling ?
 
No patches applied to v4ldvb or kernel source.

 On 3/11/08, Nicolas Will [EMAIL PROTECTED] wrote:
 What changed between 2.6.22 and 2.6.24? huh... funny, heh?

 So, if 2.6.24 is finger pointed, I'm interested in a solution, as I have
 a planned upgrade to it in about a month's time.

In fact I saw failures against linux-2.6.23.12 I've diffed the two trees and am 
browsing (at leisure) the changes to see if anything leaps out.

Just enabled mythtv multirec too to see if I can put a bit more stress on the 
system, still no failures. When I have time I'll flip back to 2.6.11.19 and see 
how easy/quickly I can get it to fail again.

Cheers,
Ivor.


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


[linux-dvb] [PATCH] allow dvb-usb firmware loading in warm state?

2008-01-21 Thread Ivor Hewitt
Hi,
I was having (still am! :) trouble with my nova-t 500 card and I wanted 
a way to be able try a different firmware... but the current code only 
loads in a cold state... and my mythbackend is pretty inaccessible, so 
I made the attached change. This allows a module parameter of 
force_load_firmware which causes the cold state logic to be used 
when warm. Thought this might be a useful idea, it was handy for me anyway.

Cheers,
Ivor

-- snip --

  /* DIB7070 generic */
diff -r 7564c110491e linux/drivers/media/dvb/dvb-usb/dvb-usb-init.c
--- a/linux/drivers/media/dvb/dvb-usb/dvb-usb-init.cSun Jan 20 
09:13:44 2008 -0200
+++ b/linux/drivers/media/dvb/dvb-usb/dvb-usb-init.cMon Jan 21 
11:55:20 2008 +
@@ -25,6 +25,10 @@ static int dvb_usb_force_pid_filter_usag
  static int dvb_usb_force_pid_filter_usage;
  module_param_named(force_pid_filter_usage, 
dvb_usb_force_pid_filter_usage, int, 0444);
  MODULE_PARM_DESC(force_pid_filter_usage, force all dvb-usb-devices to 
use a PID filter, if any (default: 0).);
+
+int dvb_usb_force_firmware;
+module_param_named(force_load_firmware, dvb_usb_force_firmware, int, 0444);
+MODULE_PARM_DESC(force_load_firmware, force firmware loading even when 
in warm state.);

  static int dvb_usb_adapter_init(struct dvb_usb_device *d)
  {
@@ -230,7 +234,7 @@ int dvb_usb_device_init(struct usb_inter
 return -ENODEV;
 }

-   if (cold) {
+   if (cold||dvb_usb_force_firmware) {
 info(found a '%s' in cold state, will try to load a 
firmware,desc-name);
 ret = dvb_usb_download_firmware(udev,props);
 if (!props-no_reconnect || ret != 0)




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


Re: [linux-dvb] [PATCH] allow dvb-usb firmware loading in warm state?

2008-01-21 Thread Ivor Hewitt
Michael Krufky wrote:
 Doesn't this cause an endless loop?  How does the driver know when to
 stop uploading firmware?

 -Mike
   
(oops hit reply, not reply all, resending)

I don't think so unless I've really missed something obvious (happens).
Isn't that device_init just called once at device startup?

Cheers
Ivor.

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