[linux-dvb] dib0700 remote control support fixed

[linux-dvb] dib0700 remote control support fixed

[Devin Heitmueller]

After seeing some recent edits to the LinuxTV DVB wiki, I think it is
probably worth a more general announcement:

http://www.linuxtv.org/wiki/index.php?title=Template:Firmware:dvb-usb-dib0700&curid=3008&diff=17297&oldid=17296

The dib0700 remote control problem that people were seeing with
firmware 1.20 has been fixed.  It was checked in at hg 9640, and will
work "out of the box" with no need to play with modprobe options.

Those of you still having problems should update to the latest v4l-dvb
code.  If you still have issues, please feel free to email me and I
will investigate.

Thank you,

Devin

-- 
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

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

Re: [linux-dvb] dib0700 remote control support fixed

[petercarm]

I'll do a test build in the next hour or so and confirm behaviour with:

- a Hauppauge Nova-T 500 (PCI)
- a Hauppauge Nova-TD USB stick

This will be my test gentoo system built from scratch with 2.6.25. 
Everything apart from remote was working correctly until I pulled a
recent version down from mercurial.  My last build, based on Mercurial
from a few days ago has got my Nova-T 500 bitching away with i2c errors
if I stop of the lirc daemon.

On Thu, 20 Nov 2008 10:14:43 -0500, "Devin Heitmueller"
<devin.heitmueller@gmail.com> said:
> After seeing some recent edits to the LinuxTV DVB wiki, I think it is
> probably worth a more general announcement:
> 
> http://www.linuxtv.org/wiki/index.php?title=Template:Firmware:dvb-usb-dib0700&curid=3008&diff=17297&oldid=17296
> 
> The dib0700 remote control problem that people were seeing with
> firmware 1.20 has been fixed.  It was checked in at hg 9640, and will
> work "out of the box" with no need to play with modprobe options.
> 
> Those of you still having problems should update to the latest v4l-dvb
> code.  If you still have issues, please feel free to email me and I
> will investigate.
> 
> Thank you,
> 
> Devin
> 
> -- 
> Devin J. Heitmueller
> http://www.devinheitmueller.com
> AIM: devinheitmueller
> 
> _______________________________________________
> 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] dib0700 remote control support fixed

[Devin Heitmueller]

On Thu, Nov 20, 2008 at 3:39 PM, petercarm
<linuxtv@hotair.fastmail.co.uk> wrote:
> I'll do a test build in the next hour or so and confirm behaviour with:
>
> - a Hauppauge Nova-T 500 (PCI)
> - a Hauppauge Nova-TD USB stick
>
> This will be my test gentoo system built from scratch with 2.6.25.
> Everything apart from remote was working correctly until I pulled a
> recent version down from mercurial.  My last build, based on Mercurial
> from a few days ago has got my Nova-T 500 bitching away with i2c errors
> if I stop of the lirc daemon.

The fix only went in on Sunday evening, so it's not surprising if you
had the issue with a relatively recent build.

Please do report back regarding how your testing goes.  Note that you
should not have any module options setup when you do the testing.

Thanks,

Devin

-- 
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

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

Re: [linux-dvb] dib0700 remote control support fixed

[petercarm]

OK it is working on the Nova-T 500 but it is throwing up "Unknown remote
controller key" messages in dmesg in amongst correctly processing the
correct key presses.  I'll try using irrecord to work on a new
lircd.conf and see if it goes away.


On Thu, 20 Nov 2008 15:46:56 -0500, "Devin Heitmueller"
<devin.heitmueller@gmail.com> said:
> On Thu, Nov 20, 2008 at 3:39 PM, petercarm
> <linuxtv@hotair.fastmail.co.uk> wrote:
> > I'll do a test build in the next hour or so and confirm behaviour with:
> >
> > - a Hauppauge Nova-T 500 (PCI)
> > - a Hauppauge Nova-TD USB stick
> >
> > This will be my test gentoo system built from scratch with 2.6.25.
> > Everything apart from remote was working correctly until I pulled a
> > recent version down from mercurial.  My last build, based on Mercurial
> > from a few days ago has got my Nova-T 500 bitching away with i2c errors
> > if I stop of the lirc daemon.
> 
> The fix only went in on Sunday evening, so it's not surprising if you
> had the issue with a relatively recent build.
> 
> Please do report back regarding how your testing goes.  Note that you
> should not have any module options setup when you do the testing.
> 
> Thanks,
> 
> Devin
> 
> -- 
> Devin J. Heitmueller
> http://www.devinheitmueller.com
> AIM: devinheitmueller

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

