Kamera kann nicht starten

Heute ist Stammtischzeit:
Jeden Donnerstag 20:30 Uhr hier im Chat.
Wer Lust hat, kann sich gerne beteiligen. ;)
  • Hi, I have Rasbian Linux raspberrypi 3.10.27+ #630 PREEMPT Fri Jan 17 19:44:36 GMT 2014 armv6l GNU/Linux

    I had this command:

    And the answer is:

    Code
    pi@raspberrypi ~ $ ./motion -n -c motion-mmalcam.conf
    [-1242819744] [NTC] [ALL] conf_load: Processing thread 0 - config file motion-mmalcam.conf
    [-1242819744] [NTC] [ALL] motion_startup: Motion mmaltest Started
    [-1242819744] [NTC] [ALL] motion_startup: Logging to file (/home/pi/motion.log)
    mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
    Segmentation fault

    Than, i wrote "sudo reboot", and after reboot "sudo motion"

    Code
    pi@raspberrypi ~ $ sudo motion
    [-1243004064] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motion.conf
    [-1243004064] [NTC] [ALL] motion_startup: Motion mmaltest Started
    [-1243004064] [NTC] [ALL] motion_startup: Logging to file (/home/pi/motion.log)
    mmal: mmal_vc_component_enable: failed to enable component: ENOSPC

    What I'm doing wrong ?

    It's my config file:

    Maybe someone can share his backup, who working mmal motion ?

  • All connected cables looks ok.
    On raspi-cofig i have enable camera.
    No, I can't, this is log:

    Code
    pi@raspberrypi ~ $ raspistill -o image.jpg
    mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
    mmal: camera component couldn't be enabled
    mmal: main: Failed to create camera component
    mmal: Failed to run camera app. Please check for firmware updates

    And after this command, the red led on camera was switch on -> https://www.dropbox.com/s/zhmuyuuhe9fb…%2013.40.09.jpg

  • Zitat


    [font="Monaco, Consolas, Courier, monospace"]Please check for firmware updates[/font]

    Do the following:

    Code
    sudo apt-get update
    sudo apt-get upgrade
    
    
    sudo rpi-update
  • I've had a similiar issue as well. The solution to my problem was to check processes that caused trouble at boot. Do you have a cronjob running which blocks the camera while the RasPi boots up? Check with "sudo crontab - l" and check running processes with "top".

    I had motion- mmal automatically turned on while booting and fixing an entry with crontab solved the problem.

    Greets

  • Yes, I have new Rasbian Linux raspberrypi 3.10.27+ #630 PREEMPT Fri Jan 17 19:44:36 GMT 2014.
    I have nettemp install from https://github.com/sosprz/nettemp , that propably I have w1-gpio loaded. How can i check this ?

    In crontab I have:


    Code
    pi@raspberrypi ~ $ sudo crontab -l
    */1 * * * * /var/www/nettemp/modules/sensors/temp_dev_read && /var/www/nettemp/modules/view/view_gen && /var/www/nettemp/modules/highcharts/highcharts
    */1 * * * * /var/www/nettemp/modules/gpio/gpio check
    */5 * * * * /var/www/nettemp/modules/sms/sms_send
    */5 * * * * /var/www/nettemp/modules/mail/mail_send
    @reboot     echo "$(date +\%y\%m\%d-\%H\%M) RPI rebooted" >> /var/www/nettemp/tmp/log.txt
    */1 * * * * /var/www/nettemp/modules/tools/system_stats
  • If my advice from above does not help, try the following:

    Please run

    Code
    top



    first and check for "motion-mmal" or "motion". End it with "kill" and the process id afterwards.
    There could be a chance that raspisill can't access your camera because motion is still using it!

    Since motion does not work with the official RasPi camera plugged in, you have to run

    Code
    sudo motion-mmal

    instead of motion. So inside your motion folder, run

    Code
    sudo motion-mmal -c motion-mmalcam.conf

    and monitor the output.

  • Hi,

    I had a similar issue with an error message when working with raspistill.
    I could fix it without downgrading by just checking the order of the modules (/etc/modules)to load.
    I used this order:

    Code
    snd-bcm2835
    w1-gpio pullup=1
    w1-therm
    w1-gpio
    i2c-dev
    i2c-bcm2708
    spi-bcm2708
    lirc_dev
    lirc_rpi gpio_out_pin=7

    and it worked fine.
    Make sure your raspi-blacklist.conf (/etc/modprobe.d) looks like that:

    Code
    #blacklist spi-bcm2708
    blacklist i2c-bcm2708

    This worked for me.

    Best regards
    Onki

Jetzt mitmachen!

Du hast noch kein Benutzerkonto auf unserer Seite? Registriere dich kostenlos und nimm an unserer Community teil!