[BUG] Since upgrading to 2.8.0. now it's not handling the wlan0mon disappearing

[rsun0525]

Describe the bug
When it was running 2.7.9, it seemed to handle the condition of wlan0mon disappearing properly by restarting whatever, etc. but since going to 2.8.0, it seems to get stuck and I have to manually do it again to fix it.

Hopefully you'll be able to see something in the pwnagotchi.log file
pwnagotchi.log

[jayofelony]

Nothing changed in that regard, so can't help.

[jayofelony]

@rsun0525 I am reopening this issue. When it is booted can you run sudo dmesg | grep brcmffor me please. ANd show me printscreen of the output.

[rsun0525]

pi@pwnagotchi400:~ $ sudo dmesg | grep brcmf
pi@pwnagotchi400:~ $ sudo dmesg | grep brcm
[ 1.214060] irq_brcmstb_l2: registered L2 intc (/soc/interrupt-controller@7ef00100, parent irq: 27)
[ 1.224347] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:
[ 1.224410] brcm-pcie fd500000.pcie: No bus range found for /scb/pcie@7d500000, using [bus 00-ff]
[ 1.224501] brcm-pcie fd500000.pcie: MEM 0x0600000000..0x063fffffff -> 0x00c0000000
[ 1.224592] brcm-pcie fd500000.pcie: IB MEM 0x0000000000..0x00ffffffff -> 0x0400000000
[ 1.225148] brcm-pcie fd500000.pcie: setting SCB_ACCESS_EN, READ_UR_MODE, MAX_BURST_SIZE
[ 1.225599] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00
[ 1.340239] brcm-pcie fd500000.pcie: link up, 5.0 GT/s PCIe x1 (SSC)
[ 1.343517] brcm-pcie fd500000.pcie: clkreq control enabled
[ 2.469105] brcmstb-i2c fef04500.i2c: @97500hz registered in polling mode
[ 2.469983] brcmstb-i2c fef09500.i2c: @97500hz registered in polling mode
[ 9.470339] Bluetooth: hci0: BCM4345C5 'brcm/BCM4345C5.raspberrypi,400.hcd' Patch
pi@pwnagotchi400:~ $

[jayofelony]

Not sure if it helps, but mine has the same issue sometimes.

You have the best wifi chip there is, the set channel failed can be ignored. You could even disable fix_services, it is set to restart at that error but it'll still work if you ignore it apparently.

[jayofelony]

pi@pwnagotchi400:~ $ sudo dmesg | grep brcmf pi@pwnagotchi400:~ $ sudo dmesg | grep brcm [ 1.214060] irq_brcmstb_l2: registered L2 intc (/soc/interrupt-controller@7ef00100, parent irq: 27) [ 1.224347] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges: [ 1.224410] brcm-pcie fd500000.pcie: No bus range found for /scb/pcie@7d500000, using [bus 00-ff] [ 1.224501] brcm-pcie fd500000.pcie: MEM 0x0600000000..0x063fffffff -> 0x00c0000000 [ 1.224592] brcm-pcie fd500000.pcie: IB MEM 0x0000000000..0x00ffffffff -> 0x0400000000 [ 1.225148] brcm-pcie fd500000.pcie: setting SCB_ACCESS_EN, READ_UR_MODE, MAX_BURST_SIZE [ 1.225599] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00 [ 1.340239] brcm-pcie fd500000.pcie: link up, 5.0 GT/s PCIe x1 (SSC) [ 1.343517] brcm-pcie fd500000.pcie: clkreq control enabled [ 2.469105] brcmstb-i2c fef04500.i2c: @97500hz registered in polling mode [ 2.469983] brcmstb-i2c fef09500.i2c: @97500hz registered in polling mode [ 9.470339] Bluetooth: hci0: BCM4345C5 'brcm/BCM4345C5.raspberrypi,400.hcd' Patch pi@pwnagotchi400:~ $

And what do you do to fix it?

[rsun0525]

For me, I generally can fix it by doing a "sudo monstart", and then a pwnkill and I'm up and running. Once in a while it crashes so badly that I have to do a sudo reboot, I'm just confused why the automatic restart stuff doesn't catch these two issues for me when it happens.

[jayofelony]

Because there is simply no wireless interface to begin with at this point. So nothing to do. And you are using a pi 4 right?

[jayofelony]

I will try a fresh flash with 2.7.9 asap on my pi 4.

[rsun0525]

That's what's really puzzling, is that it got a lot more stable doing a fresh flash to 2.7.9 but after upgrading to 2.8.0, it became unstable, looking at your change log, don't see why this would of been a problem. I can do a fresh flash again if you like and then manually kick off the 2.8.0 (unless you prefer me to let it sit there and automatically upgrade).

[jayofelony]

I do know of an issue with the Pi 4 wifi firmware of nexmon, I am currently in talks with them about a fix hopefully. I will know more about that tomorrow.

[jayofelony]

fresh flash of 2.7.9 works out the box with a buddy of mine, just flashed it.