Wifi Issue on older Broadcom MBP from latest updates

dlazar · 7 August 2024 19:20

2015 MBP laptop with Broadcom driver brcmfmac.

I have two Garuda boot options. KDE or Hyprland. When I login to KDE, it works fine. However, when I log in to Hyprland, the wifi is now pooched. Won’t connect no matter what I do.

As far as I can tell, since both Hyprland and KDE were updated today, it cannot be a core OS update thing, but instead, has to be some configuration change that happened?

How the heck does someone debug this? The wpa_supplicant for older Broadcom chipsets is apparently causing all sorts of recent issues with wifi connections, but KDE has the latest and it works!

Is there something I need to read into that with Hyprland? Why would a window manager change underlying OS operational goodness?

tbg · 8 August 2024 08:00

Hi there @dlazar

It is likely a conflict between your two installations preventing your wifi from being initialized correctly in Hyprland. This is one of the reasons we do not recommend dual booting or installing multiple desktops unless you are a very Linux savvy user. Always be sure to cold boot into Hyprland to help avoid conflicts.

I would suggest masking the wpa_supplicant.service in Hyprland and install and use iwd instead.

Please be aware that our forum expects a garuda-inxi output to be posted along with all help requests. This garuda-inxi output is especially important if you wish to receive assistance with Network/WiFi issues. Be sure to post any requested outputs from within a Hyprland session.

In addition, please post the terminal output of the following command while in a Hyprland session:

hwinfo --netcard --bluetooth | grep -Ei "(speed|hotplug|model|status|cmd|file|detected|driver:)" | grep -v "Config S"

We look forward to receiving more detailed information to be able to assist you further.

dlazar · 8 August 2024 13:54

It is not a dual-boot off one partition. Each partition is a separate OS, so I see no problems due to cross-pollution of files. Here are more details though, so hopefully something jumps out as obvious as to why WIFI is suddenly DOA after working fine for many months!

Garuda INXI

System:
  Kernel: 6.10.3-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=06acdcf4-1e32-48ce-acfb-52238c8277f1 rw rootflags=subvol=@
    quiet loglevel=3 ibt=off
  Desktop: Hyprland v: 0.41.2-169-gb0a70f63 with: waybar tools: swayidle
    avail: swaylock vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Laptop System: Apple product: MacBookPro12,1 v: 1.0
    serial: <superuser required> Chassis: type: 9 v: Mac-E43C1C25D4880AD6
    serial: <superuser required>
  Mobo: Apple model: Mac-E43C1C25D4880AD6 v: MacBookPro12,1
    serial: <superuser required> uuid: <superuser required> UEFI: Apple
    v: 486.0.0.0.0 date: 08/03/2023
Battery:
  ID-1: BAT0 charge: 59.6 Wh (97.2%) condition: 61.3/74.8 Wh (82.0%)
    volts: 12.4 min: 11.4 model: DP bq20z451 type: Li-ion serial: N/A
    status: discharging cycles: 236
