Nova-T 500 kernel module dvb-usb-dib0700 requires options for LNA activation.

Bug #140272 reported by frink
36
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Mythbuntu
Invalid
Medium
Nick Fox
Nominated for 10.04 by Tom Inglis
Nominated for 8.10 by N Carter
Nominated for 9.04 by N Carter
Nominated for 9.10 by N Carter
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Nick Fox

Bug Description

Binary package hint: linux-source-2.6.22

As per this site

http://www.mythtv.org/wiki/index.php/Hauppauge_WinTV_Nova-T_500_PCI

The Nova-T 500 requires the option

 options dvb-usb-dib0700 force_lna_activation=1

in /etc/modprobe.d/options to activate the on board LNA. You almost always need the LNA activated so it would be nice if it were done by default.

Tags: cft-2.6.27
Revision history for this message
Nick Fox (nickj-fox) wrote :

Research is being started on finding the required packages and options for fixing this

Changed in linux-source-2.6.22:
assignee: nobody → nickj-fox
status: New → In Progress
Revision history for this message
Nick Fox (nickj-fox) wrote :

0.15-0ubuntu1 :: mythbuntu-lirc-generator

This release adds support for auto config of this remote. However the kernel modules and such are not supported as of yet. this work is still being researched.

Changed in mythbuntu:
assignee: nobody → nickj-fox
milestone: none → 8.04-alpha1
Revision history for this message
remybig (remybig) wrote :

with AVerTV DVB-T Volar X (A815) no firmware valid
on gutsy no detected
on hardy / (sony vaio laptop ) freeze if we plug more 1 periph on usb

sorry for my english

http://www.avermedia.com/avertv/Support/Download.aspx?Type=APDriver&tab=APDriver&id=39

Revision history for this message
laga (laga) wrote :

According to comments in the #mythtv-users channel, this is still a problem in Ubuntu Hardy.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Care to confirm this is still an issue with the latest Alpha for the upcoming Intrepid Ibex 8.10 which has a 2.6.26 based kernel. More information regarding the latest Alpha for Intrepid can be found at http://www.ubuntu.com/testing. Please let us know your results.

Also, this report will remain open against the actively developed kernel bug against 2.6.22 this does not qualify for a Stable Release Update and will be closed - http://wiki.ubuntu.com/StableReleaseUpdates . Thanks.

Changed in linux:
status: New → Incomplete
Changed in linux-source-2.6.22:
status: In Progress → Won't Fix
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

laga (laga)
Changed in mythbuntu:
milestone: 8.04-alpha1 → 8.10-beta
Thomas Mashos (tgm4883)
Changed in mythbuntu:
status: New → Incomplete
Revision history for this message
graingert (tagrain) wrote :

The new kernel is even WORSE!! ubuntu 8.10 recognises the card as something else, with only one tuner; this does not work at all!

Revision history for this message
MarcRandolph (mrand) wrote :

Removing 8.10 milestone since there are reports of it not being fixed

Changed in mythbuntu:
milestone: 8.10-beta → none
status: Incomplete → Confirmed
Changed in linux:
status: Incomplete → Confirmed
Revision history for this message
Nick Fox (nickj-fox) wrote :

This will need re-tested again in Karmic to see if the newer kernel is still affected by the issue.

Changed in mythbuntu:
status: Confirmed → Incomplete
Revision history for this message
jonny (jonny-jonespenarth) wrote :

I confirm that this bug still affects Karmic, kernel 2.6.31-15-generic with a Hauppauge WinTV Nova-T 500 DVB-T tuner card. However, the remedy has changed slightly from earlier reports.

The fix now requires the configuration directive to be enteretd in /etc/modprobe.d/options.conf (note the extra .conf on the filename that wasn't required for earlier kernel versions). The configuration file file should contain this line:

options dvb-usb-dib0700 force_lna_activation=1

Revision history for this message
Thomas Mashos (tgm4883) wrote :

Thank you for helping to improve Mythbuntu by opening this ticket. I am marking this ticket as confirmed because it appears to have enough information to help the developers understand the problem. It is possible I am wrong and another more experienced triager or developer may adjust the status of the ticket to "incomplete" and request additional information.

Changed in mythbuntu:
status: Incomplete → Triaged
importance: Undecided → Medium
Revision history for this message
Tom Inglis (tominglis) wrote :

I can confirm that this is still an issue in Mythbuntu 10.04.

Revision history for this message
Tom Inglis (tominglis) wrote :

I should also point out that unless you do a cold reboot (shutting down and powering off, then powering on and starting up), the change in the options.conf file will not necessarily have an effect.

Revision history for this message
Nick Fox (nickj-fox) wrote :

Marking Invalid. If this is still a bug it needs retested. Far too much has changed to use the info in this bug to go off of.

Changed in mythbuntu:
status: Triaged → Invalid
Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.