Raspberry Pi 4 wont boot.

[corematrix]

I'm having an issue with my 2018 Raspberry Pi 4 Model B and Motion Eye OS. It simply won't boot. I know it works well with Raspian and the attached Camera but it won't boot at all. I'm using the official imager software and etcher but still no luck.

Any thoughts?

motionEyeOS Version

20200606

Board Model

Raspberry PI 4B+).

Camera

Raspberry PI HQ

[ccrisan]

Alright guys, I'll see what the problem is. Thanks for reporting it.

[ccrisan]

I've identified the problem and fixed it in https://github.com/ccrisan/thingos/commit/8fc517678c369b3b5efa760cdbedc24058a27d78. The new nightly build dev20200907 should contain the fix. Please test and report back.

[starbasessd]

Tested last night & today on a 4GB and 8GB model. Working for wifi only booting. See other ticket for all issues tested.

On Mon, Sep 7, 2020 at 2:27 PM Calin Crisan notifications@github.com wrote:

I've identified the problem and fixed it in ccrisan/thingos@8fc5176 https://github.com/ccrisan/thingos/commit/8fc517678c369b3b5efa760cdbedc24058a27d78. The new nightly build dev20200907 should contain the fix. Please test and report back.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2419#issuecomment-688466167, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZTUHMFHOQESQLBW6CPCGTSEUQ2RANCNFSM4N2WG3XA .

-- Thanks

Kevin Shumaker

Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel

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?

[PaddyDax]

After installing dev20200907, wifi is still not working. Getting "Configuring wireless network: no link".

[starbasessd]

I've done new installs on 3 SDCards, (8GB, 16GB, and 32GB) and booted them all on both a 4GB RPi4 and an 8GB RPi4, no issue. Image SD Card copy wpa_supplicant.conf file to /boot (usually drive E: on my Win 10) install card to RPi4 Boot Works I will assume that you're able to boot the full, desktop, or Lite versions of RaspberryPiOS with the same process and it works? You need to copy the wpa_supplicant.conf file prior to boot. The content of the file needs to reflect your country, your ssid, and your password, with country in caps, and ssid and password in quotes as shown:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1 country=US

network={ ssid="ssid" psk="password" key_mgmt=WPA-PSK }

On Mon, Sep 7, 2020 at 6:47 PM PaddyDax notifications@github.com wrote:

After installing dev20200907, wifi is still not working. Getting "Configuring wireless network: no link".

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2419#issuecomment-688531863, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZTUHKQOFKAA6QLJJMLSMLSEVPJ5ANCNFSM4N2WG3XA .

-- Thanks

Kevin Shumaker

Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel

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?

[bespinalo]

After spending a whole day looking for a solution to be able to use my RPI4 4GB with Motioneyeos I did the following:

Edit the file called config.txt, the values gpu_mem = 128 to gpu_mem = 16 with this you could see the error when booting the RPI4

there I noticed that it was telling me that a start.elf file was missing, I copied that file from a working image of Raspbian OS to the SD where I had installed the Motioneyeos and that's it, with this I could load the OS correctly.

NOTE: I had created the wpa_supplicant.conf before. use version dev20201026 but it is the same error for this version and stable (20200606)

[starbasessd]

Did you update to the latest boot loader? https://www.raspberrypi.org/documentation/hardware/raspberrypi/booteeprom.md

On Mon, Mar 15, 2021 at 12:04 AM bespinalo @.***> wrote:

After spending a whole day looking for a solution to be able to use my RPI4 4GB with Motioneyeos I did the following:

Edit the file called config.txt, the values gpu_mem = 128 to gpu_mem = 16 with this you could see the error when booting the RPI4

there I noticed that it was telling me that a start.elf file was missing, I copied that file from a working image of Raspbian OS to the SD where I had installed the Motioneyeos and that's it, with this I could load the OS correctly.

NOTE: I had created the wpa_supplicant.conf before. use version dev20201026 but it is the same error for this version and stable (20200606)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2419#issuecomment-799073900, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZTUHNMMKBSBEO3PC54YQ3TDWBM3ANCNFSM4N2WG3XA .

-- Thanks

Kevin Shumaker

Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel

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?

[bespinalo]

Yes last version, Sep 3 2020 13:11:4

[starbasessd]

Oops, my bad. Pi4-8GB files with the incompatible start4.elf on 20200606. Even using the 2021-01-16 boot loader. Strange. @CCrisan This is only an issue with the 8GB Tripping as a bug. start4.elf is missing in build for dev20201026 Pi4-8GB boots fine Pi4-4GB works with 20200606 and dev20201026

Weird, huh? Pi4-4GB 20200606 Boot normal Pi4-4GB dev20201026 boot normal Pi4-8GB 20200606 fails with start4.elf not compatible Pi4-8GB dev20201026 boot normal 20200606 boots Pi4-4GB with start4.elf but fails with Pi4-8GB dev20201028 has start.elf but not start4.elf and boots both.

[crazydiamondAU]

yes this is the original problem I had.

I did not try the dev one . will give it a go when i get home

On Mon, Mar 15, 2021 at 11:42 PM starbasessd @.***> wrote:

Oops, my bad. Pi4-8GB files with the incompatible start4.elf on 20200606. Even using the 2021-01-16 boot loader. Strange. @ccrisan https://github.com/ccrisan This is only an issue with the 8GB Tripping as a bug. start4.elf is missing in build for dev20201026 Pi4-8GB boots fine Pi4-4GB works with 20200606 and dev20201026

Weird, huh? Pi4-4GB 20200606 Boot normal Pi4-4GB dev20201026 boot normal Pi4-8GB 20200606 fails with start4.elf not compatible Pi4-8GB dev20201026 boot normal 20200606 boots Pi4-4GB with start4.elf but fails with Pi4-8GB dev20201028 has start.elf but not start4.elf and boots both.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2419#issuecomment-799429599, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQD2YBC5HS3ZSPO4SWJJP2TTDYFF5ANCNFSM4N2WG3XA .

[Der-Bert]

Hi all, I´ve tested with raspi 4 2 GB RAM and 4GB RAM. Firmware ist 2020-09-03 the motioeyeos version is: motioneyeos-raspberrypi4-dev20201026

it works :-) hope the information helps

[starbasessd]

Siting here on a boring Sasturday (US EDT) testing vrious things, and lo and behold: Pi3B & B+ both boot from USB, too, using dev20201026. Even Supports my "Official" Raspberry Pi 7" DSI display, both WiFis, etc.Only change needed is in cmdline.txt, change root=/dev/mmcblk0p2 to /dev/sda2. Really nice. Thanks @ccrisan wish I had noticed before. Any chance of upgrading dev20201026 to release? And note the feature in Release Notes, too.

[Timmmm]