CPU:
  Info: model: Intel Core i5-5287U bits: 64 type: MT MCP arch: Broadwell
    gen: core 5 level: v3 note: check built: 2015-18 process: Intel 14nm
    family: 6 model-id: 0x3D (61) stepping: 4 microcode: 0x2F
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
    L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 2301 high: 2904 min/max: 500/3300 scaling:
    driver: intel_cpufreq governor: schedutil cores: 1: 500 2: 2901 3: 2900
    4: 2904 bogomips: 23201
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Iris Graphics 6100 vendor: Apple driver: i915 v: kernel
    arch: Gen-8 process: Intel 14nm built: 2014-15 ports: active: eDP-1
    empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:162b
    class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.1
    compositor: Hyprland v: 0.41.2-169-gb0a70f63 driver: X: loaded: modesetting
    alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 1
  Monitor-1: eDP-1 model: Apple Color LCD built: 2013 res: 2560x1600 hz: 60
    dpi: 227 gamma: 1.2 scale: 1.597656 size: 286x179mm (11.26x7.05")
    diag: 337mm (13.3") ratio: 16:10 modes: 2560x1600
  API: Vulkan v: 1.3.279 layers: 3 device: 0 type: integrated-gpu name: Intel
    Iris Graphics 6100 (BDW GT3) driver: mesa intel v: 24.1.5-arch1.1
    device-ID: 8086:162b surfaces: xcb,xlib,wayland device: 1 type: cpu
    name: llvmpipe (LLVM 18.1.8 256 bits) driver: mesa llvmpipe
    v: 24.1.5-arch1.1 (LLVM 18.1.8) device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel Broadwell-U Audio vendor: Apple driver: snd_hda_intel
    v: kernel bus-ID: 00:03.0 chip-ID: 8086:160c class-ID: 0403
  Device-2: Intel Wildcat Point-LP High Definition Audio
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:9ca0
    class-ID: 0403
  Device-3: Broadcom 720p FaceTime HD Camera driver: N/A pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 14e4:1570 class-ID: 0480
  API: ALSA v: k6.10.3-zen1-2-zen status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.2.2 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Broadcom BCM43602 802.11ac Wireless LAN SoC vendor: Apple
    driver: brcmfmac v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 03:00.0 chip-ID: 14e4:43ba class-ID: 0280
  IF: wlp3s0 state: dormant mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Apple Bluetooth Host Controller driver: btusb,hid-generic,usbhid
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-3:2
    chip-ID: 05ac:8290 class-ID: fe01
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2
    lmp-v: 8 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
  Local Storage: total: 523.22 GiB used: 96.14 GiB (18.4%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Apple model: SSD SM0512G
    size: 465.92 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: JA0Q scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: SanDisk model: USB 3.2Gen1
    size: 57.3 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 3.2
    spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
    fw-rev: 1.00 scheme: MBR
Partition:
  ID-1: / raw-size: 224.27 GiB size: 224.27 GiB (100.00%)
    used: 96.14 GiB (42.9%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 900 KiB (0.3%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 224.27 GiB size: 224.27 GiB (100.00%)
    used: 96.14 GiB (42.9%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
  ID-4: /var/log raw-size: 224.27 GiB size: 224.27 GiB (100.00%)
    used: 96.14 GiB (42.9%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
  ID-5: /var/tmp raw-size: 224.27 GiB size: 224.27 GiB (100.00%)
    used: 96.14 GiB (42.9%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 15.52 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 17.08 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sda3 maj-min: 8:3
Sensors:
  System Temperatures: cpu: 47.0 C pch: 47.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB available: 15.52 GiB used: 1.59 GiB (10.2%)
  Processes: 248 Power: uptime: 14h 49m states: freeze,mem,disk
    suspend: deep avail: s2idle wakeups: 2 hibernate: platform avail: shutdown,
    reboot, suspend, test_resume image: 6.2 GiB Init: systemd v: 256
    default: graphical tool: systemctl
  Packages: 1520 pm: pacman pkgs: 1514 libs: 406 tools: pacseek,paru
    pm: flatpak pkgs: 6 Compilers: gcc: 14.2.1 Shell: garuda-inxi default: Zsh
    v: 5.9 running-in: kitty inxi: 3.3.35
Garuda (2.6.26-1):
  System install date:     2024-01-31
  Last full system update: 2024-08-06
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:            NetworkManager-wait-online.service

hoping journalctl logging of NetworkManager exposes the exact issues:

systemd[1]: Starting Network Manager...
<debug> [1723123912.7388] monotonic timestamp started counting 1.516209570 seconds ago with an offset of 53289.0 seconds to CLOCK_BOOTTIME (local time is 2024-08-08 06:31:52)
<info>  [1723123912.7389] NetworkManager (version 1.48.6-1) is starting... (after a restart, boot:f8b9ce1a-7fbf-4eeb-89ee-6c8164d05703)
<info>  [1723123912.7389] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf, unmanaged-lo.conf)
<debug> [1723123912.7389] CONFIG: config-data[0x627d914e2240]: 4 groups
<debug> [1723123912.7389] CONFIG: 
<debug> [1723123912.7389] CONFIG: [main]
<debug> [1723123912.7389] CONFIG:   configure-and-quit=no
<debug> [1723123912.7389] CONFIG: 
<debug> [1723123912.7389] CONFIG: [connectivity]
<debug> [1723123912.7389] CONFIG:   uri=http://ping.archlinux.org/nm-check.txt
<debug> [1723123912.7389] CONFIG: 
<debug> [1723123912.7389] CONFIG: [keyfile]
<debug> [1723123912.7389] CONFIG:   unmanaged-devices=interface-name:lo
<debug> [1723123912.7389] CONFIG: 
<debug> [1723123912.7389] CONFIG: [logging]
<debug> [1723123912.7389] CONFIG:   level=DEBUG
<debug> [1723123912.7389] CONFIG:   domains=all
<debug> [1723123912.7390] CONFIG: 
<debug> [1723123912.7390] CONFIG: # no-auto-default file "/var/lib/NetworkManager/no-auto-default.state"
<debug> [1723123912.7390] config: state: successfully read state file "/var/lib/NetworkManager/NetworkManager.state"
<debug> [1723123912.7390] WEXT support is enabled
<debug> [1723123912.7390] create NMDBusManager singleton (727f8532206fe69b)
<debug> [1723123912.7398] bus-manager: D-Bus connection created and ObjectManager object registered
<debug> [1723123912.7399] netns[0541170d7f57eb50]: new netns (net:8, mnt:9)
<debug> [1723123912.7400] platform-linux: create (ignore netns, initial netns, use udev, no tc-cache)
<debug> [1723123912.7400] platform-linux: genl: generic netlink socket for sync operations created: port=14536, fd=11
<debug> [1723123912.7400] platform-linux: genl: generic netlink socket created: port=3505187123, fd=12
<debug> [1723123912.7400] platform-linux: rtnl: rtnetlink socket created: port=14536, fd=13
<debug> [1723123912.7401] platform-linux: populate platform cache
<debug> [1723123912.7402] platform: (lo) signal: link   added: 1: lo <UP,LOWER_UP;loopback,up,running,lowerup> mtu 65536 arp 772 loopback? not-init addrgenmode eui64 addr 00:00:00:00:00:00 brd 00:00:00:00:00:00 driver unknown tx-queue-len 1000 gso-max-size 65536 gso-max-segs 65535 gro-max-size 65536 rx:15210,1160208 tx:15210,1160208
<debug> [1723123912.7403] platform: kernel-support for IFLA_PERM_ADDRESS (IFLA_PERM_ADDRESS netlink attribute) detected: supported
<debug> [1723123912.7404] platform-linux: genl:ctrl: new family-id for nl80211: 0x26
<debug> [1723123912.7405] wifi-nl80211 (wlp3s0): using nl80211 for Wi-Fi device control
<debug> [1723123912.7406] platform: (wlp3s0) signal: link   added: 4: wlp3s0 <UP;broadcast,multicast,up> mtu 1500 arp 1 wifi? not-init addrgenmode eui64 addr A4:5E:60:C4:03:CD permaddr A4:5E:60:C4:03:CD brd FF:FF:FF:FF:FF:FF driver brcmfmac tx-queue-len 1000 gso-max-size 65536 gso-max-segs 65535 gro-max-size 65536 rx:0,0 tx:0,0
<debug> [1723123912.7406] platform: (lo) signal: address 4   added: 127.0.0.1/8 brd 0.0.0.0 lft forever pref forever lifetime 1-0[4294967295,4294967295] dev 1 flags permanent src kernel
<debug> [1723123912.7406] platform: (lo) signal: address 6   added: ::1/128 lft forever pref forever lifetime 1-0[4294967295,4294967295] dev 1 flags permanent,noprefixroute src kernel
<debug> [1723123912.7407] platform: (lo) signal: route   4   added: type local table 255 127.0.0.0/8 dev 1 metric 0 mss 0 rt-src rt-kernel scope host pref-src 127.0.0.1
<debug> [1723123912.7407] platform: (lo) signal: route   4   added: type local table 255 127.0.0.1/32 dev 1 metric 0 mss 0 rt-src rt-kernel scope host pref-src 127.0.0.1
<debug> [1723123912.7407] platform: (lo) signal: route   6   added: type local table 255 ::1/128 dev 1 metric 0 mss 0 rt-src rt-kernel
<debug> [1723123912.7407] platform: kernel-support for FRA_PROTOCOL (FRA_PROTOCOL attribute for policy routing rules) detected: supported
<debug> [1723123912.7407] platform: kernel-support for FRA_UID_RANGE (FRA_UID_RANGE attribute for policy routing rules) not detected: assume supported
<debug> [1723123912.7407] platform: kernel-support for FRA_L3MDEV (FRA_L3MDEV attribute for policy routing rules) not detected: assume supported
<debug> [1723123912.7407] platform: kernel-support for FRA_IP_PROTO (FRA_IP_PROTO, FRA_SPORT_RANGE, FRA_DPORT_RANGE attributes for policy routing rules) not detected: assume supported
<debug> [1723123912.7407] platform: signal: rt-rule   added: [4] 0: from all lookup 255 protocol 2
<debug> [1723123912.7407] platform: signal: rt-rule   added: [4] 32766: from all lookup 254 protocol 2
<debug> [1723123912.7408] platform: signal: rt-rule   added: [4] 32767: from all lookup 253 protocol 2
<debug> [1723123912.7408] platform-linux: genl:ctrl: new family-id for ethtool: 0x16
<debug> [1723123912.7408] platform-linux: genl:ctrl: new family-id for devlink: 0x17
<debug> [1723123912.7408] platform-linux: genl:ctrl: new family-id for mptcp_pm: 0x20
<debug> [1723123912.7408] platform: signal: rt-rule   added: [6] 0: from all lookup 255 protocol 2
<debug> [1723123912.7408] platform: signal: rt-rule   added: [6] 32766: from all lookup 254 protocol 2
<debug> [1723123912.7415] platform: (wlp3s0) signal: link changed: 4: wlp3s0 <UP;broadcast,multicast,up> mtu 1500 arp 1 wifi? init addrgenmode eui64 addr A4:5E:60:C4:03:CD permaddr A4:5E:60:C4:03:CD brd FF:FF:FF:FF:FF:FF driver brcmfmac tx-queue-len 1000 gso-max-size 65536 gso-max-segs 65535 gro-max-size 65536 rx:0,0 tx:0,0
<debug> [1723123912.7418] platform: (lo) signal: link changed: 1: lo <UP,LOWER_UP;loopback,up,running,lowerup> mtu 65536 arp 772 loopback? init addrgenmode eui64 addr 00:00:00:00:00:00 brd 00:00:00:00:00:00 driver unknown tx-queue-len 1000 gso-max-size 65536 gso-max-segs 65535 gro-max-size 65536 rx:15210,1160208 tx:15210,1160208
<debug> [1723123912.7418] setup NMPlatform singleton (f1851caa2ae72911)
<debug> [1723123912.7418] global-tracker: track [a7def9812e0db586,0] routing-rule "[4] 0: from all lookup 255 protocol 2"
<debug> [1723123912.7419] global-tracker: track [a7def9812e0db586,0] routing-rule "[6] 0: from all lookup 255 protocol 2"
<debug> [1723123912.7419] global-tracker: track [a7def9812e0db586,0] routing-rule "[4] 32766: from all lookup 254 protocol 2"
<debug> [1723123912.7419] global-tracker: track [a7def9812e0db586,0] routing-rule "[4] 32767: from all lookup 253 protocol 2"
<debug> [1723123912.7419] global-tracker: track [a7def9812e0db586,0] routing-rule "[6] 32766: from all lookup 254 protocol 2"
<debug> [1723123912.7419] global-tracker: track [d8a6d4ddf87f8a9d,0] routing-rule "[4] 0: from all lookup 255 protocol 2"
<debug> [1723123912.7419] global-tracker: track [d8a6d4ddf87f8a9d,0] routing-rule "[4] 32766: from all lookup 254 protocol 2"
<debug> [1723123912.7419] global-tracker: track [d8a6d4ddf87f8a9d,0] routing-rule "[4] 32767: from all lookup 253 protocol 2"
<debug> [1723123912.7419] global-tracker: track [d8a6d4ddf87f8a9d,0] routing-rule "[6] 0: from all lookup 255 protocol 2"
<debug> [1723123912.7419] global-tracker: track [d8a6d4ddf87f8a9d,0] routing-rule "[6] 32766: from all lookup 254 protocol 2"
<debug> [1723123912.7419] create NMNetns singleton (cf79a3ea49268311)
<debug> [1723123912.7421] auth[0x627d914ffda0]: create auth-manager: polkit enabled
<debug> [1723123912.7421] auth[0x627d914ffda0]: set instance
<debug> [1723123912.7421] setup NMAuthManager singleton (6f542399293336a8)
<info>  [1723123912.7424] manager[0x627d91504640]: monitoring kernel firmware directory '/lib/firmware'.
<debug> [1723123912.7424] session-monitor: using systemd-logind session tracking
<debug> [1723123912.7424] create NMSessionMonitor singleton (5f40facadaf672df)
<debug> [1723123912.7424] create NMAgentManager singleton (71ad3ffd4f0231df)
<info>  [1723123912.8034] hostname: hostname: using hostnamed
<info>  [1723123912.8034] hostname: static hostname changed from (none) to "david-macbookpro121"
<debug> [1723123912.8034] create NMHostnameManager singleton (456c6d8329e5942d)
<debug> [1723123912.8037] create NMFirewalldManager singleton (1b54a1691823f5db)
<info>  [1723123912.8038] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink
<debug> [1723123912.8039] dns-plugin[f12d11cba9bbe882]: [systemd-resolved] update-pending changed (pending)
<debug> [1723123912.8039] dns-mgr: update-pending changed: pending
<debug> [1723123912.8039] create NMDnsManager singleton (dcf7a268845f29f1)
<debug> [1723123912.8039] policy: hostname-mode: full
<info>  [1723123912.8051] rfkill3: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0/ieee80211/phy2/rfkill3) (driver brcmfmac)
<debug> [1723123912.8052] Wi-Fi rfkill switch rfkill3 state now 1/unblocked
<debug> [1723123912.8052] Wi-Fi rfkill state now 'unblocked'
<info>  [1723123912.8053] manager[0x627d91504640]: rfkill: Wi-Fi hardware radio set enabled
<info>  [1723123912.8053] manager[0x627d91504640]: rfkill: WWAN hardware radio set enabled
<debug> [1723123912.8053] setup NMManager singleton (58ad11623af6f89e)
<debug> [1723123912.8063] create NMConnectivity singleton (d86522f4effbeb2f)
<debug> [1723123912.8064] Loaded device plugin: NM6LowpanDeviceFactory (internal)
<debug> [1723123912.8065] Loaded device plugin: NMBondDeviceFactory (internal)
<debug> [1723123912.8065] Loaded device plugin: NMBridgeDeviceFactory (internal)
<debug> [1723123912.8065] Loaded device plugin: NMDummyDeviceFactory (internal)
<debug> [1723123912.8065] Loaded device plugin: NMEthernetDeviceFactory (internal)
<debug> [1723123912.8065] Loaded device plugin: NMGenericDeviceFactory (internal)
<debug> [1723123912.8065] Loaded device plugin: NMHsrDeviceFactory (internal)
<debug> [1723123912.8066] Loaded device plugin: NMInfinibandDeviceFactory (internal)
<debug> [1723123912.8066] Loaded device plugin: NMIPTunnelDeviceFactory (internal)
<debug> [1723123912.8066] Loaded device plugin: NMLoopbackDeviceFactory (internal)
<debug> [1723123912.8066] Loaded device plugin: NMMacsecDeviceFactory (internal)
<debug> [1723123912.8066] Loaded device plugin: NMMacvlanDeviceFactory (internal)
<debug> [1723123912.8066] Loaded device plugin: NMPppDeviceFactory (internal)
<debug> [1723123912.8066] Loaded device plugin: NMTunDeviceFactory (internal)
<debug> [1723123912.8067] Loaded device plugin: NMVethDeviceFactory (internal)
<debug> [1723123912.8067] Loaded device plugin: NMVlanDeviceFactory (internal)
<debug> [1723123912.8067] Loaded device plugin: NMVrfDeviceFactory (internal)
<debug> [1723123912.8067] Loaded device plugin: NMVxlanDeviceFactory (internal)
<debug> [1723123912.8067] Loaded device plugin: NMWireGuardDeviceFactory (internal)
<debug> [1723123912.8067] Loaded device plugin: NMWpanDeviceFactory (internal)
<info>  [1723123912.8071] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.48.6-1/libnm-device-plugin-adsl.so)
<info>  [1723123912.8083] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.48.6-1/libnm-device-plugin-bluetooth.so)
<info>  [1723123912.8087] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.48.6-1/libnm-device-plugin-ovs.so)
<info>  [1723123912.8161] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.48.6-1/libnm-device-plugin-team.so)
<info>  [1723123912.8165] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.48.6-1/libnm-device-plugin-wifi.so)
<info>  [1723123912.8167] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.48.6-1/libnm-device-plugin-wwan.so)
<debug> [1723123912.8169] create NMModemManager singleton (ebe4fb55b557c096)
<debug> [1723123912.8170] create NMOvsdb singleton (b3b42b943146a021)
<info>  [1723123912.8170] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
<info>  [1723123912.8170] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
<info>  [1723123912.8171] manager: Networking is disabled by state file
<debug> [1723123912.8171] dispatcher: (1) dispatching action 'hostname'
<info>  [1723123912.8173] settings: Loaded settings plugin: keyfile (internal)
<debug> [1723123912.8206] ++ connection.id             = 'WIFI602'
<debug> [1723123912.8206] ++ connection.interface-name = 'wlp3s0'
<debug> [1723123912.8206] ++ connection.permissions    = []
<debug> [1723123912.8206] ++ connection.timestamp      = 1723057825
<debug> [1723123912.8206] ++ connection.type           = '802-11-wireless'
<debug> [1723123912.8206] ++ connection.uuid           = '77c55583-f77b-4a34-bbe0-1f9d5eb49bf5'
<debug> [1723123912.8206] ++ 802-11-wireless           [ 0x627d915823a0 ]
<debug> [1723123912.8207] ++ 802-11-wireless.mac-address-blacklist = []
<debug> [1723123912.8207] ++ 802-11-wireless.mac-address-denylist = []
<debug> [1723123912.8207] ++ 802-11-wireless.mode      = 'infrastructure'
<debug> [1723123912.8207] ++ 802-11-wireless.ssid      = ((GBytes*) 0x627d91569c10)
<debug> [1723123912.8207] ++ 802-11-wireless-security  [ 0x627d915824e0 ]
<debug> [1723123912.8207] ++ 802-11-wireless-security.key-mgmt = 'wpa-psk'
<debug> [1723123912.8207] ++ 802-11-wireless-security.psk = ****
<debug> [1723123912.8207] ++ ipv4                      [ 0x627d91582680 ]
<debug> [1723123912.8207] ++ ipv4.addresses            = ((GPtrArray*) 0x627d914db010)
<debug> [1723123912.8207] ++ ipv4.dns                  = []
<debug> [1723123912.8208] ++ ipv4.method               = 'auto'
<debug> [1723123912.8208] ++ ipv4.routes               = ((GPtrArray*) 0x627d914db010)
<debug> [1723123912.8208] ++ ipv4.routing-rules        = <unknown>
<debug> [1723123912.8208] ++ ipv6                      [ 0x627d91582890 ]
<debug> [1723123912.8208] ++ ipv6.addr-gen-mode        = 1
<debug> [1723123912.8208] ++ ipv6.addresses            = ((GPtrArray*) 0x627d914db010)
<debug> [1723123912.8208] ++ ipv6.dns                  = []
<debug> [1723123912.8208] ++ ipv6.method               = 'auto'
<debug> [1723123912.8208] ++ ipv6.routes               = ((GPtrArray*) 0x627d914db010)
<debug> [1723123912.8208] ++ ipv6.routing-rules        = <unknown>
<debug> [1723123912.8213] device[90ff88f711337733] (lo): ifindex: set ifindex 1 (l3cfg: 7dddebeef72c29e5)
<debug> [1723123912.8217] device[90ff88f711337733] (lo): constructed (NMDeviceLoopback)
<debug> [1723123912.8217] device[90ff88f711337733] (lo): start setup of NMDeviceLoopback, kernel ifindex 1
<debug> [1723123912.8217] device[90ff88f711337733] (lo): hw-addr: hardware address now 00:00:00:00:00:00
<debug> [1723123912.8218] device[90ff88f711337733] (lo): hw-addr: update initial MAC address 00:00:00:00:00:00
<debug> [1723123912.8218] device[90ff88f711337733] (lo): hw-addr: unable to read permanent MAC address (use current: 00:00:00:00:00:00)
<debug> [1723123912.8218] platform-linux: error reading net:/sys/class/net/lo/phys_port_id: error reading 4096 bytes from file descriptor: Operation not supported
<debug> [1723123912.8219] platform-linux: sysctl: reading 'net:/sys/class/net/lo/dev_id': '0x0'
<debug> [1723123912.8220] platform-linux: error reading net:/sys/class/net/lo/device/sriov_numvfs: Failed to open file "device/sriov_numvfs" with openat: No such file or directory
<debug> [1723123912.8220] dhcp: init: enabled DHCP client 'dhcpcanon' (not available)
<debug> [1723123912.8221] dhcp: init: enabled DHCP client 'dhclient' (not available)
<debug> [1723123912.8221] dhcp: init: enabled DHCP client 'dhcpcd' (not available)
<debug> [1723123912.8221] dhcp: init: enabled DHCP client 'internal'
<debug> [1723123912.8221] dhcp: init: enabled DHCP client 'systemd' (undocumented internal plugin)
<debug> [1723123912.8221] dhcp: init: enabled DHCP client 'nettools' (undocumented internal plugin)
<info>  [1723123912.8221] dhcp: init: Using DHCP client 'internal'
<debug> [1723123912.8221] create NMDhcpManager singleton (df9c5850909d7e22)
<debug> [1723123912.8221] device[90ff88f711337733] (lo): unmanaged: flags set to [platform-init,!external-down=0x4/0x104/unmanaged/unrealized], set-managed [external-down=0x100])
<debug> [1723123912.8222] device[90ff88f711337733] (lo): unmanaged: flags set to [platform-init,user-settings,!external-down=0x14/0x114/unmanaged/unrealized], set-unmanaged [user-settings=0x10])
<debug> [1723123912.8222] device[90ff88f711337733] (lo): unmanaged: flags set to [user-settings,!platform-init,!external-down=0x10/0x114/unmanaged/unrealized], set-managed [platform-init=0x4])
<debug> [1723123912.8222] device[90ff88f711337733] (lo): unmanaged: flags set to [sleeping,user-settings,!platform-init,!external-down=0x11/0x115/unmanaged/unrealized], set-unmanaged [sleeping=0x1])
<info>  [1723123912.8225] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
<debug> [1723123912.8241] (wlp3s0) config: backend is "wpa_supplicant" (iwd support enabled)
<debug> [1723123912.8242] device[bae48e9914987d57] (wlp3s0): ifindex: set ifindex 4 (l3cfg: e57f5fcb758f3d61)
<debug> [1723123912.8244] device[bae48e9914987d57] (wlp3s0): constructed (NMDeviceWifi)
<info>  [1723123912.8244] device (wlp3s0): driver supports Access Point (AP) mode
<debug> [1723123912.8245] create NMSupplicantManager singleton (b1a25ed729b43dcf)
<debug> [1723123912.8246] device[bae48e9914987d57] (wlp3s0): start setup of NMDeviceWifi, kernel ifindex 4
<debug> [1723123912.8246] device[bae48e9914987d57] (wlp3s0): hw-addr: hardware address now A4:5E:60:C4:03:CD
<debug> [1723123912.8246] device[bae48e9914987d57] (wlp3s0): hw-addr: update initial MAC address A4:5E:60:C4:03:CD
<debug> [1723123912.8246] device[bae48e9914987d57] (wlp3s0): hw-addr: read permanent MAC address 'A4:5E:60:C4:03:CD'
<debug> [1723123912.8247] platform-linux: error reading net:/sys/class/net/wlp3s0/phys_port_id: error reading 4096 bytes from file descriptor: Operation not supported
<debug> [1723123912.8248] platform-linux: sysctl: reading 'net:/sys/class/net/wlp3s0/dev_id': '0x0'
<debug> [1723123912.8249] platform-linux: error reading net:/sys/class/net/wlp3s0/device/sriov_numvfs: Failed to open file "device/sriov_numvfs" with openat: No such file or directory
<debug> [1723123912.8249] device[bae48e9914987d57] (wlp3s0): unmanaged: flags set to [platform-init,!user-settings=0x4/0x14/unmanaged/unrealized], set-managed [user-settings=0x10])
<debug> [1723123912.8249] device[bae48e9914987d57] (wlp3s0): unmanaged: flags set to [!platform-init,!user-settings=0x0/0x14/managed/unrealized], set-managed [platform-init=0x4])
<debug> [1723123912.8249] manager: rfkill: Wi-Fi available 1 hw-enabled 1 sw-enabled 1
<debug> [1723123912.8250] device[bae48e9914987d57] (wlp3s0): device now enabled
<debug> [1723123912.8250] device[bae48e9914987d57] (wlp3s0): (enable): device blocked by UNMANAGED state
<debug> [1723123912.8250] device[bae48e9914987d57] (wlp3s0): unmanaged: flags set to [sleeping,!platform-init,!user-settings=0x1/0x15/unmanaged/unrealized], set-unmanaged [sleeping=0x1])
<info>  [1723123912.8253] manager: (wlp3s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/2)
<debug> [1723123912.8259] create NMVpnManager singleton (f6fffe7b61c74cdf)
<debug> [1723123912.8259] manager: creating virtual devices...
<debug> [1723123912.8259] setting up local loopback
<debug> [1723123912.8259] platform-linux: link: change 1: flags: set 0x1/0x1 ([up] / [up])
<debug> [1723123912.8260] platform-linux: do-request-link: 1 
<debug> [1723123912.8261] platform-linux: do-change-link[1]: success
systemd[1]: Started Network Manager.

