Image won’t boot on Raspberry Pi Zero 2 W

AlexWhitehouse commented 3 years ago

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)

Flash image to SD
Load SD into RPiZ2W
Try to boot

Your Environment

[x] You're using the official images (1.5.5)
[x] You're using a raspberry pi zero 2 w
[x] You're using a supported LCD (waveshare v2)

V0r-T3x commented 2 years ago

I installed the @DrSchottky img. It work but I'm not able to link my pisugar2 into i2c. Is some one have an idea how to make it work? All seem set up, but the /dev/i2c-1 don't appear. I have a waveshare LCD 240x240 connected in SPI working with the fbcp-ili9341 buffer and the screen working well. I take some notes on what I did after installing the image.

my /etc/modules:

i2c-bcm2835
i2c-dev

my /boot/config.txt

[all]
dtoverlay=dwc2
dtoverlay=spi1-3cs
dtparam=spi=on

#dtparam=i2c=on
dtparam=i2c_arm=on
dtparam=i2c1=on
#dtparam=i2c_vc=on
#device_tree_param=i2c_arm=on

gpu_mem=32
dtoverlay=dpi24
display_rotate=0
enable_dpi_lcd=1
display_default_lcd=1
dpi_group=2
dpi_mode=87
dpi_output_format=0x6016
hdmi_timings=240 1 38 10 20 240 1 38 10 20 0 0 0 60 0 6400000 1
framebuffer_width=240
framebuffer_height=240

hdmi_group=2
hdmi_mode=87
hdmi_cvt=240 240 60 1 0 0 0
hdmi_force_hotplug=1

makerph commented 2 years ago

check the contacts. then run sudo i2cdetect -y 1

V0r-T3x commented 2 years ago

Thanks @makerph, the connections are good, if I use another raspbios or kali the pisugar2 work without problem.

If I use i2cdetect -y 1 or ls /dev | grep i2c I got nothing cause the file /dev/i2c-1 is not created. If I use dtparam=i2c_vc=on I got the i2c-0, i2c-10 and i2c-11.

I'm asking here because I don't know if I'm missing something or If it's a problem from the image itself.

V0r-T3x commented 2 years ago

I found my problem. I just removed dtoverlay=dpi24.

AABatteries commented 2 years ago

I reuploaded my image with latest nexmon patches for 2w https://anonfiles.com/9fE0e0M1xe/pwnagotchi-raspberry-pi-os-lite-master-05032022_zip

Rule of thumb to check if is nexmon the cause of the malfunctions is to run tcpdump (or airodump) on mon0. If you're getting data likely it's not.

The link is not working for me, any chance for a reupload, or a different host? Tried the mentioned torrent as well but it is corrupted unfortunately.

V0r-T3x commented 2 years ago

@AABatteries https://ufile.io/ab3gcxly

DrSchottky commented 2 years ago

I made a new beta (for which I sent a PR) https://github.com/DrSchottky/pwnagotchi/releases/tag/v1.5.6-beta2 The main difference with the previous image I posted here before is that it uses Kalipi for nexmon driver/fw.

