starbasessd

Created USB boot device using dev20201026 for Pi4 modified cmdline.txt from mmcblk0p2 to sda2 copied your uncompressed zipped /boot files to /boot copied my wpa_supplicant.conf and ssh.txt files to /boot...

Further on 4-4GB, ssh performance is almost nonexistent. top display takes 3-5 seconds, and refreshes are likewise slow/delayed. Haven't even bothered to install my cameras.

On my Pi4-8GB it does work as normal. Both on bootup, and into ssh session. Reboot, and system is corrupted. Will research further, but I believe it has to do...

@ccrisan I believe this maay be another good reason to run a new build for dev & release.

You need to update the rpi-eeprom to something from this year (Apr 2021 is latest) Raspberry Pi Imager provides a GUI for updating the bootloader and selecting the boot mode....

Using the RaspberryPiOS: vcgencmd bootloader_version rpi-eeprom-update report results for both commands Also, on the PRi4-8GB make sure you are using motionEyeOS dev20201026 and not 20200606

If you can figure out how it's triggered (see https://github.com/ccrisan/motioneyeos/issues/1636#issuecomment-424536198) If it's a simple dtbo file from /boot/overlays on a RaspberryPiOS you could copy that (those) files into the boot...

I don't have one to play with here, so I can only point you to the equivalent to the the #1636 comment... There may be apps, settings in /boot/config.txt that...

As to the motionEye issues, which instructions did you follow? You cannot access the stream until the camera is added and set up in motionEye. Did you use 'admin' and...

If I were a programmer, or had the ability to trigger a new build, I would be happy to help. I am but a Level 3 Enterprise Help Desk with...