dlazar · 8 August 2024 14:03

My hardware in this 2015-ish MBP is:

Broadcom BCM43602 802.11ac Wireless LAN SoC
wlp3s0
no link detected
brcmfmac is active
driver was activated with modprobe brcmfmac

As I said, strangely (Good though) the KDE version of Garuda I boot and that has the same updates, works fine. Hence this whole post trying to see why the Hyprland version of same said OS with same updates has died on me!!! So frustrating!

tbg · 8 August 2024 16:08

Generally, the fix for your WiFi having gone “dormant” is to issue the following command:

ip link set wlp3s0 mode default

If issuing this command on its own isn’t enough to reinitiate your adapter, then completely restarting your WiFi connection is sometimes required.

nmcli networking off
sleep 1
sudo systemctl stop NetworkManager
sleep 1
sudo ip link set wlp3s0 down
sleep 1
sudo modprobe -rv b43
sudo modprobe -rv b43legacy
sudo modprobe -rv ssb
sudo modprobe -rv brcm80211
sudo modprobe -rv brcmfmac
sudo modprobe -rv brcmsmac
sudo modprobe -rv bcma
sudo modprobe -rv wl
sudo modprobe -rv btusb
sleep 1
sudo rfkill unblock wifi
sleep 3
sudo modprobe -v brcmfmac
sleep 1
sudo ip link set wlp3s0 mode default
sleep 1
sudo ip link set wlp3s0 up
sleep 1
sudo systemctl start NetworkManager
sudo nmcli networking on
nmcli r wifi off
nmcli r wifi on