Thank you @starbasessd! Until I read your message all I got was a blinking cursor. Not even an error message. Changing root=/dev/mmcblk0p2 to root=/dev/sda2 gets me further (though Raspbian doesn't seem to require that change?).

Unfortunately I get the issue @corematrix mentioned - it seems to require a wired network connection to boot, otherwise it just reboots constantly.

---- booting motionEyeOS dev20201026 ----
 * Detecting disk device: /dev/sda
...
 * Configuring wired network: no link
panic: rebooting in 10 seconds (caused by network)
panic: rebooting (caused by network)

I previously used Motion Eye OS on a Raspberry Pi 3B and it didn't require an ethernet link.

[starbasessd]

@Timmmm Did you also include a valid wpa_supplicant.conf, and ssh.txt files, too?

[Timmmm]

Hmm so a little Googling told me that it was because I was missing wpa_supplicant.conf, which I thought was weird because I definitely created it. I tried again and it turns out it gets to

 * Starting wpa_supplicant:

And then it instantly reboots (no error) and deletes the wpa_supplicant.conf file! The next boot it goes back to * Configuring wired network and if I check the disk wpa_supplicant.conf is gone.

[starbasessd]

Please post your wpa_supplicant.conf (change SSID and Passphrase to generic) The biggest causes I've found are they are created with Windows Notepad (not NotePad++), use the wrong format, or have the name wpa_supplicant.conf.txt.

[Timmmm]

I didn't make those mistakes and the line endings are correct. I've tried this:

network={
    ssid="..."
    psk="..."
}

And this:

update_config=1
ctrl_interface=/var/run/wpa_supplicant

network={
    scan_ssid=1
    ssid="..."
    psk="..."
}

Here's a video because I suspect this sounds unbelievable.

https://user-images.githubusercontent.com/376842/119516150-68f6f780-bd6e-11eb-91c0-1728afc7e1b8.mp4

[Timmmm]

Oh one thing I should mention - I did run sudo rpi-eeprom-update -d -a to update the firmware. Not sure if that would affect things. However the official Raspbian release works fine even with the updated firmware.

[starbasessd]

Try:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1 country=US

network={ ssid="SSID" psk="passphrase" key_mgmt=WPA-PSK }

[starbasessd]

Oh one thing I should mention - I did run sudo rpi-eeprom-update -d -a to update the firmware. Not sure if that would affect things. However the official Raspbian release works fine even with the updated firmware.

It could if you used a modified boot order or other eeprom feature. the '-d' overwrites any options you might have set before.

[Timmmm]

I set the boot order afterwards (following this guide). It is booting from USB so I don't think that can be the issue.

The config you suggested actually worked! Pretty crazy! I would have thought if there were permission errors or whatever it would at least give an error message.

Unfortunately I then get another hard restart at * Creating SSH keys: or something like that.

I might just give up and install Motion Eye on Rasbian. :-/

[Timmmm]

Actually I may have spoken too soon. It worked once with that config, but now I can't get it to work again. I give up.

[starbasessd]

with all the false starts and restarts, I'd try starting over with a fresh image, and correct wpa_supplicant.conf and ssh.txt

[starbasessd]

with all the false starts and restarts, I'd try starting over with a fresh image, and correct wpa_supplicant.conf and ssh.txt and fixed cmdline.txt

[mrose84]

I copied these two files from a known good booting RaspberryPiOS to the /boot partition (fixup4.dat & start4.elf in zip file) This allows the RPi4-8GB to boot and run normally. This is a work-around until @ccrisan can update the image. This has been tested with the firmware update 2020-05-14 and motionEyeOS 20200606RPi4. Your mileage may vary. Please let me know if this helps you or not so I can make other notes.

RPi4-8GB-Boot-Files.zip

i know i'm a little late to this party, but i literally just made a github account to tell you i love you =)

[starbasessd]

BTW, if you update the rpi-eeprom to this year (latest is 4/29/2021) the dev20201026 not only boots to SDCard, but will boot to USB, too. Non-8GB can use 20200606...

[XanthisThePirate]

hey ive tried the fix from starbasessd and all it does is put my pi4 8GB into a boot loop. any help would be greatly appreciated.

[starbasessd]

So you have a 4/29/2021 or later rpi-eeprom, and you're using a valid wpa_supplicant.conf file with dev20201026 image, correct? If you have a monitor connected, can you see what the boot loop is caused by? Do you have an ethernet connection available to test with?

[tiensvanzyl]

Thanks @starbasessd dev20201026 did the trick for me on my Pi4 2GB. I am plugged into a LAN cable though and this image booted successfully

[starbasessd]

You should be able to set up WiFi on the Pi4-2GB and use it, too.

[RodCleaves]

I have the same problem as several commenters here. I have a perfectly well working security/camera system working on Pi 3. However, I decided to something a little more compact. So, I bought the new Zero 2 W. It runs everything I throw at it except MotionEyes OS. Depending on the version either nothing happens or it stops on the Raspberry splash screen, but never any further.

I can run anything else on Zero 2 W except motionEyes OS. I think this a great OS and I'd even pay for it. I'm not much of Linux internals guy. FYI, I have the one direct attached camera and three other wireless.

Any/all tips will be greatly appreciated. I'm more a hardware guy than a software guy, please take pity.

/rod

[starbasessd]

This thread is related to the Pi4 boot issues, not PiZero2W. There is an image (forked by @jawsper that seems to remedy the issue on PiZero2W, here: https://github.com/ccrisan/motioneyeos/issues/2827#issuecomment-967737252

[RodCleaves]

Got'ch. Sorry for the lack of edicate. Except for downloading a few things, today is first foray into commenting on GitHub. This thread seemed like it was close to the point. Frankly I didn't see a 'zero' thread. This OS works great on every SBC I've tried and was surprised with the 'zero 2 w' result.

Thanks, rod

[starbasessd]

@RodCleaves there are a couple threads in motionEyeOS for PiZero2W. You can also go the motionEye on another OS like RaspberryPiOS, Debian, Ubuntu, etc. If you have issues using Jawsper's image you can ask in that other thread, or open a new issue, and we'll do our best to help.

[starbasessd]

Closing. Many solutions posted in both open and closed issues. Most are related to the rpi-eeprom updates needed, post 4/2021.

[beug99]

Hello:) I have the same problem with motion eye OS, I downloaded 20200606.img and the two zip files, to fix the boot problem. However, no USB cameras are showing. I have now installed dev20201026.img.xz" but after doing this my pi will not turn on. Does anyone have any suggestions? I have a raspberry pi 400.

[starbasessd]

@beug99 Which image are you downloading, specifically? Can you tell us what error you are getting during the boot (what is showing on the monitor? Is it a network panic or something else?) Are you using Ethernet of Wifi? If wifi, 2.4GGhz (a,b,g,n) or 5GHz (ac)? Try connecting to the 2.4GHz. If using WiFi post your wpa_supplicant.conf file (delete your SSID & password) I posted what mine looks like below. The 400 has some changes from the Pi4 and came out after the last image was created (dev20201026) and wasn't tested.

---

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1 country=US

network={ ssid="SSID" psk=password }

[beug99]

I installed motioneyeos-raspberrypi4-dev20201026.img.xz](https://github.com/motioneye-project/motioneyeos/releases/download/nightly-dev/motioneyeos-raspberrypi4-dev20201026.img.xz) 57.2 MB Oct 26, 2020. No error appears on the screen, the Pi does not turn on. The green power light flashes for a few seconds and then turns off. I have been using wired internet connection. However, I can use wifi.

Here is my Wpa_supplicant.conf file:

country=AU ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1

QUT network

network={ ssid="QUT" key_mgmt=WPA-EAP eap=PEAP

put your QUT username between these quotes

    identity="n11578939"
    # replace the hash:... with a hash of your password
    # from ./wifi-pass.sh
    password=hash:866f74f294204881a12498fca7717e7b
    phase1="peaplabel=0"
    phase2="auth=MSCHAPV2"
    priority=10

}

My 1st Home network

network={ ssid="Telstra364C76" key_mgmt=WPA-PSK psk="zqvru6rsguzkcka8" }

My 2nd Home network

network={ ssid="SSID2" key_mgmt=WPA-PSK psk="PSKPASS2" }

Im not sure if it is correct.

[starbasessd]

@beug99 What utility are you using to put the image onto the SDCard? With the dev20201026 you don't even get the rainbow pre-load or the bootloader screens, but you do get them with the 20200606 image?

[beug99]

I use Raspberry Pi imager but have also tried to use balenaEtcher. Yes, I would get the rainbow preload screen with 20200606 image but not with the dev20201026, nothing comes up.

[starbasessd]

Do not use RPiImager. It is not designed to work with read only file systems like motionEyeOS. Any x file mods (like pre-loading the wifi settings in it) breaks the image. I don't have a 400 to test here, so I have no clue as to why it wouldn't work with dev20201026. I would grab another SDCard, do a clean install of dev230201026 with an older version of Etcher or Win32DiskImager (if Windows) or even dd if a linux or mac, to see if you can at least get the rainbow or bootloader screens. Also, change to the other HDMI port prior to boot to see if it makes a difference.

[beug99]

Thank you, I have solved the problem:) I downloaded motion eyes through my Pi terminal and have been able to connect to my USB camera:) However, I am now facing issues getting motion notifications to my email. I am getting this error message:

Notification email failed: 5.7.8 Username and Password not accepted. Learn more at 5.7.8 https://support.google.com/mail/?p=BadCredentials b23-20020a170902b61700b001a194df5a58sm2369523pls.167 - gsmtp!

I have removed special characters from my password but still does not work.

[starbasessd]

@beug99 did you go through the troubleshooting steps at that page? Did you create a 'less secure app' password? Do you have 2 factor authentication Turned on? If so, you must create the 'less secure app' password. Since Google went to the more secure logins for everything, it has created havoc for many apps, to the point that GDrive needs to be re-written for motionEye (and DropBox) and we are waiting on the new developers to do so...

[beug99]

Thank you for your fast response. I did follow the troubleshooting instructions and was still getting the error. The problem is solved. I connected it to my Outlook account instead.

[beug99]

But I am having this error with connecting my Dropbox as my file storage. Will this be fixed, when developers rewrite the GDrive? Sorry I'm pretty noob at this haha