Hi, U would have applied the correct patch from bytesex.org and compiled the kernel. But while loading the bttv driver (in my system i have bttv based tv tuner card) using "modprobe" see to that the new bttv driver is loaded. There are possibities where the old bttv driver is loaded instead of the new bttv driver. so rename the old bttv driver and load as usual. Default bttv driver will be at /lib/modules/2.4.20/kernel/drivers/media/video. rename it. New bttv driver will be at /lib/modules/2.4.20/v4l2. load this. After loading u can find the following in dmesg output. bttv: driver version 0.9.11 loaded bttv: using 8 buffers with 2080k (520 pages) each for capture bttv: Host bridge is Intel Corp. 82810E DC-133 GMCH [Graphics Memory Controller Hub] bttv: Bt8xx card found (0). PCI: Found IRQ 3 for device 01:05.0 PCI: Sharing IRQ 3 with 00:1f.3 PCI: Sharing IRQ 3 with 00:1f.5 PCI: Sharing IRQ 3 with 01:05.1 bttv0: Bt878 (rev 17) at 01:05.0, irq: 3, latency: 64, mmio: 0xe7bfe000 bttv0: using: BT878(Prolink PixelView PlayT) [card=37,insmod option] bttv0: gpio config override: mask=0xffffffff, mux=0x1,0xffffffff,0xffffffff,0xffffffff,0xffffffff Note the new bttv driver version. This indicates that u have loaded v4l2 not v4l1. Try this one out. On Wed, 19 Nov 2003 John Coppens wrote : >Hi all... > >I'm completely confused. In one machine, I developed a program that uses >the v4l2 API and works fine. On another machine it doesn't. I cannot find >what went wrong, and I need the thing urgently (of course). > >The machine that works is kernel 2.4.20, I applied the patch, and use an >SAAxxx chip there. Works A-ok. > >The new machine has 2.4.22 installed, and I applied the 2.4.22-3 patch > from bytesex.org. I enabled all the options (I think), and recompiled. >Here I have a Pinnacle PCTV (nothing else - no pro/sat/...) 'dmesg' shows >the card is recognized as a type 39, and no errors are reported. > >xawtv works just excellent. So does ttv, and a few others. > >v4l-info gives me info, but obtained thru v4l1 (VIDEOCGCAP), so it does >not recognize v4l2. > >v4l-conf says: >/dev/video0 [v4l2] ioctl VIDIOC_QUERYCAP: Invalid argument, then >/dev/video0 [v4l]: configuration done. > >I didn't see v4l2-common loaded, so I modprobed it manually, no >difference. Same with v4l1-compat. I do not have 'Load "v4l"' in either >machine in the XF86Config, so I guess this is not necessary. > >My program relies on v4l2 - Should I change the program to be able to use >v4l? > >Could it have something to do with not having sound installed in the new >machine? > >I've seen quite a few references to the v4l-conf message, but no real >answers. > >HELP!... I'd really appreciate some hints! > >John > > >-- >video4linux-list mailing list >Unsubscribe mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe >https://www.redhat.com/mailman/listinfo/video4linux-list There is no substitution for hard work. Information is wealth.
