Pi Zero W newer releases getting stuck, not working #2106
Comments
|
BTW: I tried going through other Pi Zero W issues, most seem unrelated to this; as they fail to work at a later or earlier stage during boot. |
|
I'm sorry I cant help you with your problem. But I hope you can help me with a small question I have. What version should I use for the Pi Zero W? Its not clearly named bij the downloads. I'm looking the latest release version 20190427. Hope you can help! |
|
@puresilk could you try and make a short video recording of the issue? Recovering the log files from the SD card when that happens could also help. |
|
@YannickGro https://github.com/ccrisan/motioneyeos/wiki/Supported-Devices will tell you to download the raspberrypi (1) version. |
|
@ccrisan, I will make a video recording on the week-end. Where are the log files stored? I did not notice any on the FAT partition after removing the SD card. |
|
@puresilk they are on the large EXT4 partition, accessible from Linux. |
|
Don't know if it is related: Just started today with motioneyeos on a Raspberry Pi Zero. Booting worked as expected, by I get reboots every now and then (3 times within the last 30 minutes while playing around). |
|
@avanc version and logs please. |
|
Sure. motionEye Version: 0.41 Is the stack traces related to Wifi? I can connect via SSH to the device and I'm asked for the password. However, I don't get a prompt afterwards. |
|
The stack traces in your log are definitely related to WiFi. Try reducing the ARM frequency to 950 in your |
|
Sorry for not following up on this earlier, "life got in the way". Here's a screenshot of the boot. It happens also when I unplug & reboot. I'm using the most recent release. The screen will get stuck at this "forever". I am using a Pi Zero W to boot it.
I don't seem to be able to find a dmesg.log or any other log file on the SD card after removing it (after the second boot attempt). I assume that this log is never written to the SD card. My only modification (prior to the first boot) was to add a wpa_supplicant.conf file:
One further note: I'm not flashing on blank SD cards, but on SD cards with Raspbian / NOOBS on them. This should not make any difference, but mentioning it just in case. |
|
On the back of the Pi, it says which model it is, can you check and see?
One of mine says:
Raspberry Pi Zero W V1.1
(C) Raspberry Pi 2016
Can you try dev20201026 or 20190911 please? Found here:
Releases · ccrisan/motioneyeos
<https://github.com/ccrisan/motioneyeos/releases>
…On Wed, Dec 30, 2020 at 5:33 AM Maximilian Batz ***@***.***> wrote:
Sorry for not following up on this earlier, "life got in the way". Here's
a screenshot of the boot. It happens also when I unplug & reboot. I'm using
the most recent release.
[image: image]
<https://user-images.githubusercontent.com/4606111/103345615-24528300-4a92-11eb-84f0-3e90ab517f3a.png>
I don't seem to be able to find a dmesg.log or any other log file on the
SD card after removing it (after the second boot attempt). I assume that
this log is never written to the SD card.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2106 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEZTUHIKY46GROT53SZUV73SXL6Y7ANCNFSM4IYLFKKQ>
.
--
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?
|
|
Possibly the Pi Zero W I'm using is defective; it works on another one. I'm closing this for now. |
|
Pi Zero 2 W arrived the other day, works fine with Pi OS and with Octoprint but just freezes with MotioneyeOS, |
|
As I've written on this page here: Raspberry Pi Zero 2 W needs up-to-date boot files. Try fixing motionEye OS boot with copying the boot files as I've outlined, and report back whether that works. |
|
Could you please open a new ticket for this issue (with all the questions answered) for the PiZeroW2, your issue, and solution found, please, link it here, and close this issue? The PiZero/W/H is only related to the PiZeroW2 by form factor. The chips used are very different (both CPU and WiFi) and the issues don't apply to both. |
I am a Raspberry Pi approved reseller, and sell kits including motioneyeOS (an older version)
I have tried several recent motionEyeOS releases with a very recent Pi Zero W (just arrived from the factory) in order to ship newer versions to customers. They all hang during boot with the same message "loading kernel modules", even if given ample time to finalize the loading.
I have preconfigured all of these SD cards with a wpa-supplicant.conf before booting up motioneyeOS.
ccrisan, I can test the newest version with a Pi Zero W, make sure it does not work, and can ship it (or several if you want) to you on my cost, as a contribution to your project. Please let me know if you would like that, to allow easier debugging for you.
motionEyeOS Version
I have tested the following releases (all Pi 1 releases):
With all of these releases the Pi Zero W hangs during boot with the message "loading kernel modules" (to be seen via HDMI output
The following version works for me on the same Pi Zero W:
Board Model
I am using the following board/model: Pi Zero W.
Camera
Default Raspberry Pi camera.
Network Connection
WiFi
Peripherals
I am using the following peripherals that I consider relevant to this issue:
none
Log Files
none were created on the root partition
The text was updated successfully, but these errors were encountered: