Guido Draheim wrote:
Yes. I did just a test recording. Now there is just one problem left:
the 'szap' command does not have a '-c' flag anymore which used to
be there in the old dvb modules 'szap' version. That breaks my scripts
and at the moment I do not know how to access the second card - which
is pointed to another satellite (ye know, the usual astra/hotbird dual).
oops, an old 'szap' in another path - dvb_szap does it right with "-c".
forget about that one. And now I go with another pb, opening xawtv on
the videodev makes it work, closing it and reopening it I gets me bogus
messages about still being use - however there is no xawtv in ps -u
and fuser /dev/v4l/video* does not show anything. - I did want to
unload/reload the driver but they say too "device or resource busy".
$ This is xawtv-3.85, running on Linux/i686 (2.4.21-0.13mdk)
config: invalid value for input: Composite1
valid choices for "input": "DVB"
ioctl: VIDIOC_S_STD(std=0x7 [PAL_B,PAL_B1,PAL_G]): Device or resource busy
ioctl: VIDIOC_OVERLAY(int=1): Device or resource busy
v4l2: read: Device or resource busy
# fuser -va /dev/v4l/video*
USER PID ACCESS COMMAND
/dev/v4l/video0
No process references; use -v for the complete list
/dev/v4l/video1
No process references; use -v for the complete list
# lsmod
Module Size Used by Not tainted
ves1x93 6116 1
dvb-ttpci 290708 1
ttpci-eeprom 2616 0 [dvb-ttpci]
dvb-core 50924 0 [ves1x93 dvb-ttpci]
input 5664 0 [dvb-ttpci]
saa7146_vv 39388 1 [dvb-ttpci]
saa7146 13428 0 [dvb-ttpci saa7146_vv]
video-buf 15536 0 [saa7146_vv]
v4l2-common 4032 0 [saa7146_vv]
v4l1-compat 11300 0 [saa7146_vv]
what to check else?
I was `insmod dvb-core dvbdev_debug=1` to see what's wrong with the device