Just as a point of reference are you using the beta drivers from osprey? At 04:23 PM 8/13/2002, you wrote:
Hello, I'm trying to get 6 bt848 (i.e. osprey 100) working in one machine. I've had success with 1 to 5 cards. Xawtv 3.72 and ``xcaplive'' (our own application) work great with 5 cards using 2.4.18 and 2.4.19 using bttv 0.7.91. It also works with 2.4.19 with the v4l2-api patch by Gerd, as well as his v4l2-20020723 modules and bttv 0.8.44 running in v4l AND v4l2 modes. However, everything goes to heck as soon as I stick in a sixth card. Bttv will still print out sane information under dmesg and detect the sixth card (it appears under /proc/video/dev). But, xawtv and xcaplive both will not work. I do get one error message with v4l: "This is xawtv-3.72, running on Linux/i686 (2.4.19) v4l: timeout (got SIGALRM), hardware/driver problems? ioctl: VIDIOCSYNC(0): Interrupted system call ioctl: VIDIOCMCAPTURE(0,fmt=4,size=48x32): Device or resource busy ioctl: VIDIOCMCAPTURE(0,fmt=1,size=48x32): Device or resource busy ioctl: VIDIOCMCAPTURE(0,fmt=7,size=48x32): Device or resource busy ioctl: VIDIOCMCAPTURE(0,fmt=13,size=48x32): Device or resource busy ioctl: VIDIOCMCAPTURE(0,fmt=15,size=48x32): Device or resource busy" With v4l2, I get no messages beyond normal startup information. The applications in general do not crash, but occasionally they do take down the machine. I know it's a vague and strange problem, but I would appreciate any help or comments. Thank-you, Felix _______________________________________________ Video4linux-list mailing list Video4linux-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/video4linux-list