Re: [linux-dvb] dib0700 remote control support fixed

[Devin Heitmueller]

On Thu, Nov 20, 2008 at 7:40 PM, petercarm
<linuxtv@hotair.fastmail.co.uk> wrote:
> OK it is working on the Nova-T 500 but it is throwing up "Unknown remote
> controller key" messages in dmesg in amongst correctly processing the
> correct key presses.  I'll try using irrecord to work on a new
> lircd.conf and see if it goes away.

Hello Peter,

Please stop top posting - it is a violation of mailing list policy.

Lirc is not required for this device.  It is automatically hooked into
the keyboard driver.

Which remote control are you using?

Devin

-- 
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

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

[linux-dvb] Hauppauge Nova T 500, dvb-usb: error while enabling fifo.

[Robert Watkins]

Hello,

I've been using a Hauppauge Nova T 500 for a while using Ubtuntu Hardy
with an occasional "mt2060 I2C read failed" error, but it's been
tolerable.

After upgrading to Intrepid Ibex it's now failing the instant the second
tuner kicks in. A reboot doesn't fix the problem. I have to shutdown and
start from cold to clear the error.

Any help would be greatly appreciated.

I've read the recent threads on the subject at
http://www.linuxtv.org/pipermail/linux-dvb/2008-June/026715.html
http://www.linuxtv.org/pipermail/linux-dvb/2008-February/023738.html
and many older ones.

I've installed the lasted drivers and firmware from
http://linuxtv.org/hg/v4l-dvb

I've add the following to /etc/modprobe.d/options
	options dvb-usb-dib0700 force_lna_activation=1
	options dvb_usb disable_rc_polling=1
	options usbcore autosuspend=-1
and follows the instructions at
http://www.blackberryforums.com/linux-users-corner/97661-enable-disable-config_usb_suspend-s-autosuspend-mode.html to rebuild the initrd for my kernel.

I've tried the dvb-usb-dib0700-1.20.fw and dvb-usb-dib0700-1.10.fw
firmware.

I've edited my mythtv setting in accordance with the instructions at
http://www.youplala.net/linux/home-theater-pc#toc-not-losing-one-of-the-nova-t-500s-tuners

If I "echo on > /sys/usb_device/.../device/power/level" to all the usb
devices set to auto, then I don't seem to get the mt2060 errors. (I
waited 10 minutes and it never turned up.)

However I still get
	[ 1661.529152] dvb-usb: error while enabling fifo.
within seconds of the second tuner starting to record, and Mythtv then
locks up.

(The current driver fixes all the problems I had with uvcvideo and the
USB microphone on my Logitech QuickCam Pro 9000, so I really want to
upgrade.)

I would appreciate any clue on what to try next.

Regards and Best Wishes,
Robert Watkins

P.S.

The firmware often fails to load first time.

[   24.192100] dib0700: loaded with support for 8 different device-types
[   24.193512] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in
cold state, will try to load a firmware
[   24.193523] firmware: requesting dvb-usb-dib0700-1.20.fw
[   24.346192] input: PC Speaker
as /devices/platform/pcspkr/input/input5
[   25.808218] dvb-usb: downloading firmware from file
'dvb-usb-dib0700-1.20.fw'
[   26.936250] dib0700: firmware download failed at 17248 with -110
[   26.936354] usbcore: registered new interface driver dvb_usb_dib0700
...

unloading the modules followed by modprobe dvb-usb-dib0700 always fixes
it.

[   81.023443] usbcore: deregistering interface driver dvb_usb_dib0700
[   81.203808] dib0700: loaded with support for 8 different device-types
[   81.205974] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in
cold state, will try to load a firmware
[   81.205988] firmware: requesting dvb-usb-dib0700-1.20.fw
[   81.216530] dvb-usb: downloading firmware from file
'dvb-usb-dib0700-1.20.fw'
[   81.434123] dib0700: firmware started successfully.
[   81.936060] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in
warm state.
[   81.936153] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[   81.936504] DVB: registering new adapter (Hauppauge Nova-T 500 Dual
DVB-T)
[   82.056946] DVB: registering adapter 0 frontend 0 (DiBcom
3000MC/P)...
[   82.125910] MT2060: successfully identified (IF1 = 1229)
[   82.623250] dvb-usb: will pass the complete MPEG2 transport stream to
the software demuxer.
[   82.623487] DVB: registering new adapter (Hauppauge Nova-T 500 Dual
DVB-T)
[   82.632653] DVB: registering adapter 1 frontend 0 (DiBcom
3000MC/P)...
[   82.637883] MT2060: successfully identified (IF1 = 1217)
[   83.205318] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully
initialized and connected.
[   83.205632] usbcore: registered new interface driver dvb_usb_dib0700
[ 1661.529152] dvb-usb: error while enabling fifo.


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

Re: [linux-dvb] dib0700 remote control support fixed

[Devin Heitmueller]

On Thu, Nov 20, 2008 at 7:40 PM, petercarm
<linuxtv@hotair.fastmail.co.uk> wrote:
> OK it is working on the Nova-T 500 but it is throwing up "Unknown remote
> controller key" messages in dmesg in amongst correctly processing the
> correct key presses.  I'll try using irrecord to work on a new
> lircd.conf and see if it goes away.

Hello Peter,

I am following up on your issue with your Nova-T 500.  I noticed the
following update to the linuxtv.org wiki:

http://www.linuxtv.org/wiki/index.php?title=Template:Firmware:dvb-usb-dib0700&curid=3008&diff=18052&oldid=17297

If there is a problem with the dib0700 1.20 firmware, I would like to
get to the bottom of it (and get Patrick Boettcher involved as
necessary).  I am especially concerned since this code is going into
2.6.27 and the behavior you are describing could definitely be
considered a regression.

As far as I have heard, most people have reported considerable
improvement with the 1.20 firmware, including users of the Nova-T 500.
 So I would like to better understand what is different about your
environment.

Could you please summarize the results of your testing on both
devices?  In particular, there should be no lircd involved, as this
device should be sending keystrokes directly via the kernel.

Thanks,

Devin

-- 
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

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

Re: [linux-dvb] dib0700 remote control support fixed

[petercarm]

On Sun, 30 Nov 2008 23:59:51 -0500, "Devin Heitmueller"
<devin.heitmueller@gmail.com> said:
> On Thu, Nov 20, 2008 at 7:40 PM, petercarm
> <linuxtv@hotair.fastmail.co.uk> wrote:
> > OK it is working on the Nova-T 500 but it is throwing up "Unknown remote
> > controller key" messages in dmesg in amongst correctly processing the
> > correct key presses.  I'll try using irrecord to work on a new
> > lircd.conf and see if it goes away.
> 
> Hello Peter,
> 
> I am following up on your issue with your Nova-T 500.  I noticed the
> following update to the linuxtv.org wiki:
> 
> http://www.linuxtv.org/wiki/index.php?title=Template:Firmware:dvb-usb-dib0700&curid=3008&diff=18052&oldid=17297
> 
> If there is a problem with the dib0700 1.20 firmware, I would like to
> get to the bottom of it (and get Patrick Boettcher involved as
> necessary).  I am especially concerned since this code is going into
> 2.6.27 and the behavior you are describing could definitely be
> considered a regression.
> 
> As far as I have heard, most people have reported considerable
> improvement with the 1.20 firmware, including users of the Nova-T 500.
>  So I would like to better understand what is different about your
> environment.

First off I'd like to point out that I had considerable success with fw
1.20 and the drivers that I tested on mid-November.  At the time, the
driver had the issues with the repeating remote control messages.  Since
the update (I think November 16th) I have not been able to get a stable
build, suffering from the i2c problem.

My test environment consists of 2 different VIA Epia boards (SP8000 and
CN10000).  I have both a PCI Nova-T 500 2040:9950 and a USB stick
Nova-TD 2040:5200 which are dibcom devices.  I also have a Hauppauge
Nova-T PCI (cx88xx) and a Kworld 399U dual tuner USB stick 1b80:e399
(af9015).

The build is a scripted build of gentoo, built as a livecd (which means
it is very repeatable).  The snapshot of gentoo portage dates from
20081028 which gives me a 2.6.25 kernel.  I'm using gentoo-sources so I
get 2.6.25-gentoo-r7.

In one of my previous posts I mentioned that I am testing remote control
functionality using lirc.  This is using devinput and allows me to
abstract the key bindings for different applications.

What else can I tell you?

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

Re: [linux-dvb] dib0700 remote control support fixed

[Devin Heitmueller]

On Mon, Dec 1, 2008 at 12:31 PM, petercarm
<linuxtv@hotair.fastmail.co.uk> wrote:
> On Sun, 30 Nov 2008 23:59:51 -0500, "Devin Heitmueller"
> <devin.heitmueller@gmail.com> said:
>> On Thu, Nov 20, 2008 at 7:40 PM, petercarm
>> <linuxtv@hotair.fastmail.co.uk> wrote:
>> > OK it is working on the Nova-T 500 but it is throwing up "Unknown remote
>> > controller key" messages in dmesg in amongst correctly processing the
>> > correct key presses.  I'll try using irrecord to work on a new
>> > lircd.conf and see if it goes away.
>>
>> Hello Peter,
>>
>> I am following up on your issue with your Nova-T 500.  I noticed the
>> following update to the linuxtv.org wiki:
>>
>> http://www.linuxtv.org/wiki/index.php?title=Template:Firmware:dvb-usb-dib0700&curid=3008&diff=18052&oldid=17297
>>
>> If there is a problem with the dib0700 1.20 firmware, I would like to
>> get to the bottom of it (and get Patrick Boettcher involved as
>> necessary).  I am especially concerned since this code is going into
>> 2.6.27 and the behavior you are describing could definitely be
>> considered a regression.
>>
>> As far as I have heard, most people have reported considerable
>> improvement with the 1.20 firmware, including users of the Nova-T 500.
>>  So I would like to better understand what is different about your
>> environment.
>
> First off I'd like to point out that I had considerable success with fw
> 1.20 and the drivers that I tested on mid-November.  At the time, the
> driver had the issues with the repeating remote control messages.  Since
> the update (I think November 16th) I have not been able to get a stable
> build, suffering from the i2c problem.
>
> My test environment consists of 2 different VIA Epia boards (SP8000 and
> CN10000).  I have both a PCI Nova-T 500 2040:9950 and a USB stick
> Nova-TD 2040:5200 which are dibcom devices.  I also have a Hauppauge
> Nova-T PCI (cx88xx) and a Kworld 399U dual tuner USB stick 1b80:e399
> (af9015).
>
> The build is a scripted build of gentoo, built as a livecd (which means
> it is very repeatable).  The snapshot of gentoo portage dates from
> 20081028 which gives me a 2.6.25 kernel.  I'm using gentoo-sources so I
> get 2.6.25-gentoo-r7.
>
> In one of my previous posts I mentioned that I am testing remote control
> functionality using lirc.  This is using devinput and allows me to
> abstract the key bindings for different applications.
>
> What else can I tell you?

Hello Peter,

Of the devices that you have, which are the ones that are failing?
Both of the dibcom devices?

I am not familiar with how lirc interacts with the dib0700 driver,
since the driver polls the bulk endpoint every 50ms and injects the
keys directly.  I will have to look at the driver and see how this
hooks into lirc.

I suspect that most people are not using lirc at all, since the device
works without it.  This would explain why you are the only person I
know of still reporting these problems.

Could you please send my your lirc configuration so I can attempt to
reproduce the issue locally?  If I can get an environment that
reproduces the issue, I can almost certainly fix it.

Thanks,

Devin

-- 
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

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

Re: [linux-dvb] dib0700 remote control support fixed

[petercarm]

On Mon, 1 Dec 2008 13:54:19 -0500, "Devin Heitmueller"
<devin.heitmueller@gmail.com> said:
> Hello Peter,
> 
> Of the devices that you have, which are the ones that are failing?
> Both of the dibcom devices?
> 
> I am not familiar with how lirc interacts with the dib0700 driver,
> since the driver polls the bulk endpoint every 50ms and injects the
> keys directly.  I will have to look at the driver and see how this
> hooks into lirc.
> 
> I suspect that most people are not using lirc at all, since the device
> works without it.  This would explain why you are the only person I
> know of still reporting these problems.
> 
> Could you please send my your lirc configuration so I can attempt to
> reproduce the issue locally?  If I can get an environment that
> reproduces the issue, I can almost certainly fix it.
> 
> Thanks,
> 
> Devin
> 
> -- 
> Devin J. Heitmueller
> http://www.devinheitmueller.com
> AIM: devinheitmueller

Just to add a bit more clarity.

The LIRC project provides drivers for otherwise unsupported RC hardware.
 For dvb-usb receivers it just piggybacks off the /dev/input device
file.  No driver from LIRC is used.  The LIRC involvement is purely in
userspace.  This is not a LIRC problem.  The problem arises whether or
not lircd is started.

The problem is suppressed if the disable_rc_polling parameter in dvb_usb
is set to 1 but obviously this disables all RC support.

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

Re: [linux-dvb] dib0700 remote control support fixed

[Devin Heitmueller]

On Mon, Dec 1, 2008 at 3:13 PM, petercarm <linuxtv@hotair.fastmail.co.uk> wrote:
> The LIRC project provides drivers for otherwise unsupported RC hardware.
>  For dvb-usb receivers it just piggybacks off the /dev/input device
> file.  No driver from LIRC is used.  The LIRC involvement is purely in
> userspace.  This is not a LIRC problem.  The problem arises whether or
> not lircd is started.

I recognize that lirc is purely in userspace, but it would be
desirable to setup a comparable environment that polls the /dev/input
device so I can attempt to reproduce the behavior locally.

That's interesting that it occurs even if lircd is not running.

> The problem is suppressed if the disable_rc_polling parameter in dvb_usb
> is set to 1 but obviously this disables all RC support.

This whole situation is suspicious since the IR polling has no
interaction with the i2c subsystem.  In fact, it no longer even uses
the same request endpoint.

Can you provide any quantitative data as to the frequency of failure
and under what circumstances this occurs?  Does it prevent tuning from
succeeding, or do you lose lock after the device is capturing?  Do you
see i2c errors when not capturing?  How often do the errors occur?
Are you unable to get tuning lock in 100% of attempts?  Are the i2c
errors always against the mt2060, or are you seeing other i2c errors
as well?

You mentioned that "The Nova-T 500 and the Nova TD USB stick are the
two dibcom devices".  I realize this, but my question was, are you
seeing failure with both of these two devices, and are these the only
two devices you see errors with?

Devin

-- 
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

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

Re: [linux-dvb] dib0700 remote control support fixed

[petercarm]

Hi Devin,

I've just got lucky with running dmesg at the onset of the problem, so
can see the initial messages rather than just the flood of read/write
failures.

Unfortunately I've only got it in my xterm buffer, so I've posted some
screenshots here:

http://linuxtv.hotair.fastmail.co.uk/Picture%203.jpg
http://linuxtv.hotair.fastmail.co.uk/Picture%204.jpg

It looks like it is crashing IRQ 10 which is assigned to the PCI bus.  

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

Re: [linux-dvb] dib0700 remote control support fixed

[Devin Heitmueller]

On Mon, Dec 1, 2008 at 3:40 PM, petercarm <linuxtv@hotair.fastmail.co.uk> wrote:
> Hi Devin,
>
> I've just got lucky with running dmesg at the onset of the problem, so
> can see the initial messages rather than just the flood of read/write
> failures.
>
> Unfortunately I've only got it in my xterm buffer, so I've posted some
> screenshots here:
>
> http://linuxtv.hotair.fastmail.co.uk/Picture%203.jpg
> http://linuxtv.hotair.fastmail.co.uk/Picture%204.jpg
>
> It looks like it is crashing IRQ 10 which is assigned to the PCI bus.

