LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Mercury tvtuner pci saa7134 problem (https://www.linuxquestions.org/questions/linux-hardware-18/mercury-tvtuner-pci-saa7134-problem-492580/)

m3mys3lf4ndi 10-15-2006 09:40 AM

Mercury tvtuner pci saa7134 problem
 
Hi there,
im trying to setup my mercury tvtuner card on FC5.

lspci gives:

00:0b.0 Multimedia controller: Philips Semiconductors SAA7130 Video Broadcast Decoder (rev 01)


dmesg:

saa7130[0]: found at 0000:00:0b.0, rev: 1, irq: 177, latency: 64, mmio: 0xfaefdc00
saa7130[0]: subsystem: 18d0:2100, board: LifeView FlyVIDEO3000 [card=2,insmod option]
saa7130[0]: board init: gpio is 38500
saa7130[0]: there are different flyvideo cards with different tuners
saa7130[0]: out there, you might have to use the tuner=<nr> insmod
saa7130[0]: option to override the default value.
input: saa7134 IR (LifeView FlyVIDEO30 as /class/input/input14
tuner 1-0061: chip found @ 0xc2 (saa7130[0])
tuner 1-0061: type set to 49 (Microtune 4042 FI5 ATSC/NTSC dual in)
saa7130[0]: i2c eeprom 00: d0 18 00 21 10 28 ff ff ff ff ff ff ff ff ff ff
saa7130[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7130[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7130[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7130[0]: registered device video0 [v4l2]
saa7130[0]: registered device vbi0
saa7130[0]: registered device radio0


(i've set card=2 and tuner=49 coz i thought that was the settings i used to have in ubuntu)

tvtime-scanner scans but doesnt find any freq...

anyone has same working card ??

cosmint_1973 10-17-2006 07:53 AM

:newbie:
Hi there also same situation, have a look. My card is Mercury. Never found an easy step-by step install guide, maybe someone could help someday newbies like me and others.

This is from lspci :

0000:00:0b.0 Multimedia controller: Philips Semiconductors SAA7130 Video Broadcast Decoder (rev 01)

... and this is from dmesg :

[17179590.380000] saa7130[0]: found at 0000:00:0b.0, rev: 1, irq: 193, latency: 64, mmio: 0xdfffbc00
[17179590.380000] saa7130[0]: subsystem: 18d0:2100, board: UNKNOWN/GENERIC [card=0,autodetected]
[17179590.380000] saa7130[0]: board init: gpio is 39100
[17179590.412000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179590.516000] saa7130[0]: i2c eeprom 00: d0 18 00 21 10 28 ff ff ff ff ff ff ff ff ff ff
[17179590.516000] saa7130[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179590.516000] saa7130[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179590.516000] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179590.516000] saa7130[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179590.516000] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179590.516000] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179590.516000] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179590.516000] saa7130[0]: registered device video0 [v4l2]
[17179590.516000] saa7130[0]: registered device vbi0
[17179590.580000] saa7134 ALSA driver for DMA sound loaded
[17179590.580000] saa7130[0]/alsa: saa7130[0] at 0xdfffbc00 irq 193 registered as card -1

So please anyone more experienced help us configure the cards. Personally just switched from Windoze and decided never to go back, no matter how hard it would be to learn Linux.
:newbie:

m3mys3lf4ndi 10-17-2006 03:34 PM

at least im not alone :D
what system ur on? did u tried to set card=2 and tuner=39 ??
this card was working fine earlier on FC4 and ubuntu so its doable but still havnt found any solution... and cant get acces to the old disk with ubuntu to have a look what numbers that was..

cosmint_1973 10-18-2006 07:55 AM

I'm lost for now
 
Actually I'm totally lost, because I installed beryl (compiz) and emerald and screwed my Xorg configuration, so I always have to login at console then type in startx and so I get into gnome.
I used to know how to set the TV card numbers, but lost the link to a very good tutorial and never found it again. So please can you remind me what is to be done to setup the card ? I know this sounds stupid but I'm a fast learner, I don't get scared of the command line anymore.

System specs : AMD Sempron 2600+, 1 GB DDRAM 400, VIA Chipset ASROCK K7VT4A PRO Motherboard, SoundBlaster Live!, 160 GB SATA Western Digital Drive, SONY DVD-RW +-, SONY CD-RW, FUJI FINE PICS A210 Camera and USB connected CANON scanner CANOSCAN D646U.

Let's hope that someone will find this thread and help us with a complete step-by step guide. I'd try make one myself but I'm not that experienced yet.

cosmint_1973 10-18-2006 08:02 AM

look, previous was on kubuntu, actually went back to gnome and ubuntu and for
lspci it gives :

0000:00:0b.0 Multimedia controller: Philips Semiconductors SAA7130 Video Broadcast Decoder (rev 01)

and dmesg gives again :

[17179590.472000] Linux video capture interface: v1.00
[17179590.604000] saa7130/34: v4l2 driver version 0.2.14 loaded
[17179590.608000] ACPI: PCI Interrupt 0000:00:0b.0[A] -> GSI 19 (level, low) -> IRQ 209
[17179590.608000] saa7130[0]: found at 0000:00:0b.0, rev: 1, irq: 209, latency: 32, mmio: 0xdfffbc00
[17179590.608000] saa7130[0]: subsystem: 18d0:2100, board: UNKNOWN/GENERIC [card=0,autodetected]
[17179590.608000] saa7130[0]: board init: gpio is 39100
[17179590.716000] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[17179590.744000] saa7130[0]: i2c eeprom 00: d0 18 00 21 10 28 ff ff ff ff ff ff ff ff ff ff
[17179590.744000] saa7130[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179590.744000] saa7130[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179590.744000] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179590.744000] saa7130[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179590.744000] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179590.744000] saa7130[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179590.744000] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179590.744000] saa7130[0]: registered device video0 [v4l2]
[17179590.744000] saa7130[0]: registered device vbi0
[17179590.756000] saa7134 ALSA driver for DMA sound loaded
[17179590.756000] saa7130[0]/alsa: saa7130[0] at 0xdfffbc00 irq 209 registered as card -1

