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
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.
> > >
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 may
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
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..
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 t
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
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
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
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
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, Pa
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, h
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 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:
> >> Jus
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 switch
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-d
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 t
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
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,
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 h
[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 wit
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)
> > Bu
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-
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
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 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 merge
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 see
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
> Contr
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: f8
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]
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
>
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
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 r
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 i
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
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 i
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 wro
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, bot
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 tre
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 distcl
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
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 u
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 s
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
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]
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 av
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) +
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 tim
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 o
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 (usin
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 ma
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 fe
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
>
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
> 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 myth
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/
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
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
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
Hello all,
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
Good n
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:5
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
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 Nico
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
> up
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] dib070
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
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: [
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-us
68 matches
Mail list logo