Please post the the input and output of any/all commands that you are requested to run.

Your Broadcom adapter sometimes has issues connecting on the 5GHz band. You may want to try lowering your channel in your router to the lowest available channel in the 5 GHz band. You could also try testing your connection on the 2.4 GHz band rather than 5GHz.

I assume you did not install and test iwd as you did not report on this. IWD sometimes improves problems with Broadcom adapters used with Linux. Of course the only real fix for Broadcom hardware is to completely macerate it in your kitchen garburator, (void where prohibited by law).

Give iwd a try and see if it improves things for you.

dlazar · 8 August 2024 16:24

The interesting thing here was the modprobe refused to unload brcmfmac because of a dependency on brcmfmac_wcc. So I unloaded that, and then the brcmfcam unloaded fine.

There was no wl module found. Only one with a not found message BTW.

After all that, she still will not connect. Tried the 2Ghz band and channel 0 and still nothing… sigh… truly a puzzle. Just busted.

dlazar · 8 August 2024 16:35

I deleted all my connections, and re-added my original working one. So that went OK till it asked for the password, which I duly provided. Now it just get stuck in an endless loop of asking for the password, even though it has the correct password.

I would love to AXE this NetworkManager code and replace it, but since this version of Garuda is not wifi enabled, deleting packages and adding new replacements seems a bit of a chore! Any tips on that?

tbg · 8 August 2024 16:37

Try deleting Network Managers state file:

sudo rm -f /var/lib/NetworkManager/NetworkManager.state

Shut down and then cold boot into Hyprland.

tbg · 8 August 2024 16:44

Sorry I didn’t see you prior post as I was posting my reply at the same time.

See this thread:

dlazar · 8 August 2024 16:53

Made no difference. I deleted said state file, rebooted Garuda. Same issue. Networking tries to fire up, flashes a dialog asking for the password with the password already filled in.

tbg · 8 August 2024 17:06

You could temporarily try disabling password authentication in your router as a troubleshooting step. Never leave your WiFi security permanently disabled. This is only for testing proposes.

I would also follow the procedure for connecting to your network from the terminal using nmcli. The instructions for doing this are on the Arch Wiki or can be found elsewhere on the net.

dlazar · 8 August 2024 17:12

nmcli manual connections to my Wifi result in

Error: Connection activation failed: Secrets were required, but not provided

So even though I provide the correct password, something in networking is borked. wpa_supplicant?

No idea, but this is frustrating as it seems to be something really stupid just out of my reach.

tbg · 8 August 2024 17:13

Try this ^^^

Also see:

Edit:

Also, disable network manager’s MAC address randomization feature. Instructions can easily be found on the Arch wiki, our forum, or the net.

