sometimes wi-fi works, sometimes it doesn't.

swirlystone5877 · 2025-06-12 13:08:46

to be more specific, whenever i boot up my computer, my wi-fi seemingly has a random chance of actually working. i've fixed it so far by just rebooting, but it's become far more annoying now. i looked everywhere, and i don't think anyone else has had an issue like this before. i'm not exactly sure what's relevant here, but i'm using a mac mini (late 2012) with a broadcom bcm4331 wireless card (driven by broadcom-wl) and with iwd network daemon. so far i've tried switching from broadcom-wl to other broadcom wireless drivers (actually just downloading the firmwares for b43 and removing broadcom-wl), but that just caused wi-fi to not work at all. i'm not exactly sure where to go from here.

Scimmia · 2025-06-12 13:19:42

Please see https://bbs.archlinux.org/viewtopic.php?id=57855

At this point, we don't even know what you mean that it doesn't work.

swirlystone5877 · 2025-06-12 13:22:27

ack, sorry.
"doesn't work" as in iwd attempts to connect, but it simply refuses (Operation failed). i'm not exactly sure what error logs to post, or what the problem is.

Last edited by swirlystone5877 (2025-06-12 13:25:43)

seth · 2025-06-12 13:29:50

iwd attempts to connect, but it simply refuses

The linked sticky you absolutely didn't read wrote:

That's not an exact error message, that's an intepretation of an error message. It's like playing chinese whispers.

The linked sticky you absolutely didn't read also wrote:

Full output of any command involved - don't just select what you think is relevant.
The systemd journal contains a record of almost everything that transpires on your system and has vast filtering possibilities, for example
journalctl -b
for the current boot

So… next to the actual IO, maybe the list of enabled services

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

and your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

swirlystone5877 · 2025-06-12 13:40:29

the enabled services command just gives me 24 lines of

0                 | -1

the journal is at http://0x0.st/8E45.txt (ignore the hostname, that was my brother...)

Last edited by swirlystone5877 (2025-06-12 13:41:11)

swirlystone5877 · 2025-06-12 13:49:57

...wait.
wait, im just realizing uploading that took wi-fi.
why is it just magically working again?
sorry if i sound really dumb right now, but i really have no idea what's going on.

seth · 2025-06-12 14:02:36

find /etc/systemd -type l -exec test -f {} \; -print

However, no competing service shows up in the journal.

Jun 12 08:24:31 FuckoTheClown iwd[540]: event: connect-info, ssid: Google, bss: 60:b7:6e:64:b6:63, signal: -55, load: 0/255
Jun 12 08:24:31 FuckoTheClown iwd[540]: event: state, old: autoconnect_quick, new: connecting (auto)
Jun 12 08:24:52 FuckoTheClown iwd[540]: event: state, old: connecting (auto), new: disconnecting
Jun 12 08:24:52 FuckoTheClown iwd[540]: event: state, old: disconnecting, new: disconnected
Jun 12 08:24:52 FuckoTheClown iwd[540]: event: connect-info, ssid: NETGEAR21-5G, bss: 10:da:43:8f:f1:7f, signal: -59, load: 0/255
Jun 12 08:24:52 FuckoTheClown iwd[540]: event: state, old: disconnected, new: connecting
Jun 12 08:24:52 FuckoTheClown iwd[540]: event: connect-failed, status: 1
Jun 12 08:24:52 FuckoTheClown iwd[540]: event: state, old: connecting, new: disconnected
Jun 12 08:24:52 FuckoTheClown iwd[540]: event: state, old: disconnected, new: autoconnect_quick
Jun 12 08:24:56 FuckoTheClown iwd[540]: event: connect-info, ssid: Google, bss: 60:b7:6e:64:b6:63, signal: -56, load: 0/255
Jun 12 08:24:56 FuckoTheClown iwd[540]: event: state, old: autoconnect_quick, new: connecting (auto)
Jun 12 08:24:56 FuckoTheClown iwd[540]: event: state, old: connecting (auto), new: connecting (netconfig)
Jun 12 08:24:59 FuckoTheClown iwd[540]: event: state, old: connecting (netconfig), new: connected

You can connect to the "Google" ssid, but not the "NETGEAR21-5G" one - do you expect to?
Since only one

Jun 12 08:24:43 FuckoTheClown sudo[1163]:   swirly : TTY=tty4 ; PWD=/home/swirly ; USER=root ; COMMAND=/usr/bin/iwctl

