Re: [Bugme-new] [Bug 15087] New: hauppauge nova-t 500 remote controller cause usb halt with Via usb controller

Re: [Bugme-new] [Bug 15087] New: hauppauge nova-t 500 remote controller cause usb halt with Via usb controller

[Andrew Morton]

(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Mon, 18 Jan 2010 21:06:57 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=15087
> 
>            Summary: hauppauge nova-t 500 remote controller cause usb halt
>                     with Via usb controller
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 2.6.32
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: blocking
>           Priority: P1
>          Component: USB
>         AssignedTo: greg@kroah.com
>         ReportedBy: fuffi.il.fuffo@gmail.com
>         Regression: Yes
> 
> 
> This is a know problem with this dvb-t card.
> If the ir receiver is disabled via modprobe option (adding this parameter in
> modprobe.conf: "#options dvb_usb disable_rc_polling=1") I cannot use it but the
> card works perfectly, but if I try to activate it (removing that option) and i
> launch the lircd daemon, I obtain a "usb halt" as described below in this old
> message in the linux-media ml.
> 
> klogd: ehci_hcd 0000:04:00.2: force halt; handhake f8018014 00004000
> 00000000 -> -110
> 
> Here, the writer find the commit that cause this regression:
> http://osdir.com/ml/linux-media/2009-08/msg00185.html
> Here is explained when it was introduced:
> http://osdir.com/ml/linux-media/2009-08/msg00182.html
> 
> It seems that this problem is present only with a via usb controller,
> unfortunately i have this one:
> 
>  lspci | grep -i via
> 01:08.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller (rev 62)
> 01:08.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller (rev 62)
> 01:08.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65)
> 
> Tell me if you need additional info.
> I'm using a 2.6.32 kernel on arch linux.
> Other relevant modprobe options:
> options dib3000mc buggy_sfn_workaround=1
> options dib7000p buggy_sfn_workaround=1
> alias net-pf-10 off
> 

This is a regression.  You have to chase links a bit, but it was
bisected down to a particular commit in
http://linuxtv.org/hg/v4l-dvb/rev/561b447ade77.

Re: [Bugme-new] [Bug 15087] New: hauppauge nova-t 500 remote controller cause usb halt with Via usb controller

[edm]

> (switched to email.  Please respond via emailed reply-to-all, not via the
> bugzilla web interface).

> On Mon, 18 Jan 2010 21:06:57 GMT
> bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote:

> > http://bugzilla.kernel.org/show_bug.cgi?id=15087
> >
> >            Summary: hauppauge nova-t 500 remote controller cause usb halt
> >                     with Via usb controller
> >            Product: Drivers
> >            Version: 2.5
> >     Kernel Version: 2.6.32
> >           Platform: All
> >         OS/Version: Linux
> >               Tree: Mainline
> >             Status: NEW
> >           Severity: blocking
> >           Priority: P1
> >          Component: USB
> >         AssignedTo: greg@xxxxxxxxx
> >         ReportedBy: fuffi.il.fuffo@xxxxxxxxx
> >         Regression: Yes
> >
> >
> > This is a know problem with this dvb-t card.
> > If the ir receiver is disabled via modprobe option (adding this parameter in
> > modprobe.conf: "#options dvb_usb disable_rc_polling=1") I cannot use it but the
> > card works perfectly, but if I try to activate it (removing that option) and i
> > launch the lircd daemon, I obtain a "usb halt" as described below in this old
> > message in the linux-media ml.
> >
> > klogd: ehci_hcd 0000:04:00.2: force halt; handhake f8018014 00004000
> > 00000000 -> -110
> >
> > Here, the writer find the commit that cause this regression:
> > http://osdir.com/ml/linux-media/2009-08/msg00185.html
> > Here is explained when it was introduced:
> > http://osdir.com/ml/linux-media/2009-08/msg00182.html
> >
> > It seems that this problem is present only with a via usb controller,
> > unfortunately i have this one:
> >
> >  lspci | grep -i via
> > 01:08.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> > Controller (rev 62)
> > 01:08.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> > Controller (rev 62)
> > 01:08.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65)
> >
> > Tell me if you need additional info.
> > I'm using a 2.6.32 kernel on arch linux.
> > Other relevant modprobe options:
> > options dib3000mc buggy_sfn_workaround=1
> > options dib7000p buggy_sfn_workaround=1
> > alias net-pf-10 off
> >
>
> This is a regression.  You have to chase links a bit, but it was
> bisected down to a particular commit in
> http://linuxtv.org/hg/v4l-dvb/rev/561b447ade77.

Hi, using the last version of v4l-dvb driver from hg, solved this
issue. I tested the card in the last days and it seems to work well
now; the IR receiver works, I tested it using irw, all the keys are
recognised.
I can't test the IR receiver with a specific program because the
.lircrc is ignored but I think it's a gnome-related problem :)
Is the option "dvb_usb_dib0700 force_lna_activation=1" still
necessary? Why this option is not activated at default?

Thank you.

Re: [Bugme-new] [Bug 15087] New: hauppauge nova-t 500 remote controller cause usb halt with Via usb controller

[Devin Heitmueller]

On Sat, Feb 6, 2010 at 12:14 PM, edm <fuffi.il.fuffo@gmail.com> wrote:
>> (switched to email.  Please respond via emailed reply-to-all, not via the
>> bugzilla web interface).

<snip>

> Hi, using the last version of v4l-dvb driver from hg, solved this
> issue. I tested the card in the last days and it seems to work well
> now; the IR receiver works, I tested it using irw, all the keys are
> recognised.
> I can't test the IR receiver with a specific program because the
> .lircrc is ignored but I think it's a gnome-related problem :)
> Is the option "dvb_usb_dib0700 force_lna_activation=1" still
> necessary? Why this option is not activated at default?

Hello edm,

Sorry for the delayed response on this.

Glad to hear it's now working for you.

With regards to the force_lna_activation option, this was never
actually related to the dib0700 firmware changes.  That option simply
may or may not be required depending on what your signal conditions
are.  Enabling the low noise amplifier is something that you will
typically do only if your signal conditions are poor, which is why it
is not enabled by default.

The fix referred to in this bug report was strictly for the dib0700
problem introduced as a result to changes for IR required to support
the 1.20 firmware.

Cheers,

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com