On Sat, 2008-05-10 at 12:45 -0700, Michael wrote:

Michael,

Please try to remember not to top post; respond in line where relevant.

>[EMAIL PROTECTED] ~]$ lsmod |grep cx18
> cx18                   84256  0
> dvb_core               73640  1 cx18
> cx2341x                11972  1 cx18
> tveeprom               15024  1 cx18
> videodev               27392  1 cx18
> v4l2_common            16192  5 cs5345,tuner,cx18,cx2341x,videodev
> v4l1_compat            14532  2 cx18,videodev
> i2c_algo_bit            6436  1 cx18
> i2c_core               20448  5
> cs5345,tuner,cx18,tveeprom,i2c_algo_bit
> [EMAIL PROTECTED] ~]$ su
> Password:
> [EMAIL PROTECTED] michael]# modprobe cx18
> [EMAIL PROTECTED] michael]# exit
> exit
> [EMAIL PROTECTED] ~]$ dmesg |grep cx18
> cx18:  Start initialization, version 1.0.0
> cx18-0: Initializing card #0
> cx18-0: Autodetected Hauppauge card
> cx18-0: cx23418 revision 01010000 (B)
> cx18-0: Invalid EEPROM
> cx18-0: DVB & VBI are not yet supported
> cs5345 0-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
> cx18-0: Couldn't allocate buffers for encoder YUV stream
> cx18-0: Error -12 setting up streams
> cx18-0: Error -12 on initialization
> cx18: probe of 0000:02:02.0 failed with error -12
> cx18:  End initialization
> 
> 
> I'm not quit sure exactly what this all means, but thanks again for
> the help!


Error -12 is -ENOMEM (Out of Memory).

You can try this:

    # cat /proc/sys/vm/min_free_kbytes

and if it's not at least 16384 then

    # echo 16384 > /proc/sys/vm/min_free_kbytes
    # cat /proc/sys/vm/min_free_kbytes

Then

    # modprobe -r cx18
    # modprobe cx18


If you're OK at this point (no more -ENOMEM), add a line like this
to /etc/sysctl.conf:

        vm.min_free_kbytes = 16384


If you still got the -ENOMEM, then try this:

    # modporbe -r cx18
    # modprobe cx18 enc_ts_buffers=0  enc_yuv_buffers=0 \
                    enc_vbi_buffers=0 enc_pcm_buffers=0 \
                    enc_mpg_buffers=1

If that doesn't work then you may want to do an 

    # lsmod | sort -n -k2

to see which kernel modules have a large size, and consider removing
them (modprobe -r) temporarily if you can, to reclaim some memory.


If all that doesn't work, I'd actually have to do research as to how to
monitor memory use (sar maybe?) and then reclaim it.


Regards,
Andy



_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to