Fedora Core 3 Motion fails with no mmap
I installed Fedora Core 3 with 2.6.11-1.27_FC3 kernel, installed all the various RPM associated including Motion 3.2.1. Using a WinTV
-PVR 150 with ivtv as the driver. It connects and appears to control the card (switching between NTSC and PAL in the syslog as appropriate from the config file) however it only runs for a second and then dumps with:
Processing thread 0 - config file /etc/motion/motion.conf
Thread 0 started
 No mmap falling back on read
motion-httpd/3.2.1 running, accepting connections
motion-httpd: waiting for data on port TCP 8080
capturing using read is deprecated!
 Motion now only supports mmap.
Seems rather odd, given I know mmap is in FC3. I assume there is something simple I am missing?
| Motion version:
| ffmpeg version:
|| curl, xmlrpc, ffmpeg, mysql, postgresql
| Server OS:
|| Fedora Core 3
- 02 Jun 2005
I need more analysis from your side to figure this out. Motion only supports the mmap way of reading images from the V4L
device. read is not supported. So if this is the only mode the driver supports then the card is not compatible with Motion. Maybe you should contact the driver team and ask.
Motion needs the image in either YUV420P
, YUV422 or RGB24 to work. (or greyscale)
Originator never came back. Question closed.
- 11 Aug 2005