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
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
Sid Boyce wrote:
> Regarding the NVidia module, NVidia themselves haven't yet conjured up a
> fix for the latest kernels.
[snip]
This was on 2.6.24 -- once I downgraded to 2.6.22, just about everything that
could break, did. For bonus points, none of the packages would recompile
either (but maybe I was being stupid).
Like said, it was easier to just hose it down and start over.
I've got the following kopts enabled for the DVB modules:
==
[EMAIL PROTECTED]:~$ cat /etc/modprobe.d/dvb-options
# enable LNA for Hauppauge Nova-T-500
options dvb-usb-dib0700 force_lna_activation=1
# disable IR remote for Nova-T-500 (and other USB-DVB IRCs)
options dvb-usb disable_rc_polling=1
# force card order -- DiB0700 (Nova-T-500) first, then CX88 (HVR-3000).
# also creates virtual i/f 10 so Myth can see the Freeview hybrid
install cx88-dvb /sbin/modprobe dvb-usb-dib0700; /sbin/modprobe
--ignore-install cx88-dvb; mkdir -p /dev/dvb/adapter10; ln -sf
/dev/dvb/adapter2/demux1 /dev/dvb/adapter10/demux0; ln -sf
/dev/dvb/adapter2/dvr1 /dev/dvb/adapter10/dvr0; ln -sf
/dev/dvb/adapter2/frontend1 /dev/dvb/adapter10/frontend0; ln -sf
/dev/dvb/adapter2/net1 /dev/dvb/adapter10/net0
==
At the moment both of the Nova-T-500's tuners are recording live TV, and the
HVR-3000 is in DVT-T mode and recording too. No problems yet, but uptime is
only 75 minutes. It's got a massive list of things to record overnight (think
"stress test"), so fingers crossed. The only USB disconnect warning in dmesg
is from when I unplugged the USB mouse after I got the R/C working.
--
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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Philip Pemberton wrote: > Nicolas Will wrote: >> My Ubuntu-provided 2.6.22 works fine. >> >> And I am not losing any tuner. Not even with the Multirec of MythTV >> 0.21. > > Right, well I've had enough of Ubuntu 8.04a2 (and I've learned a valuable > lesson about not using alpha OSes on "production" systems). This is mostly > down to my own actions, though -- the kernel is utterly hosed, the nVidia > driver won't load, and the HVR-3000 is refusing to talk (instead insisting > that the demux chip isn't talking). > > I've backed the system off to 7.10 (Gutsy) and it seems stable -- I had to > modify the patch from http://dev.kewl.org/hauppauge/ to apply on the latest Hg > source... Much fun. It seems to work, so I'll probably publish the repository > tomorrow some time (after the day I've had I don't feel like doing much of > anything). > > Plus I'd rather like to see if it works before I go unleashing it on the > masses at large. > > I'm just waiting for ScanDVB to finish making a channels.conf for ASTRA 28.2E, > after that I'll see if I can crash the T500 :) > Regarding the NVidia module, NVidia themselves haven't yet conjured up a fix for the latest kernels. I hope they do so as one kernel symbol (init_mm) that is needed was temporarily reexported and will again not be exported from 2.6.26-rc. That seems to be the holdup at NVidia, hopefully will be sorted by the time 2.6.25 final appears. NVIDIA_2.6.25.patch.txt can be downloaded from the NVidia Linux forum which works with later 2.6.24-git kernels and 2.6.25-rc. Here I have been running it with kernels up to current 2.6.25-rc5-git5. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ 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
Nicolas Will wrote:
> My Ubuntu-provided 2.6.22 works fine.
>
> And I am not losing any tuner. Not even with the Multirec of MythTV
> 0.21.
Right, well I've had enough of Ubuntu 8.04a2 (and I've learned a valuable
lesson about not using alpha OSes on "production" systems). This is mostly
down to my own actions, though -- the kernel is utterly hosed, the nVidia
driver won't load, and the HVR-3000 is refusing to talk (instead insisting
that the demux chip isn't talking).
I've backed the system off to 7.10 (Gutsy) and it seems stable -- I had to
modify the patch from http://dev.kewl.org/hauppauge/ to apply on the latest Hg
source... Much fun. It seems to work, so I'll probably publish the repository
tomorrow some time (after the day I've had I don't feel like doing much of
anything).
Plus I'd rather like to see if it works before I go unleashing it on the
masses at large.
I'm just waiting for ScanDVB to finish making a channels.conf for ASTRA 28.2E,
after that I'll see if I can crash the T500 :)
--
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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
On Sat, 2008-03-15 at 19:42 +, Ivor Hewitt 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) I only have the lna option. > > Is the ubuntu kernel completely generic? Really not, if you mean straight out of kernel.org. > > 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? I do get some of those errors, never a tuner drop. Nico ___ 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
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
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
Patched v4l-dvb to include the streaming and reception patches that was included a while back. (I´ll check the date of my v4l-dvb tree). I think I have LNA and maybe I disable the remote to, but i need to check and get back about the modprob-d options. /Henrik On Wed, Mar 12, 2008 at 8:48 PM, Patrik Hansson <[EMAIL PROTECTED]> wrote: > 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 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
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
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
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
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
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
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
On Tue, 2008-03-11 at 22:03 +, Philip Pemberton wrote: > [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. > > Is this a distribution kernel, or one built from virgin (i.e. > unmodified from > www.kernel.org or one of the mirrors) source code? > > Is there any possibility of you uploading your .config file somewhere? > I'm > curious what kernel options you have set.. especially USB_SUSPEND > (USB > autosuspend -- not sure if this was added to 2.6.24 or if .22 had it > as well; > I don't have a .22 source tree at the moment). > > 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. > My Ubuntu-provided 2.6.22 works fine. And I am not losing any tuner. Not even with the Multirec of MythTV 0.21. Nico ___ 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
[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.
Is this a distribution kernel, or one built from virgin (i.e. unmodified from
www.kernel.org or one of the mirrors) source code?
Is there any possibility of you uploading your .config file somewhere? I'm
curious what kernel options you have set.. especially USB_SUSPEND (USB
autosuspend -- not sure if this was added to 2.6.24 or if .22 had it as well;
I don't have a .22 source tree at the moment).
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.
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
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 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
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] Nova-T 500 issues - losing one tuner
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
Nicolas Will wrote:
> As much as I understand your position, where it's coming from, and the
> reasoning behind it (and I'm not necessarily against it, trust me on
> that), blaming it all on the closed parts is maybe just as bad as
> blaming a USB vendor or open source coders and giving up.
It seems to be able to handle one or two recordings, then on the third it
falls flat on its face. I told it to record Jurassic Park, and as soon as the
recording was due to start, I got this in dmesg:
Mar 3 21:00:03 dragon kernel: [51071.390905] mt2060 I2C write failed
Mar 3 21:00:03 dragon kernel: [51071.390907] >>> 03 14 04 07 ff ff
Mar 3 21:00:03 dragon kernel: [51071.390910] ep 0 write error (status = -19,
len: 6)
Mar 3 21:00:03 dragon kernel: [51071.390912] >>> 03 14 04 08 ff ff
Mar 3 21:00:03 dragon kernel: [51071.390915] ep 0 write error (status = -19,
len: 6)
Mar 3 21:00:03 dragon kernel: [51071.390917] >>> 03 14 04 09 ff f0
Mar 3 21:00:03 dragon kernel: [51071.390920] ep 0 write error (status = -19,
len: 6)
Mar 3 21:28:02 dragon -- MARK --
Mar 3 21:48:02 dragon -- MARK --
Mar 3 21:52:31 dragon kernel: [54213.772868] modifying (0) streaming state for 0
Mar 3 21:52:31 dragon kernel: [54213.772874] data for streaming: 0 10
Mar 3 21:52:31 dragon kernel: [54213.772876] >>> 0f 00 10 00
Mar 3 21:52:31 dragon kernel: [54213.772881] ep 0 write error (status = -19,
len: 4)
Mar 3 21:52:31 dragon kernel: [54213.773463] dvb-usb: Hauppauge Nova-T 500
Dual DVB-T successfully deinitialized and disconnected.
Mar 3 21:52:31 dragon kernel: [54214.011201] usb 2-1: new high speed USB
device using ehci_hcd and address 3
Mar 3 21:52:31 dragon kernel: [54214.144020] usb 2-1: configuration #1 chosen
from 1 choice
Mar 3 21:52:31 dragon kernel: [54214.144429] FW GET_VERSION length: 16
Mar 3 21:52:31 dragon kernel: [54214.144431] cold: 0
Mar 3 21:52:31 dragon kernel: [54214.144433] dvb-usb: found a 'Hauppauge
Nova-T 500 Dual DVB-T' in warm state.
Mar 3 21:52:31 dragon kernel: [54214.144457] dvb-usb: will pass the complete
MPEG2 transport stream to the software demuxer.
Mar 3 21:52:31 dragon kernel: [54214.144638] DVB: registering new adapter
(Hauppauge Nova-T 500 Dual DVB-T)
Mar 3 21:52:31 dragon kernel: [54214.144806] >>> 0c 08 80
Mar 3 21:52:31 dragon kernel: [54214.158937] >>> 0c 08 c0
Mar 3 21:52:31 dragon kernel: [54214.178924] >>> 0c 0f 80
[.]
I'm beginning to suspect a power supply or cooling issue; it seems to get
worse the longer the machine is running... 15 hours uptime and the T500 is
basically dead now, and a reboot only brings it back into the land of the
living for a couple of hours at most...
Now where did I put that 500W junker that came with the case...
--
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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Darren Salt wrote:
> Which revision?
Huh. Rev 62 UHCI and Rev 65 EHCI. Maybe it's not the USB HA then.
> I have a VIA-based USB card in one computer here; I've had no problems with
> it whatsoever. It shows up as:
>
> 00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1
> Controller (rev 61)
> 00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1
> Controller (rev 61)
> 00:10.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63)
There's a VIA southbridge in this machine; it actually works quite nicely with
most things - exceptions being my Icybox IB380 hard drive enclosure and a
Minolta film scanner.
--
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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
On Sun, 2008-03-02 at 23:07 +, Darren Salt wrote: > I demand that Philip Pemberton may or may not have written... > > > And now the icing on the cake: > [snip] > > [17302.420405] BUG: unable to handle kernel paging request at > virtual address > > fa23bda0 > > [17302.420412] printing eip: f89bd162 *pde = 374ac067 *pte = > > > [17302.420417] Oops: [#1] SMP > > [17302.420420] Modules linked in: [...] ath_hal(P) [...] nvidia(P) > [...] > > [17302.420481] Pid: 9917, comm: kdvb-ad-1-fe-0 Tainted: P > > (2.6.24-11-generic #1) > [snip] > > You lose. Twice. > > Can you cause that oops *without* the taintware? If not, do not pass > Go, do > not collect £200, go directly to the two relevant vendors and > (possibly) get > passed back and forth :-) > > (You may be able to remove one of the taintware modules by upgrading > to > 2.6.25-rc3; you can remove the other by using nv or nouveau.) w Let's not go there. That is potential flame bait. As much as I understand your position, where it's coming from, and the reasoning behind it (and I'm not necessarily against it, trust me on that), blaming it all on the closed parts is maybe just as bad as blaming a USB vendor or open source coders and giving up. Until a week ago I had an Atheros card needing that hal blob. I am still running the nvidia blob today (can't wait to remove it and use the built-in Intel 965G chip with my ADD2 card once the open drivers get better than the nvidia stuff. And they will, the full specs are out, including for H.264 hardware acceleration). And my tuners worked, both. No oops. Let's keep on thing in mind: Philip is running a development version of Ubuntu that may need some stabilisation itself. Nico ___ 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 demand that Philip Pemberton may or may not have written... > And now the icing on the cake: [snip] > [17302.420405] BUG: unable to handle kernel paging request at virtual address > fa23bda0 > [17302.420412] printing eip: f89bd162 *pde = 374ac067 *pte = > [17302.420417] Oops: [#1] SMP > [17302.420420] Modules linked in: [...] ath_hal(P) [...] nvidia(P) [...] > [17302.420481] Pid: 9917, comm: kdvb-ad-1-fe-0 Tainted: P > (2.6.24-11-generic #1) [snip] You lose. Twice. Can you cause that oops *without* the taintware? If not, do not pass Go, do not collect £200, go directly to the two relevant vendors and (possibly) get passed back and forth :-) (You may be able to remove one of the taintware modules by upgrading to 2.6.25-rc3; you can remove the other by using nv or nouveau.) -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Buy local produce. Try to walk or cycle. TRANSPORT CAUSES GLOBAL WARMING. Kix are for trids. ___ 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 demand that Philip Pemberton may or may not have written... [snip] > The blasted thing has a VIA USB controller on board - from experience it > seems VIA are one of the few companies that still haven't managed to come > up with a USB2 host-controller design that works properly without a filter > driver sitting between the USB stack and the chip... Which revision? I have a VIA-based USB card in one computer here; I've had no problems with it whatsoever. It shows up as: 00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 61) 00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 61) 00:10.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) [snip] -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Output less CO2 => avoid massive flooding.TIME IS RUNNING OUT *FAST*. I am what I am and that's all that I am. ___ 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, 2008-03-02 at 21:49 +, Philip Pemberton wrote: > > I give up. Philip, You are having problems to an extend that nobody experienced or reported. Certainly not me. So either there is something wrong in your process, your software, or you have some faulty hardware. Nico ___ 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
And now the icing on the cake:
[17296.754309] <<< b5 7d
[17296.754311] I2C read failed on address a
[17298.643002] >>> 02 15 81 fd
[17298.643012] ep 0 read error (status = -19)
[17298.643013] <<< b5 7d
[17298.643015] I2C read failed on address a
[17300.535677] >>> 02 15 81 fd
[17300.535687] ep 0 read error (status = -19)
[17300.535688] <<< b5 7d
[17300.535690] I2C read failed on address a
[17302.193280] usbcore: deregistering interface driver dvb_usb_dib0700
[17302.314293] dib0700: loaded with support for 6 different device-types
[17302.420405] BUG: unable to handle kernel paging request at virtual address
fa23bda0
[17302.420412] printing eip: f89bd162 *pde = 374ac067 *pte =
[17302.420417] Oops: [#1] SMP
[17302.420420] Modules linked in: dvb_usb_dib0700 dib7000p dib7000m dvb_usb
dib0070 isofs udf video output container sbs sbshc ac dock battery mt2060
dib3000mc dibx000_common iptable_filter ip_tables x_tables af_packet lp
dvb_pll ipv6 cx22702 wlan_wep isl6421 cx24123 cx88_dvb cx88_vp3054_i2c
wlan_scan_sta ath_rate_sample snd_hda_intel tuner tea5767 tda8290 snd_hwdep
tda18271 tda827x tuner_xc2028 xc5000 snd_seq_dummy tda9887 cx88_alsa
snd_pcm_oss snd_mixer_oss tuner_simple tuner_types snd_seq_oss mt20xx tea5761
ath_pci wlan ath_hal(P) sr_mod cdrom snd_pcm nvidia(P) snd_seq_midi cx8802
cx8800 snd_page_alloc cx88xx snd_rawmidi snd_seq_midi_event ir_common
i2c_algo_bit videodev v4l1_compat compat_ioctl32 v4l2_common atiixp
videobuf_dvb dvb_core snd_seq snd_timer snd_seq_device tveeprom
videobuf_dma_sg videobuf_core btcx_risc snd i2c_piix4 button ati_agp agpgart
ide_core i2c_core parport_pc parport soundcore shpchp pci_hotplug k8temp evdev
pcspkr pata_atiixp ext3 jbd mbcache sg sd_mod ata_generic floppy uhci_hcd
pata_acpi ahci ohci_hcd ehci_hcd libata usbcore scsi_mod ssb r8169 thermal
processor fan fuse
[17302.420479]
[17302.420481] Pid: 9917, comm: kdvb-ad-1-fe-0 Tainted: P
(2.6.24-11-generic #1)
[17302.420484] EIP: 0060:[] EFLAGS: 00010286 CPU: 0
[17302.420493] EIP is at i2c_transfer+0x22/0x60 [i2c_core]
[17302.420496] EAX: fa23bda0 EBX: ffda ECX: 0003 EDX: dddebf00
[17302.420498] ESI: dddebf00 EDI: f77a255c EBP: 0003 ESP: dddebed8
[17302.420500] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068
[17302.420503] Process kdvb-ad-1-fe-0 (pid: 9917, ti=dddea000 task=d8c59680
task.ti=dddea000)
[17302.420505] Stack: dddebf00 f7515a28 dddebf00 dddebf54 dddebf68 f9c811bb
[17302.420510]ddadb700 000a 0004 dddebf58 0074
0002 dddebf9a
[17302.420515]000a 0004 dddebf54 0282 0282 0024
dddebf00 0001
[17302.420520] Call Trace:
[17302.420529] [] dibx000_i2c_gated_tuner_xfer+0x10b/0x1b0
[dibx000_common]
[17302.420563] [] del_timer_sync+0xe/0x20
[17302.420576] [] i2c_transfer+0x3e/0x60 [i2c_core]
[17302.420590] [] mt2060_writereg+0x3c/0x60 [mt2060]
[17302.420601] [] dvb_frontend_thread+0x1ae/0x300 [dvb_core]
[17302.420620] [] autoremove_wake_function+0x0/0x40
[17302.420632] [] dvb_frontend_thread+0x0/0x300 [dvb_core]
[17302.420644] [] kthread+0x42/0x70
[17302.420647] [] kthread+0x0/0x70
[17302.420653] [] kernel_thread_helper+0x7/0x10
[17302.420665] ===
[17302.420666] Code: ff 83 c4 04 0f b6 c0 5b c3 83 ec 14 89 5c 24 04 bb da ff
ff ff 89 7c 24 0c 89 c7 89 6c 24 10 89 cd 89 74 24 08 89 14 24 8b 40 0c <8b>
00 85 c0 74 1f 8d 77 20 89 f0 e8 1e af 95 c7 8b 5f 0c 89 e9
[17302.420689] EIP: [] i2c_transfer+0x22/0x60 [i2c_core] SS:ESP
0068:dddebed8
[17302.420697] ---[ end trace 8ec949325fb5108c ]---
I give up.
--
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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Nicolas Will wrote:
> You do know that the cx24123 module has nothing to do with the
> Nova-t-500, don't you?
I know. It's for the HVR-3000's satellite demux.
> Would you have a DVB-S card in the system as well?
See above :)
> Other than this issue, how's the stability of 0.21 in Hardy?
> I'm itching... After al,l I ran Gutsy since alpha 2, for hardware
> support reasons, but I have no real motivation apart from "I want to try
> the latest and greatest" today.
Myth itself is quite stable, but Mythbuntu had some issues with the initial
8.04a2 release -- mostly with VNC and setting up the Myth transcoding daemon
('mkdir /var/lib/mythdvd/temp; chmod 777 /var/lib/mythdvd/temp' as root fixed
it for me). The LIRC config files for the Nova-T500's remote are a bit
mangled, and some buttons don't work by default.
Other than that, ripping DVDs to MPEG files and playing them back results in
issues with A/V sync; switching the player to "default player" in File Types
seems to have cured that.
Stability-wise, it puts MediaPortal to shame. Feature-wise, it's got
everything I need. Once I get the Nova-T500 to behave itself, and MythTV to
hibernate (or even shut down completely) and set an ACPI wakeup timer, I'll
consider the project 'done' :)
--
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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Nicolas Will wrote:
> I am shocked by all your problems.
I'm not.
The blasted thing has a VIA USB controller on board - from experience it seems
VIA are one of the few companies that still haven't managed to come up with a
USB2 host-controller design that works properly without a filter driver
sitting between the USB stack and the chip...
I've got an uptime of 1 hour with the tuners idling (EIT scan on one of the
tuners, other idle), but as soon as I start channel-hopping, the stupid thing
falls over.
So for what it's worth, here's the spec of my machine:
- Biostar TA690G mainboard; AMD 690G chipset. Onboard VGA disabled.
- AMD Athlon64 X2 4000+ AM2 CPU
- 2GB RAM, dual channel mode
- WD Caviar-GP (WD5000AACS) 500GB Quiet Drive
- LiteOn LH-20A1P DVD writer
- Hauppauge HVR-3000 DVB-S/T hybrid tuner
- Hauppauge Nova-T 500 dual DVB-T
And the OS:
- Mythbuntu 8.04 alpha2 (Ubuntu Hardy) with latest updates
- Kernel 2.6.24-11-generic
- MythTV 0.21.0~fixes16259-0ubuntu1
I know a few folks are using 2.6.22 kernels.. just out of curiosity, has
anyone got a Nova-T 500 working on 2.6.24? I'm just about to dig into the
kernel changelog to see if anything's been changed relating to USB (especially
anything to do with handling of VIA USB chipsets), though I doubt this is a
kernel issue.
IIRC there was something related to USB bandwidth handling that went into the
kernel not long ago... hmm, I wonder...
--
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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
On Sun, 2008-03-02 at 14:09 +, Philip Pemberton wrote: > Patrik Hansson wrote: > > When i started using options usbcore autosuspend=-1 i deactivated > debug=15 > > Will reactivate it again and reset my clock also. > > Well, changing channels on Myth seems to provoke it into failing... > and it > usually kills both tuners at the same time. Something is very badly > wrong with > this thing... > > I think I'm going to move the T500 into my Windows PC and buy a couple > of > cheap USB sticks for Freeview. This has gone on long enough. I am shocked by all your problems. I am certainly not experiencing this sort of mayhem on my system. Nico ___ 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
Patrik Hansson wrote:
> When i started using options usbcore autosuspend=-1 i deactivated debug=15
> Will reactivate it again and reset my clock also.
Well, changing channels on Myth seems to provoke it into failing... and it
usually kills both tuners at the same time. Something is very badly wrong with
this thing...
I think I'm going to move the T500 into my Windows PC and buy a couple of
cheap USB sticks for Freeview. This has gone on long enough.
--
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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Patrik Hansson wrote:
> When i started using options usbcore autosuspend=-1 i deactivated debug=15
> Will reactivate it again and reset my clock also.
Just had a USB disconnect..
Switched MythTV to BBC HD, CPU load hit 100% and video jittered like mad.
Switched back to Freeview via the Nova, both tuners down. USB disconnect and
I2C errors in dmesg. Killed off mythbackend and the T500 re-attached, but
wouldn't work (continuous disconnects whenever I loaded mythbackend) until I
killed mythbackend, rmmod'ed dvb-usb-dib0700, then modprobed dvb-usb-dib0700
and restarted mythbackend.
I've disabled EIT scanning on all but one of the Nova-T500 tuners, and set
"open on demand" for both Nova-T500 tuners and both HVR-3000 tuners.
If Myth isn't holding the tuner open, maybe it'll be a little more tolerant of
this kind of glitch.. but it doesn't seem to switch to another tuner on the
same source if one is dead, it just keeps hammering the same tuner over and
over until it gives up... Urgh.
--
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
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
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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
On Fri, 2008-02-29 at 21:31 +, Philip Pemberton wrote: >Answers are "2.6.24-8-generic", Mythbuntu 8.04 alpha 2, Hg > 615ce34, and > yes (EIT scanning on) for me, and firmware is dvb-usb-dib0700-1.10.fw > (in > /lib/firmware/2.6.24-8-generic). I'm planning to try > dvb-usb-dib0700-03-pre1.fw at some point -- is this older or newer > than 1.10 > (it's listed on the Wiki as a possible solution to the disconnect > issue). You should really stick to the 1.10 firmware. 03-pre1 was an earlier test and has more issues. Nico ___ 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
Ben Firshman wrote:
> Mine has now been running for a couple of days now without problems, I will
let you know if I lose a tuner.
Strange, mine's still crashing out after a couple of hours. Just out of
curiosity...
- What kernel are you running? Distribution? Driver version?
- If you're using MythTV, do you have "Use this card for EIT scanning"
enabled for the T-500?
- What firmware?
Answers are "2.6.24-8-generic", Mythbuntu 8.04 alpha 2, Hg 615ce34, and
yes (EIT scanning on) for me, and firmware is dvb-usb-dib0700-1.10.fw (in
/lib/firmware/2.6.24-8-generic). I'm planning to try
dvb-usb-dib0700-03-pre1.fw at some point -- is this older or newer than 1.10
(it's listed on the Wiki as a possible solution to the disconnect issue).
I'm also staring daggers at the VIA USB controller chip on the T500... I've
had nothing but trouble from VIA USB chips, with the possible exception of the
K8T800 Pro on the motherboard in my desktop machine. FWIW, the PVR is based
on a Biostar TA690G board, which uses the AMD/ATI 690G, but I've got a
Gainward nVidia GeForce 8400GS PCIe-x16 card in there (because the 690G is a
poor excuse for a graphics chip and only just works under Windows, let alone
Linux!)
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
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
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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
On Thu, 2008-02-28 at 19:11 +, Philip Pemberton wrote: > [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. You do know that the cx24123 module has nothing to do with the Nova-t-500, don't you? Would you have a DVB-S card in the system as well? I do, and I have this module loaded too, zero error message involving it, and I'm not really losing any tuner in normal use. I have * 1 Hauppauge Nova-t-500 * 1 KWorld DVB-S 100 * Gutsy 64-bit system * Ubuntu 2.6.22 kernel * Ubuntu updates+backports * Medibuntu * Mythbuntu's 0.20.2-fixes updates * a recent v4l-dvb tree compiles against the Ubuntu headers. The only other USB device I am using is an RF transmitter for my keyboard. All (and I like documenting) details there: http://www.youplala.net/linux/home-theater-pc Other than this issue, how's the stability of 0.21 in Hardy? I'm itching... After al,l I ran Gutsy since alpha 2, for hardware support reasons, but I have no real motivation apart from "I want to try the latest and greatest" today. nico ___ 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
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.
--
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
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] Nova-T 500 issues - losing one tuner
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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Christophe Boyanique wrote:
> options dvb-usb-dib0700 force_lna_activation=1
> options dvb_usb disable_rc_polling=1
Did that last night and I'm still seeing MT2060 I2C timeouts... *sigh*
This is on Mythbuntu 8.04 alpha-2, latest updates, running drivers from Hg TIP
patched for the HVR-3000 (using the dev.kewl.org multi-frontend patch).
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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Hello Ben Firshman you wrote : > Which one disables the remote? I don't use the remote, so I could try > disabling it and see if I get any problems. > This one disables the remote: options dvb_usb disable_rc_polling=1 Christophe. ___ 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
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
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
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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
> 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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
Hi Jonas, > You don't need to reboot to regain the other tuner. I use the following: Do you have a way to automate this ? Ie to detect that a tuner is gone ? Christophe. ___ 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
Not too much comfort, but... > Maybe a different problem, but the tuner is really lost until a reboot > all the same. You don't need to reboot to regain the other tuner. I use the following: service mythbackend stop modprobe -r dvb_usb_dib0700 modprobe dvb_usb_dib0700 service mythbackend start After that, the tuner is back on line. // J ___ 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, 2008-02-06 at 19:29 +, Nicolas Will wrote: > Well... > > You can now laugh at me, the supposedly problem-free user... > > I managed to get my nova-t-500 to lose a tuner too! > > MythTV was recording on tuner 1. > > I was channel surfing on tuner 2. > > After flipping through a few channels, I got a black screen. > > I looked at the logs. MythTV is complaining that the file it uses to > watch TV (in fact you never watch the stream from the card, MythTV > records the channel in a file, then plays that file) is invalid. > > You bet it is invalid, it's mostly not there, or with a size of zero. > > I guess that the tuner became non-responsive and thus outputs nothing. > > Getting out of "LiveTV" and coming back does not fix it. Trying to go > to > another channel serves no purpose, MythTV must be desperately trying > to > get any sort of response from the tuner before sending it any new > command. > > That was a long "me too", but a "me too" all the same. > > Dang ! > > Oh, my reception quality that used to be ugly has been fixed. I am now > a > user of a 26dB gain masthead amplifier. My signal strength took a 25% > improvement, BER and UNC are zero on all channels. Still using the > internal LNA, though; I haven't tried doing without it. Ah... It looks like only ITV4 is problematic, even if the other channels on the multiplex are fine. Maybe a different problem, but the tuner is really lost until a reboot all the same. I have tried without the LNA, same difference. but it's an opportunity to measure signal and BER without it... Anybody know about any ITV4 problem on the UK-Durris transmitter? Nico ___ 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
Well... You can now laugh at me, the supposedly problem-free user... I managed to get my nova-t-500 to lose a tuner too! MythTV was recording on tuner 1. I was channel surfing on tuner 2. After flipping through a few channels, I got a black screen. I looked at the logs. MythTV is complaining that the file it uses to watch TV (in fact you never watch the stream from the card, MythTV records the channel in a file, then plays that file) is invalid. You bet it is invalid, it's mostly not there, or with a size of zero. I guess that the tuner became non-responsive and thus outputs nothing. Getting out of "LiveTV" and coming back does not fix it. Trying to go to another channel serves no purpose, MythTV must be desperately trying to get any sort of response from the tuner before sending it any new command. That was a long "me too", but a "me too" all the same. Dang ! Oh, my reception quality that used to be ugly has been fixed. I am now a user of a 26dB gain masthead amplifier. My signal strength took a 25% improvement, BER and UNC are zero on all channels. Still using the internal LNA, though; I haven't tried doing without it. Nico ___ 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
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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
On Sun, 2008-02-03 at 10:39 +0100, Jonas Anden wrote: > > 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 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'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
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)... > >
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
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
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
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
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
