Skip to content
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] Since upgrading to 2.8.0. now it's not handling the wlan0mon disappearing #39

Closed
rsun0525 opened this issue Jan 30, 2024 · 22 comments
Assignees
Labels
bug Something isn't working

Comments

@rsun0525
Copy link

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

@rsun0525 rsun0525 added the bug Something isn't working label Jan 30, 2024
@jayofelony
Copy link
Owner

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

@jayofelony jayofelony closed this as not planned Won't fix, can't repro, duplicate, stale Jan 31, 2024
@jayofelony jayofelony reopened this Feb 1, 2024
@jayofelony jayofelony self-assigned this Feb 1, 2024
@jayofelony
Copy link
Owner

@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
Copy link
Author

rsun0525 commented Feb 1, 2024

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
Copy link
Owner

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

image

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
Copy link
Owner

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
Copy link
Author

rsun0525 commented Feb 1, 2024

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
Copy link
Owner

jayofelony commented Feb 1, 2024

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
Copy link
Owner

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

@rsun0525
Copy link
Author

rsun0525 commented Feb 1, 2024

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
Copy link
Owner

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
Copy link
Owner

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

@Ravioli5
Copy link
Contributor

Ravioli5 commented Feb 2, 2024

I'm getting this.

pi@spark:~ $ sudo dmesg | grep brcmf
[ 7.814908] brcmfmac: loading out-of-tree module taints kernel.
[ 7.982876] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 8.038403] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 8.039409] usbcore: registered new interface driver brcmfmac
[ 8.525091] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 8.539485] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan 26
2024 15:07:50 version 7.45.206 (nexmon.org: 2.2.2-514-gf195c-1) FWID 01-88ee44ea[ 9.874484] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[ 10.402341] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[ 11.308401] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled
[ 11.331508] brcmfmac: brcmf_vif_add_validate: Attempt to add a MONITOR interface...
[ 11.331529] brcmfmac: brcmf_mon_add_vif: brcmf_mon_add_vif called
[ 11.331534] brcmfmac: brcmf_mon_add_vif: Adding vif "wlan0mon"
[ 463.970708] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled
[ 467.028351] brcmfmac: brcmf_vif_add_validate: Attempt to add a MONITOR interface...
[ 467.028385] brcmfmac: brcmf_vif_add_validate: ... there is already a monitor
interface, returning EOPNOTSUPP
[ 467.028402] ieee80211 phy0: brcmf_cfg80211_add_iface: iface validation failed: err=-95
[ 554.368570] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled
[ 557.397637] brcmfmac: brcmf_vif_add_validate: Attempt to add a MONITOR interface...
[ 557.397655] brcmfmac: brcmf_vif_add_validate: ... there is already a monitor
interface, returning EOPNOTSUPP
[ 557.397707] ieee80211 phy0: brcmf_cfg80211_add_iface: iface validation failed: err=-95

@Ravioli5
Copy link
Contributor

Ravioli5 commented Feb 2, 2024

That's what I get at first... I have not done apt get or apt upgrade or update since flashing either. Bootloader is up to date too. Fix_services isn't working either...

@jayofelony
Copy link
Owner

Like the error says, there is a monitor interface already it seems

@Ravioli5
Copy link
Contributor

Ravioli5 commented Feb 2, 2024

Is there a way to fix this?

@Ravioli5
Copy link
Contributor

Ravioli5 commented Feb 2, 2024

This happens until the wlan0mon goes down (or nexmon I'm not really sure which one)

@Ravioli5
Copy link
Contributor

Ravioli5 commented Feb 2, 2024

I found this in the thing as well.

[ 557.397707] ieee80211 phy0: brcmf_cfg80211_add_iface: iface validation failed: err=-95
[ 2712.856823] ieee80211 phy0: brcmf_fw_crashed: Firmware has halted or crashed
[ 2712.941511] ieee80211 phy0: brcmf_fil_cmd_data: bus is down. we have nothing
to do.
[ 2712.941529] ieee80211 phy0: brcmf_net_mon_stop: BRCMF_C_SET_MONITOR error (-5)
[ 2713.141342] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 2713.145532] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 2713.474046] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 2713.477451] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan 26
2024 15:07:50 version 7.45.206 (nexmon.org: 2.2.2-514-gf195c-1) FWID 01-88ee44ea

@jayofelony
Copy link
Owner

jayofelony commented Feb 2, 2024

Yep that is the crash I am talking to the nexmon devs about
seemoo-lab/nexmon#595

@Ravioli5
Copy link
Contributor

Ravioli5 commented Feb 2, 2024

Ah, ok guess I just have to wait for a bit

@jayofelony
Copy link
Owner

I will close this issue, as there is no fix and perhaps not for a while also. It is what it is I guess for now.

@Ravioli5
Copy link
Contributor

Ravioli5 commented Feb 2, 2024

Oh, I guess I'll have to live with it or wait for a while then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants
@rsun0525 @jayofelony @Ravioli5 and others