saa7130 TV tuner stopped working in 9.10 and 10.04

Bug #583549 reported by pdlethbridge
38
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Linux
Expired
High
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I successfully got tvtime working by using the following commands for it to see my tv capture card.
sudo nano /etc/modprobe.d/saa7134 hit enter
next you will be asked for your password enter and press the enter key.

now in the nano editor, type the following lines pressing enter at the end of each one.

alias chr-major-81 videodev enter
alias chr-major-81-0 saa7134 enter
options saa7134 card=42 tuner=43 oss=1 enter

now press the control key (ctrl) and the "x" key at the same time
you will be asked if you want to save file: saa7134
say yes by pressing "y" key on the keyboard.
Doing nothing or applying this did not work in 9.10 or 10.04. A work around was suggested that I try a different kernel. This I could not do.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.33
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pdleth 1146 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH5'/'Intel ICH5 with ALC655 at irq 17'
   Mixer name : 'Realtek ALC655 rev 0'
   Components : 'AC97a:414c4760'
   Controls : 41
   Simple ctrls : 26
Date: Thu May 20 17:17:38 2010
HibernationDevice: RESUME=UUID=69dca19b-c71a-46ee-955a-efb5d628d2c9
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: MICRO-STAR INC. MS-6728
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=34cf22d4-30c0-4f0b-aca0-11fd6a8add27 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:

SourcePackage: linux
dmi.bios.date: 09/29/2004
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V3.A
dmi.board.name: MS-6728
dmi.board.vendor: MICRO-STAR INC.
dmi.board.version: 2.00
dmi.chassis.asset.tag: 0123ABC
dmi.chassis.type: 3
dmi.chassis.vendor: Uknown Chassis Manufacture
dmi.chassis.version: Version 1.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.A:bd09/29/2004:svnMICRO-STARINC.:pnMS-6728:pvr2.00:rvnMICRO-STARINC.:rnMS-6728:rvr2.00:cvnUknownChassisManufacture:ct3:cvrVersion1.00:
dmi.product.name: MS-6728
dmi.product.version: 2.00
dmi.sys.vendor: MICRO-STAR INC.

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

Hi pdlethbridge,

If you could also please 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: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
pdlethbridge (pdleth) wrote :

If I installed this, would that be the right one?
/home/pdleth/Desktop/linux-image-2.6.34-020634rc7-generic_2.6.34-020634rc7_i386.deb

Revision history for this message
pdlethbridge (pdleth) wrote :

I've tried twice to change the kernels, but failed both times requiring me to reinstall the OS. Very time consuming. Any ideas that would help would be greatly appreciated. Paul

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

pdlethbridge,
     if that is the one listed in the page for kernel translation to mainline, then yes, that would be correct.

I'm not sure I understand why you were forced to do a complete reinstall. The kernel installation is relatively straightforward and does not remove your original kernel. Could you please describe why you needed to reinstall?

Thanks!

~JFo

Revision history for this message
pdlethbridge (pdleth) wrote :

 After installation, I rebooted and ended up with a blank screen, no dos prompt or anything, after waiting a few minutes, I rebooted and same thing. So I reinstalled the OS. Tried a different kernel and had the same thing. Sorry, you are dealing with a person of limited computer abilities.

Revision history for this message
pdlethbridge (pdleth) wrote :

this is the page:
Index of /~kernel-ppa/mainline/v2.6.34-rc7-lucid
[ICO] Name Last modified Size Description
[DIR] Parent Directory -
[ ] BUILD.LOG 10-May-2010 12:06 2.7M
[ ] CHANGES 10-May-2010 10:05 21K
[ ] linux-headers-2.6.34-020634rc7-generic_2.6.34-020634rc7_amd64.deb 10-May-2010 11:07 692K
[ ] linux-headers-2.6.34-020634rc7-generic_2.6.34-020634rc7_i386.deb 10-May-2010 12:06 675K
[ ] linux-headers-2.6.34-020634rc7_2.6.34-020634rc7_all.deb 10-May-2010 10:08 9.6M
[ ] linux-image-2.6.34-020634rc7-generic_2.6.34-020634rc7_amd64.deb 10-May-2010 11:07 30M
[ ] linux-image-2.6.34-020634rc7-generic_2.6.34-020634rc7_i386.deb 10-May-2010 12:06 30M
[ ] linux-source-2.6.34_2.6.34-020634rc7_all.deb 10-May-2010 10:08 2.2K
Apache/2.2.8 (Ubuntu) Server at kernel.ubuntu.com Port 80

Revision history for this message
pdlethbridge (pdleth) wrote :

I tried it a third time. This time I got a dos screen but couldn't get to the desk top. Well, that's three strikes and I'm out. I've gone back to my old reliable 9.04

Revision history for this message
pdlethbridge (pdleth) wrote :

I was unable to do the up stream testing

Revision history for this message
Burt P. (pburt0) wrote :

Well, this is an old bug #458832 that has somehow been marked as a duplicate of this new report.
Anyway, the problem is with v4l-dvb's Phillips SAA713X tuner driver (saa7134), not tvtime, and the bug has been reported at https://bugzilla.kernel.org/show_bug.cgi?id=15254 where it has been ignored for some time. It is a kernel module that will have to be fixed by them, not Ubuntu, and they aren't working on it so don't hold your breath.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
status: Invalid → Confirmed
summary: - tvtime stopped working in 9.10 and 10.04
+ saa7130 TV tuner stopped working in 9.10 and 10.04
Revision history for this message
pickarooney (richard-walsh) wrote :

Apologies if I'm not doing this right, but I have a similar problem with a BT878 chip TV card. It simply will not pick up any channels on Karmic or Lucid but works perfectly on Jaunty.

Revision history for this message
penalvch (penalvch) wrote :

pdlethbridge, thank you for reporting this and helping make Ubuntu better. 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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

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

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.

tags: added: karmic
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in linux:
importance: Unknown → High
status: Unknown → Confirmed
Changed in linux:
status: Confirmed → Expired
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!

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.