Hello people!
I bought my Terratec Cinergy 400 PCI tv card and have this drivers installed: v4l, v4l2 and saa7134-0.2.8 on RedHat 9.
I installed alsa drivers for my integrated soundcard (Realtek ALC650). There is a cable from the tv card plugged into “Line In” of my sound card. Without loading saa7134 module I can hear slight untuned tv noise. When I load the module with
“modprobe saa7134 card=8” this noise disappear.
After starting tvtime I can see tv. Works great but sound.
I get this error message from tvtime:

videoinput: Can't mute card. Post a bug report with your
videoinput: driver info to tvtime.net
videoinput: Include this error: 'Invalid argument'

Info of which driver it wants me to send I don’t know. I’ve attached modinfo of my tv and soundcard.

Guys, really want to have it working. TVtime is much better than any software I’ve ever seen for Windows.

Thank you,
Dmitry!


modinfo saa7134
filename: /lib/modules/2.4.20-8custom/v4l2/saa7134.o
description: "v4l2 driver module for saa7130/34 based TV cards"
author: "Gerd Knorr <kraxel@bytesex.org> [SuSE Labs]"
license: "GPL"
parm: irq_debug int, description "enable debug messages [IRQ handler]"
parm: core_debug int, description "enable debug messages [core]"
parm: gpio_tracking int, description "enable debug messages [gpio]"
parm: video_nr int, description "video device number"
parm: ts_nr int, description "ts device number"
parm: vbi_nr int, description "vbi device number"
parm: radio_nr int, description "radio device number"
parm: oss int, description "register oss devices (default: no)"
parm: dsp_nr int, description "oss dsp device number"
parm: mixer_nr int, description "oss mixer device number"
parm: tuner int array (min = 1, max = 8), description "tuner type"
parm: card int array (min = 1, max = 8), description "card type"
parm: latency int, description "pci latency timer"
parm: i2c_debug int, description "enable debug messages [i2c]"
parm: i2c_scan int, description "scan i2c bus at insmod time"
parm: video_debug int, description "enable debug messages [video]"
parm: gbuffers int, description "number of capture buffers, range 2-32"
parm: vbi_debug int, description "enable debug messages [vbi]"
parm: vbibufs int, description "number of vbi buffers, range 2-32"
parm: audio_debug int, description "enable debug messages [tv audio]"
parm: audio_carrier int, description "audio carrier location"
parm: oss_debug int, description "enable debug messages [oss]"
parm: oss_rate int, description "sample rate (valid are: 32000,48000)"
parm: ts_debug int, description "enable debug messages [ts]"
parm: tsbufs int, description "number of ts buffers, range 2-32"

modinfo snd-via82xx
filename: /lib/modules/2.4.20-8custom/kernel/sound/pci/snd-via82xx.o
description: "VIA VT82xx audio"
author: "Jaroslav Kysela <perex@suse.cz>"
license: "GPL"
parm: index int array (min = 1, max = 8), description "Index value for VIA 82xx bridge."
parm: id string array (min = 1, max = 8), description "ID string for VIA 82xx bridge."
parm: enable int array (min = 1, max = 8), description "Enable audio part of VIA 82xx bridge."
parm: mpu_port long array (min = 1, max = 8), description "MPU-401 port."
parm: ac97_clock int array (min = 1, max = 8), description "AC'97 codec clock (default 48000Hz)."
parm: dxs_support int array (min = 1, max = 8), description "Support for DXS channels (0 = auto, 1 = enable, 2 = disable, 3 = 48k only)"

No solution yet, but I have the same problem as you:
kernel 2.6.2
saa7134 module card=9 (medion 5044
alsa snd-via82xx sounddriver build-in
(redhat 9 with freshrpms via apt-get, but i dont think that matters much)

When the module is inserted I get some error messages like this one:
kernel: saa7134[0]/audio: audio carrier scan failed, using 5.500 MHz [last detected]

With xwatv i get a nice picture, but the sound (via line-out -> line-in) is only white noise.

Maybe someone has some idea what the 5.5 MHz number is for? Are there regional differences how the tv sound is transmitted that the driver is having troubles with?

I had a look in the source, and found some clues that there were some bugs with the type of card i have. Does anybody know anything more about the nature of these bugs?

tnx,

Jelle

Yes there are. PAL-B uses 5.5MHz, others may use 6.0 or 6.5MHz. You can force the audio carrier using
insmod /path/to/saa7134.ko card=x audio_carrier=5500 - or 6000 or 6500 - depending on your region. You could just try each one and see which gives you sound.

I found I could not force the audio_carrier with 2.6.4 so will probably drop back to 2.6.3 (2.6.2 may be fine too).

i810_audio is waiting for a params et I do not know how ?

#modinfo i810_audio
filename: /lib/modules/2.4.18-bf2.4/kernel/drivers/sound/i810_audio.o
description: "Intel 810 audio support"
author: ""
license: "GPL"
parm: ftsodell int
parm: clocking int
parm: strict_clocking int
parm: spdif_locked int


Must I upgrade linux kernel or use parameter to use this module ?

Help

It may be that your module needs parameters when it is being loaded. an upgrade of the kernel when you don't know what the problem is will not solve much probably.
It will help if you describe your problem better: when do you see this message and what have you done to reproduce it.
Good luck

hi folks! anyone tried to provide audio_carrier= parameter in kernels 2.6.8.1 or 2.6.9? I couldn't use older kernel as I simply doesn't have any of them and right now I couldn't download older version :-\
my problem is pretty similar to described above, maybe someone could take check out my post to see if there is solution to my problem? Here is the post http://www.linuxquestions.org/questi...hreadid=248173

Thanks in advance!