tv tuner card with saa7134 not detected automatically

Bug #86217 reported by Renjoy
42
Affects Status Importance Assigned to Milestone
linux (Baltix)
New
Undecided
Unassigned
linux (Ubuntu)
Won't Fix
Medium
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Mercury TV tuner card with SAA7134 chip is not detected automatically.

The website for the product follows:
http://www.mercury-pc.com/product-detail.php?link=p-addcards&subtitle=Add-On%20Cards&productid=97

The module saa7134 is loaded with the card and tuner paramters to be the default.

As per page http://gentoo-wiki.com/HARDWARE_saa7134 it says to modprobe saa7134 with card=2 and tuner=3, and it works.

But it is not detected automatically.

Tags: cft-2.6.27
Revision history for this message
Renjoy (renjoy) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for your bug report. Could you please also add the full output of 'lspci -vvnn' to your bug report as an attachment? Thanks in advance.

Revision history for this message
Renjoy (renjoy) wrote : Re: [Bug 86217] Re: tv tuner card with saa7134 not detected automatically

Hi Brian,Sorry for the delay.
I have attached lspci output.
Also the remote doesnt work fully.

I am using tvtime to view tv.
Please let me know if you need any more details.
I was out of town for last 2 weeks. But hereon you can expect quick replies.

On 2/21/07, Brian Murray <email address hidden> wrote:
>
> Thanks for your bug report. Could you please also add the full output
> of 'lspci -vvnn' to your bug report as an attachment? Thanks in
> advance.
>
> ** Changed in: Ubuntu
> Sourcepackagename: None => linux-source-2.6.20
> Assignee: (unassigned) => Brian Murray
> Status: Unconfirmed => Needs Info
>
> --
> tv tuner card with saa7134 not detected automatically
> https://launchpad.net/bugs/86217
>

--
Regards

Renjoy Henry

Revision history for this message
Brian Murray (brian-murray) wrote :

The output of 'sudo lspci -vv' and 'sudo lspci -vvn' doesn't seem to be in your bug report. Please visit the bugs web page and add them. Thanks again.

Revision history for this message
Renjoy (renjoy) wrote :
Revision history for this message
Renjoy (renjoy) wrote :
Changed in linux-source-2.6.20:
assignee: brian-murray → ubuntu-kernel-team
status: Needs Info → Confirmed
Revision history for this message
Julian Alarcon (julian-alarcon) wrote :

I also have a Global TV Terminator tuner card with SAA7134. And happen the same.. since I remember (Dapper) and until here (Gutsy).
The steps to config this card are here:
http://gentoo-wiki.com/HARDWARE_saa7134

Revision history for this message
Brian Murray (brian-murray) wrote :

This doesn't meet the criteria for a Stable Release Update but we will and try and get it fixed for Gutsy. Thanks!

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Triaged
Changed in linux-source-2.6.20:
assignee: ubuntu-kernel-team → nobody
status: Confirmed → Won't Fix
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Guys,

I'm going to carry this bug forward to the upcoming Intrepid Ibex 8.10 release. However, against 2.6.22 this will be closed as it doesn't qualify for a Stable Release Update - http://wiki.ubuntu.com/StableReleaseUpdates .

Julian, can you also attach the output of 'sudo lspci -vvnn' . Thanks.

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Triaged
Changed in linux-source-2.6.22:
status: Triaged → 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.

Revision history for this message
Julian Alarcon (julian-alarcon) wrote :

Sorry for the delay.

Here is my outpout of 'sudo lspci -vvn' command.

Revision history for this message
Brian Murray (brian-murray) wrote :

Have you tested this with 2.6.27?

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

It would be great if those who experience this issue could provide feedback if this exists against the 2.6.27 Intrepid kernel. I'm setting the status to Incomplete for now. Thanks.

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

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Andy Whitcroft (apw) wrote :

Can anyone confirm whether this is still and issue on either Intrepid or the new Jaunty release? If you are seeing this could you indicate which specific kernel version you are seeing it with (cat /proc/version_signature). Thanks in advance.

Changed in linux (Ubuntu):
assignee: nobody → Andy Whitcroft (apw)
status: Incomplete → In Progress
Andy Whitcroft (apw)
Changed in linux (Ubuntu):
status: In Progress → Incomplete
Revision history for this message
Renjoy (renjoy) wrote : Re: [Bug 86217] Re: tv tuner card with saa7134 not detected automatically

Hi,

I dont have the hardware anymore to test this.

On Tue, Apr 28, 2009 at 1:56 PM, Andy Whitcroft <email address hidden> wrote:

