motioneye
motioneye copied to clipboard
motioneye-project
"no device" when starting wifi on RPi Zero 2 W on Jaspers image
When trying to boot Jaspers Image for the Raspberry Pi Zero 2 W I get the following error:
` * Detecting disk device: /dev/mmcblk0
- Checking data filesystem: done
- Mounting filesystems: done
- Mounting overlay filesystems: done
- Loading kernel modules: done
- Setting hostname: done
- Configuring CPU frequency: done
- Starting syslogd: done
- Loading device-tree overlays: done
- Starting throttle watcher: done
- Starting eudev: done
- Starting watchdog: done
- Starting rngd: done
- Preparing AP interfaces: none
- Starting wpa_supplicant: no device
- Configuring wireless network: no device
- Configuring wired network: no device`
I get this error on 2 different boards with this image. Using the official Raspbian Image I do not get this error. I also tried this on 2 differently named wifi networks with the same result. When using a usb-to-network adapter it boots sucessfully. I checked then that the wpa_supplicant.conf was written correctly, and it was.
Any ideas? Maybe a missing driver or something?
Sounds like a corrupted image. The whole point of @jawsper s image is because the 'official' motionEyeOS images don't have support for the wifi chip on the PiZero2W.
Can you post your wpa_supplicant.conf file (blot out the SSID and password) Make sure that the wpa_supplicant.conf doesn't end with .txt if created on a Win10 machine. Is it the same file that is copied to the /boot partition on the RPiOS image?
The content of my wpa_supplicant.conf:
`country=DE update_config=1 ctrl_interface=/var/run/wpa_supplicant
network={ scan_ssid=1 ssid="MYSSID" psk="MYPASSWD" }`
and the extension is just .conf not .txt
I downloaded the image again, and tried it with balenaEtcher and the Raspberry Pi Imager. No success.
Is it possible that I do not have the same wifi chip as you? How can I check that?
You are sure you have the PiZero2W card? What does it have for model number on the back? I haven't heard of any 'newer' models, yet. You state the PiZero2Ws connect on wifi using RaspberryPiOS? Without the usb to ethernet adapter? Also assuming the ` at the beginning of the first line and end of the last line are not in the actual file...
I'm pretty sure. I bought them here: https://www.elektor.de/raspberry-pi-zero-2-w
Added some photos of one of the boards
.
Hi Derolly, I am facing very same issue. Here is the link to img I am trying:
https://github.com/jawsper/motioneyeos/releases/download/20211113/motioneyeos-raspberrypi3.img.gz
And here what is containing wpa_supplicant.conf file. I have used Linux enters "LF".
country=CZ ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1
network={ ssid="ssid" psk="psswd" }
For parsing issues, can you move the country=CZ to the 3rd line? Can you add key_mgmt=WPA-PSK to the line after psk= and before }
Hi Starbasessd,
just tested with the same result.
Here is the config file: ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1 country=CZ
network={ ssid="ssid" psk="passwd" key_mgmt=WPA-PSK }
Console output:
- booting motionEyeOS unknown
- Detecting disk device: /dev/mncblko
- Creating data partition: done
- Formatting data partition: done
- Mounting data partition: done
- Copying data skeleton: done
- Mounting filesystems: done
- Mounting overlay filesystems: done
- Setting empty root password: done
- Copying version file: done
- Setting UTC timezone: done
- Loading kernel modules: done
- Setting hostname: done
- Configuring CPU frequency: done
- Starting syslogd: done
- Loading device-tree overlays: done
- Starting throttle watcher: done
- Starting eudeu: done
- Starting watchdog: done
- Starting rngd: done
- Preparing AP interfaces: none
- Starting wpa _supplicant: no device
- Configuring wireless network: no device
- Configuring wired network: no device panic: rebooting (caused by network)
- shutting down motionEyeOS unknown
- Stopping motioneye: failed
- Stopping smbd: failed
- Stopping nbd: failed
- Stopping proftpd: failed
- Stopping sshd: failed
- Stopping crond: failed
- Stopping ntpd: failed
- Stopping network: done
- Stopping pa_supplicant: done
- Stopping rngd: done
- Stopping eudev: done
- Stopping throttle watcher: done
- Stopping syslogd: done The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes Requesting system reboot
If it were an official image, I'd be questioning: /dev/mncblko that would be /dev/mmcblk0 , but maybe @jawsper has an idea?
Sorry, /dev/mncblko is my fault. I took a picture of the screen and did OCR. I can see "0" (zero) on the picture but OCR wrote it as "o". Again sorry for this confusing.
Hi @MStcz, can you check if there's a file called bcm2710-rpi-zero-2.dtb in your boot partition? (the same as where you put the wpa_supplicant.conf)
Hi @jawsper, it is there. MD5 of the file is E3C5B4E88C84C8351E8FD44C4FCD652B.
Hmm that matches the one I have. Have you tried running the official Raspberry Pi OS on this specific Pi, to rule out a hardware issue?
On my two Pi zero 2 w the official Raspbian Buster runs perfect. Thats what I'm using motioneye on right now. But your image still does not work with both zero 2 w.
This image is working with the same wpa_supplicant.conf config file. https://downloads.raspberrypi.org/raspios_armhf/images/raspios_armhf-2021-11-08/2021-10-30-raspios-bullseye-armhf.zip
I'm having the same issue with zero results in changing the wpa_supplicant.conf (I've tried them all). I have another Pi Zero2 which is working fine. Using that image doesn't work either.
The only difference between the Pi Zero2's are the version and chip serial.
Working: version 1.5 with chip serial 210340G Not working: version 2.11 with chip serial 210340E
*edit Both are working fine with bullseye by the way.
@dvandijk Interesting. Can you post a pic of both PiZero2W backs (where it shows the version number)? I have been told in the RPi forums that there aren't 2 versions, but that would explain why there are more and more issues...
Ah that is very interesting! Seems there could be a new chip revision, possibly requires another rpi-firmware update.
Interesting, the main CPU does seem to be identical, but perhaps they had to update the Wifi chip. I'll build an image with the latest firmware later tonight.
@dvandijk Any chance you could get the identifying info off the silver WiFi chips? Please?
@dvandijk Can you try this new version? https://github.com/jawsper/motioneyeos/releases/tag/20220119-dev I updated rpi-firmware (not sure if needed) and rpi-wifi-firmware (this may fix your issue).
I tried the image and can confirm that it works on my pi! Thank you @jawsper 👍
HI @jawsper, thank you for the build. It works for my PiZero2W when other builds would not. However, applying config changes to the camera with you build yields this error for my Remote MotionEye Camera.
2022-01-30 03:02:17: [motioneye] ERROR: 'privacy_mask' Traceback (most recent call last): File "usr/lib/python2.7/site-packages/tornado/web.py", line 1548, in _stack_context_handle_exception File "usr/lib/python2.7/site-packages/tornado/web.py", line 1756, in wrapper File "/usr/lib/python2.7/site-packages/motioneye/handlers.py", line 297, in post File "/usr/lib/python2.7/site-packages/motioneye/handlers.py", line 205, in wrapper File "/usr/lib/python2.7/site-packages/motioneye/handlers.py", line 537, in set_config File "/usr/lib/python2.7/site-packages/motioneye/handlers.py", line 376, in set_camera_config File "/usr/lib/python2.7/site-packages/motioneye/config.py", line 834, in motion_camera_ui_to_dict KeyError: 'privacy_mask' 2022-01-30 03:02:17: [motioneye] ERROR: 500 POST /config/1/set/?_username=admin&_admin=true&_signature=adb1e6260cf73e1d5c822e8f0aba57e1f72fa5b9 (192.168.1.31) 15.75ms
I do notice an inconsistent use of "/" leading (missing in the first 2 lines), maybe a bad edit? Are both motionEyes running on PiZero2Ws? Or which is which?
I do notice an inconsistent use of "/" leading (missing in the first 2 lines), maybe a bad edit? Are both motionEyes running on PiZero2Ws? Or which is which?
I doubled check and was able to reproduce the missing "/" - its not a bad edit. I am running PiZero2W.
