Re: [linux-dvb] Nova-T 500 issues - losing one tuner
On Sat, Mar 15, 2008 at 10:42 PM, Patrik Hansson [EMAIL PROTECTED] wrote: On Sat, Mar 15, 2008 at 8:42 PM, Ivor Hewitt [EMAIL PROTECTED] wrote: 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. The only error in my log the lat time i lost a tuner was: mt2060 I2C read failed So not even a write failed. During the night i had another read failed, but this time both tuners stayed alive. ___ 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
On Sun, Mar 16, 2008 at 10:40 AM, Patrik Hansson [EMAIL PROTECTED] wrote: On Sat, Mar 15, 2008 at 10:42 PM, Patrik Hansson [EMAIL PROTECTED] wrote: On Sat, Mar 15, 2008 at 8:42 PM, Ivor Hewitt [EMAIL PROTECTED] wrote: 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. The only error in my log the lat time i lost a tuner was: mt2060 I2C read failed So not even a write failed. During the night i had another read failed, but this time both tuners stayed alive. Just wanted to add that i just lost a tuner (no.2) (eq L__ in mythtv), but this time without errors in dmesg. ___ 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
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 ? 2008/3/14 Ivor Hewitt [EMAIL PROTECTED]: 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-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
On Sat, Mar 15, 2008 at 8:42 PM, Ivor Hewitt [EMAIL PROTECTED] wrote: 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. The only error in my log the lat time i lost a tuner was: mt2060 I2C read failed So not even a write failed. ___ 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
On 3/12/08, Ben Firshman [EMAIL PROTECTED] wrote: 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 Could you specify which fix ? ___ 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/3/12 Henrik Beckman [EMAIL PROTECTED]: 2.6.22-14 with patches, stable for me. /Henrik On Tue, Mar 11, 2008 at 12:07 PM, [EMAIL PROTECTED] wrote: Not sure if this helps or adds that much to the discussion... (I think this was concluded before) But I finally switched back to kernel 2.6.22.19 on March 5th (with current v4l-dvb code) and haven't had any problems with the Nova-t 500 since. Running mythtv with EIT scanning enabled. Looking in the kernel log I see a single mt2060 read failed message on March 6th and 9th and a single mt2060 write failed on March 8th. These events didn't cause any problems or cause the tuner or mythtv to fail though. Ivor. ___ 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 Henrik: What options (if any) are you using in modprobe.d ? Do you mean that you have patched the kernel or the v4l-dvb tree ? ___ 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
On Wed, Mar 5, 2008 at 12:03 AM, Ben Firshman [EMAIL PROTECTED] wrote: 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 I just want check something i just discovered. Under /sys/module/dvb_core/parameters/ i have something called dvb_powerdown_on_sleep This i set to 1 for me. I also have one called dvb_shutdown_timeout and that is set to 0 Exactly what is it that options usbcore autosuspend=-1 controls ? I would have expected that at least one of those should be -1 ___ 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
On Wed, Mar 12, 2008 at 9:34 PM, Patrik Hansson [EMAIL PROTECTED] wrote: On Wed, Mar 5, 2008 at 12:03 AM, Ben Firshman [EMAIL PROTECTED] wrote: 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 I just want check something i just discovered. Under /sys/module/dvb_core/parameters/ i have something called dvb_powerdown_on_sleep This i set to 1 for me. I also have one called dvb_shutdown_timeout and that is set to 0 Exactly what is it that options usbcore autosuspend=-1 controls ? I would have expected that at least one of those should be -1 .and now i see were i made my mistake (usbcore vs dvb_core) and made a fool out of myself. please disregard my last email. ___ 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
Have you applied any patches to the v4l-dvb source before compiling ? On 3/11/08, Nicolas Will [EMAIL PROTECTED] wrote: On Tue, 2008-03-11 at 11:07 +, [EMAIL PROTECTED] wrote: Not sure if this helps or adds that much to the discussion... (I think this was concluded before) But I finally switched back to kernel 2.6.22.19 on March 5th (with current v4l-dvb code) and haven't had any problems with the Nova-t 500 since. Running mythtv with EIT scanning enabled. Looking in the kernel log I see a single mt2060 read failed message on March 6th and 9th and a single mt2060 write failed on March 8th. These events didn't cause any problems or cause the tuner or mythtv to fail though. ah. So this begs the question: 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. 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
On Sun, Mar 2, 2008 at 9:09 AM, Philip Pemberton [EMAIL PROTECTED] wrote: Nicolas Will wrote: You should really stick to the 1.10 firmware. 03-pre1 was an earlier test and has more issues. Well, I've figured out what was going on. Seems if you run 'make' against the source tree with one kernel, it will always build modules for said kernel until you run 'make distclean'. I started by building for 2.6.24-8-generic, then upgraded to -10-generic, then to -11-generic, and only did a 'make clean; make; sudo make install' when I rebuilt v4l-dvb, as this worked for Madwifi. So to summarise, if you're going to reuse the same source tree for multiple kernels, make distclean before making the drivers, or it'll build for the last kernel you built for... Not sure if it installs to the running kernel, but it certainly doesn't use the headers for the running kernel... But at least the card seems to be behaving now. Up 10 hours with: options dvb-usb-dib0700 debug=15 force_lna_activation=1 options dvb_usb disable_rc_polling=1 options usbcore autosuspend=-1 I've also blacklisted dvb-usb-dib0700 and modprobe'd it in an rc-script, so my HVR-3000 ends up as device 0 and the two T-500 tuners end up as devices 1 and 2; said shell script also sets up symlinks for the 1st and 2nd front-ends on the HVR to devices 10 and 11, because MythTV doesn't like the idea of a card having multiple front-ends... The clock is once again running... -- 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 When i started using options usbcore autosuspend=-1 i deactivated debug=15 Will reactivate it again and reset my clock also. ___ 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
On 2/28/08, Dominique P. [EMAIL PROTECTED] wrote: Hi I have exactly the same problem, all seems fine on vdr until I start one recording that use the second timer , I got thousand of message like this one , it seems stg is not well loaded some time, I just have to shutdown vdr, I can see that device disconnect itself on dmesg and all is OK when starting vdr another time ... hope somebody have a solution for that Best regards kernel = 2.6.22.18-desktop586-1mdv on mandriva 2008.0 Le Thursday 28 February 2008 20:11:39 Philip Pemberton, vous avez écrit : Patrik Hansson wrote: 20:37:40 up 1 day, 8 min ...and counting, both tuners working fine. There are two: [14153.150380] mt2060 I2C read failed [18967.903269] mt2060 I2C read failed recorded in dmesg but nothing fatal. [EMAIL PROTECTED]:~$ uptime 19:06:28 up 23:42, 3 users, load average: 1.19, 1.22, 1.18 And the log is full of this crap: Feb 28 06:29:13 dragon syslogd 1.5.0#1ubuntu1: restart. Feb 28 06:29:13 dragon kernel: [39865.332785] cx24123_readreg: reg=0x14 (error=-121) Feb 28 06:29:13 dragon kernel: [39865.333946] cx24123_readreg: reg=0x20 (error=-121) Feb 28 06:29:13 dragon kernel: [39865.432586] cx24123_readreg: reg=0x14 (error=-121) Feb 28 06:29:13 dragon kernel: [39865.433733] cx24123_readreg: reg=0x20 (error=-121) Feb 28 06:29:13 dragon kernel: [39865.532380] cx24123_readreg: reg=0x14 (error=-121) Feb 28 06:29:13 dragon kernel: [39865.533473] cx24123_readreg: reg=0x20 (error=-121) Feb 28 06:29:13 dragon kernel: [39865.632210] cx24123_readreg: reg=0x14 (error=-121) Feb 28 06:29:13 dragon kernel: [39865.633301] cx24123_readreg: reg=0x20 (error=-121) Feb 28 06:29:13 dragon kernel: [39865.731998] cx24123_readreg: reg=0x14 (error=-121) Feb 28 06:29:13 dragon kernel: [39865.733092] cx24123_readreg: reg=0x20 (error=-121) Feb 28 06:29:14 dragon kernel: [39865.831820] cx24123_readreg: reg=0x14 (error=-121) Feb 28 06:29:14 dragon kernel: [39866.374256] mt2060 I2C write failed (len=2) Feb 28 06:29:14 dragon kernel: [39866.374262] mt2060 I2C write failed (len=6) Feb 28 06:29:14 dragon kernel: [39866.374264] mt2060 I2C read failed Feb 28 06:29:14 dragon kernel: [39866.382298] mt2060 I2C read failed Feb 28 06:29:14 dragon kernel: [39866.390210] mt2060 I2C read failed Feb 28 06:29:14 dragon kernel: [39866.398195] mt2060 I2C read failed Feb 28 06:29:14 dragon kernel: [39866.406181] mt2060 I2C read failed Feb 28 06:29:14 dragon kernel: [39866.414175] mt2060 I2C read failed Feb 28 06:29:14 dragon kernel: [39866.422213] mt2060 I2C read failed Feb 28 06:29:14 dragon kernel: [39866.430162] mt2060 I2C read failed And the tuner is utterly shot. It worked for most of one recording, then promptly died. *sigh* Patrik, just out of curiosity, what kernel are you running? I'm running 2.6.24-8-generic on Mythbuntu 8.04 alpha 2 and thinking about downgrading to an earlier kernel. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb 1: I got a mailer-daemon reply saing that my ip was spamfiltred (I use gmail?) when replying to what kernel i use. My kernel is 2.6.22-14-generic 2: This morning I hade L__ on my second tuner. some more mt2060 I2C read failed in dmesg. ___ 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
On Tue, Feb 26, 2008 at 8:37 PM, Patrik Hansson [EMAIL PROTECTED] wrote: On Tue, Feb 26, 2008 at 8:18 PM, Philip Pemberton [EMAIL PROTECTED] 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. It was a module and i put the option i /etc/modprobe.d/options next to options dvb-usb-dib0700 force_lna_activation=1 Running now, will be back with the results. On a side note: Could that be the reason debug=15 also might work as a workaround, there is so much traffic that the usb never suspends ? Thanks Phil for the fix, hope it stays stable.. 20:37:40 up 1 day, 8 min ...and counting, both tuners working fine. There are two: [14153.150380] mt2060 I2C read failed [18967.903269] mt2060 I2C read failed recorded in dmesg but nothing fatal. ___ 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
On Tue, Feb 26, 2008 at 8:18 PM, Philip Pemberton [EMAIL PROTECTED] 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. It was a module and i put the option i /etc/modprobe.d/options next to options dvb-usb-dib0700 force_lna_activation=1 Running now, will be back with the results. On a side note: Could that be the reason debug=15 also might work as a workaround, there is so much traffic that the usb never suspends ? Thanks Phil for the fix, hope it stays stable.. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Very quiet around Nova-T 500
On Wed, Feb 20, 2008 at 4:14 PM, hermann pitton [EMAIL PROTECTED] wrote: Hi Nico, Am Mittwoch, den 20.02.2008, 07:12 + schrieb Nicolas Will: On Wed, 2008-02-20 at 01:12 +0100, hermann pitton wrote: Now stop that logging madness and get back to work! ... ;o) This is a rather comical situation, though... The debugging tool is providing a rather unexpected and unwelcomed fix. Nico Hi, no, it is not. It is well known! Timings are very critical on almost all drivers. We hold breath on almost everything coming down from above, nobody has the ability, or whom should ever want it, to test all possible side effects on all supported devices ... That something breaks is very common, and that others have to give the plumbers, is nothing new. To stay fair, it mostly has a good reason, and if there are some remaining ticks left, you might get it adjusted, but ... On the other side it is the same ... May post may have sounded offensive, apparently. Sorry about that, my intentions were on the lighter sides of life. Nico nothing offending at all, did enjoy your above comment :) and like your active support for others. It is just not totally unexpected that high debug levels can have some spin-off and I'm curious about it. Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Kernel 2.6.24-2 Debug=15 Got this after 5 minutes of LiveTV: (Dunno if it could be usefull or not) modifying (1) streaming state for 1 data for streaming: 10 13 0f 10 13 00 usb 10-1: USB disconnect, address 2 03 14 03 01 60 00 ep 0 write error (status = -19, len: 6) mt2060 I2C write failed 03 14 04 07 ff ff ep 0 write error (status = -19, len: 6) 03 14 04 08 ff ff ep 0 write error (status = -19, len: 6) 03 14 04 09 ff f0 ep 0 write error (status = -19, len: 6) 02 17 81 fd ep 0 read error (status = -19) 77 8d I2C read failed on address b 02 17 81 ca ep 0 read error (status = -19) 00 20 I2C read failed on address b 02 17 81 fd ep 0 read error (status = -19) 77 8d I2C read failed on address b 02 17 81 fd ep 0 read error (status = -19) 77 8d I2C read failed on address b 02 17 81 fd ep 0 read error (status = -19) 77 8d I2C read failed on address b 02 17 81 fd ep 0 read error (status = -19) 77 8d I2C read failed on address b 02 17 81 fd ep 0 read error (status = -19) 77 8d I2C read failed on address b 02 17 81 fd ep 0 read error (status = -19) 77 8d I2C read failed on address b 02 17 81 fd ep 0 read error (status = -19) 77 8d I2C read failed on address b ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Very quiet around Nova-T 500
I have now set the debug to 15 and will test this tonight. On 2/20/08, Nicolas Will [EMAIL PROTECTED] wrote: On Wed, 2008-02-20 at 10:36 +0100, Jonas Anden wrote: The strange thing is that modinfo does not say anything about a level 15 debug for the dvb_usb_dib0700 module. http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#dvb_usb_dib0700 The debug value is a bit field, with each bit representing a different category. With all bits on (ie full debugging) the decimal value becomes 15. I should have guessed. Documented for poor souls with slow brains like me. 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] Very quiet around Nova-T 500
On 2/19/08, Jonas Anden [EMAIL PROTECTED] wrote: There is not a lot being said about the Nova-T 500 the last week. Don´t know if that is a good (coders coding) or a bad (nothin happening) Or coders busy on other code, or coders who ran out of ideas, or coders enjoying life, etc. ..or just waiting for the problem to reappear ;( The trouble with the second tuner dying is tricky (for me) to isolate. As a workaround, enabling full debug (debug=15) on the dvb_usb_dib0700 module has made my system rock solid. I turned on debugging to try to isolate the issue, but with debugging enabled the problem does not appear (at least not on my system). I haven't really figured out *what* in the debug code is helping yet, but I still suspect that this is timing-related and the debug code simply slows things down a bit. Enabling debugging will put a whole lot of junk in your system log files, but at least the second tuner wont die on you. If you go this path, make sure your log rotation works as it should -- my weekly rotated logs are up to 130 MB in size ;) // J ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Could someone that knows what they are doing document that option on the wiki ? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T-500 disconnect issues
I will definently look in to this and will try to upgrade the kernel. (will prob. screw it up but anyways). Ps. Got a good kernel upgrade-how to for 7.10 ? Ds. On 2/14/08, Simeon Walker [EMAIL PROTECTED] wrote: On 14/02/2008, General [EMAIL PROTECTED] wrote: Hi. I have been following the discussion regarding the mt2060 I2C read / write failed errors. I am running Ubuntu and get the same behaviour since I upgraded to the latest kernel (2.6.24.1) to resolve some wireless driver issues I was having. When I was running the standard Ubuntu kernel (2.6.22-14-generic) I never had the disconnect issues in 3 or 4 months of 24/7 usage. This was using the latest v4l- dvb sources as per the wiki. Perhaps this would suggest that the error is not with the dib0700 driver but elsewhere? So my dilemma is do I have a constant wireless connection but a dvb driver that drops out or a constant dvb driver with a wireless connection that drops out?! Ah but you can get the latest wireless drivers for your current kernel: http://linuxwireless.org/en/users/Download Sim ___ 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] Very quiet around Nova-T 500
Hello There is not a lot being said about the Nova-T 500 the last week. Don´t know if that is a good (coders coding) or a bad (nothin happening) but i would like to know if there is anything we could do ? I can´t write code but maybe i can help in some other way ? Testing builds or whatever. Just my 5 cents / Patrik Hansson ___ 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
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. On Feb 7, 2008 5:51 PM, Jonas Anden [EMAIL PROTECTED] wrote: Do you have a way to automate this ? Ie to detect that a tuner is gone ? No, I have yet to find any log message that says things aren't OK. Mythbackend seems to just fail its recordings and not create the recording file, which is kind of annoying. In my point of view, it would be better if mythbackend would *crash*, since this would make the other backend (which uses analog tuners) take over the recording. It wouldn't be the same quality, but at least the show would be recorded... // J ___ 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
