-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] pwnagotchi stops working after short time #250
Comments
I had this problem before with a different project of mine, but not with pwnagotchi (I don't have a screen yet). |
EDIT: nope, it doesn't, crashed again :D
OLD:
|
I found this: raspberrypi/linux#2794 |
Looks like I fixed it with different power cable and more amps. Or maybe the SD-Card is shit. So if anyone has the same problem, change either the sd card or the cable/adapter or both |
This is getting mysterious. On my laptop booted in manual mode, service stopped and started with |
I have had similar problems: in my case the contents of the card were corrupted and upon restart (unplug + plug) the system was not loaded. @evilsocket and others have suggested that the cause could be an old / bad microsd, in fact it seems to be a common problem with the microsd cards used as secondary memory, due to frequent writing, as mentioned here: https://www.raspberrypi.org/forums/viewtopic.php?t=36533 I hope I've helped |
I can load the system, the MANUAL mode works fine and longer than 10 min. The problem is the AUTO mode. |
I already switched sd cards, same behavior for both. |
I solved it using Steps to solve:
Some models of the RPi0W have a H· on one of the coils, maybe these have problems. |
This should probably go in the docs somewhere? |
If you had the same problem & solved it for you, probably yes. |
Describe the bug
After starting the pwnagotchi (RPI0W with waveshare v2) via PWR USB and waiting for around 5-10 min, the pwnagotchi stops working, no screen refreshes anymore, no ethernet ssh access. Same happens if started manually via ssh.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The unit should stay on and refreshes the screen periodically, especially if it encounters new wifis.
Screenshots
None
Environment (please complete the following information):
EDIT2:
running in manual mode does NOT introduce this problem.
EDIT:
last dmesg before it gone
last output from python
EDIT3: from the log output with debug enabled
The text was updated successfully, but these errors were encountered: