[MPlayer-users] ioctl request buffers failed: Invalid argument

[mini-k at thedadsarmy.com]

Anyone else seeing this or have a suggestion?

`mplayer /dev/video0` works fine.

When executing `mplayer tv:// -tv device=/dev/video0:driver=v4l2` or `mplayer
tv:// -tv device=/dev/video0:driver=v4l` I get 'ioctl get mbuf failed: Invalid
argument'

Full results of `mplayer tv:// -tv device=/dev/video0:driver=v4l2` :

MPlayer 1.0pre7try2-3.2.3 (C) 2000-2005 MPlayer Team
CPU: Advanced Micro Devices  (Family: 8, Stepping: 2)
Detected cache-line size is 64 bytes
CPUflags:  MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1


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.
Opening joystick device /dev/input/js0
Can't open joystick device /dev/input/js0 : No such file or directory
Can't init input joystick
Setting up LIRC support...
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support.
You will not be able to use your remote control.
Playing tv://.
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 ;-)
Selected device: WinTV PVR 150
 Tuner cap: STEREO LANG1 LANG2
 Tuner rxs: MONO LANG2
 Capabilites:  video capture  VBI capture device  tuner  audio  read/write
 supported norms: 0 = NTSC; 1 = PAL; 2 = SECAM;
 inputs: 0 = Tuner; 1 = Composite 0; 2 = Composite 1; 3 = S-Video 0; 4 = S-Video
1;
 Current input: 0
 Current format: unknown (0x4745504d)
v4l2: current audio mode is : STEREO
v4l2: ioctl request buffers failed: Invalid argument


MPlayer interrupted by signal 11 in module: demux_open
- MPlayer crashed by bad usage of CPU/FPU/RAM.
  Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
  disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.
  It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
  gcc version. If you think it's MPlayer's fault, please read
  DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
  won't help unless you provide this information when reporting a possible bug.