[MPlayer-users] Unable to view tv: ioctl query fails with v4l2 driver

[ope]

I am trying to get mplayer to play tv but am running
into the following problem.

Hardware is:
AMD 850 CPU
ATI TV-Wonder VE capture card
nVidia GeForce4 video card

Running Debian unstable, kernel 2.4.22

If I run the following command:
mplayer -v tv://3 -tv
norm=NTSC:device=/dev/video0:driver=v4l2

I get the following output:
MPlayer 1.0pre3-2.95.4 (C) 2000-2003 MPlayer Team

CPU: Advanced Micro Devices Athlon Thunderbird 846.6
MHz (Family: 6, Stepping: 2)
Detected cache-line size is 64 bytes
CPUflags:  MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 0
SSE2: 0
Compiled for x86 CPU with extensions: MMX MMX2 3DNow
3DNowEx

Reading config file /etc/mplayer/mplayer.conf
Reading config file /home/liv/.mplayer/config
Reading /home/liv/.mplayer/codecs.conf: Can't open
'/home/liv/.mplayer/codecs.conf': No such file or
directory
Reading /etc/mplayer/codecs.conf: Can't open
'/etc/mplayer/codecs.conf': No such file or directory
Using built-in default codecs.conf.
CommandLine: '-v' 'tv://3' '-tv'
'norm=NTSC:device=/dev/video0:driver=v4l2'
get_path('font/font.desc') ->
'/home/liv/.mplayer/font/font.desc'
font: can't open file:
/home/liv/.mplayer/font/font.desc
Font /usr/share/mplayer/font/font.desc loaded
successfully! (206 chars)
Using MMX (with tiny bit MMX2) Optimized
OnScreenDisplay
Linux RTC init error in ioctl (rtc_irqp_set 1024):
Permission denied
Try adding "echo 1024 >
/proc/sys/dev/rtc/max-user-freq" to your system
startup scripts.
Using usleep() timing
get_path('input.conf') ->
'/home/liv/.mplayer/input.conf'
Can't open input config file
/home/liv/.mplayer/input.conf: No such file or
directory
Can't open input config file /etc/mplayer/input.conf:
No such file or directory
Falling back on default (hardcoded) input config
get_path('3.conf') -> '/home/liv/.mplayer/3.conf'

Playing tv://3.
STREAM: [null] tv://3
STREAM: Description: Null stream
STREAM: Author: Albeu
STREAM: Comment:
TV detected! ;-)
Selected driver: v4l2
 name: Video 4 Linux 2 input
 author: Martin Olschewski
<olschewski at zpr.uni-koeln.de>
 comment: first try, more to come ;-)
v4l2: ioctl query capabilities failed: Invalid
argument
v4l2: 0 frames successfully processed, 0 frames
dropped.
v4l2: up to 0 video frames buffered.


Exiting... (End of file)


I am not sure why ioctl fails when I specify v4l2.  If
I specify v4l the driver is able to detect the ATI
TV-Wonder without any problems.  Does anyone have an
idea why this could be happening?  Is the difference
between v4l and v4l2 enough that I should take the
time to figure it out or should I ignore and just use v4l?

__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus