my BCM4313 802.11bgn wireless network adapter stopped to works after last update

pier_andreit · November 28, 2020, 1:49pm

on my leap 15.1 using KDE my BCM4313 802.11bgn wireless network adapter stopped to works after last update, I don’t know if this is the correct forum or hardware is better.
the usual home wireless network where before the laptop working with automatic connection doesn’t works, a light blue circle start to rotate and no connection result, the password is ok and the other laptop connect at the same network correctly.
how can I have my wireless working again??

Sauerland · November 28, 2020, 3:45pm

Please post:

/sbin/lspci -nnk | grep -iA3 net

Also:

ping -c2 8.8.8.8

ping -c2 google.com

If first ping is running without error and second has an error as root:

netconfig update -f

pier_andreit · November 28, 2020, 5:37pm

here is

procuste@localhost:~> /sbin/lspci -nnk | grep -iA3 net02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)
        Subsystem: Askey Computer Corp. Device [144f:7179]
        Kernel driver in use: bcma-pci-bridge
        Kernel modules: bcma
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
        Subsystem: Samsung Electronics Co Ltd Device [144d:c597]
        Kernel driver in use: r8169
        Kernel modules: r8169
procuste@localhost:~>

here is

procuste@localhost:~> ping -c2 8.8.8.8connect: Network is unreachable
procuste@localhost:~> 




procuste@localhost:~> ping -c2 google.com
ping: google.com: Name or service not known
procuste@localhost:~>

both have errors

deano_ferrari · November 28, 2020, 9:53pm

Does a wireless network device node exist (as expected)?

ip link

I assume that you’re using NetworkManager. Can you show us the output of the following?

nmci d

Also, open a terminal window and then do

sudo journalctl -fu NetworkManager

Try to activate the wireless connection, then observe and capture the logging.

Sauerland · November 28, 2020, 10:53pm

Also please post:

/usr/sbin/rfkill list all

Svyatko · November 29, 2020, 8:05pm

https://wiki.archlinux.org/index.php/Broadcom_wireless

Try to use “broadcom-wl” from Packman repo.

broadcom-wl - Wireless driver for Broadcom 43xx series of chips

These packages contain Broadcom’s IEEE 802.11a/b/g/n hybrid Linux® device driver for use with Broadcom’s BCM4311-, BCM4312-, BCM4321-, and BCM4322-based hardware.

pier_andreit · November 30, 2020, 9:06pm

deano_ferrari:

Does a wireless network device node exist (as expected)?
ip link
I assume that you’re using NetworkManager. Can you show us the output of the following?
nmci d
Also, open a terminal window and then do
sudo journalctl -fu NetworkManager
Try to activate the wireless connection, then observe and capture the logging.

manythanks deano,
here is the first:

ip link----------------
procuste@localhost:~> ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether e8:11:32:71:fb:ea brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
    link/ether de:fb:eb:00:6b:b3 brd ff:ff:ff:ff:ff:ff
procuste@localhost:~>

here is the second:

I assume that you’re using NetworkManager. Can you show us the output of the following?

you assume right, at least in my intention I think I know I’m using
but your instruction result unknown

procuste@localhost:~> nmci dIf 'nmci' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    cnf nmci
procuste@localhost:~> cnf nmci
 nmci: command not found                     
procuste@localhost:~>

here is the third:

procuste@localhost:~> sudo journalctl -fu NetworkManager

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:


    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.


