On 2003-01-24 at 10:27:59 +0100, Christoph Berg <cb@xxxxxxxxxxxx> wrote: > > The kernel version is '2.4.20-cb1' (from a Debian kernel build using > make-kpkg). bttv tried to install to /lib/modules/2.4.20/ and of course > failed. I put a symlink 2.4.20 -> 2.4.20-cb1 there, but bttv.o wasn't > copied even then, only the other modules. That's not necessarily because of your patched kernel; bttv.o just didn't get copied over when I tried 0.7.102. You can copy it manually (you probably have to run 'depmod -a' afterwards). With 0.9.4, it does get copied, but to /lib/modules/2.4.20/v4l2/, so if you already have a bttv.o in /lib/modules/2.4.20/kernel/drivers/media/video/, things get messy (apparently, the kernel loads the first bttv.o it encounters and that's the wrong one). > I'm a bit confused about the patches mentioned on > http://bytesex.org/bttv/: They all seem to apply to v4l2. So if I want > to use plain v4l, should I patch my kernel in any way? (besides > installing bttv 0.7.x of course) As long as you get the patch-*-kraxel.gz archive, I think things should be okay, but I'm also rather confused about it. Since 0.9.4 creates the lib/modules/2.4.20/v4l2/ directory, it may mean that 0.7.102 uses v4l1. Possibly. I'm using bttv 0.9.4 with a PCTV Rave (same model as yours, with the mt2032 tuner) on kernel 2.4.20, Debian testing/unstable, and I have few problems watching TV with it (xawtv, tvtime, mplayer). There's only one channel out of 31 (Danish cable) that scantv doesn't find. I have never had a lock up when trying to watch TV (only when experimenting with captures). So, provided your card doesn't have a defect, it should be possible to get it to work on your system. Capturing is a bigger problem; I've so far spent two weeks trying to get that to work properly and I'm close to giving up. There's some sort of timing issue that causes duplicate frames, so capturing on Linux isn't worth it so far (but it works fairly perfectly with several different Windows programs). -R.
