v4l-dvb module broken and outdated

Bug #583717 reported by quequotion
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

The v4l-dvb module in Lucid is broken.
This bug has been confirmed upstream: http://ivtvdriver.org/pipermail/ivtv-users/2010-February/subject.html
 (see thread "Audio Gone?")

Due to an initialization error, some capture card sound processors are mistaken as IR recievers. The result is a capture card that captures video only. No audio is processed at all.

This was fixed quite a while ago, but ubuntu still uses the outdated, broken module. The same module was used for Karmic.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi quequotion,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 583717

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
quequotion (quequotion) wrote :

Perhaps I didn't make myself clear in my initial post, by "the same module was used for Karmic" I meant the module used in Lucid is exactly the same as the module used in Karmic and it is just as broken as it was last year.

This problem still exists in Lucid and still has the same solution as it did in Karmic: compile the modulde from the SVN or latest release and install manually.

A bug introduced into the driver last year, which causes a certain type of chip to be misdetected as an infrared transevier, was present in the version Ubuntu copied from Debian when building Karmic. It is still present in Lucid.

Again, please check this link and read the thread "Audio Gone?" (full details, confirmation from the developers, etc): http://ivtvdriver.org/pipermail/ivtv-users/2010-February/subject.html

Revision history for this message
quequotion (quequotion) wrote :

by the way the kernel logs and upstream testing you want are also in that thread. I don't want to be redundant so please take a look at the link.

tags: added: kernel-core kernel-needs-review
removed: needs-kernel-logs needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
tags: added: kernel-reviewed
removed: kernel-needs-review
Revision history for this message
penalvch (penalvch) wrote :

quequotion, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

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

Other bug subscribers

Remote bug watches

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