You need version saa7134-0.2.7-tar.gz for sound with the FV2k. You don't really have to remove the old version. Just 'make install' right over it. You can automate the mopdrobe by running the following little script (on Debian). Note ^D is Ctrl-D. # cat > /etc/modutils/tv alias char-major-81 videodev alias char-major-81-0 saa7134 options saa7134 card=3 above saa7134 tuner options tuner type=39 ^D # update-modules Cheers, Shaun On Sat April 26, 2003 18h48, you wrote: > Hi Everybody. > > I'm a novice Linux user running Debian. Another problem is my > english, it's very poor, so it's possible I misunderstood some > directions. > I work on Debian woody 3.0.1, kernel 2.4.20. > I'm trying to install a FlyVideo 2000FM, so I went to > bytesex.org/saa7134 and downloaded the driver saa7134-0.2.6-tar.gz > and the v4l > snapshoot v4l2-0030415.tar.gz. > > I installed saa7134-0.2.6 because 0.2.7 gave me compile problems. > I created the directory /usr/src/saa7134 aund untar both files > inside. each one genered their directory saa7134 and v4l. I > compiled first v4l. cd v4l; make KDIR=/usr/src/linux and make > install; Everything was OK. I repeated the procedure with saa7134 > directory; make (same KDIR) and make install. Again I found no > problems. > > I reboot the system and tried to execute any application to see TV > I had none (remeber I'm a novice) so I went again to bytesex.org > and herad about xawtv, so I did an apt-cache search xawtv and based > on the output I installed the following: > apt-get install xawtv-applet xawtv-tools came xawtv v4l-conf sacntv > xawtv-plugins. > > Everything installed ok. The xawtv version installed was 3.72. > > I rebooted my machine again and now I find xawtv to execute. As a > normal user I execute xawtv and receive the following: > > ------------------------------------------------------------------- >--------------------------------------------------------- Apr 26 > 19:57:11 debian kernel: Linux video capture interface: v1.00 Apr 26 > 19:57:11 debian kernel: i2c-core.o: i2c core module Apr 26 19:57:11 > debian kernel: i2c-algo-bit.o: i2c bit algorithm module Apr 26 > 19:57:11 debian kernel: bttv: driver version 0.7.96 loaded Apr 26 > 19:57:11 debian kernel: bttv: using 4 buffers with 2080k (8320k > total) for capture Apr 26 19:57:11 debian kernel: bttv: Host bridge > is VIA Technologies, Inc. VT8361 [KLE133] Host Bridge Apr 26 > 19:57:11 debian insmod: > /lib/modules/2.4.20/kernel/drivers/media/video/bttv.o: init_module: > No such device > Apr 26 19:57:11 debian insmod: Hint: insmod errors can be caused by > incorrect module parameters, including invalid IO or IRQ > parameters > Apr 26 19:57:11 debian insmod: > /lib/modules/2.4.20/kernel/drivers/media/video/bttv.o: insmod > char-major-81 failed > Apr 26 19:57:11 debian kernel: Linux video capture interface: v1.00 > Apr 26 19:57:12 debian kernel: i2c-core.o: i2c core module > Apr 26 19:57:12 debian kernel: i2c-algo-bit.o: i2c bit algorithm > module Apr 26 19:57:12 debian kernel: bttv: driver version 0.7.96 > loaded Apr 26 19:57:12 debian kernel: bttv: using 4 buffers with > 2080k (8320k total) for capture Apr 26 19:57:12 debian kernel: > bttv: Host bridge is VIA Technologies, Inc. VT8361 [KLE133] Host > Bridge Apr 26 19:57:12 debian insmod: > /lib/modules/2.4.20/kernel/drivers/media/video/bttv.o: init_module: > No such device > Apr 26 19:57:12 debian insmod: Hint: insmod errors can be caused by > incorrect module parameters, including invalid IO or IRQ > parameters > Apr 26 19:57:12 debian insmod: > /lib/modules/2.4.20/kernel/drivers/media/video/bttv.o: insmod > char-major-81 failed > Apr 26 19:57:12 debian kernel: Linux video capture interface: v1.00 > Apr 26 19:57:12 debian kernel: i2c-core.o: i2c core module > Apr 26 19:57:12 debian kernel: i2c-algo-bit.o: i2c bit algorithm > module Apr 26 19:57:12 debian kernel: bttv: driver version 0.7.96 > loaded Apr 26 19:57:12 debian kernel: bttv: using 4 buffers with > 2080k (8320k total) for capture Apr 26 19:57:12 debian kernel: > bttv: Host bridge is VIA Technologies, Inc. VT8361 [KLE133] Host > Bridge Apr 26 19:57:13 debian insmod: > /lib/modules/2.4.20/kernel/drivers/media/video/bttv.o: init_module: > No such device > Apr 26 19:57:13 debian insmod: Hint: insmod errors can be caused by > incorrect module parameters, including invalid IO or IRQ > parameters > Apr 26 19:57:13 debian insmod: > /lib/modules/2.4.20/kernel/drivers/media/video/bttv.o: insmod > char-major-81 failed > > ------------------------------------------------------------------- >------------------------------------------------------------- > > After a good reading session I lerand I must do a modprobe in order > to load the module so I did a su root and modprobe saa7134, it > loads OK. > > First question. Do I need to execute this command every time I > reboot my machine in order to watch YV? in other words, does not > exists a more automatic way? > > Now, with the module loaded I execute xawtv again. OK, I got some > image but it was very poor so after some minutes I click with the > right button on the TV screen and an options menu appears, there I > saw that Normal TV is shown as PAL, here in Venezuela we use NTSC > so I changed it. Now the image is very good, but I have no sound. > But here there is another problem, every time I close xawtv and > execte it again I must set NTSC manually again, is it correct? > > I reviewed my /etc/modules.conf file and I couldn't see nothing > about saa7134, is it correct? > > I was looking in the list archives and found some patches tht must > be done to the sources, but I'm not clear if they apply to my case. > I also review inside the snapsoot directory (in bytesex.org) and > there exists a file for xawtv (xawtv-20030414.tar.gz) I don't know > if I must use it or not. > > One late question If I decide to use the saa7134-0.2.7 or later > driver, how can I unistall the previus one? > > Thank very much for your hekp and for being so patient.