and this drives me nuts. Where can I change card numbers for tuner and stuff ?

m3mys3lf4ndi 10-18-2006 12:49 PM

do (as root):
modprobe saa7134 card=2 tuner=39
(might have to do in the path is not set: /sbin/modprobe ......)
that should load saa7134 module into kernel, then run tvtime and see if thers any input, if not - do /sbin/rmmod saa7134 to unload it and try some other settings... plenty of them... ;)

cosmint_1973 10-19-2006 03:33 AM

Thanks will sure do try but until then let me say I fixed my Xorg config all by myself (noob here).
Also found this thing here about how some1 managed to get his Mercury card working.

By the way, which software are you using for viewing TV and what distribution ?

Hailey's_Comet 01-24-2007 10:47 PM

there will be a setting in /etc/modprobe.preload with the line:

saa7134

on the same line put "card=n tuner=n" without quotes, and replace "n" according to what the number should be. after doing that with my card, i now get to see and change channels - but no audio.

hey, it's a start...

ciotog 02-07-2007 09:37 AM

FYI Hailey's Comet solved the problem in this thread:
http://www.linuxquestions.org/questi...d.php?t=521609

For any future browsers, be advised however that not all Mercury TV Tuner cards use the Philips chipset, I have one for example that uses Conexant.

rodrixx 04-30-2007 04:01 PM

tv card
 
Easy fix, to make it work run (in root):
rmmod saa7134
modprobe saa7134 card=3 tuner=39


It will most likely work. If it does, read the rest to put these commands at startup so you wont need to execute them everytime you want to watch tv.

First, undo any changes to any config files you may have modified to try to make it work. Log in as root. In your startup script (in my case its boot.local) in /etc/init.d i put these lines and it works perfect.

rmmod saa7134
modprobe saa7134 card=3 tuner=39


What happens is that the driver settings the kernel assigns are not properly configured and if you just modprobe without rmmodding, it'll add to the mess (if it even works).

NOTE FOR XGL/COMPIZ USERS: If you're using compiz/xgl you will notice that the image is gargled (in kdetv anyway) but not when Desktop Effects are disabled. In kdetv, go in Settings>Configure kdetv. Now go in the Image Filters tab, uncheck Overscan.

colin.mcewan 05-01-2007 03:59 AM

Tried your proposed solution bur when I typed sudo rmmod saa7134 I was informed that saa7134 was in use by alsa.

How do I get past this please?

rodrixx 05-01-2007 12:55 PM

Quote:

Originally Posted by colin.mcewan
Tried your proposed solution bur when I typed sudo rmmod saa7134 I was informed that saa7134 was in use by alsa.

How do I get past this please?

Quit anything using the tv card.

If that doesnt work, make the modifications in the terminal, shutdown X. If you don't know how to do that, restart, go in failsafe mode.

ciotog 05-01-2007 05:00 PM

A better method of removing modules is to use the -r option with modprobe. This will remove any dependent modules that aren't being used as well. The manpage for rmmod even recommends this.

Also rather than removing the module and adding it back in via a script (an ugly hack, if you ask me), you should add some lines to /etc/modules.conf like so:
Code:

# V4L #
options saa7134 card=3
options tuner type=39


rodrixx 05-01-2007 08:01 PM

Where do you get "type"?
wouldnt it be
options saa7134 card=3 tuner=39



Quote:

Originally Posted by ciotog
A better method of removing modules is to use the -r option with modprobe. This will remove any dependent modules that aren't being used as well. The manpage for rmmod even recommends this.

Also rather than removing the module and adding it back in via a script (an ugly hack, if you ask me), you should add some lines to /etc/modules.conf like so:
Code:

# V4L #
options saa7134 card=3
options tuner type=39



ciotog 05-01-2007 09:45 PM

That should work too - in fact on my system the files in /etc/modprobe.d are used instead of modules.conf, and I created the file tvtuner there which has options cx88xx card=50 tuner=69. So in other words there may be more to it depending on how your system is set up.


All times are GMT -5. The time now is 04:42 AM.