Rpi 2B stuck at rainbow test image

[Dennis Jones]

Hello All....  first time poster here.  I have been attempting to load the MotionEyeOS on two of my Rpi 2Bs.  Both stick at the rainbow screen. Here's what I have checked and tried:

1. I use Balena Etcher to write the image

2. I use a Windows 10 machine to run Balena Etcher

3. I have tried two different class 10 23GB SD cards - no joy

4. I have download a new img three times - no joy

5. I have booted two different Rpi 2Bs with just Raspbian (no motioneyeOS) - both succeeded

6. I have removed any USB attachments (wireless and keyboard/mouse) - no joy

7. I copied a known good kernel to the motiioneyeOS SD - no joy

8. Reset the kernel to the downloaded one again - no joy

9. Did a search of issues on the GitHub page - no joy

10. Did a search on this group - no joy other than problems with Rpi 3B+ that were similar

11. Did a web search using Bing, Google - no joy other than it seems to point to a corrupted kernel.

I'm sorry if I have wasted anyone's time but would like some advice as to what to try next.  Thank you ahead of time.

//dj

[Kevin Shumaker]

I recommend  RPiImager (available from the RPiFoundation website

 or Win32Disk Imager https://sourceforge.net/projects/win32diskimager/

Be sure to use: https://github.com/ccrisan/motioneyeos/releases/download/20200606/motioneyeos-raspberrypi2-20200606.img.xz image

I just did a 16GB SDCard with no issue for my Pi2

--
You received this message because you are subscribed to the Google Groups "motioneye" group.
To unsubscribe from this group and stop receiving emails from it, send an email to motioneye+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/motioneye/c0d3af16-058b-4fc7-97a4-0ab2950d731cn%40googlegroups.com.

--

Thanks

Kevin Shumaker

Personal Tech Support

N38° 19' 56.52"
W85° 45' 8.56"

Semper Gumby
“Don't tell people how to do things. Tell them what to do and let them surprise you with their results.” - G.S. Patton, Gen. USA
Ethics are what we do when no one else is looking.
Quis custodiet ipsos custodes?

“There is no end to the good you can do if you don’t care who gets the credit.” - C Powell

You know we're sitting on four million pounds of fuel, one nuclear weapon and a thing that has 270,000 moving parts built by the lowest bidder. Makes you feel good, doesn't it?

[Michael Cooper]

I totally agree with Kevin

To view this discussion on the web visit https://groups.google.com/d/msgid/motioneye/CACYR9JfhNcV2xUpajwpq5_MN5duj3SbwX8Za0K0SDn98oZ0dqw%40mail.gmail.com.

--
Michael A Cooper
Linux Certified / Docker Certified
http://www.coopfire.com

[Dennis Jones]

Thank you Kevin.. I am going to try that and I'll report back in a while.   The last statement in your signature gave me a smile.  I rode a nuclear fast attack submarine during the Cold War and it was similar - rode for the first year before I was qualified and got my own bunk - next to a Subroc.  18" away from a nuclear warhead on a boat that was the same class as the USS Thresher which many know was lost at sea.  The first deployment after our yard period to get a  new nuclear power plant we did our sea trials in the Bahamas and did the exact evolutions that the Thresher did.... it was a tooshy tighteninig time! LOL

[Dennis Jones]

Thank you to all who offered ideas/help...  as it turns out, my Raspberry Pi Model 2B has a glitch and will not function with the MotionEyeOS.  I set up another Model 2B with a fresh download on a fresh SD card and it booted up and is running now.  My only issue is that I see that the local Raspberry Pi camera isn't "seen" by the OS... checking some things now.  But thank you all for your help.

Dennis

On Friday, February 19, 2021 at 4:02:12 PM UTC-6 StarbaseSSD wrote:

[Kevin Shumaker]

Thanks for the update.

Glitch in that particular Pi? May one ask what kind of glitch?

As to your camera, I've seen 2 common issues: Bad ribbon cable, or cable not oriented correctly at camera end or at the Pi end.

It should be 'auto-discovered' but if not, then added as a MMAL type.

Let us know if we can be of further assistance...

[Dennis Jones]

I'm constantly amazed at how seemingly difficult issues are in reality - simple.  I spent too much time fiddling with the camera from the computer vantage point and didn't think to remove the camera from the Pi box it is installed in.  Once I did that, and carefully inspected the camera, I realized that the camera connection to the camera PC board was not completely locked down.  Relieved that this was the issue regarding whether I would see a picture or not,, I pushed the connector down and started up my MotioneyeOS Pi again.  Still no picture.  I fortunately had not fastened the camera board in the pi-box yet and saw that the connector had popped off again.  So here is how I fixed this issue... I cut two very small pieces of velcro, super-glued one piece to the top of the connector and then attached the other piece on top of it.  Once it was re-installed in the Pi-box it was being held in place by those pieces of velcro.  So I now have a new security camera device that I'm having some fun with!  

To answer the other question re: "the glitch," I am not completely sure what difference there is between the two Pi 2 Model B's might be, but once I switched to the second Pi 2 Model B, everything went swimmingly with regard to getting past the rainbow boot up screen..  Referring back to the iterations I went through attempting to get past that doesn't provide an answer either.  So I downloaded the latest version of Buster and painted it on the original 32GB SD Card.  The Pi Model 2B that would not work with MotioneyeOS worked just fine using the Buster build.  I'm in the process of updating that Pi and am thinking of what else I could do to discover what the issue could be.  If you have any suggestions as to what you might check if it were you with the same issue, I'm all ears! LOL  Otherwise I am thinking that if I were to have a video of my troubleshooting with audio, I might find that it was <again> a cockpit malfunction or better described as PEBKAC; Problem Exists Between Keyboard and Chair. LOL.

Last, I am completely surprised at how well MotioneyeOS handles video on a Raspi Model 2B!!!  For such a limited machine it does wonderfully.  It's a pleasant surprise and Kudos to Mr. Risan and his creation.  I'm already planning on expansion of the number of cameras and finally have found use for the many Raspberry Pi's I have laying about!  Kudos also to Chris of YouTube's "Explaining Computers" for doing such an informative video on MotioneyeOS.  I highly recommend Chris and his YouTube channel.  I believe his abilities are top notch in sharing computer related knowledge to the masses as well as being a very good 'British Dry" comedian.  Hope others benefit from all of this as much as I did... learned quite a bit.

//dj

[Kevin Shumaker]

Thank you for the update

 It does help. The cable issue is one of the bigger ones with RPiCams.

There are 2 models of the Pi2B: the older one with a 2836 Broadcom chip V1.1 (which I have) and the last generation manufactured with a 2837 Broadcom chip V1.2. The supposed only real difference is whether it can be

 USB booted without an SD Card. Unfortunately, motionEyeOS doesn't support boot from anything from SDCard (my personal pet peeve... A ThingOS issue)

I would try an older version of motionEyeOS (like 20190911) and just be sure to download and install with Win32DiskImager or RPiImager, rather than the product you used before.

If you get the Rainbow screen, it usually means you have the wrong version (Like motioneye-raspberrypi or motioneye-raspberrypi3. It's a wrong kernel error, and each version is kernel specific.

--
You received this message because you are subscribed to the Google Groups "motioneye" group.
To unsubscribe from this group and stop receiving emails from it, send an email to motioneye+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/motioneye/abffc3ff-fd7e-4e90-b1dd-53958226ec63n%40googlegroups.com.