MPlayer 1istribution-Packman-4.0.2 (C) 2000-2005 MPlayer Team
CPU: Advanced Micro Devices (Family: 8, Stepping: 0)
Detected cache-line size is 64 bytes
CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1
Compiled with runtime CPU detection - WARNING - this is not optimal!
To get best performance, recompile MPlayer with --disable-runtime-cpudetection.
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: Connection refused
Failed to open LIRC support.
You will not be able to use your remote control.
Playing tv://.
TV detected! ;-)
Selected driver: v4l
name: Video 4 Linux input
author: Alex Beregszaszi
comment: under development
Selected device: zr36120 video
Capabilites: capture tuner overlay clipping scales
Device type: 171
Supported sizes: 32x32 => 768x576
Inputs: 3
0: Composite0: audio camera (tuner:0, norm

al)
1: Television: tuner audio tv camera (tuner:1, norm

al)
2: S-Video: audio camera (tuner:0, norm

al)
Card reports an unknown audio mode !
Trying two channel audio. Use forcechan to override.
Card reports an unknown audio mode !
Trying two channel audio. Use forcechan to override.
Card reports an unknown audio mode !
Trying two channel audio. Use forcechan to override.
Using input 'Television'
ioctl set picture 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.