Woah.  You didn't mention it was doing a panic.

I'm not sure what is going on there.  You're getting errors in
af9013/af9016, so it's not specific to the mt2060 like other people
were reporting issues.

I'll look at the backtrace tonight and see if I can figure out what
happened.  In the meantime, could you please update to the hg
immediately before and after the November 16th changeset and confirm
that IR change definitely caused the issue?

Thanks,

Devin


-- 
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

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

Re: [linux-dvb] dib0700 remote control support fixed

[petercarm]

On Mon, 1 Dec 2008 15:47:54 -0500, "Devin Heitmueller"
<devin.heitmueller@gmail.com> said:
> 
> Woah.  You didn't mention it was doing a panic.
> 
> I'm not sure what is going on there.  You're getting errors in
> af9013/af9016, so it's not specific to the mt2060 like other people
> were reporting issues.
> 
> I'll look at the backtrace tonight and see if I can figure out what
> happened.  In the meantime, could you please update to the hg
> immediately before and after the November 16th changeset and confirm
> that IR change definitely caused the issue?

I've since removed the Kworld (Afatech device) and it is still doing the
same on reboot.

The problems can be reproduced with just the Nova-T 500.  The same OS
image runs fine on boxes running with the afatech and connexant devices
I have available.  It will take me a while to re-arrange my test
hardware to test the Nova-TD in isolation.

I'll go back to the rev 9638, as you suggest.  Again, it will take me
overnight to get that sorted.

I'm signing off for a couple of hours now but I am as keen to get to the
bottom of this as you.

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

Re: [linux-dvb] dib0700 remote control support fixed

[Darren Salt]

I demand that petercarm may or may not have written...

> I've just got lucky with running dmesg at the onset of the problem, so can
> see the initial messages rather than just the flood of read/write failures.

> Unfortunately I've only got it in my xterm buffer, so I've posted some
> screenshots here:

If it's displayed in an X terminal, it's saveable as a text file:
drag-select, "xclip >foo". If it's somewhere in /var/log, use $EDITOR to save
part of the file somewhere user-readable.

You have no excuse for using screenshots. :-)

[snip]
-- 
| Darren Salt    | linux or ds at              | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
|   Kill all extremists!

You will be awarded the Nobel Peace Prize. Posthumously.

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

Re: [linux-dvb] dib0700 remote control support fixed

[petercarm]

On Tue, 02 Dec 2008 14:35:24 +0000, "Darren Salt"
<linux@youmustbejoking.demon.co.uk> said:
> I demand that petercarm may or may not have written...
> 
> > I've just got lucky with running dmesg at the onset of the problem, so can
> > see the initial messages rather than just the flood of read/write failures.
> 
> > Unfortunately I've only got it in my xterm buffer, so I've posted some
> > screenshots here:
> 
> If it's displayed in an X terminal, it's saveable as a text file:
> drag-select, "xclip >foo". If it's somewhere in /var/log, use $EDITOR to
> save
> part of the file somewhere user-readable.
> 
> You have no excuse for using screenshots. :-)
> 

;-)

I guess that as a some-time project manager I appreciate the merits of
getting something completed rather than applying finesse to a job of
zero importance.

(Minimal livecd build.  No xclip.)

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

Re: [linux-dvb] dib0700 remote control support fixed

[petercarm]

I've been busy testing and I have an apology to make.

It looks like the problem is with a riser card.  When I moved the Nova-T
500 to an identical VIA SP8000 in a case that allowed a direct fitting
PCI card, the problems stabilized.

This does explain why I was the only one seeing these problems.  Curious
that the card was stable for DVB functions if the RC polling was
disabled.  I will amend the wiki to make sure it reflects the current
status of the driver.

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

Re: [linux-dvb] dib0700 remote control support fixed

[Devin Heitmueller]

On Tue, Dec 2, 2008 at 4:49 PM, petercarm <linuxtv@hotair.fastmail.co.uk> wrote:
> I've been busy testing and I have an apology to make.
>
> It looks like the problem is with a riser card.  When I moved the Nova-T
> 500 to an identical VIA SP8000 in a case that allowed a direct fitting
> PCI card, the problems stabilized.
>
> This does explain why I was the only one seeing these problems.  Curious
> that the card was stable for DVB functions if the RC polling was
> disabled.  I will amend the wiki to make sure it reflects the current
> status of the driver.

Well, I'm just breathing a sigh of relief - I had no idea how I was
going to debug this issue.

My only guess is that there is probably little or no recurring traffic
on the bus when idle, but that changes with the addition of the RC
polling (requests every 50ms).

Thanks for taking the time to isolate the cause of the problem.

Devin

-- 
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

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

Re: [linux-dvb] dib0700 remote control support fixed

[petercarm]

More testing.

Moving on from the riser card issue, I've now got a fairly predictable
case where warm restart of the box results in endless mt2060 i2c errors.

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

Re: [linux-dvb] dib0700 remote control support fixed

[Devin Heitmueller]

On Wed, Dec 3, 2008 at 10:30 AM, petercarm
<linuxtv@hotair.fastmail.co.uk> wrote:
> More testing.
>
> Moving on from the riser card issue, I've now got a fairly predictable
> case where warm restart of the box results in endless mt2060 i2c errors.
>

Hello Peter,

Just to be clear, this is in a box that doesn't have the riser card?

Does it happen even before you start streaming video?  Or does it
occur when you do the first tune?

Can you please provide a detailed explanation regarding what that
"fairly predictable case" is?

Thanks,

Devin


-- 
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

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

Re: [linux-dvb] dib0700 remote control support fixed

[petercarm]

On Wed, 3 Dec 2008 10:34:02 -0500, "Devin Heitmueller"
<devin.heitmueller@gmail.com> said:
> On Wed, Dec 3, 2008 at 10:30 AM, petercarm
> <linuxtv@hotair.fastmail.co.uk> wrote:
> > More testing.
> >
> > Moving on from the riser card issue, I've now got a fairly predictable
> > case where warm restart of the box results in endless mt2060 i2c errors.
> >
> 
> Hello Peter,
> 
> Just to be clear, this is in a box that doesn't have the riser card?
> 
> Does it happen even before you start streaming video?  Or does it
> occur when you do the first tune?
> 
> Can you please provide a detailed explanation regarding what that
> "fairly predictable case" is?
> 
> Thanks,
> 
> Devin

This is the case without the riser.  The log showed the failure 8
seconds after the driver initialized.  Mythtv backend may have started
in the meantime, but had no current jobs.  It may be related to EIT
scanning.

So far three times out of four it has failed on issuing "reboot".  It
has worked every time with a power down before restarting.  I'm doing a
clean rebuild of the complete test environment to eliminate any cached
results, just in case.  This will take about 8 hours.

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

Re: [linux-dvb] dib0700 remote control support fixed

[Devin Heitmueller]

On Wed, Dec 3, 2008 at 11:27 AM, petercarm
<linuxtv@hotair.fastmail.co.uk> wrote:
>
> On Wed, 3 Dec 2008 10:34:02 -0500, "Devin Heitmueller"
> <devin.heitmueller@gmail.com> said:
>> On Wed, Dec 3, 2008 at 10:30 AM, petercarm
>> <linuxtv@hotair.fastmail.co.uk> wrote:
>> > More testing.
>> >
>> > Moving on from the riser card issue, I've now got a fairly predictable
>> > case where warm restart of the box results in endless mt2060 i2c errors.
>> >
>>
>> Hello Peter,
>>
>> Just to be clear, this is in a box that doesn't have the riser card?
>>
>> Does it happen even before you start streaming video?  Or does it
>> occur when you do the first tune?
>>
>> Can you please provide a detailed explanation regarding what that
>> "fairly predictable case" is?
>>
>> Thanks,
>>
>> Devin
>
> This is the case without the riser.  The log showed the failure 8
> seconds after the driver initialized.  Mythtv backend may have started
> in the meantime, but had no current jobs.  It may be related to EIT
> scanning.
>
> So far three times out of four it has failed on issuing "reboot".  It
> has worked every time with a power down before restarting.  I'm doing a
> clean rebuild of the complete test environment to eliminate any cached
> results, just in case.  This will take about 8 hours.

