video buffer size (128 kB) is too small

есть 2.6.17, rh11, там стоят две карты DC10plus Pinnacle

в 2.4 я накладывал bigphysarea patch и при загрузке ядру давал команду ядру при старте mem=235M bigphysarea=4096, что высвобождало мне дял нужд видео 16
метров оперативы и все было отлично и отлично работало, цифровало
видео 768x576.

Вся фишка в том, что этого патча для ядра 2.6.17 нет.
И система грузит автоматом дрова для карт и вот такое дело:

Jun 28 05:19:33 observ motion: [0] Processing thread 0 - config file motion-dist.conf
Jun 28 05:19:33 observ motion: [0] Unknown config option "ffmpeg_cap_new"
Jun 28 05:19:33 observ motion: [0] Unknown config option "ffmpeg_cap_motion"
Jun 28 05:19:33 observ motion: [0] Unknown config option "ffmpeg_timelapse"
Jun 28 05:19:33 observ motion: [0] Unknown config option "ffmpeg_timelapse_mode"
Jun 28 05:19:33 observ motion: [0] Unknown config option "ffmpeg_bps"
Jun 28 05:19:33 observ motion: [0] Unknown config option "ffmpeg_variable_bitrate"
Jun 28 05:19:33 observ motion: [0] Unknown config option "ffmpeg_video_codec"
Jun 28 05:19:33 observ motion: [0] Unknown config option "ffmpeg_deinterlace"
Jun 28 05:19:33 observ motion: [0] Unknown config option "movie_filename"
Jun 28 05:19:33 observ motion: [0] Unknown config option "timelapse_filename"
Jun 28 05:19:33 observ motion: [0] Unknown config option "sql_log_image"
Jun 28 05:19:33 observ motion: [0] Unknown config option "sql_log_snapshot"
Jun 28 05:19:33 observ motion: [0] Unknown config option "sql_log_mpeg"
Jun 28 05:19:33 observ motion: [0] Unknown config option "sql_log_timelapse"
Jun 28 05:19:33 observ motion: [0] Unknown config option "sql_query"
Jun 28 05:19:33 observ motion: [0] Motion 3.2.10 Started
Jun 28 05:19:33 observ motion: [0] Thread 1 is from motion-dist.conf
Jun 28 05:19:33 observ motion: [0] Webcam port 8085
Jun 28 05:19:33 observ kernel: DC10plus[0]: zoran_open(motion, pid=[12680]), users(-)=0
Jun 28 05:19:33 observ motion: [1] cap.driver: "zoran"
Jun 28 05:19:33 observ motion: [1] cap.card: "DC10plus[0]"
Jun 28 05:19:33 observ motion: [1] cap.bus_info: "PCI:0000:01:02.0"
Jun 28 05:19:33 observ motion: [1] cap.capabilities=0x04000007
Jun 28 05:19:33 observ motion: [1] - VIDEO_CAPTURE
Jun 28 05:19:33 observ motion: [1] - VIDEO_OUTPUT
Jun 28 05:19:33 observ motion: [1] - VIDEO_OVERLAY
Jun 28 05:19:33 observ motion: [1] - STREAMING
Jun 28 05:19:33 observ motion: [1] Supported palettes:
Jun 28 05:19:33 observ motion: [1] 0: RGBO (15-bit RGB)
Jun 28 05:19:33 observ motion: [1] 1: RGBP (16-bit RGB)
Jun 28 05:19:33 observ motion: [1] 2: BGR3 (24-bit RGB)
Jun 28 05:19:33 observ motion: [1] 3: BGR4 (32-bit RGB)
Jun 28 05:19:33 observ motion: [1] 4: YUYV (4:2:2, packed, YUYV)
Jun 28 05:19:33 observ motion: [1] 5: MJPG (Hardware-encoded Motion-JPEG)
Jun 28 05:19:33 observ motion: [1] index_format 6 Test palette YUYV (640x480)
Jun 28 05:19:33 observ kernel: DC10plus[0]: v4l_set_format() - video buffer size (128 kB) is too small
Jun 28 05:19:33 observ motion: [1] Error setting pixel format.
Jun 28 05:19:33 observ motion: [1] VIDIOC_S_FMT: Invalid argument
Jun 28 05:19:33 observ kernel: DC10plus[0]: v4l_grab() - wrong bytes-per-pixel format
Jun 28 05:19:33 observ kernel: DC10plus[0]: v4l_set_format() - video buffer size (128 kB) is too small
Jun 28 05:19:33 observ kernel: DC10plus[0]: v4l_grab() - wrong bytes-per-pixel format
Jun 28 05:19:33 observ kernel: DC10plus[0]: v4l_set_format() - video buffer size (128 kB) is too small
Jun 28 05:19:33 observ motion: [1] Failed with all supported palettes - giving up: Invalid argument
Jun 28 05:19:33 observ kernel: DC10plus[0]: v4l_grab() - wrong bytes-per-pixel format
Jun 28 05:19:33 observ motion: [1] Could not fetch initial image from camera
Jun 28 05:19:33 observ motion: [1] Motion continues using width and height from config file(s)
Jun 28 05:19:33 observ motion: [1] Resizing pre_capture buffer to 1 items
Jun 28 05:19:38 observ motion: [1] Closing active webcam sockets


Вобщем, каким образом мне корректно выделять память для нужд видео
оцифровки? и где в этом редхате указать параметры загрузки модуля?
Либо на крайний случай rmmod'ить загруженные модули и modprob'ить их
заново с параметрами?

Cпасибо.