Feel free to test it and report bugs (I'm mostly interested in 2W stability) Thanks

therealziggy commented 2 years ago

I made a new beta (for which I sent a PR) https://github.com/DrSchottky/pwnagotchi/releases/tag/v1.5.6-beta2 The main difference with the previous image I posted here before is that it uses Kalipi for nexmon driver/fw.

Feel free to test it and report bugs (I'm mostly interested in 2W stability) Thanks

hey @DrSchottky , thanks for keeping this up I just got it running an hour ago on my pi 2w, im not sure if i did something wrong but the pwnagotchi isnt able to discover any wifi network... it keeps searching and comes up with 0 APS (even tho im sure there are at least 12 around that i used to be able to capture using the previous firmware)

DrSchottky commented 2 years ago

I made a new beta (for which I sent a PR) https://github.com/DrSchottky/pwnagotchi/releases/tag/v1.5.6-beta2 The main difference with the previous image I posted here before is that it uses Kalipi for nexmon driver/fw. Feel free to test it and report bugs (I'm mostly interested in 2W stability) Thanks

hey @DrSchottky , thanks for keeping this up I just got it running an hour ago on my pi 2w, im not sure if i did something wrong but the pwnagotchi isnt able to discover any wifi network... it keeps searching and comes up with 0 APS (even tho im sure there are at least 12 around that i used to be able to capture using the previous firmware)

Thanks!

Could you check dmesg to see if chip crashed?
Did it work with the image I posted here (https://ufile.io/ab3gcxly) ?

therealziggy commented 2 years ago

I made a new beta (for which I sent a PR) https://github.com/DrSchottky/pwnagotchi/releases/tag/v1.5.6-beta2 The main difference with the previous image I posted here before is that it uses Kalipi for nexmon driver/fw. Feel free to test it and report bugs (I'm mostly interested in 2W stability) Thanks

hey @DrSchottky , thanks for keeping this up I just got it running an hour ago on my pi 2w, im not sure if i did something wrong but the pwnagotchi isnt able to discover any wifi network... it keeps searching and comes up with 0 APS (even tho im sure there are at least 12 around that i used to be able to capture using the previous firmware)

Thanks!

Could you check dmesg to see if chip crashed?

Did it work with the image I posted here (https://ufile.io/ab3gcxly) ?

I just tried the image in your reply and it works fine
Im not on a Linux machine atm so I can't check dmesg

Dreadmond commented 2 years ago

I made a new beta (for which I sent a PR) https://github.com/DrSchottky/pwnagotchi/releases/tag/v1.5.6-beta2 The main difference with the previous image I posted here before is that it uses Kalipi for nexmon driver/fw.

Feel free to test it and report bugs (I'm mostly interested in 2W stability) Thanks

hey @DrSchottky , thanks for keeping this up I just got it running an hour ago on my pi 2w, im not sure if i did something wrong but the pwnagotchi isnt able to discover any wifi network... it keeps searching and comes up with 0 APS (even tho im sure there are at least 12 around that i used to be able to capture using the previous firmware)

Thanks!

Could you check dmesg to see if chip crashed?

Did it work with the image I posted here (https://ufile.io/ab3gcxly) ?

I have the same issue with 0AP found.

Here's my dmesg:

 5.103240] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1)

[ 5.104700] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1) [ 5.104873] : Unregister from media controller [ 5.104884] (efault): Unregistering node (null)[0] device node /dev/video0 [ 5.104896] (efault): Unregistering node (null)[0] device node /dev/video0 [ 5.104905] (efault): Unregistering node (null)[0] device node /dev/video0 [ 5.104915] (efault): Unregistering node (null)[0] device node /dev/video0 [ 5.131863] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned. [ 5.148483] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1) [ 5.267329] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 5.295591] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 5.393124] brcmfmac: F1 signature read @0x18000000=0x1541a9a6 [ 5.410659] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43436s-sdio for chip BCM43430/1 [ 5.411597] usbcore: registered new interface driver brcmfmac [ 5.420490] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43436s-sdio.raspberrypi,model-zero-2-w.bin failed with error -2 [ 5.613104] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43436s-sdio for chip BCM43430/1 [ 5.613326] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43436s-sdio for chip BCM43430/1 [ 5.613395] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 5.614029] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Feb 5 2021 12:49:07 version 7.45.96 (r745790) FWID 01-71817851 es7 [ 8.062906] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled [ 8.163073] uart-pl011 3f201000.serial: no DMA platform data [ 8.267916] brcmfmac: brcmf_vif_add_validate: Attempt to add a MONITOR interface... [ 8.267954] brcmfmac: brcmf_mon_add_vif: brcmf_mon_add_vif called [ 8.267967] brcmfmac: brcmf_mon_add_vif: Adding vif "mon0"

DrSchottky commented 2 years ago

If you're having wireless problems with 2W with the new image try to add to start_monitor_interface() in /usr/bin/pwnlib these two lines:

  iw dev mon0 set power_save off
  iw dev wlan0 set power_save off

so that it becomes

# starts mon0
start_monitor_interface() {
  rfkill unblock all
  ifconfig wlan0 up && iw phy "$(iw phy | head -1 | cut -d" " -f2)" interface add mon0 type monitor && ifconfig mon0 up
  iw dev mon0 set power_save off
  iw dev wlan0 set power_save off
}

and let me know if it gets better

DamianPilot382 commented 2 years ago

Just as a reference, I followed what @Aiaid said in this thread and it got monitor mode working for me on a pi zero 2 W. Hopefully everyone can find it useful!

FallingLights commented 2 years ago

If you're having wireless problems with 2W with the new image try to add to start_monitor_interface() in /usr/bin/pwnlib these two lines:
  iw dev mon0 set power_save off
  iw dev wlan0 set power_save off
so that it becomes
# starts mon0
start_monitor_interface() {
  rfkill unblock all
  ifconfig wlan0 up && iw phy "$(iw phy | head -1 | cut -d" " -f2)" interface add mon0 type monitor && ifconfig mon0 up
  iw dev mon0 set power_save off
  iw dev wlan0 set power_save off
}
and let me know if it gets better

I'm running on the v1.5.6-beta2 build with the power_save off and there are still 0 APS

vojthor commented 2 years ago

Same issue here, running v1.5.6-beta2 on Zero 2W, no APs, not seeing anything in manual mode from bettercap interface either...

DrSchottky commented 2 years ago

@FallingLights @vojthor Could/did you try the old image (https://ufile.io/ab3gcxly)? Is it working? If so, would you be able to build nexmon on your pi?

vojthor commented 2 years ago

@DrSchottky I can see APs with this build in bettercap. Can you give me more docs about "building nexmon"? Happy to help but I'm kinda noob to this topic...

makerph commented 2 years ago

I've been testing v1.5.6-beta2 on zero 2w for more than 2 weeks now. I observe that I can see lots of AP's and I can confirm that pwnagotchi have lot of deauths but it only got few handshakes even I'm in stationary position in places infested with access points (condominiums, malls etc...)

LilianHori commented 2 years ago

@FallingLights @vojthor Could/did you try the old image (https://ufile.io/ab3gcxly)? Is it working? If so, would you be able to build nexmon on your pi?

Hey, thanks a lot, this one worked for me, all the other one did not on Pi Zero 2W (AI was ON but finding no APS) Also my Pi Zero 2W seems to be far more efficient at pwning that my Pi Zero W (it got way more handshake in the same amount of time while they were both right next to each other)

I'll be looking into what Nexmon is and see if I can help if needed

ywaf commented 2 years ago

doesn't seem to be working for me either, old image boots but fails to put interface into monitor, beta2 seems to put into monitor but no aps found :(

please let me know if I can be of use

BirbEXE commented 2 years ago

can't tell if it works or not on my zero 2 w, i've ended up with a waveshare 2.13" e-paper V3 display lmao

makerph commented 2 years ago

the image release before the 1.5.6 beta works for me. Just don't update the system via apt upgrade I suspect this breaks something..

wpa-2 commented 2 years ago

Have you got a link to that>?

ghost commented 2 years ago

Has this been resolved? Is there v3 support for e-paper display?

BirbEXE commented 2 years ago

Has this been resolved? Is there v3 support for e-paper display?

AFAIK there isn't currently :(

ywaf commented 2 years ago

Has this been resolved? Is there v3 support for e-paper display?

AFAIK there isn't currently :(

Yes there is loads of forks that support v3

https://github.com/DrSchottky/pwnagotchi

Or merge the v3 commit from that repo onto your pre existing sd image

BirbEXE commented 2 years ago

Has this been resolved? Is there v3 support for e-paper display?

AFAIK there isn't currently :(

Yes there is loads of forks that support v3

https://github.com/DrSchottky/pwnagotchi

Or merge the v3 commit from that repo onto your pre existing sd image

Thanks for telling me, I didn't know DrSchottky's image supported the v3 display

TNT599 commented 1 year ago

What is the current status on this, seems to still not work?

ywaf commented 1 year ago

What is the current status on this, seems to still not work?

Use drschottkys 1.5.6 image or the 1.5.5 modified he posted on anonfiles earlier in the thread. (1.5.5 you will have to manually merge commits for V3 display if you r using one)

TNT599 commented 1 year ago

Okay, thank you.

BirbEXE commented 1 year ago

sorry if this is an odd question but does @DrSchottky's image for the pi zero 2 w include ssh support or should I add that to config.txt + cmdline.txt my pwnagotchi detects that it's been plugged in and goes into manual mode, but it doesn't show on my computer not sure if this is an issue on the my computer side of things or not. I've tried sshing into my pi but it seems to not show up on my (windows) computer as a network connection.

any help/suggestions appreciated.

vablings commented 1 year ago

sorry if this is an odd question but does @DrSchottky's image for the pi zero 2 w include ssh support or should I add that to config.txt + cmdline.txt my pwnagotchi detects that it's been plugged in and goes into manual mode, but it doesn't show on my computer not sure if this is an issue on the my computer side of things or not. I've tried sshing into my pi but it seems to not show up on my (windows) computer as a network connection.

any help/suggestions appreciated.

You will need to install the RNDIS gadget driver. https://www.youtube.com/watch?v=bDZ7P7VzQWE Here is a short video showing how to do it. Once you have installed the driver you will need to configure the pwnagotchi as outlined in the setup guide. Once thats done you should be able to SSH into the unit in cmd using ssh pi@10.0.0.2

vablings commented 1 year ago

On an unrelated note with regards to DrSchottys image is there a way to configure the display further. Im using an inkyphat color display and i don't believe it supports partial refresh so freaks out when in AUTO mode (i tried ui.fps=0.0 to no avail)

BirbEXE commented 1 year ago

You will need to install the RNDIS gadget driver. https://www.youtube.com/watch?v=bDZ7P7VzQWE Here is a short video showing how to do it. Once you have installed the driver you will need to configure the pwnagotchi as outlined in the setup guide. Once thats done you should be able to SSH into the unit in cmd using ssh pi@10.0.0.2

Oh my god, I completely forgot that I had to install this. Pretty sure I've reinstalled windows since the first time I tried this with the original pi zero. I would never have tried that, thanks so much!

BirbEXE commented 1 year ago

I'm using DrSchotty's image and I'm not getting any access points detected at all

makerph commented 1 year ago

try the older DrSchotty's mage before the 1.5.6 beta but don't do apt update/upgrade it will break something that causes issue capturing handshake.

LilianHori commented 1 year ago

I'm using DrSchotty's image and I'm not getting any access points detected at all

Have you tried this one https://github.com/evilsocket/pwnagotchi/issues/1046#issuecomment-1211328517 it worked well for me on PI02

otzy007 commented 1 year ago

with both the 1.5.6 from DrSchotty https://github.com/DrSchottky/pwnagotchi/releases/tag/v1.5.6 and the one from this comment https://github.com/evilsocket/pwnagotchi/issues/1046#issuecomment-1211328517 I'm getting this kernel panic on my Pi Zero 2 W

rakosi2 commented 1 year ago

@otzy007 What program are you using to flash the image?

otzy007 commented 1 year ago

I'm flashing it with dd on macos sudo dd if=pwnagotchi-raspberrypi-os-lite-v1.5.6.img of=/dev/disk4

The 1.5.6 beta it starts but it's unable to use the wifi

rakosi2 commented 1 year ago

I have gotten the same error with dd. Using the official Raspberry pi flasher does seem to properly flash it for me.

otzy007 commented 1 year ago

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

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.15.44-Re4son-v7+ (root@kali-rpi) (gcc (Debian 11.2.0-19) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP Debian kali-pi (2022-07-03)
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi Zero 2 W Rev 1.0
[    0.000000] random: crng init done
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] Reserved memory: created CMA memory pool at 0x1ac00000, size 64 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000000000-0x000000001effffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x000000001effffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000001effffff]
[    0.000000] percpu: Embedded 16 pages/cpu s35788 r8192 d21556 u65536
[    0.000000] pcpu-alloc: s35788 r8192 d21556 u65536 alloc=16*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 125860
[    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:F8:0A:6F vc_mem.mem_base=0x1fa00000 vc_mem.mem_size=0x20000000  console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 fsck.repair=yes rootwait modules-load=dwc2,g_ether
[    0.000000] Unknown kernel command line parameters "modules-load=dwc2,g_ether", will be passed to user space.
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 420712K/507904K available (10240K kernel code, 1342K rwdata, 3040K rodata, 1024K init, 578K bss, 21656K reserved, 65536K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 32256 entries in 95 pages
[    0.000000] ftrace: allocated 95 pages with 6 groups
[    0.000000] trace event string verifier disabled
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000]  Rude variant of Tasks RCU enabled.
[    0.000000]  Tracing variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000001] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000024] Switching to timer-based delay loop, resolution 52ns
[    0.000454] Console: colour dummy device 80x30
[    0.001277] printk: console [tty1] enabled
[    0.001349] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.001409] pid_max: default: 32768 minimum: 301
[    0.001577] LSM: Security Framework initializing
[    0.001813] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.001863] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.003385] cgroup: Disabling memory control group subsystem
[    0.003677] CPU: Testing write buffer coherency: ok
[    0.004219] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.005569] Setting up static identity map for 0x100000 - 0x10003c
[    0.005776] rcu: Hierarchical SRCU implementation.
[    0.006792] smp: Bringing up secondary CPUs ...
[    0.007942] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.009206] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.010471] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.010621] smp: Brought up 1 node, 4 CPUs
[    0.010722] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.010757] CPU: All CPU(s) started in HYP mode.
[    0.010785] CPU: Virtualization extensions available.
[    0.011586] devtmpfs: initialized
[    0.028902] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.029178] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.029256] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.032490] pinctrl core: initialized pinctrl subsystem
[    0.033881] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.037972] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.043851] audit: initializing netlink subsys (disabled)
[    0.044160] audit: type=2000 audit(0.040:1): state=initialized audit_enabled=0 res=1
[    0.044780] thermal_sys: Registered thermal governor 'step_wise'
[    0.045337] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.045403] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.045684] Serial: AMBA PL011 UART driver
[    0.054154] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.080067] raspberrypi-firmware soc:firmware: Attached to firmware from 2022-05-24T13:26:13, variant start_cd
[    0.090083] raspberrypi-firmware soc:firmware: Firmware hash is 2c647ef4127e289d4a0cb5cfbb22855bfb7f1723
[    0.139236] Kprobes globally optimized
[    0.146915] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
[    0.149215] SCSI subsystem initialized
[    0.149512] usbcore: registered new interface driver usbfs
[    0.149600] usbcore: registered new interface driver hub
[    0.149692] usbcore: registered new device driver usb
[    0.150033] usb_phy_generic phy: supply vcc not found, using dummy regulator
[    0.150705] usb_phy_generic phy: dummy supplies not allowed for exclusive requests
[    0.151046] pps_core: LinuxPPS API ver. 1 registered
[    0.151079] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.151138] PTP clock support registered
[    0.152757] clocksource: Switched to clocksource arch_sys_counter
[    0.223478] VFS: Disk quotas dquot_6.6.0
[    0.223636] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.223862] FS-Cache: Loaded
[    0.224147] CacheFiles: Loaded
[    0.234861] NET: Registered PF_INET protocol family
[    0.235105] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.236409] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[    0.236497] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
[    0.236597] TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.236725] TCP: Hash tables configured (established 4096 bind 4096)
[    0.236889] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.236952] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.237235] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    0.243738] RPC: Registered named UNIX socket transport module.
[    0.243778] RPC: Registered udp transport module.
[    0.243807] RPC: Registered tcp transport module.
[    0.243835] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.794769] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    1.800290] Initialise system trusted keyrings
[    1.800617] workingset: timestamp_bits=14 max_order=17 bucket_order=3
[    1.810746] zbud: loaded
[    1.812838] FS-Cache: Netfs 'nfs' registered for caching
[    1.813851] NFS: Registering the id_resolver key type
[    1.813917] Key type id_resolver registered
[    1.813946] Key type id_legacy registered
[    1.814112] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.814148] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    1.955931] Key type asymmetric registered
[    1.955970] Asymmetric key parser 'x509' registered
[    1.956093] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[    1.956136] io scheduler mq-deadline registered
[    1.956166] io scheduler kyber registered
[    1.959940] bcm2708_fb soc:fb: FB found 1 display(s)
[    1.995522] Console: switching to colour frame buffer device 228x61
[    2.011004] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 1824x984
[    2.018272] bcm2835-rng 3f104000.rng: hwrng registered
[    2.018843] vc-mem: phys_addr:0x00000000 mem_base=0x1fa00000 mem_size:0x20000000(512 MiB)
[    2.020235] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    2.032920] brd: module loaded
[    2.043125] loop: module loaded
[    2.043913] Loading iSCSI transport class v2.0-870.
[    2.045969] usbcore: registered new interface driver lan78xx
[    2.046140] usbcore: registered new interface driver smsc95xx
[    2.046261] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    2.046611] dwc_otg: FIQ enabled
[    2.046624] dwc_otg: NAK holdoff enabled
[    2.046636] dwc_otg: FIQ split-transaction FSM enabled
[    2.046652] Module dwc_common_port init
[    2.046884] usbcore: registered new interface driver usb-storage
[    2.047210] mousedev: PS/2 mouse device common for all mice
[    2.050294] sdhci: Secure Digital Host Controller Interface driver
[    2.050418] sdhci: Copyright(c) Pierre Ossman
[    2.050924] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.052709] ledtrig-cpu: registered to indicate activity on CPUs
[    2.053208] hid: raw HID events driver (C) Jiri Kosina
[    2.053402] usbcore: registered new interface driver usbhid
[    2.053469] usbhid: USB HID core driver
[    2.057150] Initializing XFRM netlink socket
[    2.057251] NET: Registered PF_PACKET protocol family
[    2.057415] Key type dns_resolver registered
[    2.057599] Registering SWP/SWPB emulation handler
[    2.058131] registered taskstats version 1
[    2.058201] Loading compiled-in X.509 certificates
[    2.058796] Key type ._fscrypt registered
[    2.061345] Key type .fscrypt registered
[    2.063861] Key type fscrypt-provisioning registered
[    2.067391] Key type encrypted registered
[    2.079026] uart-pl011 3f201000.serial: cts_event_workaround enabled
[    2.081940] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 114, base_baud = 0) is a PL011 rev2
[    2.086628] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[    2.089714] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
[    2.094959] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
[    2.097545] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
[    2.128054] sdhost: log_buf @ 77ec576c (dad10000)
[    2.181936] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    2.195144] of_cfs_init
[    2.198924] of_cfs_init: OK
[    2.203703] Waiting for root device /dev/mmcblk0p2...
[    2.243330] mmc0: host does not support reading read-only switch, assuming write-enable
[    2.250080] mmc0: new high speed SDHC card at address 1234
[    2.254607] mmcblk0: mmc0:1234 SA32G 28.9 GiB 
[    2.262162]  mmcblk0: p1 p2
[    2.266517] mmcblk0: mmc0:1234 SA32G 28.9 GiB
[    2.306640] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[    2.310752] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[    2.323959] mmc1: new high speed SDIO card at address 0001
[   10.076778] EXT4-fs (mmcblk0p2): recovery complete
[   10.178750] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[   10.182052] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[   10.194688] devtmpfs: mounted
[   10.205032] Freeing unused kernel image (initmem) memory: 1024K
[   10.209219] Run /sbin/init as init process
[   10.212342]   with arguments:
[   10.212350]     /sbin/init
[   10.212358]   with environment:
[   10.212365]     HOME=/
[   10.212372]     TERM=linux
[   10.212379]     modules-load=dwc2,g_ether
[   10.805391] systemd[1]: System time before build time, advancing clock.
[   10.984358] NET: Registered PF_INET6 protocol family
[   10.988173] Segment Routing with IPv6
[   10.990794] In-situ OAM (IOAM) with IPv6
[   11.073107] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[   11.081154] systemd[1]: Detected architecture arm.
[   11.170487] systemd[1]: Set hostname to <pwnagotchi>.
[   11.770673] systemd[1]: Configuration file /etc/systemd/system/pwngrid-peer.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
[   11.776595] systemd[1]: Configuration file /etc/systemd/system/pwnagotchi.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
[   11.808252] systemd[1]: Configuration file /etc/systemd/system/bettercap.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
[   11.838485] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[   11.847481] systemd[1]: Listening on Journal Audit Socket.
[   11.854985] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[   11.862262] systemd[1]: Reached target Paths.
[   12.588699] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null). Quota mode: none.
[   12.594549] dwc2 3f980000.usb: supply vusb_d not found, using dummy regulator
[   12.598170] dwc2 3f980000.usb: supply vusb_a not found, using dummy regulator
[   12.699751] systemd-journald[148]: Received request to flush runtime journal from PID 1
[   12.822921] dwc2 3f980000.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM
[   12.826734] dwc2 3f980000.usb: DWC OTG Controller
[   12.830271] dwc2 3f980000.usb: new USB bus registered, assigned bus number 1
[   12.834359] dwc2 3f980000.usb: irq 66, io mem 0x3f980000
[   12.838199] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[   12.841763] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   12.845378] usb usb1: Product: DWC OTG Controller
[   12.848616] usb usb1: Manufacturer: Linux 5.15.44-Re4son-v7+ dwc2_hsotg
[   12.851142] usb usb1: SerialNumber: 3f980000.usb
[   12.854510] hub 1-0:1.0: USB hub found
[   12.857141] hub 1-0:1.0: 1 port detected
[   12.907791] using random self ethernet address
[   12.910894] using random host ethernet address
[   12.918254] usb0: HOST MAC 56:82:cb:63:ee:63
[   12.921497] usb0: MAC 26:ce:27:f0:62:66
[   12.924376] using random self ethernet address
[   12.927116] using random host ethernet address
[   12.929884] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
[   12.932625] g_ether gadget: g_ether ready
[   12.935187] dwc2 3f980000.usb: bound driver g_ether
[   12.956374] i2c_dev: i2c /dev entries driver
[   13.148556] dwc2 3f980000.usb: new device is high-speed
[   13.171925] dwc2 3f980000.usb: new address 3
[   13.220697] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[   13.222240] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[   13.222259] [vc_sm_connected_init]: start
[   13.222598] vc_sm_cma_vchi_init: failed to open VCHI service (-1)
[   13.222610] [vc_sm_connected_init]: failed to initialize shared memory service
[   13.242530] mc: Linux media interface: v0.10
[   13.299192] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[   13.300765] bcm2835_audio bcm2835_audio: there is not valid maps for state default
[   13.301542] videodev: Linux video capture interface: v2.00
[   13.303679] bcm2835_audio bcm2835_audio: card created with 8 channels
[   13.386631] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[   13.386631] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[   13.387214] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[   13.400343] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[   13.401924] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
[   13.407594] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1)
[   13.407618] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1)
[   13.407739] : Unregister from media controller
[   13.407757] (efault): Unregistering node (null)[0] device node /dev/video0
[   13.407773] (efault): Unregistering node (null)[0] device node /dev/video0
[   13.407793] (efault): Unregistering node (null)[0] device node /dev/video0
[   13.407805] (efault): Unregistering node (null)[0] device node /dev/video0
[   13.423684] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[   13.433002] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=-1)
[   13.602187] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   13.654818] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   13.757383] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[   13.763432] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43436s-sdio for chip BCM43430/1
[   13.764355] usbcore: registered new interface driver brcmfmac
[   13.792183] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43436s-sdio.raspberrypi,model-zero-2-w.bin failed with error -2
[   13.998087] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43436s-sdio for chip BCM43430/1
[   13.998260] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43436s-sdio for chip BCM43430/1
[   13.998355] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[   13.998967] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Feb  5 2021 12:49:07 version 7.45.96 (r745790) FWID 01-71817851 es7
[   15.642508] uart-pl011 3f201000.serial: no DMA platform data
[   15.753907] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[   15.978848] brcmfmac: brcmf_vif_add_validate: Attempt to add a MONITOR interface...
[   15.978883] brcmfmac: brcmf_mon_add_vif: brcmf_mon_add_vif called
[   15.978893] brcmfmac: brcmf_mon_add_vif: Adding vif "mon0"
[   16.003106] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled
[   16.085191] fuse: init (API version 7.34)
[   16.756491] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k SSFS
[   21.952901] Bluetooth: Core ver 2.22
[   21.953026] NET: Registered PF_BLUETOOTH protocol family
[   21.953035] Bluetooth: HCI device and connection manager initialized
[   21.953062] Bluetooth: HCI socket layer initialized
[   21.953077] Bluetooth: L2CAP socket layer initialized
[   21.953106] Bluetooth: SCO socket layer initialized
[   21.994962] Bluetooth: HCI UART driver ver 2.3
[   21.994992] Bluetooth: HCI UART protocol H4 registered
[   21.995121] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   21.996282] Bluetooth: HCI UART protocol Broadcom registered
[   22.432232] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   22.432266] Bluetooth: BNEP filters: protocol multicast
[   22.432294] Bluetooth: BNEP socket layer initialized
[   32.472806] cam-dummy-reg: disabling