Ok.  That's good to know.  It's possible that the driver does not
clear out all its state when being initialized and the reboot alone
doesn't cut power to the device so there is something that persists
across the reboot.  This would definitely make sense as to why we see
it with this device and not the USB based dib0700 devices.

There are two things that would be useful here I think:

If you can confirm whether the change on November 16th *really* has
anything to do with the failure (by trying snapshots of the v4l-dvb
tree before and after the change).

Add a call to dump_stack() right after the error line in the code, so
we can see what the stack looks like at the time of failure.

I'm glad it's readily reproducible, which will make it easier to
isolate the problem and validate any fix we come up with.

Devin

-- 
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller

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

Re: [linux-dvb] dib0700 remote control support fixed

[Robert Watkins]

[-- Attachment #1.1: Type: text/plain, Size: 1647 bytes --]

On Mon, 2008-12-01 at 17:31 +0000, petercarm wrote:

> First off I'd like to point out that I had considerable success with fw
> 1.20 and the drivers that I tested on mid-November.  At the time, the
> driver had the issues with the repeating remote control messages.  Since
> the update (I think November 16th) I have not been able to get a stable
> build, suffering from the i2c problem.
> 
> My test environment consists of 2 different VIA Epia boards (SP8000 and
> CN10000).  I have both a PCI Nova-T 500 2040:9950 and a USB stick
> Nova-TD 2040:5200 which are dibcom devices.  I also have a Hauppauge
> Nova-T PCI (cx88xx) and a Kworld 399U dual tuner USB stick 1b80:e399
> (af9015).
> 

I too have a PCI Nova-T 500 2040:9950 that works well with the 1.20
firmware and a 2.6.24 kernel and the latest drivers from
http://linuxtv.org/hg/v4l-dvb.
For me kernels 2.6.25 & 2.6.27 have problems. See here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/303667. 


> The build is a scripted build of gentoo, built as a livecd (which means
> it is very repeatable).  The snapshot of gentoo portage dates from
> 20081028 which gives me a 2.6.25 kernel.  I'm using gentoo-sources so I
> get 2.6.25-gentoo-r7.

Can you confirm that 2.6.24 was the last good kernel for a PCI Nova-T
500 2040:9950?


> In one of my previous posts I mentioned that I am testing remote control
> functionality using lirc.  This is using devinput and allows me to
> abstract the key bindings for different applications.
> 
> What else can I tell you?
> 

If you start from cold do you see the same firmware load failure that
I'm seeing?

Regards and Best Wishes,
Robert


[-- Attachment #1.2: Type: text/html, Size: 2140 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

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

Re: [linux-dvb] dib0700 remote control support fixed

[petercarm]

On Mon, 1 Dec 2008 13:54:19 -0500, "Devin Heitmueller"
<devin.heitmueller@gmail.com> said:
> Hello Peter,
> 
> Of the devices that you have, which are the ones that are failing?
> Both of the dibcom devices?
> 
> I am not familiar with how lirc interacts with the dib0700 driver,
> since the driver polls the bulk endpoint every 50ms and injects the
> keys directly.  I will have to look at the driver and see how this
> hooks into lirc.
> 
> I suspect that most people are not using lirc at all, since the device
> works without it.  This would explain why you are the only person I
> know of still reporting these problems.
> 
> Could you please send my your lirc configuration so I can attempt to
> reproduce the issue locally?  If I can get an environment that
> reproduces the issue, I can almost certainly fix it.
> 
> Thanks,
> 
> Devin
> 
> -- 
> Devin J. Heitmueller
> http://www.devinheitmueller.com
> AIM: devinheitmueller

The Nova-T 500 and the Nova TD USB stick are the two dibcom devices.

What output should I be getting from the remote control?  Having
previously seen RC signals coming through on /dev/input I need some
clues for where to look if things have changed.

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