I’m guessing your WiFi state is now “default” and no longer reported as"dormant", is this being reported correctly now?

tbg · 8 August 2024 17:33

See my above edits before replying please.

dlazar · 8 August 2024 17:35

Actually, doing a garuda-inxi shows it is dormant. None of that StackOverflow nmcli expo helped, but it is nice to see that there are precedents for this issue. It is sad that somehow I got something gummed up here, as it seems my only solution is to just re-install garuda from scratch and let a virgin install take over, then re-customize that all over again in whatever, 10, 20 hours… to get back to where I was!

Or, walk away from this install as a lesson in problems with me and Hyprland, take my 30 years with linux to bed to cry, and then just use the KDE version I have which does indeed still work. If that version craps out, then I just chuck this 2015 MBP in the garbage.

tbg · 8 August 2024 18:03

That would actually save you a lot of frustration in the long run. Apple hardware in general is not Linux friendly. That is not to say that it can not be made to work correctly with Linux, but it is often very difficult, (especially with Broadcom WiFi).

I have answered thousands of networking help requests, and invariably the toughest cases are always with Apple/Broadcom hardware.

Some support threads have taken over 100 posts to finally get their Broadcom WiFi working, only to break a few days later for no apparent reason. I understand your frustration, as I’ve been there on hundreds of Broadcom support cases that often go unresolved. Apple really doesn’t want their hardware to be repurposed and made useful for another decade. They want their users to go out and purchase another expensive brand new Apple product, not run Linux.

Sorry to be so negative about your hardware, but after dealing with Broadcom issues for many years it’s pretty hard to say good things about them.

dlazar · 8 August 2024 18:14

I get that. Sadly though, it was working perfect until just 2 days ago, at which point I did the usual rolling update, and added kitty terminal to my setup. That killed my wifi! So crappy. Especially as I did the same rolling update on my KDE boot, and it continues to work fine.

So there is clearly something busted somewhere, and not being cleaned out regardless the nmcli calls I have done. I wish I could rollback but unfortunately, this Hyprland install of mine is a zombie has no rollback!! So I am stuck with it as is… not working, and not fun.

At least I learned a bit about Hyprland. Was nice while it lasted!

system · 22 August 2024 18:14

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.