[sudo] password for root: 
-- Logs begin at Sat 2020-11-28 13:06:30 CET. --
nov 30 20:04:56 localhost.localdomain NetworkManager[1202]: <info>  [1606763096.2296] device (wlan0): supplicant interface state: disabled -> inactive
nov 30 20:10:11 localhost.localdomain NetworkManager[1202]: <info>  [1606763411.9920] device (wlan0): set-hw-addr: set MAC address to 2E:EC:A6:95:06:0E (scanning)
nov 30 20:10:12 localhost.localdomain NetworkManager[1202]: <info>  [1606763412.2520] device (wlan0): supplicant interface state: inactive -> disabled
nov 30 20:10:12 localhost.localdomain NetworkManager[1202]: <info>  [1606763412.2897] device (wlan0): supplicant interface state: disabled -> inactive
nov 30 20:15:27 localhost.localdomain NetworkManager[1202]: <info>  [1606763727.9636] device (wlan0): set-hw-addr: set MAC address to DE:FB:EB:00:6B:B3 (scanning)
nov 30 20:15:28 localhost.localdomain NetworkManager[1202]: <info>  [1606763728.2235] device (wlan0): supplicant interface state: inactive -> disabled
nov 30 20:15:28 localhost.localdomain NetworkManager[1202]: <info>  [1606763728.2617] device (wlan0): supplicant interface state: disabled -> inactive
nov 30 20:20:43 localhost.localdomain NetworkManager[1202]: <info>  [1606764043.9909] device (wlan0): set-hw-addr: set MAC address to D6:E0:B8:70:21:00 (scanning)
nov 30 20:20:44 localhost.localdomain NetworkManager[1202]: <info>  [1606764044.2488] device (wlan0): supplicant interface state: inactive -> disabled
nov 30 20:20:44 localhost.localdomain NetworkManager[1202]: <info>  [1606764044.2776] device (wlan0): supplicant interface state: disabled -> inactive
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.5862] device (wlan0): Activation: starting connection 'Home&Life SuperWiFi-D9A9' (9bf7a2cc-8567-4073-b678-d69d16e128b5)
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.5863] audit: op="connection-activate" uuid="9bf7a2cc-8567-4073-b678-d69d16e128b5" name="Home&Life SuperWiFi-D9A9" pid=1931 uid=1000 result="success"
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.5866] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.5868] manager: NetworkManager state is now CONNECTING
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.6055] device (wlan0): set-hw-addr: reset MAC address to E0:CA:94:34:BA:5B (preserve)
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.8626] device (wlan0): supplicant interface state: inactive -> disabled
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.8630] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.8633] device (wlan0): Activation: (wifi) access point 'Home&Life SuperWiFi-D9A9' has security, but secrets are required.
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.8633] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.8634] sup-iface[0x558952e41160,wlan0]: wps: type pbc start...
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.8672] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.8677] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.8680] device (wlan0): Activation: (wifi) connection 'Home&Life SuperWiFi-D9A9' has security, and secrets exist.  No new secrets needed.
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.8680] Config: added 'ssid' value 'Home&Life SuperWiFi-D9A9'
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.8681] Config: added 'scan_ssid' value '1'
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.8681] Config: added 'bgscan' value 'simple:30:-80:86400'
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.8681] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256'
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.8681] Config: added 'psk' value '<hidden>'
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.8681] Config: added 'ieee80211w' value '1'
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.8975] device (wlan0): supplicant interface state: disabled -> inactive
nov 30 20:23:04 localhost.localdomain NetworkManager[1202]: <info>  [1606764184.9137] device (wlan0): supplicant interface state: inactive -> scanning
nov 30 20:23:05 localhost.localdomain NetworkManager[1202]: <info>  [1606764185.6298] device (wlan0): supplicant interface state: scanning -> authenticating
nov 30 20:23:05 localhost.localdomain NetworkManager[1202]: <info>  [1606764185.6299] device (wlan0): supplicant interface state: authenticating -> associating
nov 30 20:23:05 localhost.localdomain NetworkManager[1202]: <info>  [1606764185.6421] device (wlan0): supplicant interface state: associating -> 4-way handshake
nov 30 20:23:05 localhost.localdomain NetworkManager[1202]: <info>  [1606764185.6562] device (wlan0): supplicant interface state: 4-way handshake -> group handshake
nov 30 20:23:05 localhost.localdomain NetworkManager[1202]: <warn>  [1606764185.6562] sup-iface[0x558952e41160,wlan0]: connection disconnected (reason -1)
nov 30 20:23:05 localhost.localdomain NetworkManager[1202]: <info>  [1606764185.6614] device (wlan0): supplicant interface state: group handshake -> disconnected
nov 30 20:23:05 localhost.localdomain NetworkManager[1202]: <info>  [1606764185.7615] device (wlan0): supplicant interface state: disconnected -> scanning
nov 30 20:23:16 localhost.localdomain NetworkManager[1202]: <info>  [1606764196.1938] device (wlan0): supplicant interface state: scanning -> associating
nov 30 20:23:16 localhost.localdomain NetworkManager[1202]: <info>  [1606764196.8508] device (wlan0): supplicant interface state: associating -> disconnected
nov 30 20:23:26 localhost.localdomain NetworkManager[1202]: <info>  [1606764206.8587] device (wlan0): supplicant interface state: disconnected -> scanning
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <warn>  [1606764209.9138] device (wlan0): Activation: (wifi) association took too long
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <info>  [1606764209.9138] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <warn>  [1606764209.9153] device (wlan0): Activation: (wifi) asking for new secrets
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <info>  [1606764209.9183] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <info>  [1606764209.9189] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <info>  [1606764209.9191] device (wlan0): Activation: (wifi) connection 'Home&Life SuperWiFi-D9A9' has security, and secrets exist.  No new secrets needed.
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <info>  [1606764209.9191] Config: added 'ssid' value 'Home&Life SuperWiFi-D9A9'
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <info>  [1606764209.9192] Config: added 'scan_ssid' value '1'
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <info>  [1606764209.9192] Config: added 'bgscan' value 'simple:30:-80:86400'
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <info>  [1606764209.9192] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256'
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <info>  [1606764209.9192] Config: added 'psk' value '<hidden>'
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <info>  [1606764209.9192] Config: added 'ieee80211w' value '1'
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <info>  [1606764209.9353] device (wlan0): supplicant interface state: scanning -> associating
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <info>  [1606764209.9840] device (wlan0): supplicant interface state: associating -> 4-way handshake
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <info>  [1606764209.9942] device (wlan0): supplicant interface state: 4-way handshake -> group handshake
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <warn>  [1606764209.9943] sup-iface[0x558952e41160,wlan0]: connection disconnected (reason -1)
nov 30 20:23:29 localhost.localdomain NetworkManager[1202]: <info>  [1606764209.9995] device (wlan0): supplicant interface state: group handshake -> disconnected
nov 30 20:23:30 localhost.localdomain NetworkManager[1202]: <info>  [1606764210.0995] device (wlan0): supplicant interface state: disconnected -> scanning

pier_andreit · November 30, 2020, 9:07pm

manythanks sauerland.
hee is:

procuste@localhost:~> /usr/sbin/rfkill list all0: samsung-wlan: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: samsung-bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
2: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
4: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
procuste@localhost:~>

pier_andreit · November 30, 2020, 9:11pm

manythanks svyatko, I downloaded and installed this
broadcom-wl-kmp-default-6.30.223.271_k4.12.14_lp151.28.83-pm151.14.4.x86_64.rpm
from here
https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.1/Essentials/x86_64/
rebooted, but nothing changed, the wireless icon with an orange question point “?” and when I try to connect a light blue circle round and connection doesn’t works

deano_ferrari · November 30, 2020, 9:54pm

pier_andreit:

here is the second:

you assume right, at least in my intention I think I know I’m using
but your instruction result unknown
procuste@localhost:~> nmci dIf 'nmci' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    cnf nmci
procuste@localhost:~> cnf nmci
 nmci: command not found                     
procuste@localhost:~> 

Sorry, that was a typo. The command is ‘nmcli’

deano_ferrari · November 30, 2020, 10:02pm

Confirm which driver is now loaded…

/sbin/lspci -nnk | grep -iA3 net

pier_andreit · November 30, 2020, 11:29pm

ok, there are 21 of this:

procuste@localhost:~> nmcli
wlan0: disconnected        "Broadcom Limited BCM4313 802.11bgn Wireless Network Adapt>
        2 connections available
        wifi (brcmsmac), 4E:8B:B8:01:87:8B, hw, mtu 1500


eth0: unavailable
        "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Co>
        ethernet (r8169), E8:11:32:71:FB:EA, hw, mtu 1500


lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

......................

wlan0: disconnected        "Broadcom Limited BCM4313 802.11bgn Wireless Network Adapt>
        2 connections available
        wifi (brcmsmac), 4E:8B:B8:01:87:8B, hw, mtu 1500


eth0: unavailable
        "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Co>
        ethernet (r8169), E8:11:32:71:FB:EA, hw, mtu 1500


lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
lines 1-12

pier_andreit · November 30, 2020, 11:30pm

and here is this other:

procuste@localhost:~> /sbin/lspci -nnk | grep -iA3 net
02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)
        Subsystem: Askey Computer Corp. Device [144f:7179]
        Kernel driver in use: bcma-pci-bridge
        Kernel modules: bcma, wl
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
        Subsystem: Samsung Electronics Co Ltd Device [144d:c597]
        Kernel driver in use: r8169
        Kernel modules: r8169
procuste@localhost:~>

deano_ferrari · November 30, 2020, 11:49pm

pier_andreit:

and here is this other:

procuste@localhost:~> /sbin/lspci -nnk | grep -iA3 net
02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)
        Subsystem: Askey Computer Corp. Device [144f:7179]
        Kernel driver in use: bcma-pci-bridge
        Kernel modules: bcma, wl

Ok, the wl module isn’t loaded.

Blacklist the bcma modules…

sudo nano /etc/modprobe.d/blacklist.conf

and add

blacklist bcma 
blacklist bcma-pci-bridge

then reboot. Report back.

Sauerland · November 30, 2020, 11:50pm

You need two rpms:
the kmp and the blacklist rpm.

You have only installed the kmp package.

Its the broadcom-wl which has the blacklist file inside…

deano_ferrari · November 30, 2020, 11:51pm

Yes, that makes sense.

pier_andreit · December 1, 2020, 7:48pm

maaaaaanythanks boyslol! I downloaded and installed also the software suggested from Sauerland
broadcom-wl-6.30.223.271-pm151.14.4.x86_64.rpm
rebooted, and everything start to work again…rotfl!