bking46 commented 1 year ago

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

LilianHori commented 1 year ago

Had the same problem but the image from there https://github.com/evilsocket/pwnagotchi/issues/1046#issuecomment-1211328517 worked well for my Pi02

Crash891 commented 1 year ago

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. Anyway guys i tried the 1.5.6 beta2 and 1.5.6: the 1.5.6 don't get the API and don't start. The 1.5.6 beta2 start, with the Logtail i can see that see the networks, it deaught and do things but it don't actually take the networks. I hope there will be a true new version of pwnagotchi, cause the rpi zero v1 can't be found in the shops, is obsolete and no one have it anymore. (of course the waveshare v3 is needed too, but that is an easyer fix)

bking46 commented 1 year ago

@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). @Crash891: The link is this one that LilianHori was referring https://ufile.io/ab3gcxly 20221123_164411

Crash891 commented 1 year ago

@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). @Crash891: The link is this one that LilianHori was referring https://ufile.io/ab3gcxly

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

Crash891 commented 1 year ago

@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). @Crash891: The link is this one that LilianHori was referring https://ufile.io/ab3gcxly

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

bking46 commented 1 year ago

@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

LilianHori commented 1 year ago

@Crash891 when something goes wrong I sometime don't have access to webUI but can still ssh in and view logs that way

evilsocket / pwnagotchi