I just recently upgraded to Fedora 30 from Fedora 29. I have noticed the following issues thus far and feel that they all may be related to a power management issue. They are as followed:
Broadcom devices using akmods, akmod-wl, broadcom-wl, from RPMFusion will not connect to wireless access points. I have been able to get it to connect a few times by pressing the wireless toggle on/off toggle key on my laptop, however, it does not connect upon start. When trying to shut down with ‘wl’ kmod loaded shutdown hangs. Even with power savings disabled in my NetworkManager configuration for WiFi, the next issue makes me think that it this issue might be related. Not to mention that if it were a driver issue I do not think one would be able to see nearby access points or any for that matter, but just not connect to them.
I am running XFCE, under power management settings I have it set to while on battery and plugged-in, suspend whenever the laptop lid is closed. When the lid is initially closed for the first time it will suspend. Once woken up and the lid is closed again or any time after that it will not suspend. Furthermore, opening a terminal and typing ‘su’ after this happens causes ‘su’ to hang and not prompt for a password. When attempting to shut down after this occurs, shutdown hangs. This issue is present even if ‘wl’ kmod is not loaded.
Hope this information can shed some light on the bugs I’ve been seeing on here about hanging shutdowns and Broadcom wireless chips having issues.
What is the exact model of your Wifi card? What does lspci show you?
The suspend issue sounds like a bug which should be opened on Red Hat Bugzilla. However, you might be able to check the logs for the suspend event to see if any errors are shown. Check your system logs by running journalctl. This might also be useful for finding out more on why Shutdown hangs while the wl module is loaded.
The Wifi card is: Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01)
Since a few days after the upgrade to Fedora 30, I have not used akmods, akmod-wl, or broadcom-wl. I have also blacklisted the bluetooth module, because it a combo Bluetooth/Wifi adapter. I have been running a USB adapter: Belkin Components F7D2102 802.11n N300 Micro Wireless Adapter v3000 [Realtek RTL8192CU]. I installed a dkms fix from github for the RTL8192CU chipset. It has been running pretty well. However, I’d say about 50% of the time shutdown hangs. So not sure as to why shutdown is hanging.
As far as the issue with suspend here are the concerns I can see from journalctl:
May 06 10:07:09 mahdev-top systemd[1]: suspend.target: Failed to set invocation ID for unit: File exists
May 06 10:07:09 mahdev-top systemd[1]: Failed to start Suspend.
The full output of journalctl is:
May 06 10:06:59 mahdev-top systemd-logind[711]: Lid closed.
May 06 10:06:59 mahdev-top dbus-broker[807]: A security policy denied :1.48 to >
May 06 10:07:00 mahdev-top NetworkManager[808]: <info> [1557155220.4678] manag>
May 06 10:07:00 mahdev-top NetworkManager[808]: <info> [1557155220.4683] manag>
May 06 10:07:00 mahdev-top systemd[1]: Reached target Sleep.
May 06 10:07:00 mahdev-top systemd[1]: Starting Suspend...
May 06 10:07:00 mahdev-top systemd-sleep[31013]: Suspending system...
May 06 10:07:00 mahdev-top kernel: PM: suspend entry (deep)
May 06 10:07:00 mahdev-top pkexec[31012]: pam_unix(polkit-1:session): session o>
May 06 10:07:00 mahdev-top audit[31012]: USER_START pid=31012 uid=1000 auid=100>
May 06 10:07:00 mahdev-top pkexec[31012]: j: Executing command [USER=root] [TTY>
May 06 10:07:00 mahdev-top dbus-broker[807]: A security policy denied :1.48 to >
May 06 10:07:01 mahdev-top kernel: PM: Syncing filesystems ... done.
May 06 10:07:01 mahdev-top slim[821]: (II) AIGLX: Suspending AIGLX clients for >
May 06 10:07:09 mahdev-top kernel: Freezing user space processes ... (elapsed 0>
May 06 10:07:09 mahdev-top kernel: OOM killer disabled.
May 06 10:07:09 mahdev-top kernel: Freezing remaining freezable tasks ... (elap>
May 06 10:07:09 mahdev-top kernel: printk: Suspending console(s) (use no_consol>
May 06 10:07:09 mahdev-top kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
May 06 10:07:09 mahdev-top kernel: sd 0:0:0:0: [sda] Stopping disk
May 06 10:07:09 mahdev-top kernel: PM: suspend devices took 0.909 seconds
May 06 10:07:09 mahdev-top kernel: ACPI: EC: interrupt blocked
May 06 10:07:09 mahdev-top kernel: ACPI: Preparing to enter system sleep state >
May 06 10:07:09 mahdev-top kernel: ACPI: EC: event blocked
May 06 10:07:09 mahdev-top kernel: ACPI: EC: EC stopped
May 06 10:07:09 mahdev-top kernel: PM: Saving platform NVS memory
May 06 10:07:09 mahdev-top kernel: Disabling non-boot CPUs ...
May 06 10:07:09 mahdev-top kernel: IRQ 29: no longer affine to CPU1
May 06 10:07:09 mahdev-top kernel: smpboot: CPU 1 is now offline
May 06 10:07:09 mahdev-top kernel: IRQ 19: no longer affine to CPU2
May 06 10:07:09 mahdev-top kernel: smpboot: CPU 2 is now offline
May 06 10:07:09 mahdev-top kernel: smpboot: CPU 3 is now offline
May 06 10:07:09 mahdev-top kernel: ACPI: Low-level resume complete
May 06 10:07:09 mahdev-top kernel: ACPI: EC: EC started
May 06 10:07:09 mahdev-top kernel: PM: Restoring platform NVS memory
May 06 10:07:09 mahdev-top kernel: LVT offset 0 assigned for vector 0x400
May 06 10:07:09 mahdev-top kernel: Enabling non-boot CPUs ...
May 06 10:07:09 mahdev-top kernel: x86: Booting SMP configuration:
May 06 10:07:09 mahdev-top kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
May 06 10:07:09 mahdev-top kernel: cache: parent cpu1 should not be sleeping
May 06 10:07:09 mahdev-top kernel: microcode: CPU1: patch_level=0x07030106
May 06 10:07:09 mahdev-top kernel: CPU1 is up
May 06 10:07:09 mahdev-top kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
May 06 10:07:09 mahdev-top kernel: cache: parent cpu2 should not be sleeping
May 06 10:07:09 mahdev-top kernel: microcode: CPU2: patch_level=0x07030106
May 06 10:07:09 mahdev-top kernel: CPU2 is up
May 06 10:07:09 mahdev-top kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
May 06 10:07:09 mahdev-top kernel: cache: parent cpu3 should not be sleeping
May 06 10:07:09 mahdev-top kernel: microcode: CPU3: patch_level=0x07030106
May 06 10:07:09 mahdev-top kernel: CPU3 is up
May 06 10:07:09 mahdev-top kernel: ACPI: Waking up from system sleep state S3
May 06 10:07:09 mahdev-top kernel: ACPI: EC: interrupt unblocked
May 06 10:07:09 mahdev-top kernel: ACPI: EC: event unblocked
May 06 10:07:09 mahdev-top kernel: smpboot: CPU 2 is now offline
May 06 10:07:09 mahdev-top kernel: smpboot: CPU 3 is now offline
May 06 10:07:09 mahdev-top kernel: ACPI: Low-level resume complete
May 06 10:07:09 mahdev-top kernel: ACPI: EC: EC started
May 06 10:07:09 mahdev-top kernel: PM: Restoring platform NVS memory
May 06 10:07:09 mahdev-top kernel: LVT offset 0 assigned for vector 0x400
May 06 10:07:09 mahdev-top kernel: Enabling non-boot CPUs ...
May 06 10:07:09 mahdev-top kernel: x86: Booting SMP configuration:
May 06 10:07:09 mahdev-top kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
May 06 10:07:09 mahdev-top kernel: cache: parent cpu1 should not be sleeping
May 06 10:07:09 mahdev-top kernel: microcode: CPU1: patch_level=0x07030106
May 06 10:07:09 mahdev-top kernel: CPU1 is up
May 06 10:07:09 mahdev-top kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
May 06 10:07:09 mahdev-top kernel: cache: parent cpu2 should not be sleeping
May 06 10:07:09 mahdev-top kernel: microcode: CPU2: patch_level=0x07030106
May 06 10:07:09 mahdev-top kernel: CPU2 is up
May 06 10:07:09 mahdev-top kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
May 06 10:07:09 mahdev-top kernel: cache: parent cpu3 should not be sleeping
May 06 10:07:09 mahdev-top kernel: microcode: CPU3: patch_level=0x07030106
May 06 10:07:09 mahdev-top kernel: CPU3 is up
May 06 10:07:09 mahdev-top kernel: ACPI: Waking up from system sleep state S3
May 06 10:07:09 mahdev-top kernel: ACPI: EC: interrupt unblocked
May 06 10:07:09 mahdev-top kernel: ACPI: EC: event unblocked
May 06 10:07:09 mahdev-top kernel: sd 0:0:0:0: [sda] Starting disk
May 06 10:07:09 mahdev-top kernel: [drm] PCIE GART of 2048M enabled (table at 0x000000000030E000).
May 06 10:07:09 mahdev-top kernel: radeon 0000:00:01.0: WB enabled
May 06 10:07:09 mahdev-top kernel: radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0x0000000023c11990
May 06 10:07:09 mahdev-top kernel: radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0x00000000d14e856f
May 06 10:07:09 mahdev-top kernel: radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0x00000000a138911d
May 06 10:07:09 mahdev-top kernel: radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0x00000000ed58bc9f
May 06 10:07:09 mahdev-top kernel: radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0x00000000f2bb4b3f
May 06 10:07:09 mahdev-top kernel: radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000078d30 and cpu addr 0x00000000554be404
May 06 10:07:09 mahdev-top kernel: radeon 0000:00:01.0: fence driver on ring 6 use gpu addr 0x0000000040000c18 and cpu addr 0x000000001f802600
May 06 10:07:09 mahdev-top kernel: radeon 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000040000c1c and cpu addr 0x00000000734c8119
May 06 10:07:09 mahdev-top kernel: [drm] ring test on 0 succeeded in 2 usecs
May 06 10:07:09 mahdev-top kernel: [drm] ring test on 1 succeeded in 2 usecs
May 06 10:07:09 mahdev-top kernel: [drm] ring test on 2 succeeded in 2 usecs
May 06 10:07:09 mahdev-top kernel: [drm] ring test on 3 succeeded in 4 usecs
May 06 10:07:09 mahdev-top kernel: [drm] ring test on 4 succeeded in 3 usecs
May 06 10:07:09 mahdev-top kernel: [drm] ring test on 5 succeeded in 1 usecs
May 06 10:07:09 mahdev-top kernel: [drm] UVD initialized successfully.
May 06 10:07:09 mahdev-top kernel: [drm] ring test on 6 succeeded in 7 usecs
May 06 10:07:09 mahdev-top kernel: [drm] ring test on 7 succeeded in 2 usecs
May 06 10:07:09 mahdev-top kernel: [drm] VCE initialized successfully.
May 06 10:07:09 mahdev-top kernel: [drm] ib test on ring 0 succeeded in 0 usecs
May 06 10:07:09 mahdev-top kernel: [drm] ib test on ring 1 succeeded in 0 usecs
May 06 10:07:09 mahdev-top kernel: [drm] ib test on ring 2 succeeded in 0 usecs
May 06 10:07:09 mahdev-top kernel: [drm] ib test on ring 3 succeeded in 0 usecs
May 06 10:07:09 mahdev-top kernel: [drm] ib test on ring 4 succeeded in 0 usecs
May 06 10:07:09 mahdev-top kernel: usb 2-1.1: reset high-speed USB device number 3 using ehci-pci
May 06 10:07:09 mahdev-top kernel: r8169 0000:04:00.0 enp4s0: Link is Down
May 06 10:07:09 mahdev-top kernel: usb 1-1.4: reset full-speed USB device number 3 using ehci-pci
May 06 10:07:09 mahdev-top kernel: [drm] ib test on ring 5 succeeded
May 06 10:07:09 mahdev-top kernel: [drm] ib test on ring 6 succeeded
May 06 10:07:09 mahdev-top kernel: [drm] ib test on ring 7 succeeded
May 06 10:07:09 mahdev-top kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
May 06 10:07:09 mahdev-top kernel: ata2.00: configured for UDMA/133
May 06 10:07:09 mahdev-top kernel: psmouse serio1: synaptics: queried max coordinates: x [..5696], y [..4884]
May 06 10:07:09 mahdev-top kernel: psmouse serio1: synaptics: queried min coordinates: x [1276..], y [1044..]
May 06 10:07:09 mahdev-top kernel: PM: resume devices took 1.806 seconds
May 06 10:07:09 mahdev-top kernel: OOM killer enabled.
May 06 10:07:09 mahdev-top kernel: Restarting tasks ... done.
May 06 10:07:09 mahdev-top systemd-logind[711]: Lid opened.
May 06 10:07:09 mahdev-top systemd[1887]: sys-devices-pci0000:00-0000:00:12.0-usb1-1\x2d1-1\x2d1.4-1\x2d1.4:1.0-bluetooth-hci0.device: Failed to set >
May 06 10:07:09 mahdev-top systemd[1]: sys-devices-pci0000:00-0000:00:12.0-usb1-1\x2d1-1\x2d1.4-1\x2d1.4:1.0-bluetooth-hci0.device: Failed to set inv>
May 06 10:07:09 mahdev-top kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 06 10:07:09 mahdev-top kernel: ata1.00: configured for UDMA/133
May 06 10:07:09 mahdev-top kernel: Bluetooth: hci0: BCM: chip id 70
May 06 10:07:09 mahdev-top kernel: Bluetooth: hci0: BCM: features 0x06
May 06 10:07:09 mahdev-top kernel: Bluetooth: hci0: BCM43142A
May 06 10:07:09 mahdev-top kernel: Bluetooth: hci0: BCM43142A0 (001.001.011) build 0000
May 06 10:07:09 mahdev-top kernel: bluetooth hci0: Direct firmware load for brcm/BCM43142A0-0a5c-216c.hcd failed with error -2
May 06 10:07:09 mahdev-top kernel: Bluetooth: hci0: BCM: Patch brcm/BCM43142A0-0a5c-216c.hcd not found
May 06 10:07:09 mahdev-top systemd-sleep[31013]: System resumed.
May 06 10:07:09 mahdev-top kernel: PM: suspend exit
May 06 10:07:09 mahdev-top systemd[1]: systemd-suspend.service: Succeeded.
May 06 10:07:09 mahdev-top systemd[1]: Started Suspend.
May 06 10:07:09 mahdev-top audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-susp>
May 06 10:07:09 mahdev-top audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspe>
May 06 10:07:09 mahdev-top systemd[1]: Stopped target Sleep.
May 06 10:07:09 mahdev-top systemd[1]: suspend.target: Failed to set invocation ID for unit: File exists
May 06 10:07:09 mahdev-top systemd[1]: Failed to start Suspend.
May 06 10:07:09 mahdev-top systemd-logind[711]: Operation 'sleep' finished.
May 06 10:07:09 mahdev-top NetworkManager[808]: <info> [1557155229.2790] manager: sleep: wake requested (sleeping: yes enabled: yes)
May 06 10:07:09 mahdev-top NetworkManager[808]: <info> [1557155229.2796] device (enp4s0): state change: unavailable -> unmanaged (reason 'sleeping',>
May 06 10:07:09 mahdev-top NetworkManager[808]: <info> [1557155229.2892] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', >
May 06 10:07:09 mahdev-top kernel: Generic PHY r8169-400:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-400:00, irq=IGNORE)
May 06 10:07:09 mahdev-top kernel: r8169 0000:04:00.0 enp4s0: Link is Down
May 06 10:07:09 mahdev-top NetworkManager[808]: <info> [1557155229.5344] manager: NetworkManager state is now DISCONNECTED
May 06 10:07:11 mahdev-top kernel: Bluetooth: hci0: command 0x1003 tx timeout
May 06 10:07:12 mahdev-top tracker-store[30975]: OK
May 06 10:07:12 mahdev-top systemd[1887]: tracker-store.service: Succeeded.
May 06 10:07:14 mahdev-top systemd[1]: systemd-rfkill.service: Succeeded.
May 06 10:07:14 mahdev-top audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkil>
May 06 10:07:14 mahdev-top systemd-logind[711]: Lid closed.
May 06 10:07:14 mahdev-top dbus-broker[807]: A security policy denied :1.48 to send method call /org/freedesktop/NetworkManager:org.freedesktop.Netwo>
May 06 10:07:15 mahdev-top NetworkManager[808]: <info> [1557155235.4583] manager: sleep: sleep requested (sleeping: no enabled: yes)
May 06 10:07:15 mahdev-top NetworkManager[808]: <info> [1557155235.4587] manager: NetworkManager state is now ASLEEP
May 06 10:07:15 mahdev-top systemd[1]: sleep.target: Failed to set invocation ID for unit: File exists
May 06 10:07:15 mahdev-top systemd[1]: Failed to start Sleep.
May 06 10:07:15 mahdev-top systemd[1]: Dependency failed for Suspend.
May 06 10:07:15 mahdev-top systemd[1]: Dependency failed for Suspend.
May 06 10:07:15 mahdev-top systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
May 06 10:07:15 mahdev-top systemd[1]: systemd-suspend.service: Job systemd-suspend.service/start failed with result 'dependency'.
May 06 10:07:15 mahdev-top systemd-logind[711]: Operation 'sleep' finished.
May 06 10:07:15 mahdev-top NetworkManager[808]: <info> [1557155235.4719] manager: sleep: wake requested (sleeping: yes enabled: yes)
May 06 10:07:15 mahdev-top NetworkManager[808]: <info> [1557155235.4721] device (enp4s0): state change: unavailable -> unmanaged (reason 'sleeping',>
May 06 10:07:15 mahdev-top NetworkManager[808]: <info> [1557155235.4836] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', >
May 06 10:07:15 mahdev-top kernel: Generic PHY r8169-400:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-400:00, irq=IGNORE)
May 06 10:07:15 mahdev-top pkexec[31070]: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
May 06 10:07:15 mahdev-top audit[31070]: USER_START pid=31070 uid=1000 auid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg>
May 06 10:07:15 mahdev-top pkexec[31070]: j: Executing command [USER=root] [TTY=unknown] [CWD=/] [COMMAND=/usr/sbin/xfpm-power-backlight-helper --set>
May 06 10:07:15 mahdev-top dbus-broker[807]: A security policy denied :1.48 to send method call /org/freedesktop/NetworkManager:org.freedesktop.Netwo>
May 06 10:07:15 mahdev-top kernel: r8169 0000:04:00.0 enp4s0: Link is Down
May 06 10:07:15 mahdev-top NetworkManager[808]: <info> [1557155235.7417] manager: NetworkManager state is now DISCONNECTED
May 06 10:07:23 mahdev-top systemd-logind[711]: Lid opened.
May 06 10:09:10 mahdev-top systemd-logind[711]: Lid closed.
May 06 10:09:10 mahdev-top dbus-broker[807]: A security policy denied :1.48 to send method call /org/freedesktop/NetworkManager:org.freedesktop.NetworkManager.Sleep to :1.5.
May 06 10:09:11 mahdev-top NetworkManager[808]: <info> [1557155351.4585] manager: sleep: sleep requested (sleeping: no enabled: yes)
May 06 10:09:11 mahdev-top NetworkManager[808]: <info> [1557155351.4590] manager: NetworkManager state is now ASLEEP
May 06 10:09:11 mahdev-top systemd[1]: sleep.target: Failed to set invocation ID for unit: File exists
May 06 10:09:11 mahdev-top systemd[1]: Failed to start Sleep.
May 06 10:09:11 mahdev-top systemd[1]: Dependency failed for Suspend.
May 06 10:09:11 mahdev-top systemd[1]: Dependency failed for Suspend.
May 06 10:09:11 mahdev-top systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
May 06 10:09:11 mahdev-top systemd[1]: systemd-suspend.service: Job systemd-suspend.service/start failed with result 'dependency'.
May 06 10:09:11 mahdev-top systemd-logind[711]: Operation 'sleep' finished.
May 06 10:09:11 mahdev-top NetworkManager[808]: <info> [1557155351.4723] manager: sleep: wake requested (sleeping: yes enabled: yes)
May 06 10:09:11 mahdev-top NetworkManager[808]: <info> [1557155351.4725] device (enp4s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
May 06 10:09:11 mahdev-top NetworkManager[808]: <info> [1557155351.4820] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
May 06 10:09:11 mahdev-top kernel: Generic PHY r8169-400:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-400:00, irq=IGNORE)
May 06 10:09:11 mahdev-top pkexec[31106]: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
May 06 10:09:11 mahdev-top audit[31106]: USER_START pid=31106 uid=1000 auid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/pkexec" hostname=? addr=? terminal=? res=success'
May 06 10:09:11 mahdev-top pkexec[31106]: j: Executing command [USER=root] [TTY=unknown] [CWD=/] [COMMAND=/usr/sbin/xfpm-power-backlight-helper --set-brightness 255]
May 06 10:09:11 mahdev-top dbus-broker[807]: A security policy denied :1.48 to send method call /org/freedesktop/NetworkManager:org.freedesktop.NetworkManager.Sleep to :1.5.
May 06 10:09:11 mahdev-top NetworkManager[808]: <info> [1557155351.7429] manager: NetworkManager state is now DISCONNECTED
May 06 10:09:11 mahdev-top kernel: r8169 0000:04:00.0 enp4s0: Link is Down
May 06 10:09:16 mahdev-top systemd-logind[711]: Lid opened.
Install the rpmfusion repos with sudo dnf install https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
And install the next things sudo dnf install kernel-devel akmod-wl it is important to update the system before this and reboot your computer. This way the kernel-devel package will match your kernel and everything will be nice and easy.
With F29 that was everything. With F30 you will need to do an extra step.
Wifi can see but can’t connect. The problem is the wpa_supplicant package. Download it from here and install it with sudo yum localinstall ./wpa_supplicant-2.6-17.fc29.x86_64.rpm This will downgrade this package, which is okey. Be aware that if you do sudo dnf update it will upgrade wpa_supplicant we do not want that. To exclude this package from upgrading, do sudo dnf update --exclude=wpa_supplicant. This should be the proper way to upgrade at least until wpa_supplicant get’s fixed…
I’ll try downgrading wpa_supplicant to the fc29 release and exclude it from future updates until a new version is available. I’ll test with the replaced version of wpa_supplicant if I still get shutdown issues. If so I’ll have to look in to that issue further. Thank you for your help!
So I’ve solved all the issues for now it seems. The advice from @p3l1gr0 for getting the Broadcom wireless adaptor to work and a little bit of research solved the suspend and power down issues. They seem to be stemming from the systemd. Specifically, in versions 240 and higher currently. See: https://github.com/systemd/systemd/issues/11810
So what I did was downgrade the systemd. In order to do that I used these steps:
Since there is no ‘systemd-rpm-macros’ for FC29’s systemd, I ran the following sudo rpm -e systemd-rpm-macros --nodeps to remove that package.
Installed the downloaded systemd RPMs: sudo yum localinstall ./systemd*.rpm
Rebooted the system
Now when I update I do sudo dnf update --exclude=wpa_supplicant,systemd* to exclude the systemd and wpa_supplicant. I will check to see if there are newer versions of wpa_supplicant (current bad version: 1:2.7-5.fc30) and systemd (current bad version: 241-8.git9ef65cb.fc30), occasionally, by not using the --exclude=wpa_supplicant,systemd*. If not I will install any updates by pressing ‘n’ then rerunning with --exclude=wpa_supplicant,systemd*.
Thanks for all the help. Hopefully, this helps anyone else facing these issues.
Hmm I had an identical symptom with FC30, of wifi networks being seen but not being able to join them. This is with the Marvel mwifiex adapter on a Surface Pro 3, and it only happens for some networks (annoyingly my work network and my phone hotspot).
I find when I boot to a kernel 5.0 series I can connect, but not when I boot to 5.1, so I don’t suspect wpa_supplicant (or else there is a relationship to its version and the kernel version).
@ mj5030 Same issue here like (2) you mention, i.e. suspend-resume borked, however generally no issue with WiFi unless I manually disconnect it (button) and then try to get it back, so far only a reboot will fix.
In my case my XFCE suspends, resumes several times until some unknown something happens, like right now perhaps Firefox waiting for me to complete the message? it had been suspending/resuming all morning until I started this message.
If this advice from @p3l1gr0 works, I’ll be a quite happy camper at least for the while. Sigh, F27 worked so well Thank you for sharing your success!
it is important to update the system before this and reboot your computer. This way the 
I disabled dnfdragora-updater.