Closed Gonioul closed 2 years ago
No, it was theoretically just released 28 Oct 2021. I don't know of anyone who has received one yet, or where they are available.
https://socialcompare.com/en/comparison/raspberrypi-models-comparison A53 4 core, but half the RAM of a Pi3B, so, again, theoretically closer related to the Pi3A. Only 802.11B/c/g/n, no ac.
Would need to get one in hand for testing. Be interesting to see what the boot process is, what OS mods were made, etc.
I have one on the way and plan to give it a shot so fingers crossed if I remember ill give both the PI Zero OS and the PI 3 OS a go and i'll let you know.
I really would appreciate it. Also, please try 20200606 and dev20201026.
I've tried the standard 20200606 pi 3 release and no lights/no boot(expected due to incorrect kernel). So have copied over the latest kernel including the Pi Zero 2 one and am now getting lights but no network connection. Will attempt to connect a screen to see if it's giving any errors out
im going to try the pi zero image and give that a go
I was afraid of that. buildroot, and ThingOS set up VERY specific chip combinations (CPU/GPU/WiFi) per version which is why 4b-8GB doesn't work on 20200606 but does work on dev20201026 (and the PiZeroW2 was but a 'gleam in the eye' of RPiFoundation. For now, I doubt if it will be a supported board with motionEyeOS, until @CCrisan can do a re-build. It should have no issues with building motionEye with the RPiOS or any others that can still support Python2.7.
Yep no luck on my end, I wonder if it's time to sell my soul to the devil and write my own kernal
Did you try dev20201026? I am beginning to doubt that buildroot / ThingOS has support (yet) for the PiZeroW2, either.
yep no luck leds flash, processor heats up no display out and im not gona mess with i2c with my brand new PI.
Have you tried PI-dev20201026 or Pi3-dev20201026 out of curiosity?
PI-3 Dev no luck I'll try the PI one
Thanks. Like I said, the motionEyeOS is very chip combination specific from buildroot and ThingOS. We'll have to wait until the next build to get the PiZeroW2 included.
I got my Pi Zero 2s today, and proceeded with testing.
Neither the RPi Zero 1 (motioneyeos-raspberrypi-20200606.img.xz) nor the RPi 3 (motioneyeos-raspberrypi3-20200606.img) images work - neither allows the RPi Zero 2 to boot (no LEDs seen, no network handshake/connectivity to router).
T'was my fear, the images are very chip specific. As I stated above, we'll have to wait. I do thank you for testing.
I've succeeded in booting MotioneyeOS on my Pi Zero 2 W, required changes are available in PR #2829
Many thanks, @jawsper, hopefully it will be added soon.
As motioneyeos is based on thingOS, I would expect the changes to be integrated there. I created a ticket to keep track of it: https://github.com/ccrisan/thingos/issues/75
i received it today. I hop a release of meyeos soon! :)
MotionEye https://github.com/ccrisan/motioneye/wiki has been confirmed operational in the mean time.
I've succeeded in booting MotioneyeOS on my Pi Zero 2 W, required changes are available in PR #2829
I tried making the image using the build script (after applying #2829 )got stuck a few times, and now at missing rootfs.tar.
@jawsper Could you please share how you did the building of the image?
Hi everyone! Any update on this? I have received my Pi Zero 2's and would really like to start using them. I have the same issue as r00kieone.....cant seem to build the image. @jawsper Can you please share the image file that works?
Just got my 2 W. The 20200606 hangs at the 4 enlarged pixels from the graphics chip and never goes further. I’m happy to help test a new image if one is available.
Currently, the only confirmed way to go is RaspberryPiOS Lite, and motionEye found here: https://github.com/ccrisan/motioneye/wiki/Install-On-Raspbian
Currently, the only confirmed way to go is RaspberryPiOS Lite, and motionEye found here: https://github.com/ccrisan/motioneye/wiki/Install-On-Raspbian
no fast camera support, right?
That would be correct, as Fast Network Camera is an option only available in motionEyeOS. The program that FNC uses is available, as 'streamEye' and can be seen here: https://github.com/ccrisan/motioneyeos/wiki/Fast-Network-Camera#streameye
That would be correct, as Fast Network Camera is an option only available in motionEyeOS. The program that FNC uses is available, as 'streamEye' and can be seen here: https://github.com/ccrisan/motioneyeos/wiki/Fast-Network-Camera#streameye
tank you. i'll wait a meyeos release for this board :). i need fast camera.
Currently, the only confirmed way to go is RaspberryPiOS Lite, and motionEye found here: https://github.com/ccrisan/motioneye/wiki/Install-On-Raspbian
I agree with Starbasessd, It works, but also I could only reliably get it doing so using Buster, not with Bullseye. (or it could be me)
On the Pi Zero2 Bullseye was failing at python-pip command, installing python3-pip didn't help, and I guess that's why I could not start the web interface, perhaps, maybe a different thread for that topic? Buster setup and installed the full motioneye without any issues.
Just a newbie's input :)
@HarveyBrookes I've posted updated instructions for RPiOS running Bullseye at: https://github.com/ccrisan/motioneye/wiki/Install-on-Raspbian-Bullseye It is fully functional (motionEye fully, not motionEyeOS fully)
No, it was theoretically just released 28 Oct 2021. I don't know of anyone who has received one yet, or where they are available.
I have one now, but Motioneye does not boot
@pdesimonee This issue opened the day after it was announced. As I stated on the other duplicate thread, and early in this thread, it's now a known issue. Harping on it doesn't do anything. A simple 'me too', or thumbs up (or down) would be sufficient.
@pdesimonee As of right now, the easiest solution is to go with https://github.com/ccrisan/motioneye/wiki/Install-On-Raspbian or https://github.com/ccrisan/motioneye/wiki/Install-on-Raspbian-Bullseye With the roughly 4 times more powerful CPU and better wifi, it handles running on the Lite OSs much better than the 1st gen PiZeroWs...
I've uploaded my built image here: https://github.com/jawsper/motioneyeos/releases/tag/20211113
The build instructions for my changes isn't really any different from the regular build, I personally used the docker build, makes it a lot easier to not run into issues with incorrect dependencies.
Edit: I messed up the release and based it on the wrong commit, so please just pretend the release was made based on my rpi-zero-2 branch :sweat:
@jawsper Is this a buildroot/ThingOS image? Is it strictly for the PiZeroW2 or all Pis, or PiZero, or Pi3?
Also, I've been running this build since my first comment here, and I've not had any issues with it. I even migrated the config from my Pi Zero 1 W and everything worked perfectly out-of-the-box.
@starbasessd This build should work on all Pi3 variants as far as I know, which should be the rpi-3-b, rpi-3-b-plus, rpi-cm3 and now also rpi-zero-2
It's a standard motioneyeos build, not sure how much of that is been synchronized with ThingOS, but I just took the latest code from here and updated a few packages, and made sure to add the rpi2-zero-2 device tree to the image.
@jawsper I was curious as to the date of the image (10/30/2021) until you stated you've been running it a while. Checking on a Pi3B+ (still haven't received a PiZeroW2 yet)
@jawsper Other than the PiZeroW2 support, anything added/upgraded? I was able to get it to boot SDCard on a Pi3B+ without issue. Wasn't able to get it to boot USB with the cmdline.txt change like dev20201026, though... Handy update as SDCards (even with the OS partitions Read-Only) USB drives last much longer...
The only changes I made are these:
raspberrypi/linux
to 5.10 (https://github.com/raspberrypi/linux/commit/3728690b4a894dd57d3913f048dcab12bb61251e)rpi-firmware
to 2ef3800b1b71c0e30c2a61ecad6e007ae96ea342
(https://github.com/raspberrypi/firmware/commit/2ef3800b1b71c0e30c2a61ecad6e007ae96ea342)rpi-wifi-firmware
to 3888ba29898bb3f056d5f1eb283cb8de4c533bef
(https://github.com/LibreELEC/brcmfmac_sdio-firmware-rpi/commit/3888ba29898bb3f056d5f1eb283cb8de4c533bef) (definitely needed for zero2)v4l2loopback
to 0.12.5
(https://github.com/umlaeute/v4l2loopback/commits/v0.12.5) (required for kernel 5.7+)bcm2710-rpi-zero-2.dtb
to the boot partitionNot sure if updating the kernel this from 5.4 all the way to 5.10 was strictly necessary, but I wasn't 100% sure if it would boot with the old kernel.
I'm not sure any of these changes would affect booting from USB...
@jawsper Thank you, your linked build worked for me. Using a V1.3 cam, but will try later with the HQ cam too. Have not tested all the functionality yet.
The only changes I made are these:
- Update
raspberrypi/linux
to 5.10 (raspberrypi/linux@3728690)- Update
rpi-firmware
to2ef3800b1b71c0e30c2a61ecad6e007ae96ea342
(raspberrypi/firmware@2ef3800)- Update
rpi-wifi-firmware
to3888ba29898bb3f056d5f1eb283cb8de4c533bef
(LibreELEC/brcmfmac_sdio-firmware-rpi@3888ba2) (definitely needed for zero2)- Update
v4l2loopback
to0.12.5
(https://github.com/umlaeute/v4l2loopback/commits/v0.12.5) (required for kernel 5.7+)- Copy
bcm2710-rpi-zero-2.dtb
to the boot partitionNot sure if updating the kernel this from 5.4 all the way to 5.10 was strictly necessary, but I wasn't 100% sure if it would boot with the old kernel.
I'm not sure any of these changes would affect booting from USB...
I just tested this with my PIzero2 and stuck on a boot loop due to no network.?
Did you insert a wpa_supplicant.conf (with valid country=xx line) (replacing xx with your country code) in the /boot partition prior to booting? It sounds like it got past the actual boot and hit the network watchdog.
I set the wifi info via RPI imager menu. I shall try an set it manually now and see what happens.
@jawsper - worked for me, as well, w/a v1.3 camera, in a zeroview enclosure. The new(er) zero-2 had no issues w/the enclosure, either. Did the headless boot config, manually (wpa_supplicant.conf, in /boot), with DHCP - works great. Not extensively tested, but everything seems to work - better streaming, higher fps - looks good! Thanks!
@wpa-3 Did a manual setup work? (vs the imager info) @Mumak Thanks for the info!
@jawsper - Perfect! Works with different cameras @ pi zeroW2, including the Raspberry Pi - Kamera, 12MP Sony IMX477R, IR-Camera,... out of the box!
@wpa-3 Did a manual setup work? (vs the imager info) @Mumak Thanks for the info!
It didn't work via the imager but once I added it manually as your suggested all was good. The only issues I seem to behaving I can only connect to the webUI via my mobile and not PC browser brave/edge all connected to the same wifi network of course.
@wpa-3 Is the PC on the same subnet as the mobile? (IP address the same first 3 numbers)?
@wpa-3 Is the PC on the same subnet as the mobile? (IP address the same first 3 numbers)?
Yes all the same network.
Hi,
Pi Zero 2 W is supposed to be Pi 3 compatible in Pi Zero format.
Has someone tested it with motioneyeos?
Regards,