shows up to fail connecting to the netgear AP, I assume somebody who likes Scary Or Die has previously configured the google AP for you? And the network actually just works until you start to fumble with it?

swirlystone5877 · 2025-06-12 14:09:27

yes, i was expecting to connect to netgear ap, but either ap is fine.
that "somebody who likes Scary Or Die" would be my mother... i don't really know what's going on, but at least we know it's not an issue with my machine alone now... (at least i think, it's early in the morning here and i only woke up a little while ago.)

the command you posted yields this:

/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/bluetooth.target.wants/bluetooth.service
/etc/systemd/system/multi-user.target.wants/iwd.service
/etc/systemd/system/multi-user.target.wants/arRPC.service
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/multi-user.target.wants/gpm.service
/etc/systemd/system/multi-user.target.wants/avahi-daemon.service
/etc/systemd/system/multi-user.target.wants/ctroller.service
/etc/systemd/system/multi-user.target.wants/fans.service
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
/etc/systemd/system/sysinit.target.wants/systemd-resolved.service
/etc/systemd/system/sockets.target.wants/avahi-daemon.socket
/etc/systemd/system/sockets.target.wants/systemd-userdbd.socket
/etc/systemd/system/timers.target.wants/pamac-cleancache.timer
/etc/systemd/system/dbus-org.freedesktop.Avahi.service
/etc/systemd/system/dbus-org.freedesktop.resolve1.service
/etc/systemd/system/display-manager.service
/etc/systemd/system/dbus-org.bluez.service
/etc/systemd/system/dbus-org.freedesktop.timesync1.service
/etc/systemd/user/pipewire-session-manager.service
/etc/systemd/user/default.target.wants/xdg-user-dirs-update.service
/etc/systemd/user/sockets.target.wants/pipewire-pulse.socket
/etc/systemd/user/sockets.target.wants/p11-kit-server.socket
/etc/systemd/user/pipewire.service.wants/wireplumber.service

Last edited by swirlystone5877 (2025-06-12 14:11:03)

seth · 2025-06-12 14:16:17

ignore the hostname, that was my brother … "somebody who likes Scary Or Die" would be my mother

Your brother is your mother?
Well, I guess it's 2025 and brothers can be mothers, too.

We haven't seen

seth wrote:

So… next to the actual IO

meaning your iwctl session.
You may use https://man.archlinux.org/man/script.1 to log it, if you want.

swirlystone5877 · 2025-06-12 14:21:08

Your brother is your mother?

no... brother set up pc, mother set up router.

script may be found here (however, it does show it miraculously connecting again): https://files.catbox.moe/hnkhw1.ansi (i didn't know what to put for the file extension lol)
...and i'm now just realizing i forgot the timing file.

Last edited by swirlystone5877 (2025-06-12 14:23:51)

seth · 2025-06-12 15:06:41

Fucko The Clown is a character from that movie, if your brother configured the PC, he'll have added the google AP?

Either way, unless I need glasses, this doesn't show any errors and the netgear router is connected.
Please provide the actual error once you encounter a failure again.

There's a wl hiccup in the journal, but rn. all we can tell is that connecting to that AP failed once for reasons (could simply be fat-finger reasons)

Arch Linux

#1 2025-06-12 13:08:46

sometimes wi-fi works, sometimes it doesn't.

#2 2025-06-12 13:19:42

Re: sometimes wi-fi works, sometimes it doesn't.

#3 2025-06-12 13:22:27

Re: sometimes wi-fi works, sometimes it doesn't.

#4 2025-06-12 13:29:50

Re: sometimes wi-fi works, sometimes it doesn't.

#5 2025-06-12 13:40:29

Re: sometimes wi-fi works, sometimes it doesn't.

#6 2025-06-12 13:49:57

Re: sometimes wi-fi works, sometimes it doesn't.

#7 2025-06-12 14:02:36

Re: sometimes wi-fi works, sometimes it doesn't.

#8 2025-06-12 14:09:27

Re: sometimes wi-fi works, sometimes it doesn't.

#9 2025-06-12 14:16:17

Re: sometimes wi-fi works, sometimes it doesn't.

#10 2025-06-12 14:21:08

Re: sometimes wi-fi works, sometimes it doesn't.

#11 2025-06-12 15:06:41

Re: sometimes wi-fi works, sometimes it doesn't.

Board footer