Image won’t boot on Raspberry Pi Zero 2 W #1046
Comments
|
Funny - i just swapped mine over with no issues at all: root@pwnagotchu:~# dmesg|more root@pwnagotchu:~# lscpu root@pwnagotchu:~# cat /usr/local/src/pwnagotchi/pwnagotchi/_version.py |
|
I don't even get past the multicoloured square to boot to the kernel image. Neither do I get any status lights on the pi itself. I have loaded other images to check there is no problem with the pi and these have booted successfully. |
|
FWIW - i'm running on a 64G SanDisk Ultra, Class 10 (A1) that had previously been running on a Pi0w-v1 You could try booting up on a V1, using the usb ethernet sharing and "internet sharing" then ssh into the pi and make sure there are no filesystem issues, and run an apt-get update / upgrade cycle to get everything up to date? (you may need to manually fix-up /etc/resolv.conf, and set your time/date.) But I didn't do any of that prior to booting it on the V2 ... just swapped the card over, and it worked fine. |
|
Very strange, I don't have a v1 to hand to test that unfortunately. Does the fact there are no status lights or anything output to HDMI suggest that the pi is not accepting the image on the SD card? It works fine with other builds just not the pwnagotchi image. |
|
you could try re-imaging the sdcard. Or try booting it on any other pi hardware you might have, possibly excepting for the wifi and cdcether, it should otherwise start up (tested on a Pi4, even cdcether works) |
|
I have re-imaged the sdcard, plugged into RPi Zero 2 and nothing. I then plug the same card into a Pi4 and I get activity lights and an IP address. I then plug the same card back into the zero 2 and get nothing again. I have also tried just raspbian light on the SD card in the zero 2 and this works fine. |
|
Seeing the same issue. The Zero 2 fails to boot with any of the following:
But it did boot with the latest raspbian For reference, here's what we see while it boots from the Pi Zero W (non Zero2) |
|
I am having the same problem on my zero 2. |
|
One difference i see in your bootlog is the kernel version: This would seem to indicate that you need to upgrade your kernel, or the image that you're using. Boot it on a working device, get internet connectivity (via wired, or 2nd wifi) and run a distro upgrade to see if there's an upgraded kernel for you. (apparently I may have done that, but I don't remember upgrading the system...) |
|
I think it defiantly could have been that, unfortunately i didn't check the version before updating but now after doing sudo apt update && sudo apt full-upgrade -y it started working and now it boots and i can ssh into it and see the web ui. |
|
One issue with this is that there's apparently a change with numpy ( #1045 ), and now the ai crashes on load. There's already a bug open on it, so you might want to go give it a thumbs-up |
|
I did see that in the logs but didn't think to much of it. That's not the only problem I'm having, whenever I try to put it into auto mode it keeps saying "[INFO] waiting for bettercap API to be available". However when I put it in my pi4 it works in auto fine. The passwords are still the default and I haven't changed them which is the common thing between all the reports of this problem on Google so I'm not sure if that's a me broke something thing Or a pi zero 2w thing.
…________________________________
From: Leif ***@***.***>
Sent: Saturday, November 6, 2021 9:37:51 AM
To: evilsocket/pwnagotchi ***@***.***>
Cc: Joshua Guthrie ***@***.***>; Manual ***@***.***>
Subject: Re: [evilsocket/pwnagotchi] Image won’t boot on Raspberry Pi Zero 2 W (Issue #1046)
One issue with this is that there's apparently a change with numpy, and now the ai crashes on load.
There's already a bug open on it, so you might want to go give it a thumbs-up
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#1046 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQQS7IWC3OQKZMCLTGRCG7LUKRTE7ANCNFSM5HGJZUXA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Retried the setups from before but did the full-upgrade and it worked in all instances. 👍 |
Glad to here it got it going, have you had any other problems running it on the pi zero 2 w I manually started the better cap api now im getting |
To clear up a little this sorted my install but I had to boot the image using a PI 3. The image wouldnt boot on a PI4. Once booted and upgraded everything looks to be working fine (so far) |
|
I've gotten the zero 2 to boot with the I notice this in the system log but doesn't seem to give many more clues. The same image works on the original 0w. The AI issue I worked around by |
|
@skontrolle you'll need to make sure you've got the most recent linux-firmware packages (libre and nonfree) installed. Worst-case, you can grab the firmware files from any ubuntu machine running 21.04 or 21.10 right out of /lib/firmware/brcm/ and install them into the same place on the rPi the "brcmfmac43436-sdio.raspberrypi,model-zero-2.txt" file warning can be ignored. it's a backup file for setting the firmware variables, but the less specific driver file will take care of it. |
|
Thanks, for the warning explanation. Is there something in bettercap I can set to log or try? |
|
I just retraced all of my steps with a clean
|
|
Okay, so @skontrolle - i think that without the kalipi kernel (and modules) you won't get the correct driver for the mon interface, so won't be able to sniff correctly. I was able to just install libavcodec58 libavformat58 without upgrading/installing the raspberrypi-bootloader/kernel by marking the two packages as "hold" - apt-mark hold kalipi-bootloader kalipi-kernel it's a horrible workaround, but seems to have gotten mine up and running fully now ( also setting /etc/default/crda to the correct domain) |
|
Thanks @akhepcat but still no joy on the wifi The kalipi-kernel has persisted through the updates. I reverted the av..58s reinstalled the I also set the For good measure, here's the wifi loading line from the kernel, is yours similar? I'm not sure it's supported upstream in nexmon yet... |
|
https://github.com/isthisausername2/pwnagotchi_rpi_zero_2_fix |
I'm sorry but... What exactly working great? Btw I didn't update libav*58 because I didn't understand what to do after with kalipi-bootloader. |
|
The steps written by @skontrolle got my Zero 2 w working*. I recommend flashing your sd card with a fresh install of pwnagotchi, following those steps or using the script on a pi that does boot, then putting that fresh sd card in your zero 2 w and seeing if that fixes it. That's how i got mine working. |
|
I cloned the repo from @isthisausername2 and made some changes to ward off some potential issues that I foresee. @andur82 - burn a new, fresh image of 1.5.5. you should also be able to use a pi3 or pi4 for the first booting and upgrades (again, you'll need to use usb-gadget or ethernet for network connectivity) That said: it still won't work on the pi zero v2, because the only firmware available for the brcmfmac43436 chip doesn't support the full promiscuous capture in monitor mode, unlike the brcmfmac43430 of the -v1. And as @skontrolle mentioned, until nexmon releases a working firmware, running this on the zero-v2 isn't going to get us anywhere. ( seemoo-lab/nexmon#500 ) |
|
@akhepcat many thanks for this explain. Strange things: on the rpi3, after done all update with libav*58 (and installing raspberry bootloader instead of the original kali) the pwnagotchi do only one round with the first found aps, then completely die. No more scan. |
|
@isthisausername2 interesting that you got it to work. What wifi firmware chipset /firmware do you get from In a sense, the original issue is solved in getting the 0w2 to boot, but the wifi issue is a different blocker for at least my boards. |
|
@akhepcat Thanks for that, i see some things added that i had no idea how to and also some other things that would help. @skontrolle I will try when i can. I remember seeing it catch a handshake but there are a few wifi networks around me so theres a chance it isn't actually working properly or they weren't in range. I took it on the bus with me today so i will see what or if its captured anything. |
|
@isthisausername2 my initial hint that things weren't working was that the access points |
|
I have gotten the same error with dd. Using the official Raspberry pi flasher does seem to properly flash it for me. |
|
This is the dmesg for the 1.5.6beta2 https://github.com/DrSchottky/pwnagotchi/releases/tag/v1.5.6-beta2 on Pi Zero 2 W |
|
Hi everyone, Just wanted to report back that with @DrSchottky images V1.5.6 and V1.5.6-beta 2 the rpi zero 2 W boots and seems to run as expected. The big issue I am facing with both images is the fact that the Pi doesn't find any networks whatsoever. After a few minutes it goes into AI mode but cannot find any networks. Have tried manu mode and then went into bettercap but it's still the same no networks. I would be greatful for any help or suggestions. I realize this issue is still open but from reading the thread I was under the impression that this is now working for some users with the pi zero 2 w. Thanks for your help |
|
Had the same problem but the image from there https://github.com/evilsocket/pwnagotchi/issues/1046#issuecomment-1211328517 worked well for my Pi02 |
The link seems to be broken... it don't open any issue... maybe is deleted. |
|
@LilianHori thanks so much for pointing out the link with that image. I am happy to report that my setup is no longer blind 😊. Will do a proper test this week to see how it goes with the rest of the functions (gps, bettercap, etc). |
thanks you very much, i'll try right now. i will need to change the files to make it work with v3 waveshare obv... maybe i'll try without screen for now |
ok, idk what he is doing... it seems to boot, but i can not open the web UI on 10.0.0.2:8080, so i can't see the logs |
|
@Crash891: For me the web ui works but I am connected via bluetooth. One suggestion would be to flash the image and add config.toml with the required parameters in the boot partition to enable the bluetooth connection with your phone. In this way you basically have access to everything ssh, sftp, webui. Hope this helps |
|
@Crash891 when something goes wrong I sometime don't have access to webUI but can still ssh in and view logs that way |
|
how am i supposed to get the v3 display to work with https://ufile.io/ab3gcxly ? |
|
I have 1.5.6b2 running on a pi 4 8 gb with kalipi. Bettercap works with wlan0 in monitor mode. Airodump-ng also works perfect, but for some reason pwnagotchi does not see networks and unable to capture. Anyone who can help me out? systemctl status pwnagotchi systemctl status bettercap systemctl status pwngrid contents of /var/log/pwnagtochi.log, last run |
|
Nevermind, I have it completely working now. Also AI is up and running with the 1.5.6b2 image on a Rpi4 8GB with kalipi aarch64. I had to set main_iface to wlan0mon. |
can you describe your full setup to get here? |
I Installed Kali Pi for arm64/aarch64. You can skip the gfortran9 part and python3.7. Python3.7, you have to build this from source. Download Tenforflow 1.15.0 from https://github.com/jayofelony/Tensorflow You must have aircrack-ng installed. Use my fork of DrSchottky's Pwnagotchi to build Pwnagotchi sudo python3.7 -m pip install -r requirements.txt Or full a full guide check out the readme |
|
Has anyone gotten their pi zero 2 W to successfully detect any networks? I've gotten mine to boot et cetera but bettercap sees nothing around it. |
Same here |
I've forked the project and tried everything I can think of for now including updating to the most recent old stable buster, updating to bettercap v2.32 (which required updating to golang v1.19.4) and going over the commits from DrSchottky v1.5.5 and v1.5.6 with a fine tooth comb. My fork boots fast and everything works except bettercap is blind and does not see any networks anywhere. If anyone is interesting in working on this with me, check out my fork. I'll release a new version tomorrow with bettercap v2.32. |
|
Great work getting everything updated. I did the same and it's no small task. Is this a driver issue, or a bettercap issue? Could you check the bettercap logs, to rule it out. If you read previous comments above, at some point a few folks ran into the blindness issue and @DrSchottky kindly re-uploaded his image with a working driver. I'm not sure what's different. Are you using that driver? If so, does your pi see any networks outside of bettercap? I've starred your fork, will take a look over the next few days. |
|
I just started messing with pwnagotchi a couple days ago. I have the files for being able to use a waveshare 2.7 V2, I didn't find it. I just got a pi 0 2, 2.13 waveshare V3 and am running through the threads. I am trying this image. Is there more info on the actual changes needed? Is it all in the kernel? I will keep checking the threads for more. |
I do see networks with my pi0 2W connected to the computer and access from the web, but I can't see anything on the screen v3 |
|
join the discord for current developments: https://discord.gg/xx4JPbXVJe |
You will need to add support for your screen its most liikely missing its files |
|
The problem is that I don't know how to do it. Now I've gotten the screen to work, but the right half of the screen doesn't give good resolution. I am totally new in this world. |
|
@totemer-web Remember that in manual mode it will look faded. In auto it should look better. Which screen are you using? |
|
waveshare v3. In none of the modes can I see it correctly. I have checked to see if it is a screen failure, and the screen is correct. |
|
https://github.com/jayofelony/pwnagotchi-torch I think this issue can be closed now @evilsocket I created a working image for Pi0W2 and other 64bit RPi's. |
Have the changes been merged back here, or do I need to use a fork? |
use the other fork! |
yeah, this one looks pretty much abandoned... |
and others
Expected Behaviour
Expected to boot on Pi Zero 2 W. Fails to boot.
Current Behaviour
Fails to boot
Possible Solution
Recompile kernel for RPiZ2W
Steps to Reproduce (for bugs)
Your Environment
You're using the official images (1.5.5)
You're using a raspberry pi zero 2 w
You're using a supported LCD (waveshare v2)
The text was updated successfully, but these errors were encountered: