Hi,
Check whether some other process uses /dev/video0 by using the
following command in the shell prompt.


fuser /dev/video0.

Kill that process. Then verify from "dmesg" command whether u have
loaded the upgraded driver. Default loading using modprobe or insmod
will load only the old driver module. Rename the old driver module and
use depmod to load new driver module.


Actually I want 2 applications to use /dev/video0 at a time. Thats the
reason why i got the device or resource busy message. I solved by
upgrading the bttv driver. I am using bttv based "Pixel view play Tv
Pro" tv tuner card. so no idea about saa7134 based tv tuner cards. But
"Hermann Pitton" one of our member knows more about saa7134 based
cards.Probably he will reply. If no other process uses /dev/video0 and
still the "device or resource busy" message occurs, then problem is
only with upgradded saa7134 driver.


All the best.

With Regards,
S.Suriya Mohan.



On Sat, 16 Aug 2003 Matthew Tidy wrote :
I have been trying to get my flyvideo 3000 to work under RH 9. I
have patched 2.4.21 kernel with the v4l2 modules and have installed
the saa7134-0.2.7 drivers. I have also installed xawtv 3.88. The
install process for both the modules and drivers have reported no
error messages. I finally type xawtv at my command line to find that
i get this as output

[EMAIL PROTECTED] ~]$ xawtv This is xawtv-3.88, running on Linux/i686 (2.4.21) ERROR: plugin magic mismatch
[xawtv=537067817,../libng/plugins/conv-audio.c=537069088]
dlsym[/usr/local/lib/xawtv/conv-audio.so]: xawtv: undefined symbol:
_ng_plugin_init
ERROR: plugin magic mismatch
[xawtv=537067817,../libng/plugins/read-mpeg.c=537069088]
ERROR: plugin magic mismatch
[xawtv=537067817,../libng/plugins/read-mpeg.c=537069088]
ERROR: plugin magic mismatch
[xawtv=537067817,../libng/plugins/read-mpeg.c=537069088]
dlsym[/usr/local/lib/xawtv/read-mpeg.so]: xawtv: undefined symbol:
_ng_plugin_init
dlopen: /usr/local/lib/xawtv/snd1-oss.so: undefined symbol:
ng_chardev_open
can't open /dev/video0: Device or resource busy
v4l-conf had some trouble, trying to continue anyway
v4l2: open /dev/video0: Device or resource busy
v4l2: open /dev/video0: Device or resource busy
v4l: open /dev/video0: Device or resource busy
no video grabber device available

Now i have been looking over this mailing list for several hours now
and this problem lookms simliar to the one described "Device or
resource busy - dont know what to do!" Thread in june. The person
having the problem however managed to solve it but they does not
descibe how they solved it. I would appreciate if i could get some
help on my little problem.

Thanks


Matthew


-- video4linux-list mailing list Unsubscribe
mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/video4linux-list
___________________________________________________
Meet your old school or college friends from
1 Million + database...
Click here to reunite www.batchmates.com/rediff.asp



--
video4linux-list mailing list
Unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/video4linux-list

Reply via email to