Does not boot on Banana PI M1

[TheFax]

Board Model

Banana pi M1

MotionEyeOS version 20200606 does not work at all on Banana pi M1. It does not boot and never reaches the login prompt.

Version 20170326 works quite well, but it is 3 years old.

Log Files

I cannot get log files. I only read the screen log that appears during startup.

[starbasessd]

Did you try the dev20201026 here? 20170326 is 6+ years old. 20200606 had a number of issues across many SBCs. You could also try installing an OS, (preferably the Lite version) and install the motionEye following the instructions here.

[TheFax]

Yes, I tried today. It does not work, and it seems to me that the errors are quite similar. I also took some photos of the monitor in order to help the developers understand the issue.

These photos have been taken during first boot. First "errors" appears in this screenshot:

...and after this, the screen is quickly fullfilled of these lines:

If I wait some minutes, the software seems to try anyway to start-up MotionOs, but it results in a error:

Like I wronte on the first mesage, login prompt is never reached. Banana Pi asks correcty an IP via DHCP, but on port 80 there isn't any service active.

[starbasessd]

This is a clean install? Where did you set up SMB services? SAMBA (SMB) is not running by default in motionEyeOS, it must be enabled in the WebGUI, Settings, Services. If it is enabled and you had never connected to it, then the SDCard was never properly erased. Can you SSH into the Banana?

[TheFax]

Yes, this is a clean install, and what you see is the first boot. This is visible by the line "creating data partition" because this action is performed once at first boot. I never set-up SMB services because I never reached WebGUI. It is not possible to SSH into the Banana.

I tried with 2 different SD cards, both 4GB, and never deleted them because writing the image is by itself a deletion of original content. I used 3 different way to burn them: 1) WIndows - With Rufus 2) Windows - With Win32 Disk Imager 3) Linux - Using official writeimage.sh script

Despite this, I cannot ensure SD cards has issues. Version 20170326 works using same hardware and same burning software.

[TheFax]

Today, I performed the test using a brand new 16GB SD card. The results were the same as those obtained in my second post. I also tried downloading the 20200203 version, which exhibited the same behavior.

I read the scripts that runs on first boot: I'm not able to see the starting of "overlay_fs" in my screen logs.

[starbasessd]

I would try another OS install that supports Python 2.7 (Debian Buster does) because I doubt the new devs are probably uninterested in supporting the older SBCs that would require their own images. Other OS install instructions here