I followed the directions on the v4l howto... did a make then a make install inside the working directory\v4l2 and the working directory\saaxxxx\ directories. So the errors i got are indicative of the driver not being installed properly? i suppose i need to patch my kernel and do the full thing instead? i'll look -dane ----- Original Message ----- From: "Wan Tat Chee" <tcwan@xxxxxxxxx> To: <video4linux-list@xxxxxxxxxx> Sent: Sunday, June 29, 2003 9:06 PM Subject: **SPAM** Re: flyvideo 3100 with saa713x mandrake 9.1 > On Fri, 27 Jun 2003, Dane Kantner wrote: > > > [root@localhost saa7134-0.2.7]# modprobe -d -v saa7134 card=16 > > /lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7134.o.gz: > > init_module: No such device > > modprobe: insmod > > /lib/modules/2.4.21-0.13mdk/kernel/drivers/media/video/saa7134.o.gz failed > > modprobe: insmod saa7134 failed > > [root@localhost saa7134-0.2.7]# > > Silly question, when you built your saa7134 modules, did you do a 'make > install'? It puts the modules by default in /lib/modules/`uname -r`/v4l2 > instead of the path above. There'd be two versions of the driver and > modprobe looks for it in .../kernel/drivers/media/video instead of > .../v4l2. > > Other caveats are that you should build the modules when running > the kernel you're using, with the same gcc/compiler tools. At > this moment, I think it's best you roll your own kernel and patch > it with the latest v4l2 patches. Otherwise strange problems can occur. > Wan Tat Chee (Lecturer)