> ** Changed in: linux (Ubuntu)
> Status: In Progress => Incomplete
>
> --
> tv tuner card with saa7134 not detected automatically
> https://bugs.launchpad.net/bugs/86217
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards

Renjoy Henry

Revision history for this message
Jijua (jijua) wrote : Re: [Bug 86217] Re: tv tuner card with saa7134 not detected automatically

I have a LifeView/Typhoon Flyvideo2000 using the saa7134 module and
actually it is not detected automatically as well (using 9.04, but the
same happened since 5.04).

At boot I have to:

sudo rmmod saa7134
sudo modprobe saa7134 card=3 tuner=1

I think the same stands for other cards that need the automatic set of
the proper parameters.

To me this is not closed.

On Tue, 2009-04-28 at 12:56 +0000, Andy Whitcroft wrote:
> ** Changed in: linux (Ubuntu)
> Status: In Progress => Incomplete
>

Revision history for this message
Julian Alarcon (julian-alarcon) wrote : Re: [Bug 86217] Re: tv tuner card with saa7134 not detected automatically

On Tue, Apr 28, 2009 at 1:44 PM, Jijua <email address hidden> wrote:

> I have a LifeView/Typhoon Flyvideo2000 using the saa7134 module and
> actually it is not detected automatically as well (using 9.04, but the
> same happened since 5.04).
>
> At boot I have to:
>
> sudo rmmod saa7134
> sudo modprobe saa7134 card=3 tuner=1
>
> I think the same stands for other cards that need the automatic set of
> the proper parameters.
>
> To me this is not closed.
>
>
> On Tue, 2009-04-28 at 12:56 +0000, Andy Whitcroft wrote:
> > ** Changed in: linux (Ubuntu)
> > Status: In Progress => Incomplete
> >
>
> --
> tv tuner card with saa7134 not detected automatically
> https://bugs.launchpad.net/bugs/86217
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Yes, the problem is still there.. I use
options saa7134 card=65 tuner=54

into the file /etc/modprobe.d/options

Revision history for this message
Jijua (jijua) wrote : Re: [Bug 86217] Re: tv tuner card with saa7134 not detected automatically

The file /etc/modprobe.d/options is no more present in 9.04 (only a
options.dpkg-bak is present in the same directory and contains the old
parameters et al.).

On Wed, 2009-04-29 at 03:24 +0000, Julián Alarcón wrote:
> On Tue, Apr 28, 2009 at 1:44 PM, Jijua <email address hidden> wrote:
>
> > I have a LifeView/Typhoon Flyvideo2000 using the saa7134 module and
> > actually it is not detected automatically as well (using 9.04, but the
> > same happened since 5.04).
> >
> > At boot I have to:
> >
> > sudo rmmod saa7134
> > sudo modprobe saa7134 card=3 tuner=1
> >
> > I think the same stands for other cards that need the automatic set of
> > the proper parameters.
> >
> > To me this is not closed.
> >
> >
> > On Tue, 2009-04-28 at 12:56 +0000, Andy Whitcroft wrote:
> > > ** Changed in: linux (Ubuntu)
> > > Status: In Progress => Incomplete
> > >
> >
> > --
> > tv tuner card with saa7134 not detected automatically
> > https://bugs.launchpad.net/bugs/86217
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>
> Yes, the problem is still there.. I use
> options saa7134 card=65 tuner=54
>
> into the file /etc/modprobe.d/options
>

Revision history for this message
Rafael Gattringer (rafael.gattringer) wrote :

Hi, I would like to confirm this bug for my Philips / Medion 7134 card. The card also didn't work with Ubuntu 7.10.

Until now I still have haven't figured out a proper parameter for "sudo modprobe saa7134 card=X" yet. I use
sox -r 32000 -t alsa hw:1,0 -t alsa hw:0,0
as a workaround.

See my attached lspci and dmesg for details.

Revision history for this message
Marc-Antoine Daneau (daneau-marc-antoine) wrote :

my card is not detected in ubuntu 9.04

04:05.0 Multimedia controller [0480]: Philips Semiconductors SAA7130 Video Broadcast Decoder [1131:7130] (rev 01)
 Subsystem: Philips Semiconductors Device [1131:0000]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 64 (3750ns min, 9500ns max)
 Interrupt: pin A routed to IRQ 20
 Region 0: Memory at febffc00 (32-bit, non-prefetchable) [size=1K]
 Capabilities: [40] Power Management version 1
  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Kernel driver in use: saa7134
 Kernel modules: saa7134

# uname -r
2.6.28-11-generic

Andy Whitcroft (apw)
Changed in linux (Ubuntu):
assignee: Andy Whitcroft (apw) → nobody
Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
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.