Hi, I'm glad it's not only me suffering with the flyvideo3k's sound problem. I'd like to mention an additional piece of info which *might* help debugging the problem. It's kinda voodoo right again, but is reproducable. I still don't get any sound when using from xawtv, but I do get proper sound from the tvcard following the steps: 1. modprobe saa7134 card=2 2. start xawtv, and exit 3. rmmod saa7134 4. modprobe saa7134 card=3 (yep, i know that's for flyvideo2k) At this point I hear the sound of the last tuned tv channel, but as soon as I start xawtv, the sound is gone right again. I were unable to get any sound while xawtv is running, nor with loading the saa7134 driver with the right settings for my card (card=2).. I'd do anything (ok, almost anything ;) to help track down this problem. If any developer could jump in debugging the problem, please mail me some instructions to try out on my config, I'll answer ASAP with the results. Best regards, Christopher Jozsa ps. my config is: gentoo linux, kernel 2.4.19 patched with gentoo stuff, v4l2 and saa7134 0.1.10 (i've tried the 3 previous driver versions as well) ps2. xawtv, sound from flyvideo3k still works on my old debian box without a hitch(!), so I guess the cabeling and mixer settings are correct On Fri, Aug 30, 2002 at 03:46:49PM +0800, Geoff wrote: > I share your unstable Flyvideo 3k problem. When I first got it working it > too worked great for a few hours, then whamo, no sound. I posted a lot of > articles earlier and we (those on the list who generously participate and I) > could not identify/resolve the issue. A few weeks ago I did a fresh install > of RedHat 7.3, rebuilt the who kernel from 2.4.18 + patches, and it worked > perfectly. I suspect part of my initial problem was that I used the wrong > patch getting from 2.4.18 + 2.4.19-?? patch + v4l patch and I had to > modified some include share memory file that displayed errors when I applied > the patch. But at the time it seemed to compile fine and worked. But later > the sound died and I hit the list trying to resolve the problem. When I > did the fresh install a few weeks ago all the 2.4.18 kernel + 2.4.19 patch + > v4l patch all worked perfectly first time. I tried to reproduce the old > problems but could not. I thought I would wait until I posted to the list > expecting it to fail again soon. It did not. Also, I was not sure of the > true source of the problem, but me tinkering with the include file might > have had something to do with it. > > So. A week ago I got a new 120GB hard drive and decided to re-arranged my > whole system and ended up re-installed RedHat 7.3 from scratch. I then > rebuilt the kernel BUT this time the current kernel was 2.4.19 (no 2.5.18 + > 2.4.19-rc3 patch or anything on http://www.kernel.org. Cool I thought. But > when I looked at the current v4l2 patch (diff file) off http://bytesex.org I > noticed it is for 2.4.19-rc3. I renamed the 2.4.19 source directory to > 2.4.19-rc3, applied the v4l2 patch, built it all, installed, rebooted, > recompiled saa7134-0.1.10, installed, modprobe saa7134, started xawtv again! > Everything worked fine - BUT now sound again! > > So. At this point, before further investigation I am waiting for a new > version of v4l2 diff file to be released based specifically on a current > kernel source / patch file combination. > > Your not alone! I will post any legitimate findings. > --Geoff > > > ----- Original Message ----- > From: "Jozsa Kristof" <dyn@xxxxxxxxxxx> > To: <video4linux-list@xxxxxxxxxx> > Sent: Friday, August 30, 2002 2:32 PM > Subject: saa7134 - the sound of silence > > > > Hi there, > > > > I've read through the July-August archive of the list, but couldn't find a > > complete solution to the well-known saa7134 based Flyvideo3K problem: > xawtv > > mutes the card (i've tried some things found in the list archive, but no > > help, it just mutes anyway), while any radio application works correctly. > > > > The strange fact is, that I have two linuxes (on two HDDs) for my box. I > do > > have my 'old' Debian box with kernel 2.4.19 (v4l2 patches) and > > saa7139-1.0.9, where my flyvideo just works *perfectly*. (X booting up, > > starting xawtv, it works with pic and sound). But I have my freshly pulled > > up gentoo linux on the other hdd, where i just cant get xawtv pushing out > > any sound from the saa7134. I use the v0.1.10 saa7134 drivers on gentoo. > > > > The setup is just the same on the two boxes, as far as I can tell. I have > > the flyvideo's line out wired into the sblive 1024's line in with an > > external cable. I load only the saa7134 driver with the option card=2, > > nothing else. I do not load the tda9887 module (which i believe was meant > > for the flyvideo's sound chip). The sblive's mixer is set to recording on > > the Line channel, the saa7134's mixer is 'recording' on its Video channel. > > These are set the very same way both on the debian box (where it works) > and > > on the gentoo (where it does not). I have no idea what it's going on here. > > > > [I have one more slight comment about my story, but you won't believe it: > I > > did have sound correctly from the saa7134 using xawtv on my gentoo box > (!), > > for about 40 minutes. Not before, not after, no idea what has changed > since > > that, or what did I do to get it work, can't reproduce it either since > that > > (happened 3 days ago). Voodoo, eh?] > > > > Any help/comments appreciated, > > Kind regards, > > > > Christopher Jozsa > > -- > > .Digital.Yearning.for.Networked.Assassination.and.Xenocide > > > > > > > > _______________________________________________ > > Video4linux-list mailing list > > Video4linux-list@xxxxxxxxxx > > https://listman.redhat.com/mailman/listinfo/video4linux-list > > > > > > _______________________________________________ > Video4linux-list mailing list > Video4linux-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/video4linux-list -- .Digital.Yearning.for.Networked.Assassination.and.Xenocide
