mmal: Received unexpected camera control callback event, 0x4

[trusk]

Hey guys,

This is my first time posting. So I bought the camera about 2 months ago, and until yesterday I didn't have the time to toy with it. So when I tried i kept getting

Code: Select all

mmal: Received unexpected camera control callback event, 0x4f525245

So naturally, I went to google, and found ideas in modifying raspi-blacklist.conf and modules. Now mine look like this:

Code: Select all

# blacklist spi and i2c by default (many users don't need them)
#blacklist spi-bcm2708
blacklist i2c-bcm2708

and

Code: Select all

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.

#w1-gpio
#w1-therm pullup=1

i2c-dev
i2c-bcm2078
spi-bcm2708
snd-bcm2835
bcm2708_wdog

Running i2cdetect -y 0 I get only dashes

Code: Select all

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- -- 

I would really appreciate some help. Also, I made sure the Sunny connector is in place.

[keendog]

yeah, i just started getting this error too, only I have had my camera for about 7 or 8 months. there are two places I have found posts on this problem or a related one.

https://github.com/raspberrypi/linux/issues/435

and

http://www.raspberrypi.org/forums/viewtopic.php?t=47627

The second post has no solution, but most people are getting the same issue, with the red light stuck on. Are you having the same LED response with this error?

[trusk]

Exactly. and I did everything that has been mentioned in issue #435

[Gecko2903]

Hey guys,

This is my first time posting. So I bought the camera about 2 months ago, and until yesterday I didn't have the time to toy with it. So when I tried i kept getting

Code: Select all

mmal: Received unexpected camera control callback event, 0x4f525245

So naturally, I went to google, and found ideas in modifying raspi-blacklist.conf and modules. Now mine look like this:

Code: Select all

# blacklist spi and i2c by default (many users don't need them)
#blacklist spi-bcm2708
blacklist i2c-bcm2708

and

Code: Select all

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.

#w1-gpio
#w1-therm pullup=1

i2c-dev
i2c-bcm2078
spi-bcm2708
snd-bcm2835
bcm2708_wdog

Running i2cdetect -y 0 I get only dashes

Code: Select all

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- -- 

I would really appreciate some help. Also, I made sure the Sunny connector is in place.

Did you ever find a solution to this issue?

[mantekka]

Looks like the camera is dead if this happens?
I have searched around various posts on this topic and none have a solution.
3rd camera module gone for me! I'm not buying another

[jeanleflambeur]

This happened to me a few days ago after trying to fit the raspi and the camera in a really tight 3d printed box. It turns out that in my case a few wires inside the ribbon cable snapped due to excessive bending. If I carefully twist the ribbon the camera works sometimes but most of the time I get the same error as the OP.

So before throwing away the camera try a new cable first.

[gfigo]

I got this error ("mmal: Received unexpected camera control callback event, 0x4f525245") after I downloaded and installed cmake and userland-master last version. Till that time my rpi camera was working. Now, there is no video feed on screen when I command "raspivid -t 20000". I've tried almost everything mentioned on forums but no change.

[Kemon]

My camera has been in the camera box for several months and worked last time I used it.
I just had exactly the same problem (0x4f525245), but after I checked Sunny connection, I saw there was a small gap and pushed it into place. Started RPI and ran "raspistill -o test.jpg" without errors.
Have been searching for this problem for several hours, but finally it works again.

I had a fresh install, update, firmware update and python-picamera installed.
sudo apt-get install rpi-update && sudo rpi-update
sudo apt-get update && sudo apt-get upgrade -y && sudo reboot
sudo apt-get install python-picamera

Hope it helps

[Amicus68]

Hello all, I encountered this exact issue with my pi camera just last night too... After reading the many posts on here I was convinced that I was just going to have to suck it up and buy a new camera module... that was until my buddy, Mike took a look at it today for me. The first thing he tried was pushing down on the beige colored control module located above (and connected to) the cameras black lens assembly. With a little bit of pressure It seated into place with an audible 'click'. I reconnected the camera module to my Raspi unit... booted her up and, BAM! My camera works again!!
I wanted to share this information with all of you folks encountering the same problem... I hope this trick fixes your cams too!

Cheers!

[spruce_capital]

Thanks to Amicus68, I too, am no longer looking at a new Camera module!
Re seated both ends of the grey cable and then tried the beige connector.
Now I have a picture again! Many thanks to the people on this forum for their posts!
Whether right or wrong, they spur on new directions to look for a solution.

[sudhi]

Folks ,
This is my second camera module.I keep receiving this message mmal: Received unexpected camera control callback event""
.Can some one clearly specify what needs to be done .Many thanks

[DougieLawson]

http://www.raspberrypi.org/forums/viewt ... 41#p564241

[pelicanpegs]

Hi Everyone

I recently purchased the Camera Module for my Pi and was receiving the same error "Unexpected Control Callback event" when trying to run motion. Both the Camera and PI (Model B) were brand new with a new SD card with Raspbian installed. I updated with apt-get update and upgraded but was still facing the same issue.

I tried all of the methods posted, blacklisting modules, checking ribbon cable, sunny connector etc, none of them worked.

Then tried swapping the camera and SD card to an older PI that I had lying about (another model B)

Now the camera works fine without any issue. The only difference I can see is that this PI that works has white clips where the camera connects and the one that doesn't work, they are black. I'm not sure if there are any other differences, but thought I would point this out just in case it may help. Let me know if you need me to confirm anything else.

Seems different people have had different things that work for them though.

[charliegalliher]

Same issue(s) here.I have over a dozen of these cameras - I use them to teach kids coding. I have lost almost all of them with the same error. I can verify it is not the cables (swapped them, problem follows the camera), not the boards or SDCard, or config (swapped pi boards, moved bad camera from port to port, then good camera from port to port - problem followed the camera). While $25 does not seem like much cash, $25 * 12 annually to keep a class up, really IS significant cash. I'm going to go with a hunch and suggest that something routine is shorting out the board . Hope it gets found...

[Clifco]

Another (y) to Amicus68, I was just about to swap the ribbon cable/bin it. The onboard connector isn't very obvious. Camera back in play....

[JDGodfrey]

Just received the same error. Had the pi and sitting on my desk, started shuffling things around and the camera fell onto the gpio pins and the pi reset. I'm sure it's fried and I've heard this module is more sensitive to failure from static discharge. Wondering if static is what has cause some of these cameras to fail and thought I might suggest the camera be put in a case to help prevent this problem.

[analog_guy]

wow, so complicated. Being an analog guy, i re-seated the connector and it worked.

[Roger Huang]

@Amicus68's answer worked like a charm!

Reseat the connector on the front side of the camera module (there is tiny letters 'sunny', perhaps this is the Sunny connector)

And everything works again : )

[TinyPi]

This happened to me a few days ago after trying to fit the raspi and the camera in a really tight 3d printed box. It turns out that in my case a few wires inside the ribbon cable snapped due to excessive bending. If I carefully twist the ribbon the camera works sometimes but most of the time I get the same error as the OP.

So before throwing away the camera try a new cable first.

Thank you, @jeanleflambeur . In my case, it was the cable that was at fault. Adjusted the position of the camera, thus the cable. The camera started working, without any errors. So, if the error persists, it is the cable that may need replacement.