[SOLVED] NM keeps connecting and fails after kernel upgrade

StJimmy · 2023-03-12 19:36:03

After installing an update to both Linux (6.2.2-arch2-1 --> 6.2.5.arch1-1) and broadcom-wl (6.30.223.271-454 --> 6.30.223.271-457), a network connection to my home wireless network cannot be established anymore. NetworkManager's indicator keeps 'spinning', and eventually gives up. nmcli monitor shows nothing other than it attempting to connect.
[EDIT: it doesn't connect to any wireless networks; setting up a WLAN hotspot on my phone yields the same result]

Hardware: "Broadcom and subsidiaries BCM43227" (requires wl, neither brcmsmac nor brcmfmac nor b43 work with it)

Rolling back both packages to their previous versions seems to be a workaround, but I'd rather not hold back these packages in the long term. The 'intermediate' packages between these versions (linux-6.2.3.arch2-1, and broadcom-wl-6.30.223.271-456) also show the same thing, so whatever is causing my issue must have happened between linux-6.2.2 and 6.2.3, and broadcom-wl-*-454 and -456.

Journal from booting the 6.2.5 kernel where it wouldn't connect: https://dpaste.com/7LX93PXCD.
(I redacted my username, hostname, and network SSID on purpose).
If other logs are needed, I'll gladly provide them.

Does anyone else experience the same thing?

Thanks in advance.

Last edited by StJimmy (2023-03-14 15:39:14)

ewaller · 2023-03-12 19:47:15

Systemd seems to be starting wpa_supplicant. If you are using NetworkManager, NetworkManager is supposed to start it.

Disable (not inhibit) wpa_supplicant if it is enabled. You might want to post the output of find /etc/systemd so we can get a look at the services you have enabled.

StJimmy · 2023-03-12 19:50:38

The weird thing is, I never manually enabled wpa_supplicant. I've not messed around with network-related services since I installed this system well over three years ago.

It also does not show up in the output of "find /etc/systemd":

/etc/systemd
/etc/systemd/network
/etc/systemd/oomd.conf
/etc/systemd/journal-upload.conf
/etc/systemd/pstore.conf
/etc/systemd/journald.conf
/etc/systemd/user
/etc/systemd/user/sockets.target.wants
/etc/systemd/user/sockets.target.wants/pulseaudio.socket
/etc/systemd/user/sockets.target.wants/p11-kit-server.socket
/etc/systemd/user/sockets.target.wants/gnome-keyring-daemon.socket
/etc/systemd/user/sockets.target.wants/gcr-ssh-agent.socket
/etc/systemd/user.conf
/etc/systemd/system.conf
/etc/systemd/journal-remote.conf
/etc/systemd/system
/etc/systemd/system/graphical.target.wants
/etc/systemd/system/graphical.target.wants/upower.service
/etc/systemd/system/timers.target.wants
/etc/systemd/system/timers.target.wants/archlinux-keyring-wkd-sync.timer
/etc/systemd/system/timers.target.wants/pacman-filesdb-refresh.timer
/etc/systemd/system/dbus-org.freedesktop.timesync1.service
/etc/systemd/system/multi-user.target.wants
/etc/systemd/system/multi-user.target.wants/acpid.service
/etc/systemd/system/multi-user.target.wants/NetworkManager.service
/etc/systemd/system/multi-user.target.wants/iptables.service
/etc/systemd/system/multi-user.target.wants/ip6tables.service
/etc/systemd/system/getty.target.wants
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/sysinit.target.wants
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
/etc/systemd/system/sleep.target.wants
/etc/systemd/system/sleep.target.wants/sxlock.service
/etc/systemd/system/network-online.target.wants
/etc/systemd/system/network-online.target.wants/NetworkManager-wait-online.service
/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service
/etc/systemd/system/sxlock.service
/etc/systemd/logind.conf
/etc/systemd/journald.conf.d
/etc/systemd/journald.conf.d/00-retention-time.conf
/etc/systemd/coredump.conf
/etc/systemd/homed.conf
/etc/systemd/timesyncd.conf
/etc/systemd/resolved.conf
/etc/systemd/networkd.conf
/etc/systemd/sleep.conf
/etc/systemd/system.conf.d
/etc/systemd/system.conf.d/user.conf

ewaller · 2023-03-12 20:48:43

I guess I was wrong. In any event, that output looks reasonable.

A shot in the dark, is your regulatory domain set correctly? Check the output of ip reg get

seth · 2023-03-12 21:00:22

wpa_supplicant is requested by NM

mrt 12 19:17:06 <redacted> dbus-daemon[288]: [system] Activating via systemd:
mrt 12 19:17:06 <redacted> dbus-daemon[288]: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
mrt 12 19:17:06 <redacted> dbus-daemon[288]: requested by ':1.3' (uid=0 pid=304 comm="/usr/bin/NetworkManager --no-daemon")

The 1st association times out across a time warp (now I've got that song in my head… great)

mrt 12 19:17:12 <redacted> wpa_supplicant[318]: wlp2s0: Trying to associate with 60:e3:27:27:a1:1d (SSID='<redacted>' freq=2412 MHz)
mrt 12 19:17:12 <redacted> NetworkManager[304]: <info>  [1678645032.0486] device (wlp2s0): supplicant interface state: disconnected -> associating
mrt 12 19:17:13 <redacted> systemd[321]: Queued start job for default target Main User Target.
mrt 12 19:17:14 <redacted> systemd-journald[171]: /var/log/journal/af0f4d3eb14544ad8e9fbf905cf46031/user-1000.journal: Monotonic clock jumped backwards relative to last journal entry, rotating.
…
mrt 12 19:17:16 <redacted> systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
mrt 12 19:17:22 <redacted> wpa_supplicant[318]: wlp2s0: Authentication with 60:e3:27:27:a1:1d timed out.

Not sure whether the subsequent failures are related to that.

Try to:
1. disable NM and start it explcitly later
2. disable https://wiki.archlinux.org/title/Networ … domization (the authentication continuously times out w/o comment and APs frequently don't like the MAC spoofing)
3. inspect the APs logs (if you can, it might hint why it's not responding)
4. connect using iwd

There're also some scan errors reported, can you detect your AP in an explcit scan (maybe after removing the configured connection)?

The pink elephant in the room is oc the out-of-tree broadcom-wl driver… and a broadcom chip.

sanza · 2023-03-12 23:40:43

Is this thing relevance?
https://github.com/raspberrypi/linux/issues/5379
https://lore.kernel.org/all/20230311141 … marcan.st/

I also experienced the same issue on raspberry pi and gpd pocket which also has a broadcom chip.

loqs · 2023-03-13 00:12:16

With the fix for the issue sanza linked https://git.kernel.org/pub/scm/linux/ke … 6b0947944a applied
https://drive.google.com/file/d/1iRfoM2 … share_link linux-6.2.5.arch1-1.1-x86_64.pkg.tar.zst
https://drive.google.com/file/d/1i6urWu … share_link linux-headers-6.2.5.arch1-1.1-x86_64.pkg.tar.zst

debo · 2023-03-13 06:44:56

I hit this problem also in linux-6.2.5. The fix that Linus pulled into the mainline seems to have solved the problem.

AndreaCattaneo · 2023-03-13 19:08:40

Same issue here.
I solved by downgrading kernel to version 6.2.1 from pacman cache

also updating to version 6.2.6 ( from testing repository ) solves the problem

You can download packages
from here: https://archlinux.org/packages/testing/ … /download/
and from here ( if you need headers ): https://archlinux.org/packages/testing/ … /download/

StJimmy · 2023-03-14 15:38:38

Sorry for the late reply lads, I've been feeling sick since yesterday.

Anyhow, upgrading to Linux 6.2.6 also fixed the issue on my end.
I'm grateful for the plentiful, informative and quick replies to this thread, however!

In regards to seth's suggestions: I did disable MAC address randomization, just to be on the safe side in the future.
And regarding your comment about Broadcom: yeah, I know... I hadn't anticipated on ever running Linux full-time when I bought this laptop some 11 years ago. Would've been nice if one of the built-in drivers supported the card, but it seems to fall just beside the use-cases for either brcmsmac or brcmfmac (both applying to - among others - some variant of the 432xx, but not the 43227...)

I'll mark this thread as solved then.
Thanks again for all your suggestions and input!

Arch Linux

#1 2023-03-12 19:36:03

[SOLVED] NM keeps connecting and fails after kernel upgrade

#2 2023-03-12 19:47:15

Re: [SOLVED] NM keeps connecting and fails after kernel upgrade

#3 2023-03-12 19:50:38

Re: [SOLVED] NM keeps connecting and fails after kernel upgrade

#4 2023-03-12 20:48:43

Re: [SOLVED] NM keeps connecting and fails after kernel upgrade

#5 2023-03-12 21:00:22

Re: [SOLVED] NM keeps connecting and fails after kernel upgrade

#6 2023-03-12 23:40:43

Re: [SOLVED] NM keeps connecting and fails after kernel upgrade

#7 2023-03-13 00:12:16

Re: [SOLVED] NM keeps connecting and fails after kernel upgrade

#8 2023-03-13 06:44:56

Re: [SOLVED] NM keeps connecting and fails after kernel upgrade

#9 2023-03-13 19:08:40

Re: [SOLVED] NM keeps connecting and fails after kernel upgrade

#10 2023-03-14 15:38:38

Re: [SOLVED] NM keeps connecting and fails after kernel upgrade

Board footer